From 797750a4dcb627e22353c1e98a006343e8e3f17d Mon Sep 17 00:00:00 2001
From: hvm-docs-refresh <actions@jpaul.io>
Date: Fri, 22 May 2026 19:31:35 +0000
Subject: [PATCH] =?UTF-8?q?weekly=20refresh:=202026-05-22T19:31Z=20?=
 =?UTF-8?q?=E2=80=94=201599=20content=20change(s)=20across=207=20bundle(s)?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

1599 content change(s) across 7 bundle(s)
1599 sidecar metadata update(s)
7 new bundle(s) added

Bundles with content changes:
  morpheus_quickspecs (NEW): 1 page(s)
    - a50009231enw
  morpheus_release_notes_8_1_0 (NEW): 1 page(s)
    - sd00007496en_us
  morpheus_release_notes_8_1_1 (NEW): 1 page(s)
    - sd00007610en_us
  morpheus_release_notes_8_1_2 (NEW): 1 page(s)
    - sd00007733en_us
  morpheus_user_manual_8_1_0 (NEW): 531 page(s)
    - GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
    - GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
    - GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
    - GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
    - GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
    ... and 526 more
  morpheus_user_manual_8_1_1 (NEW): 532 page(s)
    - GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
    - GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
    - GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
    - GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
    - GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
    ... and 527 more
  morpheus_user_manual_8_1_2 (NEW): 532 page(s)
    - GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F
    - GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1
    - GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1
    - GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5
    - GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C
    ... and 527 more
---
 corpus/.digest/history.jsonl                  |    0
 corpus/morpheus_quickspecs/a50009231enw.json  |   12 +
 corpus/morpheus_quickspecs/a50009231enw.md    |  111 ++
 .../sd00007496en_us.json                      |   26 +
 .../sd00007496en_us.md                        |   75 +
 .../sd00007610en_us.json                      |   26 +
 .../sd00007610en_us.md                        |   51 +
 .../sd00007733en_us.json                      |   26 +
 .../sd00007733en_us.md                        |   77 +
 ...-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json |   26 +
 ...ID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md |   19 +
 ...-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json |   26 +
 ...ID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md |   18 +
 ...-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json |   26 +
 ...ID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md |   88 ++
 ...-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json |   26 +
 ...ID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md |   52 +
 ...-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json |   26 +
 ...ID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md |    9 +
 ...-030A6638-D9C6-492A-A021-8634B29738F7.json |   26 +
 ...ID-030A6638-D9C6-492A-A021-8634B29738F7.md |   63 +
 ...-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json |   26 +
 ...ID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md |   16 +
 ...-034C870E-F6DE-4D0B-950B-23A627D33C65.json |   26 +
 ...ID-034C870E-F6DE-4D0B-950B-23A627D33C65.md |   14 +
 ...-038058DD-CC8D-41F7-AF14-DB01B16993C4.json |   26 +
 ...ID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md |   41 +
 ...-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json |   26 +
 ...ID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md |   60 +
 ...-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json |   26 +
 ...ID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md |    7 +
 ...-0441F3DD-FF73-49C0-8900-718B95266989.json |   26 +
 ...ID-0441F3DD-FF73-49C0-8900-718B95266989.md |  262 ++++
 ...-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json |   26 +
 ...ID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md |  115 ++
 ...-06D232B4-F473-44C5-AD24-AECD128273E5.json |   26 +
 ...ID-06D232B4-F473-44C5-AD24-AECD128273E5.md |  136 ++
 ...-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json |   26 +
 ...ID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md |   14 +
 ...-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json |   26 +
 ...ID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md |   32 +
 ...-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json |   26 +
 ...ID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md |   71 +
 ...-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json |   26 +
 ...ID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md |   10 +
 ...-092B4E74-3662-4E21-9DA0-67958362DBE4.json |   26 +
 ...ID-092B4E74-3662-4E21-9DA0-67958362DBE4.md |   24 +
 ...-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json |   26 +
 ...ID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md |   22 +
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |   26 +
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |    8 +
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |   26 +
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   34 +
 ...-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json |   26 +
 ...ID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md |   50 +
 ...-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json |   26 +
 ...ID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md |   12 +
 ...-0BBD18FA-91D0-406A-B004-3F068114DE70.json |   26 +
 ...ID-0BBD18FA-91D0-406A-B004-3F068114DE70.md |   61 +
 ...-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json |   26 +
 ...ID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md |  113 ++
 ...-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json |   26 +
 ...ID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md |   22 +
 ...-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json |   26 +
 ...ID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md |   21 +
 ...-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json |   26 +
 ...ID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md |   54 +
 ...-101B0634-4367-4B11-ACA0-923AC1CA635E.json |   26 +
 ...ID-101B0634-4367-4B11-ACA0-923AC1CA635E.md |   19 +
 ...-10BE13E9-1014-4162-97E7-A1056FED89B3.json |   26 +
 ...ID-10BE13E9-1014-4162-97E7-A1056FED89B3.md |   24 +
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |   26 +
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |    7 +
 ...-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json |   26 +
 ...ID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md |   12 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |   26 +
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |   14 +
 ...-127B939B-0C18-40CC-AC49-8DD0D58BE444.json |   26 +
 ...ID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md |   35 +
 ...-133E4178-5B4C-4BFF-8213-2662774F0B37.json |   26 +
 ...ID-133E4178-5B4C-4BFF-8213-2662774F0B37.md |   20 +
 ...-13940199-9CEA-485B-87AF-AB47536CD6AE.json |   26 +
 ...ID-13940199-9CEA-485B-87AF-AB47536CD6AE.md |  306 ++++
 ...-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json |   26 +
 ...ID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md |   22 +
 ...-13B77F8D-BA84-4649-A4C1-D137357E7A78.json |   26 +
 ...ID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md |  124 ++
 ...-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json |   26 +
 ...ID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md |   31 +
 ...-151B596B-EE69-4D4B-8C80-964A90D3523C.json |   26 +
 ...ID-151B596B-EE69-4D4B-8C80-964A90D3523C.md |   28 +
 ...-151C50C5-5883-4137-A9B0-EAF5F8087117.json |   26 +
 ...ID-151C50C5-5883-4137-A9B0-EAF5F8087117.md |   40 +
 ...-1621A716-2765-4655-B4D0-C95B8416F4D3.json |   26 +
 ...ID-1621A716-2765-4655-B4D0-C95B8416F4D3.md |   22 +
 ...-173469C2-D5C6-47F6-8A01-41C3D73B679B.json |   26 +
 ...ID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md |   45 +
 ...-1741A126-636E-4A96-812C-48A8B7A25E88.json |   26 +
 ...ID-1741A126-636E-4A96-812C-48A8B7A25E88.md |   23 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |   26 +
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   13 +
 ...-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json |   26 +
 ...ID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md |  450 ++++++
 ...-180B8370-AEF2-45C1-9E72-99FF796CB222.json |   26 +
 ...ID-180B8370-AEF2-45C1-9E72-99FF796CB222.md |   39 +
 ...-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json |   26 +
 ...ID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md |   81 +
 ...-1AA91E38-BE43-4571-ADEB-714F77E9E728.json |   26 +
 ...ID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md |   62 +
 ...-1AC5F825-20D5-4B28-936A-2DD024250026.json |   26 +
 ...ID-1AC5F825-20D5-4B28-936A-2DD024250026.md |    6 +
 ...-1B184F05-C570-446E-8C3A-FC24792DE213.json |   26 +
 ...ID-1B184F05-C570-446E-8C3A-FC24792DE213.md |   28 +
 ...-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json |   26 +
 ...ID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md |  176 +++
 ...-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json |   26 +
 ...ID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md |   48 +
 ...-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json |   26 +
 ...ID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md |  124 ++
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |   26 +
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |    9 +
 ...-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json |   26 +
 ...ID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md |   15 +
 ...-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json |   26 +
 ...ID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md |    3 +
 ...-1E710344-0932-4A51-B605-18AEF716E46F.json |   26 +
 ...ID-1E710344-0932-4A51-B605-18AEF716E46F.md |  115 ++
 ...-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json |   26 +
 ...ID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md |  161 ++
 ...-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json |   26 +
 ...ID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md |  140 ++
 ...-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json |   26 +
 ...ID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md |   63 +
 ...-1F30FE4D-FAD1-444B-9570-E20C339F257C.json |   26 +
 ...ID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md |  227 +++
 ...-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json |   26 +
 ...ID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md |    9 +
 ...-1FE536B8-0BE2-4851-8801-174C49D984F3.json |   26 +
 ...ID-1FE536B8-0BE2-4851-8801-174C49D984F3.md |   10 +
 ...-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json |   26 +
 ...ID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md |   12 +
 ...-20D6853D-60F1-45A8-90F5-47E242D57DB4.json |   26 +
 ...ID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md |   91 ++
 ...-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json |   26 +
 ...ID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md |   12 +
 ...-21F2F208-7360-4468-B1FF-524CA30CB993.json |   26 +
 ...ID-21F2F208-7360-4468-B1FF-524CA30CB993.md |   21 +
 ...-2277183A-E315-4439-A885-C111A77C7154.json |   26 +
 ...ID-2277183A-E315-4439-A885-C111A77C7154.md |   80 +
 ...-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json |   26 +
 ...ID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md |  240 +++
 ...-25A367DD-64FA-417A-B88B-B1D95C3E258B.json |   26 +
 ...ID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md |  128 ++
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |   26 +
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  199 +++
 ...-269D2944-5080-4897-86F5-AC949F4B83F1.json |   26 +
 ...ID-269D2944-5080-4897-86F5-AC949F4B83F1.md |   34 +
 ...-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json |   26 +
 ...ID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md |    8 +
 ...-27706317-FA6C-49E6-8D44-FAE2E35217F8.json |   26 +
 ...ID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md |   42 +
 ...-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json |   26 +
 ...ID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md |  130 ++
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |   26 +
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |    9 +
 ...-29661D5A-2426-4114-B839-1242C7A7D6A8.json |   26 +
 ...ID-29661D5A-2426-4114-B839-1242C7A7D6A8.md |   50 +
 ...-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json |   26 +
 ...ID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md |   36 +
 ...-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json |   26 +
 ...ID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md |   51 +
 ...-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json |   26 +
 ...ID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md |   28 +
 ...-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json |   26 +
 ...ID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md |   20 +
 ...-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json |   26 +
 ...ID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md |    8 +
 ...-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json |   26 +
 ...ID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md |   52 +
 ...-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json |   26 +
 ...ID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md |   10 +
 ...-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json |   26 +
 ...ID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md |  220 +++
 ...-2D22E37B-3698-46F3-88BB-A36D96C849EF.json |   26 +
 ...ID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md |  207 +++
 ...-2D8A0A86-2231-4239-AB44-5475B4AE0827.json |   26 +
 ...ID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md |  489 ++++++
 ...-2DE45951-E56A-4651-AB77-F8C894E28788.json |   26 +
 ...ID-2DE45951-E56A-4651-AB77-F8C894E28788.md |   32 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |   26 +
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   39 +
 ...-2DFC3858-043A-4053-AB10-F4534C7D7240.json |   26 +
 ...ID-2DFC3858-043A-4053-AB10-F4534C7D7240.md |   56 +
 ...-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json |   26 +
 ...ID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md |   26 +
 ...-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json |   26 +
 ...ID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md |  156 ++
 ...-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json |   26 +
 ...ID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md |  104 ++
 ...-2F776F04-B8E7-428D-823B-AB121DFE48AB.json |   26 +
 ...ID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md |   15 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |   26 +
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |  462 ++++++
 ...-3148715A-05C1-4793-9B2B-6DB66D7C101D.json |   26 +
 ...ID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md |   43 +
 ...-3159C5BA-04D5-4035-9842-86197618F7D2.json |   26 +
 ...ID-3159C5BA-04D5-4035-9842-86197618F7D2.md |  363 +++++
 ...-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json |   26 +
 ...ID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md |    8 +
 ...-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json |   26 +
 ...ID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md |  188 +++
 ...-32D8CBBE-0375-48BC-8038-E6618F94BE83.json |   26 +
 ...ID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md |  561 +++++++
 ...-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json |   26 +
 ...ID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md |  102 ++
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |   26 +
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |    6 +
 ...-3391053D-4F2A-49A4-8823-E63F708C55C4.json |   26 +
 ...ID-3391053D-4F2A-49A4-8823-E63F708C55C4.md |   21 +
 ...-33E060CF-9C8E-4AA3-971B-7C5E06954157.json |   26 +
 ...ID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md |   51 +
 ...-34DE6BFF-C4CD-4C78-A963-62798D548E61.json |   26 +
 ...ID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md |    7 +
 ...-3535B779-7CDA-4288-A03A-02E0F9552B7B.json |   26 +
 ...ID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md |   55 +
 ...-3559161C-E53A-419A-B7E5-663F1440004F.json |   26 +
 ...ID-3559161C-E53A-419A-B7E5-663F1440004F.md |    5 +
 ...-35F886E0-C4F0-42F5-AF68-AA1481040D76.json |   26 +
 ...ID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md |   92 ++
 ...-367B7FE3-99E0-438C-87C0-43F9A179B552.json |   26 +
 ...ID-367B7FE3-99E0-438C-87C0-43F9A179B552.md |   78 +
 ...-36BA3E37-26D3-488F-85C2-942C45119F02.json |   26 +
 ...ID-36BA3E37-26D3-488F-85C2-942C45119F02.md |  297 ++++
 ...-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json |   26 +
 ...ID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md |   13 +
 ...-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json |   26 +
 ...ID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md |   11 +
 ...-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json |   26 +
 ...ID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md |    5 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |   26 +
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |  112 ++
 ...-382BFCD5-DE8D-4C54-B3D6-704970132153.json |   26 +
 ...ID-382BFCD5-DE8D-4C54-B3D6-704970132153.md |  207 +++
 ...-38B4C746-179D-43CA-9205-9DC63ACC87EF.json |   26 +
 ...ID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md |  246 +++
 ...-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json |   26 +
 ...ID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md |   12 +
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |   26 +
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |   12 +
 ...-39D4284E-C733-48AD-94DE-CD929AEB0431.json |   26 +
 ...ID-39D4284E-C733-48AD-94DE-CD929AEB0431.md |  128 ++
 ...-3A38516A-B491-407B-AF69-9DF38E4266DF.json |   26 +
 ...ID-3A38516A-B491-407B-AF69-9DF38E4266DF.md |   29 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |   26 +
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |   25 +
 ...-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json |   26 +
 ...ID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md |   87 ++
 ...-3B6AC391-B993-47A2-8264-7389873C8D6D.json |   26 +
 ...ID-3B6AC391-B993-47A2-8264-7389873C8D6D.md |   16 +
 ...-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json |   26 +
 ...ID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md |   41 +
 ...-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json |   26 +
 ...ID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md |  325 ++++
 ...-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json |   26 +
 ...ID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md |   11 +
 ...-3CA69B8E-D437-40EC-9755-668930BA21F4.json |   26 +
 ...ID-3CA69B8E-D437-40EC-9755-668930BA21F4.md |  281 ++++
 ...-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json |   26 +
 ...ID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md |   33 +
 ...-3CEB493A-1086-4AE2-8220-93B372329509.json |   26 +
 ...ID-3CEB493A-1086-4AE2-8220-93B372329509.md |    5 +
 ...-3D3058F0-C2FE-4995-8D62-55A069D50709.json |   26 +
 ...ID-3D3058F0-C2FE-4995-8D62-55A069D50709.md |  139 ++
 ...-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json |   26 +
 ...ID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md |   11 +
 ...-3E6007AB-2F77-4783-8610-592F1BB9125B.json |   26 +
 ...ID-3E6007AB-2F77-4783-8610-592F1BB9125B.md |  163 ++
 ...-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json |   26 +
 ...ID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md | 1373 +++++++++++++++++
 ...-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json |   26 +
 ...ID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md |   92 ++
 ...-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json |   26 +
 ...ID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md |   86 ++
 ...-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json |   26 +
 ...ID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md |   40 +
 ...-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json |   26 +
 ...ID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md |  157 ++
 ...-421A3218-7033-4066-AF8E-AA2D46D4385C.json |   26 +
 ...ID-421A3218-7033-4066-AF8E-AA2D46D4385C.md |   26 +
 ...-44272A47-8855-48A0-B475-E940CE97DD7A.json |   26 +
 ...ID-44272A47-8855-48A0-B475-E940CE97DD7A.md |   16 +
 ...-443DA867-07E9-416F-ABFB-2C4BF2312D53.json |   26 +
 ...ID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md |  191 +++
 ...-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json |   26 +
 ...ID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md |   22 +
 ...-44644079-BC85-448F-B542-23E18E9D5602.json |   26 +
 ...ID-44644079-BC85-448F-B542-23E18E9D5602.md |   72 +
 ...-44A7BA66-FC27-40C3-8A12-2704D2043B53.json |   26 +
 ...ID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md |   69 +
 ...-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json |   26 +
 ...ID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md |   30 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |   26 +
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |  272 ++++
 ...-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json |   26 +
 ...ID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md |  130 ++
 ...-45DBACB2-9ED7-4538-9BF9-2D121178F539.json |   26 +
 ...ID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md |   47 +
 ...-46A53E20-D2A8-4233-8829-7865C7A434B7.json |   26 +
 ...ID-46A53E20-D2A8-4233-8829-7865C7A434B7.md |   42 +
 ...-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json |   26 +
 ...ID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md |   11 +
 ...-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json |   26 +
 ...ID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md |   18 +
 ...-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json |   26 +
 ...ID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md |  383 +++++
 ...-48ED6B2F-2E0B-491F-A497-139DD9B91284.json |   26 +
 ...ID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md |   17 +
 ...-49022137-A78E-4863-B1CF-D455EDD1A7D2.json |   26 +
 ...ID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md |    3 +
 ...-49067498-304A-4C38-B9C1-D8CF296DD3FA.json |   26 +
 ...ID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md |   28 +
 ...-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json |   26 +
 ...ID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md |   53 +
 ...-4983900F-0A3F-4F61-BB06-8270BE27C886.json |   26 +
 ...ID-4983900F-0A3F-4F61-BB06-8270BE27C886.md |   33 +
 ...-49F13E32-7912-4F28-8C78-5DF3AB06E690.json |   26 +
 ...ID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md |    9 +
 ...-4A13998A-C40E-4505-B1A1-16B21926D177.json |   26 +
 ...ID-4A13998A-C40E-4505-B1A1-16B21926D177.md |   15 +
 ...-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json |   26 +
 ...ID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md |   39 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |   26 +
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |    3 +
 ...-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json |   26 +
 ...ID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md |   15 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |   26 +
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |   13 +
 ...-4F4F8735-4673-4408-BDA3-C295F2A88174.json |   26 +
 ...ID-4F4F8735-4673-4408-BDA3-C295F2A88174.md |    7 +
 ...-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json |   26 +
 ...ID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md |    7 +
 ...-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json |   26 +
 ...ID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md |  257 +++
 ...-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json |   26 +
 ...ID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md |  153 ++
 ...-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json |   26 +
 ...ID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md |  301 ++++
 ...-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json |   26 +
 ...ID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md |   55 +
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |   26 +
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |    8 +
 ...-5473844F-B09C-4F23-AC2F-A305A384136B.json |   26 +
 ...ID-5473844F-B09C-4F23-AC2F-A305A384136B.md |   61 +
 ...-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json |   26 +
 ...ID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md |   41 +
 ...-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json |   26 +
 ...ID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md |   11 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |   26 +
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |    9 +
 ...-563347AC-C86B-4AC7-BF58-B80A3201662F.json |   26 +
 ...ID-563347AC-C86B-4AC7-BF58-B80A3201662F.md |   13 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |   26 +
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   27 +
 ...-56F6E993-6289-4BC0-AFD6-938516823FC8.json |   26 +
 ...ID-56F6E993-6289-4BC0-AFD6-938516823FC8.md |   15 +
 ...-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json |   26 +
 ...ID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md |  184 +++
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |   26 +
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   34 +
 ...-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json |   26 +
 ...ID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md |   31 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |   26 +
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |   25 +
 ...-589A7663-2242-4FBE-9214-FE0F91A29972.json |   26 +
 ...ID-589A7663-2242-4FBE-9214-FE0F91A29972.md |   49 +
 ...-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json |   26 +
 ...ID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md |    9 +
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |   26 +
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   13 +
 ...-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json |   26 +
 ...ID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md |  110 ++
 ...-5AE10D03-5E33-4437-8477-059B0390B662.json |   26 +
 ...ID-5AE10D03-5E33-4437-8477-059B0390B662.md |   28 +
 ...-5B7DB753-B382-4E98-BF3A-599C15334A69.json |   26 +
 ...ID-5B7DB753-B382-4E98-BF3A-599C15334A69.md |    8 +
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |   26 +
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  119 ++
 ...-5CBD20D3-D323-4F6E-A543-E19708439C5D.json |   26 +
 ...ID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md |   15 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |   26 +
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   26 +
 ...-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json |   26 +
 ...ID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md |   80 +
 ...-5D659229-2AFA-4A63-9194-D128E673AA02.json |   26 +
 ...ID-5D659229-2AFA-4A63-9194-D128E673AA02.md |   22 +
 ...-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json |   26 +
 ...ID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md |  363 +++++
 ...-5F72EBA5-E780-4511-8EA0-4ABA11628663.json |   26 +
 ...ID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md |    4 +
 ...-607895C8-5308-4A68-9219-1EA342DB9C6C.json |   26 +
 ...ID-607895C8-5308-4A68-9219-1EA342DB9C6C.md |    9 +
 ...-60BD671A-C620-49C7-81EB-56C5197E61C2.json |   26 +
 ...ID-60BD671A-C620-49C7-81EB-56C5197E61C2.md |   45 +
 ...-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json |   26 +
 ...ID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md |   31 +
 ...-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json |   26 +
 ...ID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md |   55 +
 ...-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json |   26 +
 ...ID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md |   75 +
 ...-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json |   26 +
 ...ID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md |   26 +
 ...-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json |   26 +
 ...ID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md |   64 +
 ...-633B871A-14AC-42B5-9BDA-8F907433F700.json |   26 +
 ...ID-633B871A-14AC-42B5-9BDA-8F907433F700.md |   34 +
 ...-63B50C5A-C3AD-4543-8A89-58110DDD5064.json |   26 +
 ...ID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md |  130 ++
 ...-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json |   26 +
 ...ID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md |   30 +
 ...-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json |   26 +
 ...ID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md |   16 +
 ...-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json |   26 +
 ...ID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md |   37 +
 ...-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json |   26 +
 ...ID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md |   34 +
 ...-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json |   26 +
 ...ID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md |   85 +
 ...-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json |   26 +
 ...ID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md |   22 +
 ...-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json |   26 +
 ...ID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md |  119 ++
 ...-663434D4-E8EB-4468-992C-107B9FD4AC30.json |   26 +
 ...ID-663434D4-E8EB-4468-992C-107B9FD4AC30.md |    7 +
 ...-66740846-A143-48D1-80FF-7314D86BE61A.json |   26 +
 ...ID-66740846-A143-48D1-80FF-7314D86BE61A.md |   56 +
 ...-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json |   26 +
 ...ID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md |   34 +
 ...-6779EFD7-BD52-4678-AC19-30AE09F26217.json |   26 +
 ...ID-6779EFD7-BD52-4678-AC19-30AE09F26217.md |   13 +
 ...-68E5CB99-152C-463C-9E41-5B2C67C659CD.json |   26 +
 ...ID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md |   14 +
 ...-690DD9D4-9114-4EE1-97F1-254D7B67B733.json |   26 +
 ...ID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md |    6 +
 ...-6A02D571-9949-4EA4-B43C-C2CED90210EF.json |   26 +
 ...ID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md |   20 +
 ...-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json |   26 +
 ...ID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md |   60 +
 ...-6B3D18B4-5885-4318-848F-DE294F57057B.json |   26 +
 ...ID-6B3D18B4-5885-4318-848F-DE294F57057B.md |  222 +++
 ...-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json |   26 +
 ...ID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md |   21 +
 ...-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json |   26 +
 ...ID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md |   85 +
 ...-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json |   26 +
 ...ID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md |   13 +
 ...-6C22C389-3D06-4DF0-B997-1CA161175182.json |   26 +
 ...ID-6C22C389-3D06-4DF0-B997-1CA161175182.md |  147 ++
 ...-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json |   26 +
 ...ID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md |   32 +
 ...-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json |   26 +
 ...ID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md |   56 +
 ...-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json |   26 +
 ...ID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md |   17 +
 ...-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json |   26 +
 ...ID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md |   16 +
 ...-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json |   26 +
 ...ID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md |  468 ++++++
 ...-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json |   26 +
 ...ID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md |   28 +
 ...-6FFCD815-6AC5-46F9-AB71-F293570366A8.json |   26 +
 ...ID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md |   87 ++
 ...-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json |   26 +
 ...ID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md |   71 +
 ...-7056841F-C280-4C83-8065-017EF45643F9.json |   26 +
 ...ID-7056841F-C280-4C83-8065-017EF45643F9.md |   75 +
 ...-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json |   26 +
 ...ID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md |   20 +
 ...-719570B7-BE8A-49B2-87D7-336A9703ED88.json |   26 +
 ...ID-719570B7-BE8A-49B2-87D7-336A9703ED88.md |   32 +
 ...-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json |   26 +
 ...ID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md |   12 +
 ...-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json |   26 +
 ...ID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md |  101 ++
 ...-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json |   26 +
 ...ID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md |  441 ++++++
 ...-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json |   26 +
 ...ID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md |   64 +
 ...-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json |   26 +
 ...ID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md |    5 +
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |   26 +
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |   13 +
 ...-75D89535-68AE-4507-A961-26CE8914F074.json |   26 +
 ...ID-75D89535-68AE-4507-A961-26CE8914F074.md |   96 ++
 ...-768B1CD6-73F8-4CBC-9675-E03000B36147.json |   26 +
 ...ID-768B1CD6-73F8-4CBC-9675-E03000B36147.md |    9 +
 ...-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json |   26 +
 ...ID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md |  411 +++++
 ...-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json |   26 +
 ...ID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md |   14 +
 ...-77287C89-E688-49C4-869F-652DE15478FB.json |   26 +
 ...ID-77287C89-E688-49C4-869F-652DE15478FB.md |   69 +
 ...-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json |   26 +
 ...ID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md |   32 +
 ...-786D5554-1448-4001-A39C-647F22CA9278.json |   26 +
 ...ID-786D5554-1448-4001-A39C-647F22CA9278.md |   31 +
 ...-78DC62BA-524C-456D-827F-465C10A1AA6F.json |   26 +
 ...ID-78DC62BA-524C-456D-827F-465C10A1AA6F.md |   43 +
 ...-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json |   26 +
 ...ID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md |    9 +
 ...-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json |   26 +
 ...ID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md |  100 ++
 ...-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json |   26 +
 ...ID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md |  106 ++
 ...-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json |   26 +
 ...ID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md |  439 ++++++
 ...-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json |   26 +
 ...ID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md |    8 +
 ...-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json |   26 +
 ...ID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md |   80 +
 ...-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json |   26 +
 ...ID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md |    9 +
 ...-7BD87211-4E8A-480C-A7B6-E502808743EC.json |   26 +
 ...ID-7BD87211-4E8A-480C-A7B6-E502808743EC.md |   21 +
 ...-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json |   26 +
 ...ID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md |   29 +
 ...-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json |   26 +
 ...ID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md |  888 +++++++++++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |   26 +
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   12 +
 ...-7CA53A6D-026B-4977-8247-349750CE4EB9.json |   26 +
 ...ID-7CA53A6D-026B-4977-8247-349750CE4EB9.md |   22 +
 ...-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json |   26 +
 ...ID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md |    3 +
 ...-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json |   26 +
 ...ID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md |   22 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |   26 +
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |  177 +++
 ...-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json |   26 +
 ...ID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md |   25 +
 ...-80911C58-F6AB-4001-B50E-EC0F43773A5E.json |   26 +
 ...ID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md |   15 +
 ...-8143252C-EC38-43B2-B2E0-443A60C01768.json |   26 +
 ...ID-8143252C-EC38-43B2-B2E0-443A60C01768.md |   63 +
 ...-8168FFDF-77DD-42E0-B747-95099C7852AB.json |   26 +
 ...ID-8168FFDF-77DD-42E0-B747-95099C7852AB.md |   17 +
 ...-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json |   26 +
 ...ID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md |  264 ++++
 ...-826F09D8-C40B-483D-9CB5-CE504BD18810.json |   26 +
 ...ID-826F09D8-C40B-483D-9CB5-CE504BD18810.md |   74 +
 ...-82C53DF1-4293-41E2-A90A-740C1814DD12.json |   26 +
 ...ID-82C53DF1-4293-41E2-A90A-740C1814DD12.md |   61 +
 ...-84B6C16D-5601-4CFB-9C53-47AE75271884.json |   26 +
 ...ID-84B6C16D-5601-4CFB-9C53-47AE75271884.md |  161 ++
 ...-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json |   26 +
 ...ID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md |   51 +
 ...-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json |   26 +
 ...ID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md |    3 +
 ...-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json |   26 +
 ...ID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md |    7 +
 ...-87CB98DB-3915-4176-822C-E86A5AA54C4D.json |   26 +
 ...ID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md |  322 ++++
 ...-8808CDAD-319E-4259-99D8-4D43440E63FE.json |   26 +
 ...ID-8808CDAD-319E-4259-99D8-4D43440E63FE.md |    9 +
 ...-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json |   26 +
 ...ID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md |   23 +
 ...-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json |   26 +
 ...ID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md |   20 +
 ...-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json |   26 +
 ...ID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md |   11 +
 ...-89F63373-6CC7-4498-9A70-75BB1FD6D779.json |   26 +
 ...ID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md |    6 +
 ...-89FD5558-DFD3-459B-A56D-BD998574F805.json |   26 +
 ...ID-89FD5558-DFD3-459B-A56D-BD998574F805.md |   14 +
 ...-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json |   26 +
 ...ID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md |   11 +
 ...-8A557829-64DF-4A0A-84FC-FC2C8755B391.json |   26 +
 ...ID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md |  172 +++
 ...-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json |   26 +
 ...ID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md |  191 +++
 ...-8AC08484-473F-41E8-B106-A90BC96B03C4.json |   26 +
 ...ID-8AC08484-473F-41E8-B106-A90BC96B03C4.md |   31 +
 ...-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json |   26 +
 ...ID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md |   39 +
 ...-8C608C16-055C-4708-BA01-87FACE15EF6D.json |   26 +
 ...ID-8C608C16-055C-4708-BA01-87FACE15EF6D.md |   86 ++
 ...-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json |   26 +
 ...ID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md |   30 +
 ...-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json |   26 +
 ...ID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md |    9 +
 ...-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json |   26 +
 ...ID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md |  176 +++
 ...-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json |   26 +
 ...ID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md |  212 +++
 ...-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json |   26 +
 ...ID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md |   80 +
 ...-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json |   26 +
 ...ID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md |   13 +
 ...-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json |   26 +
 ...ID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md |   20 +
 ...-9132296F-B580-4107-8041-9E30C7EC4291.json |   26 +
 ...ID-9132296F-B580-4107-8041-9E30C7EC4291.md |    8 +
 ...-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json |   26 +
 ...ID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md |   35 +
 ...-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json |   26 +
 ...ID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md |   17 +
 ...-9372294C-3A13-490D-BF63-BA01AB008C43.json |   26 +
 ...ID-9372294C-3A13-490D-BF63-BA01AB008C43.md |   11 +
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |   26 +
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  116 ++
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |   26 +
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |   13 +
 ...-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json |   26 +
 ...ID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md |    8 +
 ...-96732ACE-6F43-453A-8F9B-FD0F1C717362.json |   26 +
 ...ID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md |   33 +
 ...-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json |   26 +
 ...ID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md |  268 ++++
 ...-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json |   26 +
 ...ID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md |   64 +
 ...-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json |   26 +
 ...ID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md |  135 ++
 ...-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json |   26 +
 ...ID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md |    3 +
 ...-98351F93-76B4-480B-91F1-58E3E3492651.json |   26 +
 ...ID-98351F93-76B4-480B-91F1-58E3E3492651.md |  152 ++
 ...-9B75C475-9243-4444-BF22-C43480298274.json |   26 +
 ...ID-9B75C475-9243-4444-BF22-C43480298274.md |   15 +
 ...-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json |   26 +
 ...ID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md |   17 +
 ...-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json |   26 +
 ...ID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md |    9 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |   26 +
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   38 +
 ...-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json |   26 +
 ...ID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md |  185 +++
 ...-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json |   26 +
 ...ID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md |   10 +
 ...-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json |   26 +
 ...ID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md |   33 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |   26 +
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |  142 ++
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |   26 +
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |  116 ++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |   26 +
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   53 +
 ...-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json |   26 +
 ...ID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md |   10 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |   26 +
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |   24 +
 ...-9ECF72A1-9565-4202-A087-82313C2F8D58.json |   26 +
 ...ID-9ECF72A1-9565-4202-A087-82313C2F8D58.md |   58 +
 ...-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json |   26 +
 ...ID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md |   14 +
 ...-9F022B96-52CA-499B-978C-2CB55DCCAF48.json |   26 +
 ...ID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md |   80 +
 ...-9F78ED42-26BC-405F-88BC-3B14279A3306.json |   26 +
 ...ID-9F78ED42-26BC-405F-88BC-3B14279A3306.md |   32 +
 ...-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json |   26 +
 ...ID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md |   69 +
 ...-A0DC9F48-028D-4283-8572-FDD0A432E125.json |   26 +
 ...ID-A0DC9F48-028D-4283-8572-FDD0A432E125.md |   27 +
 ...-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json |   26 +
 ...ID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md |  264 ++++
 ...-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json |   26 +
 ...ID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md |   94 ++
 ...-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json |   26 +
 ...ID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md |   15 +
 ...-A2766933-3113-44EF-8458-88636F4301B3.json |   26 +
 ...ID-A2766933-3113-44EF-8458-88636F4301B3.md |    3 +
 ...-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json |   26 +
 ...ID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md |  146 ++
 ...-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json |   26 +
 ...ID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md |   38 +
 ...-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json |   26 +
 ...ID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md |   19 +
 ...-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json |   26 +
 ...ID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md |   13 +
 ...-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json |   26 +
 ...ID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md |   21 +
 ...-A50734F6-41F7-4350-B07E-92C559E94119.json |   26 +
 ...ID-A50734F6-41F7-4350-B07E-92C559E94119.md |   30 +
 ...-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json |   26 +
 ...ID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md |   19 +
 ...-A586E426-9C40-4FD0-B749-7E962F9F04C4.json |   26 +
 ...ID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md |    9 +
 ...-A75681BD-B103-4441-AAD7-E1F848FFE56E.json |   26 +
 ...ID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md |    5 +
 ...-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json |   26 +
 ...ID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md |   97 ++
 ...-AB0E1772-B646-49E2-8318-B2495341839D.json |   26 +
 ...ID-AB0E1772-B646-49E2-8318-B2495341839D.md |   11 +
 ...-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json |   26 +
 ...ID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md |   95 ++
 ...-AB883016-0848-46D7-8BB0-37DF09076725.json |   26 +
 ...ID-AB883016-0848-46D7-8BB0-37DF09076725.md |   15 +
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |   26 +
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   41 +
 ...-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json |   26 +
 ...ID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md |   57 +
 ...-AB95E8ED-82A1-493E-82D0-613D80FB602E.json |   26 +
 ...ID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md |   31 +
 ...-ABC2295F-BA5B-49C6-BF73-263A724F948F.json |   26 +
 ...ID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md |  959 ++++++++++++
 ...-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json |   26 +
 ...ID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md |   34 +
 ...-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json |   26 +
 ...ID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md |   36 +
 ...-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json |   26 +
 ...ID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md |    7 +
 ...-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json |   26 +
 ...ID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md |   11 +
 ...-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json |   26 +
 ...ID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md |   14 +
 ...-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json |   26 +
 ...ID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md |   12 +
 ...-ADDC3274-0758-43B9-BF31-6EA3EB319288.json |   26 +
 ...ID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md |   32 +
 ...-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json |   26 +
 ...ID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md |    8 +
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |   26 +
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   19 +
 ...-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json |   26 +
 ...ID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md |   57 +
 ...-AFA85086-2874-4303-8999-E919DF886C44.json |   26 +
 ...ID-AFA85086-2874-4303-8999-E919DF886C44.md |   31 +
 ...-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json |   26 +
 ...ID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md |  300 ++++
 ...-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json |   26 +
 ...ID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md |   55 +
 ...-B2113088-6A1D-4A43-A781-BD280C35FA69.json |   26 +
 ...ID-B2113088-6A1D-4A43-A781-BD280C35FA69.md |   18 +
 ...-B299B747-2692-4406-9FCD-760C2EFE1E65.json |   26 +
 ...ID-B299B747-2692-4406-9FCD-760C2EFE1E65.md |   15 +
 ...-B379FDF9-2963-4336-AFC1-14372793FA70.json |   26 +
 ...ID-B379FDF9-2963-4336-AFC1-14372793FA70.md |   21 +
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |   26 +
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |  183 +++
 ...-B47A4967-DCA3-45C4-B983-83CEB43711DC.json |   26 +
 ...ID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md |  295 ++++
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |   26 +
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |    3 +
 ...-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json |   26 +
 ...ID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md |   16 +
 ...-B637812E-A51A-4AD5-B6F1-5E5822709711.json |   26 +
 ...ID-B637812E-A51A-4AD5-B6F1-5E5822709711.md |   23 +
 ...-B67FF274-342F-4B96-B5F9-0B8222C662DC.json |   26 +
 ...ID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md |    3 +
 ...-B6D4283B-948C-4722-8C96-21CDB727D0EE.json |   26 +
 ...ID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md |   90 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |   26 +
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |    6 +
 ...-B73068EC-E619-4EA2-B84B-D4941E1D1779.json |   26 +
 ...ID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md |  314 ++++
 ...-B7496F21-B633-436F-850B-507E482F96F2.json |   26 +
 ...ID-B7496F21-B633-436F-850B-507E482F96F2.md |   30 +
 ...-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json |   26 +
 ...ID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md |   38 +
 ...-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json |   26 +
 ...ID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md |   11 +
 ...-B7E3F043-2330-4392-9803-B649558F488B.json |   26 +
 ...ID-B7E3F043-2330-4392-9803-B649558F488B.md |   10 +
 ...-B86C6485-C80C-480F-87B4-4352963D74A5.json |   26 +
 ...ID-B86C6485-C80C-480F-87B4-4352963D74A5.md |   93 ++
 ...-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json |   26 +
 ...ID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md |   78 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |   26 +
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   40 +
 ...-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json |   26 +
 ...ID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md |   39 +
 ...-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json |   26 +
 ...ID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md |   29 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |   26 +
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   60 +
 ...-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json |   26 +
 ...ID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md |   47 +
 ...-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json |   26 +
 ...ID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md |  182 +++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |   26 +
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   15 +
 ...-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json |   26 +
 ...ID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md |  179 +++
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |   26 +
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |   52 +
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |   26 +
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |   28 +
 ...-BD4F0587-C0E9-4120-9D74-B54015579A60.json |   26 +
 ...ID-BD4F0587-C0E9-4120-9D74-B54015579A60.md |    6 +
 ...-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json |   26 +
 ...ID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md |   26 +
 ...-BE80C9FF-D456-4120-937D-6FB30FA422D4.json |   26 +
 ...ID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md |   13 +
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |   26 +
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  591 +++++++
 ...-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json |   26 +
 ...ID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md |    9 +
 ...-BF226F62-E06D-4C61-8326-523D3F8CE492.json |   26 +
 ...ID-BF226F62-E06D-4C61-8326-523D3F8CE492.md |    8 +
 ...-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json |   26 +
 ...ID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md |   32 +
 ...-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json |   26 +
 ...ID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md |   47 +
 ...-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json |   26 +
 ...ID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md |  190 +++
 ...-C1680569-1170-4460-B42D-9B8D3D5125B6.json |   26 +
 ...ID-C1680569-1170-4460-B42D-9B8D3D5125B6.md |   61 +
 ...-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json |   26 +
 ...ID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md |   31 +
 ...-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json |   26 +
 ...ID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md |   27 +
 ...-C1E03C38-4DD6-43E9-8310-61A2FE452243.json |   26 +
 ...ID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md |  118 ++
 ...-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json |   26 +
 ...ID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md |   38 +
 ...-C20033B6-4C42-4BEC-84C0-D313859D9126.json |   26 +
 ...ID-C20033B6-4C42-4BEC-84C0-D313859D9126.md |  514 ++++++
 ...-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json |   26 +
 ...ID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md |    5 +
 ...-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json |   26 +
 ...ID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md |   45 +
 ...-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json |   26 +
 ...ID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md |  204 +++
 ...-C3B37EC3-FBB1-40BC-95B2-770849390851.json |   26 +
 ...ID-C3B37EC3-FBB1-40BC-95B2-770849390851.md |    5 +
 ...-C3FB4228-B601-4FD3-9802-8D40BEF90787.json |   26 +
 ...ID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md |   14 +
 ...-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json |   26 +
 ...ID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md |  152 ++
 ...-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json |   26 +
 ...ID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md |   27 +
 ...-C52A3557-8979-44A4-9FCE-480426F55A7F.json |   26 +
 ...ID-C52A3557-8979-44A4-9FCE-480426F55A7F.md |  499 ++++++
 ...-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json |   26 +
 ...ID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md |  495 ++++++
 ...-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json |   26 +
 ...ID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md |  301 ++++
 ...-C6AB6E89-39FB-498A-A333-5550A593DA7B.json |   26 +
 ...ID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md |   18 +
 ...-C742E2B5-1585-459D-B13A-139DEB0AC122.json |   26 +
 ...ID-C742E2B5-1585-459D-B13A-139DEB0AC122.md |   22 +
 ...-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json |   26 +
 ...ID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md |   18 +
 ...-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json |   26 +
 ...ID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md |   55 +
 ...-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json |   26 +
 ...ID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md |  102 ++
 ...-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json |   26 +
 ...ID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md |   55 +
 ...-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json |   26 +
 ...ID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md | 1018 ++++++++++++
 ...-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json |   26 +
 ...ID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md |    9 +
 ...-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json |   26 +
 ...ID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md |   13 +
 ...-CA96F723-CABE-4A23-AEAC-220BE12D2970.json |   26 +
 ...ID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md |    7 +
 ...-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json |   26 +
 ...ID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md |   51 +
 ...-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json |   26 +
 ...ID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md |   13 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |   26 +
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   12 +
 ...-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json |   26 +
 ...ID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md |  114 ++
 ...-CC1F0809-F068-41F6-853A-0033148C3436.json |   26 +
 ...ID-CC1F0809-F068-41F6-853A-0033148C3436.md |   20 +
 ...-CCC7880B-8316-4FDD-91D6-9680671E23D9.json |   26 +
 ...ID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md |  185 +++
 ...-CD1058AC-228F-424E-A2B0-45B93F4C582F.json |   26 +
 ...ID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md |   51 +
 ...-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json |   26 +
 ...ID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md |  358 +++++
 ...-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json |   26 +
 ...ID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md |   33 +
 ...-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json |   26 +
 ...ID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md |  204 +++
 ...-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json |   26 +
 ...ID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md |  113 ++
 ...-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json |   26 +
 ...ID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md |   11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |   26 +
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |   10 +
 ...-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json |   26 +
 ...ID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md |    6 +
 ...-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json |   26 +
 ...ID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md |   41 +
 ...-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json |   26 +
 ...ID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md |   25 +
 ...-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json |   26 +
 ...ID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md |   12 +
 ...-D3100235-F327-4C00-9AF8-F5C974D2F698.json |   26 +
 ...ID-D3100235-F327-4C00-9AF8-F5C974D2F698.md |   13 +
 ...-D3548220-4D77-4DBB-8313-CFAD68416264.json |   26 +
 ...ID-D3548220-4D77-4DBB-8313-CFAD68416264.md |   30 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |   26 +
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |   59 +
 ...-D47A61E0-1F97-4E09-A62C-C8B990640F56.json |   26 +
 ...ID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md |   28 +
 ...-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json |   26 +
 ...ID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md |   14 +
 ...-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json |   26 +
 ...ID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md |    5 +
 ...-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json |   26 +
 ...ID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md |   13 +
 ...-D63E4175-CA68-4648-B912-F20796292DD3.json |   26 +
 ...ID-D63E4175-CA68-4648-B912-F20796292DD3.md |   52 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |   26 +
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |    9 +
 ...-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json |   26 +
 ...ID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md |   86 ++
 ...-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json |   26 +
 ...ID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md |  230 +++
 ...-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json |   26 +
 ...ID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md |  143 ++
 ...-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json |   26 +
 ...ID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md |  150 ++
 ...-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json |   26 +
 ...ID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md |    7 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |   26 +
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   83 +
 ...-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json |   26 +
 ...ID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md |   28 +
 ...-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json |   26 +
 ...ID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md |   16 +
 ...-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json |   26 +
 ...ID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md |   53 +
 ...-DB2EE423-511B-432B-8425-82326DC29158.json |   26 +
 ...ID-DB2EE423-511B-432B-8425-82326DC29158.md |   24 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |   26 +
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |   23 +
 ...-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json |   26 +
 ...ID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md |   21 +
 ...-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json |   26 +
 ...ID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md |    7 +
 ...-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json |   26 +
 ...ID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md |  132 ++
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |   26 +
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |   13 +
 ...-DD626086-0E0C-460D-85BC-8E654BEEF70A.json |   26 +
 ...ID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md |   17 +
 ...-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json |   26 +
 ...ID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md |   15 +
 ...-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json |   26 +
 ...ID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md |    3 +
 ...-DE4B3C05-2C42-42E8-849A-B13E77080955.json |   26 +
 ...ID-DE4B3C05-2C42-42E8-849A-B13E77080955.md |   11 +
 ...-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json |   26 +
 ...ID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md |   75 +
 ...-DED3B0BE-A491-472F-B40B-A08F64835F17.json |   26 +
 ...ID-DED3B0BE-A491-472F-B40B-A08F64835F17.md |  150 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |   26 +
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |   68 +
 ...-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json |   26 +
 ...ID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md |   53 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |   26 +
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  142 ++
 ...-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json |   26 +
 ...ID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md |  159 ++
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |   26 +
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |   28 +
 ...-E012A526-E6C4-408D-A69C-AD7BC08B882C.json |   26 +
 ...ID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md |   63 +
 ...-E01FA212-4E9E-4403-9508-E4BB971643A3.json |   26 +
 ...ID-E01FA212-4E9E-4403-9508-E4BB971643A3.md |  203 +++
 ...-E02DD704-C987-41BB-AF3F-A23F35C097BD.json |   26 +
 ...ID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md |   27 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |   26 +
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |   65 +
 ...-E1159A9B-4A53-400A-A1E7-8604539EB39D.json |   26 +
 ...ID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md |   11 +
 ...-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json |   26 +
 ...ID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md |    7 +
 ...-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json |   26 +
 ...ID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md |   37 +
 ...-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json |   26 +
 ...ID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md |   92 ++
 ...-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json |   26 +
 ...ID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md |    7 +
 ...-E3911F3D-F635-42FA-B014-078FD60D3130.json |   26 +
 ...ID-E3911F3D-F635-42FA-B014-078FD60D3130.md |   23 +
 ...-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json |   26 +
 ...ID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md |   14 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |   26 +
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   49 +
 ...-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json |   26 +
 ...ID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md |  117 ++
 ...-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json |   26 +
 ...ID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md |   31 +
 ...-E55D4270-ED77-4161-8712-45824C891713.json |   26 +
 ...ID-E55D4270-ED77-4161-8712-45824C891713.md |   38 +
 ...-E5C429F5-9F57-481D-968A-64793E86EBCE.json |   26 +
 ...ID-E5C429F5-9F57-481D-968A-64793E86EBCE.md |   34 +
 ...-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json |   26 +
 ...ID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md |   15 +
 ...-E6C2AF29-A549-4B96-A778-039FC445D7F2.json |   26 +
 ...ID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md |    3 +
 ...-E748BC6D-7E45-4324-A174-9FB2012CBA27.json |   26 +
 ...ID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md |   13 +
 ...-E7DD5576-68E3-449D-8606-D2861BF53808.json |   26 +
 ...ID-E7DD5576-68E3-449D-8606-D2861BF53808.md |   12 +
 ...-E816369D-52FD-43B2-88F6-A5F748829203.json |   26 +
 ...ID-E816369D-52FD-43B2-88F6-A5F748829203.md |   10 +
 ...-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json |   26 +
 ...ID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md |   16 +
 ...-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json |   26 +
 ...ID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md |   48 +
 ...-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json |   26 +
 ...ID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md |   20 +
 ...-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json |   26 +
 ...ID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md |   18 +
 ...-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json |   26 +
 ...ID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md |   27 +
 ...-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json |   26 +
 ...ID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md |   11 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |   26 +
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |  191 +++
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |   26 +
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |    8 +
 ...-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json |   26 +
 ...ID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md |  496 ++++++
 ...-ED404402-F168-4635-ADEB-02609465196E.json |   26 +
 ...ID-ED404402-F168-4635-ADEB-02609465196E.md |   20 +
 ...-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json |   26 +
 ...ID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md |   19 +
 ...-EF20CD89-B756-4F84-BC6A-55B2488B5947.json |   26 +
 ...ID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md |   46 +
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |   26 +
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |   13 +
 ...-F003BCEE-0E64-412A-9045-295910E15A5A.json |   26 +
 ...ID-F003BCEE-0E64-412A-9045-295910E15A5A.md |  133 ++
 ...-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json |   26 +
 ...ID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md |    3 +
 ...-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json |   26 +
 ...ID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md |   53 +
 ...-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json |   26 +
 ...ID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md |    9 +
 ...-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json |   26 +
 ...ID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md |  328 ++++
 ...-F6459690-0DE9-48CE-95B2-C7BE033E8088.json |   26 +
 ...ID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md |   19 +
 ...-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json |   26 +
 ...ID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md |    4 +
 ...-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json |   26 +
 ...ID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md |   18 +
 ...-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json |   26 +
 ...ID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md |   31 +
 ...-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json |   26 +
 ...ID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md |  231 +++
 ...-F7C9EB98-701B-4C51-966C-3448AF3575AF.json |   26 +
 ...ID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md |   26 +
 ...-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json |   26 +
 ...ID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md |   80 +
 ...-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json |   26 +
 ...ID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md |  114 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |   26 +
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  189 +++
 ...-FBA4AD60-9130-49BD-B10F-074439138A4B.json |   26 +
 ...ID-FBA4AD60-9130-49BD-B10F-074439138A4B.md |   13 +
 ...-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json |   26 +
 ...ID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md |   14 +
 ...-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json |   26 +
 ...ID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md |   17 +
 ...-FE7CCD11-6021-491F-BC50-596DA68F9206.json |   26 +
 ...ID-FE7CCD11-6021-491F-BC50-596DA68F9206.md |   13 +
 ...-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json |   26 +
 ...ID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md |   56 +
 ...-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json |   26 +
 ...ID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md |   30 +
 ...-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json |   26 +
 ...ID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md |  111 ++
 ...-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json |   26 +
 ...ID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md |   25 +
 ...-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json |   26 +
 ...ID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md |   19 +
 ...-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json |   26 +
 ...ID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md |   18 +
 ...-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json |   26 +
 ...ID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md |   88 ++
 ...-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json |   26 +
 ...ID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md |   52 +
 ...-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json |   26 +
 ...ID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md |    9 +
 ...-030A6638-D9C6-492A-A021-8634B29738F7.json |   26 +
 ...ID-030A6638-D9C6-492A-A021-8634B29738F7.md |   63 +
 ...-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json |   26 +
 ...ID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md |   16 +
 ...-034C870E-F6DE-4D0B-950B-23A627D33C65.json |   26 +
 ...ID-034C870E-F6DE-4D0B-950B-23A627D33C65.md |   14 +
 ...-038058DD-CC8D-41F7-AF14-DB01B16993C4.json |   26 +
 ...ID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md |   41 +
 ...-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json |   26 +
 ...ID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md |   60 +
 ...-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json |   26 +
 ...ID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md |    7 +
 ...-0441F3DD-FF73-49C0-8900-718B95266989.json |   26 +
 ...ID-0441F3DD-FF73-49C0-8900-718B95266989.md |  262 ++++
 ...-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json |   26 +
 ...ID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md |  115 ++
 ...-06D232B4-F473-44C5-AD24-AECD128273E5.json |   26 +
 ...ID-06D232B4-F473-44C5-AD24-AECD128273E5.md |  136 ++
 ...-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json |   26 +
 ...ID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md |   14 +
 ...-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json |   26 +
 ...ID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md |   32 +
 ...-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json |   26 +
 ...ID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md |   71 +
 ...-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json |   26 +
 ...ID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md |   10 +
 ...-092B4E74-3662-4E21-9DA0-67958362DBE4.json |   26 +
 ...ID-092B4E74-3662-4E21-9DA0-67958362DBE4.md |   24 +
 ...-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json |   26 +
 ...ID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md |   22 +
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |   26 +
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |    8 +
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |   26 +
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   34 +
 ...-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json |   26 +
 ...ID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md |   50 +
 ...-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json |   26 +
 ...ID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md |   12 +
 ...-0BBD18FA-91D0-406A-B004-3F068114DE70.json |   26 +
 ...ID-0BBD18FA-91D0-406A-B004-3F068114DE70.md |   61 +
 ...-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json |   26 +
 ...ID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md |  113 ++
 ...-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json |   26 +
 ...ID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md |   22 +
 ...-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json |   26 +
 ...ID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md |   21 +
 ...-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json |   26 +
 ...ID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md |   54 +
 ...-101B0634-4367-4B11-ACA0-923AC1CA635E.json |   26 +
 ...ID-101B0634-4367-4B11-ACA0-923AC1CA635E.md |   19 +
 ...-10BE13E9-1014-4162-97E7-A1056FED89B3.json |   26 +
 ...ID-10BE13E9-1014-4162-97E7-A1056FED89B3.md |   24 +
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |   26 +
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |    7 +
 ...-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json |   26 +
 ...ID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md |   12 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |   26 +
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |   14 +
 ...-127B939B-0C18-40CC-AC49-8DD0D58BE444.json |   26 +
 ...ID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md |   35 +
 ...-133E4178-5B4C-4BFF-8213-2662774F0B37.json |   26 +
 ...ID-133E4178-5B4C-4BFF-8213-2662774F0B37.md |   20 +
 ...-13940199-9CEA-485B-87AF-AB47536CD6AE.json |   26 +
 ...ID-13940199-9CEA-485B-87AF-AB47536CD6AE.md |  306 ++++
 ...-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json |   26 +
 ...ID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md |   22 +
 ...-13B77F8D-BA84-4649-A4C1-D137357E7A78.json |   26 +
 ...ID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md |  124 ++
 ...-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json |   26 +
 ...ID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md |   31 +
 ...-151B596B-EE69-4D4B-8C80-964A90D3523C.json |   26 +
 ...ID-151B596B-EE69-4D4B-8C80-964A90D3523C.md |   28 +
 ...-151C50C5-5883-4137-A9B0-EAF5F8087117.json |   26 +
 ...ID-151C50C5-5883-4137-A9B0-EAF5F8087117.md |   40 +
 ...-1621A716-2765-4655-B4D0-C95B8416F4D3.json |   26 +
 ...ID-1621A716-2765-4655-B4D0-C95B8416F4D3.md |   22 +
 ...-173469C2-D5C6-47F6-8A01-41C3D73B679B.json |   26 +
 ...ID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md |   45 +
 ...-1741A126-636E-4A96-812C-48A8B7A25E88.json |   26 +
 ...ID-1741A126-636E-4A96-812C-48A8B7A25E88.md |   23 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |   26 +
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   13 +
 ...-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json |   26 +
 ...ID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md |  450 ++++++
 ...-180B8370-AEF2-45C1-9E72-99FF796CB222.json |   26 +
 ...ID-180B8370-AEF2-45C1-9E72-99FF796CB222.md |   39 +
 ...-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json |   26 +
 ...ID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md |   81 +
 ...-1AA91E38-BE43-4571-ADEB-714F77E9E728.json |   26 +
 ...ID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md |   62 +
 ...-1AC5F825-20D5-4B28-936A-2DD024250026.json |   26 +
 ...ID-1AC5F825-20D5-4B28-936A-2DD024250026.md |    6 +
 ...-1B184F05-C570-446E-8C3A-FC24792DE213.json |   26 +
 ...ID-1B184F05-C570-446E-8C3A-FC24792DE213.md |   28 +
 ...-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json |   26 +
 ...ID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md |  176 +++
 ...-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json |   26 +
 ...ID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md |   48 +
 ...-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json |   26 +
 ...ID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md |  124 ++
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |   26 +
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |    9 +
 ...-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json |   26 +
 ...ID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md |   15 +
 ...-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json |   26 +
 ...ID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md |    3 +
 ...-1E710344-0932-4A51-B605-18AEF716E46F.json |   26 +
 ...ID-1E710344-0932-4A51-B605-18AEF716E46F.md |  115 ++
 ...-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json |   26 +
 ...ID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md |  161 ++
 ...-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json |   26 +
 ...ID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md |  140 ++
 ...-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json |   26 +
 ...ID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md |   63 +
 ...-1F30FE4D-FAD1-444B-9570-E20C339F257C.json |   26 +
 ...ID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md |  227 +++
 ...-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json |   26 +
 ...ID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md |    9 +
 ...-1FE536B8-0BE2-4851-8801-174C49D984F3.json |   26 +
 ...ID-1FE536B8-0BE2-4851-8801-174C49D984F3.md |   10 +
 ...-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json |   26 +
 ...ID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md |   12 +
 ...-20D6853D-60F1-45A8-90F5-47E242D57DB4.json |   26 +
 ...ID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md |   91 ++
 ...-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json |   26 +
 ...ID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md |   12 +
 ...-21F2F208-7360-4468-B1FF-524CA30CB993.json |   26 +
 ...ID-21F2F208-7360-4468-B1FF-524CA30CB993.md |   21 +
 ...-2277183A-E315-4439-A885-C111A77C7154.json |   26 +
 ...ID-2277183A-E315-4439-A885-C111A77C7154.md |   80 +
 ...-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json |   26 +
 ...ID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md |  240 +++
 ...-25A367DD-64FA-417A-B88B-B1D95C3E258B.json |   26 +
 ...ID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md |  128 ++
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |   26 +
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  199 +++
 ...-269D2944-5080-4897-86F5-AC949F4B83F1.json |   26 +
 ...ID-269D2944-5080-4897-86F5-AC949F4B83F1.md |   34 +
 ...-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json |   26 +
 ...ID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md |    8 +
 ...-27706317-FA6C-49E6-8D44-FAE2E35217F8.json |   26 +
 ...ID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md |   42 +
 ...-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json |   26 +
 ...ID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md |  130 ++
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |   26 +
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |    9 +
 ...-29661D5A-2426-4114-B839-1242C7A7D6A8.json |   26 +
 ...ID-29661D5A-2426-4114-B839-1242C7A7D6A8.md |   50 +
 ...-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json |   26 +
 ...ID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md |   36 +
 ...-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json |   26 +
 ...ID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md |   51 +
 ...-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json |   26 +
 ...ID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md |   28 +
 ...-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json |   26 +
 ...ID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md |   20 +
 ...-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json |   26 +
 ...ID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md |    8 +
 ...-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json |   26 +
 ...ID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md |   52 +
 ...-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json |   26 +
 ...ID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md |   10 +
 ...-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json |   26 +
 ...ID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md |  220 +++
 ...-2D22E37B-3698-46F3-88BB-A36D96C849EF.json |   26 +
 ...ID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md |  207 +++
 ...-2D8A0A86-2231-4239-AB44-5475B4AE0827.json |   26 +
 ...ID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md |  489 ++++++
 ...-2DE45951-E56A-4651-AB77-F8C894E28788.json |   26 +
 ...ID-2DE45951-E56A-4651-AB77-F8C894E28788.md |   32 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |   26 +
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   39 +
 ...-2DFC3858-043A-4053-AB10-F4534C7D7240.json |   26 +
 ...ID-2DFC3858-043A-4053-AB10-F4534C7D7240.md |   56 +
 ...-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json |   26 +
 ...ID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md |   26 +
 ...-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json |   26 +
 ...ID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md |  156 ++
 ...-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json |   26 +
 ...ID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md |  104 ++
 ...-2F776F04-B8E7-428D-823B-AB121DFE48AB.json |   26 +
 ...ID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md |   15 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |   26 +
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |  462 ++++++
 ...-3148715A-05C1-4793-9B2B-6DB66D7C101D.json |   26 +
 ...ID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md |   43 +
 ...-3159C5BA-04D5-4035-9842-86197618F7D2.json |   26 +
 ...ID-3159C5BA-04D5-4035-9842-86197618F7D2.md |  363 +++++
 ...-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json |   26 +
 ...ID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md |    8 +
 ...-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json |   26 +
 ...ID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md |  188 +++
 ...-32D8CBBE-0375-48BC-8038-E6618F94BE83.json |   26 +
 ...ID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md |  561 +++++++
 ...-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json |   26 +
 ...ID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md |  102 ++
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |   26 +
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |    6 +
 ...-3391053D-4F2A-49A4-8823-E63F708C55C4.json |   26 +
 ...ID-3391053D-4F2A-49A4-8823-E63F708C55C4.md |   21 +
 ...-33E060CF-9C8E-4AA3-971B-7C5E06954157.json |   26 +
 ...ID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md |   51 +
 ...-34DE6BFF-C4CD-4C78-A963-62798D548E61.json |   26 +
 ...ID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md |    7 +
 ...-3535B779-7CDA-4288-A03A-02E0F9552B7B.json |   26 +
 ...ID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md |   55 +
 ...-3559161C-E53A-419A-B7E5-663F1440004F.json |   26 +
 ...ID-3559161C-E53A-419A-B7E5-663F1440004F.md |    5 +
 ...-35F886E0-C4F0-42F5-AF68-AA1481040D76.json |   26 +
 ...ID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md |   92 ++
 ...-367B7FE3-99E0-438C-87C0-43F9A179B552.json |   26 +
 ...ID-367B7FE3-99E0-438C-87C0-43F9A179B552.md |   78 +
 ...-36BA3E37-26D3-488F-85C2-942C45119F02.json |   26 +
 ...ID-36BA3E37-26D3-488F-85C2-942C45119F02.md |  297 ++++
 ...-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json |   26 +
 ...ID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md |   13 +
 ...-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json |   26 +
 ...ID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md |   11 +
 ...-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json |   26 +
 ...ID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md |    5 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |   26 +
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |  112 ++
 ...-382BFCD5-DE8D-4C54-B3D6-704970132153.json |   26 +
 ...ID-382BFCD5-DE8D-4C54-B3D6-704970132153.md |  207 +++
 ...-38B4C746-179D-43CA-9205-9DC63ACC87EF.json |   26 +
 ...ID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md |  246 +++
 ...-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json |   26 +
 ...ID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md |   12 +
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |   26 +
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |   12 +
 ...-39D4284E-C733-48AD-94DE-CD929AEB0431.json |   26 +
 ...ID-39D4284E-C733-48AD-94DE-CD929AEB0431.md |  128 ++
 ...-3A38516A-B491-407B-AF69-9DF38E4266DF.json |   26 +
 ...ID-3A38516A-B491-407B-AF69-9DF38E4266DF.md |   29 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |   26 +
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |   25 +
 ...-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json |   26 +
 ...ID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md |   87 ++
 ...-3B6AC391-B993-47A2-8264-7389873C8D6D.json |   26 +
 ...ID-3B6AC391-B993-47A2-8264-7389873C8D6D.md |   16 +
 ...-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json |   26 +
 ...ID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md |   41 +
 ...-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json |   26 +
 ...ID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md |  325 ++++
 ...-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json |   26 +
 ...ID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md |   11 +
 ...-3CA69B8E-D437-40EC-9755-668930BA21F4.json |   26 +
 ...ID-3CA69B8E-D437-40EC-9755-668930BA21F4.md |  281 ++++
 ...-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json |   26 +
 ...ID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md |   33 +
 ...-3CEB493A-1086-4AE2-8220-93B372329509.json |   26 +
 ...ID-3CEB493A-1086-4AE2-8220-93B372329509.md |    5 +
 ...-3D3058F0-C2FE-4995-8D62-55A069D50709.json |   26 +
 ...ID-3D3058F0-C2FE-4995-8D62-55A069D50709.md |  139 ++
 ...-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json |   26 +
 ...ID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md |   11 +
 ...-3E6007AB-2F77-4783-8610-592F1BB9125B.json |   26 +
 ...ID-3E6007AB-2F77-4783-8610-592F1BB9125B.md |  163 ++
 ...-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json |   26 +
 ...ID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md | 1373 +++++++++++++++++
 ...-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json |   26 +
 ...ID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md |   92 ++
 ...-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json |   26 +
 ...ID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md |   86 ++
 ...-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json |   26 +
 ...ID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md |   40 +
 ...-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json |   26 +
 ...ID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md |  157 ++
 ...-421A3218-7033-4066-AF8E-AA2D46D4385C.json |   26 +
 ...ID-421A3218-7033-4066-AF8E-AA2D46D4385C.md |   26 +
 ...-44272A47-8855-48A0-B475-E940CE97DD7A.json |   26 +
 ...ID-44272A47-8855-48A0-B475-E940CE97DD7A.md |   16 +
 ...-443DA867-07E9-416F-ABFB-2C4BF2312D53.json |   26 +
 ...ID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md |  191 +++
 ...-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json |   26 +
 ...ID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md |   22 +
 ...-44644079-BC85-448F-B542-23E18E9D5602.json |   26 +
 ...ID-44644079-BC85-448F-B542-23E18E9D5602.md |   72 +
 ...-44A7BA66-FC27-40C3-8A12-2704D2043B53.json |   26 +
 ...ID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md |   69 +
 ...-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json |   26 +
 ...ID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md |   30 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |   26 +
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |  316 ++++
 ...-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json |   26 +
 ...ID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md |  130 ++
 ...-45DBACB2-9ED7-4538-9BF9-2D121178F539.json |   26 +
 ...ID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md |   47 +
 ...-46A53E20-D2A8-4233-8829-7865C7A434B7.json |   26 +
 ...ID-46A53E20-D2A8-4233-8829-7865C7A434B7.md |   42 +
 ...-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json |   26 +
 ...ID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md |   11 +
 ...-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json |   26 +
 ...ID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md |   18 +
 ...-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json |   26 +
 ...ID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md |  383 +++++
 ...-48ED6B2F-2E0B-491F-A497-139DD9B91284.json |   26 +
 ...ID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md |   17 +
 ...-49022137-A78E-4863-B1CF-D455EDD1A7D2.json |   26 +
 ...ID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md |    3 +
 ...-49067498-304A-4C38-B9C1-D8CF296DD3FA.json |   26 +
 ...ID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md |   28 +
 ...-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json |   26 +
 ...ID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md |   53 +
 ...-4983900F-0A3F-4F61-BB06-8270BE27C886.json |   26 +
 ...ID-4983900F-0A3F-4F61-BB06-8270BE27C886.md |   33 +
 ...-49F13E32-7912-4F28-8C78-5DF3AB06E690.json |   26 +
 ...ID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md |    9 +
 ...-4A13998A-C40E-4505-B1A1-16B21926D177.json |   26 +
 ...ID-4A13998A-C40E-4505-B1A1-16B21926D177.md |   15 +
 ...-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json |   26 +
 ...ID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md |   39 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |   26 +
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |    3 +
 ...-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json |   26 +
 ...ID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md |   15 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |   26 +
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |   13 +
 ...-4F4F8735-4673-4408-BDA3-C295F2A88174.json |   26 +
 ...ID-4F4F8735-4673-4408-BDA3-C295F2A88174.md |    7 +
 ...-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json |   26 +
 ...ID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md |    7 +
 ...-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json |   26 +
 ...ID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md |  257 +++
 ...-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json |   26 +
 ...ID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md |  153 ++
 ...-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json |   26 +
 ...ID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md |  301 ++++
 ...-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json |   26 +
 ...ID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md |   55 +
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |   26 +
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |    8 +
 ...-5473844F-B09C-4F23-AC2F-A305A384136B.json |   26 +
 ...ID-5473844F-B09C-4F23-AC2F-A305A384136B.md |   61 +
 ...-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json |   26 +
 ...ID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md |   41 +
 ...-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json |   26 +
 ...ID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md |   11 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |   26 +
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |    9 +
 ...-563347AC-C86B-4AC7-BF58-B80A3201662F.json |   26 +
 ...ID-563347AC-C86B-4AC7-BF58-B80A3201662F.md |   13 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |   26 +
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   27 +
 ...-56F6E993-6289-4BC0-AFD6-938516823FC8.json |   26 +
 ...ID-56F6E993-6289-4BC0-AFD6-938516823FC8.md |   15 +
 ...-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json |   26 +
 ...ID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md |  184 +++
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |   26 +
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   34 +
 ...-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json |   26 +
 ...ID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md |   31 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |   26 +
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |   25 +
 ...-589A7663-2242-4FBE-9214-FE0F91A29972.json |   26 +
 ...ID-589A7663-2242-4FBE-9214-FE0F91A29972.md |   49 +
 ...-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json |   26 +
 ...ID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md |    9 +
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |   26 +
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   13 +
 ...-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json |   26 +
 ...ID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md |  110 ++
 ...-5AE10D03-5E33-4437-8477-059B0390B662.json |   26 +
 ...ID-5AE10D03-5E33-4437-8477-059B0390B662.md |   28 +
 ...-5B7DB753-B382-4E98-BF3A-599C15334A69.json |   26 +
 ...ID-5B7DB753-B382-4E98-BF3A-599C15334A69.md |    8 +
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |   26 +
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  119 ++
 ...-5CBD20D3-D323-4F6E-A543-E19708439C5D.json |   26 +
 ...ID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md |   15 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |   26 +
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   26 +
 ...-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json |   26 +
 ...ID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md |   80 +
 ...-5D659229-2AFA-4A63-9194-D128E673AA02.json |   26 +
 ...ID-5D659229-2AFA-4A63-9194-D128E673AA02.md |   22 +
 ...-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json |   26 +
 ...ID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md |  363 +++++
 ...-5F72EBA5-E780-4511-8EA0-4ABA11628663.json |   26 +
 ...ID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md |    4 +
 ...-607895C8-5308-4A68-9219-1EA342DB9C6C.json |   26 +
 ...ID-607895C8-5308-4A68-9219-1EA342DB9C6C.md |    9 +
 ...-60BD671A-C620-49C7-81EB-56C5197E61C2.json |   26 +
 ...ID-60BD671A-C620-49C7-81EB-56C5197E61C2.md |   45 +
 ...-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json |   26 +
 ...ID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md |   31 +
 ...-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json |   26 +
 ...ID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md |   55 +
 ...-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json |   26 +
 ...ID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md |   75 +
 ...-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json |   26 +
 ...ID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md |   26 +
 ...-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json |   26 +
 ...ID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md |   64 +
 ...-633B871A-14AC-42B5-9BDA-8F907433F700.json |   26 +
 ...ID-633B871A-14AC-42B5-9BDA-8F907433F700.md |   34 +
 ...-63B50C5A-C3AD-4543-8A89-58110DDD5064.json |   26 +
 ...ID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md |  130 ++
 ...-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json |   26 +
 ...ID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md |   30 +
 ...-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json |   26 +
 ...ID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md |   16 +
 ...-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json |   26 +
 ...ID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md |   37 +
 ...-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json |   26 +
 ...ID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md |   34 +
 ...-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json |   26 +
 ...ID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md |   85 +
 ...-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json |   26 +
 ...ID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md |   22 +
 ...-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json |   26 +
 ...ID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md |  119 ++
 ...-663434D4-E8EB-4468-992C-107B9FD4AC30.json |   26 +
 ...ID-663434D4-E8EB-4468-992C-107B9FD4AC30.md |    7 +
 ...-66740846-A143-48D1-80FF-7314D86BE61A.json |   26 +
 ...ID-66740846-A143-48D1-80FF-7314D86BE61A.md |   56 +
 ...-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json |   26 +
 ...ID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md |   34 +
 ...-6779EFD7-BD52-4678-AC19-30AE09F26217.json |   26 +
 ...ID-6779EFD7-BD52-4678-AC19-30AE09F26217.md |   13 +
 ...-68E5CB99-152C-463C-9E41-5B2C67C659CD.json |   26 +
 ...ID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md |   14 +
 ...-690DD9D4-9114-4EE1-97F1-254D7B67B733.json |   26 +
 ...ID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md |    6 +
 ...-6A02D571-9949-4EA4-B43C-C2CED90210EF.json |   26 +
 ...ID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md |   20 +
 ...-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json |   26 +
 ...ID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md |   60 +
 ...-6B3D18B4-5885-4318-848F-DE294F57057B.json |   26 +
 ...ID-6B3D18B4-5885-4318-848F-DE294F57057B.md |  222 +++
 ...-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json |   26 +
 ...ID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md |   21 +
 ...-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json |   26 +
 ...ID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md |   85 +
 ...-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json |   26 +
 ...ID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md |   13 +
 ...-6C22C389-3D06-4DF0-B997-1CA161175182.json |   26 +
 ...ID-6C22C389-3D06-4DF0-B997-1CA161175182.md |  147 ++
 ...-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json |   26 +
 ...ID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md |   32 +
 ...-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json |   26 +
 ...ID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md |   56 +
 ...-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json |   26 +
 ...ID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md |   17 +
 ...-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json |   26 +
 ...ID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md |   16 +
 ...-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json |   26 +
 ...ID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md |  468 ++++++
 ...-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json |   26 +
 ...ID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md |   28 +
 ...-6FFCD815-6AC5-46F9-AB71-F293570366A8.json |   26 +
 ...ID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md |   87 ++
 ...-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json |   26 +
 ...ID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md |   71 +
 ...-7056841F-C280-4C83-8065-017EF45643F9.json |   26 +
 ...ID-7056841F-C280-4C83-8065-017EF45643F9.md |   75 +
 ...-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json |   26 +
 ...ID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md |   20 +
 ...-719570B7-BE8A-49B2-87D7-336A9703ED88.json |   26 +
 ...ID-719570B7-BE8A-49B2-87D7-336A9703ED88.md |   32 +
 ...-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json |   26 +
 ...ID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md |   12 +
 ...-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json |   26 +
 ...ID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md |  101 ++
 ...-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json |   26 +
 ...ID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md |  441 ++++++
 ...-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json |   26 +
 ...ID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md |   64 +
 ...-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json |   26 +
 ...ID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md |    5 +
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |   26 +
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |   13 +
 ...-75D89535-68AE-4507-A961-26CE8914F074.json |   26 +
 ...ID-75D89535-68AE-4507-A961-26CE8914F074.md |   96 ++
 ...-768B1CD6-73F8-4CBC-9675-E03000B36147.json |   26 +
 ...ID-768B1CD6-73F8-4CBC-9675-E03000B36147.md |    9 +
 ...-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json |   26 +
 ...ID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md |  411 +++++
 ...-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json |   26 +
 ...ID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md |   14 +
 ...-77287C89-E688-49C4-869F-652DE15478FB.json |   26 +
 ...ID-77287C89-E688-49C4-869F-652DE15478FB.md |   69 +
 ...-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json |   26 +
 ...ID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md |   32 +
 ...-786D5554-1448-4001-A39C-647F22CA9278.json |   26 +
 ...ID-786D5554-1448-4001-A39C-647F22CA9278.md |   31 +
 ...-78DC62BA-524C-456D-827F-465C10A1AA6F.json |   26 +
 ...ID-78DC62BA-524C-456D-827F-465C10A1AA6F.md |   43 +
 ...-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json |   26 +
 ...ID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md |    9 +
 ...-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json |   26 +
 ...ID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md |  100 ++
 ...-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json |   26 +
 ...ID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md |  106 ++
 ...-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json |   26 +
 ...ID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md |  439 ++++++
 ...-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json |   26 +
 ...ID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md |    8 +
 ...-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json |   26 +
 ...ID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md |   80 +
 ...-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json |   26 +
 ...ID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md |    9 +
 ...-7BD87211-4E8A-480C-A7B6-E502808743EC.json |   26 +
 ...ID-7BD87211-4E8A-480C-A7B6-E502808743EC.md |   21 +
 ...-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json |   26 +
 ...ID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md |   29 +
 ...-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json |   26 +
 ...ID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md |  888 +++++++++++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |   26 +
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   12 +
 ...-7CA53A6D-026B-4977-8247-349750CE4EB9.json |   26 +
 ...ID-7CA53A6D-026B-4977-8247-349750CE4EB9.md |   22 +
 ...-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json |   26 +
 ...ID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md |    3 +
 ...-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json |   26 +
 ...ID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md |   22 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |   26 +
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |  177 +++
 ...-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json |   26 +
 ...ID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md |   25 +
 ...-80911C58-F6AB-4001-B50E-EC0F43773A5E.json |   26 +
 ...ID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md |   15 +
 ...-8143252C-EC38-43B2-B2E0-443A60C01768.json |   26 +
 ...ID-8143252C-EC38-43B2-B2E0-443A60C01768.md |   63 +
 ...-8168FFDF-77DD-42E0-B747-95099C7852AB.json |   26 +
 ...ID-8168FFDF-77DD-42E0-B747-95099C7852AB.md |   17 +
 ...-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json |   26 +
 ...ID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md |  264 ++++
 ...-826F09D8-C40B-483D-9CB5-CE504BD18810.json |   26 +
 ...ID-826F09D8-C40B-483D-9CB5-CE504BD18810.md |   74 +
 ...-82C53DF1-4293-41E2-A90A-740C1814DD12.json |   26 +
 ...ID-82C53DF1-4293-41E2-A90A-740C1814DD12.md |   61 +
 ...-84B6C16D-5601-4CFB-9C53-47AE75271884.json |   26 +
 ...ID-84B6C16D-5601-4CFB-9C53-47AE75271884.md |  161 ++
 ...-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json |   26 +
 ...ID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md |   51 +
 ...-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json |   26 +
 ...ID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md |    3 +
 ...-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json |   26 +
 ...ID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md |    7 +
 ...-87CB98DB-3915-4176-822C-E86A5AA54C4D.json |   26 +
 ...ID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md |  322 ++++
 ...-8808CDAD-319E-4259-99D8-4D43440E63FE.json |   26 +
 ...ID-8808CDAD-319E-4259-99D8-4D43440E63FE.md |    9 +
 ...-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json |   26 +
 ...ID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md |   23 +
 ...-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json |   26 +
 ...ID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md |   20 +
 ...-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json |   26 +
 ...ID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md |   11 +
 ...-89F63373-6CC7-4498-9A70-75BB1FD6D779.json |   26 +
 ...ID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md |    6 +
 ...-89FD5558-DFD3-459B-A56D-BD998574F805.json |   26 +
 ...ID-89FD5558-DFD3-459B-A56D-BD998574F805.md |   14 +
 ...-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json |   26 +
 ...ID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md |   11 +
 ...-8A557829-64DF-4A0A-84FC-FC2C8755B391.json |   26 +
 ...ID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md |  172 +++
 ...-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json |   26 +
 ...ID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md |  191 +++
 ...-8AC08484-473F-41E8-B106-A90BC96B03C4.json |   26 +
 ...ID-8AC08484-473F-41E8-B106-A90BC96B03C4.md |   31 +
 ...-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json |   26 +
 ...ID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md |   39 +
 ...-8C608C16-055C-4708-BA01-87FACE15EF6D.json |   26 +
 ...ID-8C608C16-055C-4708-BA01-87FACE15EF6D.md |   86 ++
 ...-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json |   26 +
 ...ID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md |   30 +
 ...-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json |   26 +
 ...ID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md |    9 +
 ...-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json |   26 +
 ...ID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md |  176 +++
 ...-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json |   26 +
 ...ID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md |  212 +++
 ...-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json |   26 +
 ...ID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md |   80 +
 ...-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json |   26 +
 ...ID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md |   13 +
 ...-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json |   26 +
 ...ID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md |   20 +
 ...-9132296F-B580-4107-8041-9E30C7EC4291.json |   26 +
 ...ID-9132296F-B580-4107-8041-9E30C7EC4291.md |    8 +
 ...-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json |   26 +
 ...ID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md |   35 +
 ...-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json |   26 +
 ...ID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md |   17 +
 ...-9372294C-3A13-490D-BF63-BA01AB008C43.json |   26 +
 ...ID-9372294C-3A13-490D-BF63-BA01AB008C43.md |   11 +
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |   26 +
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  116 ++
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |   26 +
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |   13 +
 ...-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json |   26 +
 ...ID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md |    8 +
 ...-96732ACE-6F43-453A-8F9B-FD0F1C717362.json |   26 +
 ...ID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md |   33 +
 ...-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json |   26 +
 ...ID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md |  268 ++++
 ...-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json |   26 +
 ...ID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md |   64 +
 ...-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json |   26 +
 ...ID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md |  135 ++
 ...-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json |   26 +
 ...ID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md |    3 +
 ...-98351F93-76B4-480B-91F1-58E3E3492651.json |   26 +
 ...ID-98351F93-76B4-480B-91F1-58E3E3492651.md |  152 ++
 ...-9B75C475-9243-4444-BF22-C43480298274.json |   26 +
 ...ID-9B75C475-9243-4444-BF22-C43480298274.md |   15 +
 ...-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json |   26 +
 ...ID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md |   17 +
 ...-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json |   26 +
 ...ID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md |    9 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |   26 +
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   38 +
 ...-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json |   26 +
 ...ID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md |  185 +++
 ...-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json |   26 +
 ...ID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md |   10 +
 ...-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json |   26 +
 ...ID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md |   33 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |   26 +
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |  142 ++
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |   26 +
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |  116 ++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |   26 +
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   53 +
 ...-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json |   26 +
 ...ID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md |   10 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |   26 +
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |   24 +
 ...-9ECF72A1-9565-4202-A087-82313C2F8D58.json |   26 +
 ...ID-9ECF72A1-9565-4202-A087-82313C2F8D58.md |   58 +
 ...-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json |   26 +
 ...ID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md |   14 +
 ...-9F022B96-52CA-499B-978C-2CB55DCCAF48.json |   26 +
 ...ID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md |   80 +
 ...-9F78ED42-26BC-405F-88BC-3B14279A3306.json |   26 +
 ...ID-9F78ED42-26BC-405F-88BC-3B14279A3306.md |   32 +
 ...-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json |   26 +
 ...ID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md |   69 +
 ...-A0DC9F48-028D-4283-8572-FDD0A432E125.json |   26 +
 ...ID-A0DC9F48-028D-4283-8572-FDD0A432E125.md |   27 +
 ...-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json |   26 +
 ...ID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md |  264 ++++
 ...-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json |   26 +
 ...ID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md |   94 ++
 ...-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json |   26 +
 ...ID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md |   15 +
 ...-A2766933-3113-44EF-8458-88636F4301B3.json |   26 +
 ...ID-A2766933-3113-44EF-8458-88636F4301B3.md |    3 +
 ...-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json |   26 +
 ...ID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md |  146 ++
 ...-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json |   26 +
 ...ID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md |   38 +
 ...-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json |   26 +
 ...ID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md |   19 +
 ...-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json |   21 +
 ...ID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md |   27 +
 ...-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json |   26 +
 ...ID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md |   13 +
 ...-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json |   26 +
 ...ID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md |   21 +
 ...-A50734F6-41F7-4350-B07E-92C559E94119.json |   26 +
 ...ID-A50734F6-41F7-4350-B07E-92C559E94119.md |   30 +
 ...-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json |   26 +
 ...ID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md |   19 +
 ...-A586E426-9C40-4FD0-B749-7E962F9F04C4.json |   26 +
 ...ID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md |    9 +
 ...-A75681BD-B103-4441-AAD7-E1F848FFE56E.json |   26 +
 ...ID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md |    5 +
 ...-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json |   26 +
 ...ID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md |   97 ++
 ...-AB0E1772-B646-49E2-8318-B2495341839D.json |   26 +
 ...ID-AB0E1772-B646-49E2-8318-B2495341839D.md |   11 +
 ...-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json |   26 +
 ...ID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md |   95 ++
 ...-AB883016-0848-46D7-8BB0-37DF09076725.json |   26 +
 ...ID-AB883016-0848-46D7-8BB0-37DF09076725.md |   15 +
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |   26 +
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   41 +
 ...-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json |   26 +
 ...ID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md |   57 +
 ...-AB95E8ED-82A1-493E-82D0-613D80FB602E.json |   26 +
 ...ID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md |   31 +
 ...-ABC2295F-BA5B-49C6-BF73-263A724F948F.json |   26 +
 ...ID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md |  959 ++++++++++++
 ...-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json |   26 +
 ...ID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md |   34 +
 ...-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json |   26 +
 ...ID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md |   36 +
 ...-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json |   26 +
 ...ID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md |    7 +
 ...-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json |   26 +
 ...ID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md |   11 +
 ...-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json |   26 +
 ...ID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md |   14 +
 ...-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json |   26 +
 ...ID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md |   12 +
 ...-ADDC3274-0758-43B9-BF31-6EA3EB319288.json |   26 +
 ...ID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md |   32 +
 ...-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json |   26 +
 ...ID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md |    8 +
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |   26 +
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   19 +
 ...-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json |   26 +
 ...ID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md |   57 +
 ...-AFA85086-2874-4303-8999-E919DF886C44.json |   26 +
 ...ID-AFA85086-2874-4303-8999-E919DF886C44.md |   31 +
 ...-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json |   26 +
 ...ID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md |  300 ++++
 ...-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json |   26 +
 ...ID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md |   55 +
 ...-B2113088-6A1D-4A43-A781-BD280C35FA69.json |   26 +
 ...ID-B2113088-6A1D-4A43-A781-BD280C35FA69.md |   18 +
 ...-B299B747-2692-4406-9FCD-760C2EFE1E65.json |   26 +
 ...ID-B299B747-2692-4406-9FCD-760C2EFE1E65.md |   15 +
 ...-B379FDF9-2963-4336-AFC1-14372793FA70.json |   26 +
 ...ID-B379FDF9-2963-4336-AFC1-14372793FA70.md |   21 +
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |   26 +
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |  183 +++
 ...-B47A4967-DCA3-45C4-B983-83CEB43711DC.json |   26 +
 ...ID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md |  295 ++++
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |   26 +
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |    3 +
 ...-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json |   26 +
 ...ID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md |   16 +
 ...-B637812E-A51A-4AD5-B6F1-5E5822709711.json |   26 +
 ...ID-B637812E-A51A-4AD5-B6F1-5E5822709711.md |   23 +
 ...-B67FF274-342F-4B96-B5F9-0B8222C662DC.json |   26 +
 ...ID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md |    3 +
 ...-B6D4283B-948C-4722-8C96-21CDB727D0EE.json |   26 +
 ...ID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md |   90 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |   26 +
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |    6 +
 ...-B73068EC-E619-4EA2-B84B-D4941E1D1779.json |   26 +
 ...ID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md |  314 ++++
 ...-B7496F21-B633-436F-850B-507E482F96F2.json |   26 +
 ...ID-B7496F21-B633-436F-850B-507E482F96F2.md |   30 +
 ...-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json |   26 +
 ...ID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md |   38 +
 ...-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json |   26 +
 ...ID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md |   11 +
 ...-B7E3F043-2330-4392-9803-B649558F488B.json |   26 +
 ...ID-B7E3F043-2330-4392-9803-B649558F488B.md |   10 +
 ...-B86C6485-C80C-480F-87B4-4352963D74A5.json |   26 +
 ...ID-B86C6485-C80C-480F-87B4-4352963D74A5.md |   93 ++
 ...-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json |   26 +
 ...ID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md |   78 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |   26 +
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   40 +
 ...-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json |   26 +
 ...ID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md |   39 +
 ...-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json |   26 +
 ...ID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md |   29 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |   26 +
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   60 +
 ...-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json |   26 +
 ...ID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md |   47 +
 ...-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json |   26 +
 ...ID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md |  182 +++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |   26 +
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   15 +
 ...-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json |   26 +
 ...ID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md |  179 +++
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |   26 +
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |   52 +
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |   26 +
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |   28 +
 ...-BD4F0587-C0E9-4120-9D74-B54015579A60.json |   26 +
 ...ID-BD4F0587-C0E9-4120-9D74-B54015579A60.md |    6 +
 ...-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json |   26 +
 ...ID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md |   26 +
 ...-BE80C9FF-D456-4120-937D-6FB30FA422D4.json |   26 +
 ...ID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md |   13 +
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |   26 +
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  591 +++++++
 ...-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json |   26 +
 ...ID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md |    9 +
 ...-BF226F62-E06D-4C61-8326-523D3F8CE492.json |   26 +
 ...ID-BF226F62-E06D-4C61-8326-523D3F8CE492.md |    8 +
 ...-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json |   26 +
 ...ID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md |   32 +
 ...-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json |   26 +
 ...ID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md |   47 +
 ...-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json |   26 +
 ...ID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md |  190 +++
 ...-C1680569-1170-4460-B42D-9B8D3D5125B6.json |   26 +
 ...ID-C1680569-1170-4460-B42D-9B8D3D5125B6.md |   61 +
 ...-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json |   26 +
 ...ID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md |   31 +
 ...-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json |   26 +
 ...ID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md |   27 +
 ...-C1E03C38-4DD6-43E9-8310-61A2FE452243.json |   26 +
 ...ID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md |  118 ++
 ...-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json |   26 +
 ...ID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md |   38 +
 ...-C20033B6-4C42-4BEC-84C0-D313859D9126.json |   26 +
 ...ID-C20033B6-4C42-4BEC-84C0-D313859D9126.md |  514 ++++++
 ...-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json |   26 +
 ...ID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md |    5 +
 ...-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json |   26 +
 ...ID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md |   45 +
 ...-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json |   26 +
 ...ID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md |  204 +++
 ...-C3B37EC3-FBB1-40BC-95B2-770849390851.json |   26 +
 ...ID-C3B37EC3-FBB1-40BC-95B2-770849390851.md |    5 +
 ...-C3FB4228-B601-4FD3-9802-8D40BEF90787.json |   26 +
 ...ID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md |   14 +
 ...-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json |   26 +
 ...ID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md |  152 ++
 ...-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json |   26 +
 ...ID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md |   27 +
 ...-C52A3557-8979-44A4-9FCE-480426F55A7F.json |   26 +
 ...ID-C52A3557-8979-44A4-9FCE-480426F55A7F.md |  499 ++++++
 ...-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json |   26 +
 ...ID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md |  495 ++++++
 ...-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json |   26 +
 ...ID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md |  301 ++++
 ...-C6AB6E89-39FB-498A-A333-5550A593DA7B.json |   26 +
 ...ID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md |   18 +
 ...-C742E2B5-1585-459D-B13A-139DEB0AC122.json |   26 +
 ...ID-C742E2B5-1585-459D-B13A-139DEB0AC122.md |   22 +
 ...-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json |   26 +
 ...ID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md |   18 +
 ...-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json |   26 +
 ...ID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md |   55 +
 ...-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json |   26 +
 ...ID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md |  102 ++
 ...-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json |   26 +
 ...ID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md |   55 +
 ...-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json |   26 +
 ...ID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md | 1018 ++++++++++++
 ...-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json |   26 +
 ...ID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md |    9 +
 ...-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json |   26 +
 ...ID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md |   13 +
 ...-CA96F723-CABE-4A23-AEAC-220BE12D2970.json |   26 +
 ...ID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md |    7 +
 ...-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json |   26 +
 ...ID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md |   51 +
 ...-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json |   26 +
 ...ID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md |   13 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |   26 +
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   12 +
 ...-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json |   26 +
 ...ID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md |  114 ++
 ...-CC1F0809-F068-41F6-853A-0033148C3436.json |   26 +
 ...ID-CC1F0809-F068-41F6-853A-0033148C3436.md |   20 +
 ...-CCC7880B-8316-4FDD-91D6-9680671E23D9.json |   26 +
 ...ID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md |  185 +++
 ...-CD1058AC-228F-424E-A2B0-45B93F4C582F.json |   26 +
 ...ID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md |   51 +
 ...-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json |   26 +
 ...ID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md |  358 +++++
 ...-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json |   26 +
 ...ID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md |   33 +
 ...-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json |   26 +
 ...ID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md |  204 +++
 ...-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json |   26 +
 ...ID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md |  113 ++
 ...-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json |   26 +
 ...ID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md |   11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |   26 +
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |   10 +
 ...-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json |   26 +
 ...ID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md |    6 +
 ...-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json |   26 +
 ...ID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md |   41 +
 ...-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json |   26 +
 ...ID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md |   25 +
 ...-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json |   26 +
 ...ID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md |   12 +
 ...-D3100235-F327-4C00-9AF8-F5C974D2F698.json |   26 +
 ...ID-D3100235-F327-4C00-9AF8-F5C974D2F698.md |   13 +
 ...-D3548220-4D77-4DBB-8313-CFAD68416264.json |   26 +
 ...ID-D3548220-4D77-4DBB-8313-CFAD68416264.md |   30 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |   26 +
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |   59 +
 ...-D47A61E0-1F97-4E09-A62C-C8B990640F56.json |   26 +
 ...ID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md |   28 +
 ...-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json |   26 +
 ...ID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md |   14 +
 ...-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json |   26 +
 ...ID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md |    5 +
 ...-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json |   26 +
 ...ID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md |   13 +
 ...-D63E4175-CA68-4648-B912-F20796292DD3.json |   26 +
 ...ID-D63E4175-CA68-4648-B912-F20796292DD3.md |   52 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |   26 +
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |    9 +
 ...-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json |   26 +
 ...ID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md |   86 ++
 ...-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json |   26 +
 ...ID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md |  230 +++
 ...-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json |   26 +
 ...ID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md |  143 ++
 ...-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json |   26 +
 ...ID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md |  150 ++
 ...-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json |   26 +
 ...ID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md |    7 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |   26 +
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   83 +
 ...-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json |   26 +
 ...ID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md |   28 +
 ...-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json |   26 +
 ...ID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md |   16 +
 ...-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json |   26 +
 ...ID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md |   53 +
 ...-DB2EE423-511B-432B-8425-82326DC29158.json |   26 +
 ...ID-DB2EE423-511B-432B-8425-82326DC29158.md |   24 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |   26 +
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |   23 +
 ...-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json |   26 +
 ...ID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md |   21 +
 ...-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json |   26 +
 ...ID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md |    7 +
 ...-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json |   26 +
 ...ID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md |  132 ++
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |   26 +
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |   14 +
 ...-DD626086-0E0C-460D-85BC-8E654BEEF70A.json |   26 +
 ...ID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md |   17 +
 ...-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json |   26 +
 ...ID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md |   15 +
 ...-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json |   26 +
 ...ID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md |    3 +
 ...-DE4B3C05-2C42-42E8-849A-B13E77080955.json |   26 +
 ...ID-DE4B3C05-2C42-42E8-849A-B13E77080955.md |   11 +
 ...-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json |   26 +
 ...ID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md |   75 +
 ...-DED3B0BE-A491-472F-B40B-A08F64835F17.json |   26 +
 ...ID-DED3B0BE-A491-472F-B40B-A08F64835F17.md |  150 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |   26 +
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |   68 +
 ...-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json |   26 +
 ...ID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md |   53 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |   26 +
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  160 ++
 ...-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json |   26 +
 ...ID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md |  159 ++
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |   26 +
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |   28 +
 ...-E012A526-E6C4-408D-A69C-AD7BC08B882C.json |   26 +
 ...ID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md |   63 +
 ...-E01FA212-4E9E-4403-9508-E4BB971643A3.json |   26 +
 ...ID-E01FA212-4E9E-4403-9508-E4BB971643A3.md |  203 +++
 ...-E02DD704-C987-41BB-AF3F-A23F35C097BD.json |   26 +
 ...ID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md |   27 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |   26 +
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |   65 +
 ...-E1159A9B-4A53-400A-A1E7-8604539EB39D.json |   26 +
 ...ID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md |   11 +
 ...-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json |   26 +
 ...ID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md |    7 +
 ...-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json |   26 +
 ...ID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md |   37 +
 ...-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json |   26 +
 ...ID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md |   92 ++
 ...-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json |   26 +
 ...ID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md |    7 +
 ...-E3911F3D-F635-42FA-B014-078FD60D3130.json |   26 +
 ...ID-E3911F3D-F635-42FA-B014-078FD60D3130.md |   23 +
 ...-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json |   26 +
 ...ID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md |   14 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |   26 +
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   49 +
 ...-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json |   26 +
 ...ID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md |  117 ++
 ...-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json |   26 +
 ...ID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md |   31 +
 ...-E55D4270-ED77-4161-8712-45824C891713.json |   26 +
 ...ID-E55D4270-ED77-4161-8712-45824C891713.md |   38 +
 ...-E5C429F5-9F57-481D-968A-64793E86EBCE.json |   26 +
 ...ID-E5C429F5-9F57-481D-968A-64793E86EBCE.md |   34 +
 ...-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json |   26 +
 ...ID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md |   15 +
 ...-E6C2AF29-A549-4B96-A778-039FC445D7F2.json |   26 +
 ...ID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md |    3 +
 ...-E748BC6D-7E45-4324-A174-9FB2012CBA27.json |   26 +
 ...ID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md |   13 +
 ...-E7DD5576-68E3-449D-8606-D2861BF53808.json |   26 +
 ...ID-E7DD5576-68E3-449D-8606-D2861BF53808.md |   12 +
 ...-E816369D-52FD-43B2-88F6-A5F748829203.json |   26 +
 ...ID-E816369D-52FD-43B2-88F6-A5F748829203.md |   10 +
 ...-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json |   26 +
 ...ID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md |   16 +
 ...-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json |   26 +
 ...ID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md |   48 +
 ...-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json |   26 +
 ...ID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md |   20 +
 ...-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json |   26 +
 ...ID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md |   18 +
 ...-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json |   26 +
 ...ID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md |   27 +
 ...-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json |   26 +
 ...ID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md |   11 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |   26 +
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |  191 +++
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |   26 +
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |    8 +
 ...-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json |   26 +
 ...ID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md |  496 ++++++
 ...-ED404402-F168-4635-ADEB-02609465196E.json |   26 +
 ...ID-ED404402-F168-4635-ADEB-02609465196E.md |   20 +
 ...-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json |   26 +
 ...ID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md |   19 +
 ...-EF20CD89-B756-4F84-BC6A-55B2488B5947.json |   26 +
 ...ID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md |   46 +
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |   26 +
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |   13 +
 ...-F003BCEE-0E64-412A-9045-295910E15A5A.json |   26 +
 ...ID-F003BCEE-0E64-412A-9045-295910E15A5A.md |  133 ++
 ...-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json |   26 +
 ...ID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md |    3 +
 ...-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json |   26 +
 ...ID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md |   53 +
 ...-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json |   26 +
 ...ID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md |    9 +
 ...-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json |   26 +
 ...ID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md |  328 ++++
 ...-F6459690-0DE9-48CE-95B2-C7BE033E8088.json |   26 +
 ...ID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md |   19 +
 ...-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json |   26 +
 ...ID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md |    4 +
 ...-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json |   26 +
 ...ID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md |   18 +
 ...-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json |   26 +
 ...ID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md |   31 +
 ...-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json |   26 +
 ...ID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md |  231 +++
 ...-F7C9EB98-701B-4C51-966C-3448AF3575AF.json |   26 +
 ...ID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md |   26 +
 ...-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json |   26 +
 ...ID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md |   80 +
 ...-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json |   26 +
 ...ID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md |  114 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |   26 +
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  189 +++
 ...-FBA4AD60-9130-49BD-B10F-074439138A4B.json |   26 +
 ...ID-FBA4AD60-9130-49BD-B10F-074439138A4B.md |   13 +
 ...-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json |   26 +
 ...ID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md |   14 +
 ...-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json |   26 +
 ...ID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md |   17 +
 ...-FE7CCD11-6021-491F-BC50-596DA68F9206.json |   26 +
 ...ID-FE7CCD11-6021-491F-BC50-596DA68F9206.md |   13 +
 ...-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json |   26 +
 ...ID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md |   56 +
 ...-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json |   26 +
 ...ID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md |   30 +
 ...-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json |   26 +
 ...ID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md |  111 ++
 ...-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json |   26 +
 ...ID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md |   25 +
 ...-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json |   26 +
 ...ID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md |   19 +
 ...-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json |   26 +
 ...ID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md |   18 +
 ...-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json |   26 +
 ...ID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md |   88 ++
 ...-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json |   26 +
 ...ID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md |   52 +
 ...-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json |   26 +
 ...ID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md |    9 +
 ...-030A6638-D9C6-492A-A021-8634B29738F7.json |   26 +
 ...ID-030A6638-D9C6-492A-A021-8634B29738F7.md |   63 +
 ...-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json |   26 +
 ...ID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md |   16 +
 ...-034C870E-F6DE-4D0B-950B-23A627D33C65.json |   26 +
 ...ID-034C870E-F6DE-4D0B-950B-23A627D33C65.md |   14 +
 ...-038058DD-CC8D-41F7-AF14-DB01B16993C4.json |   26 +
 ...ID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md |   41 +
 ...-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json |   26 +
 ...ID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md |   60 +
 ...-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json |   26 +
 ...ID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md |    7 +
 ...-0441F3DD-FF73-49C0-8900-718B95266989.json |   26 +
 ...ID-0441F3DD-FF73-49C0-8900-718B95266989.md |  262 ++++
 ...-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json |   26 +
 ...ID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md |  115 ++
 ...-06D232B4-F473-44C5-AD24-AECD128273E5.json |   26 +
 ...ID-06D232B4-F473-44C5-AD24-AECD128273E5.md |  136 ++
 ...-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json |   26 +
 ...ID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md |   14 +
 ...-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json |   26 +
 ...ID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md |   32 +
 ...-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json |   26 +
 ...ID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md |   71 +
 ...-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json |   26 +
 ...ID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md |   10 +
 ...-092B4E74-3662-4E21-9DA0-67958362DBE4.json |   26 +
 ...ID-092B4E74-3662-4E21-9DA0-67958362DBE4.md |   24 +
 ...-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json |   26 +
 ...ID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md |   22 +
 ...-09A31CD3-8237-4668-8509-A1C2EA9F3775.json |   26 +
 ...ID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md |    8 +
 ...-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json |   26 +
 ...ID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md |   34 +
 ...-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json |   26 +
 ...ID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md |   50 +
 ...-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json |   26 +
 ...ID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md |   12 +
 ...-0BBD18FA-91D0-406A-B004-3F068114DE70.json |   26 +
 ...ID-0BBD18FA-91D0-406A-B004-3F068114DE70.md |   61 +
 ...-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json |   26 +
 ...ID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md |  113 ++
 ...-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json |   26 +
 ...ID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md |   22 +
 ...-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json |   26 +
 ...ID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md |   21 +
 ...-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json |   26 +
 ...ID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md |   54 +
 ...-101B0634-4367-4B11-ACA0-923AC1CA635E.json |   26 +
 ...ID-101B0634-4367-4B11-ACA0-923AC1CA635E.md |   19 +
 ...-10BE13E9-1014-4162-97E7-A1056FED89B3.json |   26 +
 ...ID-10BE13E9-1014-4162-97E7-A1056FED89B3.md |   24 +
 ...-10D04894-711A-400A-98A7-A3DECE437CDA.json |   26 +
 ...ID-10D04894-711A-400A-98A7-A3DECE437CDA.md |    7 +
 ...-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json |   26 +
 ...ID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md |   12 +
 ...-12450828-47CC-4F83-9E94-AF80242C2E3A.json |   26 +
 ...ID-12450828-47CC-4F83-9E94-AF80242C2E3A.md |   14 +
 ...-127B939B-0C18-40CC-AC49-8DD0D58BE444.json |   26 +
 ...ID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md |   35 +
 ...-133E4178-5B4C-4BFF-8213-2662774F0B37.json |   26 +
 ...ID-133E4178-5B4C-4BFF-8213-2662774F0B37.md |   20 +
 ...-13940199-9CEA-485B-87AF-AB47536CD6AE.json |   26 +
 ...ID-13940199-9CEA-485B-87AF-AB47536CD6AE.md |  306 ++++
 ...-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json |   26 +
 ...ID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md |   22 +
 ...-13B77F8D-BA84-4649-A4C1-D137357E7A78.json |   26 +
 ...ID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md |  124 ++
 ...-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json |   26 +
 ...ID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md |   31 +
 ...-151B596B-EE69-4D4B-8C80-964A90D3523C.json |   26 +
 ...ID-151B596B-EE69-4D4B-8C80-964A90D3523C.md |   28 +
 ...-151C50C5-5883-4137-A9B0-EAF5F8087117.json |   26 +
 ...ID-151C50C5-5883-4137-A9B0-EAF5F8087117.md |   40 +
 ...-1621A716-2765-4655-B4D0-C95B8416F4D3.json |   26 +
 ...ID-1621A716-2765-4655-B4D0-C95B8416F4D3.md |   22 +
 ...-173469C2-D5C6-47F6-8A01-41C3D73B679B.json |   26 +
 ...ID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md |   45 +
 ...-1741A126-636E-4A96-812C-48A8B7A25E88.json |   26 +
 ...ID-1741A126-636E-4A96-812C-48A8B7A25E88.md |   23 +
 ...-17B067B3-32C3-4DE7-82DE-B6033C235495.json |   26 +
 ...ID-17B067B3-32C3-4DE7-82DE-B6033C235495.md |   13 +
 ...-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json |   26 +
 ...ID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md |  450 ++++++
 ...-180B8370-AEF2-45C1-9E72-99FF796CB222.json |   26 +
 ...ID-180B8370-AEF2-45C1-9E72-99FF796CB222.md |   39 +
 ...-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json |   26 +
 ...ID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md |   81 +
 ...-1AA91E38-BE43-4571-ADEB-714F77E9E728.json |   26 +
 ...ID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md |   62 +
 ...-1AC5F825-20D5-4B28-936A-2DD024250026.json |   26 +
 ...ID-1AC5F825-20D5-4B28-936A-2DD024250026.md |    6 +
 ...-1B184F05-C570-446E-8C3A-FC24792DE213.json |   26 +
 ...ID-1B184F05-C570-446E-8C3A-FC24792DE213.md |   28 +
 ...-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json |   26 +
 ...ID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md |  176 +++
 ...-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json |   26 +
 ...ID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md |   48 +
 ...-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json |   26 +
 ...ID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md |  124 ++
 ...-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json |   26 +
 ...ID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md |    9 +
 ...-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json |   26 +
 ...ID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md |   15 +
 ...-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json |   26 +
 ...ID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md |    3 +
 ...-1E710344-0932-4A51-B605-18AEF716E46F.json |   26 +
 ...ID-1E710344-0932-4A51-B605-18AEF716E46F.md |  115 ++
 ...-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json |   26 +
 ...ID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md |  161 ++
 ...-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json |   26 +
 ...ID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md |  140 ++
 ...-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json |   26 +
 ...ID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md |   63 +
 ...-1F30FE4D-FAD1-444B-9570-E20C339F257C.json |   26 +
 ...ID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md |  227 +++
 ...-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json |   26 +
 ...ID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md |    9 +
 ...-1FE536B8-0BE2-4851-8801-174C49D984F3.json |   26 +
 ...ID-1FE536B8-0BE2-4851-8801-174C49D984F3.md |   10 +
 ...-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json |   26 +
 ...ID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md |   12 +
 ...-20D6853D-60F1-45A8-90F5-47E242D57DB4.json |   26 +
 ...ID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md |   91 ++
 ...-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json |   26 +
 ...ID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md |   12 +
 ...-21F2F208-7360-4468-B1FF-524CA30CB993.json |   26 +
 ...ID-21F2F208-7360-4468-B1FF-524CA30CB993.md |   21 +
 ...-2277183A-E315-4439-A885-C111A77C7154.json |   26 +
 ...ID-2277183A-E315-4439-A885-C111A77C7154.md |   80 +
 ...-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json |   26 +
 ...ID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md |  240 +++
 ...-25A367DD-64FA-417A-B88B-B1D95C3E258B.json |   26 +
 ...ID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md |  128 ++
 ...-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json |   26 +
 ...ID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md |  199 +++
 ...-269D2944-5080-4897-86F5-AC949F4B83F1.json |   26 +
 ...ID-269D2944-5080-4897-86F5-AC949F4B83F1.md |   34 +
 ...-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json |   26 +
 ...ID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md |    8 +
 ...-27706317-FA6C-49E6-8D44-FAE2E35217F8.json |   26 +
 ...ID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md |   42 +
 ...-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json |   26 +
 ...ID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md |  130 ++
 ...-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json |   26 +
 ...ID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md |    9 +
 ...-29661D5A-2426-4114-B839-1242C7A7D6A8.json |   26 +
 ...ID-29661D5A-2426-4114-B839-1242C7A7D6A8.md |   50 +
 ...-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json |   26 +
 ...ID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md |   36 +
 ...-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json |   26 +
 ...ID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md |   51 +
 ...-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json |   26 +
 ...ID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md |   28 +
 ...-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json |   26 +
 ...ID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md |   20 +
 ...-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json |   26 +
 ...ID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md |    8 +
 ...-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json |   26 +
 ...ID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md |   52 +
 ...-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json |   26 +
 ...ID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md |   10 +
 ...-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json |   26 +
 ...ID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md |  220 +++
 ...-2D22E37B-3698-46F3-88BB-A36D96C849EF.json |   26 +
 ...ID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md |  207 +++
 ...-2D8A0A86-2231-4239-AB44-5475B4AE0827.json |   26 +
 ...ID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md |  489 ++++++
 ...-2DE45951-E56A-4651-AB77-F8C894E28788.json |   26 +
 ...ID-2DE45951-E56A-4651-AB77-F8C894E28788.md |   32 +
 ...-2DEB33CC-132A-494C-B242-CA09B02E9333.json |   26 +
 ...ID-2DEB33CC-132A-494C-B242-CA09B02E9333.md |   39 +
 ...-2DFC3858-043A-4053-AB10-F4534C7D7240.json |   26 +
 ...ID-2DFC3858-043A-4053-AB10-F4534C7D7240.md |   56 +
 ...-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json |   26 +
 ...ID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md |   26 +
 ...-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json |   26 +
 ...ID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md |  156 ++
 ...-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json |   26 +
 ...ID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md |  104 ++
 ...-2F776F04-B8E7-428D-823B-AB121DFE48AB.json |   26 +
 ...ID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md |   15 +
 ...-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json |   26 +
 ...ID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md |  462 ++++++
 ...-3148715A-05C1-4793-9B2B-6DB66D7C101D.json |   26 +
 ...ID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md |   43 +
 ...-3159C5BA-04D5-4035-9842-86197618F7D2.json |   26 +
 ...ID-3159C5BA-04D5-4035-9842-86197618F7D2.md |  363 +++++
 ...-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json |   26 +
 ...ID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md |    8 +
 ...-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json |   26 +
 ...ID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md |  188 +++
 ...-32D8CBBE-0375-48BC-8038-E6618F94BE83.json |   26 +
 ...ID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md |  561 +++++++
 ...-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json |   26 +
 ...ID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md |  102 ++
 ...-334FA46B-AE38-41A7-BACC-8F8384C5D010.json |   26 +
 ...ID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md |    6 +
 ...-3391053D-4F2A-49A4-8823-E63F708C55C4.json |   26 +
 ...ID-3391053D-4F2A-49A4-8823-E63F708C55C4.md |   21 +
 ...-33E060CF-9C8E-4AA3-971B-7C5E06954157.json |   26 +
 ...ID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md |   51 +
 ...-34DE6BFF-C4CD-4C78-A963-62798D548E61.json |   26 +
 ...ID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md |    7 +
 ...-3535B779-7CDA-4288-A03A-02E0F9552B7B.json |   26 +
 ...ID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md |   55 +
 ...-3559161C-E53A-419A-B7E5-663F1440004F.json |   26 +
 ...ID-3559161C-E53A-419A-B7E5-663F1440004F.md |    5 +
 ...-35F886E0-C4F0-42F5-AF68-AA1481040D76.json |   26 +
 ...ID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md |   92 ++
 ...-367B7FE3-99E0-438C-87C0-43F9A179B552.json |   26 +
 ...ID-367B7FE3-99E0-438C-87C0-43F9A179B552.md |   78 +
 ...-36BA3E37-26D3-488F-85C2-942C45119F02.json |   26 +
 ...ID-36BA3E37-26D3-488F-85C2-942C45119F02.md |  297 ++++
 ...-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json |   26 +
 ...ID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md |   13 +
 ...-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json |   26 +
 ...ID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md |   11 +
 ...-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json |   26 +
 ...ID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md |    5 +
 ...-37CA1665-B331-452A-AA3D-59608D85F006.json |   26 +
 ...ID-37CA1665-B331-452A-AA3D-59608D85F006.md |  112 ++
 ...-382BFCD5-DE8D-4C54-B3D6-704970132153.json |   26 +
 ...ID-382BFCD5-DE8D-4C54-B3D6-704970132153.md |  207 +++
 ...-38B4C746-179D-43CA-9205-9DC63ACC87EF.json |   26 +
 ...ID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md |  246 +++
 ...-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json |   26 +
 ...ID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md |   12 +
 ...-397630C5-C2CE-4E35-A45D-0228C8F70867.json |   26 +
 ...ID-397630C5-C2CE-4E35-A45D-0228C8F70867.md |   12 +
 ...-39D4284E-C733-48AD-94DE-CD929AEB0431.json |   26 +
 ...ID-39D4284E-C733-48AD-94DE-CD929AEB0431.md |  128 ++
 ...-3A38516A-B491-407B-AF69-9DF38E4266DF.json |   26 +
 ...ID-3A38516A-B491-407B-AF69-9DF38E4266DF.md |   29 +
 ...-3A627DBF-D797-42A2-A9AC-AAC321376068.json |   26 +
 ...ID-3A627DBF-D797-42A2-A9AC-AAC321376068.md |   25 +
 ...-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json |   26 +
 ...ID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md |   87 ++
 ...-3B6AC391-B993-47A2-8264-7389873C8D6D.json |   26 +
 ...ID-3B6AC391-B993-47A2-8264-7389873C8D6D.md |   16 +
 ...-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json |   26 +
 ...ID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md |   41 +
 ...-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json |   26 +
 ...ID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md |  325 ++++
 ...-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json |   26 +
 ...ID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md |   11 +
 ...-3CA69B8E-D437-40EC-9755-668930BA21F4.json |   26 +
 ...ID-3CA69B8E-D437-40EC-9755-668930BA21F4.md |  281 ++++
 ...-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json |   26 +
 ...ID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md |   33 +
 ...-3CEB493A-1086-4AE2-8220-93B372329509.json |   26 +
 ...ID-3CEB493A-1086-4AE2-8220-93B372329509.md |    5 +
 ...-3D3058F0-C2FE-4995-8D62-55A069D50709.json |   26 +
 ...ID-3D3058F0-C2FE-4995-8D62-55A069D50709.md |  139 ++
 ...-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json |   26 +
 ...ID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md |   11 +
 ...-3E6007AB-2F77-4783-8610-592F1BB9125B.json |   26 +
 ...ID-3E6007AB-2F77-4783-8610-592F1BB9125B.md |  163 ++
 ...-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json |   26 +
 ...ID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md | 1373 +++++++++++++++++
 ...-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json |   26 +
 ...ID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md |   92 ++
 ...-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json |   26 +
 ...ID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md |   86 ++
 ...-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json |   26 +
 ...ID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md |   40 +
 ...-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json |   26 +
 ...ID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md |  157 ++
 ...-421A3218-7033-4066-AF8E-AA2D46D4385C.json |   26 +
 ...ID-421A3218-7033-4066-AF8E-AA2D46D4385C.md |   26 +
 ...-44272A47-8855-48A0-B475-E940CE97DD7A.json |   26 +
 ...ID-44272A47-8855-48A0-B475-E940CE97DD7A.md |   16 +
 ...-443DA867-07E9-416F-ABFB-2C4BF2312D53.json |   26 +
 ...ID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md |  191 +++
 ...-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json |   26 +
 ...ID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md |   22 +
 ...-44644079-BC85-448F-B542-23E18E9D5602.json |   26 +
 ...ID-44644079-BC85-448F-B542-23E18E9D5602.md |   72 +
 ...-44A7BA66-FC27-40C3-8A12-2704D2043B53.json |   26 +
 ...ID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md |   69 +
 ...-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json |   26 +
 ...ID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md |   30 +
 ...-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json |   26 +
 ...ID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md |  316 ++++
 ...-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json |   26 +
 ...ID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md |  130 ++
 ...-45DBACB2-9ED7-4538-9BF9-2D121178F539.json |   26 +
 ...ID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md |   47 +
 ...-46A53E20-D2A8-4233-8829-7865C7A434B7.json |   26 +
 ...ID-46A53E20-D2A8-4233-8829-7865C7A434B7.md |   42 +
 ...-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json |   26 +
 ...ID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md |   11 +
 ...-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json |   26 +
 ...ID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md |   18 +
 ...-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json |   26 +
 ...ID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md |  383 +++++
 ...-48ED6B2F-2E0B-491F-A497-139DD9B91284.json |   26 +
 ...ID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md |   17 +
 ...-49022137-A78E-4863-B1CF-D455EDD1A7D2.json |   26 +
 ...ID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md |    3 +
 ...-49067498-304A-4C38-B9C1-D8CF296DD3FA.json |   26 +
 ...ID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md |   28 +
 ...-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json |   26 +
 ...ID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md |   53 +
 ...-4983900F-0A3F-4F61-BB06-8270BE27C886.json |   26 +
 ...ID-4983900F-0A3F-4F61-BB06-8270BE27C886.md |   33 +
 ...-49F13E32-7912-4F28-8C78-5DF3AB06E690.json |   26 +
 ...ID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md |    9 +
 ...-4A13998A-C40E-4505-B1A1-16B21926D177.json |   26 +
 ...ID-4A13998A-C40E-4505-B1A1-16B21926D177.md |   15 +
 ...-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json |   26 +
 ...ID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md |   39 +
 ...-4CCF6004-31A7-4B35-996D-5E12877CB443.json |   26 +
 ...ID-4CCF6004-31A7-4B35-996D-5E12877CB443.md |    3 +
 ...-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json |   26 +
 ...ID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md |   15 +
 ...-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json |   26 +
 ...ID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md |   13 +
 ...-4F4F8735-4673-4408-BDA3-C295F2A88174.json |   26 +
 ...ID-4F4F8735-4673-4408-BDA3-C295F2A88174.md |    7 +
 ...-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json |   26 +
 ...ID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md |    7 +
 ...-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json |   26 +
 ...ID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md |  257 +++
 ...-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json |   26 +
 ...ID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md |  153 ++
 ...-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json |   26 +
 ...ID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md |  301 ++++
 ...-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json |   26 +
 ...ID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md |   55 +
 ...-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json |   26 +
 ...ID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md |    8 +
 ...-5473844F-B09C-4F23-AC2F-A305A384136B.json |   26 +
 ...ID-5473844F-B09C-4F23-AC2F-A305A384136B.md |   61 +
 ...-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json |   26 +
 ...ID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md |   41 +
 ...-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json |   26 +
 ...ID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md |   11 +
 ...-55E760C3-2167-4A03-88ED-D9078C196D74.json |   26 +
 ...ID-55E760C3-2167-4A03-88ED-D9078C196D74.md |    9 +
 ...-563347AC-C86B-4AC7-BF58-B80A3201662F.json |   26 +
 ...ID-563347AC-C86B-4AC7-BF58-B80A3201662F.md |   13 +
 ...-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json |   26 +
 ...ID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md |   27 +
 ...-56F6E993-6289-4BC0-AFD6-938516823FC8.json |   26 +
 ...ID-56F6E993-6289-4BC0-AFD6-938516823FC8.md |   15 +
 ...-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json |   26 +
 ...ID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md |  184 +++
 ...-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json |   26 +
 ...ID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md |   34 +
 ...-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json |   26 +
 ...ID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md |   31 +
 ...-580E4107-827A-43F6-888D-5CDD41EB42E0.json |   26 +
 ...ID-580E4107-827A-43F6-888D-5CDD41EB42E0.md |   25 +
 ...-589A7663-2242-4FBE-9214-FE0F91A29972.json |   26 +
 ...ID-589A7663-2242-4FBE-9214-FE0F91A29972.md |   49 +
 ...-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json |   26 +
 ...ID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md |    9 +
 ...-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json |   26 +
 ...ID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md |   13 +
 ...-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json |   26 +
 ...ID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md |  110 ++
 ...-5AE10D03-5E33-4437-8477-059B0390B662.json |   26 +
 ...ID-5AE10D03-5E33-4437-8477-059B0390B662.md |   28 +
 ...-5B7DB753-B382-4E98-BF3A-599C15334A69.json |   26 +
 ...ID-5B7DB753-B382-4E98-BF3A-599C15334A69.md |    8 +
 ...-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json |   26 +
 ...ID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md |  119 ++
 ...-5CBD20D3-D323-4F6E-A543-E19708439C5D.json |   26 +
 ...ID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md |   15 +
 ...-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json |   26 +
 ...ID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md |   26 +
 ...-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json |   26 +
 ...ID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md |   80 +
 ...-5D659229-2AFA-4A63-9194-D128E673AA02.json |   26 +
 ...ID-5D659229-2AFA-4A63-9194-D128E673AA02.md |   22 +
 ...-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json |   26 +
 ...ID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md |  363 +++++
 ...-5F72EBA5-E780-4511-8EA0-4ABA11628663.json |   26 +
 ...ID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md |    4 +
 ...-607895C8-5308-4A68-9219-1EA342DB9C6C.json |   26 +
 ...ID-607895C8-5308-4A68-9219-1EA342DB9C6C.md |    9 +
 ...-60BD671A-C620-49C7-81EB-56C5197E61C2.json |   26 +
 ...ID-60BD671A-C620-49C7-81EB-56C5197E61C2.md |   45 +
 ...-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json |   26 +
 ...ID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md |   31 +
 ...-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json |   26 +
 ...ID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md |   55 +
 ...-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json |   26 +
 ...ID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md |   75 +
 ...-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json |   26 +
 ...ID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md |   26 +
 ...-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json |   26 +
 ...ID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md |   64 +
 ...-633B871A-14AC-42B5-9BDA-8F907433F700.json |   26 +
 ...ID-633B871A-14AC-42B5-9BDA-8F907433F700.md |   34 +
 ...-63B50C5A-C3AD-4543-8A89-58110DDD5064.json |   26 +
 ...ID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md |  130 ++
 ...-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json |   26 +
 ...ID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md |   30 +
 ...-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json |   26 +
 ...ID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md |   16 +
 ...-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json |   26 +
 ...ID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md |   37 +
 ...-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json |   26 +
 ...ID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md |   34 +
 ...-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json |   26 +
 ...ID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md |   85 +
 ...-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json |   26 +
 ...ID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md |   22 +
 ...-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json |   26 +
 ...ID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md |  119 ++
 ...-663434D4-E8EB-4468-992C-107B9FD4AC30.json |   26 +
 ...ID-663434D4-E8EB-4468-992C-107B9FD4AC30.md |    7 +
 ...-66740846-A143-48D1-80FF-7314D86BE61A.json |   26 +
 ...ID-66740846-A143-48D1-80FF-7314D86BE61A.md |   56 +
 ...-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json |   26 +
 ...ID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md |   34 +
 ...-6779EFD7-BD52-4678-AC19-30AE09F26217.json |   26 +
 ...ID-6779EFD7-BD52-4678-AC19-30AE09F26217.md |   13 +
 ...-68E5CB99-152C-463C-9E41-5B2C67C659CD.json |   26 +
 ...ID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md |   14 +
 ...-690DD9D4-9114-4EE1-97F1-254D7B67B733.json |   26 +
 ...ID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md |    6 +
 ...-6A02D571-9949-4EA4-B43C-C2CED90210EF.json |   26 +
 ...ID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md |   20 +
 ...-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json |   26 +
 ...ID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md |   60 +
 ...-6B3D18B4-5885-4318-848F-DE294F57057B.json |   26 +
 ...ID-6B3D18B4-5885-4318-848F-DE294F57057B.md |  222 +++
 ...-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json |   26 +
 ...ID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md |   21 +
 ...-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json |   26 +
 ...ID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md |   85 +
 ...-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json |   26 +
 ...ID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md |   13 +
 ...-6C22C389-3D06-4DF0-B997-1CA161175182.json |   26 +
 ...ID-6C22C389-3D06-4DF0-B997-1CA161175182.md |  147 ++
 ...-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json |   26 +
 ...ID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md |   32 +
 ...-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json |   26 +
 ...ID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md |   56 +
 ...-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json |   26 +
 ...ID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md |   17 +
 ...-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json |   26 +
 ...ID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md |   16 +
 ...-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json |   26 +
 ...ID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md |  468 ++++++
 ...-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json |   26 +
 ...ID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md |   28 +
 ...-6FFCD815-6AC5-46F9-AB71-F293570366A8.json |   26 +
 ...ID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md |   87 ++
 ...-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json |   26 +
 ...ID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md |   71 +
 ...-7056841F-C280-4C83-8065-017EF45643F9.json |   26 +
 ...ID-7056841F-C280-4C83-8065-017EF45643F9.md |   75 +
 ...-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json |   26 +
 ...ID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md |   20 +
 ...-719570B7-BE8A-49B2-87D7-336A9703ED88.json |   26 +
 ...ID-719570B7-BE8A-49B2-87D7-336A9703ED88.md |   32 +
 ...-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json |   26 +
 ...ID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md |   12 +
 ...-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json |   26 +
 ...ID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md |  101 ++
 ...-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json |   26 +
 ...ID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md |  441 ++++++
 ...-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json |   26 +
 ...ID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md |   64 +
 ...-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json |   26 +
 ...ID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md |    5 +
 ...-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json |   26 +
 ...ID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md |   13 +
 ...-75D89535-68AE-4507-A961-26CE8914F074.json |   26 +
 ...ID-75D89535-68AE-4507-A961-26CE8914F074.md |   96 ++
 ...-768B1CD6-73F8-4CBC-9675-E03000B36147.json |   26 +
 ...ID-768B1CD6-73F8-4CBC-9675-E03000B36147.md |    9 +
 ...-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json |   26 +
 ...ID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md |  411 +++++
 ...-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json |   26 +
 ...ID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md |   14 +
 ...-77287C89-E688-49C4-869F-652DE15478FB.json |   26 +
 ...ID-77287C89-E688-49C4-869F-652DE15478FB.md |   69 +
 ...-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json |   26 +
 ...ID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md |   32 +
 ...-786D5554-1448-4001-A39C-647F22CA9278.json |   26 +
 ...ID-786D5554-1448-4001-A39C-647F22CA9278.md |   31 +
 ...-78DC62BA-524C-456D-827F-465C10A1AA6F.json |   26 +
 ...ID-78DC62BA-524C-456D-827F-465C10A1AA6F.md |   43 +
 ...-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json |   26 +
 ...ID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md |    9 +
 ...-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json |   26 +
 ...ID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md |  100 ++
 ...-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json |   26 +
 ...ID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md |  106 ++
 ...-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json |   26 +
 ...ID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md |  439 ++++++
 ...-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json |   26 +
 ...ID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md |    8 +
 ...-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json |   26 +
 ...ID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md |   80 +
 ...-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json |   26 +
 ...ID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md |    9 +
 ...-7BD87211-4E8A-480C-A7B6-E502808743EC.json |   26 +
 ...ID-7BD87211-4E8A-480C-A7B6-E502808743EC.md |   21 +
 ...-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json |   26 +
 ...ID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md |   29 +
 ...-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json |   26 +
 ...ID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md |  888 +++++++++++
 ...-7C6154EA-09BC-4E68-8BAB-D784F0582440.json |   26 +
 ...ID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md |   12 +
 ...-7CA53A6D-026B-4977-8247-349750CE4EB9.json |   26 +
 ...ID-7CA53A6D-026B-4977-8247-349750CE4EB9.md |   22 +
 ...-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json |   26 +
 ...ID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md |    3 +
 ...-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json |   26 +
 ...ID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md |   22 +
 ...-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json |   26 +
 ...ID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md |  177 +++
 ...-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json |   26 +
 ...ID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md |   25 +
 ...-80911C58-F6AB-4001-B50E-EC0F43773A5E.json |   26 +
 ...ID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md |   15 +
 ...-8143252C-EC38-43B2-B2E0-443A60C01768.json |   26 +
 ...ID-8143252C-EC38-43B2-B2E0-443A60C01768.md |   63 +
 ...-8168FFDF-77DD-42E0-B747-95099C7852AB.json |   26 +
 ...ID-8168FFDF-77DD-42E0-B747-95099C7852AB.md |   17 +
 ...-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json |   26 +
 ...ID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md |  264 ++++
 ...-826F09D8-C40B-483D-9CB5-CE504BD18810.json |   26 +
 ...ID-826F09D8-C40B-483D-9CB5-CE504BD18810.md |   74 +
 ...-82C53DF1-4293-41E2-A90A-740C1814DD12.json |   26 +
 ...ID-82C53DF1-4293-41E2-A90A-740C1814DD12.md |   61 +
 ...-84B6C16D-5601-4CFB-9C53-47AE75271884.json |   26 +
 ...ID-84B6C16D-5601-4CFB-9C53-47AE75271884.md |  161 ++
 ...-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json |   26 +
 ...ID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md |   51 +
 ...-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json |   26 +
 ...ID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md |    3 +
 ...-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json |   26 +
 ...ID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md |    7 +
 ...-87CB98DB-3915-4176-822C-E86A5AA54C4D.json |   26 +
 ...ID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md |  322 ++++
 ...-8808CDAD-319E-4259-99D8-4D43440E63FE.json |   26 +
 ...ID-8808CDAD-319E-4259-99D8-4D43440E63FE.md |    9 +
 ...-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json |   26 +
 ...ID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md |   23 +
 ...-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json |   26 +
 ...ID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md |   20 +
 ...-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json |   26 +
 ...ID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md |   11 +
 ...-89F63373-6CC7-4498-9A70-75BB1FD6D779.json |   26 +
 ...ID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md |    6 +
 ...-89FD5558-DFD3-459B-A56D-BD998574F805.json |   26 +
 ...ID-89FD5558-DFD3-459B-A56D-BD998574F805.md |   14 +
 ...-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json |   26 +
 ...ID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md |   11 +
 ...-8A557829-64DF-4A0A-84FC-FC2C8755B391.json |   26 +
 ...ID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md |  172 +++
 ...-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json |   26 +
 ...ID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md |  191 +++
 ...-8AC08484-473F-41E8-B106-A90BC96B03C4.json |   26 +
 ...ID-8AC08484-473F-41E8-B106-A90BC96B03C4.md |   31 +
 ...-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json |   26 +
 ...ID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md |   39 +
 ...-8C608C16-055C-4708-BA01-87FACE15EF6D.json |   26 +
 ...ID-8C608C16-055C-4708-BA01-87FACE15EF6D.md |   86 ++
 ...-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json |   26 +
 ...ID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md |   30 +
 ...-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json |   26 +
 ...ID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md |    9 +
 ...-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json |   26 +
 ...ID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md |  176 +++
 ...-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json |   26 +
 ...ID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md |  212 +++
 ...-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json |   26 +
 ...ID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md |   80 +
 ...-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json |   26 +
 ...ID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md |   13 +
 ...-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json |   26 +
 ...ID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md |   20 +
 ...-9132296F-B580-4107-8041-9E30C7EC4291.json |   26 +
 ...ID-9132296F-B580-4107-8041-9E30C7EC4291.md |    8 +
 ...-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json |   26 +
 ...ID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md |   35 +
 ...-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json |   26 +
 ...ID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md |   17 +
 ...-9372294C-3A13-490D-BF63-BA01AB008C43.json |   26 +
 ...ID-9372294C-3A13-490D-BF63-BA01AB008C43.md |   11 +
 ...-94133965-3802-4768-A71D-2AD5F8402BD9.json |   26 +
 ...ID-94133965-3802-4768-A71D-2AD5F8402BD9.md |  116 ++
 ...-949DC89F-26C2-4028-9A1F-2616FB466736.json |   26 +
 ...ID-949DC89F-26C2-4028-9A1F-2616FB466736.md |   13 +
 ...-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json |   26 +
 ...ID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md |    8 +
 ...-96732ACE-6F43-453A-8F9B-FD0F1C717362.json |   26 +
 ...ID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md |   33 +
 ...-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json |   26 +
 ...ID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md |  268 ++++
 ...-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json |   26 +
 ...ID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md |   64 +
 ...-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json |   26 +
 ...ID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md |  135 ++
 ...-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json |   26 +
 ...ID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md |    3 +
 ...-98351F93-76B4-480B-91F1-58E3E3492651.json |   26 +
 ...ID-98351F93-76B4-480B-91F1-58E3E3492651.md |  152 ++
 ...-9B75C475-9243-4444-BF22-C43480298274.json |   26 +
 ...ID-9B75C475-9243-4444-BF22-C43480298274.md |   15 +
 ...-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json |   26 +
 ...ID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md |   17 +
 ...-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json |   26 +
 ...ID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md |    9 +
 ...-9BDE2563-18FC-49B0-83D7-47F57E044D97.json |   26 +
 ...ID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md |   38 +
 ...-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json |   26 +
 ...ID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md |  185 +++
 ...-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json |   26 +
 ...ID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md |   10 +
 ...-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json |   26 +
 ...ID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md |   33 +
 ...-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json |   26 +
 ...ID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md |  142 ++
 ...-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json |   26 +
 ...ID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md |  116 ++
 ...-9DA820B7-7477-4980-848B-7161BDB5C43E.json |   26 +
 ...ID-9DA820B7-7477-4980-848B-7161BDB5C43E.md |   53 +
 ...-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json |   26 +
 ...ID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md |   10 +
 ...-9EC70919-852C-427E-ACDF-D59319D72468.json |   26 +
 ...ID-9EC70919-852C-427E-ACDF-D59319D72468.md |   24 +
 ...-9ECF72A1-9565-4202-A087-82313C2F8D58.json |   26 +
 ...ID-9ECF72A1-9565-4202-A087-82313C2F8D58.md |   58 +
 ...-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json |   26 +
 ...ID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md |   14 +
 ...-9F022B96-52CA-499B-978C-2CB55DCCAF48.json |   26 +
 ...ID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md |   80 +
 ...-9F78ED42-26BC-405F-88BC-3B14279A3306.json |   26 +
 ...ID-9F78ED42-26BC-405F-88BC-3B14279A3306.md |   32 +
 ...-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json |   26 +
 ...ID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md |   69 +
 ...-A0DC9F48-028D-4283-8572-FDD0A432E125.json |   26 +
 ...ID-A0DC9F48-028D-4283-8572-FDD0A432E125.md |   27 +
 ...-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json |   26 +
 ...ID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md |  264 ++++
 ...-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json |   26 +
 ...ID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md |   94 ++
 ...-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json |   26 +
 ...ID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md |   15 +
 ...-A2766933-3113-44EF-8458-88636F4301B3.json |   26 +
 ...ID-A2766933-3113-44EF-8458-88636F4301B3.md |    3 +
 ...-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json |   26 +
 ...ID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md |  146 ++
 ...-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json |   26 +
 ...ID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md |   38 +
 ...-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json |   26 +
 ...ID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md |   19 +
 ...-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json |   21 +
 ...ID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md |   27 +
 ...-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json |   26 +
 ...ID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md |   13 +
 ...-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json |   26 +
 ...ID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md |   21 +
 ...-A50734F6-41F7-4350-B07E-92C559E94119.json |   26 +
 ...ID-A50734F6-41F7-4350-B07E-92C559E94119.md |   30 +
 ...-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json |   26 +
 ...ID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md |   19 +
 ...-A586E426-9C40-4FD0-B749-7E962F9F04C4.json |   26 +
 ...ID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md |    9 +
 ...-A75681BD-B103-4441-AAD7-E1F848FFE56E.json |   26 +
 ...ID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md |    5 +
 ...-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json |   26 +
 ...ID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md |   97 ++
 ...-AB0E1772-B646-49E2-8318-B2495341839D.json |   26 +
 ...ID-AB0E1772-B646-49E2-8318-B2495341839D.md |   11 +
 ...-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json |   26 +
 ...ID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md |   95 ++
 ...-AB883016-0848-46D7-8BB0-37DF09076725.json |   26 +
 ...ID-AB883016-0848-46D7-8BB0-37DF09076725.md |   15 +
 ...-AB938CF2-D0FE-4516-931D-0238D0662B84.json |   26 +
 ...ID-AB938CF2-D0FE-4516-931D-0238D0662B84.md |   41 +
 ...-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json |   26 +
 ...ID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md |   57 +
 ...-AB95E8ED-82A1-493E-82D0-613D80FB602E.json |   26 +
 ...ID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md |   31 +
 ...-ABC2295F-BA5B-49C6-BF73-263A724F948F.json |   26 +
 ...ID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md |  959 ++++++++++++
 ...-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json |   26 +
 ...ID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md |   34 +
 ...-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json |   26 +
 ...ID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md |   36 +
 ...-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json |   26 +
 ...ID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md |    7 +
 ...-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json |   26 +
 ...ID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md |   11 +
 ...-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json |   26 +
 ...ID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md |   14 +
 ...-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json |   26 +
 ...ID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md |   12 +
 ...-ADDC3274-0758-43B9-BF31-6EA3EB319288.json |   26 +
 ...ID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md |   32 +
 ...-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json |   26 +
 ...ID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md |    8 +
 ...-AE27985B-5909-407F-A105-5B0574715D13.json |   26 +
 ...ID-AE27985B-5909-407F-A105-5B0574715D13.md |   19 +
 ...-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json |   26 +
 ...ID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md |   57 +
 ...-AFA85086-2874-4303-8999-E919DF886C44.json |   26 +
 ...ID-AFA85086-2874-4303-8999-E919DF886C44.md |   31 +
 ...-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json |   26 +
 ...ID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md |  300 ++++
 ...-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json |   26 +
 ...ID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md |   55 +
 ...-B2113088-6A1D-4A43-A781-BD280C35FA69.json |   26 +
 ...ID-B2113088-6A1D-4A43-A781-BD280C35FA69.md |   18 +
 ...-B299B747-2692-4406-9FCD-760C2EFE1E65.json |   26 +
 ...ID-B299B747-2692-4406-9FCD-760C2EFE1E65.md |   15 +
 ...-B379FDF9-2963-4336-AFC1-14372793FA70.json |   26 +
 ...ID-B379FDF9-2963-4336-AFC1-14372793FA70.md |   21 +
 ...-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json |   26 +
 ...ID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md |  183 +++
 ...-B47A4967-DCA3-45C4-B983-83CEB43711DC.json |   26 +
 ...ID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md |  295 ++++
 ...-B5387FE3-B36D-4924-B168-329B6E41D811.json |   26 +
 ...ID-B5387FE3-B36D-4924-B168-329B6E41D811.md |    3 +
 ...-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json |   26 +
 ...ID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md |   16 +
 ...-B637812E-A51A-4AD5-B6F1-5E5822709711.json |   26 +
 ...ID-B637812E-A51A-4AD5-B6F1-5E5822709711.md |   23 +
 ...-B67FF274-342F-4B96-B5F9-0B8222C662DC.json |   26 +
 ...ID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md |    3 +
 ...-B6D4283B-948C-4722-8C96-21CDB727D0EE.json |   26 +
 ...ID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md |   90 ++
 ...-B6F5194C-290E-464F-A718-232984A6E8B5.json |   26 +
 ...ID-B6F5194C-290E-464F-A718-232984A6E8B5.md |    6 +
 ...-B73068EC-E619-4EA2-B84B-D4941E1D1779.json |   26 +
 ...ID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md |  314 ++++
 ...-B7496F21-B633-436F-850B-507E482F96F2.json |   26 +
 ...ID-B7496F21-B633-436F-850B-507E482F96F2.md |   30 +
 ...-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json |   26 +
 ...ID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md |   38 +
 ...-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json |   26 +
 ...ID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md |   11 +
 ...-B7E3F043-2330-4392-9803-B649558F488B.json |   26 +
 ...ID-B7E3F043-2330-4392-9803-B649558F488B.md |   10 +
 ...-B86C6485-C80C-480F-87B4-4352963D74A5.json |   26 +
 ...ID-B86C6485-C80C-480F-87B4-4352963D74A5.md |   93 ++
 ...-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json |   26 +
 ...ID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md |   78 +
 ...-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json |   26 +
 ...ID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md |   40 +
 ...-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json |   26 +
 ...ID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md |   39 +
 ...-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json |   26 +
 ...ID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md |   29 +
 ...-BB270862-D56D-4B6F-86B7-030ED273E907.json |   26 +
 ...ID-BB270862-D56D-4B6F-86B7-030ED273E907.md |   60 +
 ...-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json |   26 +
 ...ID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md |   47 +
 ...-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json |   26 +
 ...ID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md |  182 +++
 ...-BC17942D-DE0B-4244-900F-DE38D31A09EC.json |   26 +
 ...ID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md |   15 +
 ...-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json |   26 +
 ...ID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md |  179 +++
 ...-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json |   26 +
 ...ID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md |   52 +
 ...-BD0C3274-B70C-437A-B89C-C77A703FFD53.json |   26 +
 ...ID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md |   28 +
 ...-BD4F0587-C0E9-4120-9D74-B54015579A60.json |   26 +
 ...ID-BD4F0587-C0E9-4120-9D74-B54015579A60.md |    6 +
 ...-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json |   26 +
 ...ID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md |   26 +
 ...-BE80C9FF-D456-4120-937D-6FB30FA422D4.json |   26 +
 ...ID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md |   13 +
 ...-BE852729-65DF-4377-9A64-F05D47CD9D49.json |   26 +
 ...ID-BE852729-65DF-4377-9A64-F05D47CD9D49.md |  591 +++++++
 ...-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json |   26 +
 ...ID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md |    9 +
 ...-BF226F62-E06D-4C61-8326-523D3F8CE492.json |   26 +
 ...ID-BF226F62-E06D-4C61-8326-523D3F8CE492.md |    8 +
 ...-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json |   26 +
 ...ID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md |   32 +
 ...-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json |   26 +
 ...ID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md |   47 +
 ...-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json |   26 +
 ...ID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md |  190 +++
 ...-C1680569-1170-4460-B42D-9B8D3D5125B6.json |   26 +
 ...ID-C1680569-1170-4460-B42D-9B8D3D5125B6.md |   61 +
 ...-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json |   26 +
 ...ID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md |   31 +
 ...-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json |   26 +
 ...ID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md |   27 +
 ...-C1E03C38-4DD6-43E9-8310-61A2FE452243.json |   26 +
 ...ID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md |  118 ++
 ...-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json |   26 +
 ...ID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md |   38 +
 ...-C20033B6-4C42-4BEC-84C0-D313859D9126.json |   26 +
 ...ID-C20033B6-4C42-4BEC-84C0-D313859D9126.md |  514 ++++++
 ...-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json |   26 +
 ...ID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md |    5 +
 ...-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json |   26 +
 ...ID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md |   45 +
 ...-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json |   26 +
 ...ID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md |  204 +++
 ...-C3B37EC3-FBB1-40BC-95B2-770849390851.json |   26 +
 ...ID-C3B37EC3-FBB1-40BC-95B2-770849390851.md |    5 +
 ...-C3FB4228-B601-4FD3-9802-8D40BEF90787.json |   26 +
 ...ID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md |   14 +
 ...-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json |   26 +
 ...ID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md |  152 ++
 ...-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json |   26 +
 ...ID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md |   27 +
 ...-C52A3557-8979-44A4-9FCE-480426F55A7F.json |   26 +
 ...ID-C52A3557-8979-44A4-9FCE-480426F55A7F.md |  499 ++++++
 ...-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json |   26 +
 ...ID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md |  495 ++++++
 ...-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json |   26 +
 ...ID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md |  301 ++++
 ...-C6AB6E89-39FB-498A-A333-5550A593DA7B.json |   26 +
 ...ID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md |   18 +
 ...-C742E2B5-1585-459D-B13A-139DEB0AC122.json |   26 +
 ...ID-C742E2B5-1585-459D-B13A-139DEB0AC122.md |   22 +
 ...-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json |   26 +
 ...ID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md |   18 +
 ...-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json |   26 +
 ...ID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md |   55 +
 ...-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json |   26 +
 ...ID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md |  102 ++
 ...-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json |   26 +
 ...ID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md |   55 +
 ...-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json |   26 +
 ...ID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md | 1018 ++++++++++++
 ...-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json |   26 +
 ...ID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md |    9 +
 ...-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json |   26 +
 ...ID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md |   13 +
 ...-CA96F723-CABE-4A23-AEAC-220BE12D2970.json |   26 +
 ...ID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md |    7 +
 ...-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json |   26 +
 ...ID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md |   51 +
 ...-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json |   26 +
 ...ID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md |   13 +
 ...-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json |   26 +
 ...ID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md |   12 +
 ...-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json |   26 +
 ...ID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md |  114 ++
 ...-CC1F0809-F068-41F6-853A-0033148C3436.json |   26 +
 ...ID-CC1F0809-F068-41F6-853A-0033148C3436.md |   20 +
 ...-CCC7880B-8316-4FDD-91D6-9680671E23D9.json |   26 +
 ...ID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md |  185 +++
 ...-CD1058AC-228F-424E-A2B0-45B93F4C582F.json |   26 +
 ...ID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md |   51 +
 ...-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json |   26 +
 ...ID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md |  358 +++++
 ...-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json |   26 +
 ...ID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md |   33 +
 ...-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json |   26 +
 ...ID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md |  204 +++
 ...-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json |   26 +
 ...ID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md |  113 ++
 ...-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json |   26 +
 ...ID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md |   11 +
 ...-CFE82665-23A3-49F2-9202-1C2A720CC64D.json |   26 +
 ...ID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md |   10 +
 ...-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json |   26 +
 ...ID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md |    6 +
 ...-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json |   26 +
 ...ID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md |   41 +
 ...-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json |   26 +
 ...ID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md |   25 +
 ...-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json |   26 +
 ...ID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md |   12 +
 ...-D3100235-F327-4C00-9AF8-F5C974D2F698.json |   26 +
 ...ID-D3100235-F327-4C00-9AF8-F5C974D2F698.md |   13 +
 ...-D3548220-4D77-4DBB-8313-CFAD68416264.json |   26 +
 ...ID-D3548220-4D77-4DBB-8313-CFAD68416264.md |   30 +
 ...-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json |   26 +
 ...ID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md |   59 +
 ...-D47A61E0-1F97-4E09-A62C-C8B990640F56.json |   26 +
 ...ID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md |   28 +
 ...-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json |   26 +
 ...ID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md |   14 +
 ...-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json |   26 +
 ...ID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md |    5 +
 ...-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json |   26 +
 ...ID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md |   13 +
 ...-D63E4175-CA68-4648-B912-F20796292DD3.json |   26 +
 ...ID-D63E4175-CA68-4648-B912-F20796292DD3.md |   52 +
 ...-D7A36529-C624-486D-8C0E-FA69A4DC4014.json |   26 +
 ...ID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md |    9 +
 ...-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json |   26 +
 ...ID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md |   86 ++
 ...-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json |   26 +
 ...ID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md |  230 +++
 ...-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json |   26 +
 ...ID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md |  143 ++
 ...-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json |   26 +
 ...ID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md |  150 ++
 ...-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json |   26 +
 ...ID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md |    7 +
 ...-DA1898BD-3EB1-432A-BD34-373B29B05B89.json |   26 +
 ...ID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md |   83 +
 ...-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json |   26 +
 ...ID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md |   28 +
 ...-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json |   26 +
 ...ID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md |   16 +
 ...-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json |   26 +
 ...ID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md |   53 +
 ...-DB2EE423-511B-432B-8425-82326DC29158.json |   26 +
 ...ID-DB2EE423-511B-432B-8425-82326DC29158.md |   24 +
 ...-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json |   26 +
 ...ID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md |   23 +
 ...-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json |   26 +
 ...ID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md |   21 +
 ...-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json |   26 +
 ...ID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md |    7 +
 ...-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json |   26 +
 ...ID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md |  132 ++
 ...-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json |   26 +
 ...ID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md |   14 +
 ...-DD626086-0E0C-460D-85BC-8E654BEEF70A.json |   26 +
 ...ID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md |   17 +
 ...-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json |   26 +
 ...ID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md |   15 +
 ...-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json |   26 +
 ...ID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md |    3 +
 ...-DE4B3C05-2C42-42E8-849A-B13E77080955.json |   26 +
 ...ID-DE4B3C05-2C42-42E8-849A-B13E77080955.md |   11 +
 ...-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json |   26 +
 ...ID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md |   75 +
 ...-DED3B0BE-A491-472F-B40B-A08F64835F17.json |   26 +
 ...ID-DED3B0BE-A491-472F-B40B-A08F64835F17.md |  150 ++
 ...-DF02CF23-8387-4D00-87AF-5F2054075F18.json |   26 +
 ...ID-DF02CF23-8387-4D00-87AF-5F2054075F18.md |   68 +
 ...-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json |   26 +
 ...ID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md |   53 +
 ...-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json |   26 +
 ...ID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md |  160 ++
 ...-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json |   26 +
 ...ID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md |  159 ++
 ...-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json |   26 +
 ...ID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md |   28 +
 ...-E012A526-E6C4-408D-A69C-AD7BC08B882C.json |   26 +
 ...ID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md |   63 +
 ...-E01FA212-4E9E-4403-9508-E4BB971643A3.json |   26 +
 ...ID-E01FA212-4E9E-4403-9508-E4BB971643A3.md |  203 +++
 ...-E02DD704-C987-41BB-AF3F-A23F35C097BD.json |   26 +
 ...ID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md |   27 +
 ...-E04CE9DF-E832-41CB-B559-1800B7943A2F.json |   26 +
 ...ID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md |   65 +
 ...-E1159A9B-4A53-400A-A1E7-8604539EB39D.json |   26 +
 ...ID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md |   11 +
 ...-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json |   26 +
 ...ID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md |    7 +
 ...-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json |   26 +
 ...ID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md |   37 +
 ...-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json |   26 +
 ...ID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md |   92 ++
 ...-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json |   26 +
 ...ID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md |    7 +
 ...-E3911F3D-F635-42FA-B014-078FD60D3130.json |   26 +
 ...ID-E3911F3D-F635-42FA-B014-078FD60D3130.md |   23 +
 ...-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json |   26 +
 ...ID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md |   14 +
 ...-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json |   26 +
 ...ID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md |   49 +
 ...-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json |   26 +
 ...ID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md |  117 ++
 ...-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json |   26 +
 ...ID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md |   31 +
 ...-E55D4270-ED77-4161-8712-45824C891713.json |   26 +
 ...ID-E55D4270-ED77-4161-8712-45824C891713.md |   38 +
 ...-E5C429F5-9F57-481D-968A-64793E86EBCE.json |   26 +
 ...ID-E5C429F5-9F57-481D-968A-64793E86EBCE.md |   34 +
 ...-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json |   26 +
 ...ID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md |   15 +
 ...-E6C2AF29-A549-4B96-A778-039FC445D7F2.json |   26 +
 ...ID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md |    3 +
 ...-E748BC6D-7E45-4324-A174-9FB2012CBA27.json |   26 +
 ...ID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md |   13 +
 ...-E7DD5576-68E3-449D-8606-D2861BF53808.json |   26 +
 ...ID-E7DD5576-68E3-449D-8606-D2861BF53808.md |   12 +
 ...-E816369D-52FD-43B2-88F6-A5F748829203.json |   26 +
 ...ID-E816369D-52FD-43B2-88F6-A5F748829203.md |   10 +
 ...-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json |   26 +
 ...ID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md |   16 +
 ...-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json |   26 +
 ...ID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md |   48 +
 ...-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json |   26 +
 ...ID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md |   20 +
 ...-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json |   26 +
 ...ID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md |   18 +
 ...-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json |   26 +
 ...ID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md |   27 +
 ...-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json |   26 +
 ...ID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md |   11 +
 ...-EC91E230-8323-4710-9A47-D57A15BE71AA.json |   26 +
 ...ID-EC91E230-8323-4710-9A47-D57A15BE71AA.md |  191 +++
 ...-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json |   26 +
 ...ID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md |    8 +
 ...-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json |   26 +
 ...ID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md |  423 +++++
 ...-ED404402-F168-4635-ADEB-02609465196E.json |   26 +
 ...ID-ED404402-F168-4635-ADEB-02609465196E.md |   20 +
 ...-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json |   26 +
 ...ID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md |   19 +
 ...-EF20CD89-B756-4F84-BC6A-55B2488B5947.json |   26 +
 ...ID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md |   46 +
 ...-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json |   26 +
 ...ID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md |   13 +
 ...-F003BCEE-0E64-412A-9045-295910E15A5A.json |   26 +
 ...ID-F003BCEE-0E64-412A-9045-295910E15A5A.md |  133 ++
 ...-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json |   26 +
 ...ID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md |    3 +
 ...-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json |   26 +
 ...ID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md |   53 +
 ...-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json |   26 +
 ...ID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md |    9 +
 ...-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json |   26 +
 ...ID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md |  328 ++++
 ...-F6459690-0DE9-48CE-95B2-C7BE033E8088.json |   26 +
 ...ID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md |   19 +
 ...-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json |   26 +
 ...ID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md |    4 +
 ...-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json |   26 +
 ...ID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md |   18 +
 ...-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json |   26 +
 ...ID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md |   37 +
 ...-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json |   26 +
 ...ID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md |  231 +++
 ...-F7C9EB98-701B-4C51-966C-3448AF3575AF.json |   26 +
 ...ID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md |   26 +
 ...-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json |   26 +
 ...ID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md |   80 +
 ...-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json |   26 +
 ...ID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md |  114 ++
 ...-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json |   26 +
 ...ID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md |  189 +++
 ...-FBA4AD60-9130-49BD-B10F-074439138A4B.json |   26 +
 ...ID-FBA4AD60-9130-49BD-B10F-074439138A4B.md |   13 +
 ...-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json |   26 +
 ...ID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md |   14 +
 ...-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json |   26 +
 ...ID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md |   17 +
 ...-FE7CCD11-6021-491F-BC50-596DA68F9206.json |   26 +
 ...ID-FE7CCD11-6021-491F-BC50-596DA68F9206.md |   13 +
 ...-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json |   26 +
 ...ID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md |   56 +
 ...-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json |   26 +
 ...ID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md |   30 +
 ...-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json |   26 +
 ...ID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md |  111 ++
 ...-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json |   26 +
 ...ID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md |   25 +
 3199 files changed, 167272 insertions(+)
 create mode 100644 corpus/.digest/history.jsonl
 create mode 100644 corpus/morpheus_quickspecs/a50009231enw.json
 create mode 100644 corpus/morpheus_quickspecs/a50009231enw.md
 create mode 100644 corpus/morpheus_release_notes_8_1_0/sd00007496en_us.json
 create mode 100644 corpus/morpheus_release_notes_8_1_0/sd00007496en_us.md
 create mode 100644 corpus/morpheus_release_notes_8_1_1/sd00007610en_us.json
 create mode 100644 corpus/morpheus_release_notes_8_1_1/sd00007610en_us.md
 create mode 100644 corpus/morpheus_release_notes_8_1_2/sd00007733en_us.json
 create mode 100644 corpus/morpheus_release_notes_8_1_2/sd00007733en_us.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
 create mode 100644 corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md

diff --git a/corpus/.digest/history.jsonl b/corpus/.digest/history.jsonl
new file mode 100644
index 0000000..e69de29
diff --git a/corpus/morpheus_quickspecs/a50009231enw.json b/corpus/morpheus_quickspecs/a50009231enw.json
new file mode 100644
index 0000000..636f058
--- /dev/null
+++ b/corpus/morpheus_quickspecs/a50009231enw.json
@@ -0,0 +1,12 @@
+{
+  "bundle_id": "morpheus_quickspecs",
+  "page_id": "a50009231enw",
+  "title": "HPE Morpheus Enterprise Software QuickSpecs",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "a50009231enw",
+  "version": "v1",
+  "product": "QuickSpecs",
+  "source_url": "https://www.hpe.com/psnow/doc/a50009231enw",
+  "fetched_from": "live"
+}
diff --git a/corpus/morpheus_quickspecs/a50009231enw.md b/corpus/morpheus_quickspecs/a50009231enw.md
new file mode 100644
index 0000000..6bc706b
--- /dev/null
+++ b/corpus/morpheus_quickspecs/a50009231enw.md
@@ -0,0 +1,111 @@
+**In an era of digital transformation, speed and agility of application modernization is key to success.**
+
+Unfortunately, it can take IT weeks to deliver new application stacks when requested because of manual hand-offs across a fragmented set of ‘software-definable’ technologies on-premises. This inefficiency has led internal IT consumers to often bypass IT in favor of public cloud application services which raises cloud costs and opens security holes.
+
+Born to provide simple and consistent provisioning of VMs, Containers, and Applications into any private or public cloud, HPE Morpheus Enterprise Software enables IT to become a true internal service provider for the business. It brings the cloud experience on-premises, extends governance to the public clouds, and bridges the gaps between technology, people, and process.
+
+### Overview
+
+HPE Morpheus Enterprise Software was uniquely engineered for platform engineering; it enables different enterprise teams to each get what they need from hybrid cloud management. IT and platform teams can quickly integrate tooling and dependencies without scripting, standardize cloud management, simplify server builds, and automate lifecycle tasks. Infrastructure and security teams can connect third-party identity providers, map groups & roles, establish role-based access controls, enforce policies, manage and rotate secrets, and more. Development teams, data analytics professionals, and other IT users, get on-demand provisioning of application services and stacks consistently across runtimes and clouds via GUI, ITSM plugin, IaC provider, full API/CLI, and CI/CD pipelines. Lastly, Managed Service Providers can use HPE Morpheus Enterprise as a white-labeled and multi-tenant portal to provide services and meter usage to be used in customer billing.
+
+![image](https://assets.ext.hpe.com/is/image/hpedam/a50009231enw_block1img?$crimg$ "image")
+
+### Standard Features
+
+#### Features
+
+**Enable Self-service Provisioning of any Workload into any Cloud On-demand**
+
+- − Integrate Hypervisors, Public Clouds, Kubernetes Clusters, IP address management, DNS, Load Balancers, IT Service Management, Backup Tools, Automation Tasks, and more into framework to automate workload deployment.
+- − Turn existing 'brownfield' hypervisors into a true private cloud by easily connecting to VMware, Nutanix, Microsoft, Oracle, OpenStack, etc. Unify public cloud access by connecting to AWS, Azure, GCP, OCI, etc.
+- − Eliminate manual handoffs and orchestrate the tools and dependencies for catalog-based deployment of Bare Metal (BMaaS), VMs (IaaS / VMaaS), containers (CaaS), App Services (PaaS), multi-tier application stacks, and public cloud services.
+- − Associate automation tasks to the lifecycle phases of workloads so IT processes can be consistently applied at startup, shutdown, reconfigure, teardown, etc. Task support includes Ansible, Chef, Salt, PowerShell, Bash, and more.
+- − Trigger provisioning activities through your interface of choice including a simple self-service catalog GUI, powerful advanced GUI interface, full fidelity API/CLI for integration into CI/CD pipelines, or leverage ITSM tools such as ServiceNow®.
+
+**Provision Built-in KVM and Kubernetes Runtime Options for Flexibility and Choice**
+
+- − Deploy and manage HPE's HVM hypervisor clusters. Based on KVM, this built-in runtime includes external storage support, VM live migration, storage live migration, data protection, and other features to host virtualized workloads.
+- − Use the built-in CNCF certified Kubernetes Service (HKS) to deploy K8s on any attached cloud. Includes open-source components such as Prometheus, Grafana, Calico and others to quickly get started with containers.
+- − Create custom K8s cluster layouts to deploy distributions such as Rancher’s K3s, Red Hat OpenShift, or vanilla upstream K8s as well as enable provisioning of cloud-managed Kubernetes clusters like AWS EKS, Azure AKS and Google GKE.
+- − Quickly view status and health of VME and Kubernetes clusters across your environment to simplify operations, view cluster metrics and logs, and provide lifecycle management of HPE native VME and HKS cluster types.
+
+**Set Governance Guardrails so Users and Teams have a Paved Road to Hybrid Cloud**
+
+- − Govern tenants, teams, and users by connecting to corporate identity providers and using SSO. Map groups and users into fine-grained role-based access control (RBAC) guardrails with dozens of policies for infrastructure and lifecycle.
+- − Improve your overall security posture by ensuring consistent golden template use, embedding security agents at provision time, locking down access, rotating credentials, managing secrets, and auditing all activity.
+- − Utilize multi-tenancy to fully segregate which teams and users have access to different cloud environments. Share hypervisors and clouds across multiple tenants or let tenants have their own individual cloud accounts.
+
+**Embrace FinOps and Lower Cost with Cross Cloud Visibility and Insight**
+
+- − Automatically discover and inventory existing instances and objects across all private and public clouds, run analytics to find problems and implement guidance recommendations for cloud cost saving.
+- − Go beyond reporting to fix cost issues at their source. Set budget guardrails and power schedules, limit clouds and plans by role, plus provide cloud cost comparisons at provision time for end-user empowerment.
+- − Centralize cost and usage data across on-premises and public cloud. Track costs and usage for every tenant, user, group, tag, app, cloud, and more for private infrastructure and public cloud including public cloud invoice synchronization.
+
+For a complete set of up-to-date technical information and integration guides please visit the:
+
+[HPE Morpheus Enterprise documentation](https://docs.morpheusdata.com/en/latest) site.
+
+### Configuration Information
+
+#### Architecture and Requirements
+
+HPE Morpheus Enterprise is a software-based appliance installation capable of orchestrating many clouds and hypervisors. Before an installation is started it is important to understand some of the base requirements. HPE Morpheus Enterprise provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability configuration, either in the same region or cross-region.
+
+There are four primary tiers of services represented within the Morpheus appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Message Tier. Each of these tiers have their own recommendations for High availability deployments that we need to cover.
+
+**Configuration options:**
+
+- − Single Host (All-In-One/default): All tiers running on a single host. The reconfigure process installs all required services. This is the default configuration.
+- − Single Hosts with Distributed Service(s): Transactional Database, Non-Transactional Database, and/or Message tiers are externalized, with the remaining services on a single host.
+- − Clustered Hosts with Distributed Transactional Database (3-Node HA): Application, Message and Non-Transactional tiers are installed and clustered on three or more hosts, with all three hosts pointing to externalized database tier.
+- − App Host(s) with Distributed Services (Full HA): Application tier is installed on one or more hosts. All UI hosts point to externalized Transactional Database, Non-Transactional Database, and Message Tiers.
+
+Additional configuration detail available at the [HPE Morpheus Enterprise documentation](https://docs.morpheusdata.com/en/latest/getting_started/getting_started.html) site.
+
+#### Product, Services, and Licensing Considerations
+
+Hewlett Packard Enterprise is making the following HPE Morpheus Enterprise Software SKUs available as term-based licensed software, not a fully managed SaaS deployment. This makes HPE Morpheus Enterprise an excellent choice for highly regulated environments with tight security guidelines.
+
+HPE Morpheus Enterprise Software SKUs are licensed per physical CPU socket for any connected on-premises cloud including Bare Metal (BMaaS) servers, hypervisor hosts, and Kubernetes worker nodes.
+
+HPE Morpheus Enterprise Software can also be used to provision workloads into public clouds like AWS, Azure, GCP, and more; public cloud workloads are factored at a 15 workload to 1 socket ratio. For example, 15 AWS EC2 instances would consume 1 socket license.
+
+New installations require installation and configuration services provided by HPE. All software licenses for HPE Morpheus Enterprise include 24x7 support in the form of HPE Tech Care Essentials as part of the license cost. HPE also highly recommends that customers attend the HPE Morpheus Enterprise – Administration training class to fully take advantage of the capabilities of the platform.
+
+You can upgrade from HPE Morpheus VM Essentials to the full capabilities of HPE Morpheus Enterprise using the upgrade options below. Upgrade licenses can be applied to an existing installation however you should consult with HPE on any suggested architectural considerations. You can also apply additional licenses to an existing installation and ‘stack’ licenses with differing term lengths.
+
+|  |  |
+| --- | --- |
+| HPE Morpheus Enterprise Software | |
+| **Description** | **SKU** |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 1-year 24x7 Support New Install E-LTU | S6E64AAE |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 3-year 24x7 Support New Install E-LTU | S6E66AAE |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 5-year 24x7 Support New Install E-LTU | S6E68AAE |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 1-year 24x7 Support Extension/Renewal E-LTU | S6E59AAE |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 3-year 24x7 Support Extension/Renewal E-LTU | S6E61AAE |
+| HPE Morpheus Enterprise Software per Socket (15 WLE) 5-year 24x7 Support Extension/Renewal E-LTU | S6E63AAE |
+| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 1-year 24x7 Support E-LTU | S6E69AAE |
+| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 3-year 24x7 Support E-LTU | S6E71AAE |
+| HPE Morpheus VM Essentials to Morpheus Enterprise Software Upgrade 5-year 24x7 Support E-LTU | S6E73AAE |
+| **HPE Morpheus Services** | |
+| **Description** | **SKU** |
+| HPE Morpheus Software Installation - standard | HA124A1#V38 |
+| HPE Morpheus Software High Availability - enhancement | HA124A1#V39 |
+| HPE Morpheus Enterprise SW Quickstrt SVC | H46SBA1 |
+| **Notes:** For fully advanced services and custom statements of work, please work with the HPE Advisory and Professional Services (HPE A&PS) team. HPE A&PS have a full set of consulting and services focused on HPE Morpheus Software for multi-cloud management. <https://www.hpe.com/psnow/doc/a00141555enw> | |
+| **HPE Morpheus Training and Education** | |
+| **Description** | **SKU** |
+| HPE Morpheus Software – Administration | H45ZD |
+| HPE Morpheus Software - Automation & Advanced Provisioning | H45ZC |
+| HPE Morpheus Software - Advanced Troubleshooting | H45YY |
+| HPE Morpheus Software - Installation | H45YZ |
+
+### Summary of Changes
+
+| **Date** | **Version History** | **Action** | **Description of Change** |
+| --- | --- | --- | --- |
+| 16-Mar-2026 | [Version 3](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=3) | Changed | New product functionality and SKU information have been added. |
+| 22-Sep-2025 | [Version 2](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=2) | Changed | HPE Rebranding applied |
+| 05-May-2025 | [Version 1](https://www.hpe.com/psnow/doc/a50009231enw.pdf?ver=1) | New | New QuickSpecs |
+
+[Have feedback on QuickSpecs? We’re listening](https://hpeexperience.questionpro.com/t/mLrbZLrb?Inform=BotQuickSpecsa50009231enw)
diff --git a/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.json b/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.json
new file mode 100644
index 0000000..a2f33ae
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_release_notes_8_1_0",
+  "page_id": "sd00007496en_us",
+  "title": "v8.1.0 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007496en_us",
+  "version": "8.1.0",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007496en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.0 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_release_notes_8_1_1",
+        "page_id": "sd00007610en_us",
+        "clustering_title": "v8.1.1 Release Notes"
+      },
+      {
+        "bundle_id": "morpheus_release_notes_8_1_2",
+        "page_id": "sd00007733en_us",
+        "clustering_title": "v8.1.2 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.md b/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.md
new file mode 100644
index 0000000..ff6e3b1
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_0/sd00007496en_us.md
@@ -0,0 +1,75 @@
+# v8.1.0 Release Notes
+
+# v8.1.0 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.0
+- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.0 February 2026
+
+IMPORTANT
+
+Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
+
+IMPORTANT
+
+HPE Morpheus Enterprise Software version v8.1.0 does not support rolling upgrades. Consult [non-rolling upgrade documentation](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html) for upgrade process steps.
+
+IMPORTANT
+
+After upgrading to v8.1.0, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
+
+# New Features
+
+Alletra MP Plugin
+:   - For complete update details, see the [Alletra MP plugin release notes](https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007519en_us)
+
+Appliance
+:   - There is now a single binary installer for both HPE Morpheus Enterprise Software and HPE Morpheus VM Essentials Software. Feature access is controlled solely by licensing. Previously, HPE Morpheus Enterprise and HPE Morpheus VM Essentials had separate binary packages
+    - For newly-installed environments without a paid license configured, the evaluation period has been extended from 30 to 60 days
+
+Aruba CX Plugin
+:   - Version 1.9.0 of the plugin has been released
+    - The serial numbers and health status for each switch are now shown within the network tab of the integration detail
+    - Other internal improvements
+
+Aruba CX DSS Plugin
+:   - Version 1.5.0 of the plugin has been released
+    - Users may now specify a Policy Distribution Target (PDT) when creating a DSS port group
+
+HVM
+:   - Added vCPU placement (NUMA and L3 boundaries) control for HVM clusters
+
+Library
+:   - HPE Morpheus VM Essentials now includes a default library of example images that can be provisioned to HVM Clusters or integrated VMware Clouds right out of the box
+
+Security
+:   - Updates to internal dependency libraries to close potential security vulnerabilities
+
+Tenants
+:   - Storage volume detail pages now show the volume UUID
+
+# Fixes
+
+API & CLI
+:   - Datastores created via API now have the Tenant permissions given in the request payload
+    - Improved the efficiency of making calls to list instances (/api/instances) which, in some environments, could be slow to respond
+
+Bare Metal
+:   - Added various fixes and hardening improvements for the HPE Bare Metal Plugin (BMaaS). See the updated integration guide for complete information on plugin use and capabilities
+
+Google Cloud
+:   - When adding Security Groups, the dropdown menu now shows only Security Groups belonging to GCP rather than all Security Groups
+
+HVM
+:   - Fixed an issue that caused GFS2 to change to a read-only state when rebooting the HVM Host
+
+NSX
+:   - Adding NSX Firewall Rules from the Network section of an Instance detail now properly shows the special modal for creating NSX Firewall Rules rather than the generic modal for other Firewall Rule types. This is the same expected modal shown when creating NSX Firewall Rules from the integration detail
+
+Terraform
+:   - When applying Terraform state or taking other actions involving Terraform (ex. creating Catalog Items from Terraform Blueprints), decimal values ending in ".0" are no longer truncated (ex. 1.0 -> 1)
+
+Published: February 2026
diff --git a/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.json b/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.json
new file mode 100644
index 0000000..1c12303
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_release_notes_8_1_1",
+  "page_id": "sd00007610en_us",
+  "title": "v8.1.1 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007610en_us",
+  "version": "8.1.1",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007610en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.1 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_release_notes_8_1_0",
+        "page_id": "sd00007496en_us",
+        "clustering_title": "v8.1.0 Release Notes"
+      },
+      {
+        "bundle_id": "morpheus_release_notes_8_1_2",
+        "page_id": "sd00007733en_us",
+        "clustering_title": "v8.1.2 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.md b/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.md
new file mode 100644
index 0000000..bc05a82
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_1/sd00007610en_us.md
@@ -0,0 +1,51 @@
+# v8.1.1 Release Notes
+
+# v8.1.1 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.3
+- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.1 March 2026
+
+IMPORTANT
+
+Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
+
+IMPORTANT
+
+HPE Morpheus Enterprise Software version v8.1.1 does not support rolling upgrades. Consult [non-rolling upgrade documentation](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html) for upgrade process steps.
+
+IMPORTANT
+
+After upgrading to v8.1.1, it is required to also upgrade HVM Host agents as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host.
+
+# New Features
+
+Aruba CX DSS Plugin
+:   - Updated the add/edit DSS port group modal to allow users to select one or more security groups
+    - Renamed "Default Firewall Policy" field to "Firewall"
+    - Users may now (optionally) make a Security Group selection for DSS Port Groups
+
+Catalog
+:   - Added CentOS 10 Stream image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Debian 13 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Alma Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+    - Added Rocky Linux 10 image templates for many supported Cloud types (HVM, VMware, Nutanix Element, Nutanix Central, OpenStack, and more)
+
+HVM
+:   - HVM Host hardware sensor data can now be surfaced into the UI. See HVM cluster documentation for details on configuring hosts to gather and surface this data
+
+# Fixes
+
+Bare Metal
+:   - Fixed provisioning failures when bare metal Instances are provisioned with default unmanaged networks using static IP addresses
+
+Instances
+:   - Fixed manually added VMs, converted to managed, still appearing as discovered
+
+Migrations
+:   - Fixed OVA export timeouts in vCenter which were left even after successful migrations
+
+Published: March 2026
diff --git a/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.json b/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.json
new file mode 100644
index 0000000..5d682d8
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_release_notes_8_1_2",
+  "page_id": "sd00007733en_us",
+  "title": "v8.1.2 Release Notes",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007733en_us",
+  "version": "8.1.2",
+  "product": "Release Notes",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007733en_us",
+  "topic_cluster": {
+    "clustering_title": "v8.1.2 Release Notes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_release_notes_8_1_0",
+        "page_id": "sd00007496en_us",
+        "clustering_title": "v8.1.0 Release Notes"
+      },
+      {
+        "bundle_id": "morpheus_release_notes_8_1_1",
+        "page_id": "sd00007610en_us",
+        "clustering_title": "v8.1.1 Release Notes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.md b/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.md
new file mode 100644
index 0000000..236b947
--- /dev/null
+++ b/corpus/morpheus_release_notes_8_1_2/sd00007733en_us.md
@@ -0,0 +1,77 @@
+# v8.1.2 Release Notes
+
+# v8.1.2 LTS Release Notes
+
+- Compatible Plugin API version: 1.3.4
+- Compatible HPE Morpheus Enterprise Software Worker version: 5.4.8+
+
+Release Dates
+
+- v8.1.2 April 2026
+
+IMPORTANT
+
+Beginning with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. This change only affects HPE Morpheus Enterprise Software as HPE Morpheus VM Essentials already uses OpenSearch. HPE continues to support both ElasticSearch and OpenSearch for external clusters. Consult [this section](https://support.hpe.com/hpesc/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html) of the user manual for upgrade, migration, and configuration details.
+
+IMPORTANT
+
+Not all HPE Morpheus Enterprise Software upgrade version hops support rolling upgrades. Consult the upgrade table contained within our upgrade documentation for rolling upgrade compatibility information. Then, select the upgrade process steps relevant to your environment and planned upgrade hop.
+
+IMPORTANT
+
+After upgrading to v8.1.2, it is recommended to check for HVM Host agent upgrades as well. To upgrade HVM Host agents, navigate to the detail page for each HVM Host, expand the ACTIONS menu, and click "Upgrade Agent." This process must be undertaken on all HVM Hosts. Alternatively, you may select "Download Agent Script" to download a shell script to handle the upgrade. Connect to the HVM Host over a terminal session and run the downloaded script. The scripts are unique to each HVM Host so you must download all required scripts and run the correct script against the correct HVM Host. Though many do, it is possible that some version upgrade hops will not contain an HVM Host agent upgrade.
+
+# New Features
+
+Localization
+:   - Added support for the Japanese keyboard layout (101/102 hardware) on hypervisor console sessions using the HPE Morpheus key extension (VMware, vCD, and HVM/KVM). It also includes a new keyboard tips pop-over in the console UI ("?" button). Japanese keyboard layout on 106/109 hardware is a planned future enhancement
+
+# Fixes
+
+API & CLI
+:   - Errors are no longer returned when sending valid DELETE calls to `/api/clusters/{cluster_id}/servers/{server_id}`
+    - Added missing parameters to the return payload received when sending a `GET` call to the `/api/apps endpoint`
+    - Instance resizes to add or remove network interfaces (`PUT /api/instances/{id}/resize`) on HVM or VMware Instances no longer return success messages without actually changing the network interface(s)
+
+Catalog
+:   - Fixed certain Catalog items getting stuck in a pending state indefinitely regardless of the success or failure of provisioning
+
+HVM
+:   - Fixed VM clones failing when the storage datastore type was changed (ex. local storage to Alletra plugin storage) from the original VM to the clone VM
+    - After restoring a VM from SimpliVity backup and successfully reconfiguring the restored VM, it can now be powered on successfully
+    - HVM Hosts will no longer fail to enter maintenance mode when a VM being live migrated to another Host transitions to a shut off state during migration
+    - Fixed an issue where certain maintenance mode sequences could cause HVM hosts to go offline or become fenced
+    - Disabling networks (unmarking the Active checkbox and saving) will no longer cause spontaneous changes to the "Enable IPV4" and/or the "DHCP Server" checkboxes on the next edit
+    - Volume attach/detach operations on VirtIO controllers no longer fail when attempted while snapshots are in progress
+    - Fixed intermittent provisioning failures when multiple VMs are simultaneously provisioned using the copy operation
+    - Fixed AltGR key input for HVM console sessions
+
+Invoices
+:   - The method used to purge old invoices now interprets the "Invoice Retainment" value set in Morpheus global settings to be defined in months (as the UI indicates) rather than days, which led to unintended early data purges
+
+Kubernetes
+:   - Updating worker node counts for Azure AKS clusters now works properly
+
+Labels
+:   - Fixed Cloud filtering by Label for Clouds shared down to child Tenants from a parent Tenant
+
+NSX
+:   - When NSX segments are shared across multiple clusters in a VDC, Morpheus can now associate the NSX segment with multiple vCenter segments
+
+OLVM
+:   - Fixed Oracle Linux Virtualization Manager (OLVM) image sync to Morpheus
+
+Plugins
+:   - The Upcloud Cloud-type integration has been ported to a plugin. Appliances not already using this integration must download the plugin and add it to the HPE Morpheus Software appliance
+    - The ESXi Cloud-type integration has been ported to a plugin. Appliances not already using this integration must download the plugin and add it to the HPE Morpheus Software appliance
+
+SCVMM
+:   - Clone actions performed on SCVMM Instances discovered and converted to managed now can be completed successfully
+
+Security
+:   - Added security enhancements
+
+Virtual Images
+:   - Creating Windows VMs with static IP addresses when cloudinit (Cloudbase-init) is set on the Virtual Image now works
+
+Published: April 2026
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json b/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
new file mode 100644
index 0000000..c4c160a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+  "title": "SSL Self-signed Certificate Regeneration",
+  "ordinal": 355,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Self-signed Certificate Regeneration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md b/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
new file mode 100644
index 0000000..0099ff5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
@@ -0,0 +1,19 @@
+# SSL Self-signed Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year self-signed non-trusted SSL certificate. Below details the process to regenerate this certificate and key.
+
+## Replacing both the certificate and private key
+
+### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/` that end in `.crt` and `.key`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
+
+## Replacing only the certificate
+
+### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/` it ends in `.crt`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json b/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
new file mode 100644
index 0000000..f06dac7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+  "title": "Settings",
+  "ordinal": 320,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md b/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
new file mode 100644
index 0000000..966fadc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
@@ -0,0 +1,18 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the HPE Morpheus Enterprise appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for HPE Morpheus Enterprise itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Whitelabel](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html)**
+- **[Email Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5_2.html)**
+- **[Clients](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[Software Licenses](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json b/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
new file mode 100644
index 0000000..b53b254
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+  "title": "Load Balancers",
+  "ordinal": 226,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md b/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
new file mode 100644
index 0000000..48b3886
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
@@ -0,0 +1,88 @@
+# Load Balancers
+
+The Load Balancers tab list currently available Load Balancers, which you can select, edit or delete, and is where you can create new or integrate with external Load Balancers.
+
+## Configuration parameters to add a new load balancer
+
+Following parameters are required configure the respective load balancers:
+
+Amazon ALB
+:   - Scheme
+    - Internal
+    - Internet-Facing
+    - Amazon Subnets (Select + to add additional) \* Specify the subnets to enable for your load balancer. You can specify only one subnet per Availability Zone. You must specify subnets from at least two Availability Zones to increase the availability of your load balancer.
+    - Amazon Security Groups (Select + to add additional)
+
+      For details, see [Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html).
+
+Azure load balancer
+:   - Cloud
+    - Resource Group \* Populated from cloud selection
+
+      For details, see [Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html).
+
+Citrix NetScaler
+:   - API Host
+    - API Port
+    - Username
+    - Password
+
+      For details, see [Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html).
+
+F5 BigIP (v11.4+)
+:   - API Host
+    - API Port
+    - Username
+    - Password
+    - Management URL
+
+      For details, see [Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html).
+
+FortiADC
+:   - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - INTERFACE (synced on auth)
+
+      For details, see [Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html).
+
+HaProxy Container (Internal, will create a HaProxy container, must have available docker host to provision to)
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - Plan \* Select the size of HaProxy container to be provisioned
+
+      For details, see [Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html).
+
+NSX load balancer
+:   - NSX
+    - Name
+    - Description
+    - Enabled
+    - Admin State
+    - Size
+    - Tier-1 Gateways
+    - Log Level
+
+      For details, see [Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html).
+
+NSX Advanced load balancer
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - AVI CLOUD
+
+      For details, see [Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html).
+
+Upon saving, your new load balancer will be added to the load balancers list and available in the load balancer drop-down list under the Provisioning Wizard Automation Section for Instance Types that have scaling enabled.
+
+### Load Balancer Detail Pages
+
+In the main Load Balancer page, select an existing Load Balancer to go to that Load Balancers Details Page, which lists Stats, Settings, Actions and Virtual Servers for that load balancer.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json b/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
new file mode 100644
index 0000000..e234152
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+  "title": "Ansible Troubleshooting",
+  "ordinal": 345,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md b/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
new file mode 100644
index 0000000..c004156
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
@@ -0,0 +1,52 @@
+# Ansible Troubleshooting
+
+When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in UI logs at `/var/log/morpheus/morpheus-ui/current​`. These can be tailed by running `morpheus-ctl tail morpheus-ui`.
+
+## Verify Ansible is installed on the HPE Morpheus Enterprise Appliance
+
+Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+### If Ansible is not installed
+
+Follow these instructions to install, or use your preferred installation method
+
+Ubuntu:
+
+```
+```
+sudo apt-get install software-properties-common  
+sudo apt-add-repository ppa:ansible/ansible  
+sudo apt-get update  
+sudo apt-get install ansible python-requests
+```
+```
+
+CentOS:
+
+```
+```
+sudo yum install epel-release  
+sudo yum install ansible python-requests
+```
+```
+
+Then create the working Ansible directory for Morpheus:
+
+```
+```
+sudo mkdir /opt/morpheus/.ansible  
+sudo chown morpheus-app.morpheus-app /opt/morpheus/.ansible
+```
+```
+
+## Validate Git repo authorization and the configured paths
+
+The public and private SSH keys need to be added to the HPE Morpheus Enterprise appliance via Infrastructure  >  Keys & Certs and the public key needs to be added to the Git repo via user settings. If both are set up correctly, you will see the playbooks and roles populate in the Ansible Integration details page.
+
+The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+
+When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+
+NOTE
+
+If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json b/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
new file mode 100644
index 0000000..8e5fac9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+  "title": "Provisioning a New Server",
+  "ordinal": 414,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a New Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md b/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
new file mode 100644
index 0000000..a47de79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
@@ -0,0 +1,9 @@
+# Provisioning a New Server
+
+Provisioning a new server allows onboarding new, unmanaged HPE ProLiant servers into a Bare Metal Cloud environment, enabling HPE Morpheus to manage their lifecycle, including automated OS deployment and hardware monitoring.
+
+**Subtopics**  
+
+- **[Importing HPE ProLiant Bare Metal Servers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html)**
+- **[Provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html)**
+- **[Post-Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json b/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
new file mode 100644
index 0000000..f035cfc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+  "title": "CyberArk Conjur",
+  "ordinal": 525,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html",
+  "topic_cluster": {
+    "clustering_title": "CyberArk Conjur",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md b/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
new file mode 100644
index 0000000..cd010fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
@@ -0,0 +1,63 @@
+# CyberArk Conjur
+
+HPE Morpheus Enterprise supports integration with CyberArk Conjur for stored credential sets as well utilization of Conjur-stored secret values via HPE Morpheus Enterprise Cypher service. This works identically to built-in credential storage and built-in Cypher functionality with the exception that your Conjur server is the storage backend rather than the HPE Morpheus Enterprise appliance itself. In some cases, this may help to consolidate secret management into one central place or it even may be a requirement to satisfy internal security policies at some organizations.
+
+CyberArk Conjur integration is not included with HPE Morpheus Enterprise out of the box. It is developed as an official plugin and may be applied to any HPE Morpheus Enterprise appliance that needs it. See the HPE Morpheus Enterprise plugin repository website for access to the latest version of the plugin.
+
+## Applying the Plugin
+
+The latest version of the CyberArk Conjur plugin is available at the HPE Morpheus Enterprise [plugin share site](https://share.morpheusdata.com/). Select the pane for the correct plugin and click the DOWNLOAD button. The plugin JAR file will be downloaded to the local computer you’re working on.
+
+![../../_images/share.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C8A10069-9604-4478-904C-F916186AB33E-high.png)
+
+With the plugin downloaded, head back to HPE Morpheus Enterprise to apply the plugin to your appliance. Plugins are added by navigating to Administration > Integrations > Plugins and clicking ADD. Drop the plugin JAR file onto the target and click UPLOAD. It may take a few moments for the plugin to be applied successfully and for the modal to be dismissed after clicking the upload button.
+
+![../../_images/addPlugin.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ED50E88D-DE3D-419D-9071-B86CFBFD5BDD-high.png)
+
+Once the plugin is added, we configure the connection details here. Edit the new Conjur plugin by clicking the pencil (✎) icon from its row in the list. Configure the following fields:
+
+- **NAME:** A friendly name for the new integration to identify it within HPE Morpheus Enterprise
+- **ENABLED:** Mark the box to make this integration active and available
+- **CONJUR API URL:** The full URL for the Conjur server, usually listening on port 8443
+- **CONJUR USERNAME:** The Conjur user account you wish to authenticate with. This user should have read, write, and execute access to the variables configured within the Conjur policy
+- **CONJUR USERNAME API KEY:** The API key for user entered in the prior field
+- **CONJUR ORGANIZATION:** The Conjur account in which the user and variables reside
+- **CLEAR SECRET ON DELETION:** When marked, secret values will be cleared when deleted from HPE Morpheus Enterprise
+
+IMPORTANT
+
+Variables are predefined by Conjur policies. This integration does not allow users to create variables but does allow you to read and update their values. If the plugin is configured to clear secrets that are deleted from HPE Morpheus Enterprise, the variable value is updated with an empty value as there is no concept of fully deleting secrets in the Conjur API. If the plugin is configured not to clear secrets on deletion, the secret object is deleted from HPE Morpheus Enterprise without altering it on the Conjur backend.
+
+By applying and configuring the plugin, the appliance now has the Conjur/Cypher integration available. If you don’t intend to use the credential store integration, you can stop here and look ahead to the feature demonstration further ahead in this guide. If you do intend to use the credential store integration as well, there’s one additional configuration step to take in the next section.
+
+## Adding A Conjur Trust Integration
+
+In order to use Conjur with HPE Morpheus Enterprise credentials, we must also add a Conjur-type integration in Infrastructure > Trust > Integrations. By applying the plugin in the previous step, we now have the ability to add this type of integration. From the Trust integrations list page, click + ADD and select “Conjur.” It’s important to note that you **do not** need to again configure the API URL and Conjur login credentials as we just did in the previous step. You may configure them here if you wish, such as if you were making multiple integrations with multiple Conjur appliances, but if you’re simply integrating with the same appliance and user account, this is unnecessary. Simply give the new Trust integration a friendly name for reference in HPE Morpheus Enterprise and indicate the desired mount point for secrets you wish to consume as done in the screenshot below.
+
+NOTE
+
+In many cases, you don’t have to configure the connection details when adding a Conjur Trust integration. See the paragraph above.
+
+![../../_images/addTrustInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AE830924-B765-498F-98B6-154E38F1A4A5-high.png)
+
+## Conjur and Credential Stores
+
+With configurations completed, we can take a look at how HPE Morpheus Enterprise is able to interface with Conjur as a credential store. As mentioned at the beginning of this guide, variables are created by Conjur policies and not by HPE Morpheus Enterprise. We can reference existing variables and update the secret values stored within.
+
+As an example, there is a variable named `BotApp/secretVar` in the target Conjur appliance. When configuring the Trust integration (in the prior section), the `BotApp/` mount point was referenced (see the screenshot in the last section). When creating stored credential sets in HPE Morpheus Enterprise against this Conjur credential store, reference the rest of the variable path as the NAME value on the credential set. In this case, the credential set will be named `secretVar` to complete the `BotApp/secretVar` path as shown in the screenshot below. Be sure to also select Conjur as the CREDENTIAL STORE value rather than the default “Internal.”
+
+![../../_images/credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4DCB5DDF-130A-4847-912C-CAE31A96EDBE-high.png)
+
+After saving and going back to the Conjur appliance, the value stored at the referenced variable has been updated. This credential set is also available for use anywhere HPE Morpheus Enterprise allows users to utilize them, such as when integrating new Clouds, authenticating REST calls to populate Option Lists, and many other places.
+
+## Conjur and Cypher
+
+In addition to stored credential sets, the CyberArk Conjur plugin also enables integration with HPE Morpheus Enterprise Cypher. Just as calls can be made to internally-stored secret values with Cypher, Conjur variable endpoints may be referenced to onboard secret strings into automation Tasks.
+
+In the screenshot below, see a simple shell script Task which echoes out a secret value stored in Conjur. As you can see, the `conjur/` mount point is referenced along with the rest of the path to the variable which should be accessed. After executing the Task, we can check the execution history and see that the Conjur-stored value is indeed echoed back out.
+
+![../../_images/cypherTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DE2D6E0C-3988-42C1-8C27-2F31438CDED9-high.png)
+
+If desired, the value stored in Conjur could also be updated through the HPE Morpheus Enterprise Cypher UI. Navigate to Tools > Cypher and click + ADD. Note the `conjur` mount point is included in the example list of available mount points shown in the modal. By creating a new Cypher entry at the `conjur` mount point which references an existing Conjur variable path, the value in Conjur can be overwritten. If you’ve configured the plugin to clear secrets on deletion, you can also update the stored value with an empty string when you delete the Cypher object in HPE Morpheus Enterprise. For our example case, we could update the value in Conjur by creating a Cypher entry at the mount point `conjur/BotApp/secretVar`.
+
+![../../_images/cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F2FAE481-318A-42D8-A12B-D1904246CF52-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json b/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
new file mode 100644
index 0000000..505e1f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+  "title": "Utilities",
+  "ordinal": 330,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md b/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
new file mode 100644
index 0000000..cbda40a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places HPE Morpheus Enterprise into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting HPE Morpheus Enterprise UI disables maintenance mode.
+
+NOTE
+
+When using HPE Morpheus Enterprise in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A HPE Morpheus Enterprise node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json b/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
new file mode 100644
index 0000000..9303fde
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+  "title": "Storage",
+  "ordinal": 228,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md b/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
new file mode 100644
index 0000000..6c7aded
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
@@ -0,0 +1,14 @@
+# Storage
+
+NOTE
+
+In v3.5.2 STORAGE PROVIDERS has been split out into BUCKETS and FILE SHARES sections.
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html)**
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html)**
+- **[Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html)**
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html)**
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
new file mode 100644
index 0000000..051ff81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+  "title": "ARM Blueprints",
+  "ordinal": 132,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html",
+  "topic_cluster": {
+    "clustering_title": "ARM Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
new file mode 100644
index 0000000..53baef2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
@@ -0,0 +1,41 @@
+# ARM Blueprints
+
+ARM Blueprints provide a simple and repeatable way of deploying infrastructure-as-code to Azure Clouds. Objects and properties are defined in a JSON file and are provisionable on-demand in |ProApp|
+
+To create a new ARM Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select ARM. NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The ARM template itself is defined in the ARM Configuration section. Using the Config Type dropdown menu, we can opt to write or paste JSON configuration directly into this modal, or we can choose to bring in a JSON which we’re keeping under version control in a Git repository.
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+If writing or pasting your configuration JSON directly into the modal, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** ARM Template JSON (.json)
+- **CONFIG:** Your JSON configuration template
+
+If bringing in a template from a Git repository, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new ARM Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json b/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
new file mode 100644
index 0000000..db1f6ed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+  "title": "File Templates",
+  "ordinal": 160,
+  "parent_title": "Templates",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html",
+  "topic_cluster": {
+    "clustering_title": "File Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md b/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
new file mode 100644
index 0000000..d10d769
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
@@ -0,0 +1,60 @@
+# File Templates
+
+File Templates are for generating config files, such as my.cnf, opensearch.yml, morpheus.rb, or any text file. With full config map variable support, Template Files are dynamically generated during a Workflow phase or ad hoc via Instance actions.
+
+File Templates can also be exposed on Instances in the Settings Tab. Ensure the Instance Type supports settings, and Category is defined in Advance Options on the Library Template config.
+
+NOTE
+
+HPE Morpheus Enterprise variables are supported in Library Templates using `<%= variable.var %>` format
+
+Examples:
+
+HA Proxy Config (haproxy.cfg)
+
+- FILE NAME: haproxy.cfg
+- FILE PATH: /config/haproxy.cfg
+- PHASE: Pre Provision
+- TEMPLATE:
+- SETTING NAME: haproxyConfig
+- SETTING CATEGORY: haproxy
+
+```
+```
+#!/bin/bash  
+global  
+ maxconn 256  
+ log /dev/log local0 warning  
+ log-tag <%=logTag%>  
+defaults  
+ mode http  
+ timeout connect 5000ms  
+ timeout client 50000ms  
+ timeout server 50000ms  
+ log global  
+frontend http-in  
+ bind *:<%=container.externalPort%>  
+ default_backend servers  
+backend servers  
+ # server server1 127.0.0.1:80 maxconn 32
+```
+```
+
+mysql config (mysqld.cnf)
+
+- FILE NAME: mysqld.cnf
+- FILE PATH: /config/mysqld.cnf
+- PHASE: Pre Provision
+
+```
+```
+#!/bin/bash  
+[mysqld]  
+pid-file= /var/run/mysqld/mysqld.pid  
+socket= /var/run/mysqld/mysqld.sock  
+datadir= /var/lib/mysql  
+# Disabling symbolic-links is recommended to prevent assorted security risks  
+symbolic-links=0  
+explicit_defaults_for_timestamp = 1
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json b/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
new file mode 100644
index 0000000..cadfac1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+  "title": "DNS",
+  "ordinal": 482,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html",
+  "topic_cluster": {
+    "clustering_title": "DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md b/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
new file mode 100644
index 0000000..6989f60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
@@ -0,0 +1,7 @@
+# DNS
+
+**Subtopics**  
+
+- **[AWS Route53](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html)**
+- **[Microsoft DNS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html)**
+- **[PowerDNS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json b/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
new file mode 100644
index 0000000..924473c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+  "title": "Policy Types",
+  "ordinal": 318,
+  "parent_title": "Policies",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md b/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
new file mode 100644
index 0000000..3fadeb9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
@@ -0,0 +1,262 @@
+# Policy Types
+
+## Cypher Policies
+
+HPE Morpheus Enterprise allows administrators to set robust Cypher policies, which determine global, role, and/or specific user access to configured Cypher secret mount points. A number of considerations should be made when deploying Cypher Access policies, including how user role permissions will interact with the policy and how conflicts between overlapping policies are resolved.
+
+### Role Permissions
+
+User Role permissions (Administration > Roles) greatly affect Cypher access. Cypher access Role permissions are set from the Features tab of the selected Role under “Tools: Cypher”. The Role permission should be set based on the highest level of access to any one individual Cypher entry needed for the specific Role. For example, if the Role needs no access to any Cypher entries, set the feature permission to “None” and hide the Cypher UI from the Role completely. Alternatively, if the Role needs to use and decrypt even one Cypher entry, set the feature permission to “Full Decrypt”. The complete set of available permissions are below:
+
+- **NONE:** Cypher UI hidden
+- **READ:** Cypher UI present, entries can be listed
+- **USER:** Cypher UI present, user sees and can use their own entries, user can create new entries
+- **FULL:** Cypher UI present, user sees and can use all entries, user can create new entries, user cannot decrypt any entries
+- **FULL DECRYPT:** Full access to Cypher features including the ability to decrypt secrets
+
+### Cypher Access Policies
+
+Like other Policy types, Cypher Access Policies are created in Administration > Policies. Click + ADD POLICY to create new. Set the type to “Cypher Access” and the relevant configuration options will be displayed. In addition to the type, enter a name for the Policy in the top section.
+
+![../../_images/polname.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F8F43DED-7C86-4242-8B6E-37376AC02AEE-high.png)
+
+In the next section, enter the key path to which the Policy will apply. In addition to static entries that point to one specific Cypher entry, this field supports pattern matching with regex. For example, enter “.\*” to refer to all Cypher entries or “secret/.\*” to refer to all entries under the secret mount point.
+
+In addition to the path, set the privileges users in the Policy scope should have on the indicated path.
+
+- **LIST:** See the entries on the indicated path listed in the Cypher UI
+- **READ:** Decrypt the entries on the indicated path
+- **WRITE:** Add new entries on the indicated path
+- **UPDATE:** Edit Cypher entries on the indicated path
+- **DELETE:** Delete entries on the indicated path
+
+![../../_images/polconfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3073851F-5D93-4F03-94A1-C77B7D140E46-high.png)
+
+Finally, set the scope for the Policy. Cypher Access Policies support Global, Role, and User scope. For example, you may want to block off sets of Cypher entries for various departments within your organization. If you have existing Roles in HPE Morpheus Enterprise for each department, you can set up Role-scoped Policies to ensure they can only list, use, and add Cypher entries which are relevant to their own department.
+
+![../../_images/polfilter.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-63A43C98-F636-420D-828D-19BF24B01237-high.png)
+
+IMPORTANT
+
+When Cypher Access Policies conflict, the Policy with the longest path string length (typically the most specific) takes precedence. For example, a Policy giving LIST and READ access to “secret/aws/.\*” would be superseded by a Policy giving NO access to “secret/aws/my-secret-key”. In such a case, the user would see everything at the “secret/aws/.\*” path except the one indicated in the more specific Policy. When Policies targeting the same path differ only in their scope, the following scope precedence is applied: Role > User > Global. For example, if a Role-scoped Policy targeting “.\*” grants LIST and READ while a User-scoped Policy targeting the same path grants LIST, the user would be granted the rights in the Role-scoped Policy.
+
+### Cloud Profiles
+
+Terraform Cloud Profiles are created on each Cloud detail page (Infrastructure > Clouds > Selected Cloud > ProfilesTab), encrypted in Cypher, and create a Cypher entry that is visible both on the Profile tab of the Cloud detail page and in Cypher. When added to a Cloud they create a Cypher entry at path tfvars/profile/cloud/$cloudCode/variables. If a Cloud profile Cypher entry is restricted by a Cypher Access policy, it will be (or will not be) listable/readable/deletable as dictated by the Policy but still will be viewable from the Cloud detail page if the user has sufficient permissions. Restricting or granting access to Cloud profiles via Policy does not affect access on the Cloud. Other Role permissions, such as “Admin: Profiles”, “Infrastructure: Clouds”, and Cloud/Group access must be used to restrict access via Cloud detail pages.
+
+### Example Policy
+
+In my example organization, I have one department that needs access to AWS-related secrets and another department that needs access to Azure-related secrets. There are many other secrets stored in my appliance but I don’t want either of these departments to access any of those.
+
+![../../_images/cypherlist.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E85ADD10-D850-4AC0-B155-027367EC2C47-high.png)
+
+For the first department, I’ve set up a Policy that allows them to list and read (including use and decryption rights) AWS secrets. A second Policy specifically excludes them from seeing one specific entry. The Policy with the more specific path will supersede the more generic Policy that includes a wildcard.
+
+![../../_images/pollist.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1FF1D390-EB0B-4C24-9289-4AF2717D8895-high.png)
+
+By impersonating the user, we see they indeed have access to just the two desired Cypher entries.
+
+![../../_images/user1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3BD14A79-055F-4C2E-AF21-EDE494DAB877-high.png)
+
+For the second department, I have set up a Policy that allows them to list and read (including use and decryption rights) Azure secrets.
+
+![../../_images/cypherlist2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6FD23103-1276-4EBB-AC2A-15440A479D4D-high.png)
+
+By impersonating the user once again, we see they indeed have access only to Azure entries.
+
+![../../_images/user2cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E2E311FD-BE92-4152-A79B-AB71DBA890B9-high.png)
+
+## Expiration Policies
+
+Expiration policies set an expiration timeframe for any instance provisioned into the cloud, role, group or by the user the policy is added to. When an instance expires, it is terminated and deleted.
+
+Configuration options for expiration policies:
+
+Expiration Type
+:   - User Configurable- expiration timeframe is editable during provisioning
+    - Fixed Expiration- user cannot change expiration timeframe
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being removed.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the expiration date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to expire.
+
+Notification Message
+:   Customizable message for notification emails. The default message is `Instance ${instance?.name} is set to expire on ${instance?.expireDate}`
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+Instances with expirations show the time until expiration in the instance detail pane. Instances with active expiration policies can be extended by selecting the EXTEND NOW button in the instance detail pane. The extension length is set in the policy by the RENEWAL DAYS field.
+
+Expirations can also be added to any instance during provisioning by entering the number of days in the EXPIRATION DAYS field in the Lifecycle section of the automation section of the provisioning wizard. Expiration can be added to any instance even if no policies have been created.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Instance and Host Names
+
+Naming Policies will populate a fixed or editable name for instances, hosts and hostnames. The Name Pattern field uses ${variable} string interpolation.
+
+NAMING TYPE
+:   User Configurable
+    :   Naming pattern will pre-populate during provisioning but can be edited by the user.
+
+    Fixed Name
+    :   Naming pattern will pre-populate during provisioning and cannot be changed.
+
+NAME PATTERN
+:   The Name Pattern field uses Static text and/or `${variable}` string interpolation, such as `morpheus${cloudCode}${type}${sequence+3000}`
+
+    An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+    Commonly used variables for naming patterns include:
+
+    ```
+    ```
+    ${groupName}  
+    ${groupCode}  
+    ${cloudName}  
+    ${cloudCode}  
+    ${type}  
+    ${accountId}  
+    ${account}  
+    ${accountType}  
+    ${platform}  
+    ${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+    ${userId}  
+    ${username}  
+    ${userInitials}  
+    ${provisionType}  
+    ${instance.instanceContext} # Environment Code  
+    ${sequence} # results in 1  
+    ${sequence+100} # results in 101  
+    ${sequence.toString().padLeft(5,'0')} #results in 00001
+    ```
+    ```
+
+    Cloud codes and Group codes are fields found in their respective configuration panes.
+
+AUTO RESOLVE CONFLICTS
+:   HPE Morpheus Enterprise will automatically resolve naming conflicts by appending a sequential -number to the name when enabled.
+
+## Shutdown Policies
+
+Shutdown policies dictate the number of days an instance is allowed to run before it is shut down. Shutdown is consistent across cloud types i.e.: in VMware, a VM is powered off. In AWS, an instance is stopped. Etc.
+
+Configuration options for shutdown policies:
+
+Shutdown Type
+:   User Configurable
+    :   Shutdown timeframe is editable during provisioning.
+
+    Fixed Expiration
+    :   User cannot change shutdown timeframe during provisioning.
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being shut down.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the shutdown date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to shut down.
+
+Notification Message
+:   Customizable message for notification email.
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Provision Approval
+
+HPE Morpheus Enterprise Provision Approvals enable an approval workflow via internal HPE Morpheus Enterprise approval or via ServiceNow workflow. If a ServiceNow integration is present, the ServiceNow option is enabled. The Approval workflow to be selected is dynamically created by querying the ServiceNow Workflow table in the integrated ServiceNow instance.
+
+This ServiceNow approval integration enables users to use the HPE Morpheus Enterprise Self-Service provisioning portal to provision new instances and still respect the required ServiceNow business approval workflow.
+
+## Power Schedules
+
+Power Schedules set daily times to shutdown and startup instances. Power schedule can be created and managed in Library > Automation > Power Scheduling
+
+NOTE
+
+Power Schedule Policies will apply to Instances created in a Group or Cloud after the Policy is enabled, and will not apply to pre-existing Instances.
+
+Configuration options for Power Schedule Policies:
+
+DESCRIPTION
+:   Add details about your Policy for reference in the Policies tab.
+
+Enabled
+:   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Groups Instances until re-enabled.
+
+ENFORCEMENT TYPE
+:   - User Configurable: Power Schedule choice is editable by User during provisioning.
+    - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+POWER SCHEDULE
+:   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## Max Resources
+
+Max Resource policies allow setting quotas for Clouds, Groups, Roles or Users for maximum amount of Memory, Storage, Cores, Hosts, VM’s, or Containers that can be created in the Cloud, Group, Role or by the User the Policy is assigned to.
+
+Configuration options for Max Resources Policies:
+
+Max Containers
+:   Sets the maximum combined total of Containers in Instances per Policy Scope.
+
+Max Cores
+:   Sets the maximum combined total of Cores in Instances per Policy Scope.
+
+Max Hosts
+:   Sets the maximum total of Hosts per Policy Scope.
+
+Max Memory
+:   Sets the maximum combined total of RAM (capacity) for Instances per Policy Scope.
+
+Max Storage
+:   Sets the maximum combined total of Storage (capacity) for Instances per Policy Scope.
+
+Max VMs
+:   Sets the maximum total of managed Virtual Machines per Policy Scope.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## User Creation
+
+The User Creation policy controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+Configuration options for User Creation Policies:
+
+TYPE
+:   User Creation
+
+DESCRIPTION
+:   Description to identify the policy config
+
+Enabled
+:   Policies enforcement can be disabled or enabled at any time.
+
+ENFORCEMENT TYPE
+:   - User Configurable: User Creation choice is editable by User during provisioning.
+    - Fixed: User cannot change User Creation setting during provisioning.
+
+CREATE USER
+:   Check to allow or force user creation. Uncheck to disable by default or force no user creation.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json b/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
new file mode 100644
index 0000000..12d7b48
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+  "title": "NSX",
+  "ordinal": 508,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html",
+  "topic_cluster": {
+    "clustering_title": "NSX",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md b/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
new file mode 100644
index 0000000..47cf0ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
@@ -0,0 +1,115 @@
+# NSX
+
+## Overview
+
+VMware NSX offers network virtualization allowing for creation and management of software-based virtual networks in an efficient and programmatic way. HPE Morpheus Enterprise offers a full-featured integration with NSX, including Project scoping for NSX 4+ integrations. HPE Morpheus Enterprise will ingest and expose its networking abstractions in the following sections of the HPE Morpheus Enterprise NSX integration:
+
+- SUMMARY
+- TRANSPORT ZONES
+- DHCP
+- SEGMENTS
+- FIREWALL
+- TIER-1 GATEWAYS
+- TIER-0 GATEWAYS
+- EDGE CLUSTERS
+- GROUPS
+
+This guide goes through the process of integrating an existing NSX installation with HPE Morpheus Enterprise and working with the associated objects synced in with the integration. For more on installing NSX and an overview of its concepts, please review the [NSX overview documentation](https://docs.vmware.com/en/VMware-NSX-Data-Center/2.0/com.vmware.nsxt.install.doc/GUID-10B1A61D-4DF2-481E-A93E-C694726393F9.html) provided by VMware.
+
+## NSX Tagging
+
+An NSX integration can apply Instance and VM tags to VMs in NSX, if desired. To apply this, mark the box for “APPLY VM TAGS” when adding or editing an NSX integration.
+
+![../../_images/applyTags.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0DEECD00-D8E9-4B5D-98C9-A07FB86C1CDE-high.png)
+
+Once this configuration is set on the integration, any tags that are applied to applicable Instances through the provisioning wizard at provision time will be applied to those VMs in NSX. In the example below, I’ve set one tag on the new Instance in the provisioning wizard:
+
+![../../_images/setTag.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-806F0064-33EE-43D9-83EB-B8A9BBF0BE93-high.png)
+
+Once provisioning is complete, the tags are confirmed to be visible in the NSX console as well:
+
+![../../_images/showNsx.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-64F1C009-4585-4F84-BBFD-FFD85FEF51D7-high.png)
+
+## NSX Projects
+
+Projects in NSX are analogous to tenants in other products and are a part of NSX version 4+. Projects allow for the isolation of networking abstractions into individual tenants within a single NSX appliance. If your organization is already utilizing NSX Projects, you are probably very familiar with their concept and execution but others can find high-level details about them [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+HPE Morpheus Enterprise supports a full-featured integration with NSX, including the ability to scope the HPE Morpheus Enterprise integration to a specific Project the service user can access. Using Project-scoped integrations allows multiple NSX integrations to be made to the same NSX appliance and ensures HPE Morpheus Enterprise users are siloed to only the NSX Projects they can access.
+
+## Add NSX Integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select Select + ADD > VMWare NSX
+3. Enter the following: 
+
+   - NAME: Name for the NSX Integration in HPE Morpheus Enterprise
+   - VISIBILITY: Public (available to all HPE Morpheus Enterprise Tenants) or Private (available only to the current Tenant). This option is shown only in the HPE Morpheus Enterprise Master Tenant
+   - API HOST: URL of the NSX Manager (ex. <https://x.x.x.x/api>)
+   - CREDENTIALS: A pre-stored credential set can be used to create this integration. If “Local Credentials” is selected, USERNAME and PASSWORD fields are presented and must be filled
+   - USERNAME: NSX service account username. Prior to NSX version 4, this is likely an admin account with access to all networking constructs. In NSX version 4 and higher, this could be an admin for access to default space constructs or it could be a Project-specific user depending on the access needs of the integration being created
+   - PASSWORD: The password for the NSX service account entered above
+   - PROJECT: As soon as an API HOST and credentials are provided, HPE Morpheus Enterprise will attempt to authenticate with the NSX appliance. When authentication is successful and a NSX 4+ appliance is detected, a PROJECT field will appear and the dropdown will be pre-populated with Projects accessible to the service user account
+   - VMWARE CLOUD: Select the existing VMware cloud associated with this NSX integration
+4. Select ADD NETWORK INTEGRATION
+
+### Results
+
+Once the NSX Integration is added HPE Morpheus Enterprise will sync in existing Transport Zones, DHCP servers and relays, Segments, firewall groups and rules, Gateways, Edge Clusters, and Groups. We can manage these synced items from within HPE Morpheus Enterprise UI, including the ability to create, edit, and delete them.
+
+NOTE
+
+The available tabs on the integration detail page will be dependent on the Project selected when the integration was created. Just like in NSX, the default view (and thus integrations scoped to the default Project) will have access to all constructs whereas individual Projects will not. Integrations scoped to individual Projects can view the DHCP, Segments, Firewall, Tier-1 Gateways, and Groups tabs but not the other tabs described here. These limitations are identical to those in the NSX console UI. More information on NSX Projects is available [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+## Summary View
+
+The SUMMARY tab contains the default view when accessing an NSX integration. From the summary view we can see the status of the NSX server, and details about interfaces and group status.
+
+## Transport Zones
+
+Access Transport Zones by selecting the Transport Zones tab. The default view of the Transport Zones tab lists Transport zones and presents some detail about them such as name, traffic type, status, and more. The integration allows for creation of new Transport Zones, editing and deleting.
+
+![../../_images/1tz.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E5021E3F-6EC5-433B-9471-40D7563D0107-high.png)
+
+## DHCP
+
+DHCP servers and relays are displayed on the DHCP tab. View information such as names and server addresses. The integration allows for creation of new servers and relays, editing and deleting.
+
+![../../_images/1dhcp.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B3C32D7F-69D9-462D-9766-55EE13CAD643-high.png)
+
+## Segments
+
+Access Segments by from the Segments tab. The summary view includes high-level information such as status, name, network name and CIDR. The integration allows for creating, editing and deleting NSX Segments
+
+![../../_images/1segments.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D72DEE9B-2CF2-40E3-9256-5C4FE66E2794-high.png)
+
+## Firewall
+
+Firewall Groups and Rules are accessible from the Firewall tab. From the summary view, Groups can be expanded to view Rules within. From the ACTIONS menu, create new Groups by selecting “Create Group”. When a Group has been expanded, the “Create Rule” selection within the ACTIONS menu will also be accessible and a new rule can be created within the selcted Group. The integration allows for viewing, creating, editing and deleting Firewall Groups and Rules.
+
+![../../_images/1firewall.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-04A798AB-AD05-4547-97F6-515C09BE616A-high.png)
+
+## Tier-0 Gateways
+
+Access Tier-0 Gateways from the Tier-0 Gateways tab. The integration allows creating, editing and deleting Tier-0 Gateways.
+
+![../../_images/1t0.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E58BC69D-9E6A-44E7-8181-4B7597235E5F-high.png)
+
+## Tier-1 Gateways
+
+Access Tier-1 Gateways from the Tier-1 Gateways tab. The integration allows creating, editing and deleting Tier-1 Gateways.
+
+![../../_images/1t1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ECFD21E1-3744-46E8-9A14-3A07AE2EA2EB-high.png)
+
+## Edge Clusters
+
+View Edge Clusters from the Edge Clusters tab. The default view lists each Edge Cluster with name, member type, cluster profile, and more. The integration allows viewing and limited editing of Edge Clusters.
+
+![../../_images/1edgeclusters.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-42A4E243-3B5E-45C6-AC05-01E63382D520-high.png)
+
+## Groups
+
+NSX Groups are viewed from the Groups tab. The default view lists each Group alone with member details. The HPE Morpheus Enterprise NSX integration allows for creating, editing and deleting Groups.
+
+![../../_images/1groups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C6C0EDD3-C289-4A0A-B449-038EF1E08D17-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json b/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
new file mode 100644
index 0000000..1721c85
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+  "title": "Mac Stadium",
+  "ordinal": 461,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06D232B4-F473-44C5-AD24-AECD128273E5.html",
+  "topic_cluster": {
+    "clustering_title": "Mac Stadium",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md b/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
new file mode 100644
index 0000000..75a014f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
@@ -0,0 +1,136 @@
+# Mac Stadium
+
+## Overview
+
+MacStadium is a provider of enterprise-class hosting solutions for Apple Mac infrastructure. It can be used to deploy a hosted private cloud for large-scale CI/CD or even a single Mac mini to test an iOS app. It allows virtualized Mac build machines
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json b/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
new file mode 100644
index 0000000..b9cb332
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+  "title": "To create a Tenant Role:",
+  "ordinal": 305,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html",
+  "topic_cluster": {
+    "clustering_title": "To create a Tenant Role:",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md b/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
new file mode 100644
index 0000000..93c7423
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
@@ -0,0 +1,14 @@
+# To create a Tenant Role:
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “Tenant Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select SAVE CHANGES
+
+## Results
+
+After saving, the Role will be created and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json b/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
new file mode 100644
index 0000000..d5d4ec2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+  "title": "Workloads: Blueprint Usage",
+  "ordinal": 69,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Blueprint Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md b/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
new file mode 100644
index 0000000..f11e355
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
@@ -0,0 +1,32 @@
+# Workloads: Blueprint Usage
+
+![../_images/11blueprintusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C67DA833-C730-4887-9672-7E63FABC0841-high.png)
+
+The Blueprint Usage dashboard lists all provisioned Apps that meet filters set on the dashboard. Once the desired group of Apps is filtered into the dashboard, administrators will see the total provisioned from each Blueprint, total number of Instances created from the Apps, and costing details.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **TYPES:** The total number of App types represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **MONTH TO DATE:** The total month-to-date spend for all Apps shown in the dashboard
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Blueprint Usage List
+
+All Blueprints which have a currently-existing App provisioned from them and selected in the dashboard filters are listed here. The name and type of the Blueprint is listed along with the total number of Instances across all provisionings, total Groups, total Clouds, and the total count of all Apps from that Blueprint.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json b/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
new file mode 100644
index 0000000..2572d32
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+  "title": "Docker Clusters",
+  "ordinal": 198,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md b/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
new file mode 100644
index 0000000..e2782a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
@@ -0,0 +1,71 @@
+# Docker Clusters
+
+## About this task
+
+Provisions a new Docker Cluster managed by Morpheus.
+
+To create a new Docker Cluster:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Docker Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Docker Cluster
+
+   RESOURCE NAME
+   :   Name for Docker Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+5. Select NEXT
+6. Populate the following (options depend on Cloud Selection and will vary): 
+
+   LAYOUT
+   :   Select from available layouts.
+
+   PLAN
+   :   Select plan for Docker Host
+
+   VOLUMES
+   :   Configure volumes for Docker Host
+
+   NETWORKS
+   :   Select the network for Docker Master & Worker VM’s
+
+   NUMBER OF HOSTS
+   :   Specify the number of hosts to be created
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+7. Select NEXT
+8. Select optional Workflow to execute
+9. Select NEXT
+10. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json b/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
new file mode 100644
index 0000000..fa97702
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+  "title": "Volume Management",
+  "ordinal": 441,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md b/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
new file mode 100644
index 0000000..3453584
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
@@ -0,0 +1,10 @@
+# Volume Management
+
+Volume life cycle management can be performed under the Infrastructure > Storage > Volumes tab. It allows the user to perform create/resize/delete operations.
+
+**Subtopics**  
+
+- **[Adding Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html)**
+- **[Deleting Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html)**
+- **[Resizing Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html)**
+- **[Reconfiguring Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json b/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
new file mode 100644
index 0000000..c731611
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+  "title": "Adding OpenShift Clusters",
+  "ordinal": 206,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html",
+  "topic_cluster": {
+    "clustering_title": "Adding OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md b/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
new file mode 100644
index 0000000..05dd0ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
@@ -0,0 +1,24 @@
+# Adding OpenShift Clusters
+
+NOTE
+
+Adding an OpenShift cluster requires a pre-existing Group and Private Cloud-type Cloud. See Groups and Clouds documentation elsewhere in this user manual for more details on those constructs.
+
+To onboard an OpenShift cluster, begin by collecting an API token and API URL from OpenShift. Bear in mind the integration user with HPE Morpheus Enterprise must be a full administrator user.
+
+1. Log into the OpenShift console
+2. In the far top-right of the application window, click on the name of the logged in user to expand a small dropdown menu
+3. Click "Copy login command"
+4. Click "Display Token"
+5. On the resulting screen, both the API URL and the API token can be copied. You will need to enter these values directly into the "Add Cluster" modal within HPE Morpheus Enterprise in the next step
+
+With the authentication details available, head back to HPE Morpheus Enterprise to add a new OpenShift cluster:
+
+1. Navigate to Infrastructure > Clusters
+2. Click + Add Cluster
+3. Select "RED HAT OPENSHIFT CLUSTER" and click Next
+4. On the Group tab, select the HPE Morpheus Enterprise Group to associate with the cluster and click Next
+5. On the Name tab, you must at least configure a "Cluster Name" attribute and select a Cloud. The "Cluster Name" is a friendly name to identify the OpenShift cluster in HPE Morpheus Enterprise. The Cloud configuration requires you to select a pre-existing Private Cloud-type Cloud. There are optional configurations here as well, such as applying Labels or adding a description
+6. On the Configure tab, select the Layout that corresponds closest to the version of OpenShift running on the cluster. Integration with HPE Morpheus Enterprise requires OpenShift version 4.x at minimum. On this tab, you'll also enter the API URL and service token collected earlier. If "Inventory Existing Instances" is checked, HPE Morpheus Enterprise with automatically onboard any virtualized workloads which are currently running on the cluster and any that are provisioned directly from the OpenShift console in the future. Click Next
+7. On the Review tab, click Complete
+8. Within a short time, the new OpenShift cluster will appear on the clusters list page alongside any other cluster that may currently be running
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json b/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
new file mode 100644
index 0000000..b78f776
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+  "title": "Common Ports & Requirements",
+  "ordinal": 349,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md b/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
new file mode 100644
index 0000000..512d7ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | DNS Resolution from node to appliance url Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node | user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node | user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..b105be1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 286,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..fe4db6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,8 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html)**
+- **[Price Sets](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html)**
+- **[Prices](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..95f528f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 327,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..72b30f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,34 @@
+# Environments
+
+## Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+### Creating Environments
+
+#### Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in HPE Morpheus Enterprise
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+   Visibility
+   :   - Private: Available only in the Tenant the environment is created in
+       - Public: Available for all Tenants. Public is only applicable for environments created in the the Master Tenant.
+
+#### Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. HPE Morpheus Enterprise-default environments can only be hidden from users during provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json b/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
new file mode 100644
index 0000000..ef06355
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+  "title": "Wiki",
+  "ordinal": 72,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md b/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
new file mode 100644
index 0000000..15e0f7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
@@ -0,0 +1,50 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, Clusters, and Self-Service Persona Catalog Items. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations  >  Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+## Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, Bare Metal, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations  >  Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations  >  Wiki
+- One Wiki is created per Tenant. There is no multi-tenant access to Wikis
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in User and Tenant Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with HPE Morpheus Enterprise
+
+NOTE
+
+The Wiki replaces Notes. Notes are automatically migrated to corresponding Wiki pages when upgrading HPE Morpheus Enterprise to 4.0.0+.
+
+## Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many HPE Morpheus Enterprise constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
+
+## Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the HPE Morpheus Enterprise appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The HPE Morpheus Enterprise [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the HPE Morpheus Enterprise appliance local storage. HPE Morpheus Enterprise generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in HPE Morpheus Enterprise Archives within your Wiki pages.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json b/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
new file mode 100644
index 0000000..ae3c472
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+  "title": "Uploading OS Images Using NFS",
+  "ordinal": 410,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using NFS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md b/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
new file mode 100644
index 0000000..240c9c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using NFS
+
+## About this task
+
+NFS allows OS images to be stored on a shared Linux file server.
+
+## Procedure
+
+1. Configure an NFSv3 file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the NFS share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json b/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
new file mode 100644
index 0000000..4c9bae0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+  "title": "Import Trusted Certificates",
+  "ordinal": 35,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html",
+  "topic_cluster": {
+    "clustering_title": "Import Trusted Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md b/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
new file mode 100644
index 0000000..87790cb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
@@ -0,0 +1,61 @@
+# Import Trusted Certificates
+
+## About this task
+
+IMPORTANT
+
+The following applies to upgrades after modifying the java keystore.
+
+Steps to import trusted certificates to HPE Morpheus Enterprise after an upgrade.
+
+## Procedure
+
+1. Obtain the full SSL certificate chain in PEM format.
+2. Copy them to each appliance and place them in the `/etc/morpheus/ssl/trusted_certs` directory.
+3. Run morpheus-ctl reconfigure on each appliance, note you don’t need to stop Morpheus before you run this.
+4. Run the following command as root: 
+
+   ```
+   ```
+   export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
+   ```
+   ```
+5. Run the following command for each certificate in the chain, adjusting the file and alias name as needed. Answer yes for the root certificate when asked it you want to trust it. 
+
+   ```
+   ```
+   /opt/morpheus/embedded/java/jre/bin/keytool -import -keystore /opt/morpheus/embedded/java/jre/lib/security/cacerts -trustcacerts -file /etc/morpheus/ssl/trusted_certs/root_ca.pem -alias some_alias -storepass changeit
+   ```
+   ```
+6. Verify by running: 
+
+   ```
+   ```
+   openssl s_client -connect host:port -showcerts -tls1_2
+   ```
+   ```
+7. You should get an output similar to: 
+
+   ```
+   ```
+   New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384  
+   Server public key is 2048 bit  
+   Secure Renegotiation IS supported  
+   No ALPN negotiated  
+   SSL-Session:  
+   Protocol : TLSv1.2  
+   Cipher  : ECDHE-RSA-AES256-GCM-SHA384  
+   Session-ID: 5D9E820E4FF2A73A9977BA663E6029AA5415FEE85F49D8B1E541F5997C8E1FB2  
+   Session-ID-ctx:  
+   Master-Key: 29EEC2E7750C659AECB9942902D9A87B824E571522812B718420FC08F8D2ACE68CB16EC812A7D90B12A86D1970FFD81C  
+   Key-Arg  : None  
+   PSK identity: None  
+   PSK identity hint: None  
+   SRP username: None  
+   Start Time: 1547219217  
+   Timeout  : 7200 (sec)  
+   Verify return code: 0 (ok) #<----------------
+   ```
+   ```
+8. If the certificates are installed correctly you should see `Verify return code: 0 (ok)`. If they were not installed correctly then you will see a return similar to: `Verify return code: 21 (unable to verify the first certificate)`
+9. Repeat for all App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json b/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
new file mode 100644
index 0000000..0a9d969
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+  "title": "EfficientIP SOLIDserver",
+  "ordinal": 516,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html",
+  "topic_cluster": {
+    "clustering_title": "EfficientIP SOLIDserver",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md b/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
new file mode 100644
index 0000000..7bcac05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
@@ -0,0 +1,113 @@
+# EfficientIP SOLIDserver
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+
+## Required Role Permissions
+
+### Add, edit and remove EfficientIP SOLIDserver integrations
+
+- Infrastructure: Network Integration: Full
+
+### View and edit synced IP pools
+
+- Infrastructure: Network IP Pools: Full
+
+### View networks and add synced IP pools to networks
+
+- Infrastructure: Networks: Full or Group
+
+### View and edit synced DNS zones, including creation of zone records
+
+- Infrastructure: Network Domains: Full
+
+## Adding EfficientIP SOLIDserver Integration
+
+### About this task
+
+The EfficientIP SOLIDserver integration type is a plugin that must be added to HPE Morpheus Enterprise before the option to create one will be available. In the future, users will be able to download this and other plugin types from a centralized marketplace. For now, the plugin jar file can be compiled from a public Github repository or can be requested from your account team. See the [Plugins Section](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) of HPE Morpheus Enterprise documentation for more on the process of uploading the plugin JAR to your appliance.
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations and click + ADD
+2. Under the IPAM section, select EfficientIP SOLIDserver
+3. Configure the following: 
+
+   - NAME: Friendly name for this EfficientIP SOLIDserver integration
+   - ENABLED: When checked, this integration will be accessible in HPE Morpheus Enterprise
+   - API URL: The FQDN for the EfficientIP server, not a specific path
+   - USERNAME: The username for an EfficientIP service account. Bear in mind this account will need API access as well as the rights to work with pools, zones, and records you wish to consume from HPE Morpheus Enterprise
+   - PASSWORD: The password for the above named account
+   - THROTTLE RATE: In larger environments, it may be necessary to introduce a rate limit on calls to the EfficientIP API from HPE Morpheus Enterprise. If the EfficientIP console UI becomes less responsive than it was prior to integration with HPE Morpheus Enterprise, it may be due to a high number of API calls in the background from HPE Morpheus Enterprise. In such a case, start with a 50ms throttle rate and adjust accordingly depending on performance
+   - DISABLE SSL SNI VERIFICATION: If necessary, disable the check for a valid SSL certificate on the EfficientIP server
+   - INVENTORY EXISTING: When checked, used IP space will be continually synced between HPE Morpheus Enterprise and EfficientIP. If left unchecked, only IP space claimed (and freed) from HPE Morpheus Enterprise is shown on the detail page for the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+Once saved, HPE Morpheus Enterprise will begin to onboard data from EfficientIP. EfficientIP networks are viewable in Infrastructure > Network > IP Pools under the IP Pools tab. Depending on EfficientIP configuration, you may see up to two “types” of Network Pools sync from EfficientIP, SOLIDserver Subnet and SOLIDserver Pool. In EfficientIP, “pools” are an optional construct that subdivides subnets. In HPE Morpheus Enterprise, both constructs are synced which gives an additional layer of organization when linking Network Pools with Networks (described in the next section) for organizations that use the pools construct. Within a selected IP Pool, host records will also sync and can be viewed in a grid or list layout. DNS Zones are synced under Infrastructure > Network > Domains. By clicking into the domain, DNS Zone records can be viewed.
+
+![../../_images/pool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8125D46A-139B-415D-A7F1-C47CE46A6FD8-high.png)
+
+## Adding IP Pools to Networks
+
+### About this task
+
+At provision time, HPE Morpheus Enterprise can automatically assign the next available IP address in an EfficientIP pool and create the corresponding DNS records. HPE Morpheus Enterprise can also clean up DNS records and free up IP address space on teardown. In order to enable this functionality, add an EfficientIP IP Pool as the Network Pool for an existing network (or networks).
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select a network to view the network detail page and click EDIT
+3. In the typeahead field for NETWORK POOL, search for and select the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Gateway, DNS and CIDR must be populated for static/pool IP assignment. If desired, select “Allow IP Override” to allow selecting between DHCP, Static entry, and pool selection at provision time. Finally, deselect “DHCP server” if a DHCP server will not be used on the network (only static and/or IP Pool assignment).
+
+## Creating Host Records
+
+### Procedure
+
+1. Select an EfficientIP Network Pool from Infrastructure > Network > IP Pools
+2. Select + ADD
+3. Configure the following:
+
+### Results
+
+- **HOSTNAME:** The hostname for the record
+- **IP ADDRESS:** The IP address for the host record
+- **DOMAIN:** Select an EfficientIP zone
+- **CREATE DNS RECORDS:** If selected, DNS A and PTR records will be created in EfficientIP
+
+1. Click SAVE CHANGES
+
+![../../_images/createhost.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-327856E4-74AE-4477-87F4-DF8DB6390B2F-high.png)
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select an EfficientIP zone from the domains list at Infrastructure > Network > Domains
+2. Click + ADD on the Zone Records tab
+3. Configure the following:
+
+### Results
+
+- **NAME:** The name for the records (hostname)
+- **TYPE:** The record type: A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+- **CONTENT:** The content of the record, such as IP address or A record
+- **TTL:** The time to live value
+
+1. Click SAVE CHANGES
+
+![../../_images/createzone.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C64B7661-39C6-4ED3-A6C7-0C57521C7794-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json b/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
new file mode 100644
index 0000000..ad2a1e1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+  "title": "Common Ports & Requirements",
+  "ordinal": 8,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md b/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
new file mode 100644
index 0000000..af2ddc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | Not required for agent installation in VMware vCenter and vCloud Director type clouds. Otherwise, access from HPE Morpheus Enterprise App Nodes to Instance Node on 5985 Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json b/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
new file mode 100644
index 0000000..00d083b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+  "title": "Adding HPE BMaaS Integration",
+  "ordinal": 400,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE BMaaS Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md b/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
new file mode 100644
index 0000000..cd21173
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
@@ -0,0 +1,21 @@
+# Adding HPE BMaaS Integration
+
+## Prerequisites
+
+This procedure describes how to integrate the HPE BMaaS with your Morpheus Enterprise environment.
+
+## About this task
+
+To install the **HPE BMaaS** plugin, perform the following steps:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Administration > Integrations.
+3. Select the Plugins tab and click Add button.
+4. Drag the HPE BMaaS `JAR` file into the Drop Files Here area, or click Add File to select it manually. ![Add Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4551F618-EBCF-470F-80C1-64A815379B94-high.png)
+5. Click the Upload.
+
+## Results
+
+After a successful upload, the HPE BMaaS is available for use.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json b/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
new file mode 100644
index 0000000..6c50390
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+  "title": "Creating and Running an SPP Update Job",
+  "ordinal": 425,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running an SPP Update Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md b/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
new file mode 100644
index 0000000..e822246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
@@ -0,0 +1,54 @@
+# Creating and Running an SPP Update Job
+
+## About this task
+
+This procedure describes how to create and execute a HPE Morpheus Job to perform firmware and driver updates using an HPE SPP image.
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs.
+2. Click Add.
+3. Enter a name for the job.
+
+   NOTE
+
+   - Separate jobs are required for different server generations (for example, Gen10 vs Gen11).
+   - Create separate jobs for **Dry Run** and **Deploy** executions.
+4. Select Workflow Job as the Job Type and click Next.
+5. Select Deploy SPP as the workflow.
+6. Enter the SPPVIRTUALIMAGE value using the ID of the Virtual Image created earlier.
+7. Select a DEPLOYMODE:
+
+   - `DryRun`: Performs inventory only
+   - `Deploy`: Applies firmware and/or driver updates
+8. For SPP Deploy Content, choose one of the following:
+
+   - Firmware only
+   - Drivers only
+   - Firmware and Drivers
+
+   NOTE
+
+   Driver inventory and updates require iSUT and AMS to be running on the target servers.
+9. In the Nodes field, enter the iLO details for each target server in JSON format (minimum 1 server, maximum 30 servers). For example:
+
+   ```
+   ```
+   [  
+     {  
+       "ilo_ip":"1.2.3.4",  
+       "ilo_user":"user1",  
+       "ilo_password":"password1"  
+     },  
+     {  
+       "ilo_ip":"1.2.3.5",  
+       "ilo_user":"user2",  
+       "ilo_password":"password2"  
+     }  
+   ]
+   ```
+   ```
+10. **Optional:**  Create a schedule, or leave the job as Manual.
+11. Select Run Now if you want to execute the job immediately.
+12. Click Next, review the settings, and click Complete.
+13. If the job was not run immediately, click the **gear icon** next to the job and select Execute.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json b/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
new file mode 100644
index 0000000..f302efc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+  "title": "Jobs",
+  "ordinal": 91,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md b/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
new file mode 100644
index 0000000..61b2dae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
@@ -0,0 +1,19 @@
+# Jobs
+
+## Required Role Permissions
+
+Provisioning: Jobs
+
+- **None:** Cannot access Provisioning > Jobs > Jobs tab
+- **Read:** Can access Provisioning > Jobs > Jobs tab but cannot create, edit, or delete Jobs
+- **Full:** Full permissions to create, view, edit, and delete Jobs
+
+Provisioning: Job Executions
+
+- **None:** Cannot access Provisioning > Jobs > Job Executions tab
+- **Read:** Can access and view Provisioning > Jobs > Job Executions tab including job execution history, status, and Job output
+
+**Subtopics**  
+
+- **[Creating Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html)**
+- **[Creating and Running Security Scan Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json b/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
new file mode 100644
index 0000000..3facb9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+  "title": "Clients",
+  "ordinal": 326,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html",
+  "topic_cluster": {
+    "clustering_title": "Clients",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md b/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
new file mode 100644
index 0000000..0ad6fd5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
@@ -0,0 +1,24 @@
+# Clients
+
+## Overview
+
+HPE Morpheus Enterprise includes pre-configured OAuth clients and allows the user to create as many additional clients as they’d like. The pre-configured clients are editable but cannot be deleted. Once configured, access tokens may be generated or re-generated from the [API Access section](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html). Their expiration times may be viewed as well. Client settings are available only in the Primary Tenant and affect all Tenants.
+
+## Creating an OAuth Client
+
+To create a new OAuth Client, click + ADD and configure the following:
+
+- **CLIENT ID:** A reference name for the client in HPE Morpheus Enterprise
+- **SECRET:** An optional OAuth client secret
+- **ACCESS TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the token should be enabled
+- **REFRESH TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the refresh token should be enabled
+
+Once the client is configured, click SAVE CHANGES.
+
+## Editing and Deleting OAuth Clients
+
+From the OAuth client list view (Administration > Settings > Clients), click the pencil (✎) or trash can (🗑) icons to edit or delete the OAuth Client.
+
+NOTE
+
+Pre-configured HPE Morpheus Enterprise-default clients may be edited but not deleted. User-created clients may be edited or deleted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..fbe6ce2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 194,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..e863d17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json b/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
new file mode 100644
index 0000000..5806303
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+  "title": "Blueprints",
+  "ordinal": 125,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md b/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
new file mode 100644
index 0000000..ac4a188
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
@@ -0,0 +1,12 @@
+# Blueprints
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html)**
+- **[Blueprint Development Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html)**
+- **[Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html)**
+- **[Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html)**
+- **[Node Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html)**
+- **[App Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html)**
+- **[Catalog Items](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html)**
+- **[Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..97f086c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 336,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..41405d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json b/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
new file mode 100644
index 0000000..e689f60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+  "title": "Spec Templates",
+  "ordinal": 159,
+  "parent_title": "Templates",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html",
+  "topic_cluster": {
+    "clustering_title": "Spec Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md b/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
new file mode 100644
index 0000000..e3ba103
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
@@ -0,0 +1,35 @@
+# Spec Templates
+
+Spec Templates allow HPE Morpheus Enterprise users to leverage several major Infrastructure-as-Code solutions. These are typically JSON or YAML-based configuration files which make creating and managing multiple resource types easier. HPE Morpheus Enterprise allows users to create and/or manage a collection of these templates for different solutions and from different sources.
+
+HPE Morpheus Enterprise currently supports Spec Templates of the following types:
+
+- Kubernetes Spec
+- Helm Chart
+- Terraform
+- ARM Template
+- CloudFormation Template
+- OneView Server Profile Template
+- UCS Service Profile Template
+
+HPE Morpheus Enterprise also allows users to leverage templates pulled from URL sources, online repositories (such as GitHub), or you can write a template locally inside the “NEW SPEC TEMPLATE” modal.
+
+TIP
+
+To see HPE Morpheus Enterprise Spec Templates in action, take a look at our guide on [creating custom Instance Types using Terraform](https://docs.morpheusdata.com/en/latest/getting_started/guides/terraform_instances.html) or see our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-use-Spec-Templates-to-create-a-custom-instance-type?language=en_US) for another example where a CloudFormation Spec Template is used to create a provisionable custom Instance Type.
+
+## Creating a Spec Template
+
+### Procedure
+
+1. Navigate to Library > Templates > Spec Templates
+2. Click + ADD
+3. Complete the following fields, then click SAVE CHANGES:
+
+### Results
+
+- **NAME**
+- **TYPE:** See the previous section for a complete list of Spec Template types
+- **SOURCE:** Local, Repository, or URL
+- **CONTENT:** If this is a local Spec Template, supply the template in this field. If the template is supplied through a URL or online repository, the CONTENT field will change to allow the user to point HPE Morpheus Enterprise to that resource
+- **VERSION:** (Only displayed on Terraform Spec Templates) Enter a Terraform version number to force a specific version when provisioning your Terraform Instance Type or App, assuming your Terraform Runtime setting (Administration > Settings > Provisioning Tab) is “auto”. If Terraform Runtime is set to “manual”, HPE Morpheus Enterprise will use the version of Terraform installed on the appliance box
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json b/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
new file mode 100644
index 0000000..d70436e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+  "title": "App Blueprints",
+  "ordinal": 131,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md b/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
new file mode 100644
index 0000000..0e2f8be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
@@ -0,0 +1,20 @@
+# App Blueprints
+
+App Blueprints support a vast array of providers and configurations with programmatic markup or Infrastructure as Code capabilities. Blueprints configs can be manually added or scoped to a git repo. HPE Morpheus Enterprise blueprints allows for full automation configuration, locked fields, tiered boots, and linked tiers with exported evars. All blueprints have permission settings for controlling group and tenant access.
+
+App Blueprint Types
+:   - HPE Morpheus Enterprise
+    - Terraform
+    - ARM (Azure)
+    - CloudFormation (AWS)
+    - Kubernetes
+    - Helm
+
+**Subtopics**  
+
+- **[ARM Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html)**
+- **[CloudFormation Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html)**
+- **[Helm Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html)**
+- **[Kubernetes Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html)**
+- **[HPE Morpheus Enterprise Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html)**
+- **[Terraform Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json b/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
new file mode 100644
index 0000000..be8e713
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+  "title": "Huawei Cloud",
+  "ordinal": 457,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.html",
+  "topic_cluster": {
+    "clustering_title": "Huawei Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md b/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
new file mode 100644
index 0000000..62e6efb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
@@ -0,0 +1,306 @@
+# Huawei Cloud
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- Huawei OBS buckets (create, manage, delete, and discovery)
+- Huawei SFS (create, manage, and delete)
+
+## Integrate Huawei Cloud with HPE Morpheus Enterprise
+
+To integrate Huawei Cloud with HPE Morpheus Enterprise, we’ll gather the following pieces of information:
+
+- Account Name
+- Identity (IAM) API URL
+- Project
+- Username
+- Password
+
+Begin by logging into your [Huawei Cloud console](https://console-intl.huaweicloud.com/console). If you’re not currently logged in, you will be prompted to do so. Once on the console page, hover over your username in the upper-right corner of the application window and select “My Credentials”.
+
+![../../../_images/1credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-073462C5-393F-4B31-B939-5DB39532766C-high.png)
+
+From the credentials page, we can gather the Account Name and the Project Name, record them for later when we provide the integration information to HPE Morpheus Enterprise.
+
+![../../../_images/2account_project.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0EA453C5-849B-4F01-AA40-AEDFFCC3A737-high.png)
+
+To gather the API endpoint URL, take a look at the complete list of [endpoints](https://developer.huaweicloud.com/en-us/endpoint). If a specific endpoint exists for your region, use it. In any other case use the endpoint for all regions. It will be formatted like this: <https://iam.myhuaweicloud.com/v3>.
+
+![../../../_images/3identity_api_endpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8DEF10C6-F6CD-4E55-9D76-D67AA280E6CF-high.png)
+
+With this information gathered, and presuming you know the credentials for the service account you wish to use, we can move back into HPE Morpheus Enterprise-UI.
+
+IMPORTANT
+
+Integrating HPE Morpheus Enterprise with Huawei Cloud requires a service account that has programmatic access.
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Huawei Cloud and click NEXT. The information we’ve gathered will be plugged into the CREATE CLOUD modal. The DOMAIN ID field will accept the Account Name field we gathered. Your completed CREATE CLOUD modal will look similar to the one pictured below:
+
+![../../../_images/4add_cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-029DC867-5A63-4F28-9423-F5C3C5C2141F-high.png)
+
+After clicking NEXT, add this new Cloud to a Group or create a new Group. On finalizing the wizard, Huawei Cloud will be integrated into HPE Morpheus Enterprise and ready for provisioning. If you opted to inventory existing workloads, those will be onboarded shortly.
+
+## Add/Edit Huawei Cloud Modal Fields
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity endpoint. See the integration steps above for more detail
+
+DOMAIN ID
+:   The DOMAIN ID field takes the “Account Name” as shown on the [Basic Informati](https://account-intl.huaweicloud.com/usercenter/?locale=en-us#/userindex/accountInfo) of the account. See the integration steps above for more detail
+
+PROJECT
+:   The target project name. See the integration steps above for more detail
+
+USERNAME
+:   The service account username. See the integration steps above for more detail
+
+PASSWORD
+:   The integration service account password. See the integration steps above for more detail
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK image type
+
+Image Store
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VMs
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment.
+
+TIP
+
+When using the RAW image format, you can bypass the image conversion service within the cloud leading to quicker performance. Other image formats are converted to RAW format and back when performing various actions. Using the RAW format from the start will bypass these conversion steps.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Huawei Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud includes the capability to work with Huawei Scalable File Service (SFS). SFS is shared file storage hosted on Huawei Cloud. By integrating HPE Morpheus Enterprise with Huawei Cloud you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Huawei Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Huawei Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+![../../../_images/1editServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DD161EBC-E99E-449A-8B3E-BA8C021C3670-high.png)
+
+Additionally, Huawei SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click + ADD to begin and set the storage server type value to “Huawei SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/2addServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E7F8C4A2-D408-4C34-9C04-C9C7C27A20F0-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to file shares displayed to those whose names match the search terms.
+
+![../../../_images/3shareList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9FD9B522-BF4F-42A5-A282-16726D330F86-high.png)
+
+We can drill into individual file shares by clicking on their hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking + ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+A “Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Huawei SFS file shares can be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking + ADD. Select the type “Huawei SFS Share”. Set the storage service field to a pre-existing Huawei SFS server. A friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones are required fields.
+
+![../../../_images/4addShare.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E135CE4B-C1C8-44C1-9F18-328901E4C10F-high.png)
+
+## Huawei Object Storage Service (OBS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud also supports Object Storage Service (OBS). HPE Morpheus Enterprise will automatically onboard existing OBS servers and buckets shortly after completing the cloud integration. Before you can add a new OBS server from HPE Morpheus Enterprise, you must know or generate a key and secret value from the Huawei console and must provide a Huawei OBS API endpoint.
+
+### Generate a Key and Secret
+
+From the Huawei web console, log into the account used to integrate Huawei Cloud with HPE Morpheus Enterprise. Hover over your account name in the upper-right corner of the application window and click “My Credentials”. Select “Access Keys” from the left-hand sidebar. To create a new key, click + Create Access Key. Complete the two-factor authentication steps in the box that appears.
+
+![../../../_images/1createKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4FC170FA-49EF-4072-A6F4-42311AB880D9-high.png)
+
+Once the key is generated, download or record the key and store it in a safe location. The key will not be viewable or available for download again after this point.
+
+### Create OBS Server in HPE Morpheus Enterprise
+
+With the key and secret value in hand from the previous section, navigate to Infrastructure > Storage > Servers. Click + ADD. On changing the server type to Huawei OBS, you will see the fields for the access key and the secret key. OBS API endpoints can be found in [Huawei endpoint documentation](https://developer.huaweicloud.com/en-us/endpoint). Include those three values in the Create Server modal along with a friendly name for use in HPE Morpheus Enterprise UI. Just like with SFS objects, we can choose to scope the server to all or specific Tenants at this time.
+
+![../../../_images/2addObsServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BFC92FBB-94A2-46A8-ABFC-E7397C7C6E9E-high.png)
+
+### Create Huawei OBS Bucket
+
+With an OBS server onboarded or created in HPE Morpheus Enterprise, you’re able to create and manage Huawei OBS buckets as needed. To create a new bucket, navigate to Infrastructure > Storage > Buckets. Click + ADD and select “Huawei OBS Bucket”. The following fields are required when creating a Huawei OBS bucket:
+
+- **NAME**: A friendly name for use in HPE Morpheus Enterprise UI
+- **STORAGE SERVICE**: Choose the OBS server to associate the new bucket with
+- **BUCKET NAME**: The name of the bucket in Huawei Cloud, this must be unique
+- **STORAGE CLASS**: If needed, view the [discussion of storage classes](https://support.huaweicloud.com/en-us/eu-west-0-usermanual-obs/en-us_topic_0050937852.html) in Huawei support documentation
+- **BUCKET ACL**: Public Read, Public Read/Write, or Private
+- **BUCKET POLICY**: Public Read, Public Read/Write, or Private
+- **STORAGE QUOTA**: Set to 0 for no quota
+
+Once finished, click SAVE CHANGES
+
+![../../../_images/3createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6A0E3B1B-0B05-4CA3-BBF6-E319A6DD6390-high.png)
+
+## Network and Router Creation
+
+Once a Huawei Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Huawei Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Huawei Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Huawei Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the Huawei project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json b/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
new file mode 100644
index 0000000..fbc5383
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 237,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md b/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
new file mode 100644
index 0000000..03f2f8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
@@ -0,0 +1,22 @@
+# OAuth 2.0 Credentials
+
+HPE Morpheus Enterprise supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how HPE Morpheus Enterprise should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+With the OAuth 2.0 credential set stored, they can be set on REST-type Option Lists to source data from behind a compatible authentication wall. With a REST-type Option List open (Library > Options > Option Lists), click the CREDENTIALS dropdown and select the credential set you’ve created. Alternatively, you can add a credential set directly in the add/edit Option List modal if needed. Option Lists can be associated with Select List or Typeahead-type Inputs and applied to Layouts, Instance Types, Workflows, and more to allow for customization at provision or Workflow execution time. Additional details on creating Option Lists can be found in the Library section of HPE Morpheus Enterprise docs.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json b/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
new file mode 100644
index 0000000..a868cfd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+  "title": "Advanced morpheus.rb Settings",
+  "ordinal": 30,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced morpheus.rb Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md b/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
new file mode 100644
index 0000000..c15d7e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
@@ -0,0 +1,124 @@
+# Advanced morpheus.rb Settings
+
+Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work.
+
+```
+```
+app['encryption_key_suffix'] = '$suffix'  
+  # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+appliance_url 'https://morpheus.appliance-url.com'  
+  # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+  # The appliance_url cannot exceed 64 characters  
+  # The appliance_url must not contain a trailing `/`.  
+bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+opensearch['auth_user'] = 'morpheus-es-user'  
+opensearch['enable'] = true  
+opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+opensearch['host'] = "127.0.0.1"  
+opensearch['port'] = "9200"  
+opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+opensearch['use_tls'] = false  
+↓ The following Opensearch settings are only valid for Internal/Embedded Opensearch services  
+opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+opensearch['memory_alloc_arena_max'] = 2  
+opensearch['memory_map_max'] = 65536  
+opensearch['memory_map_threshold'] = 131072  
+opensearch['memory_top_pad'] = 131072  
+opensearch['memory_trim_threshold'] = 131072  
+opensearch['open_files'] = 204800  
+opensearch['secure_mode'] = false  
+opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+opensearch['xmx'] = 0.25  
+guacd['guacamole_enabled'] = false  
+guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+mysql['enable'] = true  
+mysql['host'] = {'127.0.0.1' => 3306}  
+mysql['use_tls'] = false  
+mysql['morpheus_db_user'] = 'morpheus-db-user'  
+mysql['morpheus_password'] = 'morpheus-db-password'  
+mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+mysql['tmp_dir'] = '/tmp/mysql'  
+mysql['log_dir'] = '/var/log/morpheus/mysql'  
+mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+mysql['max_connections'] = 151  
+mysql['max_allowed_packet'] = 67108864  
+mysql['mysql_connect_timeout'] = 60000  
+mysql['mysql_max_reconnects'] = 2  
+mysql['mysql_queries_before_retry_source'] = 0  
+mysql['mysql_seconds_before_retry_source'] = 300  
+nginx['cache_max_size'] = '5000m'  
+nginx['enable'] = true  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['max_loops'] = 60 # seconds  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['log_format_name'] = 'custom'  
+nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+nginx['ssl_company_name'] = "Morpheus, LLC"  
+nginx['ssl_country_name'] = "US"  
+nginx['ssl_email_address'] = "personal@email.com"  
+nginx['ssl_locality_name'] = "San Mateo"  
+nginx['ssl_organizational_unit_name'] = "DevOps"  
+nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+nginx['ssl_session_timeout'] = "5m"  
+nginx['ssl_state_name'] = "CA"  
+nginx['worker_connections'] = 10240  
+nginx['workers'] = integer calculated from number of cpus  
+nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+rabbitmq['enable'] = true  
+rabbitmq['host'] = '127.0.0.1'  
+rabbitmq['port'] = '5672'  
+rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+rabbitmq['vhost'] = 'morpheus'  
+↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+rabbitmq['heartbeat'] = nil  
+rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+rabbitmq['nodename'] = 'rabbit@localhost'  
+rabbitmq['port'] = '5672'  
+rabbitmq['use_tls'] = false  
+repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+ui['kerberos_config'] = nil  
+ui['kerberos_login_config'] = nil  
+ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+ui['max_memory_mb'] = nil  
+ui['memory_alloc_arena_max'] = 2  
+ui['memory_map_max'] = 65536  
+ui['memory_map_threshold'] = 131072  
+ui['memory_top_pad'] = 131072  
+ui['memory_trim_threshold'] = 131072  
+ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+ui['support_links'] = {  
+  'name' => ['url', 'i18n'],  
+  'name1' => ['url1', i18n1'],  
+  'name2' => ['url2', i18n2']  
+} #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+ui['xmx'] = 0.25
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json b/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
new file mode 100644
index 0000000..b25dfd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+  "title": "Overview",
+  "ordinal": 225,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md b/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
new file mode 100644
index 0000000..ce51737
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
@@ -0,0 +1,31 @@
+# Overview
+
+HPE Morpheus Enterprise provisions the following load balancers:
+
+- Amazon ALB (Application Load Balancer)
+- Azure Load Balancer
+- HaProxy Container
+
+and integrates with the following external load balancers:
+
+- Citrix NetScaler
+- F5 BigIP (v11.4+)
+- FortiADC
+- NSX
+- NSX Advanced
+
+Once created or integrated, load balancers are available as an option to be added during provision time or post-provisioning.
+
+Once a load balancer is added to an instance, you can manually scale or configure auto-scaling based on thresholds or schedules, and burst across clouds with cloud priority.
+
+In the load balancers page there are two sections:
+
+Load Balancers
+:   View or edit existing load balancers, add new load balancers.
+
+Virtual Servers
+:   View and link to Instances that are attached to load balancers.
+
+## Group and Tenant Access
+
+Load balancers can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the load balancer resource. Only workloads being provisioned to the selected Groups would have visibility to the load balancer. Workloads provisioned to other Groups would not see the load balancer as an available selection. **Tenant Permissions** control which Tenants may see the load balancer. Public visibility allows access to the load balancer for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json b/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
new file mode 100644
index 0000000..ac5ce4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+  "title": "Adding HPE SPP to the Virtual Image Library",
+  "ordinal": 423,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE SPP to the Virtual Image Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md b/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
new file mode 100644
index 0000000..433ba42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
@@ -0,0 +1,28 @@
+# Adding HPE SPP to the Virtual Image Library
+
+## About this task
+
+This procedure describes how to add an HPE Service Pack for ProLiant (SPP) ISO to the Morpheus Virtual Images library for use in firmware and driver update workflows.
+
+1. Obtain the appropriate HPE SPP ISO for the target ProLiant server generation.
+
+   NOTE
+
+   A separate ISO is required for each server generation (for example, Gen10 and Gen11).
+2. In the Morpheus appliance, navigate to Library > Virtual Images.
+3. Click Add > SPP.
+4. Enter a name for the image (for example, `HPE Gen10 SPP 2025.09.00`).
+5. From the Operating System drop-down list, select the appropriate **HPE SPP for Gen…** entry.
+6. Add the SPP ISO using one of the following methods:
+   - Upload the locally downloaded ISO file, or
+   - Select **URL / PATH** and paste the full URL for the ISO.
+7. Leave all other properties at their default values.
+8. Click Save Changes.
+
+   NOTE
+
+   When uploading a local file, wait for the upload to complete.
+9. In the Virtual Images list, wait until:
+   - Source shows `Uploaded`
+   - Status shows `Active`
+10. Record the **ID** of the Virtual Image entry. This ID is required when creating the update job.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json b/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
new file mode 100644
index 0000000..c0ead9e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+  "title": "Orchestrating Load Balancers",
+  "ordinal": 227,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html",
+  "topic_cluster": {
+    "clustering_title": "Orchestrating Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md b/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
new file mode 100644
index 0000000..590d37f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
@@ -0,0 +1,40 @@
+# Orchestrating Load Balancers
+
+A large part of application orchestration and automation involves tying various web services and backend services into different load balancer configurations. If the automation tool is unable to communicate or integrate with this aspect of your infrastructure, a lot of gaps will be created in the full orchestrated flow of application deployment. This is why Morpheus provides deep integration with load balancers and explicit definitions with catalog items as to how they are connected to provisioned instances. Some of the functionality includes:
+
+- Public Cloud Load Balancer Support
+- Private Cloud Load Balancer Support
+- Port Type definitions (Profiles like HTTP/HTTPS or UDP)
+- SSL Certificate Management and SSL Certificate Upload
+- SSL Passthrough or Forced Redirect
+
+Not only does Morpheus have an ability to provision HAProxy based load balancer containers for easy consumption in development environments, but also has direct tie ins with several Load Balancer Types:
+
+- F5 BigIP
+- Netscaler
+- NSX Advanced Load Balancer
+- Amazon ELB
+- Amazon ALB
+- Azure Load Balancer
+- Fortinet
+- Openstack Octavia
+- HA Proxy
+- NSX
+
+Morpheus exposes configuration options during provisioning of an Instance relevant and common to each supported LB Integration. In some cases, Morpheus also provides direct management and sync support for VIP configurations on the various Load Balancers (such as F5, and NSX Advanced Load Balancer), However in a day to day orchestrated workflow this would not be the ideal means by which a user should consume load balancer services.
+
+By tying the Load Balancer associations into the provisioning of instances and the definition of the instance catalog item, the lifecycle of the VIP can more easily be maintained throughout the lifecycle of whatever application may be deployed.
+
+## Setting up an Instance for Load Balancer Consumption
+
+Several of the provided Morpheus instance types are ready to go with load balancer orchestration out of the box (Apache, Nginx, Tomcat, Node.js, etc). It is also fairly easy to extend existing generic instance types during provisioning to be tied to load balancers or to set up said catalog items in advanced for such functionality.
+
+When creating a custom Instance Type (in Library), one can define a list of exposed ports that the node type within the instance exposes. When defining these exposed ports it prompts for a Name, Port Number, and LB Type. The LB Type is what enables load-balancer functionality. This can either be HTTP,HTTPS, or TCP. This specification helps build the correct profile for the VIP as well as setup the appropriate types of Health Monitors within the target load balancer integration.
+
+Now, when a user consumes this custom instance type (either through single instance provisioning or full application blueprint provisioning), a section appears in the Automation phase of provisioning. Each port that is defined that exposes a load-balancer gets a dropdown to choose which load balancer integration attach to the exposed port and various prompts become available.
+
+These prompts control features ranging from target VIP Address to selecting an SSL Certificate to be applied to the VIP. These SSL Certificates will even go so far as to create SSL Profiles in integrations for things like an F5 automatically for the application.
+
+Once the instance is provisioned, as part of the final phase, the load balancer configuration will be applied and maintained on the instance. This association can be manipulated after the fact via the “Scale” tab found on the Instance Detail page.
+
+Another benefit to associating load-balancers this way is that the pool members are automatically maintained during scaling events, either via auto-scaling thresholds or manual node additions / removals.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json b/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
new file mode 100644
index 0000000..f319dd1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+  "title": "Overview",
+  "ordinal": 171,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md b/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
new file mode 100644
index 0000000..d7d78dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
@@ -0,0 +1,22 @@
+# Overview
+
+Infrastructure  >  Clusters is for creating and managing Kubernetes Clusters, HPE Morpheus Enterprise manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS, AKS and GKE.
+
+## Cluster Types
+
+Table 1.
+
+     |  |  |  |
+| --- | --- | --- |
+| **Name** | **Description** | **Provider Type** |
+| Kubernetes Cluster | Provisions by default a Kubernetes cluster consisting of 1 Kubernetes Master and 3 Kubernetes Worker nodes. Additional system layouts available including Master clusters. Custom layouts can be created. | Kubernetes |
+| Docker Cluster | Provisions by default a Morpheus controlled Docker Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus Docker Hosts are automatically converted to Clusters upon 4.0.0 upgrade. | Docker |
+| EKS Cluster | Amazon EKS (Elastic Kubernetes Service) Clusters | Kubernetes |
+| AKS Cluster | Azure AKS (Azure Kubernets Service) Clusters | Kubernetes |
+| Ext Kubernetes | Brings an existing (brownfield) Kubernetes cluster into HPE Morpheus Enterprise | Kubernetes |
+| GKE Cluster | Google Cloud GKE (Google Kubernetes Engine) Clusters | Kubernetes |
+| HVM Cluster | A KVM‐based virtualization solution. See the detailed section below on HVM Clusters for complete use documentation. | KVM |
+
+NOTE
+
+Refer to clusterLayouts for supported Clouds per Cluster Type.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json b/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
new file mode 100644
index 0000000..1c8856f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+  "title": "Diagrams",
+  "ordinal": 343,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html",
+  "topic_cluster": {
+    "clustering_title": "Diagrams",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md b/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
new file mode 100644
index 0000000..eac468d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
@@ -0,0 +1,45 @@
+# Diagrams
+
+The HPE Morpheus Enterprise diagram repository contains many diagrams related to HPE Morpheus Enterprise appliance architectures, HPE Morpheus Enterprise concepts, and reference diagrams for integrating HPE Morpheus Enterprise with third-party technologies.
+
+## Appliance Architectures
+
+### All-in-one (single node) Installation
+
+![../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+### 3-node High Availability (HA) Installation
+
+![../_images/morpheus-3node-ha.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EF3C066B-2133-4DBC-8E53-1C23C38740D4-high.png)
+
+### Fully Distributed High Availability (HA) Installation
+
+![../_images/FullDistributedSingleSite.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6791DB71-7757-41D2-985E-8E45863D89CD-high.png)
+
+## HPE Morpheus Enterprise Concepts
+
+### Cloud-Group-Role Relationship
+
+![../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+### Library Items
+
+![../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
+
+### Mapping Morpheus Constructs to Public and Private Cloud Constructs
+
+![../_images/awsAndMorpheusConstructs.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-921BCD31-0FFD-4AB6-98C5-9FA5BCC5E31C-high.png)
+
+## Third-Party Technology Integration
+
+### Zerto
+
+![../_images/morpehus_zerto_chart.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+### Veeam
+
+![../_images/MorpheusVeeamIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-42CD5807-1040-4713-9939-451BA81D9190-high.png)
+
+### Mapping Identity Source Groups to Morpheus Roles
+
+![../_images/mapIdentityToMorpheus.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-58D1993D-5964-4804-877B-ECF3112E147E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json b/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
new file mode 100644
index 0000000..bb23dcf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+  "title": "Unmanaged Networks",
+  "ordinal": 429,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html",
+  "topic_cluster": {
+    "clustering_title": "Unmanaged Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md b/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
new file mode 100644
index 0000000..267ae3f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
@@ -0,0 +1,23 @@
+# Unmanaged Networks
+
+The unmanaged Network mode is used when the network infrastructure is not managed by HPE Morpheus.
+
+In this case, there is a minimal configuration that is created as default when the cloud gets created with the network mode set to `Unmanaged network`. This minimal configuration includes a default Resource Pool that can be used to associate compute servers with, and a default unmanaged network that is available during instance provisioning to attach with compute servers.
+
+The default unmanaged network is configured as an untagged network with DHCP as the IP allocation method. This allows a compute instance provisioned to come up with network connectivity without any specific network configuration required from the user.
+
+The unmanaged network assumes:
+
+- The network infrastructure to be configured correctly for the untagged network to work correctly.
+- A DHCP server stood up in the infrastructure for that network.
+
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DD9E1A8A-D473-4DDE-9761-DD613DCF1F4B-high.png)
+
+Users can create other networks (VLANs) if required, in addition to the default unmanaged network, and use them in their BM instance.
+
+NOTE
+
+- If the ALLOW IP OVERRIDE checkbox is selected (allows selection of DHCP or static IP or IP Pool), ensure that the CIDR and GATEWAY fields are configured correctly.
+- At present, only one physical interface is supported for the unmanaged network mode.
+
+The network consumption by an instance is the same as for managed networks.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..b5b8302
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 101,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..665ed96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,13 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html)**
+- **[Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
+- **[Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html)**
+- **[Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html)**
+- **[Library Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html)**
+- **[Operating Systems](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html)**
+- **[Variables](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json b/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
new file mode 100644
index 0000000..f59a0ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+  "title": "Morpheus Virtual Desktops",
+  "ordinal": 367,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Virtual Desktops",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md b/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
new file mode 100644
index 0000000..c487bdd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
@@ -0,0 +1,450 @@
+# Morpheus Virtual Desktops
+
+## VDI Pools Overview
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
+
+## Virtual Desktop Persona Overview
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json b/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
new file mode 100644
index 0000000..5ab7a3e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+  "title": "Costing: Cloud Costing",
+  "ordinal": 58,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Cloud Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md b/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
new file mode 100644
index 0000000..346e11c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
@@ -0,0 +1,39 @@
+# Costing: Cloud Costing
+
+![../_images/1cloudcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-429BA931-09F3-4CC2-AC8E-45B3D0167664-high.png)
+
+The Cloud Costing dashboard breaks down total costs by cloud type, cloud region, and individual cloud. This includes reporting the total number of clouds that meet your filters, the month-to-date running total, the projected monthly spend, among other useful metrics.
+
+## Filters
+
+Filter the Clouds pulled into the dashboard by one or more of the following fields:
+
+- Cloud (all matched by search)
+- Group
+- Cloud (selected from dropdown)
+- Tenant
+- Tag (Key)
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Clouds that meet set filters:
+
+- **CLOUDS:** The total number of Clouds that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Clouds meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Clouds meeting dashboard filters
+- **CLOUD TYPES:** The number of distinct cloud types that meet the dashboard filters, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud types
+- **REGIONS:** The total number of regions represented by Clouds meeting the dashboard filters
+
+In addition to the totals described above, graphs visualize the percentage of these totals accounted for by specific Clouds, Cloud types, and Cloud regions.
+
+## Cloud List
+
+Each Cloud that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Cloud:
+
+- **TYPE:** The Cloud type, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud type
+- **NAME:** The name given to the Cloud in HPE Morpheus Enterprise at the time of integration
+- **LOCATION:** The Cloud location (if available)
+- **REGION:** The Cloud region (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Cloud listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Cloud listed
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json b/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
new file mode 100644
index 0000000..af75340
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+  "title": "Security Groups",
+  "ordinal": 222,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html",
+  "topic_cluster": {
+    "clustering_title": "Security Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md b/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
new file mode 100644
index 0000000..269452d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
@@ -0,0 +1,81 @@
+# Security Groups
+
+Infrastructure  >  Network - Security Groups
+
+## Overview
+
+A Security Group acts as a virtual firewall that controls the traffic for one or more Instances. When you launch an instance, you associate one or more Security Groups with the instance. You add rules to each Security Group that allow traffic to or from its associated Instances. You can modify the rules for a Security Group at any time; the new rules are automatically applied to all Instances that are associated with the Security Group.
+
+IMPORTANT
+
+The local firewall setting must be enabled for Security Groups to be applied in the guest firewall (iptables). The local firewall setting can be enabled in Infrastructure > Clouds > Click the Cloud > Edit > Advanced Options > LocalFirewall (On/Off)
+
+IMPORTANT
+
+When then local firewall setting is enabled, Morpheus will automatically set an iptable rule to allow incoming connections on tcp port 22 from the Morpheus Appliance.
+
+IMPORTANT
+
+If the local firewall setting is configured on a cloud that supports Security Groups natively (AWS for example), the local firewall setting is ignored and the guest firewall will not be modified. Security Groups will be attached to the instance as normal
+
+## Add Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the + Add Security Group button.
+3. From the Security Group Wizard input a name, and description.
+4. Save Changes
+
+## Add Security Group Rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to add a rule to.
+3. From the Security Group page click the + Add Rule button.
+4. From the Rule Wizard select the rule type and input source and depending on the type selected protocol and input a port range.
+5. Save Changes
+
+## Edit Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to edit a rule in.
+3. Click the edit icon on the row of the Security Group rule you wish to edit.
+4. Modify information as needed.
+5. Save Changes
+
+## Delete Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to delete a rule from.
+3. Click the delete icon on the row of the Security Group rule you wish to delete.
+
+## Add Cloud Security Group
+
+### About this task
+
+To add Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the desired cloud to add a Security Group
+3. Click the Networks tab
+4. Within the “Security Groups” section, click on a Security Group to edit its rules
+5. Alternatively, click + ADD SECURITY GROUP to create a new one
+
+## Remove Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the cloud to remove the Security Group from.
+3. Click the Security Groups tab.
+4. Click the Edit Security Groups button.
+5. Click the - (Minus) button of the Security Group from the Added Security Groups list to remove.
+6. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json b/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
new file mode 100644
index 0000000..ab01b28
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+  "title": "Building Catalog Blueprints",
+  "ordinal": 141,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md b/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
new file mode 100644
index 0000000..626f291
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
@@ -0,0 +1,62 @@
+# Building Catalog Blueprints
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+HPE Morpheus Enterprise Blueprints allow for full multi-tier application deployment. In the Self Service catalog, user can create catalog items based on pre-existing App Blueprints. If new Blueprints need to be created for the Service Catalog, see other sections of HPE Morpheus Enterprise docs on building App Blueprints of various supported types. Just like with catalog Instances, we can pre-configure Blueprints and present them to users viewing the Service Catalog Persona view for easy, one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Blueprint. The modal window will appear to configure and add a new catalog Blueprint.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIGURE:** Click CONFIGURE to use the familiar App provisioning wizard to tie Blueprint and App deployment configuration to the Catalog Item
+- **APP SPEC:** Inject App spec here for any fields required to provision an App from your Blueprint. You may also inject any overrides to the existing Blueprint spec that are desired. App Spec configuration must be YAML, a simple example that names the App and sets the Group and Cloud is included below:
+
+  ```
+  ```
+  #Example App Spec  
+  name: '<%= customOption.appName %>'  
+  group:  
+    name: Dev Group  
+  environment: Dev  
+  tiers:  
+    Web:  
+      instances:  
+        - instance:  
+            type: nginx  
+            cloud: Dev AWS  
+    App:  
+      instances:  
+        - instance:  
+            type: apache  
+            cloud: Dev AWS
+  ```
+  ```
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+
+  NOTE
+
+  App spec custom option variables should be single quoted in YAML: `cloud: '<%= customOption.cloud %>'`. Additionally, not all variables are available here as many are unknown until provisioning. Users may use any custom Input values (customOption) as well as name or hostname values which are resolved as part of naming policy evaluation.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json b/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
new file mode 100644
index 0000000..6a766f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+  "title": "Creating Roles",
+  "ordinal": 300,
+  "parent_title": "Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md b/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
new file mode 100644
index 0000000..25beaa4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
@@ -0,0 +1,6 @@
+# Creating Roles
+
+**Subtopics**  
+
+- **[User Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html)**
+- **[Tenant Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json b/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
new file mode 100644
index 0000000..17dea66
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+  "title": "Create a MultiTenant User Role",
+  "ordinal": 303,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html",
+  "topic_cluster": {
+    "clustering_title": "Create a MultiTenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md b/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
new file mode 100644
index 0000000..222c262
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
@@ -0,0 +1,28 @@
+# Create a MultiTenant User Role
+
+## About this task
+
+A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select the MULTITENANT ROLE checkbox
+7. Optionally select the MULTITENANT LOCKED checkbox \* When enabled, the FEATURE ACCESS settings in the Role will not be editable by subtenants. Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+8. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
new file mode 100644
index 0000000..4577e8b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+  "title": "Volumes",
+  "ordinal": 232,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
new file mode 100644
index 0000000..7409f80
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
@@ -0,0 +1,176 @@
+# Volumes
+
+Volumes sync or created in HPE Morpheus Enterprise can be viewed in Infrastructure- Storage - Volumes. Volumes can be added for Storage Servers integrated with HPE Morpheus Enterprise in the Infrastructure- Storage - Servers section.
+
+## Volumes Types
+
+The available Volume Types list and filterable by are:
+
+- 3Par Volume
+- Alibaba Cloud SSD
+- Alibaba Efficiency Disk
+- Alibaba Cloud Disk
+- AWS gp2
+- AWS io1
+- AWS sc1
+- AWS st1
+- Azure Volume
+- Azure Disk
+- Bluemix Disk
+- Bluemix SAN
+- Bluemix SAN
+- CD ROM
+- DO Disk
+- ECS Block Storage
+- ECS Object Storage
+- ECS Shared File System
+- Floppy Disk
+- Google Standard
+- HP Enclosure Disk
+- Oracle iSCSI
+- Isilon NFS Volume
+- Nutanix IDE
+- Nutanix SATA
+- Nutanix SCSI
+- Open Telekom Volume
+- Openstack Disk
+- Openstack Volume
+- Oracle Block Volume
+- Oracle Disk
+- Oracle Virtual Volume
+- SCVMM Datastore
+- Softlayer Disk
+- Softlayer SAN
+- Softlayer SAN
+- Disk
+- UpCloud Disk
+- UpCloud MaxIOPS
+- NULL
+- NULL
+- VMWare Datastore
+- VMWare Disk
+
+## CREATE VOLUME
+
+At least one Storage Server Integration from Infrastructure- Storage - Servers is required to create volumes from Infrastructure- Storage - Volumes.
+
+### 3par
+
+#### About this task
+
+To Add a 3Par Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select 3Par from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the 3par Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   3Par Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+       PROVISION TYPE
+       :   - FULL
+           - TPVV
+           - SNP
+           - PEER
+           - UNKNOWN
+           - TDVV
+
+       Click COMPLETE
+       :   Select COMPLETE
+
+### Dell EMC ECS
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC ECS from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the DELL EMC ECS Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   ECS Block Storage ECS Object Storage ECS Shared File System
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+   Click COMPLETE
+   :   Select COMPLETE
+
+### Dell EMC Isilon
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC Isilon from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the Dell EMC Isilon Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   Isilon NFS Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       ALLOWED IP’s
+       :   Specify IP Addresses to limit accessibility to the File Share
+           :   Leave blank for open access
+               :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+   Click COMPLETE
+   :   Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json b/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
new file mode 100644
index 0000000..f264378
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+  "title": "Add Citrix NetScaler Integration",
+  "ordinal": 494,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html",
+  "topic_cluster": {
+    "clustering_title": "Add Citrix NetScaler Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md b/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
new file mode 100644
index 0000000..e3332c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
@@ -0,0 +1,48 @@
+# Add Citrix NetScaler Integration
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Citrix NetScaler**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Citrix LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E18D9A6C-6C61-4C00-9B2C-45F95C2FEEF7-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the NetScaler API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the NetScaler API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NetScaler service account username.
+   :   **PASSWORD \***: Enter NetScaler service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new NetScaler Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new NetScaler Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new NetScaler Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json b/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
new file mode 100644
index 0000000..f48089a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+  "title": "Add Virtual Image",
+  "ordinal": 151,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md b/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
new file mode 100644
index 0000000..5b416f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
@@ -0,0 +1,124 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be upload to HPE Morpheus Enterprise from local files or URL’s. Amazon and Azure Marketplace metadata can also be added to the Virtual Images library, enabling the creation of custom catalog Instance Type from Marketplace images (no image is transferred to HPE Morpheus Enterprise when adding Marketplace images).
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the HPE Morpheus Enterprise Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the HPE Morpheus Enterprise Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - Alibaba
+   - Amazon AMI
+   - Azure Marketplace
+   - Digital Ocean
+   - ISO
+   - PXE Boot
+   - QCOW2
+   - RAW
+   - VHD
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+## VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to HPE Morpheus Enterprise, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be sync’d into HPE Morpheus Enterprise.
+
+If all the vCenters are added as Clouds into HPE Morpheus Enterprise and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in HPE Morpheus Enterprise. This means that as you deploy to the various vCenter Clouds in HPE Morpheus Enterprise using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+This eliminates the need for creating multiple Node Types for each virtual image if the templates were named differently in each vCenter. This can reduce the overhead of maintaining multiple Node Types and reduces user selections. As well, this can reduce the cloning time of VMs by avoiding network transfers of images between geographic locations, ensuring the closest VM template is selected.
+
+HPE Morpheus Enterprise supports VMware Content Libraries storing VM templates and syncing into HPE Morpheus Enterprise, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Data Center** level object. The same process above applies to a single VMware cloud with multiple logical data centers. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..1a2a6f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 291,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..94bbb99
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,9 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html)**
+- **[Role Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
+- **[Creating Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json b/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
new file mode 100644
index 0000000..7a70bc9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+  "title": "Overview",
+  "ordinal": 254,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md b/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
new file mode 100644
index 0000000..c86a881
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
@@ -0,0 +1,15 @@
+# Overview
+
+HPE Morpheus Enterprise provides great monitoring features out of the box. Anything provisioned within HPE Morpheus Enterprise automatically gets a check created in the monitoring service. These checks are organized hierarchically in “Groups” and “Apps”. This makes it easy to gain a perspective as to what a customer or full stack facing impact is in the event of a particularly instance failure. This also takes into account redundancy layers when it comes to calculating the applications overall uptime percentage.
+
+HPE Morpheus Enterprise also includes a monitoring integration with ServiceNow.
+
+**Subtopics**  
+
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html)**
+- **[Checks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html)**
+- **[Monitoring Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html)**
+- **[Incidents](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html)**
+- **[Contacts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html)**
+- **[Alert Rules](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json b/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
new file mode 100644
index 0000000..b5a0bc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+  "title": "Editing and Deleting from the Self Service Catalog",
+  "ordinal": 143,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Deleting from the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md b/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
new file mode 100644
index 0000000..b04dae8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
@@ -0,0 +1,3 @@
+# Editing and Deleting from the Self Service Catalog
+
+Once created, Service Catalog items can be edited or deleted from the Catalog Items list view (Library > Blueprints > Catalog Items). Click the pencil icon in the relevant row to edit the Service Catalog item or the trash can icon to delete it. Alternatively, Service Catalog items can be made inactive to remove them as provisioning options rather than deleting them.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json b/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
new file mode 100644
index 0000000..0f8d540
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+  "title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+  "ordinal": 369,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md b/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
new file mode 100644
index 0000000..a101779
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
@@ -0,0 +1,115 @@
+# Backing Up and Restoring HPE Morpheus Enterprise Appliance
+
+HPE Morpheus Enterprise includes built-in tools for backing up managed Instances as well as the appliance itself. Use this guide to configure a location and schedule for backing up your HPE Morpheus Enterprise appliance. This guide also includes steps for restoring or migrating your appliance from the created backup. The steps are the same whether your appliance is deployed in a single node or distributed architecture.
+
+The built-in HPE Morpheus Enterprise appliance backup functionality backs up the MySql data. In addition to the database, it’s advisable to back up your shared storage (at `/var/opt/morpheus/morpheus-ui`) and the morpheus.rb configuration file.
+
+NOTE
+
+The destination HPE Morpheus Enterprise appliance must be running the same version as that which the backup was taken from.
+
+## Create A Backup Job
+
+### About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the execute scheduling section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+### Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
+
+## Integrate a Bucket or File Share
+
+### About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in storage documentation.
+
+## Configuring HPE Morpheus Enterprise Appliance Backup
+
+### About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+### Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+### Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
+
+## Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json b/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
new file mode 100644
index 0000000..9e91239
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+  "title": "Approvals",
+  "ordinal": 77,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html",
+  "topic_cluster": {
+    "clustering_title": "Approvals",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md b/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
new file mode 100644
index 0000000..d16dd46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
@@ -0,0 +1,161 @@
+# Approvals
+
+HPE Morpheus Enterprise and Service Now Approvals
+
+## Overview
+
+Policies can be created for Groups and Clouds to require approvals for actions with the built-in HPE Morpheus Enterprise approvals engine, or via a ServiceNow integration. Approvals can be configured for Provisioning and Lifecycle extensions.
+
+## Configuring Approvals
+
+### About this task
+
+Configuring HPE Morpheus Enterprise for Approvals
+
+To configure HPE Morpheus Enterprise for approvals:
+
+### Procedure
+
+1. Configure Roles for Approval access
+2. Optionally configure a ServiceNow Integration for ServiceNow approvals. 
+
+   - Please note ServiceNow integration is not required for Internal Approvals.
+3. Create approvals policies for: 
+
+   - Internal Approvals
+   - SNOW Approvals
+
+### Configure Roles
+
+Configure User Role access settings in Administration > Roles > (Role) > Operations: Approvals.
+
+- All Users with a Role applied containing Operations: Approvals set to Full will have approval authority, and be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to Read will be able to view Approval requests and history, but will not be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to None will not have access to the Operations: Approvals section, and such will not be able to see or act on approval requests.
+- Regardless of Role settings, any instance or app provisioned by any user to a group or cloud with an active Approval policy applied will require approval before the instance or app will provision.
+
+### ServiceNow Approvals
+
+#### About this task
+
+Configure ServiceNow integration for SNOW Approvals
+
+#### Procedure
+
+1. Navigate to Admin > Integrations
+2. Select + NEW INTEGRATION
+3. Select ServiceNow from the Type dropdown in the Integration modal and enter: 
+
+   - Name
+     :   Name of the integration in HPE Morpheus Enterprise
+   - Enabled
+     :   Leave checked to enable the integration.
+   - Host
+     :   URL of the ServiceNow host (ex: <https://ven0000.service-now.com>)
+   - User
+     :   A User in ServiceNow that is able to access the REST interface and create/update/delete incidents, requests, requested items, item options, catalog items, workflows, etc.
+   - Password
+     :   Password for User above
+4. Save Changes
+
+#### Results
+
+HPE Morpheus Enterprise then configures the integration with ServiceNow, syncs ServiceNow workflows which are available when creating approvals policies. (This process can take up to 5 minutes depending on the size of the workflow table in ServiceNow.)
+
+### Create Approval Policies
+
+- Policies applied to a Group are created in Infrastructure > Groups > (group) > Policies tab.
+- Policies applied to a Cloud are created in Infrastructure > Clouds > (cloud) > Policies tab.
+
+#### To create an Approval policy:
+
+##### Procedure
+
+1. Navigate to the Policies tab in the Group or Cloud to which the policy will apply.
+2. Select + ADD POLICY to open the New Policy wizard
+3. Select Provision Approval from the Type dropdown
+4. Add an optional description
+5. Leave Enabled selected for this Policy to be active once saved.
+   :   - Enabled can be deselected to disable to policy.
+6. In the config section, select either Internal Approvals or ServiceNow Approvals: 
+
+   - Internal Approvals
+     :   Approval requests will be managed within HPE Morpheus Enterprise via the Operations: Approvals section.
+   - ServiceNow Approvals
+     :   Approval requests will be managed with ServiceNow (SNOW). Please note a ServiceNow integration (Admin: Integrations) must be configured prior to SNOW Approval policy generation.
+
+         - For ServiceNow Approvals, select the appropriate ServiceNow workflow for this policy. Please note the workflows presented are created in ServiceNow and synced with HPE Morpheus Enterprise .
+7. Add the HPE Morpheus Enterprise Accounts to which this policy will apply, or leave the Accounts field blank to apply to all accounts.
+8. Save
+
+##### Results
+
+Upon saving, a new policy is created in the Group or Cloud Policies tab.
+
+NOTE
+
+SNOW Approvals will take a few moments to save as the policy is generated.
+
+## Managing Approval Requests
+
+Once Instance approval policies are added to a Group or Cloud, any Instance or App provisioned into that Group or Cloud will create an approval request entry in the Operations  >  Approvals section.
+
+NOTE
+
+User Role permission Operations: Approvals  >  FULL is required to manage Approvals.
+
+- To Approve, Deny, or Cancel an internal approval request, select the request and use the Actions dropdown.
+- To Cancel a ServiceNow Approval request, select the request and use the Actions dropdown. ServiceNow approvals are managed in ServiceNow.
+
+NOTE
+
+Instances requiring provisioning approval will have a PENDING status until approved.
+
+Each Approval Request will have:
+
+- Name: A name for the approval in HPE Morpheus Enterprise
+- Monthly Price (Est.): The estimated monthly price of the Instance to be provisioned
+- Request Type: What is being requested, such as Instance approval
+- External Name: For ServiceNow integrations, the name of the approval in the ServiceNow console
+- Type: Internal or ServiceNow
+- Status
+- Date Created
+- Requested By: The HPE Morpheus Enterprise user making the request
+- Actions dropdown (for internal approval requests)
+  :   - Approve
+      - Deny
+      - Cancel
+- Actions dropdown (for ServiceNow requests)
+  :   - Cancel
+
+NOTE
+
+The Approvals list view can be sorted by NAME, REQUEST TYPE, EXTERNAL NAME, DATE CREATED, and REQUESTED BY
+
+### Internal approval requests
+
+#### About this task
+
+To Approve, Deny or Cancel an Internal approval request:
+
+#### Procedure
+
+1. Navigate to Operations  >  Approvals
+2. Select the Name of the Approval request
+3. Select Actions on the far right of the request
+4. Select Approve, Deny, or Cancel from the Actions dropdown
+5. Select OK on the confirmation modal
+
+#### Results
+
+- When an Internal request is approved, the related instance will begin to provision immediately and the request will show approved.
+- When an Internal request is denied, the related instances status will change to Denied and the request will show Rejected in the Approvals section.
+- When an Internal request is canceled, the related related instances status will change to Cancelled and the request will be canceled.
+
+### ServiceNow Approval requests
+
+ServiceNow approval request are managed in ServiceNow. The process of approving or rejecting requests is determined by the ServiceNow Workflow selected when configuring the SNOW Approval policy. These Workflows are configured in ServiceNow.
+
+IMPORTANT
+
+HPE Morpheus Enterprise syncs with ServiceNow every 5 minutes. Once an Approval Request is Approved or Rejected in Service Now, it will take up to 5 minutes for the instance to respond accordingly, and the status for the approval request in the Approvals section in HPE Morpheus Enterprise to update.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json b/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
new file mode 100644
index 0000000..20ccd81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+  "title": "Nutanix Prism Central",
+  "ordinal": 468,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Central",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md b/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
new file mode 100644
index 0000000..7d6df89
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
@@ -0,0 +1,140 @@
+# Nutanix Prism Central
+
+HPE Morpheus Enterprise offers Nutanix Prism Central Cloud integration support through and official plugin. Adding the plugin to a HPE Morpheus Enterprise appliance adds a new Cloud integration type for Nutanix Prism Central. Download the plugin from the HPE Morpheus Enterprise [Plugin Exchange](https://share.morpheusdata.com/morpheus-nutanix-prism/about) and upload it to the appliance. Plugins are uploaded at Administration > Integrations > Plugins. See HPE Morpheus Enterprise [plugin documentation](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) for more details on adding plugins.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Project scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Creating a Minimal Service Account
+
+Integrating Nutanix Prism Central with HPE Morpheus Enterprise requires the use of a service account which has sufficient privileges to work with all Nutanix contructs that HPE Morpheus Enterprise touches. If possible, it’s recommended to use a service account with full administrator rights. This is because there is currently a bug on the Nutanix side that prevents limited roles from working with backups and snapshots. If you choose to use the minimal role permissions outlined in this section, those features will not work until the bug is resolved.
+
+### Recommended Minimal Service Account
+
+- The user belongs to the built-in “Prism Viewer” role
+- The user must be added to any Projects that need to be surfaced to the integration
+- The user must belong to a custom role with the permissions listed in the expandable section below
+
+#### Required Custom Role Permissions
+
+- Access Console VM
+- Allow Cross Cluster VM Migration
+- Allow VM Power Off
+- Allow VM Power On
+- Allow VM Reboot
+- Allow VM Reset
+- Allow VM Volume Group Connection
+- Clone VM
+- Copy Image Remote
+- Create External Subnet
+- Create Image
+- Create Layer2 Stretch
+- Create Overlay Subnet
+- Create Subnet
+- Create VM
+- Delete External Subnet
+- Delete Image
+- Delete Layer2 Stretch
+- Delete Subnet
+- Delete VM
+- Delete VM Recovery Point
+- Deploy VM Templates
+- Expand VM Disk Size
+- Export VM
+- Mount VM CDROM
+- Restore VM Recovery Point
+- Revert VM
+- Snapshot VM
+- Unmount VM CDROM
+- Update Cluster
+- Update Container Disks
+- Update External Subnet
+- Update Image
+- Update Layer2 Stretch
+- Update Overlay Subnet
+- Update Subnet
+- Update VM
+- Update VM Boot Config
+- Update VM Categories
+- Update VM CPU
+- Update VM Description
+- Update VM Disk List
+- Update VM GPU List
+- Update VM Memory
+- Update VM Memory Overcommit
+- Update VM Name
+- Update VM NGT Config
+- Update VM NIC List
+- Update VM Owner
+- Update VM Power State
+- Update VM Power State Mechanism
+- Update VM Project
+- Update VM Recovery Point
+- View Availability Zone
+- View Category
+- View Cluster
+- View Cluster Networking Capabilities
+- View Container
+- View Container Datastore
+- View Container Stats
+- View Dashboard
+- View External Subnet
+- View Host
+- View Image
+- View Layer2 Stretch
+- View Layer2 Stretch Related Entities
+- View Marketplace Item
+- View Name Category
+- View Network Gateway
+- View Overlay Subnet
+- View Project
+- View Storage Pool
+- View Subnet
+- View Value Category
+- View vCenter Cluster
+- View vCenter Container
+- View vCenter Node
+- View vCenter VM
+- View Virtual Switch
+- View VM
+- View VM Host Affinity Policy
+- View VM Recovery Point
+- View VM Templates
+- View VPC
+- View Vpn Connection
+
+IMPORTANT
+
+Due to a current Nutanix bug, non-administrator service accounts will not be able to utilize backup or snapshot features via HPE Morpheus Enterprise. Users who need these features should integrate using an administrator service account rather than the minimal user described here.
+
+## Adding a Nutanix Prism Central Cloud
+
+Adding Nutanix Prism Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the NPC appliance at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the Nutanix Prism Central plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), NUTANIX PRISM CENTRAL should be selectable as a Cloud type to add. Select it and click NEXT.
+
+![../../../_images/pickType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-75A6B1BB-774A-4E63-B8E7-70CF427BE53C-high.png)
+
+At minimum, it’s required to configure the following to add the new cloud:
+
+- **NAME:** A friendly name for the new NPC Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx:9440>)
+- **USERNAME:** Username for a Nutanix Prism Central service account (see the previous section for recommendations on service account user role configuration)
+- **PASSWORD:** The password for the service account
+- **VMM API VERSION:** Allows the user to select which VMM API versions their environment will support as HPE Morpheus Enterprise cannot auto-detect this and endpoint support differs between versions
+
+You’ll know the API URL and credentials have been entered correctly when the PROJECTS dropdown becomes populated. You may choose to scope Nutanix Prism Central Clouds to a specific project or scope the Cloud to all Projects. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+![../../../_images/configureCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B94510F8-00EB-4108-943D-8029EDB50DCD-high.png)
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json b/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
new file mode 100644
index 0000000..27024dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+  "title": "Creating Jobs",
+  "ordinal": 92,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md b/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
new file mode 100644
index 0000000..2f4ae05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
@@ -0,0 +1,63 @@
+# Creating Jobs
+
+## About this task
+
+NOTE
+
+Jobs require existing Tasks or Workflows. See the appropriate section of HPE Morpheus Enterprise docs for more on creating [Tasks](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#tasks) and [Workflows](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#workflows).
+
+To create a new Job:
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs
+2. Select + ADD
+3. Enter the following 
+
+   - NAME: Name of the Job in HPE Morpheus Enterprise
+   - JOB TYPE: A Task Job will execute a selected Task, a Workflow Job will execute a selected Workflow
+   - ENABLED: When checked, the Job will run as scheduled
+4. Select NEXT
+5. Configure the Job 
+
+   Task Jobs
+   :   TASK: Select target Task. If relevant to the Task, Input fields will be presented
+
+       SCHEDULE:
+       :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions > ExecuteDate And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually) Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+           NOTE
+
+           HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+
+       Workflow Jobs
+       :   WORKFLOW: Select target Workflow. If relevant to the Workflow, Input fields will be presented
+
+           SCHEDULE:
+           :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions  >  Execute
+
+               Date And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually)
+
+               Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+               NOTE
+
+               HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+6. Select NEXT
+7. Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json b/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
new file mode 100644
index 0000000..2a531ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+  "title": "Building Catalog Instances",
+  "ordinal": 140,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md b/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
new file mode 100644
index 0000000..b6e1690
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
@@ -0,0 +1,227 @@
+# Building Catalog Instances
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+An Instance in HPE Morpheus Enterprise is a set of one or more containers or virtual machines that correlate to a single, horizontally-scalable entity or service suite. From the Self Service section, we can pre-configure HPE Morpheus Enterprise Instances and present them to users viewing the Service Catalog Persona for one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Instance. The modal window will appear to configure and add a new catalog Instance.
+
+![../../_images/createInstance1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0D1DD7D2-5438-441D-9D5D-515401798FE8-high.png)
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When marked, this Catalog Item will be available from the provisioning Catalog view
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIG:** Enter, view, or edit Instance config here. Click CONFIGURE to build a base configuration through the HPE Morpheus Enterprise Instance wizard. After configuration through the Instance wizard, you may need to overwrite some static values in the Instance JSON body with calls to custom Input values. This allows your users to easily set the Instance Plan, Group, name, tags, or anything else they may need to control. Dynamic inputs are passed with the following syntax: “<%= customOptions.fieldName %>” where fieldName is the Field Name value set on the Input
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+## Using Forms with Catalog Items
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+Using Forms provides a number of advantages over using Inputs. Once the Form is selected, HPE Morpheus Enterprise helpfully provides a sidebar which contains all variables that can be consumed in the Instance config from the Form:
+
+![../../_images/catalogSidebar.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4820885E-F91A-4F9E-881B-4C5ECEC0F160-high.png)
+
+Many Form Inputs are designed to auto-inject themselves into the Instance config, you can see in the screenshot above that “AUTO INJECT” is checked. For variables that auto-inject, you do not need to override any static configuration with a variable call in order to consume that form value. In most cases, you should leave auto-inject turned on but the option is available to disable it for more advanced situations such as if you wanted to code custom logic into the variable call.
+
+Other types of Form Inputs do not auto-inject and, for these, you must override any static configuration in the Instance config with a variable call. For these situations, HPE Morpheus Enterprise helpfully provides the results of all variables so you can be sure you’re injecting the proper call. Click on the question mark (?) button immediately to the right of the “FORM VARIABLES” header to see a list of available variables and an example resolved variable. Variable tiles may be dragged from the sidebar into the CONFIG text area and a properly-formatted variable call will be inserted.
+
+![../../_images/optionTypeHelp.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF683E2D-8807-45D4-8E2B-B807A250D92B-high.png)
+
+As an example, see the configuration for an Ubuntu server in the expandable section below. You’ll notice in the configuration that a VMware Cloud, a specific Group, a specific Plan, and other static configurations are set. Since the Group, Cloud, Plan and other variables are able to be automatically injected, the user may select a different Group, Cloud, Plan, etc. from the form at provision time. The creator of the Catalog Item does not need to override those static configurations with variable calls.
+
+### Example Catalog Item Config
+
+```
+```
+{  
+  "hostName": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "metadata": "<%=customOptions.targetTags%>",  
+  "backup": {  
+    "backupRepository": 40,  
+    "veeamManagedServer": "",  
+    "jobSchedule": 2,  
+    "createBackup": true,  
+    "jobAction": "new",  
+    "jobRetentionCount": "3",  
+    "providerBackupType": 12,  
+    "target": 37006  
+  },  
+  "instance": {  
+    "userGroup": {  
+      "id": ""  
+    },  
+    "tags": "Forms,Test"  
+  },  
+  "defaultExpandAdvanced": false,  
+  "volumes": [  
+    {  
+      "maxIOPS": null,  
+      "displayOrder": 0,  
+      "unitNumber": "0",  
+      "minStorage": 5368709120,  
+      "configurableIOPS": false,  
+      "uuid": "a6781cc1-31ca-406b-aea0-e33ea1a18b7f",  
+      "controllerMountPoint": "2200223:0:4:0",  
+      "internalId": "[ESXi-DC2-QA-LUN01] Morpheus Ubuntu 22.04 20230307/Morpheus Ubuntu 22.04 20230307.vmdk",  
+      "id": 5255832,  
+      "datastoreId": "autoCluster",  
+      "maxStorage": 26843545600,  
+      "volumeCustomizable": true,  
+      "readonlyName": false,  
+      "controllerId": 2200223,  
+      "externalId": "2000",  
+      "virtualImageId": 1418543,  
+      "vId": 1418543,  
+      "size": 25,  
+      "name": "root",  
+      "planResizable": true,  
+      "rootVolume": true,  
+      "storageType": 1,  
+      "typeId": 1,  
+      "resizeable": true,  
+      "uniqueId": null  
+    }  
+  ],  
+  "type": "ubuntu",  
+  "ports": [  
+    {  
+      "code": "ubuntu.22",  
+      "visible": true,  
+      "internalPort": 22,  
+      "loadBalancePort": null,  
+      "loadBalanceProtocol": null,  
+      "sortOrder": 1,  
+      "name": "SSH",  
+      "id": 7,  
+      "shortName": "ssh",  
+      "externalPort": 22,  
+      "loadBalance": false  
+    }  
+  ],  
+  "version": "22.04",  
+  "hideLock": true,  
+  "cloud": {  
+    "name": "QA VMware",  
+    "id": 26324  
+  },  
+  "layout": {  
+    "code": "vmware-ubuntu-22.04-single",  
+    "id": 2608414  
+  },  
+  "showScale": false,  
+  "environment": "2",  
+  "networkInterfaces": [  
+    {  
+      "ipMode": "",  
+      "primaryInterface": true,  
+      "showNetworkPoolLabel": true,  
+      "showNetworkDhcpLabel": false,  
+      "network": {  
+        "idName": "VLAN0002 - Internal Server",  
+        "pool": {  
+          "name": "10.32.20.0 /22",  
+          "id": 18823  
+        },  
+        "id": "network-173431",  
+        "hasPool": false  
+      },  
+      "networkInterfaceTypeId": 4,  
+      "networkInterfaceTypeIdName": "VMXNET 3"  
+    }  
+  ],  
+  "copies": 1,  
+  "loadBalancer": [],  
+  "name": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "storageControllers": [  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 0,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "IDE 0",  
+      "typeId": 2,  
+      "id": 1729031,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 1,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "1",  
+      "removable": false,  
+      "name": "IDE 1",  
+      "typeId": 2,  
+      "id": 1729032,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "SCSI LSI Logic Parallel",  
+      "maxDevices": 15,  
+      "displayOrder": 2,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": 7,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "SCSI 0",  
+      "typeId": 4,  
+      "id": 1729030,  
+      "category": "scsi"  
+    }  
+  ],  
+  "config": {  
+    "poolProviderType": null,  
+    "isVpcSelectable": true,  
+    "smbiosAssetTag": null,  
+    "isEC2": false,  
+    "resourcePoolId": "pool-139625",  
+    "hostId": null,  
+    "createUser": true,  
+    "nestedVirtualization": null,  
+    "vmwareFolderId": "group-v80",  
+    "noAgent": false  
+  },  
+  "plan": {  
+    "code": "vm-8192",  
+    "id": 149  
+  },  
+  "group": {  
+    "name": "All Clouds",  
+    "id": "2"  
+  }  
+}
+```
+```
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json b/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
new file mode 100644
index 0000000..4255f41
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+  "title": "Nesting Workflows",
+  "ordinal": 119,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html",
+  "topic_cluster": {
+    "clustering_title": "Nesting Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md b/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
new file mode 100644
index 0000000..6c21ec8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
@@ -0,0 +1,9 @@
+# Nesting Workflows
+
+HPE Morpheus Enterprise allows Workflows to be nested for easier Workflow creation when many Workflows are used in an environment which have only slight differences or which are made up of common pieces. Nestable Workflows are created like any other Operational Workflow. Once the Workflow is saved, it can be embedded into a special Task type called “Nested Workflow.” A Nested Workflow-type Task simply references an Operational Workflow which may need to be used within other Workflows. Once Nested Workflow Tasks are created they can be used as part of any new Operational or Provisioning Workflows that are created thereafter (or may be added to existing Workflows too). For more on creating Tasks, see HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#tasks).
+
+NOTE
+
+Results from prior Tasks are still accessed using the same syntax even when a prior Task is embedded in a Nested Workflow. Additional syntax to reference the Nested Workflow Task or the Workflow itself are not needed. See HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#task-results) for more on chaining Task results.
+
+Nested Workflows Video Demo
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json b/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
new file mode 100644
index 0000000..bf1ee2d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+  "title": "Contacts",
+  "ordinal": 260,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html",
+  "topic_cluster": {
+    "clustering_title": "Contacts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md b/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
new file mode 100644
index 0000000..f313cc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
@@ -0,0 +1,10 @@
+# Contacts
+
+To configure user notifications, a contact must first be created in Monitoring  >  Contacts. These contacts can be one of a few types:
+
+- **Contact:** Used for either Email or SMS
+- **Web Hook:** Used for posting a notification to a web endpoint or Alert Ops
+- **Slack Hook:** Used for posting notifications to a Slack channel (ex. [https://slack.com/[Slack](https://slack.com/%5BSlack)])
+- **VictorOps:** Provides a web post format consistent with the required notification format for Victor Ops.
+
+Most of these options provide convenient examples and information when configuring the contact. Once they are configured, contacts can freely be used to build Alert Rules.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json b/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
new file mode 100644
index 0000000..691ae66
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+  "title": "Uploading OS Images Using S3-Compatible Object Storage",
+  "ordinal": 408,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md b/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
new file mode 100644
index 0000000..57f63ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using S3-Compatible Object Storage
+
+## About this task
+
+S3-compatible object storage (such as MinIO) provides scalable and durable storage for OS images.
+
+## Procedure
+
+1. Configure an S3 storage bucket under Infrastructure > Storage > Buckets.
+2. Provide access credentials with read/write permissions.
+3. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+4. Confirm successful upload and activation.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json b/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
new file mode 100644
index 0000000..f118694
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+  "title": "Cloud Resource Tagging with Morpheus",
+  "ordinal": 370,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Resource Tagging with Morpheus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md b/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
new file mode 100644
index 0000000..a5dbb7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
@@ -0,0 +1,91 @@
+# Cloud Resource Tagging with Morpheus
+
+## Introduction
+
+As organizations scale their cloud environments, they often need to devise methodologies for organizing those resources. Tags consist of key and optional value pairs which make it easier to search for or filter your cloud resources based on categories relevant to the organization. While each public or private cloud handles tagging slightly differently, Morpheus removes that complexity and differentiation by handling tags in a consistent way across clouds. In addition, the Morpheus policy engine gives administrators tools to set up guard rails and ensure cloud resource tagging is handled consistently with each provisioning.
+
+This guide will go through Morpheus tagging features and best practices, as well as include provisioning examples from some of the most commonly integrated clouds.
+
+NOTE
+
+Tag syncing is bi-directional in Morpheus for supported clouds. Tag syncing is currently supported in Amazon, Azure, Google, VMware, and Alibaba Clouds.
+
+## Tagging on Provisioning
+
+In the simplest use case, tags can be entered manually in most provisioning scenarios. For example, on the Configure tab of the Create Instance wizard, the user can expand the Tags section and enter as many Tags as he or she needs to comply with organization practices.
+
+![../../_images/1_manual_tag.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A9D53B5E-99C6-49D9-9F6E-8E1A18C1CFA7-high.png)
+
+Once the resource is deployed, Tags are synced and applied to the provisioned machine in the relevant cloud. Tags are shown on the Instance detail page in Morpheus and can also be confirmed in the cloud console if desired. Tag syncing is also a two-way street in that any tag updates applied within Morpheus or within the cloud console will be reflected everywhere.
+
+NOTE
+
+Tag updates made in the cloud console may take up to five minutes to be reflected in Morpheus UI following the next sync of cloud data.
+
+## Custom Instance Types and Tagging
+
+Manually tagging resources as described in the previous section will work in some cases but many administrators will likely need to pre-seed the provisioning wizards with tagging prompts or build dropdown lists for tag values. This is accomplished in Morpheus through the use of custom Instance Types, Inputs, and Option Lists.
+
+To get started, first create an Option List to hold dropdown or typeahead sets of available key values if needed based on organizational tagging policy. If the tag value field should be manually entered at provision time or if the value field is to be left blank, this step can be skipped. Option Lists are created and stored in the Morpheus Library (Library). They can be populated manually by entering CSV or JSON datasets as shown in the example below. They can also be dynamically populated through Morpheus API or REST calls.
+
+![../../_images/2_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5216C432-43A8-4C56-9D07-4C3D728D757A-high.png)
+
+With the set of possible values defined (if needed), we next create an Input to prompt the user for tag input when provisioning relevant Instance types. Inputs are also housed in the Morpheus Library (Library).
+
+It’s important to note the value entered for the FIELD NAME on the new Input will be set as the tag key. The EXPORT AS TAG box should also be marked. By default, the TYPE value is Text. This is appropriate when the user should be prompted with a free text field at provision time to enter a tag value. To tie this Input to the Option List that was just created (if needed), change the TYPE value to Select List or Typeahead. Typeahead works best for very long lists while Select List is often a better user experience for lists of a more manageable size. Set the Option List we created in the previous step in the OPTION LIST value (if needed).
+
+![../../_images/3_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FC1E55AE-02D8-40CB-9BE5-E0ED9106E1E7-high.png)
+
+At this point, we are ready to add this Input to any custom Instance Types or Layouts. When those Instance Types or Layouts are provisioned, the values input by the user become tags associated with the created cloud resources. By setting the Input on an Instance Type, the tag selection appears when provisioning all associated Layouts. Alternatively, if the Input is set on individual Layouts, it will only appear when those Layouts are provisioned.
+
+Instance Types and Layouts are also stored in the Morpheus Library (Library). By opening up any custom Instance Type, we can add the Input we just created when editing the Instance Type. Additionally, we can drill into associated Layouts and apply the Input to selected Layouts if that’s more appropriate.
+
+![../../_images/4_instance_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3F4F0DA9-5384-489B-AC6F-C33024D7F939-high.png)
+
+Going forward, each time the chosen Instance Type or Layout is provisioned, the user will be prompted to enter relevant tag selections. We can even require the user input these values or govern their inputs through tagging policies which will be discussed in the next section.
+
+## Instituting Tagging Policies
+
+If needed, Morpheus allows cloud resource tagging to be governed through its native policy engine. Like other policies, tag policies are added from Administration > Policies. By creating a new policy and setting the TYPE to Tags, the relevant fields are revealed.
+
+NOTE
+
+Tag policy scanning and enforcement is only currently supported for Azure, Amazon AWS, VMware, and Google Cloud Platform clouds. Additional Clouds may be supported in the future.
+
+With a tag policy, we can choose to enforce the policy on a strict or passive basis by marking or unmarking the STRICT ENFORCEMENT box. Strictly enforced tagging policies will not allow provisioning to proceed in supported clouds if the policy requirements are not met. If we opt to enforce the policy passively, a warning banner will appear on the detail page of any server that does not meet policy requirements. Additionally, existing servers in supported clouds will be scanned and those which do not meet policy requirements will also receive the warning banner.
+
+A tag policy must be given a KEY value. If we define only a KEY value, the policy will look for a tag with that key and any (or no) value. Alternatively, we can select any pre-existing Option List as the VALUE LIST to require the tag contain a value that exists in that list or even enter a specific VALUE.
+
+Finally, like other HPE Morpheus Enterprise policies, we can choose to scope it globally, by group, by cloud, or by user. Primary Tenant administrators can also choose to scope the policy to one or more Subtenants.
+
+![../../_images/5_tag_policy_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B7104343-4BFF-4072-808C-403A0182CD17-high.png)
+
+## Tagging in Action
+
+With the prep work complete, we can take a look at our Inputs in action at provision time. In this example case, several Inputs have been created and applied to one custom Instance Type. The example Instance Type has three associated CentOS Layouts, one for AWS, one for VMware, and one for Azure. Regardless of the selected Layout, users are prompted to fill the same tag fields and our tagging remains consistent regardless of the user who is provisioning a new resource at the time.
+
+## Tagging and AWS
+
+When provisioning my CentOS Instance Type with an Amazon Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/6_aws_provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-45A12345-D313-46FB-9806-C09FB33C0A9B-high.png)
+
+In the AWS web console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to the AWS web console. The opposite is also true.
+
+![../../_images/7_aws_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9164DCFD-602C-4B6B-ADA7-B389FB81215E-high.png)
+
+## Tagging and VMware
+
+When provisioning my CentOS Instance Type with a VMware Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/8_vmware_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-264EA4E8-7CD7-45D2-9CE1-CF46AC2E0598-high.png)
+
+In the VMware console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to VMware. The opposite is also true.
+
+## Tagging and Azure
+
+When provisioning my CentOS Instance Type with an Azure Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/9_azure_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-62F1E8EF-C109-4E41-BAF8-C76B9E31E27F-high.png)
+
+In the Azure console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to Azure. The opposite is also true.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json b/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
new file mode 100644
index 0000000..cf5f8f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+  "title": "Resizing Volume",
+  "ordinal": 444,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html",
+  "topic_cluster": {
+    "clustering_title": "Resizing Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md b/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
new file mode 100644
index 0000000..8bc2590
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
@@ -0,0 +1,12 @@
+# Resizing Volume
+
+## About this task
+
+This procedure allows the user to resize a volume. Volume size can only be increased. A rescan is required on the server OS to see the increased size.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Resize for the volume to be deleted.
+3. Specify the new size and click Resize.   
+   ![Resize volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9E3B3BDC-4EE0-491F-B1FC-BDFF31E19553-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json b/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
new file mode 100644
index 0000000..5dd0f23
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+  "title": "Specifying Network Usage",
+  "ordinal": 435,
+  "parent_title": "Network Usage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html",
+  "topic_cluster": {
+    "clustering_title": "Specifying Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md b/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
new file mode 100644
index 0000000..43798aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
@@ -0,0 +1,21 @@
+# Specifying Network Usage
+
+## About this task
+
+Perform the following to specify networks used during instance provisioning:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Provisioning > Instances.
+3. Select **HPE**Bare Metal (ILO) Server as the type.
+4. Click Next.
+5. Specify a Group, Cloud, and a Name for the Instance.
+6. Click Next.
+7. Select a Network.
+8. Select an interface type (Bond/Physical).
+9. Specify any required virtual interface.
+10. Click Next and complete. ![Instance Bond Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5359D1DC-7863-49EC-9F61-4C14BFC8F0F1-high.png)
+
+    For physical interfaces, the interfaces represent the physical ports in their display order. Virtual networks specify that tagged networks under the primary network specified are to be configured on the server OS with an IP interface. If any of those tagged networks are not required to be configured on the server OS as an IP interface, do not specify a virtual interface for those.   
+    ![InstancePhysicalNetwork](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CA592D7B-4562-4AA1-8A46-BF66F13DC305-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.json b/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.json
new file mode 100644
index 0000000..8accc92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+  "title": "Dashboard",
+  "ordinal": 54,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2277183A-E315-4439-A885-C111A77C7154.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.md b/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.md
new file mode 100644
index 0000000..0fcb616
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2277183A-E315-4439-A885-C111A77C7154.md
@@ -0,0 +1,80 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within HPE Morpheus Enterprise UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+NOTE
+
+Opensearch 7.16+ is required for the Log Trends Dashboard panel to work. When using versions below 7.16 you will see error messages in logs due to this panel missing needed dependencies to work correctly but these errors may be safely ignored.
+
+## Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of HPE Morpheus Enterprise user accounts
+
+## System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [HPE Morpheus Enterprise Health](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html#GUID-E6FCD7DB-6973-459F-9EBC-3088B211CF1C).
+
+## Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
+
+## Alarms
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
+
+## Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
+
+## Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+## Daily Cloud Instances
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
+
+## Group Workloads
+
+The instantaneous count of host or container records broken down by Group association
+
+## Cloud Workloads
+
+The instantaneous count of host or container records broken down by Cloud association
+
+## Cluster Workloads
+
+The instantaneous count of managed containers broken down by Cluster association
+
+![../_images/dashboard2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1B7CFE86-1657-4EF7-B515-E3D104CDB5D2-high.png)
+
+## Log History
+
+Log History shows a snapshot of various time segments throughout the current day and the number of logs generated during each segment. Hover over any bar on the graph to see a breakdown in severity of the logs within each segment
+
+## Log Trends
+
+Log Trends identifies and lists repeated messages found in recent longs. If desired, this view can be filtered to show only Error or Warning-level log messages
+
+## Job Executions
+
+Displays the number of successful and unsuccessful Job executions over the last day, week or month
+
+## Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
+
+## Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
+
+## Activity
+
+The activity list displays the last few events that have taken place in HPE Morpheus Enterprise by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json b/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
new file mode 100644
index 0000000..d861376
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+  "title": "SCVMM",
+  "ordinal": 469,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.html",
+  "topic_cluster": {
+    "clustering_title": "SCVMM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md b/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
new file mode 100644
index 0000000..dd30a9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
@@ -0,0 +1,240 @@
+# SCVMM
+
+NOTE
+
+HPE Morpheus Enterprise supports SCVMM cloud deployment as HA SCVMM failover cluster. You must follow the process to have a singular agent API key and only one agent online at a time.
+
+## Requirements
+
+- Access to SCVMM host on port 5985 for Agent installation
+- Access to Hyper-V host on port 2179 for hypervisor console access
+- HPE Morpheus Enterprise Agent installation (installed on the target SCVMM host via port 5985 and WinRM)
+- User with administrator privileges
+
+## Agent Requirement
+
+SCVMM and Hyper-V integrations utilize the HPE Morpheus Enterprise Agent for communication with the HPE Morpheus Enterprise appliance, making the HPE Morpheus Enterprise Agent required. This also means SCVMM and Hyper-V Clouds can only point to one HPE Morpheus Enterprise Appliance at any given time. If another HPE Morpheus Enterprise Appliance adds an SCVMM or Hyper-V Cloud thats is already managed by another HPE Morpheus Enterprise Appliance, the HPE Morpheus Enterprise Agent appliance\_url will be updated to point to the new HPE Morpheus Enterprise appliance\_url, and the previous HPE Morpheus Enterprise Appliance will no longer be able to communicate with the SCVMM Cloud or Hyper-V Cloud until the Agent configuration is updated to point to the previous appliance again. In HPE Morpheus Enterprise version 4.2.1 and higher, multiple HPE Morpheus Enterprise clouds can be created by integrating with the same SCVMM host. This allows users to create separate Clouds with are scoped to different SCVMM Cloud, Host and/or Cluster combinations.
+
+## Add a SCVMM Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select SCVMM, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   NOTE
+
+   You will need to open port 5985 in order for HPE Morpheus Enterprise to communicate to SCVMM. You will also want to make sure the SCVMM Controller has WinRM enabled.
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   SCVMM HOST
+   :   IP address or URL of SCVMM host server
+
+   USERNAME
+   :   SCVMM Username, for example: svc.scvmm
+
+   PASSWORD
+   :   SCVMM user Password
+
+   CLOUD
+   :   To scope the SCVMM Integration to a single Cloud, select it from the Cloud dropdown, which populates after establishing communication and authorization over port 5985 using the supplied username and password. To scope to all Clouds, leave the dropdown selection as `Select Cloud`
+
+   HOST GROUP
+   :   To scope the SCVMM Integration to a single host group, select a host group from the dropdown list. To scope to all host groups, select `All Hosts`
+
+   CLUSTER
+   :   To scope the SCVMM Integration to a single cluster, select a cluster from the dropdown list. To scope to all host groups, select `All`
+
+   LIBRARY SHARE
+   :   Select a Library Share to be used with the cloud integration
+
+   SHARED CONTROLLER
+   :   When creating additional HPE Morpheus Enterprise clouds that point to an SCVMM host already integrated with this appliance, select the appropriate shared controller value from the dropdown.
+
+       IMPORTANT
+
+       Only set `SHARED CONTROLLER` on additional HPE Morpheus Enterprise clouds and not on the Primary HPE Morpheus Enterprise SCVMM cloud. Failure to set the `SHARED CONTROLLER` on secondary HPE Morpheus Enterprise clouds pointed to the same SCVMM cluster will cause agent comm issues resulting in provisioning failures.
+
+       WORKING PATH
+       :   Path for HPE Morpheus Enterprise to write to, for example `c:\cloud`
+
+       DISK PATH
+       :   Path for Virtual Disks, for example `c:\virtualdisks`
+
+       HIDE HOST SELECTION FROM USERS
+       :   Prevents host selection from appearing in provisioning wizards
+
+       INVENTORY EXISTING INSTANCES
+       :   Enable for HPE Morpheus Enterprise to automatically discover existing VMs in the scoped resources
+
+       ENABLE HYPERVISOR CONSOLE
+       :   Enable to use VNC Hypervisor Console for HPE Morpheus Enterprise console connection as opposed to the default SSH and RDP console connection methods. Requires resolution of all Hyper-V host names and access over port 2179 from the HPE Morpheus Enterprise appliance to Hyper-V hosts.
+
+       SCVMM Specific Advanced Options
+
+       INSTALL AGENT
+       :   Enabled by default, INSTALL AGENT installs the HPE Morpheus Enterprise agent on the scvmm Controller when adding the cloud, which is required for full functionally unless using a shared controller in which scenario the agent would already be installed on the scvmm controller node. Disabling INSTALL AGENT on the cloud config when not using a shared controller will remove the ability to provision to the cloud.
+
+       Advanced Options
+
+       DOMAIN
+       :   Specify a default domain for instances provisioned to this Cloud.
+
+       SCALE PRIORITY
+       :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+       APPLIANCE URL
+       :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+       TIME ZONE
+       :   Configures the time zone on provisioned VM’s if necessary.
+
+       DATACENTER ID
+       :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+       NETWORK MODE
+       :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+       LOCAL FIREWALL
+       :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+       SECURITY SERVER
+       :   Security Server setting is for Security Service Integrations such as ACI
+
+       TRUST PROVIDER
+       :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+       STORAGE MODE
+       :   Single Disk, LVM or Clustered
+
+       BACKUP PROVIDER
+       :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+       REPLICATION PROVIDER
+       :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+       GUIDANCE
+       :   Enable Guidance recommendations on cloud resources.
+
+       COSTING
+       :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+       DNS INTEGRATION
+       :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+       SERVICE REGISTRY
+       :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+       CONFIG MANAGEMENT
+       :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+       CMDB
+       :   Select CMDB Integration to automatically update selected CMDB.
+
+       CMDB DISCOVERY
+       :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+       CHANGE MANAGEMENT
+       :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+       AGENT INSTALL MODE
+       :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+           - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+       VDI GATEWAY
+       :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+       CUSTOM LOGOS
+
+       When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+       INVENTORY OPTIONS
+
+       Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+       - Service Plans
+       - Resource Pools
+       - Networks
+       - Security Groups
+       - Datastores
+       - Folders
+
+       Provisioning Command
+
+       PROXY
+       :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+       Bypass Proxy for Appliance URL
+       :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+       NO PROXY
+       :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+       USER DATA (LINUX)
+       :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After clicking NEXT, the new Cloud can be added to a Group or configured with additional advanced options.
+
+### Create Ubuntu 22.04 image template
+
+Use the template creation steps detailed in the below article:
+
+https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006774en\_us&page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD\_2.html#ariaid-title1
+
+with the exceptions as below:
+
+1. Enable required VM integration services before deploying the VM
+
+- Naviagate to "Hardware Configuration" -> "Advanced" -> "Integration Services". Check the checkbox "Guest services" under "Services".
+
+2. After the the step titled "Complete the installation process and reboot the machine. Update the package list and apply any upgrades", execute the below (to install a collection of utilities for hypervisor integration) :
+
+```
+```
+sudo apt install -y linux-cloud-tools-$(uname -r) linux-tools-$(uname -r)
+```
+```
+
+Follow the subsequent steps as in the article.
+
+**Create windows template**
+
+Create a new machine in SCVMM and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+**Procedure**
+
+- Apply any service packs / updates to the operating system.
+- Install .Net at least 4.5.2
+- Install SCVMM Agent
+- Ensure Windows Firewall will allow WinRM connections.
+- Shutdown the virtual machine and convert to a template.
+
+  Note : Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json b/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
new file mode 100644
index 0000000..41315ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+  "title": "Repositories",
+  "ordinal": 97,
+  "parent_title": "Code",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html",
+  "topic_cluster": {
+    "clustering_title": "Repositories",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md b/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
new file mode 100644
index 0000000..5816d96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
@@ -0,0 +1,128 @@
+# Repositories
+
+The Provisioning ‣ Code ‣ Repositories section contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repository folders and files, view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. This section also handles Import/Export functionality which allows users to backup HPE Morpheus Enterprise items (Tasks, Library Items, etc.) as code in a repository which can also be imported into another appliance, if desired.
+
+- Browse integrated repositories
+- View repo files
+- Switch branches
+- Trigger repo refreshes
+- Filter by Integration, Organization or Text search
+- Create Custom Views
+- Create Tasks from repo files
+- Create Spec Templates from repo files
+
+## Role Permissions
+
+Access and capabilities for the **Repositories** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Administration: Users`
+:   - None: Can view repo list but cannot browse repo folder and file names, select branch, refresh repositories or access/view file contents
+    - Read or Full: Can view repo list, browse repo folder and file names, select branch, refresh repositories. Cannot access/view file contents without Read or Full level permission on `Provisioning: Code Repositories`
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents
+
+Role: Feature Access: `Provisioning: Tasks`
+:   - None: Cannot create Tasks from repo files in repository browser
+    - Read or Full: Can create Tasks from repo files in repository browser
+
+Role: Feature Access: `Provisioning: Library`
+:   - None: Cannot create Spec Templates from files in repository browser
+    - Read or Full: Can create Spec Templates from files in repository browser
+
+## List Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Users with sufficient permissions will see a list view of all integrated code repositories
+4. Use the Search, Integrations or Organizations filter to filter listed repositories
+
+### Results
+
+TIP
+
+Select the gear icon ⚙ in the top right of the repos list view to create and save custom list views.
+
+## Refresh Repository
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ACTIONS ▿ > `Refresh`
+
+## Browse Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Users with sufficient permissions can browse repo folder and file names, select branches, and refresh repositories. Users can access/view file contents with Read or Full level permission on `Provisioning: Code Repositories`
+5. Select target folder icon to drill into the folder
+
+## View Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ℹ icon to right of target file name
+
+### Results
+
+NOTE
+
+Users can access/view file contents only with Read or Full level permission on `Provisioning: Code Repositories`. File contents displayed is from last repo sync. Refresh repo to ensure current version for recent commits.
+
+## Create Task from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of compatible target file name
+5. Select target task type from available actions
+6. Complete the NEW TASK wizard to create a new Task. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Shell and Powershell Tasks types can be created from the code repo browser in v8.0.7. Ensure file compatibility with target Task type.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Tasks`.
+
+## Create Spec Template from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of target file name
+5. Select target spec template type from available actions
+6. Complete the NEW SPEC TEMPLATE wizard to create a new Spec Template. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Terraform spec template types can be created from the code repo browser in v8.0.7. Other spec template types can be created from repo files by changing the TYPE field in the NEW SPEC TEMPLATE wizard.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Templates`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..4f11e1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 263,
+  "parent_title": "Tools",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..7fbcf01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,199 @@
+# Cypher
+
+## Overview
+
+Cypher at its core is a secure Key/Value store. But what makes cypher useful is the ability to securely store or generate credentials to connect to your instances. Not only are these credentials encrypted but by using a cypher you don’t have to burn in connection credentials between instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
+
+## Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between HPE Morpheus Enterprise and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
+
+## Creating Cypher Keys
+
+### Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
+
+## Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
+
+## tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
+
+## Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your HPE Morpheus Enterprise user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
+
+## UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than HPE Morpheus Enterprise. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the HPE Morpheus Enterprise Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
+
+## Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
+
+## Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another HPE Morpheus Enterprise user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks and Workflows that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
+
+NOTE
+
+You can reference the original owner of a workflow so that keys can be used in a subtenant. Example `PASSWORD=<%=cypher.read('secret/myuserpassword')%>` could be changed to `PASSWORD=<%=cypher.read('secret/myuserpassword',true)%>` within a library or a workflow and the true means OWNER true. This will keep that key in the master tenants cypher store.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json b/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
new file mode 100644
index 0000000..e34db71
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+  "title": "Add NSX advanced load balancer",
+  "ordinal": 502,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX advanced load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md b/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
new file mode 100644
index 0000000..462b75b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
@@ -0,0 +1,34 @@
+# Add NSX advanced load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX Advanced Load Balancer**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX adv LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0257709D-4A5C-441C-9E7B-C5793572100E-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   API HOST \*
+   :   Enter the API host name.
+
+   API PORT \*
+   :   Enter the PORT number.
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NSX service account username.
+   :   **PASSWORD \***: Enter NSX service account password.
+
+   AVI CLOUD
+   :   From the drop-down list, select the AVI cloud (VMware Avi Load Balancer).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json b/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
new file mode 100644
index 0000000..99866c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+  "title": "Delete Workflow",
+  "ordinal": 121,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md b/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
new file mode 100644
index 0000000..2b5e366
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
@@ -0,0 +1,8 @@
+# Delete Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Delete icon on the row of the workflow you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json b/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
new file mode 100644
index 0000000..39e240a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+  "title": "Canonical MAAS",
+  "ordinal": 460,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.html",
+  "topic_cluster": {
+    "clustering_title": "Canonical MAAS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md b/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
new file mode 100644
index 0000000..7fab104
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
@@ -0,0 +1,42 @@
+# Canonical MAAS
+
+MAAS from Canonical is an open-source server orchestration tool. It’s designed to allow administrators to build a datacenter from on-premises, bare-metal servers where large networks of individual units can be discovered, deployed, and reconfigured.
+
+## Integrating MAAS and HPE Morpheus Enterprise
+
+### About this task
+
+Integrating MAAS with HPE Morpheus Enterprise is a simple process requiring the MAAS API URL and API Key. We’ll start by gathering what we need from the MAAS UI, then move back into HPE Morpheus Enterprise to store the required details.
+
+We can gather the API key by clicking on the username in the upper-right corner of the MAAS UI window. From this preferences page, click on “API keys” as shown in the screenshot:
+
+![../../../_images/1prefPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2CE6F9DA-2A53-497D-B397-89CE446156D7-high.png)
+
+From the API keys page, select the displayed key and copy it. Alternatively, you can click the copy button in the UI to add the full key to your clipboard. Store this key in an accessible location for a later step.
+
+![../../../_images/2maasApi.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C7F62A15-E82D-479B-9D76-2A83365CD918-high.png)
+
+In addition to the API key, we need the MAAS API URL. As entered in HPE Morpheus Enterprise, the value will be like the following example: `http://<maas-hostname-or-ip>:5240`. We’ll enter the API URL into HPE Morpheus Enterprise duriong the next step.
+
+In HPE Morpheus Enterprise, navigate to the list of integrated Clouds and start a new MAAS Cloud integration:
+
+### Procedure
+
+1. Infrastructure > Clouds
+2. Click + ADD
+3. Select “MAAS”
+4. Click NEXT
+
+### Results
+
+On the “CREATE CLOUD” modal, you must at least give a friendly name for the Cloud in HPE Morpheus Enterprise, MAAS API URL and API KEY. An example is shown below:
+
+![../../../_images/3createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AA9E6041-8181-4D62-8EC4-516C7234E0FF-high.png)
+
+TIP
+
+You’ll know the credentials are entered correctly when your list of MAAS resource pools is synced in as you can see in the example screenshot.
+
+Click NEXT and add this new Cloud to an existing Group or create a new Group for it. Once you advanced past the end of the wizard, the Cloud is added and HPE Morpheus Enterprise begins to inventory (if you’ve opted to inventory when adding the Cloud).
+
+![../../../_images/4cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-598C2A66-38D0-4401-B1C5-14CF91A97474-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json b/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
new file mode 100644
index 0000000..8c2104d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+  "title": "Active Directory",
+  "ordinal": 281,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html",
+  "topic_cluster": {
+    "clustering_title": "Active Directory",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md b/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
new file mode 100644
index 0000000..9bf18f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
@@ -0,0 +1,130 @@
+# Active Directory
+
+## Overview
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+## How It Works
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+## Example Integration
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in-built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+## Adding an Active Directory Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following: 
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES. 
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Troubleshooting
+
+### About this task
+
+If you’re unable to get the Active Directory integration to work, the following troubleshooting steps may be useful to ensure your appliance can talk to the Active Directory server.
+
+### Procedure
+
+1. Open firewall ports 
+
+   Source: HPE Morpheus Enterprise appliance Destination: AD server’s FQDN or IP address Non-SSL AD integration: TCP-389 SSL AD integration: TCP-636
+2. Checking open LDAP connections from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following:
+
+   ```
+   ```
+   $ sudo lsof i- | grep :ldap
+   ```
+   ```
+3. Check LDAP connectivity from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following. Be sure to replace the placeholder values in the command with the correct values for your environment:
+
+   ```
+   ```
+   $ ldapsearch   -x -h xx.xx.xx.xx -D "binding-user@acme.com" -W -b "cn=users,dc=acme,dc=com"
+   ```
+   ```
+4. Run tcpflow from the HPE Morpheus Enterprise appliance for non-SSL enabled AD identity Integrations 
+
+   Use tcpflow from the HPE Morpheus Enterprise appliance and then start the identity source configuration once again. Keep in mind this will only work for AD servers which are not SSL enabled:
+
+   ```
+   ```
+   $ sudo tcpflow -i any -c -v port 389
+   ```
+   ```
+5. Check the AD and domain controllers event logs 
+
+   Check the event logs for LDAP queries from the HPE Morpheus Enterprise appliance to ensure network connectivity.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..8b65f10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 262,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..083255b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,9 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Image Builder](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
+- **[VDI Pools](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json b/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
new file mode 100644
index 0000000..5cefdf2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+  "title": "Email Templates",
+  "ordinal": 323,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html",
+  "topic_cluster": {
+    "clustering_title": "Email Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md b/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
new file mode 100644
index 0000000..1b25100
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
@@ -0,0 +1,50 @@
+# Email Templates
+
+## Email Templates
+
+HPE Morpheus Enterprise sends out email to its users periodically to alert for various conditions such as an Instance provisioning success, warnings about upcoming Instance expiration, requests for password reset links, and more. HPE Morpheus Enterprise includes system-default email templates for all of these emailed conditions but allows users to create their own email templates to override the default template.
+
+On accessing the Email Templates tab, users will see a list of all email templates that currently exist. We can also see the owner which created the template as well as the associated Account (Tenant). System-default templates are shown as being owned by “System” and show no associated Account (Tenant). When a Master Tenant user creates a template, the option is given to tie the template to an Account or to make a global template. The Accounts column will show “Global” for global templates. Templates will apply in order of specificity: Tenant-specific templates apply first, then custom global templates, and finally system templates if no others exist for that email type.
+
+IMPORTANT
+
+Email templates apply in order of specificity. Tenant-specific templates apply over custom global templates which apply over system-default templates.
+
+![../../_images/emailTemplateList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-278D8A99-12B8-47EE-8FC8-F360DDA69C70-high.png)
+
+### Creating Templates
+
+Before creating the first template, it’s important to realize email from custom templates will still come wrapped in the standard HPE Morpheus Enterprise email headers and footers. It will also have included styling. This styling comes directly from your Tenant whitelabel configuration and will include HPE Morpheus Enterprise standard styling or your custom whitelabel styling depending on appliance configuration. The template itself should only include email body content which will be inserted within the styling wrapper.
+
+IMPORTANT
+
+It is possible to break the functionality of certain types of generated email by creating a custom template. For example, in a password reset email, you must ensure the password reset button is still included with the template. Other functionality-breaking scenarios may also be possible. Review the system-default template of any email type to copy syntax examples for such vital components.
+
+Some template types will have variables accessible, such as the logged in user’s name (to address the email) or an Instance name. To see the available variables, click on the info button for the system-default template of the type you wish to create. You’ll see the variables mentioned in a comment at the bottom of the template such as in this example Confirm Password Update Template:
+
+```
+```
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.greeting"}}}</p>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.message"}}}</p>  
+<a href={{{url}}}>{{{i18n "com.bertramlabs.plugins.accounts.password.email.linkLabel"}}}</a>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.signature"}}} </p>  
+<!-- available hbs variables are user.displayName and user.username -->
+```
+```
+
+To begin creating a new template, from the Email Templates tab of the global settings page (Administration > Settings), click + CREATE. The following configurations must be set:
+
+- **TYPE:** Select the email type for the new template
+- **TEMPLATE:** The HTML markdown for the new custom email template
+- **TENANTS:** This option is only available in the Master Tenant. Select a specific Tenant to tie the template to that Tenant or leave it empty to create a global template
+
+The following is an example of a Forgot Password Template. Note that it calls in the variable for the associated user display name and username.
+
+```
+```
+<p>Hello {{{user.displayName}}},</p>  
+<p>You have requested to reset the password for the account with username: {{{user.username}}}.</p>  
+<p>To reset the password, please click the button below. If you did not make this request, you can ignore this email but you should change your password.</p>  
+<a href='{{{forgotPasswordUrl}}}' class="btn-primary">Magical Password Reset Button</a>
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json b/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
new file mode 100644
index 0000000..5d8a65a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+  "title": "Hardware Requirements",
+  "ordinal": 179,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md b/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
new file mode 100644
index 0000000..6d8ae13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System:** Ubuntu 22.04
+- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory:** 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space:** For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while HPE Morpheus Enterprise will configure Ceph for multi-node clusters
+- **Network Connectivity:** HVM hosts must be assigned static IP addresses. They also need DNS resolution of the HPE Morpheus Enterprise appliance and Internet access in order to download and install system packages for HVM dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus Enterprise Agent communication with the HPE Morpheus Enterprise appliance | HVM Host | HPE Morpheus Enterprise appliance server | 443 | TCP |
+| HPE Morpheus Enterprise Agent communication with the HVM Host for hypervisor console | HPE Morpheus Enterprise appliance server | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus Enterprise appliance server | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus Enterprise server SSH access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTP) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json b/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
new file mode 100644
index 0000000..fce6c0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+  "title": "Morpheus UI war files",
+  "ordinal": 28,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus UI war files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md b/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
new file mode 100644
index 0000000..b42926c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
@@ -0,0 +1,51 @@
+# Morpheus UI war files
+
+## About this task
+
+Pre-release or patched versions of the HPE Morpheus Enterprise UI are sometimes provided. To deploy the ui war on a HPE Morpheus Enterprise Appliance:
+
+## Procedure
+
+1. Download the war file to the target appliance 
+
+   ```
+   ```
+   wget https://url/war_file
+   ```
+   ```
+
+   NOTE
+
+   If the war file is provided via a droplr link, ensure a `+` is added to end of droplr url or the file will not download
+2. Backup current war file 
+
+   ```
+   ```
+   sudo mv /opt/morpheus/lib/morpheus/morpheus-ui.war /opt/morpheus/lib/morpheus/morpheus-ui.bak.`date +"%m-%d-%Y"`
+   ```
+   ```
+3. Move and rename new war file 
+
+   ```
+   ```
+   sudo mv <file> /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+4. Ensure war is owned by `morpheus-app` 
+
+   ```
+   ```
+   sudo chown morpheus-app:morpheus-app /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+5. Restart the HPE Morpheus Enterprise UI 
+
+   ```
+   ```
+   sudo morpheus-ctl restart morpheus-ui
+   ```
+   ```
+
+## Results
+
+The new ui war will load on startup!
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json b/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
new file mode 100644
index 0000000..00761a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 422,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md b/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
new file mode 100644
index 0000000..2223330
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
@@ -0,0 +1,28 @@
+# Firmware and Driver Lifecycle Management
+
+Starting with HPE BMaaS version 1.0.0, HPE Morpheus Enterprise supports firmware and driver updates for HPE ProLiant bare-metal servers using preloaded tasks and workflows. This capability enables administrators to centrally manage server firmware and driver compliance using HPE Service Pack for ProLiant (SPP) images, executed directly from the HPE Morpheus appliance.
+
+Firmware and driver updates are performed through **Jobs and Workflows** in HPE Morpheus and can be run in **Dry Run (inventory)** or **Deploy** modes. Updates can target firmware only, drivers only, or both, depending on operational requirements. The update process supports multiple servers per job and provides detailed execution logs for auditing and troubleshooting.
+
+## Prerequisites
+
+Before performing firmware and driver updates, ensure the following:
+
+- HPE BM Plugin version 1.0.0 or later is installed.
+- An appropriate HPESPP ISO is available for each server generation (for example, Gen10 and Gen11 require different SPP ISOs).
+- The HPE Morpheus appliance has access to the SPP ISO, either through:
+
+  - A locally downloaded ISO file, or
+  - A URL accessible without authentication.
+- For driver inventory and updates within a deployed operating system:
+
+  - iSUT (Integrated Smart Update Tools) and AMS (Agentless Management Service) must be installed and running on the target servers.
+  - ESXi hosts are expected to already have iSUT installed.
+
+**Subtopics**  
+
+- **[Adding HPE SPP to the Virtual Image Library](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html)**
+- **[Installing iSUT on Deployed Instances (Optional)](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html)**
+- **[Creating and Running an SPP Update Job](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html)**
+- **[Monitoring and Completion](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html)**
+- **[Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json b/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
new file mode 100644
index 0000000..22b441f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+  "title": "API Access",
+  "ordinal": 338,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md b/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
new file mode 100644
index 0000000..7118ec5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
@@ -0,0 +1,20 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+If needed, Primary Tenant administrators may configure the expiration periods for existing clients or create new clients from HPE Morpheus Enterprise global settings (Administration > Settings > Clients). See [client configuration documentation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html) for more details.
+
+- **morph-api:** Used for HPE Morpheus Enterprise API access and should be the default token-type used
+- **morph-cli:** Used for HPE Morpheus Enterprise CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json b/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
new file mode 100644
index 0000000..83bdac0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+  "title": "Upgrading",
+  "ordinal": 20,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md b/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
new file mode 100644
index 0000000..b8819a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
@@ -0,0 +1,8 @@
+# Upgrading
+
+**Subtopics**  
+
+- **[Upgrading Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html)**
+- **[Single Node/AIO Appliance Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html)**
+- **[3-Node HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html)**
+- **[Full HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json b/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
new file mode 100644
index 0000000..5957de8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+  "title": "Okta",
+  "ordinal": 283,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html",
+  "topic_cluster": {
+    "clustering_title": "Okta",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md b/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
new file mode 100644
index 0000000..44ba4a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
@@ -0,0 +1,52 @@
+# Okta
+
+## Overview
+
+HPE Morpheus Enterprise allows users to integrate an Okta deployment for user management and authentication. In HPE Morpheus Enterprise, identity sources are added on a per-Tenant basis and Morpheus allows you to map Okta user groups to HPE Morpheus Enterprise user groups. User accounts are automatically created with matching metadata and role permissions when users are authenticated.
+
+## Adding an Okta Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + IDENTITY SOURCE
+5. Choose TYPE: “Okta”
+6. Populate the following, then select SAVE CHANGES:
+
+### Results
+
+Name
+:   Unique name for authentication type
+
+Description
+:   A description for your new Okta Identity Source
+
+Okta URL
+:   Your Okta URL
+
+Administrator API Token
+:   Your Okta Administrator API Token
+
+Required Group
+:   The Okta group that users must be in to have access (optional)
+
+Default Role
+:   The default role a user is assigned if no group is listed under an Okta user that maps within the Morpheus Role Mappings section
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Now, allowed Okta users can log into HPE Morpheus Enterprise via their Okta credentials and a user will be automatically generated within HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+NOTE
+
+If you’ve created multi-tenant roles, these will also appear here and can be mapped to Okta user groups allowing you to map users to equivalent user groups in HPE Morpheus Enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json b/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
new file mode 100644
index 0000000..9d71748
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+  "title": "Edit Workflow",
+  "ordinal": 120,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md b/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
new file mode 100644
index 0000000..1318da7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
@@ -0,0 +1,10 @@
+# Edit Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Edit icon on the row of the workflow you wish to edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json b/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
new file mode 100644
index 0000000..9dcbff7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+  "title": "Inputs",
+  "ordinal": 154,
+  "parent_title": "Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html",
+  "topic_cluster": {
+    "clustering_title": "Inputs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md b/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
new file mode 100644
index 0000000..0320bf3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
@@ -0,0 +1,220 @@
+# Inputs
+
+Inputs are custom input fields that can be added to Instance Types and Layouts, then presented in Instance, App, and Cloning wizards. The resulting value is available in the Instance config map as <%=customOptions.fieldName%> or <%=customOptions[‘fieldName’], the latter syntax being required in certain situations such as when the field name contains a hyphen “-” (ex. <%=customOption[‘my-field-name’]). The fieldName and value can also be exported as Tags.
+
+![../../_images/new_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ADEB1679-C4C4-4345-B276-57B434C94563-high.png)
+
+## Create Input
+
+NOTE
+
+All possible fields listed. Displayed fields depend on `TYPE` selection
+
+NAME
+:   Name of the Input
+
+DESCRIPTION
+:   Description for reference in Input list view
+
+FIELD NAME
+:   This is the input fieldName property that the value gets assigned to
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+HIDDEN
+:   When marked, this Input will be hidden from the user but the value will still be accessible. This allows for alternate Input types to be used as hidden Inputs than what is possible with “Hidden” type Inputs (described further below). This is also different from Input “Visibility” settings as the values of non-visible Inputs is not accessible for consumption in automation routines
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value. It should also be noted that when an Input is not visible, its value is not available for consumption in automation routines. Use the “Hidden” flag (see above) to configure hidden yet accessible values
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+TYPE
+:   - **Text:** Text Input Field
+    - **Text Area:** A text area input, when selected an additional option appears to allow the user to configure the default number of visible rows in the text area
+    - **Select List:** Populated by Option Lists, presents a manual or REST-populated dropdown list
+    - **Checkbox:** Checkbox for `on` or `off` values
+    - **Number:** Input field allowing only numbers
+    - **Typeahead:** Populated by Option Lists: Rather than presenting a potentially-large dropdown menu, the user can begin typing a selection into a text field and choose the desired option. Multiple selections can be allowed with this type by marking the ‘ALLOW MULTIPLE SELECTIONS’ box
+    - **Hidden:** No field will be displayed, but the field name and default value will be added to the Instance config map for reference
+    - **Password:** An input field with suitable encryption for accepting passwords
+    - **Radio List:** Populated by Option Lists, presents a selection of radio buttons for the provisioning user
+
+LABEL
+:   This is the input label that typically shows to the left of a custom option
+
+ROWS
+:   For `Textarea` type Option Lists, determines how many text rows will be given when the Input is presented
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+REMOVE NO SELECTION
+:   For Select List-type Inputs. When marked, the Input will default to the first item in the list rather than to an empty selection. This is especially useful when only one choice is anticipated to be in the list as it saves the user from manually making a default selection
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+    **Verify Pattern Demo**
+
+DEFAULT CHECKED
+:   For `Checkbox` types, when marked the Checkbox will be checked by default
+
+OPTION LIST
+:   For `Select List` types, select a pre-existing Option List to set dropdown values
+
+    NOTE
+
+    `Select List` and `Typeahead` Inputs require creation and association of an Option List
+
+## Cascading Inputs
+
+One powerful facet of HPE Morpheus Enterprise Inputs is the ability to present users with different lists of input options based on their selections in other Inputs within the same wizard or modal. One common example, which is fully illustrated in this section, is to have a user select:
+
+- The Group they wish to provision into…
+- Then select the target Cloud from a list limited to Clouds which are in the selected Group…
+- Then select the target network from a list limited to networks which are available to the selected Cloud and Group
+
+To set this up, we will first configure our Inputs (custom option fields that can be applied to Instance Types and other HPE Morpheus Enterprise constructs) and Option Lists (dynamic lists of possible choices which can be associated with Inputs and presented in a dropdown or typeahead format). Once the custom options are configured, we will associate them with a new service catalog item and take a look at how the user would interact with them.
+
+### Group Custom Options
+
+To begin, we will create a new [Option List](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#option-lists) In this case, we will select type of “Morpheus Api” which will populate the list based on a call to the internal HPE Morpheus Enterprise API. Option Lists can also be populated by calls to external REST APIs or even from static lists that you enter manually. When dynamically populating Option Lists, whether via HPE Morpheus Enterprise API or an external API, translation and/or request scripts may be needed to prepare the request or translate the results. More on that as we build out the example.
+
+I have called my Option List “Groups” and selected “Groups” from the OPTION LIST menu. This simply indicates that Groups are the construct we want to call into our list from HPE Morpheus Enterprise API. In this case, we want to present a list of all Groups to the user by their name and pass the Group database ID in the background. Since it is common to create Option Lists from HPE Morpheus Enterprise API where the construct name is displayed to the user and the ID is passed, we actually do not need to input any translation scripts in this case. However, I will include a translation script here which does the same thing simply to provide more clarity to the example. HPE Morpheus Enterprise [Option List documentation](https://docs.morpheusdata.com/en/latest/library/options/option_lists.html) includes additional details on available translation script inputs and which are available without translation as a convenience feature.
+
+```
+```
+for (var x = 0; x < data.length; x++) {  
+  results.push({name: data[x].name, value:data[x].id});  
+}
+```
+```
+
+After saving the Option List, create the Input that presents the list we just created. I gave my Input the name of “Selected Group”, field name of “selectedGroup”, and label of “Group”. For type, choose “Select List” and a new field will appear at the bottom of the modal where we can select the Option List we just created. With this configuration, the Input will present as a dropdown list containing the options called from our Option List.
+
+### Cloud Custom Options
+
+Adding the Option List and Input for Clouds will be similar to the prior step with the exception that we will be including a request script which effectively filters the list of available Clouds to only those associated with the selected group. Follow the same process to start a new Option List, I have configured mine as follows:
+
+- **NAME:** Parsed Clouds
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Clouds
+
+We also need a request script that loads the `siteId` attribute of the `results` variable with the Group ID if the user has made a group selection. Essentially it appends this input as a query parameter to the API call, calling (for example) `./api/clouds?siteId=1` rather than `.../api/clouds`. It should be similar to the script below. Note that we are referencing the `selectedGroup` field name we created previously and that a “site” is the term for Groups in the HPE Morpheus Enterprise database.
+
+```
+```
+if (input.selectedGroup) {  
+  results.siteId = input.selectedGroup  
+}
+```
+```
+
+We also need a translation script which will be identical to the one used previously with the exception that if there is no input on the `selectedGroups` field, nothing will be displayed for the Clouds option.
+
+```
+```
+if (input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+We also need to create an Input to house this Option List. This process will be very similar to creating the previous Input except that we need to set selectedGroup as the Dependent Field. Setting a dependent field on an Input will trigger it to reload each time a selection is made in the indicated option. My configuration is as follows:
+
+- **NAME:** Parsed Cloud
+- **FIELD NAME:** parsedCloud
+- **DEPENDENT FIELD:** selectedGroup
+- **TYPE:** Select List
+- **LABEL:** Cloud
+- **OPTION LIST:** Parsed Clouds
+
+Save your changes once done.
+
+### Network Custom Option
+
+Finally, we will create an Option List/Input pair for network selection. In this case, it will be dependent on both the Group and Cloud selection. My Option List configuration is below:
+
+- **NAME:** Parsed Networks
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Networks
+
+### Request Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+  results.cloudId = input.parsedCloud  
+  results.groupId = input.selectedGroup  
+}
+```
+```
+
+### Translation Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+The Input is configured as follows:
+
+- **NAME:** Parsed Networks
+- **FIELD NAME:** parsedNetwork
+- **DEPENDENT FIELD:** parsedCloud
+- **TYPE:** Select List
+- **LABEL:** Network
+- **OPTION LIST:** Parsed Networks
+
+### Setting Custom Options at Provision Time
+
+At this point, our dependent options are ready to be applied to custom Instance Types, Workflows or Service Catalog items as needed. When creating them, we can select an unlimited number of Inputs from a typeahead field on the create modal and they will be presented when a user goes to provision that element or run that Workflow. As an example, I have created a Service Catalog item that incorporates the three Inputs we have created. You can see how the dependent fields reload and present different options based on my selections.
+
+![../../_images/cascadingOptionList.gif](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-41F98D9A-033E-4560-8F99-824818F25590-high.gif)
+
+## Visibility Field
+
+The Input Visibility field allows users to set conditions under which the Input field is displayed. Visibility field accepts `fieldName:value` or `fieldName:(regex)`, where “fieldName” equals the fieldName of another Input which will determine the visibility of this Input, and “value” equals the target value of the other Input (or a regex pattern that matches to the values that meet your desired conditions). You can simply enter “fieldName” when visibility should be triggered when any value is entered. When the value of the target Input matches the “value” or “(regex)” set in the Visibility field, this Input will be displayed. When the value of the target Input does not match “value” or satisfy the “(regex)” set in the Visibility field, this Input will not be displayed.
+
+Expanding on the simplified example above, we could trigger visibility based on any one of multiple selections from the same Input by using a different regular expression, such as `color:(red|blue|yellow)`. Additionally, we are not restricted to the conditions of just one Input to determine visibility as the following would also be valid: `color:(red|blue|yellow),shape:(square)`. In the previous example, the Input “Color” would have to be set to red, blue, or yellow OR the Input “Shape” would have to be set to square in order to trigger visibility of the Input currently being configured. Prepend the previous example with `matchAll::` in order to require both conditions to be met rather than one or the other (ex. `matchAll::color:(red|blue|yellow),shape:(square)`).
+
+## Required Field
+
+The Required field allows for Inputs to be conditionally required. In this field, enter the Field Name value for another Input and, if that Input is filled by the user, the current Input will become required. This feature could also be used in conjunction with the Visibility field described above in that you may want a field to be required when visible but not required when hidden. Below is a simple abstract example showing how the second displayed Input becomes required when the first displayed Input is filled.
+
+![../../_images/required.gif](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E44477FD-45A4-44BD-A7CA-0587E51A09ED-high.gif)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json b/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
new file mode 100644
index 0000000..b9c0f0d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+  "title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+  "ordinal": 366,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md b/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
new file mode 100644
index 0000000..ac2dc56
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
@@ -0,0 +1,207 @@
+# Creating XaaS Instance Types with HPE Morpheus Enterprise
+
+HPE Morpheus Enterprise version 5.4.2 and higher includes the ability to build and provision XaaS Instance Types. These are non-VM backed Layouts which allow users to represent anything as an Instance. This includes the ability to utilize Provisioning Workflows to manage all phases of the Instance lifecycles consistently and automatically. XaaS Instance Types can also be tied into service plans to track costs or bill customers.
+
+In this specific example, we will create an XaaS Instance Type to manage the lifecycle of folders within a Dropbox account. Users will be able to visit the HPE Morpheus Enterprise Catalog and have the folder created by entering a name for the folder and clicking a single button. We’ll see how each folder is then represented as an Instance. With the Instance standing, users will be able to update the folder name by simply editing a custom value on the Instance. Finally, when the Instance is deleted, the folder is deleted from Dropbox as well.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Clouds
+- Inputs
+- Tasks
+- Workflows
+- Instance Types
+- Layouts
+- Catalog Items
+- Instances
+
+NOTE
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. In this guide we will go through the process of creating a HPE Morpheus Enterprise-type Cloud which can be used to hold your XaaS resources.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the Dropbox API token as a Cypher entry. Creating Dropbox developer accounts and obtaining API keys goes beyond the scope of this guide but Dropbox developer tools are well-documented if you want to try this out for yourself. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dropboxtoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-865BCB56-4457-4DA6-A9A1-34CFCD22EEAE-high.png)
+
+One of my Tasks will also send a request to the HPE Morpheus Enterprise API so I’ll create a second Cypher entry to store a HPE Morpheus Enterprise API key:
+
+- **KEY:** secret/morphapitoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+## Create Cloud
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. For this example, I’m creating a Cloud just to organize Dropbox folders. Navigate to Infrastructure > Clouds and click + ADD. The only required steps to create the Cloud are to give it a name and associate it with a Group. I’ve given mine a generic name but you could opt to be more targeted with your naming if you will use many HPE Morpheus Enterprise-type Clouds to manage other types of resources.
+
+- **NAME:** MorphCloud
+
+![../../_images/1cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B1A71913-825C-4533-BBBD-AEF60F33F4F1-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create two Inputs in this case, one to allow the user to enter a name for their folder on provisioning and another which will be visible when editing the Instance to allow the user to rename their folder.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** DropBox Folder Name (The name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** dbfoldername (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **SHOW ON EDIT:** Checked (When checked, this Option is visible when editing an Instance)
+- **EDITABLE:** Checked (When checked, this Option is editable in addition to being visible while editing the Instance)
+- **LABEL:** DropBox Folder Name (The label the user sees next to the input field)
+
+Once done, click SAVE CHANGES
+
+![../../_images/2input.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-13B6ACC4-D949-465D-B229-1A7E9D065999-high.png)
+
+Next, configure a second Input with the following attributes:
+
+- **NAME:** DropBox Folder New Name
+- **FIELD NAME:** dbfoldernewname
+- **TYPE:** Text
+- **SHOW ON EDIT:** Checked
+- **EDITABLE:** Checked
+- **LABEL:**
+
+Click SAVE CHANGES
+
+## Create Tasks
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ll write the Task configuration directly into the HPE Morpheus Enterprise Tasks. However, Tasks can also be sourced directly from integrated version control repositories (like Github) so you never have to copy and paste code or make manual updates when your code changes.
+
+For this example, we need to create four Tasks. One to create the folder, one to rename the folder, one to rename the HPE Morpheus Enterprise Instance, and one to delete the folder. I’ve used Python Tasks to interact with the Dropbox Python SDK. I won’t go into how to write the individual Tasks here but the Python SDK is well-documented if you want to try things out for yourself. The same functions could be carried out using other Task types as well.
+
+![../../_images/3tasks.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BBDD2BA6-FF48-4A8B-903C-7F8C08E972A2-high.png)
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Dropbox - Create Folder
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Local (Select Repository to source your code from an integrated version control repository)
+- **CONTENT:** Enter Task content here
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the Dropbox API token from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US)
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES
+
+![../../_images/5createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-82B72BAF-618B-4F5A-B82F-8D4BE96BD27A-high.png)
+
+The process for creating the remaining three Tasks is very similar, expand the sections below to see screenshots of the Task config, if desired:
+
+### Dropbox - Delete Folder
+
+![../../_images/6deletetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-020E198F-49C6-4228-ABE8-C5580D223F15-high.png)
+
+### Dropbox - Rename Folder
+
+![../../_images/7renametask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-05551E97-6453-4079-A6D5-B0CF880BC840-high.png)
+
+### Dropbox - Reset Instance Name
+
+![../../_images/8resetinstancetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BFB5EBC7-4C8A-4F58-AB33-90475BCB8B6E-high.png)
+
+## Create Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need the following to occurring during the Instance lifecycle:
+
+- At the provisioning phase, we want a folder to be created
+- At the reconfigure phase (when the Instance is edited), we want the folder to be renamed and the Instance name to be updated
+- At the teardown phase (when the Instance is deleted), we want the folder to be deleted
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **PLATFORM:** All
+- **TASKS - Provision:** Dropbox - Create Folder
+- **TASKS - Reconfigure:** Dropbox - Rename Folder; Dropbox - Reset Instance Name
+- **TASKS - Teardown:** Dropbox - Delete Folder
+
+Once done, click SAVE CHANGES
+
+![../../_images/9workflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4710C85B-97B8-4EFB-B607-8D8289BEE58C-high.png)
+
+## Create Instance Type
+
+With the Workflow and Inputs complete, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. From this, we’ll create a catalog item that our users can order in a later step.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **CODE:** xaas
+- **CATEGORY:** Utility
+- **ICON:** If desired, search the file system on your local computer for a Dropbox logo icon for easier identification of this Instance Type at provision time
+- **ENVIRONMENT PREFIX:** XAAS
+
+![../../_images/10instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-08F8C46C-E7EE-4E11-B0D2-D204B32405B6-high.png)
+
+Click SAVE CHANGES.
+
+## Create Layout
+
+After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case Workflow. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on (when dealing with VM-based Instance Types). Configure the Layout as follows:
+
+- **NAME:** XaaS - Dropbox
+- **VERSION:** Latest
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Workflow
+- **WORKFLOW:** Select the Workflow we’ve just created, “XaaS - Dropbox”. By selecting this, all Instances provisioned with this Layout will automatically have our chosen Tasks run during specific Instance lifecycle phases
+- **INPUTS:** Search and find the two custom Inputs we created earlier, “DropBox Folder Name” and “DropBox Folder New Name”
+
+![../../_images/11layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3C57ACEF-141F-4DED-929C-1724C2B1F81C-high.png)
+
+## Create Catalog Item
+
+Catalog Items offer a simplified provisioning process. Administrators can create Catalog Items using existing Instance Types, App Blueprints, or Workflows. Most or all of the provisioning options can be pre-selected leaving fewer decisions up to the user and allowing them to easily create what they need. In this case, we’ll create one based on the Instance Type that was made in the previous sections. Navigate to Library > Blueprints > Catalog Items and click + ADD, then Instance. Configure the following:
+
+- **NAME:** XaaS - Dropbox Folder
+- **ENABLED:** Checked (If unchecked, this Catalog Item will not be displayed in the provisioning catalog for users)
+- **LOGO:** If desired, browse your local disk for a Dropbox logo to make this Catalog Item easily recognizable
+
+Then, click CONFIGURATION WIZARD. On the “TYPE” tab, search for the Instance Type we created and click NEXT. On the “Group” tab, select the HPE Morpheus Enterprise-type Cloud and enter any name (we’ll override this name value later so it’s dynamic based on user input). Click NEXT. On the “CONFIGURE” tab, the Layout and Plan fields should default to acceptable values. Enter anything for the “Dropbox Folder Name”, we will also update this to be dynamic in the next step. Click through the final two tabs, there’s no need to attach our Workflow on the “AUTOMATION TAB” since we already have it on our Layout. Finally, click COMPLETE.
+
+Once finished, you’ll see the JSON configuration map for the Instance loaded into the “CONFIG” field. Update the “dbfoldername” Input value and the Instance name value to dynamically take on the user-entered value on the “Dropbox Folder Name” field as I’ve done in my screenshot below:
+
+![../../_images/12catitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F93420D1-2F2A-479B-9ACD-56A52256AD43-high.png)
+
+Near the bottom of the modal window, search for and attach the “DropBox Folder Name” Input. This will be the only input our users need to make to order their folder. Then, click SAVE CHANGES
+
+## Ordering Catalog Item
+
+At this point, the configuration steps are completed. As a test, we can order a folder from the provisioning Catalog. Navigate to Provisioning > Catalog and click “Order” on our “XaaS - Dropbox Folder” item. We need only provide a name for our folder and click “Order Now”.
+
+![../../_images/13orderitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-27E8619F-240F-43AE-A00F-70489E83CE32-high.png)
+
+If we now head to Provisioning > Instances, we can see a new Instance entry has been created for our Dropbox folder. Note that the Instance is named for our folder name exactly as we configured earlier.
+
+![../../_images/14inslist.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2FA0BA43-267B-4BFD-8C3A-46A8879844F4-high.png)
+
+Taking a look in the Dropbox web console, we can also see a folder has been created just as we’d expect.
+
+![../../_images/15dbcreate.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-38887B6A-8B2B-44AA-BDA0-91C557D414F8-high.png)
+
+## Managing and Deleting Instances
+
+Back in HPE Morpheus Enterprise, we can take a look at the Instance detail page (Provisioning > Instances > Specific Instance) and perform some Day 2 actions. By clicking EDIT, we can update Instance details. When Input values are updated, HPE Morpheus Enterprise will automatically trigger reconfigure actions on our Instance. In our case, we’ve configured it to update the folder name in Dropbox and update the Instance name in HPE Morpheus Enterprise for easier identification. As you can see in the screen shot, I’m providing a new folder name value:
+
+![../../_images/16editins.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4A83E6DE-B560-4FBC-A948-892DA9AFBBE2-high.png)
+
+As expected, our Instance name is updated and the folder is renamed on the Dropbox side:
+
+![../../_images/17insdetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9E516B64-6C3D-4577-B7C6-E67FC23ADBB2-high.png) ![../../_images/18dbupdate.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FB2B154B-85F7-4AA0-B77E-FB596CE9F7FE-high.png)
+
+Finally, I’ll delete the Instance. This has the effect of deleting the Instance object out of HPE Morpheus Enterprise and triggering our Teardown-phase action which deletes the folder from Dropbox:
+
+![../../_images/19dbdelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5D5388E9-5251-499E-ABE9-36A1342F356C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json b/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
new file mode 100644
index 0000000..0917e2c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+  "title": "3 Node HA Install Example",
+  "ordinal": 18,
+  "parent_title": "Installation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html",
+  "topic_cluster": {
+    "clustering_title": "3 Node HA Install Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md b/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
new file mode 100644
index 0000000..f501899
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
@@ -0,0 +1,489 @@
+# 3 Node HA Install Example
+
+Distributed App Nodes with Externalized MySQL Database
+
+A common and recommended HA Morpheus deployment consists of three app nodes using embedded services and an external MySQL DB cluster (minimum of 3 nodes).
+
+IMPORTANT
+
+HA environments installed without engagement from Morpheus are not eligible for support. The provided configuration serves as a sample only and requirements may vary. Please reach out to your account manager to discuss deploying a HA environment to meet the requirements for support.
+
+## Assumptions
+
+This guide assumes the following:
+
+- App nodes can resolve each others short names
+- All app nodes have access to shared storage mounted at `/var/opt/morpheus/morpheus-ui`.
+- This configuration is designed to tolerate the complete failure of a single node but not more. Specifically, the Elasticsearch tier requires MORE than 50% of the nodes to be up and clustered at all times. However, you can always add more nodes to increase resilience.
+- You have a load balancer available and configured to distribute traffic between the app nodes. [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
+
+![Morpheus 3-Node HA Architecture](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-627980F3-725B-4765-8CF0-89FD087667C8-high.png)
+
+## Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## MySQL requirements for Morpheus HA
+
+The requirements are as follows:
+
+- MySQL version v8.0.x (minimum of v8.0.72)
+- MySQL cluster with at least 3 nodes for redundancy.
+- Morpheus application nodes have connectivity to MySQL cluster.
+
+NOTE
+
+Morpheus does not create primary keys on all tables. If you use a clustering technology that requires primary keys, you will need to leverage the invisible primary key option in MySQL 8
+
+## Configure Morpheus Database and User
+
+### Procedure
+
+1. Create the Database you will be using with HPE Morpheus Enterprise. Login to mysql node: 
+
+   ```
+   ```
+   [root@node: ~]  mysql -u root -p  
+     # password: `enter root password`  
+   mysql> CREATE DATABASE morpheus CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;  
+   mysql> show databases;
+   ```
+   ```
+2. Next create your HPE Morpheus Enterprise database user. This is the user the HPE Morpheus Enterprise app nodes will auth with mysql. 
+
+   ```
+   ```
+   mysql> CREATE USER 'morpheus'@'%' IDENTIFIED BY 'morpheusDbUserPassword';
+   ```
+   ```
+3. Next Grant your new HPE Morpheus Enterprise user permissions. 
+
+   ```
+   ```
+   mysql> GRANT ALL PRIVILEGES ON morpheus.* TO 'morpheus'@'%' with grant option;  
+   mysql> GRANT SELECT, PROCESS, SHOW DATABASES, RELOAD ON *.* TO 'morpheus'@'%';  
+   mysql> FLUSH PRIVILEGES;  
+   mysql> exit
+   ```
+   ```
+
+## App Node Installation
+
+### Requirements
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `outbound` access to the various backend services:
+
+- mySQL Port to External DB
+
+  - 3306/tcp
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `inbound` from agents and users:
+
+- HTTPS Port
+
+  - 443/tcp
+- RabbitMQ Ports
+
+  - 4369 (epmd - inter node cluster discovery)
+  - 5671 (TLS from nodes to RabbitMQ)
+  - 5672 (non-TLS from nodes to RabbitMQ)
+  - 15671 (HTTPS API)
+  - 15672 (HTTP API)
+  - 25672 (inter node cluster communication)
+  - 61613 (STOMP - non-TLS)
+  - 61614 (STOMP - TLS)
+- OpenSearch Ports
+
+  - 9200 (API access)
+  - 9300 (inter node cluster communication)
+
+### Installation
+
+#### Procedure
+
+1. First begin by downloading and installing the requisite HPE Morpheus Enterprise packages to ALL HPE Morpheus Enterprise app nodes. 
+
+   HPE Morpheus Enterprise packages can be found in the Downloads section of the [Morpheus Hub](https://morpheushub.com/download)
+
+   RHELL/CentOS
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance-ver-1.el8.x86_64.rpm  
+   [root@node: ~] rpm -ihv morpheus-appliance-appliance-ver-1.el8.x86_64.rpm
+   ```
+   ```
+
+   Ubuntu
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance_ver-1.amd64.deb  
+   [root@node: ~] dpkg -i morpheus-appliance-appliance_ver-1.amd64.deb
+   ```
+   ```
+2. Do NOT run reconfigure yet. The HPE Morpheus Enterprise configuration file must be edited prior to the initial reconfigure.
+3. Next you will need to edit the HPE Morpheus Enterprise configuration file `/etc/morpheus/morpheus.rb` on each node. 
+
+   NOTE
+
+   In the configuration below, the UID and GID for the users and groups are defined for services that will be embedded. This ensures they are consistent on all nodes. If they are not consistent, the shared storage permissions can become out of sync and errors will appear for plugins, images, etc. If not specified, Morpheus will automatically find available UIDs/GIDs starting at 999 and work down. Availability of UIDs and GIDs can be seen by inspecting `/etc/passwd` and `/etc/group` respectively. Change the UIDs and GIDs below based on what is available.
+
+   You can find additional configuration settings [here](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#advanced-morpheus-rb-settings)
+
+   Node 1
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.01'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node01'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.02'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node02'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.03'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node03'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   NOTE
+
+   The configurations above for `` `mysql['host'] `` shows a list of hosts, if the database has multiple endpoints. Like other options in the configuration, `mysql['host']` can be a single entry, if the database has a single endpoint: `mysql['host'] = 'myDbEndpoint.example.com` or `mysql['host'] = '10.100.10.111'`
+
+   IMPORTANT
+
+   The OpenSearch node names set in `opensearch['node_name']` must match the host entries in opensearch[‘es\_hosts’]. `node_name` is used for `node.name` and `es_hosts` is used for `cluster.initial_master_nodes` in the generated opensearch.yml config. Node names that do not match entries in cluster.initial\_master\_nodes will cause clustering issues.
+
+   IMPORTANT
+
+   The rabbitmq[‘node\_name’] in the Node 1 example above is rabbit@node01. The shortname for the server of node01 must be resolvable by DNS or /etc/hosts of all other hosts, same for node02 and node03. FQDNs cannot be used here
+4. Mount shared storage at `/var/opt/morpheus/morpheus-ui` on each App node if you have not already done so. Create the directory if it does not already exist.
+5. Reconfigure on all nodes 
+
+   All Nodes
+
+   ```
+   ```
+   [root@node: ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   HPE Morpheus Enterprise will come up on all nodes and OpenSearch will auto-cluster. RabbitMQ will need to be clustered manually after reconfigure completes on all nodes.
+
+## Clustering Embedded RabbitMQ
+
+### Procedure
+
+1. Select one of the nodes to be your Source Of Truth (SOT) for RabbitMQ clustering (Node 1 for this example). On the nodes that are NOT the SOT (Nodes 2 & 3 in this example), begin by stopping the UI and RabbitMQ. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop morpheus-ui  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   [root@node2 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop morpheus-ui  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   [root@node3 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+2. Then on the SOT node, we need to copy the secrets for RabbitMQ. 
+
+   Begin by copying secrets from the SOT node to the other nodes.
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /etc/morpheus/morpheus-secrets.json  
+    "rabbitmq": {  
+      "morpheus_password": "***REDACTED***",  
+      "queue_user_password": "***REDACTED***",  
+      "cookie": "***REDACTED***"  
+    },
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /etc/morpheus/morpheus-secrets.json  
+     "rabbitmq": {  
+       "morpheus_password": "***node01_morpheus_password***",  
+       "queue_user_password": "***node01_queue_user_password***",  
+       "cookie": "***node01_cookie***"  
+     },
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] vi /etc/morpheus/morpheus-secrets.json  
+   "rabbitmq": {  
+     "morpheus_password": "***node01_morpheus_password***",  
+     "queue_user_password": "***node01_queue_user_password***",  
+     "cookie": "***node01_cookie***"  
+   },
+   ```
+   ```
+3. Then copy the erlang.cookie from the SOT node to the other nodes 
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # 754363AD864649RD63D28
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+
+   Nodes 3
+
+   ```
+   ```
+   [root@node3 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+4. Once the secrets and cookie are copied from node01 to nodes 2 & 3, run a reconfigure on nodes 2 & 3. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+5. Next we will join nodes 2 & 3 to the cluster. 
+
+   IMPORTANT
+
+   The commands below must be run at root
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop rabbitmq  
+   [root@node2 ~] morpheus-ctl start rabbitmq  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node02' ...  
+   [root@node2 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node02' with 'rabbit@node01' ...  
+   [root@node2 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node02' ...
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop rabbitmq  
+   [root@node3 ~] morpheus-ctl start rabbitmq  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node03' ...  
+   [root@node3 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node03' with 'rabbit@node01' ...  
+   [root@node3 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node03' ...
+   ```
+   ```
+
+   NOTE
+
+   If you receive an error `unable to connect to epmd (port 4369) on node01: nxdomain (non-existing domain)` make sure to add all IPs and short (non-fqdn) hostnames to the `/etc/hosts` file to ensure each node can resolve the other hostnames.
+6. Next reconfigure Nodes 2 & 3 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+7. The last thing to do is start the HPE Morpheus Enterprise UI on the two nodes that are NOT the SOT node. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+8. You will be able to verify that the UI services have restarted properly by inspecting the logfiles. A standard practice after running a restart is to tail the UI log file. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   The UI should be available once the Morpheus logo is displayed in the logs. Look for the ascii logo accompanied by the install version and start time:
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2024  
+   timestamp: ****************************************
+   ```
+   ```
+
+## Embedded Elasticsearch
+
+Morpheus clusters OpenSearch automatically.
+
+## Load Balancer
+
+Configure your load balancer to distribute traffic between the app nodes.
+
+You can see some examples here: [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json b/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
new file mode 100644
index 0000000..67db700
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+  "title": "Workloads: Apps Usage",
+  "ordinal": 70,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Apps Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md b/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
new file mode 100644
index 0000000..9a1f1f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
@@ -0,0 +1,32 @@
+# Workloads: Apps Usage
+
+![../_images/12appusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9916D4B0-7144-4088-98AC-2B2F2E780378-high.png)
+
+The Apps Usage dashboard lists all provisioned Apps that meet a set of filters and organizes them by Cloud. Totals for cost and resource usage of all relevant Apps can be viewed with a per-Cloud breakdown.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **TOTAL COST:** The total cost of all selected Apps
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Instance Usage List
+
+All Clouds with a currently-provisioned App which is selected in the dashboard filters are listed here. The name of the Cloud is listed along with its App count, the total memory, total storage, total CPU cores and price of the Apps provisioned in that Cloud are also listed.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..dde801f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 325,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..7c4d145
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,39 @@
+# Backups
+
+## Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+IMPORTANT
+
+Appliances with an HA architecture containing multiple app nodes must ensure all nodes can access stored backups. By default, if no “Default Backup Bucket” configuration is made, backups are stored in `/var/opt/morpheus/bitcan`. If this path is local to the app nodes, all other app nodes would not be able to reach the backups. In such a case, one solution would be to create an NFS share for the `bitcan` directory for all app nodes. Another solution would be to make a “Default Backup Bucket” configuration selection, which all nodes would then use for backup storage and retrieval.
+
+### HPE Morpheus Enterprise Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to HPE Morpheus Enterprise if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json b/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
new file mode 100644
index 0000000..301b817
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+  "title": "Oracle Linux Virtualization Manager",
+  "ordinal": 463,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Linux Virtualization Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md b/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
new file mode 100644
index 0000000..75a282f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
@@ -0,0 +1,56 @@
+# Oracle Linux Virtualization Manager
+
+Oracle Linux Virtualization Manager (OLVM) allows administrators to manage and support a multi-host Oracle Linux KVM environment. HPE Morpheus Enterprise has developed and supports a plugin which allows an OLVM environment to be integrated and consumed as any other Cloud type within the HPE Morpheus Enterprise ecosystem. OLVM Clouds can be scoped to individual OLVM datacenters or scoped across all datacenters depending on configuration at the time of integration. Once integrated, HPE Morpheus Enterprise can automatically bring onboard OLVM resources including existing hosts, VMs (if desired), virtual images, networks and datastores.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Datacenter scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Adding an OLVM Cloud
+
+Adding OLVM Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the OLVM at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the OLVM plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), OLVM should be selectable as a Cloud type to add. Select it and click NEXT.
+
+At minimum, it’s required to configure the following to add the new Cloud:
+
+- **NAME:** A friendly name for the new OLVM Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx/ovirt-engine/api>)
+- **USERNAME:** Username for a OLVM service account, using an admin account will avoid any downstream permissions issues that could prevent features of the integration from working properly
+- **PASSWORD:** The password for the service account
+- **DATACENTER:** The Cloud may be scoped to a specific datacenter or to all datacenters
+
+You’ll know the API URL and credentials have been entered correctly when the DATACENTER dropdown becomes populated. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
+
+## Monitoring the OLVM Cloud
+
+After integrating the Cloud, click into the Cloud detail page to see high level details about the OLVM environment including computed costs, number and health of hosts, resource utilization, and the number of running workloads.
+
+![../../../_images/cloudDetail1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-096B3009-F0C1-4217-9152-D59226017104-high.png)
+
+Additional tabs on the detail page allow administrators to view a list of hosts (and click into a host detail page, if desired), view a list of running VMs (and click into a VM detail page, if desired), view and manage networks and datastores, view or add Docker clusters, and view any containers running on Docker hosts.
+
+## Provisioning to the OLVM Cloud
+
+There are multiple ways to consume the new OLVM Cloud as a provisioning target. Adding an OLVM Cloud to HPE Morpheus Enterprise adds the OLVM Instance Type to the provisioning wizard. From the Instance list page (Provisioning > Instances), click + ADD and select “OLVM.”
+
+![../../../_images/olvmInsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6CDB3D9E-AFDF-45DC-830C-0356DCF91ABA-high.png)
+
+HPE Morpheus Enterprise syncs in all available Virtual Images from OLVM and presents them along with Datacenter and Cluster selections. Select the proper resource sizing and image template to provision a new VM into OLVM.
+
+![../../../_images/configIns.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E0A6E761-BCFB-4307-8E0F-76A9548B7230-high.png)
+
+In addition to using the built-in OLVM Instance Type, adding the OLVM Cloud allows administrators to add OLVM-type Layouts to new or existing Instance Types. Add new Layouts in the HPE Morpheus Enterprise Library (Library > Blueprints > Layouts). When adding a new Layout, select “OLVM” from the Technology dropdown to make this Layout available when an OLVM Cloud has been selected as the provisioning target. See the Library section of HPE Morpheus Enterprise UI documentation for more details on building out Library items.
+
+![../../../_images/layoutTech.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A46EF9A1-9EC9-416E-BB80-3B516BF4BB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json b/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
new file mode 100644
index 0000000..3d5f042
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+  "title": "Costing: Workload Costing",
+  "ordinal": 62,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Workload Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md b/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
new file mode 100644
index 0000000..8243ca8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
@@ -0,0 +1,26 @@
+# Costing: Workload Costing
+
+![../_images/5workloadcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-102FBE32-895E-4617-80D4-AA313E7BB572-high.png)
+
+The Workload Costing dashboard allows administrators to look at all or a subset of HPE Morpheus Enterprise-managed workloads to analyze their cost impact. Filters can be set to isolate a specific group of workloads and cost breakdowns are shown. Graphs are generated to reveal cost breakdowns of individual workloads or certain groups of workloads.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matched by search)
+- Group
+- Cloud
+- Tenant
+- Tag (Key). This is a required field and the top key in the list will be pre-selected by default
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all workloads that meet set filters:
+
+- **WORKLOADS:** The total number of workloads that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all workloads meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all workloads meeting dashboard filters
+- **TYPES:** The total number of workload types represented among workloads meeting set filters
+- **SIZES:** The total number of unique workload sizes represented among workloads meeting set filters
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json b/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
new file mode 100644
index 0000000..c0d8469
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+  "title": "Communication Data",
+  "ordinal": 51,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md b/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
new file mode 100644
index 0000000..3aa1028
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
@@ -0,0 +1,156 @@
+# Communication Data
+
+The following page contains communication information between the HPE Morpheus Enterprise appliance, integrated technologies, managed machines, and services.
+
+## Communication Frequency and Configurability
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency and Configurability
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Elastic Search Check | Server Pull | Elastic Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | 5 minutes | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Push | ServiceNow | Sync HPE Morpheus Enterprise library items to ServiceNow catalog | Nightly | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
+
+## Ports and Protocols
+
+The following table contains communication port and protocol data between HPE Morpheus Enterprise appliance tiers, managed machines, and services. All communication to and from HPE Morpheus Enterprise goes thru the application tier with exception of inter-cluster communications for each of the HPE Morpheus Enterprise tiers when using a distributed architecture.
+
+Ports used to communicate with integrated technologies are those defined for the integration’s API. They are not represented in this table as many of these are configurable and may be different in each customer environment. Additionally, ports used to complete Morpheus checks are customizable and may vary for each check configured. They are also not represented in this table.
+
+Table 2. Ports and Protocols
+
+       | Source | Destination | Port | Protocol | Description |
+| --- | --- | --- | --- | --- |
+| User | Application Tier | 443 | TCP | User Access |
+| Morpheus Servers | DNS Servers | 53 | TCP | Domain Name Resolution |
+| Morpheus Servers | Time Source | 123 | TCP | Time Resolution |
+| Morpheus Servers | Web or Offline Installer | 80, 443 | TCP | Download repos and Morpheus packages (yum/apt repos) |
+| Managed Machine | Application Tier | 443 | TCP | Morpheus Agent Communications |
+| Managed Machine | Application Tier | 80, 443 | TCP | Agent Installation. (Requires port 80 only for Ubuntu 14.04) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Clout‐init (Linux) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Cloudbase‐init (Windows) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation VMtools |
+| Managed Machine | Application Tier | N/A | N/A | Static IP Assignment & IP Pools (Cloud‐init or VMware Tools) |
+| Managed Machine | Docker Image Repo | 443 | TCP | Applicable if using docker |
+| Managed Machine | Application Tier | 69 | TCP/UDP | PXE Boot (Forwarded to internal PXE port 6969) |
+| Application Tier | Managed Machine | 5985 | TCP | Agent Installation WinRM (Windows) |
+| Application Tier | Managed Machine | 22 | TCP | Agent Installation SSH (Linux) |
+| Application Tier | Managed Machine | 22, 3389, 443 | TCP | Remote Console (SSH, RDP, Hypervisor Console |
+| Application Tier | AWS S3 | 443 | TCP | Morpheus Catalog Image Download |
+| Application Tier | Hypervisor | 443 | TCP | Hypervisor hostname resolvable by Morpheus Application Tier |
+| Application Tier | Non‐ Transactional Database Tier | 443 | TCP | Applicable if using Amazon Elasticsearch Service |
+| Application Tier | Docker CE Repo | 443 | TCP | Applicable only when integrated with Docker |
+| Application Tier | Rubygems | 443 | TCP |  |
+| Application Tier | Morpheus Hub | 443 | TCP | (Optional) Telemetry data (Disabled only via license feature) |
+| Application Tier | Mail Server | 25 or 465 | SMTP | Send email from Morpheus |
+| Application Tier | postmarkapp | 2525 | TCP | Send email from Morpheus (such as alerts and password reset requests) when custom SMTP settings aren’t present |
+| Application Tier | Messaging Tier | 5672 | TCP | AMQP non‐TLS connections |
+| Application Tier | Messaging Tier | 5671 | TCP | AMQPS TLS enabled connections |
+| Application Tier | Messaging Tier | 61613 | TCP | STOMP Plugin connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Application Tier | Messaging Tier | 61614 | TCP | STOMP Plugin TLS enabled connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Messaging Tier | Messaging Tier | 25672 | TCP | Inter‐node and CLI tool communication |
+| Administrator Web Browser | RabbitMQ Server Management | 15672 | TCP | Management plugin |
+| Administrator Web Browser | RabbitMQ Server Management | 15671 | TCP | Management plugin SSL |
+| Messaging Tier Cluster Node | Messaging Tier Cluster Node | 4369 | TCP | erlang (epmd) peer discovery service used by RabbitMQ nodes and CLI tools |
+| Application Tier | Non‐Transactional Database Tier | 9200 | TCP | Elasticsearch requests (Used in all cases except when utilizing AWS ES service) |
+| Application Tier | Non‐Transactional Database Tier | 443 | TCP | Elasticsearch requests (Used in all cases where ES is consumed as a PaaS service) |
+| Non‐Transactional Database Tier | Non‐Transactional Database Tier | 9300 | TCP | Elasticsearch Cluster |
+| Transactional Database Tier | Transactional Database Tier | 4567 | TCP/UDP | Write‐set replication traffic (over TCP) and multicast replication (over TCP and UDP). |
+| Transactional Database Tier | Transactional Database Tier | 4568 | TCP | Incremental State Transfer (IST) |
+| Application Tier | Transactional Database Tier | 3306 | TCP | MySQL client connections |
+| Backup Solution | Transactional Database Tier | 4444 | TCP | State Snapshot Transfer (SST) |
+| Application Tier | Integrated Technology | Varies | TCP | Integrations (Uses the port of the 3rd party systems API) |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json b/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
new file mode 100644
index 0000000..37e681f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+  "title": "Offline Installations and Upgrades",
+  "ordinal": 32,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html",
+  "topic_cluster": {
+    "clustering_title": "Offline Installations and Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md b/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
new file mode 100644
index 0000000..2af4ba1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
@@ -0,0 +1,104 @@
+# Offline Installations and Upgrades
+
+For customers that have an appliance behind a firewall/proxy that does not allow downloads from our Amazon download site, you can add the supplemental package to add the needed packages the standard Morpheus installer would have downloaded.
+
+## Offline Installation Requirements
+
+- NTP should be correctly configured and the server is able to connect to the NTP server in the ntp.conf file
+- The OS package repositories should be configured to use local LAN repository servers or the server should be able to receive packages from the configured repositories
+- The standard Morpheus and supplemental packages must be downloaded from another system and transferred to the Morpheus Appliance server
+- The supplemental package is additive, the full installer is also required
+
+NOTE
+
+The supplemental package is linked 1-to-1 to the appliance release. For example the supplemental package for 4.2.1-1 should be used with the appliance package 4.2.1-1
+
+## Offline Install
+
+## Ubuntu/Debian
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the Supplemental packages on to the appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_version_amd64.deb  
+   wget http://example_url/morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_version_amd64.deb  
+   sudo dpkg -i morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   # edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus log file located at /var/log/morpheus/morpheus-ui/current with the command `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
+
+## CentOS/RHEL
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the matching Supplemental package on to the Appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_package_url.noarch.rpm  
+   wget http://example_url/morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo rpm -i morpheus-appliance_package_url.noarch.rpm  
+   sudo rpm -i morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   #Edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus-ui log file with `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json b/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
new file mode 100644
index 0000000..f4ba2ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+  "title": "Default Unmanaged Network Support",
+  "ordinal": 402,
+  "parent_title": "Creating an HPE BMaaS Cloud",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html",
+  "topic_cluster": {
+    "clustering_title": "Default Unmanaged Network Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md b/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
new file mode 100644
index 0000000..c5ef5a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
@@ -0,0 +1,15 @@
+# Default Unmanaged Network Support
+
+HPE Morpheus Enterprise 8.0.13 and later automatically create a default unmanaged network during the **Bare Metal Cloud** creation process.
+
+When you select Unmanaged Network as the network mode, HPE Morpheus performs the following actions:
+
+- Creates a default unmanaged network automatically.
+- Configures the network to use DHCP for IP allocation.
+- Enables immediate selection of the network during instance provisioning.
+
+The below image shows the default unmanaged network automatically created during Bare-Metal cloud creation.   
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9CB5E90B-9DED-4601-84AD-CA4E4538E297-high.png)
+
+The below image shows an untagged VLAN configuration with DHCP selected as the IP allocation method.   
+![Edit Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C186BB86-0721-493C-B4ED-10864ABF69F3-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..d93b16a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 230,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..b4dc4e1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,462 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
+
+## Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+
+## Alibaba Buckets
+
+### About this task
+
+To Add an Alibaba Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Amazon S3 Buckets
+
+### About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Google Cloud Storage Buckets
+
+### About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in HPE Morpheus Enterprise
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in HPE Morpheus Enterprise
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of HPE Morpheus Enterprise
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by HPE Morpheus Enterprise. When selecting ‘Backup Old Files’, HPE Morpheus Enterprise will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, HPE Morpheus Enterprise will delete any files that reach a certain number of days old
+
+## Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Openstack Swift Buckets
+
+### About this task
+
+To Add an Azure Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Rackspace CDN Buckets
+
+### About this task
+
+To Add a Rackspace CDN Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json b/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
new file mode 100644
index 0000000..322cce0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+  "title": "IPv6",
+  "ordinal": 38,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html",
+  "topic_cluster": {
+    "clustering_title": "IPv6",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md b/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
new file mode 100644
index 0000000..0f69d4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
@@ -0,0 +1,43 @@
+# IPv6
+
+## Overview
+
+There may be situations where instances only have IPv6 routing available. HPE Morpheus Enterprise fully supports IPv6 for the appliance and agent comms.
+
+To enable IPv6 listener on the HPE Morpheus Enterprise appliance, you must modify the NGINX listeners.
+
+## Configuring NGINX Listeners
+
+### Procedure
+
+1. Confirm IPv6 is enabled and IP address is applied within the Morpheus underlying OS.
+2. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:80;
+   ```
+   ```
+3. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus-ssl.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:443 ssl;
+   ```
+   ```
+4. Restart the NGINX service: 
+
+   ```
+   ```
+   morpheus-ctl restart nginx  
+   ok: run: nginx: (pid 47868) 0s
+   ```
+   ```
+5. The site should now be resolvable via IPv6. To test you should be able to do the following: 
+
+   ```
+   ```
+   curl -k -6 https://[<IPv6 Address>]/ping  
+   MORPHEUS PING
+   ```
+   ```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json b/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
new file mode 100644
index 0000000..81a4581
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+  "title": "Kubernetes Clusters",
+  "ordinal": 197,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md b/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
new file mode 100644
index 0000000..b966e6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
@@ -0,0 +1,363 @@
+# Kubernetes Clusters
+
+## Requirements
+
+- Agent installation is required for Master and Worker Nodes. Refer to [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html) section for additional information.
+- Access to Cloud Front, Image copy access and permissions for System and Uploaded Images used in Cluster Layouts
+  :   Image(s) used in Cluster Layouts must either exist in destination cloud/resource or be able to be copied to destination by Morpheus, typically applicable for non-public clouds. For the initial provision, Morpheus System Images are streamed from Cloud Front through Morpheus to target destination. Subsequent provisions clone the local Image.
+- System Kubernetes Layouts require Master and Worker nodes to access to the following over 443 during K8s install and configuration:
+
+  - Morpheus Appliance url (443)
+  - <https://packages.cloud.google.com>
+  - <https://storage.googleapis.com>
+  - <https://docs.projectcalico.org>
+  - <https://openebs.github.io>
+  - <https://cloud.weave.works>
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
+
+## Creating Kubernetes Clusters
+
+### About this task
+
+Provisions a new Kubernetes Cluster in selected target Cloud using selected Layout.
+
+NOTE
+
+When deploying a highly-available Kubernetes cluster, it’s important to note that HPE Morpheus Enterprise does not currently auto-deploy a load balancer. Additionally, when HPE Morpheus Enterprise runs the `kubeadm init` command in the background during cluster provisioning, it also sets the `--control-plane-endpoint` flag to the first control plane node. This is a hard-coded behavior. To accomplish a highly-available cluster, users may wish to update the configured control plane endpoint, such as to a DNS name pointing to a load balancer. We are currently investigating updates to the product that would allow the user to specify such a DNS name prior to kicking off cluster provisioning. Additionally, users can circumvent this issue by configuring and deploying their own custom Cluster Layouts.
+
+HPE Morpheus Enterprise maintains a number of default Kubernetes Cluster Layouts which are updated frequently to offer support for current versions. AKS & GKE Kubernetes versions will dynamically update to the providers supported versions. HPE Morpheus Enterprise also supports creation of custom Kubernetes Cluster Layouts, a process which is described in detail in a later section.
+
+To create a new Kubernetes Cluster:
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Kubernetes Cluster`
+4. Select a Group for the Cluster
+5. Select NEXT
+6. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Kubernetes Cluster
+
+   RESOURCE NAME
+   :   Name for Kubernetes Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+7. Select NEXT
+8. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   LAYOUT
+   :   Select from available layouts. System provided layouts include Single Master and Cluster Layouts.
+
+   PLAN
+   :   Select plan for Kubernetes Master
+
+   VOLUMES
+   :   Configure volumes for Kubernetes Master
+
+   NETWORKS
+   :   Select the network for Kubernetes Master & Worker VM’s
+
+   CUSTOM CONFIG
+   :   Add custom Kubernetes annotations and config hash
+
+   CLUSTER HOSTNAME
+   :   Cluster address Hostname (cluster layouts only)
+
+   POD CIDR
+   :   POD network range in CIDR format ie 192.168.0.0/24 (cluster layouts only)
+
+   WORKER PLAN
+   :   Plan for Worker Nodes (cluster layouts only)
+
+   NUMBER OF WORKERS
+   :   Specify the number of workers to provision
+
+   LOAD BALANCER
+   :   Select an available Load Balancer (cluster layouts only) }
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain override for DNS records
+
+       HOSTNAME
+       :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+
+   Autoscaler
+   :   The Cluster Autoscaler is a Kubernetes component that automatically adjusts the number of worker nodes in your cluster based on the resource requirements of your workloads. When application demand increases and existing nodes are unable to schedule new pods, the autoscaler adds additional nodes to the cluster. Conversely, when demand drops and nodes become underutilized, the autoscaler removes unnecessary nodes, helping to optimize resource usage and control costs.
+   :   NOTE
+
+       During scale down, the Cluster Autoscaler will skip nodes that have workloads which cannot be safely evicted, such as pods with persistent or local storage (e.g., Rook Ceph), or pods that are constrained by affinity or anti-affinity rules.
+   :   |  |  |
+       | --- | --- |
+       | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+       | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+       | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+9. Select NEXT
+10. Select optional Workflow to execute
+11. Select NEXT
+12. Review and select COMPLETE 
+
+    - The Master Node(s) will provision first.
+    - Upon successful completion of VM provision, Kubernetes scripts will be executed to install and configure Kubernetes on the Masters.
+      :   NOTE
+
+          Access to the sites listed in the [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892) section is required from Master and Worker nodes over 443
+    - After Master or Masters are successfully provisioned and Kubernetes is successfully installed and configured, the Worker Nodes will provision in parallel.
+    - Provision status can be viewed:
+      :   - From the Status next to the Cluster in Infrastructure  >  Clusters
+          - Status bar with eta and current step available on Cluster detail page, accessible by selecting the Cluster name from Infrastructure  >  Clusters
+    - All process status and history is available - From the Cluster detail page History tab, accessible by selecting the Cluster name from Infrastructure  >  Clusters and the History tab - From Operations - Activity - History - Individual process output available by clicking i on target process
+13. Once all Master and Worker Nodes are successfully provisioned and Kubernetes is installed and configured, the Cluster status will turn green. 
+
+    IMPORTANT
+
+    Cluster provisioning requires successful creation of VMs, Agent Installation, and execution of Kubernetes workflows. Consult process output from ``Infrastructure  >  Clusters - Details and morpheus-ui current logs at `Administration - Health - Morpheus Logs` for information on failed Clusters.
+
+### Intra-Kubernetes Cluster Port Requirements
+
+The table below includes port requirements for the machines within the cluster (not for the HPE Morpheus Enterprise appliance itself). Check that the following ports are open on Control-plane and Worker nodes:
+
+Table 1. Control‐plane node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 6443 | Kubernetes API Server | All |
+| TCP | Inbound | 6783 | Weaveworks |  |
+| TCP | Inbound | 2379‐2380 | etcd server client API | kube‐apiserver, etcd |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 10251 | kube‐scheduler | Self |
+| TCP | Inbound | 10252 | kube‐controller‐manager | Self |
+
+Table 2. Worker node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 30000‐32767 | NodePort Services | All |
+
+## Adding Worker Nodes
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `ADD (type) Kubernetes Worker` 
+
+   NAME
+   :   Name of the Worker Node. Auto=populated with `${cluster.resourceName}-worker-${seq}`
+
+   DESCRIPTION
+   :   Description of the Worker Node, displayed in Worker tab on Cluster Detail pages, and on Worker Host Detail page
+
+   CLOUD
+   :   Target Cloud for the Worker Node.
+4. Select NEXT
+5. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   SERVICE PLAN
+   :   Service Plan for the new Worker Node
+
+   NETWORK
+   :   Configure network options for the Worker node.
+
+   HOST
+   :   If Host selection is enabled, optionally specify target host for new Worker node
+
+   FOLDER
+   :   Optionally specify target folder for new Worker node
+       :   Advanced Options
+           :   DOMAIN
+               :   Specify Domain override for DNS records
+
+               HOSTNAME
+               :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+6. Select NEXT
+7. Select optional Workflow to execute
+8. Select NEXT
+9. Review and select COMPLETE
+
+### Results
+
+NOTE
+
+Ensure there is a default StorageClass available when using a Morpheus Kubernetes cluster with OpenEBS so that Kubernetes specs or HELM templates that use a default StorageClass for Persistent Volume Claims can be utilised.
+
+## Configure Autoscaler
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `Configure Autoscaler`
+4. |  |  |
+   | --- | --- |
+   | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+   | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+   | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+5. Select `Apply`
+
+## Kubernetes Cluster Detail Pages
+
+The Kubernetes Cluster Detail page provides a high degree of monitoring and control over Kubernetes Clusters. This includes monitoring of all nodes in the Cluster, `kubectl` command line, account and role control, workload management, and more. The upper section of the page (which is persistent regardless of the currently-selected tab) provides high level costing and monitoring information, including a current aggregate metric for the CPU, memory and storage use.
+
+![../../_images/clusterDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-824D0DA3-5400-4EF0-BE66-A96F64902C89-high.png)
+
+The upper section also includes the ACTIONS menu which includes the following functions:
+
+- **REFRESH:** Forces a routine sync of the cluster status
+- **PERMISSIONS:** View and edit the Group, Service Plan, and Tenant access permissions for the cluster
+- **VIEW API TOKEN:** Displays the API token for the cluster
+- **VIEW KUBE CONFIG:** Displays the cluster configuration
+- **RUN WORKLOAD:** Run deployments, stateful sets, daemon sets, or jobs and target them to a specific namespace
+- **UPGRADE CLUSTER:** Upgrade the cluster to a higher version of Kubernetes
+
+  IMPORTANT
+
+  Kubelet configuration cleanup is required to upgrade clusters. The `--pod-infra-container-image` flag is deprecated from Kubernetes version 1.35.3. Upgrading clusters to v1.35.3 or later will fail if this deprecated flag is present in the Kubelet configuration. This flag must be manually removed from all nodes prior to initiating the upgrade process. See upgrade process below:
+  1. Edit the kubelet environment configuration file with `sudo vim /var/lib/kubelet/kubeadm-flags.env`
+  2. Locate the `KUBELET_KUBEADM_ARG`S entry and remove the following entry: `--pod-infra-container-image=registry.k8s.io/pause:3.10`
+  3. Save the file and exit the editor
+  4. Reload the configuration and restart the service with `sudo systemctl daemon-reload` and `sudo systemctl restart kubelet`
+  5. This process is repeated for all cluster nodes
+- **ADD KUBERNETES WORKER:** Launches a wizard which allows users to configure a new worker for the cluster
+
+Additional monitoring and control panes are located within tabs, some of which contain subtabs.
+
+- [Summary](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22330E1_D22331E1_D22332E1_D22333E1_D22334E1_D22335E1)
+- [Control](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22340E1_D22341E1_D22342E1_D22343E1_D22344E1_D22345E1)
+- [Access](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22350E1_D22351E1_D22352E1_D22353E1_D22354E1_D22355E1)
+- [Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22360E1_D22361E1_D22362E1_D22363E1_D22364E1_D22365E1)
+- [Workloads](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22370E1_D22371E1_D22372E1_D22373E1_D22374E1_D22375E1)
+- [Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22380E1_D22381E1_D22382E1_D22383E1_D22384E1_D22385E1)
+- [Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22390E1_D22391E1_D22392E1_D22393E1_D22394E1_D22395E1)
+- [Containers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22400E1_D22401E1_D22402E1_D22403E1_D22404E1_D22405E1)
+- [Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22410E1_D22411E1_D22412E1_D22413E1_D22414E1_D22415E1)
+- [History](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22420E1_D22421E1_D22422E1_D22423E1_D22424E1_D22425E1)
+- [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22430E1_D22431E1_D22432E1_D22433E1_D22434E1_D22435E1)
+
+### Summary
+
+The summary tab contains high-level details on health and makeup of the cluster. ![../../_images/clusterSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-42D2FAC8-D054-4AEC-8D10-59C6B15EE02A-high.png)
+
+### Control
+
+Contains the `kubectl` command line with ability to target commands to specific namespaces. The Control tab also contains the Packages subtab which displays the list of packages and their versions. ![../../_images/clusterControl.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-88388DAC-D1A7-4218-B17A-D605AB1D9095-high.png)
+
+### Access
+
+The Access Tab contains view and edit tools for Namespaces, accounts, roles, and role bindings. ![../../_images/clusterAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BC2EC859-76DA-4EC4-883C-DBA8BAD9DD52-high.png)
+
+### Nodes
+
+The nodes tab includes a list of master and worker nodes in the cluster, their statuses, and the current compute, memory, and storage pressure on each node. ![../../_images/clusterNodes.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-88E093F0-4EAB-4E6D-A023-F1C70F06812A-high.png)
+
+### Workloads
+
+View and edit existing Pods, Deployments, Replica Sets, Daemon Sets, Stateful Sets, and Jobs. Add new Deployments, Stateful Sets, Daemon Sets, and Jobs through the ACTIONS menu near the top of the Cluster Detail Page. ![../../_images/clusterWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5AA1E4AA-4AD5-4A7F-A274-2D7C01357494-high.png)
+
+### Network
+
+View, add, and edit Services, Endpoints, Ingress and Network Policies ![../../_images/clusterNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A94FC46E-8856-411E-8E6A-F2B6DBEAB45F-high.png)
+
+### Storage
+
+View, add, and edit Storage classes, Volume claims, Volumes, Config maps, and Secrets ![../../_images/clusterStorage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2A352500-C7FF-43CD-B91B-AD299208090B-high.png)
+
+### Containers
+
+View a list of containers running on the cluster and restart or delete them if needed. This list can be filtered by Namespace or a specific Worker if desired. ![../../_images/clusterContainers.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8D0ABC87-4D4D-4A4B-91A3-214698B516DD-high.png)
+
+### Monitoring
+
+View logs and events with filtering tools and search functionality available. ![../../_images/clusterMonitoring.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-02EEA1D6-F4BE-4060-AEBB-B6A2BD715EF6-high.png)
+
+### History
+
+View the Cluster lifecycle history. This includes lists of automation packages (Tasks and Workflows) run against the cluster or its nodes, the success of these scripts and the output. ![../../_images/clusterHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-394CC8A6-5257-4B4C-BF41-E10643BEEE8A-high.png)
+
+### Wiki
+
+View the HPE Morpheus Enterprise Wiki entry for this Cluster. This Wiki page may also be viewed in the Wiki section (Operations > Wiki). Edit the Wiki as desired, most standard Markdown syntax will be honored allowing the use of headings, links, embedded images, and more. ![../../_images/clusterWiki.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BAD395AC-5FAD-495D-B797-EEDA93C17B73-high.png)
+
+## Adding External Kubernetes Clusters
+
+HPE Morpheus Enterprise supports the management and consumption of Kubernetes clusters provisioned outside of HPE Morpheus Enterprise. These are referred to as External Kubernetes Clusters in HPE Morpheus Enterprise UI. This could be used, for example, to onboard and manage OpenShift clusters. In order to fully integrate the Kubernetes cluster with the HPE Morpheus Enterprise feature set, you may need to create a service account for HPE Morpheus Enterprise. Without first taking that step, some features may not work fully, such as listing all namespaces. The process for creating a service account and integrating the Cluster with HPE Morpheus Enterprise is described here.
+
+First, create the Service Account within the Kubernetes cluster:
+
+```
+```
+kubectl create serviceaccount morpheus
+```
+```
+
+Next, create the Role Binding:
+
+```
+```
+kubectl create clusterrolebinding morpheus-admin \  
+--clusterrole=cluster-admin --serviceaccount=default:morpheus \  
+--namespace=default
+```
+```
+
+With those items created, we can gather the API URL and the API token which will be used to add the existing cluster to HPE Morpheus Enterprise in the next step:
+
+```
+```
+kubectl config view --minify | grep server | cut -f 2- -d ":" | tr -d " "
+```
+```
+
+```
+```
+SECRET_NAME=$(kubectl get secrets | grep ^morpheus | cut -f1 -d ' ')  
+kubectl describe secret $SECRET_NAME | grep -E '^token' | cut -f2 -d':' | tr -d " "
+```
+```
+
+After finishing those steps, we can now create the external cluster in HPE Morpheus Enterprise. Navigate to Infrastructure > Clusters. Click + ADD CLUSTER and then select “External Kubernetes Cluster”. Set the following fields, you will have to advance through the pages of the wizard to see all fields indicated:
+
+- **GROUP:** A previously created HPE Morpheus Enterprise Group
+- **CLOUD:** A previously-integrated Cloud
+- **CLUSTER NAME:** A friendly name for the onboarded cluster in HPE Morpheus Enterprise UI
+- **RESOURCE NAME:** The resource name will be pre-pended to Kubernetes hosts associated with this cluster when shown in HPE Morpheus Enterprise UI
+- **LAYOUT:** Set an associated Layout
+- **API URL:** Enter the API URL gathered in the previous step
+- **API TOKEN:** Enter the API Token gathered in the previous step
+- **KUBE CONFIG:** Enter Kubeconfig YAML to authenticate the cluster
+
+The above are the required fields, others may be optionally configured depending on the situation. Complete the wizard and HPE Morpheus Enterprise will begin the process of onboarding the existing cluster into management within HPE Morpheus Enterprise UI. Once things are finalized and statuses are green, the cluster can be monitored and consumed as any other cluster provisioned from HPE Morpheus Enterprise.
+
+![../../_images/extKube.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E72E1043-FF51-4388-9D80-79CC7660C86A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json b/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
new file mode 100644
index 0000000..2e45176
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+  "title": "Tenant Roles",
+  "ordinal": 304,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md b/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
new file mode 100644
index 0000000..b563ad2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
@@ -0,0 +1,8 @@
+# Tenant Roles
+
+A Tenant Role sets the highest possible permissions for a Tenant. User Roles within that Tenant cannot exceed those of the Tenants assigned Tenant Role. Tenant Roles can be assigned to single or multiple Tenants, and do not apply to the Master Account.
+
+**Subtopics**  
+
+- **[To create a Tenant Role:](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html)**
+- **[Setting an Optional Landing URL](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json b/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
new file mode 100644
index 0000000..8de0691
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+  "title": "Nutanix Prism Element",
+  "ordinal": 462,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Element",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md b/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
new file mode 100644
index 0000000..6cea424
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
@@ -0,0 +1,188 @@
+# Nutanix Prism Element
+
+## Overview
+
+Nutanix Prism Element simplifies datacenter infrastructure by integrating server and storage resources allowing applications to run at scale. HPE Morpheus Enterprise enhances Nutanix resources by allowing efficient and seamless deployment of virtualized or containerized applications, management of existing brownfield resources in Nutanix Clouds, pricing and cost tracking, and monitoring of running workloads.
+
+## Features
+
+- Virtual machine provisioning
+- Brownfield discovery
+- Containers
+- Backups / Snapshots
+- Datastores
+- Kubernetes
+- Resources Groups
+- Migrations
+- HPE Morpheus Enterprise costing and pricing
+- Auto Scaling
+- Load Balancing
+- Remote Console for hypervisor hosts and running workloads
+- Two-way Cloud sync
+- Lifecycle Management and Resize
+
+NOTE
+
+Prism Central is currently supported and is maintained as a separate, plugin-based Cloud integration. See the [Prism Central plugin page](https://share.morpheusdata.com/plugin/morpheus-nutanix-prism/about) on the HPE Morpheus Enterprise plugin share site for additional details and access to the plugin. There is also an [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/prismCentral/prismCentral.html) for that plugin here in HPE Morpheus Enterprise UI documentation.
+
+## Getting Started
+
+To get started, first confirm that a few prerequisite steps have been completed. The Nutanix cluster should be provisioned and available on the network. In a typical configuration, Nutanix will be available at the `https://fqdn:9440` URL. Have the credentials for an administrator service account available to integrate HPE Morpheus Enterprise with the Nutanix cluster. With those prerequisites already completed, you’re ready to add a Nutanix Cloud to HPE Morpheus Enterprise using the instructions in the next section.
+
+## Adding a Nutanix Cloud
+
+To start, navigate to the Cloud list page (Infrastructure > Clouds) and click + ADD. On the ADD CLOUD modal, you will at least need to provide a NAME for the Cloud in HPE Morpheus Enterprise along with the API URL and credentials. Other fields listed here are optional but may be needed for the Cloud to perform as desired in your environment.
+
+- **NAME:** A name for the Nutanix Cloud within HPE Morpheus Enterprise
+- **CODE:** A unique code for the cloud which is used in HPE Morpheus Enterprise API, CLI, and in automation scripts
+- **LABELS:** Select or create a new Label to apply to the Cloud. See [Labels documentation](https://docs.morpheusdata.com/en/latest/library/labels.html) for a complete description of the usefulness of Labels
+- **LOCATION:** An optional description field for the Cloud to hold location information
+- **VISIBILITY:** For multitenant environments, sets the visibility level for Tenants outside of the one the Cloud resources are assigned to
+- **TENANT:** If the visibility is set to private, this sets the Tenant the Cloud resources are assigned to
+- **ENABLED:** When checked, HPE Morpheus Enterprise will perform regular syncs with this Cloud and the Cloud will also be selectable as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** Indicates whether HPE Morpheus Enterprise should control the power state for provisioned VMs (not brownfield discovered VMs). If VMs are powered off for an unknown reason (that is, outside of HPE Morpheus Enterprise) they will be powered back on. Leave unchecked if you wish to manage workload power state outside of HPE Morpheus Enterprise
+- **API URL:** The URL for the Nutanix Prism API, typically in a format like `https://xx.xx.xx.xx:9440`
+- **CREDENTIALS:** Choose a pre-stored username/password credential set or enter a username/password set. If entering the credentials locally, you may also choose to securely store the credentials for later use. Depending on selection, additional fields will be added to facilitate that choice
+- **API VERSION:** Select the API version supported by your Nutanix environment to ensure HPE Morpheus Enterprise is not targeting endpoints which are incompatible with your environment
+- **INVENTORY EXISTING INSTANCES:** When checked, HPE Morpheus Enterprise will automatically onboard workloads which are already running in the Nutanix environment but which were provisioned outside of HPE Morpheus Enterprise. These may be brought under HPE Morpheus Enterprise management at a later time, if desired
+- **ENABLE HYPERVISOR CONSOLE:** When checked, enables remote console support directly to the hypervisor
+
+In addition to these basic settings, there are also some advanced options. These are similar but not identical for every Cloud type and some of them may not appear for Nutanix Clouds.
+
+### Advanced Cloud Options
+
+**Advanced Options**
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+**CUSTOM LOGOS**
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+**INVENTORY OPTIONS**
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+**Provisioning Command**
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+With the above configurations made, click NEXT. Choose to add the Cloud to an existing Group or to create a new Group and click NEXT once again. Finally, review the details of the new Cloud on the REVIEW tab and click COMPLETE if all looks good. At this point the new Cloud will be added to HPE Morpheus Enterprise and the initial Cloud sync will begin. On the Cloud list page (Infrastructure > Clouds), we will see the Cloud in an “OK” status once it is ready to be consumed in HPE Morpheus Enterprise as a provisioning target. Click into the Cloud detail page by clicking on the NAME of the Cloud from the list. Continue on to the next section for an overview of the details available on the Cloud detail.
+
+## Monitoring Nutanix Clouds
+
+On clicking into the Nutanix Cloud, you’ll land on the Summary tab. Here we can see high-level details including cost metrics for the month, general resource utilization information, and information on the number of hosts, workloads, and more that are currently running within the Cloud scope.
+
+![../../../_images/cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1E122ED6-DF89-43B3-AB53-F645F37F8371-high.png)
+
+You’ll also notice the Clusters tab. Here you can see and click into any Docker or Kubernetes Clusters which are running on the Nutanix Cloud. HPE Morpheus Enterprise will see these clusters as provisioning targets themselves for containerized applications (as opposed to the Cloud itself for virtualized applications). You can also add new Kubernetes or Dockers clusters from this tab. HPE Morpheus Enterprise includes built-in Cluster Layouts but custom Cluster Layouts can also be created. There is a guide on creating your own custom Kubernetes Cluster Layouts in the Clusters section of HPE Morpheus Enterprise UI documentation.
+
+On the Hosts tab, you’ll see all Nutanix hypervisior hosts which are associated with the cluster. Host health metrics are viewable and we can click into individual hosts to see even greater detail on the individual host detail pages.
+
+The VM and Containers tabs show all current VM and container workloads across the cluster. When integrating the Cloud, if you opted to inventory existing workloads, discovered resources will appear here. If not (or if there simply are none), only HPE Morpheus Enterprise-provisioned workloads will appear here.
+
+## Provisioning New Workloads
+
+With the Cloud integrated, you’re already to provision new workloads. HPE Morpheus Enterprise comes pre-installed with a number of default library items designed to work with each supported Cloud integration type, including Nutanix. While this guide will not go through the process of using the provisioning wizard (see Provisioning > Instances page to start), you could provision a default workload to test functionality now if desired. Additionally, HPE Morpheus Enterprise will sync Virtual Images from Nutanix Clouds (Library > Virtual Images) and custom Library items may be built from these images. See the Library section of HPE Morpheus Enterprise documentation for more information on piecing together Instance Types, images, and automation scripts into cohesive and easily-consumed Library items.
+
+## Service Plans
+
+HPE Morpheus Enterprise includes a default set of Service Plans. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, and CPU cores. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Nutanix or create a new one. These all can be easily managed from the Administration > Plans & Pricing section.
+
+## Docker
+
+So far, this document has covered how to add the Nutanix cloud integration and has enabled users the ability to provision virtual machine-based Instances. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this, a Docker Host must first be provisioned into Nutanix (multiple are needed when dealing with horizontal scaling scenarios). As mentioned previously, these can be viewed or created from the Clusters tab of the Cloud detail page.
+
+To provision a Docker Host, simply navigate to the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a Nutanix Docker Host. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top. Just like with VMs, HPE Morpheus Enterprise includes default containerized items out of the box so provisioning to Docker hosts can be tested even before you’ve created your own container-based Library items.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, then the Agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a Nutanix Instance. From the Instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the Instance detail page. Snapshots taken outside HPE Morpheus Enterprise will be synced every five minutes (by default). To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json b/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
new file mode 100644
index 0000000..3116554
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+  "title": "Load Balancer Configuration",
+  "ordinal": 31,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancer Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md b/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
new file mode 100644
index 0000000..4374b2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
@@ -0,0 +1,561 @@
+# Load Balancer Configuration
+
+For configurations with 2 or more Applications Nodes, a load balancer is recommended to ensure high availability (HA) from disruptions and upgrades. Below are the guidelines to configuring a load balancer for HPE Morpheus Enterprise but each configuration may differ based on the organization’s requirements.
+
+## Requirements
+
+- WebSockets enabled
+- Load Balance 443 (optionally redirect 80 to 443)
+
+  - SSL Termination (Offload), Bridging, and Passthrough are supported
+- Round-Robin or least connection distribution
+- HTTPS monitor `https://ip_address/ping` body for `MORPHEUS PING` or status of 200, for node operational health
+
+## Example configurations
+
+Below are a few examples of configuring load balancers to meet the needs of a HA configuration. The examples assume SSL bridging will be used, which means an SSL (TLS) certificate is presented by the load balancer to clients and the load balancer will communicate with the backend nodes via a different (possibly same) certificate. This configuration is recommended because the HPE Morpheus Enterprise application nodes will create self-signed certificates and the load balancer will present a valid certificate to end users. Additionally, all communication will be encrypted. This reduces the overhead of maintaining the certificates on the HPE Morpheus Enterprise application nodes, as the load balancer can ignore invaild certs on the application nodes. However, the certificates on the HPE Morpheus Enterprise application nodes are not required to be self-signed, they can be replaced with other trusted certificates following the [SSL Certificates](https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html) documentation.
+
+TIP
+
+The list below is not meant to be a complete list for all load balancers. The provided examples are common deployments that can be used for reference. The settings mentioned in the examples list the primary settings that may need to be configured, other settings are based on the organization’s needs requirements and own configuration.
+
+### F5 BIG-IP
+
+**Monitor**
+
+- **Type:** HTTPS
+- **Send String:** GET /ping
+- **Receive String:** MORPHEUS PING
+
+**Pool**
+
+- **Health Monitor:** Select monitor created in the **Monitor** section
+- **Load Balancing Method:** Least Connections (member) is recommended (alternatively Round Robin)
+- **Node Service Port:** 443/HTTPS
+
+**Virtual Server**
+
+- **Type:** Standard
+- **Service Port:** 443/HTTPS
+- **Protocol:** TCP
+- **Protocol Profile (Client):** tcp
+- **Protocol Profile (Server):** tcp
+- **HTTP Profile (Client):** http
+- **HTTP Profile (Server):** http
+- **SSL Profile (Client):** clientssl (or preferred profile with a trusted certificate)
+- **SSL Profile (Server):** serverssl
+- **Source Address Translation:** Auto Map
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### AWS Application Load Balancer (ALB)
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### HAProxy
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### Azure Application Gateway
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json b/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
new file mode 100644
index 0000000..2aea012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+  "title": "Veeam",
+  "ordinal": 383,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.html",
+  "topic_cluster": {
+    "clustering_title": "Veeam",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md b/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
new file mode 100644
index 0000000..fb2f5fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
@@ -0,0 +1,102 @@
+# Veeam
+
+Veeam is a backup and replication platform designed to work with popular on-prem cloud providers, including VMware, Microsoft Hyper-V, and vCloud Director. HPE Morpheus Enterprise integrates with your existing Veeam appliance which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Veeam with HPE Morpheus Enterprise, sharing a Veeam integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from Veeam backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Veeam integration as the default backup target for compatible clouds
+- Select Veeam integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Veeam Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Integrations
+2. Select + ADD
+3. Select Veeam
+4. Fill in the following: 
+
+   Name
+   :   Friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, this integration will be active and available for use
+
+   API URL
+   :   IP or Hostname of the Veeam Enterprise Manager, must be HTTPS for VEEAM 10
+
+   Port
+   :   Port number configured to access the Veeam server, must be 9398 for VEEAM 10
+
+   Username
+   :   Username for an admin service account in Veeam
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise)
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that added the integration
+
+           Public
+           :   Available to Subtenants (primary tenant option only)
+5. Click SAVE
+
+### Results
+
+NOTE
+
+Veeam Backup Enterprise Manager must be installed in order to successfully integrate HPE Morpheus Enterprise with Veeam.
+
+IMPORTANT
+
+Once Veeam service has been integrated with HPE Morpheus Enterprise, Veeam server(s) will be available to select as the backup provider for VMware, Hyper-V, and vCloud Director cloud integrations (Infrastructure > Clouds > Edit a compatible Cloud). To enable Veeam backups, select the appropriate Veeam server as the “backup provider” for your cloud integrations as needed. Failure to do so will result in blank `Backup Repositories` and `Backup Job Templates` options when configuring Veeam Backups during provisioning.
+
+## Set Veeam as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Veeam integrations are supported as backup target for VMware, Hyper-V, and vCloud Director Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware, Hyper-V, or vCD Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Veeam integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-96E45BAD-D2AD-43F9-AE73-7AF6E41035F2-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Veeam is set as the backup provider, Veeam will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Veeam backup type
+- **Repository:** Select a repository synced from the Veeam backup provider associated with the Cloud
+- **Managed Server:** Select a managed server associated with the backup server selected in the previous step
+- **Backup Name:** A name for the backup in Morpheus, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A8EBDB01-089D-4518-B943-4DACE51F7528-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Veeam
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..cf7ae9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 358,
+  "parent_title": null,
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..1b368d7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Guides](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
new file mode 100644
index 0000000..c24972c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+  "title": "Boot Menus",
+  "ordinal": 250,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Menus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
new file mode 100644
index 0000000..d66dff7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
@@ -0,0 +1,21 @@
+# Boot Menus
+
+System-seeded Boot Menus are displayed and user-created Boot Menus can be edited and deleted. User-created Boot Menus are edited or deleted by clicking on the pencil or trash can icon in the appropriate row.
+
+## Adding a Boot Menu
+
+To begin, click + ADD. Available fields include:
+
+- NAME: Name of the Boot Menu
+- DESCRIPTION: Description of the Boot Menu
+- TYPE: Select between **bios, uefi, ipxe and grub**
+- ENABLED: Determines if the Boot Menu is active
+- DEFAULT MENU
+- ROOT MENU
+- MENU NAME
+- BOOT IMAGE
+- ANSWER FILE
+- MENU CONTENT
+- SUB MENUS
+
+Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json b/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
new file mode 100644
index 0000000..e2de39b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+  "title": "Budgets",
+  "ordinal": 74,
+  "parent_title": "Costing",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html",
+  "topic_cluster": {
+    "clustering_title": "Budgets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md b/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
new file mode 100644
index 0000000..4545bef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
@@ -0,0 +1,51 @@
+# Budgets
+
+Budgets provide insight into spending across their designated scope, allowing users to create and plan a budget targeted to their account, clouds, tenants, users, or groups.
+
+## Creating A Budget
+
+1. Navigate to Operations  >  Costing  >  Budgets
+2. Start a new budget by clicking + ADD
+
+   1. **Name**
+   2. **Description**
+   3. **Scope:** Here you can choose which construct this budget is tied to (Account, Tenant, Cloud, Group, or User)
+   4. **Period:** Currently “Year” is the only option
+   5. **Year:** Select a year to set budgets for future years. Alternatively, select “custom” to create a multi-year budget or input a custom fiscal year if required by your organization
+   6. **Forecast Model:** Optionally apply a forecast model to the Budget. When applied, forecasted amounts for each budget interval will be computed and graphical trend lines will be shown based on the model computation
+   7. **Interval:** Choose Month, Quarter, Year then fill in the budgeted amount for that interval (for quarter and year interval Budgets the entered amount is evenly split across the months in the given interval)
+3. Click SAVE CHANGES
+
+![../_images/createBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-18A42C5E-8C61-4ADA-AF78-23E743A230ED-high.png)
+
+## Multi-year Budgets
+
+Some organizations may need to create multi-year budgets or may need to set a fiscal year period. By default, annual budgets are tied to a calendar year (January - December) but HPE Morpheus Enterprise offers the flexibility of setting a fiscal year period when needed. When selecting a value from the YEAR dropdown in the add/edit budget modal, select “Custom” rather than one of the discreet years from the list. After selecting Custom, START DATE and END DATE fields allow the user to input any desired fiscal year period. Users can enter a period of up to three years using the start and end date bookends. The entered period must be one, two or three full years, partial years are not permitted.
+
+In the example below, I’ve created a three-year budget:
+
+![../_images/multiBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5E19B144-131B-4F0D-892B-9D10DB431658-high.png)
+
+## Budget Monitoring
+
+As the year (or years) goes on, existing Budgets can be reviewed to compare actual spend against the budgeted amount. To access the Budget detail, navigate to Operations > Costing > Budgets and select the desired Budget. The reported actual amount for a given month will be the same as the total cost reported for the month on the Invoice with the same scoping (for the current month, projected cost is used). Depending on the Cloud type, this figure can be pulled from a public clouds live costing API (such as with AWS, Azure, or GCP Clouds) or from the HPE Morpheus Enterprise in-built cost metering for private clouds (like VMware).
+
+Example Budget, Cloud-scoped:
+
+![../_images/budget.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4A12A8C3-AB86-4D4A-AF4E-432D5D9515BA-high.png)
+
+Example Cloud Invoice for the same month:
+
+![../_images/invoice.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-36CA0790-41CA-421C-9971-50062F8B82F4-high.png)
+
+## Cloud Budgets
+
+If you scope a budget to a Cloud, visit the Cloud summary tab in Infrastructure  >  Clouds  >  Select Cloud to see a cost-to-budget breakdown for that Cloud.
+
+![../_images/cloudBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C731E3A8-F507-477B-93AB-71BC98DA37A0-high.png)
+
+## Budget Analytics
+
+In Operations  >  Analytics  >  Budget Analysis select scope (Account, Tenant, Cloud, Group, User) to view the budget analysis. If a budget exists for the selected scope, a cost breakdown against budgeted amounts will be shown.
+
+![../_images/budgetAnalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EA3645F4-5E49-4CFC-90CF-4A04880BF602-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json b/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
new file mode 100644
index 0000000..e75179b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+  "title": "Retrying Workflows",
+  "ordinal": 116,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html",
+  "topic_cluster": {
+    "clustering_title": "Retrying Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md b/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
new file mode 100644
index 0000000..05c1e7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
@@ -0,0 +1,7 @@
+# Retrying Workflows
+
+When a Workflow fails, HPE Morpheus Enterprise allows users to retry from the failed Task. Access the Workflow execution from the executions list page (Provisioning > Executions), from the Executions tab of the Workflow detail page (Library > Automation > Workflows > Selected Workflow), or from the History tab on the Instance detail page (Provisioning > Instances > Selected Instance). From the execution, select the Retry button which looks like a clockwise circular arrow and is highlighted in the screenshot below. This can be very useful as it allows you to resume what could potentially be a very long running Workflow from a point of failure without needing to start from the beginning. Similarly, if a provisioned Instance is in a failed state due to a failure in an attached Workflow (such as a failed Task in the Provision phase of an attached Provisioning Workflow), the user can opt to resume the Tasks from the failure point after making a correction and restore the Instance to a successfully-provisioned state.
+
+Retry Workflow Tasks Video Demo
+
+![../../_images/retryTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-433AD4AB-C735-49B2-913B-302BF3209248-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json b/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
new file mode 100644
index 0000000..b800ee6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+  "title": "Prerequisites",
+  "ordinal": 398,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md b/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
new file mode 100644
index 0000000..c5bb6a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
@@ -0,0 +1,55 @@
+# Prerequisites
+
+Before integrating the HPE BMaaS with Morpheus Enterprise, verify that the following prerequisites are met to ensure successful deployment and operation.
+
+## Supported Hardware
+
+HPE BMaaS supports the following HPE ProLiant server platforms:
+
+- HPE ProLiant Gen10 Plus servers
+- HPE ProLiant Gen11 servers
+- HPE ProLiant Gen12 servers
+
+Ensure that servers are equiped with a supported HPE iLO version and are reachable over the network.
+
+## Network Connectivity
+
+The Morpheus Enterprise appliance must have:
+
+- Network connectivity to the iLO management interface of each ProLiant server
+- Network connectivity to the physical data network interfaces used for operating system provisioning
+- Proper routing and firewall rules allowing bidirectional communication between Morpheus and target servers
+- For environments using managed networking, additional connectivity to supported network switches (for example, HPE Aruba CX) is required.
+
+## Access Credentials
+
+Ensure the following credentials are available for each ProLiant server:
+
+- iLO IP address
+- iLO administrator username
+- iLO administrator password
+
+Credentials must have sufficient privileges to perform power operations, hardware inventory, and virtual media mounting.
+
+## Morpheus Platform Requirements
+
+- A supported version of Morpheus Enterprise is installed and operational
+- Administrative access to Morpheus for HPE BMaaS installation and configuration
+- Sufficient storage configured in Morpheus for OS images
+
+## Operating System Images
+
+OS ISO images available in the Morpheus Virtual Image Library
+
+## SSH Keys for Remote Login tothe Instance
+
+- Configure the SSH key access from an authorized host, for details see HPE Morpheus Enterprise documentation.
+- You can configure the SSH in HPE Morpheus under Infrastructure > Trust > Key Pairs
+
+## User Settings for OS (Linux and Windows)
+
+When provisioning a Linux- or Windows-based resource and opting to create users during the provisioning, the credentials entered in this section are used to create user during. For configuration, navigate to User Settings > Linux or User Settings > Windows Settings.
+
+## Proxy Configuration
+
+To configure proxy, navigate to Infrastructure > Network > Proxies.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json b/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
new file mode 100644
index 0000000..02c247a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+  "title": "Trust",
+  "ordinal": 524,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md b/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
new file mode 100644
index 0000000..214df0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
@@ -0,0 +1,5 @@
+# Trust
+
+**Subtopics**  
+
+- **[CyberArk Conjur](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json b/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
new file mode 100644
index 0000000..2918ee8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+  "title": "Managing Instances",
+  "ordinal": 86,
+  "parent_title": "Instances",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md b/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
new file mode 100644
index 0000000..3d8d83b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
@@ -0,0 +1,92 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Metadata, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual VM’s or Containers and cannot be undone, unless a Delayed Removal policy has been applied prior to the Deletion. To delete Instances without deleting associated VM’s, delete the Instances VM record(s) from the Infrastructure section with “Remove Infrastructure” deselected and select “Remove Associated Instances” in the VM delete modal options. This will delete the records in HPE Morpheus Enterprise but leave the infrastructure in place.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+## Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Service
+:   Stops, Starts or Restarts the service associated with the Instance Type.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Lock/Unlock Instance
+:   A locked instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, cpu, ram, networks and storage controller changes. Available options depend on the instance type and service plan configuration. Some resize actions require an instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. Only available for Instances with backups enabled.
+
+Run Workflow
+:   Presents workflow options and then immediately runs selected Workflow on the Instance. Workflows can be created in the Library > Automationsection.
+
+Run Script
+:   Presents Script options and immediately executes selected Script on the Instance. Scripts can be created in the Library section.
+
+Apply Template
+:   Presents Template options and immediately applies selected Template to the Instance. Templates can be created in the Library section.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on instance configuration and type.
+
+Eject Disk
+:   Ejects attached disk/iso.
+
+Add Slave
+:   Adds a database slave in the Instance.
+
+Change Master
+:   Changes the database Master node in an Instance.
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding HPE Morpheus Enterprise Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
+
+## Performing Instance Actions
+
+### Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. Click the Instance from the list of instances you wish to perform an action on.
+3. Click the Actions drop down button and select an Action.
+
+## Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab button on the bottom of Instance Detail pages. Instances with associated VMware VM’s will bi-directionally sync HPE Morpheus Enterprise Instance Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json b/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
new file mode 100644
index 0000000..fd7ad3e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+  "title": "PowerDNS",
+  "ordinal": 485,
+  "parent_title": "DNS",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html",
+  "topic_cluster": {
+    "clustering_title": "PowerDNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md b/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
new file mode 100644
index 0000000..44673f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
@@ -0,0 +1,78 @@
+# PowerDNS
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with PowerDNS to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in PowerDNS Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add PowerDNS Integration
+
+### About this task
+
+PowerDNS can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   PowerDNS
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   API HOST
+   :   URL of PowerDNS API. Example: `http://10.30.20.10:8081`
+
+   Token
+   :   PowerDNS API Token
+
+   Version
+   :   PowerDNS API Version
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, PowerDNS Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring PowerDNS with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json b/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
new file mode 100644
index 0000000..c8a56ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+  "title": "Google Cloud Platform (GCP)",
+  "ordinal": 394,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-36BA3E37-26D3-488F-85C2-942C45119F02.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Platform (GCP)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md b/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
new file mode 100644
index 0000000..956b472
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
@@ -0,0 +1,297 @@
+# Google Cloud Platform (GCP)
+
+## Integration Features
+
+- Provisioning Virtual Machines
+- Network tagging
+- Private and Local Images
+- Google VM Snapshots
+- Brownfield Inventory
+- Costing
+- Right-sizing
+- Shared Network Support
+
+## Requirements for Integration with HPE Morpheus Enterprise
+
+To integrate HPE Morpheus Enterprise with Google Cloud Platform, you will need the following. APIs are enabled in “APIs & Services” and must be enabled for all projects or the selected project (depending on your GCP Cloud integration settings). The next section contains more detailed steps for enabling API in the GCP web console.
+
+- The Compute Engine API enabled
+- The Cloud Resource Manager API enabled
+- The Cloud Billing API
+- The Identity and Access Management (IAM) API enabled
+- The BigQuery API enabled
+- The BigQuery Data Transfer API enabled
+- The Kubernetes Engine API enabled (required to provision GKE clusters)
+- Credentials for an IAM service account with Owner or Compute Admin role permissions
+- The private key and client email for the service account
+
+This integration guide goes through the process of configuring your account and obtaining the information necessary to integrate with HPE Morpheus Enterprise. Continue to the next section for a detailed look at enabling the APIs mentioned above.
+
+## Enabling the Required APIs
+
+In order to take full advantage of the HPE Morpheus Enterprise integration with Google Cloud, a number of APIs must be enabled within the GCP web console. It’s recommended that you enable all of the APIs listed in the preceding section regardless of the HPE Morpheus Enterprise feature set you intend to use. This will ensure you do not run into problems down the road stemming from a lack of access which may take time to diagnose.
+
+Log into the Google Cloud web console and navigate to the APIs and Services page. You may find this in the Quick access area of the welcome page or you can search for it as shown in the screenshot below.
+
+![../../../_images/apis.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C41DCEFF-896A-485D-B7F1-1097EF7E1E18-high.png)
+
+From the APIs and Services page, a list of enabled APIs and some details about your usage are shown. To enable new APIs, click + ENABLE APIS & SERVICES near the top of the window. Now on the API library page, search for the API you wish to enable. Here I’ve searched for the Kubernetes Engine API.
+
+![../../../_images/apisearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-11AC3447-F2D7-4C1D-B2FD-AF477146AB37-high.png)
+
+From the search results, click on the API you wish to enable to view its detail page. Click ENABLE. Once successfully enabled, the button will change to a MANAGE button. It may take a few moments for the API to be fully enabled. You may also be prompted to enable the Cloud Billing API or create an association with a Billing Account when enabling APIs. Go ahead and do so if prompted.
+
+![../../../_images/apienable.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-88E68260-6F46-43BB-8525-EF1D814408B5-high.png)
+
+Repeat this process until all required APIs (listed in the previous section) are enabled.
+
+## Creating a Service Account
+
+### Procedure
+
+1. From anywhere in the GCP web console, search for “service accounts” in the global search bar at the top of the window
+2. Click on the Service Accounts page (within the IAM & Admin stack)
+3. A list of existing service accounts within the selected Project is shown (if any)
+4. To create a new one, click + CREATE SERVICE ACCOUNT 
+
+   ![../../../_images/3create_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A3CD48CE-C19C-41EF-A6C2-286B2320673B-high.png)
+5. Enter at least a name for your new service and click CREATE AND CONTINUE 
+
+   ![../../../_images/4config_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5E5FB1A4-AE19-4582-BF8A-CBDF18100628-high.png)
+6. After creating the service account, you’ll be prompted to set a role for the account. In order to fully integrate with HPE Morpheus Enterprise, you must use an account in the Owner role or the Compute Admin role
+7. Click CONTINUE 
+
+   ![../../../_images/5service_acct_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-172734F2-7D01-4F27-83CA-40CB948F05D2-high.png)
+8. Following creation of the service account, you’ll be taken back to the list of existing service accounts
+
+## Generating Keys and Integrating with HPE Morpheus Enterprise
+
+### Procedure
+
+1. From the list of service accounts, click the ellipsis button (…) to the right of a selected account
+2. Click “Manage Keys” 
+
+   ![../../../_images/6create_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-94F3D47B-1CE6-4C7C-A572-745199DE161D-high.png)
+3. On the Keys page, click “Add Key” and then “Create New Key”
+4. Select JSON format and click CREATE
+5. A JSON-formatted document will be downloaded, this document contains the Project ID, private key, and client email values needed to complete the integration process in the next step
+
+## Add a GCP Cloud
+
+### About this task
+
+NOTE
+
+The JSON-formatted document downloaded when creating a key for your service account contains all of the required values for completing the integration. Consult the above section on generating keys if needed.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select + CREATE CLOUD, select Google Cloud, and then click NEXT.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   PRIVATE KEY
+   :   The service account private key. Paste in the entire value between (but not including) the quotation marks in your downloaded JSON document, formatted like the following example: `-----BEGIN PRIVATE KEY-----(your_key)-----END PRIVATE KEY-----`
+
+   CLIENT EMAIL
+   :   The service account client email, ex: morpheus@morpheus.iam.gserviceaccount.com
+
+   PROJECT ID
+   :   Projects will auto-populate upon successful entry of the private key and client email. You can opt to scope the GCP integration to a single Project or select “All” to instead select the Project from the Resource Pool dropdown at provision time
+
+   REGION
+   :   Regions will auto-populate upon successful entry of the private key and client email. Select the appropriate region for this Cloud, if applicable. You can also opt to scope the GCP integration to all regions to allow users to select from any region at provision time
+
+   INVENTORY EXISTING INSTANCES
+   :   If checked, existing GCP resources will be inventoried and appear as unmanaged virtual machines in HPE Morpheus Enterprise.
+
+   If advanced options are not needed, click NEXT to advance to the Group selection page. Otherwise, continue on with this guide and review advanced or provisioning options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After reviewing all options, click NEXT to advance to the Group selection page. Following Group selection, click COMPLETE to finish the integration process. If you’ve opted to inventory existing Instances, they will be viewable in HPE Morpheus Enterprise shortly. At this point, you are ready to provision new resources in Google Cloud Platform as needed!
+
+### Results
+
+IMPORTANT
+
+If you experience difficulties adding a GCP Cloud, review the above guide and ensure you’ve met all requirements for completing the integration. For example, if the Compute Engine API is not enabled, HPE Morpheus Enterprise will not accept credentials entered on the Create Cloud modal. If you repeatedly run into problems completing the integration process, review the above guide in its entirely and double check that each step is completed and your account meets all configuration requirements.
+
+## Create a GCP Project
+
+### About this task
+
+On initial integration, HPE Morpheus Enterprise will sync Projects and allow you to scope the integration to a specific Project or to scope the integration to all Projects. As time goes on, additional Projects are continually synced and can be managed from within the Resources tab on the Cloud detail page (Infrastructure > Clouds > Selected GCP Cloud). Within the Resources tab, users can edit some Project settings as well as delete Projects if needed.
+
+To create a new GCP Project:
+
+### Procedure
+
+1. Click + ADD RESOURCE POOL
+2. Enter a name value for the new Project
+3. Mark the “DEFAULT” box if you’d prefer newly provisioned Instances default to the new Project
+4. Enter a Project ID and ensure it meets the listed validation requirements
+5. Set a Parent value if the new Project should exist underneath a parent organization
+6. Finally, select a billing account
+7. Click SAVE CHANGES
+
+### Results
+
+After a few minutes, the new Project will be ready on the GCP side and HPE Morpheus Enterprise will be ready to provision new resources into it.
+
+## Enabling Live Costing for GCP
+
+GCP costing is done at the Billing Account level. Each Billing Account can be linked to one or more GCP Projects. All projects which are linked to the Billing Account will have their costing data available to HPE Morpheus Enterprise but if the GCP Cloud has been scoped to only one Project, HPE Morpheus Enterprise will ingest costing data only for that Project. Users can view the Billing Account linked to a particular project by clicking on the hamburger menu (main menu button in the far upper-left of the console window) and selecting billing. A pop-up window will give users the option to navigate to the Billing Account which is linked to the currently-selected Project.
+
+![../../../_images/costing1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9F511176-D2F9-4455-A1EB-7E9EA11219B3-high.png)
+
+Within the Billing Account, Standard Usage Cost must be enabled for HPE Morpheus Enterprise to access costing data. From the page for the appropriate Billing Account, click on Billing Export and then click “Edit Settings” under the “Standard usage cost heading”. Specify a project and create a dataset or specify an existing one. In doing this, you’re specifying a location for the dataset which will be for the entire billing account and not just for the Project the dataset resides in.
+
+![../../../_images/costing2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A3C3C708-1787-4F98-AA95-99BBBDDCEFAC-high.png)
+
+With configuration in the GCP console completed, we can now enable cost onboarding from the HPE Morpheus Enterprise side. Add or edit an existing GCP Cloud (Infrastructure > Clouds). Within the Advanced Options section, note the COSTING PROJECT and COSTING DATASET fields. When selecting a Project, associated datasets (if any) will automatically be loaded into the dropdown in the next field for selection. Additionally, the COSTING field should be set to “Sync Costing” rather than “Off”. Recall from the previous paragraph that this is merely pointing to the Project that houses the appropriate dataset. If your GCP Cloud in HPE Morpheus Enterprise is configured for all Projects, all costing data will be consumed for the Projects linked to the associated Billing Account (assuming those Projects have billing enabled). If the GCP Cloud in HPE Morpheus Enterprise is scoped to just one Project, only billing data for that Project will be onboarded. For this reason, the selected Costing Project can be (but is not necessarily) the Project to which the HPE Morpheus Enterprise Cloud is scoped.
+
+![../../../_images/costing3.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-15DC0856-A5ED-4CE5-8AFF-7C30A062DA86-high.png)
+
+## Windows Images
+
+HPE Morpheus Enterprise can add custom metatdata that will be injected into the unattend conf by GCP during provisioning. This is required for customizations including setting the Windows Administrator password during provisioning. GCP Windows Images must be syspreped using the `GCESysprep` command prior to image creation, and must have platform/os set on the Virtul Image record in HPE Morpheus Enterprise after image sync for successful customization and Agent Installation.
+
+### GCP Windows Requirements
+
+- GCP Windows Images must be syspreped using the `GCESysprep` command prior to Image creation in GCP. Refer to [Googles “creating-windows-os-image” doc](https://cloud.google.com/compute/docs/instances/windows/creating-windows-os-image).
+- Once the Image is synced into Morpheus, the Platform (Windows, Windows 2016 etc) must be set on the HPE Morpheus Enterprise Virtual Image record, otherwise linux is assumed and the metadata will not be generated correctly.
+- The Global Windows “Administrator” password must be set in HPE Morpheus Enterprise under `/admin/provisioning/settings` > Windows Settings > AdministratorPassword, or Administrator and password defined on the HPE Morpheus Enterprise Virtual Image record.
+- Be aware the unattend configuration during startup after sysprep delays causes a reboot and a prolonged finalization process during provisioning, and console/rdp may not be available during this time as windows is configuring.
+
+NOTE
+
+Some Google provided Windows Images have slow startups that cause the Morpheus Agent service to not start within the default 30 second service startup timeframe, including after initial reboot after sysprep/unattend configuration. This can be adjusted by running `New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\" -Name "ServicesPipeTimeout" -PropertyType DWORD -Value 180000` in powershell on the Windows Image.
+
+IMPORTANT
+
+Failure to use a GCP Windows Image that has not been sysprepped using `GCESysprep` will cause Agent Installation, Automation, and Console issues as HPE Morpheus Enterprise will not be able to set user credentials and authenticate.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json b/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
new file mode 100644
index 0000000..5828d44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+  "title": "Adding hosts",
+  "ordinal": 185,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md b/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
new file mode 100644
index 0000000..68ac0eb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
@@ -0,0 +1,13 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the HVM Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once HPE Morpheus Enterprise has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
+
+![../../_images/addHost.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-23D2DBDA-8840-4B60-A4B2-04DAD55E279E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json b/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
new file mode 100644
index 0000000..1aeaeed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+  "title": "Attaching Logs to Case",
+  "ordinal": 346,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html",
+  "topic_cluster": {
+    "clustering_title": "Attaching Logs to Case",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md b/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
new file mode 100644
index 0000000..05d8d58
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
@@ -0,0 +1,11 @@
+# Attaching Logs to Case
+
+When submitting a case it is critical to attach the relevant logs. The logs can be found at `/var/log/morpheus/morpheus-ui/current`. Logs can be attached to the case at anytime.
+
+When submitting logs please reproduce the error right before capturing and sending the log file. This will ensure the activity that took place and resulted in an error is contained in the logs.
+
+Log rotation takes the current file each night or after it’s a certain size and compresses them. The `*.s` files in the current directory are rotated and zipped logs that can be sent as is.
+
+The logs can also be captured from the Morpheus UI. Under Administration > Health > Morpheus Logs. Please copy relevant logs and add to case as an attachment.
+
+![../_images/Morpheus-Health-Logs.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json b/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
new file mode 100644
index 0000000..0084411
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+  "title": "Role Permissions",
+  "ordinal": 106,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md b/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
new file mode 100644
index 0000000..846b505
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
@@ -0,0 +1,5 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete tasks.
+
+Tasks Types that can execute locally against the HPE Morpheus Enterprise Appliance have an additional Role Permission: `Tasks - Script Engines`. Script Engine Task Types will be hidden for users without `Tasks - Script Engines` role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..68d1662
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 234,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..11bccce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1,112 @@
+# Servers
+
+## Add Storage Server
+
+### Adding 3Par Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+#### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC Isilon Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json b/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
new file mode 100644
index 0000000..2342cab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+  "title": "Creating Custom Cluster Layouts",
+  "ordinal": 145,
+  "parent_title": "Cluster Layouts",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Custom Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md b/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
new file mode 100644
index 0000000..f7e8cd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
@@ -0,0 +1,207 @@
+# Creating Custom Cluster Layouts
+
+Custer Layouts can be built for an infinite number of use cases and targeting a wide range of configurations or provisioning technologies. However, it still may help to see an example Cluster Layout created. In this section, we’ll create an example Cluster Layout which provisions a Kubernetes Cluster to a VMware vCenter Cloud containing a master node and three worker nodes. We’ll build out two Node Types to embed in the Cluster, one master and one worker. Within the Node Types, we will embed Script Templates needed to configure the nodes as they are provisioned and allow the workers to join the cluster. Script Templates can be configured to execute at various phases of the lifecycle of the node, similar to a Provisioning Workflow, so HPE Morpheus Enterprise can orchestrate the whole process.
+
+## Creating Script Templates
+
+We’ll first start by creating the necessary Script Templates. In this example, I’ll use a generic prep script that both the master and worker nodes will utilize and then I’ll create three additional scripts (two for the master node and one for the worker nodes) to accomplish various Kubernetes cluster setup tasks (`kubeadm init`, creating Role Bindings, joining workers to the cluster, etc.). I’ll briefly describe each here and step through the process of creating the Script Template objects in HPE Morpheus Enterprise.
+
+To begin a new Script Template, navigate to Library > Templates > Script Templates and click + ADD. All of the scripts used in this example will be “Bash” type, run as user “root” and with SUDO marked.
+
+The first script to add will be a prep script that both the master and worker nodes will use. This script turns swap off, installs `containerd`, runs updates, sets network config, and installs `kubelet`, `kubeadm`, and `kubectl`. Set this script to run in the PreProvision phase. The complete script, named “k8sprep” in my example can be viewed below:
+
+### k8sprep Script Template
+
+```
+```
+function wait_for_dpkg() {  
+  FRONT_END_LOCK_FILE=/var/lib/dpkg/lock-frontend  
+  DPKG_LOCK_FILE=/var/lib/apt/lists/lock  
+  echo "checking for dpkq lock existence..."  
+  if [ -e "$DPKG_LOCK_FILE" ]; then  
+    while fuser $DPKG_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $DPKG_LOCK_FILE..."  
+      sleep 1  
+    done  
+  fi  
+  echo "checking for dpkq lock-frontend existence..."  
+  if [ -e "$FRONT_END_LOCK_FILE" ]; then  
+    while fuser $FRONT_END_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $FRONT_END_LOCK_FILE..."  
+      sleep 1  
+    done  
+    echo "force removing lock $FRONT_END_LOCK_FILE"  
+    sudo rm $FRONT_END_LOCK_FILE  
+    sleep 5  
+  fi  
+}  
+  # Swap must be turned off see https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo swapoff -a ; sudo sed -i '/ swap / s/^/#/' /etc/fstab  
+  # Install containerd packages from Debian sse: https://docs.docker.com/engine/install/ubuntu/  
+wait_for_dpkg  
+sudo apt-get update  
+sudo apt-get install ca-certificates curl gnupg lsb-release -y  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpgsudo  
+echo   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \  
+$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null  
+sudo apt-get update  
+  # the Docker documentation advises to install the whole Docker runtime environment but containerd.io is sufficient  
+sudo apt-get install containerd.io -y  
+  # Prepare the necessary network config see: https://kubernetes.io/docs/setup/production-environment/container-runtimes/  
+sudo cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf  
+overlay  
+br_netfilter  
+EOF  
+sudo modprobe overlay  
+sudo modprobe br_netfilter  
+sudo cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf  
+net.bridge.bridge-nf-call-iptables  = 1  
+net.bridge.bridge-nf-call-ip6tables = 1  
+net.ipv4.ip_forward                 = 1  
+EOF  
+  # Apply sysctl params without reboot  
+sudo sysctl --system  
+  # Install kubeadm follwing the K8s documentation: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo apt-get install -y apt-transport-https ca-certificates curl  
+sudo curl -fsSL  https://packages.cloud.google.com/apt/doc/apt-key.gpg|sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/k8s.gpg  
+sudo echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list  
+sudo apt-get update  
+sudo apt-get -y install -y kubelet=1.26.1-00 kubeadm=1.26.1-00 kubectl=1.26.1-00  
+sudo apt-mark hold kubelet kubeadm kubectl  
+  # see https://github.com/etcd-io/etcd/issues/13670  
+cat << EOF | sudo tee /etc/containerd/config.toml  
+version = 2  
+  [plugins]  
+  [plugins."io.containerd.grpc.v1.cri"]  
+   [plugins."io.containerd.grpc.v1.cri".containerd]  
+      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]  
+        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]  
+          runtime_type = "io.containerd.runc.v2"  
+          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]  
+            SystemdCgroup = true  
+EOF  
+sudo systemctl restart containerd
+```
+```
+
+Next we’ll add a script called “kubeadm-init” in this example which will create and configure some working directories, set the `kubeadm` config yaml, and run `kubeadm init`. Set this script to run in the PreProvision phase as well. The complete script can be viewed below:
+
+### kubeadm-init Script Template
+
+```
+```
+mkdir -p <%=morpheus.morpheusHome%>/kube  
+mkdir -p <%=morpheus.morpheusHome%>/kube/working  
+mkdir -p <%=morpheus.morpheusHome%>/.kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube/working  
+cat <<EOF | sudo tee <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+# kubeadm-config.yaml  
+kind: ClusterConfiguration  
+apiVersion: kubeadm.k8s.io/v1beta3  
+kubernetesVersion: v1.26.1  
+networking:  
+  serviceSubnet: "10.96.0.0/16"  
+  podSubnet: "10.244.0.0/24"  
+  dnsDomain: "cluster.local"  
+apiServer:  
+  extraArgs:  
+    authorization-mode: "Node,RBAC"  
+clusterName: "example-cluster"  
+---  
+kind: KubeletConfiguration  
+apiVersion: kubelet.config.k8s.io/v1beta1  
+cgroupDriver: systemd  
+EOF  
+sudo kubeadm init --config <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+sudo cp -i /etc/kubernetes/admin.conf <%=morpheus.morpheusHome%>/.kube/config &&  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/.kube/config
+```
+```
+
+Lastly, we’ll add a setup script for the Kubernetes master node called “k8s-master-setup” for this example. This script creates the service account and role bindings. Set this script to run in the PostProvision phase and view the complete script below:
+
+### k8s-master-setup Script Template
+
+```
+```
+#create a service account  
+cd <%=morpheus.morpheusHome%>  
+#kubectl -n kube-system create sa morpheus  
+kubectl create sa morpheus  
+cat <<EOF | tee <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+apiVersion: v1  
+kind: Secret  
+metadata:  
+  name: morpheus-token  
+  annotations:  
+    kubernetes.io/service-account.name: morpheus  
+type: kubernetes.io/service-account-token  
+EOF  
+kubectl create clusterrolebinding serviceaccounts-cluster-admin --clusterrole=cluster-admin --group=system:serviceaccounts  
+kubectl create -f <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
+```
+```
+
+The three scripts we’ve just created will prepare the master node for our cluster. We now need an additional script that will prepare the worker nodes and join them to the cluster. The worker nodes will also use the “k8s-prep” script we added in the very first step which you’ll see in the next step when we create the node types.
+
+Add a fourth script which I’ve called “k8s-join” for this example. This script takes advantage of a special `joinCommand` variable as you’ll see when you view the full script. If you want to see exactly what this does later, you can create a new Bash script Task that echoes out that variable and run it against an existing Kubernetes worker node VM (`echo "<%=morpheus.kubernetes.joinCommand%>"`). Set this script to run in the PostProvision phase and view the full script below:
+
+### k8s-join Script Template
+
+```
+```
+sudo <%=morpheus.kubernetes.joinCommand%>
+```
+```
+
+This completes the needed Script Templates which we will set on two new Node Types in the next step. Continue on to the next section.
+
+## Creating Node Types
+
+With the Script Templates created we now need to make two new Node Types, one for the master node and one for the worker nodes. In this example case, we don’t need to add a new Virtual Image because we can use one of the preinstalled system images for Ubuntu on VMware vCenter which will work fine. Node Types are created in Library > Blueprints > Node Types. Once there, click + ADD. Within the modal for the new Node Type, configure the following:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the master node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep”, “kubeadm-init” and “k8s-master-setup” Script Templates (you may have called them something different)
+
+Finally, click SAVE CHANGES.
+
+Repeat the process to create a second Node Type. The second time around, use the following configurations:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the worker node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep” and “k8s-join” Script Templates (you may have called them something different)
+
+Once done, click SAVE CHANGES to save the second Node Type. With the pieces in place, we are now ready to create the Cluster Layout object itself. Continue on to the next section.
+
+## Creating a Cluster Layout
+
+At this point we can create the Cluster Layout object in HPE Morpheus Enterprise and attach the Node Types we’ve just created (which themselves have our Script Templates applied). Cluster Layouts are created in Library > Blueprints > Cluster Layouts. Click + ADD and configure the following:
+
+- **NAME:** Provide a name for the Cluster Layout, can be anything to denote this is a Kubernetes cluster
+- **VERSION:** The version number you wish to apply to this Cluster Layout which is useful if you later iterate on this Cluster Layout
+- **CLUSTER TYPE:** Kubernetes Cluster
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4096 MB
+- **INPUTS:** Use the typeahead field to add configured Inputs to the Cluster Layout
+- **MASTER NODES:** Use the typeahead field to find the Kubernetes master Node Type we just created
+- **WORKER NODES:** Use the typeahead field to find the Kubernetes worker Node Type we just created. Set the “Count” value to three (3) since we wish to have three worker nodes in this cluster
+- **CLUSTER PACKAGES:** Use the typeahead field to add configued Cluster Packages to the Cluster Layout. Cluster Packages are created in the [Templates section](https://docs.morpheusdata.com/en/latest/library/templates/templates.html)
+- **SPEC TEMPLATES:** Use the typeahead field to add Spec Templates to the Cluster Layout
+
+Click SAVE CHANGES to save the Cluster Layout.
+
+## Testing and Wrap-Up
+
+At this point we are finished and we have a viable Kubernetes cluster that we can deploy with just one click. To add a new managed cluster to this HPE Morpheus Enterprise environment, navigate to Infrastructure > Clusters. To provision a cluster from the layout we just created, click + ADD CLUSTER and select “Kubernetes Cluster” from the dropdown menu. Make the appropriate selections to target the new cluster to an existing VMware vCenter Cloud and complete the wizard. Once complete, the new cluster will be visible on your clusters list page and from there you can drill into the detail page to view relevant details about the cluster including monitoring metrics, current workloads, and more.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json b/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
new file mode 100644
index 0000000..05c1b07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+  "title": "Dell ECS",
+  "ordinal": 520,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html",
+  "topic_cluster": {
+    "clustering_title": "Dell ECS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md b/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
new file mode 100644
index 0000000..8378aa5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
@@ -0,0 +1,246 @@
+# Dell ECS
+
+## Overview
+
+HPE Morpheus Enterprise integrates with DELL EMC ECS via the ECS api. This allows Morpheus to talk directly to the ECS services.
+
+When you add a ECS Server, HPE Morpheus Enterprise will sync in the following.
+
+- Storage Groups
+- Buckets
+- File shares
+
+Users will be able to create the following items within ECS without direct access to the ECS console.
+
+- Buckets
+- File shares
+
+## Storage Servers
+
+The first step in the Dell EMC ECS integration is to add a Dell EMC ECS Storage Server. Once added, Buckets, Files Shares and Storage Groups will be synced in and can be access and managed in HPE Morpheus Enterprise.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Buckets
+
+- **Buckets** will be listed in Infrastructure - Storage - Buckets
+
+  - Buckets can be created and deleted with Infrastructure - Storage Role Permissions
+  - Buckets can be browsed with Infrastructure: Storage Browser Role permissions
+  - File and folders can be uploaded, downloaded and deleted with Full Infrastructure: Storage Browser Role permissions.
+
+## Adding Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell ECS Bucket.
+
+To Add a Dell ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell ECS bucket.
+
+   USER
+   :   Your Dell EMC ECS S3 user account
+
+   SECRET KEY
+   :   Your Dell EMC ECS S3 Secret
+       :   Example: jW+pFyAPtSS5FuEqKwt44xlpM/2
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Add Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json b/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
new file mode 100644
index 0000000..4b6e9f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+  "title": "Hosts",
+  "ordinal": 210,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md b/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
new file mode 100644
index 0000000..9c729d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
@@ -0,0 +1,12 @@
+# Hosts
+
+![../../_images/infra_compute_header_hosts_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BC2FD43F-BD46-40FD-BA88-FA7789B6DE81-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Hosts in HPE Morpheus Enterprise are Hypervisors and Container hosts that VMs and Containers are hosted on, such as ESXi Hosts and Kubernetes Master and Workers. These hosts are populated from integrated clouds, hosts and clusters provisioned from Morpheus, or manually added hosts.
+
+Provisioning new hosts takes place in the Infrastructure > Clusters section of HPE Morpheus Enterprise. For example, provisioning a new Docker cluster in that section will begin the process of creating a HPE Morpheus Enterprise-managed Docker cluster with one host (by default). Additional hosts and custom layouts can also be created. See the [Clusters section](https://docs.morpheusdata.com/en/latest/infrastructure/clusters/clusters.html) of HPE Morpheus Enterprise docs for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..8fd1178
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 295,
+  "parent_title": "Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..ff7433f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,12 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[User Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html)**
+- **[Tenant Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html)**
+- **[Cloud Access Levels](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json b/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
new file mode 100644
index 0000000..d2aa6ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+  "title": "Import and Export",
+  "ordinal": 98,
+  "parent_title": "Code",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html",
+  "topic_cluster": {
+    "clustering_title": "Import and Export",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md b/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
new file mode 100644
index 0000000..2cd4d47
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
@@ -0,0 +1,128 @@
+# Import and Export
+
+Onboarded Git repositories can be configured as either import or export targets for a HPE Morpheus Enterprise appliance. This means that many created HPE Morpheus Enterprise constructs, such as Tasks, Library Items, and others, can be backed up to an integrated Git repository as code. This backup can take place on an automatic schedule (syncs every four hours) or can be triggered manually after changes are made. Users can back up all supported constructs within the appliance to a single repository or use Labels to back up only selected items. Exported constructs can also be imported into target appliances. This is useful for sharing items between two HPE Morpheus Enterprise environments, such as from a development appliance to a production appliance.
+
+NOTE
+
+The use of this feature requires an integrated Git repository. Please see our [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for Github or other Git integrations if you’ve not yet integrated your code repositories. While Morpheus can onboard and work with both public and private code repositories, it is strongly recommended that you use private repositories for exporting your Morpheus constructs as code.
+
+Supported Constructs:
+
+- Tasks
+- Workflows
+- Spec Templates
+- Library Items
+- Forms
+
+NOTE
+
+When exporting all supported constructs HPE Morpheus Enterprise will export more than just the above types, however, only the above types are exportable as individual resources. This list may expand in the future as additional constructs become supported by future updates.
+
+## Role Permissions
+
+Access and capabilities for the Import/Export feature set is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Export/Import`
+:   - **None:** Cannot access the edit button on the Code List Page (Provisioning > Code) to set Import/Export settings or see Import/Export actions on the Code Repository Detail Page
+    - **Full:** Code repositories can be edited to set Import/Export configurations and Import/Export actions can be viewed and used on Code Repository Detail Pages
+
+## Import/Export Settings
+
+Code repositories are set to allow import, export or both from the Code Repositories List Page (Provisioning > Code). Click the edit button (✎) to the right of the selected repository to edit its import/export settings. When editing a code repository for import and export, set the following configurations:
+
+- **ENABLED:** When marked, routine syncs will take place between HPE Morpheus Enterprise and this repository. This includes all file syncs and not just actions related to import and export
+- **IMPORT/EXPORT:** Set “Auto export all” to automatically export once every four hours, “Manual export” to enable this repository for manual exports on demand, “Manual import” to enable this repository for manual imports on demand, “Import/Export” to enable both manual imports and exports on demand
+- **PATH:** The path within the repository where HPE Morpheus Enterprise should import from or export to
+- **EXPORT LABEL FILTER:** Enter a Label and HPE Morpheus Enterprise will export or import only constructs which include the Label into the repository. This must be a single Label, it cannot be a list of multiple Labels
+
+Once you’ve configured the code repository, click SAVE CHANGES
+
+NOTE
+
+Code repositories must have at least one file in them in order to export HPE Morpheus Enterprise constructs as code. This can be as simple as a README file, they just cannot be empty.
+
+![../../_images/editRepo.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1897DAD3-23E6-4D44-8331-93C40D4FD9FA-high.png)
+
+## Exporting
+
+After a repository is configured to allow export (see previous section), it may perform periodic automatic refreshes or the user may need to refresh the repository on demand (depending on settings). To manually initiate an export, drill into the Repository Detail page, click ACTIONS, and click “Export All Resources”.
+
+![../../_images/exportAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-01557155-5F51-4E18-9423-80740E675D88-high.png)
+
+Any new or updated constructs will be refreshed within the repository at the path your repository is configured to export into. Bear in mind that, even if you’ve configured HPE Morpheus Enterprise to export only constructs categorized with a specific Label, any required dependencies would also be exported. For example, if you’ve labeled a Workflow to be exported, HPE Morpheus Enterprise will also export the dependency Tasks so the Workflow will be functional. A similar behavior applies for exported Library Items which may have a number of dependencies. In the screenshot below, files can be seen populating the targeted Github repository.
+
+![../../_images/githubView.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-200CE557-64D2-4090-9C52-EE941972E411-high.png)
+
+HPE Morpheus Enterprise items are exported as scribe files. These are HCL-formatted representations of the construct as code. They include static attributes representative of the attributes set on the construct itself or they may use UUIDs to refer to other constructs or integrations. It shouldn’t be necessary to view or edit them unless you’re curious.
+
+![../../_images/viewScribe.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5C55D002-8AF1-4F8D-9EAE-D6839820B80F-high.png)
+
+## Importing
+
+After HPE Morpheus Enterprise constructs have been exported as code, they can be pulled down into other appliances which have the same repositories integrated. Items can be imported ad-hoc from the file browser within a Code Repository Detail page. Click on the gear (⚙) dropdown to the right of any scribe file that may exist in your repository. For example, in the screenshot below, an individual Task is being imported into the destination appliance.
+
+![../../_images/importFile.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E526F230-60CB-4FB1-ACCE-EA127DA5E7D2-high.png)
+
+In addition to importing one-off items, code repositories may also be configured for import so that many items can be imported at once. The same configurations can be made for import as export, including a specific path within the repository to import from and whether only specific Label groups should be targeted. Triggering a larger scale import for a whole repository is done from the Code Repository Detail Page. Click the ACTIONS button and then click “Import All Resources”.
+
+![../../_images/importAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-66220000-CC18-46E6-9B31-28E732091886-high.png)
+
+Once the import has been initiated, HPE Morpheus Enterprise will check to see if a new item will be created, if an existing item would be updated, if no action could be taken due to a conflict, or if no changes would result. This information is presented to the user who may then decide if the import action should go ahead.
+
+![../../_images/checkImport.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7E6E76A0-2B8D-49C7-ADBE-3D515134ED07-high.png)
+
+IMPORTANT
+
+Care has been taken with HPE Morpheus Enterprise Import/Export to ensure that existing work cannot be wiped out by an import action. For example, if a Task with a name identical to a pre-existing Task would try to be imported, HPE Morpheus Enterprise will require the naming conflict be resolved before the import can take place. In fact, HPE Morpheus Enterprise Import can only create new items or overwrite items created by import. It cannot overwrite anything user-created or anything pre-seeded with the system at install. Additionally, import cannot be scheduled automatically. Users must initiate all imports.
+
+IMPORTANT
+
+Importing resources which rely on existing integrations or sensitive values will require some additional configuration on the destination appliance. For example, importing a Task which references code in a separate repository which is not integrated on the target appliance will be imported with reference to the missing integration. This integration would need to be added before the Task could be used. Another example scenario would be a Task which references a secret value held in HPE Morpheus Enterprise Cypher. Once again, the Task would be imported and the required Cypher references would need to be made within the destination appliance before the Task could be used.
+
+## Checking Imported Items Prior to Use
+
+As mentioned in the previous section, not every imported item will immediately be available for use. This is primarily due to the target appliance lacking an integration (for example, an Ansible Tower integration required for an imported Task) or a securely stored secret string (for example, a Task that calls a secret string stored in HPE Morpheus Enterprise Cypher). HPE Morpheus Enterprise will still import these resources but this section discusses some manual changes that may have to be made to imported items in order for them to be usable. HPE Morpheus Enterprise will attempt to export all dependent resources (for example, the needed Tasks if a Workflow is exported) but imported items should still be checked and manually supplemented under certain conditions outlined below.
+
+When exporting, remember that HPE Morpheus Enterprise cannot export to a completely empty repository. Any file (such as a README) needs to exist first. Items deleted from HPE Morpheus Enterprise but previously exported to your repository will continue to exist in the repository. If you wish to delete them from any future imports, you must manually delete them from the repo. Finally, bear in mind that export functionality will only export items which are owned by the Tenant in which the export is created. HPE Morpheus Enterprise does not currently support exporting items which are shared to the tenant from the Master Tenant.
+
+### Protected Fields and User Credentials
+
+Protected information and secret values are not exported. When importing any resources which rely on protected information, the user will need to manually update the resource on the target appliance. Examples include anything authenticated using a stored credential set (from the Infrastructure > Trust > Credentials section), anything with a password field (such as HTTP Tasks or REST-based Option Lists accessing password-protected information), Chef Task Data Bag Keys, and more. Anything configured with a password or other protected field will need to be edited on the importing appliance and updated to have the protected information needed to function.
+
+### Integrations
+
+When an imported Task requires an integration that does not exist on the appliance, an integration will be created with the same name. The integration credentials will not be established, nor will any other configuration fields outside of the name. Users will need to update the integration configuration to make it functional in order for the imported Task to function.
+
+### SSH Keys
+
+SSH Keys are not set on imported resources, such as Tasks configured to be executed on a remote host. Users will need to add a valid key to the importing appliance and update the Task to use that SSH Key.
+
+### Ansible Tower Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on Ansible Tower Tasks.
+
+### vRealize Orchestrator Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on vRO Tasks.
+
+### Option Lists
+
+Option lists need to be edited and saved prior to use in order to load any initial data sets that have been configured on the Option List.
+
+### Forms
+
+Input defaults that are ID-based will require manual correction after import. For example, if you have a Group Input which defaults to `GroupName:A(ID:2)`, when imported it will still be based off an ID value of 2. It’s highly likely that in the importing environment, a different Group will have an ID value of 2. A manual change to the correct ID value is required in the destination environment. Bear in mind that if you re-import a Form, you will also undo any manual changes you’ve made in the importing environment. Thus, if you update all defaults after importing, and then import once again, these manual default changes will be wiped out.
+
+Additionally, when Forms are using existing Inputs, those Inputs will be exported and imported for use in the destination environment. On import, HPE Morpheus Enterprise will add the needed Inputs unless the destination environment already has an Input with the same CODE value. This could give the appearance of creating duplicate Inputs if the destination environment happens to have an Input with the same name but a different code value. Users may wish to rename Inputs in the event they end up with more than one having the same name.
+
+### Tasks
+
+The user must ensure the presence of any dependency required by a Task. One example would be any Cypher keys being called by the Task. Add any required Cypher entries with identical keys or add compatible Cypher keys and update the Task configuration to utilize the updated Cypher mountpoints. Cypher is just one example, any other dependency required by the Task must be present. HPE Morpheus Enterprise does not parse the Task configuration to determine which dependencies are or are not present or required.
+
+### Icons and Images
+
+Icons which are set up on imported Instance Types will need to be manually uploaded to the appliance after import. They are not brought over as part of the import/export process.
+
+### Virtual Images
+
+When importing Node Types, the associated Virtual Image is mapped by its “Code” value. It is expected that a Virtual Image with the correct “Code” value already exists on the target appliance. If not, the Node Type will be imported without any Virtual Image attached. The user will then need to edit the Node Type and associate it with a compatible Virtual Image in order to become usable.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json b/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
new file mode 100644
index 0000000..db92902
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+  "title": "HPE Bare Metal (BMaaS)",
+  "ordinal": 395,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Bare Metal (BMaaS)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md b/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
new file mode 100644
index 0000000..1610297
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
@@ -0,0 +1,29 @@
+# HPE Bare Metal (BMaaS)
+
+HPE Bare-Metal-as-a-Service (BMaaS) for Morpheus Enterprise extends Morpheus hybrid cloud management capabilities to HPE ProLiant physical servers. This integration allows the Morpheus platform to discover, provision, and manage these servers as first-class resources. Additionally, HPE BMaaS Cloud integrates HPE ProLiant bare-metal infrastructure into cloud environments to enable cloud-based provisioning and lifecycle management.
+
+HPE BMaaS manages the end-to-end server lifecycle, including hardware discovery, bare-metal provisioning, operating system deployment, monitoring, and metering. The Morpheus interface centrally orchestrates these tasks. This unified approach enables organizations to manage physical infrastructure, virtual machines, and cloud resources using consistent workflows, policies, and governance controls.
+
+HPE BMaaS Cloud provides the following key capabilities:
+
+- **Automated Server Discovery**: Automatically imports and discovers HPE ProLiant servers.
+- **Bare-Metal Provisioning**: Provisions hardware using custom or pre-configured OS images.
+- **Comprehensive OS Deployment**: Deploys Windows and Linux with unattended installations and customizable boot parameters.
+- **Lifecycle Management**: Manages firmware and drivers using the HPE Service Pack for ProLiant (SPP).
+- **Flexible Networking**: Supports both unmanaged and managed network integrations.
+- **Metering and Billing**: Maps discovered hardware to service plans to align metering with billing.
+- **Logical Organization**: Organizes resources into Bare Metal Clouds and Resource Pools to support multi-site environments and scalable infrastructure segmentation.
+
+HPE BMaaS improves operational visibility and server lifecycle control. It offers a scalable, automated approach to manage physical infrastructure across both greenfield (new) and brownfield (existing) environments.
+
+**Subtopics**  
+
+- **[Supported Software Versions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html)**
+- **[Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html)**
+- **[Compute Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html)**
+- **[Network Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html)**
+- **[Storage Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html)**
+- **[Troubleshooting and Diagnostics](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html)**
+- **[Known Limitations and Operational Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..7b18043
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 269,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..9142595
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json b/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
new file mode 100644
index 0000000..3686b79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+  "title": "Reports",
+  "ordinal": 55,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html",
+  "topic_cluster": {
+    "clustering_title": "Reports",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md b/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
new file mode 100644
index 0000000..aaeb497
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
@@ -0,0 +1,87 @@
+# Reports
+
+## Overview
+
+HPE Morpheus Enterprise offers 28 different report types which are designed to slice up costing and usage across Clouds, Tenants, and more. Reports can be run on-demand as needed or can be scheduled to run on certain intervals to be viewed at a later time. The list of available report types can be viewed at Operations > Reports.
+
+![../_images/1reportList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF328552-F0CB-4A16-89DE-DD5E534DDA21-high.png)
+
+## Report Types
+
+### ACCOUNT INVENTORY
+
+- Tenant Inventory Summary
+
+### CLOUD USAGE
+
+- Cloud Usage
+- Cloud Usage App Summary
+- Cloud Usage Instance Type Summary
+- [Tenant Usage](https://docs.morpheusdata.com/en/latest/operations/report_types/tenant_usage.html)
+
+### CLOUD COST
+
+- Amazon Reservation Coverage
+- Amazon Reservation Utilization
+- Amazon Savings Inventory Summary
+- Amazon Savings Plan Coverage
+- Amazon Savings Plan Utilization
+- Application Cost
+- Cloud Cost
+- Group Cost
+- Instance Cost
+- Tenant Cost
+- Time Series Cost
+
+### INFRASTRUCTURE INVENTORY
+
+- Cloud Inventory Summary
+- Container Host Inventory Summary
+- Group Inventory Summary
+- Guidance
+- Hypervisor Inventory Summary
+- Migration Planning
+- Tenant Resource Allocation
+
+### PROVISIONING INVENTORY
+
+- Instance Inventory Summary
+- Software Inventory
+- Software Inventory By Server
+- Tag Compliance
+- Virtual Machine Inventory Summary
+- Workload Summary
+
+By clicking into a report type, users can see any previous runs and active report schedules. New on-demand runs and new schedules of the selected report type can be created, edited, or deleted from here. The next few sections go into creating, editing, scheduling, viewing, and deleting reports in greater detail.
+
+## Create Reports
+
+To create a new report, navigate to the report type list page (Operations > Reports). Click RUN NOW to the right of the specific report type to bring up the wizard to run that particular report. The required and optional fields to run the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/2reportExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-39F2C925-F3CB-4E65-B5A6-B5B515D2A1F6-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Once the report is run, it will be visible in the list of Instance Cost reports and all reports until deleted.
+
+## Schedule Reports
+
+In addition to running on-demand reports, HPE Morpheus Enterprise also allows reports to be scheduled. This allows you to save report configuration and have access to refreshed information on the schedule you need.
+
+The process of scheduling a report is nearly identical to running on on-demand. From the report type list page (Operations > Reports) click SCHEDULE to the right of the report type you wish to schedule. The required and optional fields to schedule the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/3scheduleExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF0ECE3F-331E-4BDF-9CF3-8DA3BAF19EFA-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Additionally, we select the time schedule on which this report should automatically run. Finally, we can opt to add a comma-separated list of email addresses which should receive an emailed link to the report each time the report is run.
+
+NOTE
+
+HPE Morpheus Enterprise includes three schedules by default: Date and Time (run once at the specified time), Daily at Midnight, and Weekly on Sunday at Midnight. Any other listed scheduling periods are user-configured execution schedules (Library > Automation > Execute Scheduling). Create a new execution schedule if none of the existing schedules work for your reporting needs.
+
+## Viewing Results
+
+A list of all report runs is viewable on the Results tab of the report types list page (Operations > Reports). To view the report itself, click on the hyperlinked report filters. Only reports that are ready for viewing will have an active hyperlink on their filters. In addition to report filters, the run date, report type, creating user, and run status are shown. Click on any of these headers to filter the report list by that column in either ascending or descending order. Any report can be deleted by clicking on the trash can icon at the end of its row.
+
+![../_images/4resultsList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CDD94D4F-361B-4237-B8FD-B88CCFCB6118-high.png)
+
+## Viewing Schedules
+
+A list of all scheduled report runs can be viewed in the Scheduled tab of the report types list page (Operations > Reports). The friendly name of the report schedule is displayed along with the report type, last run time, next run time, and success status of the previous run. Schedules can be edited or deleted by clicking on the pencil or trash can icon, respectively. We can also view the most recent run of a given schedule (if it was successful) by clicking on the hyperlinked “last run” value.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json b/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
new file mode 100644
index 0000000..aca3117
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+  "title": "Remote Storage",
+  "ordinal": 438,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md b/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
new file mode 100644
index 0000000..acd2745
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
@@ -0,0 +1,16 @@
+# Remote Storage
+
+Remote storage enables lifecycle management of volumes on supported **HPE Alletra storage arrays** (including **Alletra MP** and **Alletra 9000**, where supported) and allows compute instances to attach to or detach from those volumes. These operations can be performed during instance provisioning or post-provisioning through the reconfigure workflow. The currently supported transport protocol is **Fibre Channel**.
+
+To get started with using remote storage, first, the storage plugin for Alletra needs to be loaded, and a storage server added. This allows the user to specify the URL where the management interface of the storage array is available, along with the user credentials to manage the storage array.
+
+There is also a concept of a datastore, which is used to represent a container for a set of volumes. A datastore is associated with a storage server and also a resource pool. The resource pool is used to represent a site or a location, which is useful when storage HA is being used with datastores associated with different sites.
+
+## Adding HPE AlletraStorage Integration
+
+You can add the Allertra Storage plugin JAR using the Upload plugin method.
+
+**Subtopics**  
+
+- **[Creating a Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html)**
+- **[Creating a Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json b/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
new file mode 100644
index 0000000..5b45c45
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+  "title": "Price Sets",
+  "ordinal": 289,
+  "parent_title": "Plans",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html",
+  "topic_cluster": {
+    "clustering_title": "Price Sets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md b/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
new file mode 100644
index 0000000..ea3c08b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
@@ -0,0 +1,41 @@
+# Price Sets
+
+Price Sets combine Prices and then attach to Plans. Prices must be created prior to creating Price Sets, but it is recommended to review the Price Set Type options prior to creating Prices.
+
+Price Unit
+:   Select the Price Unit to use for the Price Set.
+
+    - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+    NOTE
+
+    Only Prices configured with matching Price Units can be used in a Price Set. “Month” is equivalent to 30 days by default. For AWS, month is 30.5 days. For Azure, month is 30.4 days.
+
+Type
+:   Price Set types determine which Prices are available to make up the set. This selection will filter the values returned in the Prices field at the bottom of the modal.
+
+    NOTE
+
+    It’s helpful to make note of the Prices options below before creating Price Sets.
+
+    - **Everything:** ‘Everything’ price sets require one or more ‘Everything’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Compute + Storage:** ‘Compute + Storage’ price sets require at least one of each ‘Memory’, CPU’, and ‘Disk Only’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Component:** ‘Component’ price sets require at least one of each ‘Memory’, ‘Cores’, ‘CPU’, and ‘Storage’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Load Balancer:** ‘Load Balancer’ price sets require at least one ‘Load Balancer’ price type and may include ‘Load Balancer Virtual Server’ price types. Load Balancer price sets are the only type which can be associated with Load Balancer Price Plans
+    - **Virtual Image:** ‘Virtual Image’ price sets require at least one ‘Storage’ price type. Virtual Image price sets are the only type which can be associated with Virtual Image Price plans
+    - **Snapshot:** ‘Snapshot’ price sets require at least one ‘Storage’ price type and may also include ‘Datastore’ price types. Snapshot price sets are the only type which can be associated with Snapshot Price plans
+    - **Software/Service:** ‘Software/Service’ Price Sets require at least one ‘Software/Service’ Price type
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
+
+Prices
+:   Search for and select Prices to be added to the Price Set. One of each Price Type required for the Price Set Type selected must be added for the Price Set to save.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json b/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
new file mode 100644
index 0000000..8044479
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+  "title": "Openstack",
+  "ordinal": 464,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md b/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
new file mode 100644
index 0000000..5fd8837
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
@@ -0,0 +1,325 @@
+# Openstack
+
+## Overview
+
+Openstack is becoming a widely used on-premise infrastructure orchestration platform. It has a wide array of contributors and enterprise sponsorships. There are several variations on Openstack as well. HPE Morpheus Enterprise supports integration with all the various platform offerings and ranges in support all the way back to Openstack Juno. The complete list of compatible versions is listed in our [Integration Compatibility table](https://docs.morpheusdata.com/en/latest/release_notes/compatibility.html#integrations). It leverages the APIs and provides full functionality as a self service portal in front of Openstack.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups and Snapshots
+- Security Group Management
+- Disk Mode support Local/Image
+- Floating IP Assignment support
+- Brownfield VM management and Migration
+- Lifecycle Management and Resize
+- Docker Host management and configuration
+- Manila File Services (SFS)
+- Object Storage (OBS)
+- Network Lifecycle
+- LBaaS/Octavia Load Balancing Services
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to Openstack that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Image to QCOW2 Image Conversion
+- QCOW2 to RAW Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+- Instance Cloning
+- HPE Morpheus Enterprise Kubernetes Cluster Deployment
+
+TIP
+
+To allow Morpheus to list Hypervisor Hosts, ensure the Openstack user used for the Cloud Integration has sufficient privileges for `os_compute_api:os-hypervisors` in `/etc/nova/policy.json` in Openstack.
+
+NOTE
+
+CEPH is not supported in Morpheus 8.0.10 or higher.
+
+## Getting Started
+
+OpenStack Clouds are very easy to integrate with HPE Morpheus Enterprise. First, go to the Infrastructure  >  Clouds section and click + ADD. Select OpenStack to begin the integration process, most branded flavors of OpenStack will work with this Cloud selection as well.
+
+WARNING
+
+Support for OpenStack v2 Identity API has been removed in v5.3.3
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   v3 Identity endpoint.
+
+DOMAIN ID
+:   For Default domains, Default can be used. For other domain the Domain ID must be entered, not the Domain Name.
+
+PROJECT
+:   Enter the target project or leave this field blank to integrate all projects
+
+USERNAME
+:   Service Username
+
+PASSWORD
+:   Service user password
+
+OS VERSION
+:   Select Openstack Version. HPE Morpheus Enterprise supports the latest versions of OpenStack, select the latest version available if your current version is not shown.
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK Image Type
+
+LB TYPE
+:   Select LB Type for Openstack LB syncing and creation
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VM’s
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment. When disabled HPE Morpheus Enterprise will use ssh and rdp for console conneciton (vm/host credentials required)
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+NOTE
+
+v5.3.3 adds openstack project management which requires additional permissions in openstack:
+
+```
+```
+identity:list_domain_roles  
+identity:list_role_assignments  
+identity:list_roles  
+identity:list_projects  
+identity:create_project  
+identity:update_project  
+identity:delete_project  
+identity:create_grant  
+identity:revoke_grant
+```
+```
+
+Most of the information in the dialog can be acquired from the Openstack dashboard. under Project  >  Access & Security  >  API Access. The API URL that is needed is the one tied to Identity. The Domain and Project inputs typically correlate to the multitenant domain setup within Openstack (sometimes just left at default) as well as the project name given to instances. HPE Morpheus Enterprise allows multiple integrations to the same Openstack cluster to be scoped to various domains and projects as needed.
+
+The remaining options help HPE Morpheus Enterprise determine which API capabilities exist in the selected Openstack environment. Hence the need for the Openstack version and image format. If a newer Openstack cluster is being used then exists in the dropdown, simply select the most recent version in the dropdown and this should function sufficiently until the new version is added.
+
+TIP
+
+Some Openstack environments do not support QCOW2 and force RAW image formats (like Metapod). This is due to some network overhead in Ceph created by using QCOW2. HPE Morpheus Enterprise keeps two copies of Openstack image templates for this exact purpose.
+
+Saving this cloud integration should perform a verification step and close upon successful completion.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure > Compute > Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+## Service Ports
+
+HPE Morpheus Enterprise consumes the following OpenStack service ports by default as part of its cloud integration. If your OpenStack implementation has been configured to use alternate service ports, these can be overwritten in the Cloud configuration under the Service Endpoints section when adding or editing the Cloud integration.
+
+![../../../_images/serviceEndpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-533A8DF6-01D2-4189-A822-6565F7C5395D-high.png)
+
+### Default Service Ports
+
+- Identity: 5000
+- Compute: 8774
+- Image: 9292
+- Key Manager: 9311
+- Network: 9696
+- Volume API v3: 8776 v3
+- Manila: 8786
+
+## OpenStack Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Openstack Cloud includes the capability to work with Openstack Scalable File Service (SFS). SFS is shared file storage hosted on Openstack Cloud. By integrating HPE Morpheus Enterprise with Openstack you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Openstack Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Openstack Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+Additionally, Openstack SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click +ADD to begin and set the storage server type value to “Openstack SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/addSfs.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-948FDB48-9D25-4116-8FAF-DF9669B6F3E1-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to only file shares whose names match the search terms.
+
+We can drill into individual file shares by clicking on the hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking +ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+“Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Openstack SFS file shares can also be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking +ADD. Select the type “Openstack SFS Share”. Set the storage service field to a pre-existing Openstack SFS server. Setting a friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones is required.
+
+## Network and Router Creation
+
+Once an OpenStack Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “OpenStack Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select OpenStack Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select OpenStack Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OpenStack project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
+
+## Advanced
+
+There are a few advanced features when it comes to provisioning on top of Openstack. Most of these present themselves in the provisioning wizard. This includes OS Volume Type (Local or Volume) which dictates whether the main OS disk is copied and run off the hypervisor or remotely mounted as a volume via Glacier. Some Openstack setups only configure hypervisors with minimal local disks so volume type is needed.
+
+Another option during provisioning is “Assign Floating IP”. This option does exactly what it says and is similar to the feature on the Openstack instance dashboard itself. It should be noted that this will attempt to acquire a floating IP from the project and, if out of capacity, will attempt to increase capacity to the project if the cloud credentials provided have sufficient administrative privileges to do so.
+
+## Docker
+
+So far this document has covered how to add the Openstack cloud integration and has described how to provision virtual machine-based Instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to work with Docker containers and even support multiple containers per Docker host. To do this, a Docker host must first be provisioned into Openstack (multiple hosts are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host, navigate to Infrastructure > Clusters and click + ADD CLUSTER. Complete the provisioning wizard including selecting the appropriate Group and Cloud. Alternatively, you can navigate to the Clusters tab for a specific Cloud (Infrastructure > Clouds > Specific Cloud detail page > Clusterstab) and begin the process of provisioning a Docker host to that Cloud from there. Once completed, this host will show up in the Hosts sections (Infrastructure > HostsOR Infrastructure > Clouds > Specific Cloud detail page > Hoststab). HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones.
+
+Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, the HPE Morpheus Enterprise Agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json b/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
new file mode 100644
index 0000000..28d9d92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md b/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
new file mode 100644
index 0000000..b88b048
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
@@ -0,0 +1,11 @@
+# Getting Started
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html)**
+- **[Capacity and Planning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html)**
+- **[Installation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html)**
+- **[Upgrades & Maintenance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html)**
+- **[Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html)**
+- **[Initial Appliance Setup](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html)**
+- **[Core Functionality](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json b/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
new file mode 100644
index 0000000..fc97d20
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+  "title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 364,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md b/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
new file mode 100644
index 0000000..61ec5d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
@@ -0,0 +1,281 @@
+# Automated Multi-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. This is a companion guide to our [single-node application deployment guide](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.xml) and, in some cases, will refer directly to sections of that guide rather than duplicating information here.
+
+In this guide, we will create a custom App Blueprint for SuiteCRM consisting of a database node and an application node. Once configured, the provisioning process is completely automated (Provisioning > Apps) and results in the two-tiered app mentioned previously. We’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a multi-tiered application:
+
+- App Blueprints
+- Cypher
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. Additionally, while this could be done on many different Cloud types, I’m setting up this Instance Type for provisioning on a VMware vCenter Cloud. You would need to have a VMware Cloud already integrated with HPE Morpheus Enterprise in order to follow the guide exactly but I will not go through the process of creating new Clouds here. If you do not have a vCenter Cloud available to you, the concepts in the guide will translate to other Cloud types, including public clouds like Amazon AWS. You may have to make slight modifications in spots in order to make a fully working Instance Type for other Clouds.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. In this case, we need to store two Cypher secrets: The first is for the MySQL root password and the second is for the user which we will use to run SSH commands from the app server to the database server. Refer to the [single-node deployment guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-cypher) for details on setting up the first Cypher entry.
+
+Next we need to set up a Cypher for the SSH user so our application node can access the database. A handy trick here is to use the user specified in the HPE Morpheus Enterprise global Cloud-Init Setting as this will be automatically created on the Instances when they are provisioned by HPE Morpheus Enterprise. To check that the user is set up correctly, in the HPE Morpheus Enterprise UI go to Administration > Settings > Provisioning. Under the Cloud-Init Settings section, ensure that a username and password is set. After that, simply create a secret/cloudinit Cypher entry which stores the password for this user using the same process by which you set up the MySQL root password Cypher entry.
+
+## Create Inputs
+
+Inputs are custom input fields in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password. The steps to create these inputs have been detailed in the companion guide, if needed, you can reference them [here](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-inputs).
+
+## Create File Template and Library Template Task
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. We’ll also create a Task which we can use to automatically set our file template at the appropriate time during provisioning. The steps to create the [File Template](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-file-templates) and [Library Template Task](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks) are detailed in the companion guide so follow the links for walkthrough steps and return to this guide.
+
+## Create Database Install Task
+
+Since the database is installed on its own node, we need a Task which installs just database. In the prior section, we created a Library Template Task but this time we will create Bash Script Tasks to handle database node installation and application node installation. We’ll also need a simple third Task to restart the Apache service after setting the config file. We’ll go through the steps for creating all three of these Tasks in this section.
+
+Navigate to Library > Automation > Tasks and click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install db multi node
+- **Code:** suitecrminstalldbMN
+- **Type:** Shell Script (The proper fields will appear once the Type is set)
+- **Sudo:** Checked
+- **Source:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **Execute Target:** Resource
+
+### Database Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` != 0 ]  
+then  
+      sleep 120  
+fi  
+#Install MariaDB, start service and enable on boot  
+wget https://downloads.mariadb.com/MariaDB/mariadb_repo_setup  
+echo "fd3f41eefff54ce144c932100f9e0f9b1d181e0edd86a6f6b8f2a0212100c32c mariadb_repo_setup" | sha256sum -c -  
+chmod +x mariadb_repo_setup  
+./mariadb_repo_setup  --mariadb-server-version="mariadb-10.6"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enable mariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -u root -e "UPDATE mysql.user SET Password=PASSWORD('$RPass') WHERE User='root';"  
+mysql -u root -e "flush privileges"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass -e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.db WHERE Db='test' OR Db='test\_%';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Set bind-address parameter in my.cnf  
+sed -e '/^bind/s/^/#/g' -i /etc/mysql/mariadb.conf.d/50-server.cnf  
+systemctl restart mariadb.service
+```
+```
+
+## Create Application Install and Apache Restart Tasks
+
+We now need to create a Bash script task to install the application. However, before we do this, we need to consider how these Tasks will run. We need to have the database installed before the application. We can achieve this in our App Blueprint by configuring the boot order so that the database is provisioned before the application. However, as part of the database configuration, we also need to create a database user and set up remote access to the database for the application server IP. The challenge here is that we cannot create the database user as part of the database install Task as we will not know the application server IP address. To get around this, we will run the database configuration Tasks within the application install task using sshpass to remotely execute the MySQL commands on the database. This is where the cloud-init user and Cypher we created earlier come in.
+
+NOTE
+
+In the code section below, remember to set the correct username for your cloud-init user. In the code below it is set to pjonesci. You will also see in the Task below we are using environment variables to pull in the IP address of the database host (MYSQL\_HOST variable). We are able to do this because in the App Blueprint we will connect the tiers which means Instances in a tier can import the evars from Instances in connected tiers.
+
+Once again, click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install app multi node
+- **Code:** suitecrminstallappMN
+- **Type:** Shell Script
+- **Sudo:** Checked
+- **Source:** Local
+- **Execute Target:** Resource
+
+### Application Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+CIPass="<%=cypher.read('secret/cloudinit')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+MYSQL_HOST="<%=evars.SUITECRMDBMN_IP%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+        sleep 120  
+fi  
+#Install sshpass and apache, start service and enable on boot  
+apt-get install sshpass -y  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Use sshpass to remotely execute mysql commands on DB server to create database and database user  
+sshpass -p $CIPass ssh -o StrictHostKeyChecking=no -t pjonesci@$MYSQL_HOST <<REMOTE  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE USER '$SCRMUser'@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO $SCRMUser@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+REMOTE  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php7.3 libapache2-mod-php7.3 php7.3-common php7.3-mysql php7.3-gmp php7.3-curl php7.3-intl php7.3-mbstring php7.3-xmlrpc php7.3-gd php7.3-bcmath php7.3-imap php7.3-xml php7.3-cli php7.3-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+ sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" /etc/php/7.3/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+curl -sS https://getcomposer.org/installer | sudo php -- --version=1.10.9 --install-dir=/usr/local/bin --filename=composer  
+git clone https://github.com/salesagility/SuiteCRM.git /var/www/html/suitecrm  
+cd /var/www/html/suitecrm  
+composer install --no-dev  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+Finally, create the Apache restart Task mentioned earlier. The exact steps to create this Task are shown in the [companion single-node application guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks).
+
+## Create Workflows
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provision phase. One Workflow will primarily handle database node installation and the other will primarily handle application node installation.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRMDB - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install db multi node” Task
+
+![../../_images/dbwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AE350F66-EE19-401B-A0C9-EB946194C3F2-high.png)
+
+Click SAVE CHANGES and then create the second Workflow:
+
+- **NAME:** SuiteCRMApp - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install app multi node”, “suitecrm file template”, and “suitecrm apache restart” Tasks
+
+Click SAVE CHANGES
+
+![../../_images/appwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B02FA612-F552-422C-B489-354AB4074DE4-high.png)
+
+## Create Instance Types for the Database and Application
+
+At this point we’re ready to put our pieces together into custom Instance Types for the database and application. Instance Types can be provisioned individually (Provisioning > Instances) but in this case we want to structure multiple Instance Types into logical tiers in an App Blueprint so they can be provisioned as a HPE Morpheus Enterprise App. Each Instance Type will contain a Layout and a Node Type, I’ll discuss each construct more fully as it’s time to create them.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Set the following configurations:
+
+- **NAME:** SUITE\_CRM\_DB\_MN
+- **CODE:** suitecrmdbmn
+- **CATEGORY:** SQL
+- **ICON:** If desired, browse your local computer for a MariaDB icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMDBMN
+
+![../../_images/dbinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-992A3460-9FE9-4F5F-ABB2-FB8F13F0B3A9-high.png)
+
+Click SAVE CHANGES. With the Instance Type created, we’re ready to add a Layout. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** LO\_SUITE\_CRM\_DB\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **WORKFLOW:** Select the “SuiteCRM - Multi Node” Workflow that was previously created
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/dblo.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6BAE38A4-A27D-447A-86D1-01C6CF434D0E-high.png)
+
+Click SAVE CHANGES. With the Layout created, we’re ready to associated a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. In this case, we’re simply going to point to a default Ubuntu image which is supplied by HPE Morpheus Enterprise though you can associate Node Types with your own custom virtual images when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** NODE\_SUITE\_CRM\_DB\_MN
+- **SHORT NAME:** nodesuitecrmdbmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+Click SAVE CHANGES. This completes the database Library item needed to build out our App Blueprint in the next section. We now need to add a Library item representing the application node. Below I will list out the configurations for the Instance Type, Layout, and Node Type, you can refer back to the steps above if you need to see the click-by-click instructions once again for creating these objects.
+
+- **NAME:** SUITE\_CRM\_APP\_MN
+- **CODE:** suitecrmappmn
+- **CATEGORY:** Apps
+- **ICON:** If desired, browse your local computer for a SuiteCRM icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMAPPMN
+
+![../../_images/appinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D63BD45E-E0A9-4D0D-BAA2-2EFF77CC111B-high.png)
+
+- **NAME:** LO\_SUITE\_CRM\_APP\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4 GB (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/applo.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-29EF47D8-7883-4F20-8C82-6995D7CA784C-high.png)
+
+- **NAME:** NODE\_SUITE\_CRM\_APP\_MN
+- **SHORT NAME:** nodesuitecrmappmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+![../../_images/appnode.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0BBD1C18-2B48-489F-959F-214CD44CED21-high.png)
+
+## Create the App Blueprint
+
+We are now ready create a HPE Morpheus Enterprise App Blueprint. HPE Morpheus Enterprise Blueprints allow pre-configured multi-tier application deployments for multiple environments. In this example we will use the custom Instance Types previously created to build out an App Blueprint for a two-tier SuiteCRM application with the database running on one VM and the application running on another VM.
+
+Go to Library > Blueprints > App Blueprints and click + ADD. Enter a name for the Blueprint (SuiteCRM Multi Node) and set type to HPE Morpheus Enterprise. Click NEXT.
+
+You will now be in the App Blueprint configuration screen where you can build out the structure of the App Blueprint. In the structure section on the left of the screen, click the + to add App Tier and then click it again to add a Database tier.
+
+![../../_images/namebp.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4B83AA01-4C21-4B94-B440-4E5E0BE1A81A-high.png)
+
+Now that we have the tiers created, we can create the configuration for each tier. Click the “+”” next to the App tier and in the window that pops up select the application Instance Type created previously (SUITE\_CRM\_APP\_MN).
+
+![../../_images/setappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-53BFEE5F-524C-498F-8000-E746C992C738-high.png) ![../../_images/nameappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D440051E-3817-4EFA-BEEF-AE37834507C5-high.png)
+
+Now click the “+” next to the Suite CRM Instance Type (under App). Select the Group and Cloud required (I’m selecting my VMware Cloud, in this case) and then click ADD CONFIG.
+
+![../../_images/setappcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-78CEFAB6-9636-4B0D-AC7A-913583BD97C9-high.png)
+
+You will now have a configuration under the Suite CRM icon. Click on the configuration and it will appear in the right-hand pane of the window. Fill in the configuration required to provision the Instance. The locks to the right of the fields allow you to lock down entries so that they cannot be changed when provisioning the App later. Do not click COMPLETE yet, we still need to configure the database tier.
+
+![../../_images/configappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-81561E16-36A7-44E7-AB89-4D944C4C34A4-high.png)
+
+Back in the left-hand pane, click the “+” next to Database and perform the same steps as before to add in the SUITE\_CRM\_DB\_MN Instance Type to the database tier. Add in the required configuration.
+
+![../../_images/configdbins.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0D8D8FF1-9617-4369-B1DF-B49DE4993A26-high.png)
+
+Once the configuration is set up for both tiers, we need to set the boot order and connect the tiers. The boot order is used to control the order in which the tiers are built. We want the database tier to build first, so we set the boot order to 0 on the database and 1 on the application. We also need to connect the tiers by checking the box under connected tiers.
+
+![../../_images/dbbootorder.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5C12EFCD-2D25-427F-AE41-752B282FF1C1-high.png)
+
+Save the App Blueprint by clicking COMPLETE.
+
+## Deploy the App Blueprint
+
+To deploy an App Blueprint, navigate to Provisioning > Apps and click + ADD. Select the App Blueprint we just created and work through the provisioning wizard, including naming the App and selecting the target Cloud.
+
+NOTE
+
+For the database hostname, specify the internal IP address of the database node
+
+![../../_images/app1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CA2843B6-3893-49B7-97B7-3236C92974E1-high.png) ![../../_images/app2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-11B85356-456E-453E-819A-E1848F22A86E-high.png) ![../../_images/app3.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-90155AD7-21F3-4243-BE6B-DE3205678495-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_APP\_NODE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json b/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
new file mode 100644
index 0000000..cc8cdf1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+  "title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+  "ordinal": 427,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html",
+  "topic_cluster": {
+    "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md b/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
new file mode 100644
index 0000000..cfb5f18
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
@@ -0,0 +1,33 @@
+# Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure
+
+After applying an HPE Service Pack for ProLiant (SPP) on Gen11 and Gen12 servers, a full cold power cycle is required to ensure proper initialization of updated firmware components.
+
+An iLO reset or standard operating system reboot is not sufficient after an SPP update.
+
+Failure to perform a cold power cycle may result in:
+
+- Inconsistent Redfish storage inventory
+- Smart Array controller desynchronization
+- Missing or stale drive objects
+- Management platform initialization failures
+- Incomplete firmware activation
+
+Perform the following steps for cold power cycle:
+
+1. **Power OFF the server**:Shut down gracefully through the operating system or iLO interface. Confirm the server is completely powered off.
+2. **Disconnect AC Power**: Physically remove all power cables from the server power supplies.
+3. **Wait for 60 Seconds**: Allow sufficient time for residual power to drain. This clears controller cache and resets hardware state.
+4. **Reconnect Power**: Reattach all power cables securely.
+5. **Power ON the Server**: Boot the system normally.
+
+A full AC power removal forces:
+
+- Smart Array controller re-enumeration
+- PCI bus reinitialization
+- Storage firmware reload
+- Redfish object tree regeneration
+- Hardware state synchronization
+
+This process resolves the majority of post-SPP Redfish storage inconsistencies observed on Gen11 and Gen12 platforms.
+
+HPE strongly recommends performing a full cold power cycle after major firmware bundle updates to ensure all updated components are fully initialized.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json b/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
new file mode 100644
index 0000000..661e848
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+  "title": "Resource Center",
+  "ordinal": 527,
+  "parent_title": null,
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3CEB493A-1086-4AE2-8220-93B372329509.html",
+  "topic_cluster": {
+    "clustering_title": "Resource Center",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md b/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
new file mode 100644
index 0000000..df78ca3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
@@ -0,0 +1,5 @@
+# Resource Center
+
+- [Developer Zone](https://developer.morpheusdata.com/)
+- [Support KnowledgeBase](https://support.morpheusdata.com/s/knowledge-base?language=en_US)
+- [White Papers](https://www.morpheusdata.com/resource-center)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json b/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
new file mode 100644
index 0000000..0b5aefe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+  "title": "F5 Load Balancers",
+  "ordinal": 498,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html",
+  "topic_cluster": {
+    "clustering_title": "F5 Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md b/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
new file mode 100644
index 0000000..ec1af30
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
@@ -0,0 +1,139 @@
+# F5 Load Balancers
+
+## Virtual Servers
+
+Instances attached to an F5 will be listed in the Virtual servers tab. Virtual servers can also be manually added in this section.
+
+### Add Virtual Server
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers
+2. Select F5 Integration name to drill into the detail page
+3. Select + ADD in the VIRTUAL SERVERS tab
+4. Fill in the following: 
+
+   - NAME
+     :   Name of the Virtual Server in HPE Morpheus Enterprise
+   - DESCRIPTION
+     :   Description of the Virtual Server in HPE Morpheus Enterprise
+   - Enabled
+     :   Uncheck to keep the configuration but disable F5 availability in HPE Morpheus Enterprise
+   - VIP TYPE
+     :   - Standard
+         - Forwarding (Layer 2)
+         - Forwarding (IP)
+         - Performance (HTTP)
+         - Performance (Layer 4)
+         - Stateless
+         - Reject
+         - DHCP
+         - Internal
+         - Message Routing
+   - VIP HOSTNAME
+     :   Enter Hostname of the VIP (optional)
+   - VIP ADDRESS
+     :   Enter IP address for the VIP
+   - VIP PORT
+     :   Enter post used for the VIP
+   - SOURCE ADDRESS
+     :   Enter Virtual Server source address
+   - PROTOCOL
+     :   tcp, udp, or sctp
+   - PROFILES Search for and select from available PROFILES
+   - POLICIES
+     :   Search for and select from available POLICIES
+   - IRULES
+     :   Search for and select from available RUEL SCRIPTS
+   - PERSISTENCE
+     :   - cookie
+         - dest-addr
+         - global-settings
+         - hash
+         - msrdp
+         - sip
+         - source-addr
+         - ssl
+         - universal
+   - DEFAULT POOL
+     :   Select from available POOLS
+5. Select SAVE CHANGES
+
+## Policies
+
+Policies will be synced and listed in the Policies tab. These policies will be available options when creating Virtual Servers.
+
+## Pools
+
+### Create Pool
+
+NAME
+:   Name of the POOL in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the POOL in HPE Morpheus Enterprise
+
+BALANCE MODE
+:   - Round Robin
+    - Least Connections
+
+SERVICE PORT
+:   Specify SERVICE PORT for the POOL
+
+MEMBERS
+:   Search for and select from available NODES
+
+MONITORS
+:   Search for and select from available Monitors
+
+## Profiles
+
+SSL Profiles are synced and and will be created when an SSL Certificate is assigned in the Load balancer section when provisioning or editing a Load balancer on an Instance.
+
+## Monitors
+
+### Create Monitor
+
+NAME
+:   Name of the MONITOR in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the MONITOR in HPE Morpheus Enterprise
+
+PARENT MONITOR
+:   Select from available MONITORS
+
+DESTINATION
+:   Specify Destination, such a `*:443`. Default is `*:*`
+
+INTERVAL
+:   Specify Monitor Interval. Default is `5`
+
+TIMEOUT
+:   Specify Monitor Timeout. Default is `15`
+
+MONITOR CONFIG
+:   Enter monitor config.
+
+## Nodes
+
+### Create Node
+
+NAME
+:   Name of the NODE in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the NODE in HPE Morpheus Enterprise
+
+ADDRESS
+:   Enter node address
+
+MONITOR
+:   Select from available MONITORS
+
+SERVICE PORT
+:   Specify SERVICE PORT for the NODE
+
+## Rule Scripts
+
+Rule Scripts will be synced and listed in the RULE SCRIPTS tab. These rules will be available options when creating Virtual Servers.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json b/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
new file mode 100644
index 0000000..2886e60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 184,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md b/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
new file mode 100644
index 0000000..1fb38e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
@@ -0,0 +1,11 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+![../../_images/managePlacement.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-496FBC66-FFC3-4D76-B3D1-F0E4F31A838D-high.png)
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json b/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
new file mode 100644
index 0000000..e05d808
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+  "title": "Forms",
+  "ordinal": 153,
+  "parent_title": "Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html",
+  "topic_cluster": {
+    "clustering_title": "Forms",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md b/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
new file mode 100644
index 0000000..d40193b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
@@ -0,0 +1,163 @@
+# Forms
+
+Forms are designed to be used with [Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items). Using the provided tools, build forms to provide the appropriate customization fields for endusers in the Provisioning Catalog. Catalog Items can also be built using HPE Morpheus Enterprise Inputs but Forms provide unique capabilities that open up additional functionality and simplify the process. Once a Form is created it is then available to be associated with a Catalog Item. This section discusses the creation of Forms, the available options, and how they can be used effectively to create Catalog Items.
+
+## Creating a New Form
+
+To begin a new Form, navigate to Library > Options > Forms and click + ADD.
+
+![../../_images/newForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-79EB5F32-18B1-4437-9727-EA6FEC436A5C-high.png)
+
+## Adding Field Groups
+
+Field Groups are logical groupings of Input fields on your Form. Especially with larger forms, they make the Form easier to read and use. You can even collapse down sections of less commonly needed Inputs to keep your Forms clean. By default a new Form has no Field Groups but one can be added by clicking “+ ADD FIELD GROUP” in the center of the NEW FORM modal (which can be seen in the screenshot above). Field Groups can accept the following options:
+
+- **NAME:** The name and label for the Field Group
+- **DESCRIPTION:** And optional description for the Field Group
+- **COLLAPSIBLE:** When marked, the user can collapse (hide) or show the Field Group
+- **COLLAPSIBLE BY DEFAULT:** If the Field Group is marked collapsible, this option will appear to make the Field Group shown (unchecked) or hidden (checked) by default
+- **VISIBILITY FIELD:** Enter the fieldName of another Input and this Field Group will appear only when that Input has a value
+
+![../../_images/newFieldGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-07A59B83-A70F-407E-83F5-B6ABCB054D52-high.png)
+
+## Adding Inputs
+
+Inputs are the Form options themselves and can take various forms, such as text fields, checkboxes, select lists or other custom forms. Inputs can be added outside of any created Field Groups or they may be added within them. Click + ADD INPUT within the desired area (inside a Field Group or outside of them).
+
+When adding Inputs, you may add any Input (Library > Options > Inputs) that is pre-existing to your form. Set “USE EXISTING” to “Yes” and make the selection from the “EXISTING OPTION TYPE” typeahead field. Once selected, you’ll notice that all other settings cannot be edited. If needed, edit this Input within the Inputs section (Library > Options > Inputs).
+
+![../../_images/existingInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-25AEAFA2-3766-4411-9796-FCCD26396206-high.png)
+
+When adding Inputs, you may also create new Inputs within the Form builder. Some available types are no different than other Inputs you might make in the Input section (Library > Options > Inputs) but other types are unique to Forms. To create a new Input, set “USE EXISTING” to “No” and select the desired type.
+
+Input types are organized by categories. Inputs in the basic category are primarily the same types of Inputs that can be made in the Inputs section (Library > Options > Inputs). These include text fields, select lists, checkbox arrays, numerical inputs, and more. You can read more about the basic Input types in HPE Morpheus Enterprise [Input documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#inputs).
+
+Inputs in the Advanced and Provisioning categories are unique to Forms and require additional explanation. Advanced inputs are similar to basic but provide some sort of data manipulation capability or have a specific targeted function. See the list of advanced Input types below:
+
+- **Byte Size:** Allows numerical disk or storage size values to be given with selectable units (MB, GB, etc.). When a value is input and the unit is changed, the same value will be automatically computed into the new unit amount (1 GB > 1024MB, for example). Users may select which unit is initially loaded by default.
+- **Code Editor:** Gives the user a code editor field. Set a language or markdown format in the “HIGHLIGHTING” field to enable automatic syntax highlighting and spacing for the user. For example, the user could enter a provisioning shell script for their workload or provide a custom JSON payload at provision time (complete with syntax highlighting for easy entry).
+- **File Content:** Access file content either locally entered or sourced from an integrated repository or outside URL
+- **Icon Picker:** Allows the user to select an icon for their workload at provision time. The user may select from previously uploaded icons, upload their own, or use the built-in icon generator tool to create a unique icon right in the Form
+- **Key Value:** Allows the user to enter as many key/value pairs as they’d like which can be onboarded into the workload config at provision time
+- **Text Array:** Allows the user to enter multiple values separated by a delimiter of your choosing. HPE Morpheus Enterprise will parse out the entered values which can be individually deleted if desired before the form is submitted
+- **Typeahead:** Similar to Select List, especially for very long lists. Search for the desired value by typing the first few letters as a search parameter. Users may also browse the complete list by clicking the dropdown icon. This Input type can also support multiple selections, if needed. Associate this type of Input with a pre-defined Option List or create a new Option List right inside the Form builder
+
+![../../_images/forms1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E413A285-DAE5-4097-ABD7-5503BDA5B518-high.png)
+
+Inputs in the provisioning category are specifically tied to some provisioning construct in HPE Morpheus Enterprise (Groups, Clouds, etc.). They’re very useful for allowing users to select specific provisioning constructs, such as the Group, Cloud, Layout, or Network they wish to provision, and can automatically inject the user’s selection into the Catalog Item. This makes for much simpler Catalog Item development as compared to setting up the configuration using just the Input construct outside of Forms.
+
+Provisioning Inputs also include relevant reload and filtering behaviors by default. For example, your Cloud Input field will automatically reload after making a Group selection or your Layout Input field will automatically reload after setting a Group, Cloud, and Instance Type. This makes it very easy to create flexible Catalog Item forms that are useful across Clouds.
+
+The following provisioning Input types are supported, each with their own automatic filtering behavior and auto-inject capability into the Catalog Item spec:
+
+- Cloud
+- Disks
+- Exposed Ports
+- Group
+- Layout
+- Networks
+- Plan
+- Resource Pool
+- Security Groups
+- Tags
+- Vmw Folders
+
+![../../_images/forms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-186CA89B-1E7C-49B9-9C71-3CD0CE4E9A59-high.png)
+
+In order for provisioning Inputs to work properly, be sure to properly set the fields they should filter against. In the screenshot below you can see for a Resource Pool Input I’ve set the Group, Cloud, Layout, and Plan Inputs that it must be filtered against in order to work. Search for the Field Label of the target Input.
+
+![../../_images/poolFilters.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8E7A4B9B-FC72-4F3D-9EB8-6625130B3DA4-high.png)
+
+Once the type selected, the new Input will have many configuration options, most of which are the same options available when creating an Input from the Inputs section though some are new and some are presented in slightly different ways. The available options depend on the Input type selected but common options are shown in the expandable section below:
+
+### Common Input Configuration Options
+
+FIELD LABEL
+:   The name and label of the Input
+
+LOCALIZED LABEL
+:   If a localization code is selected, this field will have a translated label relative to the localization language selected for the appliance or user
+
+FIELD NAME
+:   This is the Input fieldName property used to resolve the field value into code or to refer to this field for creating dynamic relationships with other Input fields
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+LOCALIZED HELP BLOCK
+:   If a localization code is selected, this field will have a translated help block relative to the localization language selected for the appliance or user
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+LOCKED
+:   The Input field is visible but locked from being edited by the user. Any configured default values will be seen and set on the Instance but the user may not change the value
+
+HIDDEN
+:   Hides the field from view. The field is still active, however, and any configured default value would still be set
+
+EXCLUDE FROM SEARCH
+:   For Select List and Typeahead Inputs, check to exclude the form data from being stored as variables (which can be leveraged from an API call when needed)
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+ALLOW MULTIPLE SELECTIONS
+:   For certain Input types which support multiple selections (Select List and Typeahead, for example), check to allow multiple items to be selected
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+A complete example form making use of provisioning Inputs and Field Groups is shown below:
+
+![../../_images/completeForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B953106A-64A3-4A8C-9BA9-428AE4A26C8A-high.png)
+
+## Using Localized Labels on Form Fields
+
+In creating a Form Input, you may enter a custom static text label by setting the FIELD LABEL attribute on the Input. Using this will set a label for your Form field which will appear the same for all users. Alternatively, you can set a dynamic text label by selecting an entry from the LOCALIZED LABEL typeahead field. By setting a Localized Label, the label will appear differently depending on the user’s web browser language localization setting, the HPE Morpheus Enterprise appliance localization setting (set in the [global settings area](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html)), or the user’s own localization setting from within the [User Settings section](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html). More specific localization settings (such as a user’s setting over the appliance-wide setting) override less specific settings.
+
+As an example, I’ll create a simple Form which has only a Group-type Input. Both the Field Label and Localized Label fields have been filled but the Localized Label takes precedence. Based on the localization settings for the user creating this Form, we see the label presented in US English as “GROUP.”
+
+![../../_images/buildForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2A54A030-6474-4ACB-B3A2-8E428EBF215E-high.png)
+
+If we then navigate to provision a Catalog Item based on this Form, we still see the US English “GROUP” field label as this specific user has a default localization of “English (United States)” in its User Settings menu.
+
+![../../_images/english.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F11BC817-1A85-4274-A47B-D401E36D4BDB-high.png)
+
+However, if we select a different user which has a default localization of “French,” and go to provision the same Catalog Item, the field label is shown in French.
+
+![../../_images/french.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-40BAFA08-1439-49F9-B642-C7C3FAED943F-high.png)
+
+HPE Morpheus Enterprise has several complete language packs and also allows users to contribute to new or in-progress language packs. If interested in creating or contributing to UI translations, take a look at [this YouTube video](https://www.youtube.com/watch?v=oX25kutg8vU).
+
+## Turning Forms into Catalog Items
+
+Once created, Forms can be associated with Catalog Items in the same way individual Inputs could before Forms were added. Add a new Catalog Items (or edit an existing one) in Library > Blueprints > Catalog Items. For complete details, refer to documentation on [creating Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#building-catalog-instances).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json b/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
new file mode 100644
index 0000000..788814f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+  "title": "Variables",
+  "ordinal": 166,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html",
+  "topic_cluster": {
+    "clustering_title": "Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md b/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
new file mode 100644
index 0000000..d23f8f1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
@@ -0,0 +1,1373 @@
+# Variables
+
+A vast number of variables are available for use in Tasks, Scripts, Templates, Resource Names, Cloud-Init User Data and Option List configs.
+
+IMPORTANT
+
+Variables are case sensitive
+
+## Pre-Provision Vars
+
+A subset of variables are available for Instance, Host Name and Hostnames. These can be passed inside `${ }` blocks during provisioning or in relevant policy configs. Groovy syntax can be resolved to allow for dynamic name generation as shown in some of the examples below.
+
+Instance Naming Policy example: `${userInitials}-${cloudCode}-${platform == 'windows' ? 'W' : 'L'}-${sequence}`
+
+Available variables for Naming Policy naming patterns include:
+
+```
+```
+${account}  
+${accountId}  
+${accountName}  
+${accountNumber}  
+${accountType}  
+${cloudCode}  
+${cloudName}  
+${customerNumber}  
+${customOptions.fieldName}  
+${groupCode}  
+${groupName}  
+${instance.instanceContext} # Environment Code  
+${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+${platform}  
+${provisionType}  
+${sequence} # results in 1  
+${sequence+100} # results in 101  
+${sequence.toString().padLeft(5,'0')} # results in 00001  
+${tenantId}  
+${tenant} # Tenant Name  
+${tenantSubdomain}  
+${type}  
+${userId}  
+${userInitials}  
+${username}
+```
+```
+
+An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+NOTE
+
+It’s not recommended that users include “>”, “<”, “%”, “$”, or “=” in naming policies.
+
+## Syntax Examples
+
+PowerShell Example: `$app_id = "<%= instance.metadata.app_id %>"`
+
+Bash Example: `HOSTNAME="<%= container.server.hostname %>"`
+
+Python Example: `hostname = morpheus['server']['hostname']`
+
+HTTP Body Example: `{"name": "<%= instance.createdByUsername %>"}`
+
+![../_images/Metadata-Enviornment-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-14CAAF3E-4218-42AA-9D8B-8511E2C5E913-high.png) ![../_images/Tags-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B9FCD0BE-6651-4DA3-BC61-3AB7E704065C-high.png)
+
+NOTE
+
+customOptions values are defined from custom Inputs.
+
+## Common Examples
+
+```
+```
+                  container.configGroup: <%=container.configGroup%>  
+                  container.configId: <%=container.configId%>  
+                  container.configPath: <%=container.configPath%>  
+                  container.configRole: <%=container.configRole%>  
+                  container.containerTypeCode: <%=container.containerTypeCode%>  
+                  container.containerTypeName: <%=container.containerTypeName%>  
+                  container.containerTypeShortName: <%=container.containerTypeShortName%>  
+                  container.cores: <%=container.cores%>  
+                  container.dataPath: <%=container.dataPath%>  
+                  container.dateCreated: <%=container.dateCreated%>  
+                  container.domainName: <%=container.domainName%>  
+                  container.environmentPrefix: <%=container.environmentPrefix%>  
+                  container.externalIp: <%=container.externalIp%>  
+                  container.hostMountPoint: <%=container.hostMountPoint%>  
+                  container.hostname: <%=container.hostname%>  
+                  container.image: <%=container.image%>  
+                  container.internalHostname: <%=container.internalHostname%>  
+                  container.internalIp: <%=container.internalIp%>  
+                  container.logsPath: <%=container.logsPath%>  
+                  container.memory: <%=container.memory%>  
+                  container.planCode: <%=container.planCode%>  
+                  container.provisionType: <%=container.provisionType%>  
+                  container.server: <%=container.server.serverTypeName%>  
+                  container.serverId: <%=container.serverId%>  
+                  container.sshHost: <%=container.sshHost%>  
+                  container.status: <%=container.status%>  
+                  container.storage: <%=container.storage%>  
+                  container.version: <%=container.version%>  
+                  customOptions: <%=customOptions.fieldName%>  
+                  accountNumber: <%= accountNumber %> #resource tenant account number  
+                  customerNumber: <%= customerNumber %> #resource tenant customer number  
+                  accountName: <%= accountName %> # resource tenant account name  
+                  taskOwner.accountNumber: <%= taskOwner.accountNumber %> #task owner tenant account number  
+                  taskOwner.customerNumber: <%= taskOwner.customerNumber %>  
+                  taskOwner.accountName: <%= taskOwner.accountName %>  
+                  user.accountNumber: <%= user.accountNumber %> #user executing task tenant account number  
+                  user.customerNumber: <%= user.customerNumber %>  
+                  user.accountName: <%= user.accountName %>  
+                  evar: <%=evars.name%>  
+                  evars: <%=evars%>  
+                  group.code: <%=group.code%>  
+                  group.datacenterId: <%=group.datacenterId%>  
+                  group.location: <%=group.location%>  
+                  group.name: <%=group.name%>  
+                  instance.autoScale: <%=instance.autoScale%>  
+                  instance.configGroup: <%=instance.configGroup%>  
+                  instance.configId: <%=instance.configId%>  
+                  instance.configRole: <%=instance.configRole%>  
+                  instance.containers[0]: <%=instance.containers[0].containerTypeName%>  
+                  instance.cores: <%=instance.cores%>  
+                  instance.createdByEmail: <%=instance.createdByEmail%>  
+                  instance.createdByFirstName: <%=instance.createdByFirstName%>  
+                  instance.createdById: <%=instance.createdById%>  
+                  instance.createdByLastName: <%=instance.createdByLastName%>  
+                  instance.createdBYUsername: <%=instance.createdByUsername%>  
+                  instance.deployGroup: <%=instance.deployGroup%>  
+                  instance.description: <%=instance.description%>  
+                  instance.displayName: <%=instance.displayName%>  
+                  instance.domainName: <%=instance.domainName%>  
+                  instance.environmentPrefix: <%=instance.environmentPrefix%>  
+                  instance.expireDate: <%=instance.expireDate%>  
+                  instance.firewallEnabled: <%=instance.firewallEnabled%>  
+                  instance.hostname: <%=instance.hostname%>  
+                  instance.instanceContext: <%=instance.instanceContext%> (tip: instanceContext = Environment)  
+                  instance.instanceLevel: <%=instance.instanceLevel%>  
+                  instance.instanceTypeCode: <%=instance.instanceTypeCode%>  
+                  instance.instanceTypeName: <%=instance.instanceTypeName%>  
+                  instance.instanceVersion: <%=instance.instanceVersion%>  
+                  instance.memory: <%=instance.memory%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.name: <%=instance.name%>  
+                  instance.networkLevel: <%=instance.networkLevel%>  
+                  instance.plan: <%=instance.plan%>  
+                  instance.provisionType: <%=instance.provisionType%>  
+                  instance.status: <%=instance.status%>  
+                  instance.statusMessage: <%=instance.statusMessage%>  
+                  instance.storage: <%=instance.storage%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.userStatus: <%=instance.userStatus%>  
+                  server.agentInstalled: <%=server.agentInstalled%>  
+                  server.agentVersion: <%=server.agentVersion%>  
+                  server.apiKey: <%=server.apiKey%>  
+                  server.category: <%=server.category%>  
+                  server.commType: <%=server.commType%>  
+                  server.configGroup: <%=server.configGroup%>  
+                  server.configId: <%=server.configId%>  
+                  server.configRole: <%=server.configRole%>  
+                  server.consoleHost: <%=server.consoleHost%>  
+                  server.consolePort: <%=server.consolePort%>  
+                  server.consoleType: <%=server.consoleType%>  
+                  server.consoleUsername: <%=server.consoleUsername%>  
+                  server.dataDevice: <%=server.dataDevice%>  
+                  server.dateCreated: <%=server.dateCreated%>  
+                  server.description: <%=server.description%>  
+                  server.displayName: <%=server.displayName%>  
+                  server.domainName: <%=server.domainName%>  
+                  server.externalId: <%=server.externalId%>  
+                  server.externalIp: <%=server.externalIp%>  
+                  server.fqdn: <%=server.fqdn%>  
+                  server.hostname: <%=server.hostname%>  
+                  server.internalId: <%=server.internalId%>  
+                  server.internalIp: <%=server.internalIp%>  
+                  server.internalName: <%=server.internalName%>  
+                  server.internalSshUsername: <%=server.internalSshUsername%>  
+                  server.lastAgentUpdate: <%=server.lastAgentUpdate%>  
+                  server.lvmEnabled: <%=server.lvmEnabled%>  
+                  server.macAddress: <%=server.macAddress%>  
+                  server.managed: <%=server.managed%>  
+                  server.maxCores: <%=server.maxCores%>  
+                  server.maxMemory: <%=server.maxMemory%>  
+                  server.maxStorage: <%=server.maxStorage%>  
+                  server.name: <%=server.name%>  
+                  server.nodePackageVersion: <%=server.nodePackageVersion%>  
+                  server.osDevice: <%=server.osDevice%>  
+                  server.osType: <%=server.osType%>  
+                  server.osTypeCode: <%=server.osTypeCode%>  
+                  server.parentServerId: <%=server.parentServerId%>  
+                  server.plan: <%=server.plan%>  
+                  server.platform: <%=server.platform%>  
+                  server.platformVersion: <%=server.platformVersion%>  
+                  server.powerState: <%=server.powerState%>  
+                  server.serialNumber: <%=server.serialNumber%>  
+                  server.serverModel: <%=server.serverModel%>  
+                  server.serverType: <%=server.serverType%>  
+                  server.serverTypeCode: <%=server.serverTypeCode%>  
+                  server.serverTypeName: <%=server.serverTypeName%>  
+                  server.serverVendor: <%=server.serverVendor%>  
+                  server.softwareRaid: <%=server.softwareRaid%>  
+                  server.sourceImageId: <%=server.sourceImageId%>  
+                  server.sshHost: <%=server.sshHost%>  
+                  server.sshPort: <%=server.sshPort%>  
+                  server.sshUsername: <%=server.sshUsername%>  
+                  server.status: <%=server.status%>  
+                  server.statusMessage: <%=server.statusMessage%>  
+                  server.tags: <%=server.tags%>  
+                  server.toolsInstalled: <%=server.toolsInstalled%>  
+                  server.visibility: <%=server.visibility%>  
+                  task.results (using task code): <%=results.taskCode%>  
+                  task.results (using task name): <%=results["Task Name"]%>  
+                  task.results.value: <%=results.taskCode.key%>  
+                  zone.agentMode: <%=zone.agentMode%>  
+                  zone.cloudTypeCode: <%=zone.cloudTypeCode%>  
+                  zone.cloudTypeName: <%=zone.cloudTypeName%>  
+                  zone.code: <%=zone.code%>  
+                  zone.domainName: <%=zone.domainName%>  
+                  zone.firewallEnabled: <%=zone.firewallEnabled%>  
+                  zone.location: <%=zone.location%>  
+                  zone.name: <%=zone.name%>  
+                  zone.regionCode: <%=zone.regionCode%>  
+                  zone.scalePriority: <%=zone.scalePriority%>  
+                  cypher: <%=cypher.read('secret/hello')%>  
+cypher: <%=cypher.read('secret/' + zone.code)%> # Make variables more dynamic based off other variables
+```
+```
+
+## Instance
+
+```
+```
+instance {  
+        adminPassword,  
+        adminUsername,  
+        apps.[],  
+        assignedDomainName,  
+        autoScale,  
+        backup.{},  
+        configGroup,  
+        configId,  
+        configRole,  
+        container.{},  
+        containers.[],  
+        cores,  
+        createBackup,  true/false  
+        createdByEmail,  
+        createdByFirstName,  
+        createdById,  
+        createdByLastName,  
+        createdByUser.{  
+                 username,  
+                 displayName,  
+                 firstName,  
+                 lastName,  
+                 email,  
+                 linuxUsername,  
+                 windowsUsername  
+        },  
+        createdByUsername,  
+        createUser, # true/false  
+        customOptions,  
+        deployGroup,  
+        description,  
+        displayName,  
+        domainName,  
+        environmentPrefix,  
+        evars:{},  
+        expireDate, # YYYY-MM-DD-T00:00:00Z  
+        expireDays,  
+        expose.[],  
+        firewallEnabled:true/false,  
+        hostId,  
+        hostname,  
+        id,  
+        instanceContext,  
+        instanceLevel,  
+        instanceTypeCode,  
+        instanceTypeName,  
+        instanceVersion,  
+        isEC2:true/false,  
+        isVpcSelectable, # true/false  
+        layoutCode,  
+        layoutId,  
+        layoutName,  
+        layoutSize,  
+        lbInstances.[],  
+        memory(bytes),  
+        memoryDisplay, #MB/GB  
+        metadata.{},  
+        name,  
+        nestedVirtualization,  
+        networkLevel,  
+        noAgent,  
+        plan,  
+        poolProviderType,  
+        ports,  
+        provisionType,  
+        resourcePoolId,  
+        scheduleStatus,  
+        servicePassword,  
+        serviceUsername,  
+        smbiosAssetTag,  
+        sslCertId,  
+        sslEnabled, # true/false  
+        status,  
+        statusMessage,  
+        storage, # bytes  
+        tags,  
+        userStatus,  
+        vmwareFolderId,  
+}
+```
+```
+
+## Container
+
+```
+```
+container {  
+        configGroup,  
+        configId,  
+        configPath,  
+        configRole,  
+        containerTypeCode,  
+        containerTypeShortName,  
+        cores,  
+        dataPath,  
+        dateCreated,  
+        domainName,  
+        environmentPrefix,  
+        externalIp,  
+        hostMountPoint,  
+        hostname,  
+        image,  
+        internalHostname,  
+        internalIp,  
+        logsPath,  
+        memory,  
+        planCode,  
+        provisionType,  
+        server:{},  
+        serverId,  
+        sshHost,  
+        status,  
+        storage,  
+        version,  
+        containerTypeName  
+}
+```
+```
+
+## Server
+
+```
+```
+server {  
+        agentInstalled,  
+        agentVersion,  
+        apiKey,  
+        category,  
+        commType,  
+        configGroup,  
+        configId,  
+        configRole  
+        consoleHost,  
+        consolePort,  
+        consoleType,  
+        consoleUsername,  
+        dataDevice,  
+        dateCreated,  
+        description,  
+        displayName,  
+        domainName,  
+        externalId,  
+        externalIp,  
+        fqdn,  
+        hostname,  
+        internalId,  
+        internalIp,  
+        internalName,  
+        internalSshUsername,  
+        lastAgentUpdate,  
+        lvmEnabled,  
+        macAddress,  
+        managed,  
+        maxCores,  
+        maxMemory,  
+        maxStorage,  
+        name,  
+        nodePackageVersion,  
+        osDevice,  
+        osType,  
+        osTypeCode,  
+        parentServerId,  
+        plan,  
+        platform,  
+        platformVersion,  
+        powerState,  
+        serialNumber,  
+        serverModel,  
+        serverType,  
+        serverTypeCode,  
+        serverTypeName,  
+        serverVendor,  
+        softwareRaid,  
+        sourceImageId,  
+        sshHost,  
+        sshPort,  
+        sshUsername,  
+        status,  
+        statusMessage,  
+        tags,  
+        toolsInstalled,  
+        visibility,  
+        volumes {  
+                name  
+                id  
+                deviceName  
+                maxStorage  
+                unitNumber  
+                displayOrder  
+                rootVolume  
+        }  
+}
+```
+```
+
+## Zone (Cloud)
+
+```
+```
+zone {  
+        agentMode,  
+        cloudTypeCode,  
+        cloudTypeName,  
+        code,  
+        datacenterId,  
+        domainName,  
+        firewallEnabled,  
+        location,  
+        name,  
+        regionCode,  
+        scalePriority  
+}
+```
+```
+
+## networkConfig
+
+```
+```
+'networkConfig': {  
+  'primaryInterface': {  
+    'doDhcp': false,  
+    'dnsServers': [],  
+    'dnsDomain': "",  
+    'netmask': "",  
+    'gateway': "",  
+    'ipAddress': "",  
+    'doDhcp6': false,  
+    'gateway6': "",  
+    'ipv6Address': "",  
+    'cidr6Suffix': "",  
+    'dnsServers6': ""  
+  },  
+  'extraInterfaces': [  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    },  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    }  
+  ]  
+}
+```
+```
+
+## Group (Site)
+
+```
+```
+group {  
+        code,  
+        location,  
+        datacenterId,  
+        name  
+}
+```
+```
+
+## Custom Options (Inputs)
+
+```
+```
+customOptions {  
+        customOptions.fieldName  
+}
+```
+```
+
+## Global
+
+ex: `<%= morpheus.user.id %>`
+
+```
+```
+"morpheus":{  
+   "user":{  
+      "id":value,  
+      "account":{  
+         "id":value  
+      },  
+      "username":"value",  
+      "displayName":"value",  
+      "email":"value",  
+      "firstName":"value",  
+      "lastName":"value",  
+      "dateCreated":0000-00-00T00:00:00Z,  
+      "lastUpdated":0000-00-00T00:00:00Z,  
+      "enabled":true/false,  
+      "accountExpired":true/false,  
+      "accountLocked":false,  
+      "passwordExpired":false,  
+      "defaultGroupId":value,  
+      "defaultZoneId":value,  
+      "hasLinuxUser":true/false,  
+      "hasWindowsUser":true/false,  
+      "role":{  
+         "id":value  
+      },  
+      "instanceLimits":value  
+   },  
+}
+```
+```
+
+## User
+
+```
+```
+'user': {'accountId': int,  
+        'accountName': 'string',  
+        'accountNumber': 'string',  
+        'attributes': {samlAttributes},  
+        'customerNumber': 'string',  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',
+```
+```
+
+## Script Variables Example
+
+Below is an example of the variables available to a script running against an Instance context.
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+```
+```
+'account': 'string',  
+'accountId': int,  
+'accountType': 'string',  
+'allowExisting': boolean,  
+'apps': [{'appContext': 'string',  
+          'description': 'string',  
+          'id': int,  
+          'name': 'string',  
+'cloud': 'string',  
+'cloudCode': 'string',  
+'cloudName': 'string',  
+'container': {'allowExisting': boolean,  
+              'certificatePath': string,  
+              'certificateStyle': string,  
+              'changeManagementExtId': int,  
+              'changeManagementServiceId': int,  
+              'cloud': 'string',  
+              'cloudConfig': {'agentInstall': agentInstallScript,  
+                              'finalizeServer': finalizeServerScript,  
+                              'meta': metaData,  
+                              'user': userData},  
+              'configGroup': int,  
+              'configId': int,  
+              'configPath': 'string',  
+              'configRole': int,  
+              'containerTypeCategory': 'string',  
+              'containerTypeCode': 'string',  
+              'containerTypeName': 'string',  
+              'containerTypeShortName': 'string',  
+              'cores': int,  
+              'coresPerSocket': int,  
+              'createUser': boolean,  
+              'customOptions': {'morph_ver': 'string',  
+              'dataPath': 'string',  
+              'dateCreated': 'string',  
+              'domainName': 'string',  
+              'environmentPrefix': 'string',  
+              'evars': {},  
+              'expireDays': 'string',  
+              'expose': ['string'],  
+              'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                                'name': 'string',  
+                                'port': int}],  
+              'externalIp': 'string',  
+              'externalPort': int,  
+              'hostMountPoint': 'string',  
+              'hostName': 'string',  
+              'hostname': 'string',  
+              'hosts': {'containerName': 'string',  
+                        'containerName': 'string',  
+                        'containerName': 'string',  
+              'id': int,  
+              'image': 'string',  
+              'instanceContext': 'string',  
+              'instanceType': {'code': 'string',  
+              'internalHostname': 'string',  
+              'internalIp': 'string',  
+              'internalPort': int,  
+              'layout': {'code': 'string',  
+                        'id': int},  
+              'logsPath': 'string',  
+              'maxCores': int,  
+              'maxCpu': int,  
+              'maxMemory': int,  
+              'maxStorage': int,  
+              'memory': int,  
+              'memoryDisplay': 'string',  
+              'mounts': [],  
+              'name': 'string',  
+              'networkId': int,  
+              'networkInterfaces': [{'id': 'string',  
+                                    'ipAddress': 'string',  
+                                    'ipMode': 'string',  
+                                    'network': {'dhcpServer': int,  
+                                                'group': int,  
+                                                'id': int,  
+                                                'name': 'string',  
+                                                'pool': int},  
+                                    'networkInterfaceTypeId': int}],  
+              'noAgent': boolean,  
+              'planCode': 'string',  
+              'portMap': {},  
+              'ports': [{'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean},  
+                        {'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean}],  
+              'provisionType': 'string',  
+              'publicKeyId': int,  
+              'server': {}  
+              'serverId': int,  
+              'shutdownDays': 'string',  
+              'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}],  
+              'sshHost': 'string',  
+              'status': 'string',  
+              'storage': int,  
+              'storageController': int,  
+              'type': 'string',  
+              'userGroup': {'id': '',  
+              'version': 'string',  
+              'vm': boolean,  
+              'volumes': [{'datastoreId': int,  
+                          'id': int,  
+                          'maxIOPS': int,  
+                          'maxStorage': int,  
+                          'name': 'string',  
+                          'rootVolume': boolean,  
+                          'size': int,  
+                          'storageType': int,  
+                          'vId': int}]},  
+'containerName': 'string',  
+'coresPerSocket': int,  
+'createUser': boolean,  
+'customOptions': {'morph_ver': 'string',  
+'deployOptions': {},  
+'evars': {},  
+'expireDays': 'string',  
+'expose': ['string'],  
+'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                  'name': 'string',  
+                  'port': int}],  
+'externalIp': 'string',  
+'group': {'code': 'string',  
+          'configCmdbId': 'string',  
+          'configManagementId': 'string',  
+          'datacenterId': int,  
+          'dnsIntegrationId': 'string',  
+          'location': 'string',  
+          'name': 'string',  
+          'serviceRegistryId': 'string',  
+'groupCode': 'string',  
+'groupName': 'string',  
+'host': ,  
+'hostMountPoint': 'string',  
+'hostName': 'string',  
+'hosts': {},  
+'input': {'backup': ,  
+          'cloud': {},  
+          'computedHostName': 'string',  
+          'computedName': 'string',  
+          'copies': int,  
+          'domainOptions': {}},  
+          'environmentVariables': {},  
+          'executionId': int,  
+          'expireDays': int,  
+          'group': {},  
+          'hostName': 'string',  
+          'instanceContext': 'string',  
+          'layout': {},  
+          'metadata': {}},  
+          'name': 'string',  
+          'plan': {},  
+          'powerScheduleType': int,  
+          'securityGroups': {},  
+          'shutdownDays': int,  
+          'type': 'string',  
+          'version': 'string'},  
+'instance': {'adminPassword': 'maskedString',  
+            'adminUsername': 'string',  
+            'allowExisting': boolean,  
+            'apps': [{}],  
+            'assignedDomainName': 'string',  
+            'autoScale': boolean,  
+            'backup': {'backupRepository': int,  
+                        'createBackup': boolean,  
+                        'enabled': boolean,  
+                        'jobAction': 'string',  
+                        'jobRetentionCount': 'string',  
+                        'providerBackupType': int,  
+                        'showScheduledBackupWarning': boolean},  
+            'cloud': 'string',  
+            'cloudConfig': {'agentInstall': agentInstallScript,  
+                            'finalizeServer': finalizeServerScript,  
+                            'meta': metaData,  
+                            'user': userData  
+                                    },  
+            'configGroup': int,  
+            'configId': int,  
+            'configRole': int,  
+            'container': {},  
+            'containers': [{}],  
+            'cores': int,  
+            'createBackup': boolean,  
+            'createUser': boolean,  
+            'createdByEmail': 'string',  
+            'createdByFirstName': 'string',  
+            'createdById': int,  
+            'createdByLastName': 'string',  
+            'createdByUser': {'accountId': int,  
+                              'displayName': 'string',  
+                              'email': 'string',  
+                              'firstName': 'string',  
+                              'id': int,  
+                              'lastName': 'string',  
+                              'linuxUsername': 'string',  
+                              'username': 'string',  
+                              'windowsUsername': 'string',  
+            'createdByUsername': 'string',  
+            'customOptions': {'morph_ver': 'string',  
+            'deployGroup': ,  
+            'description': 'string',  
+            'displayName': 'string',  
+            'domainName': 'string',  
+            'environmentPrefix': 'string',  
+            'evars': {  
+            'expireDate': date,  
+            'expireDays': 'string',  
+            'expose': ['string'],  
+            'firewallEnabled': boolean,  
+            'hostName': 'string',  
+            'hostname': 'string',  
+            'id': int,  
+            'instanceContext': 'string',  
+            'instanceLevel': 'string',  
+            'instanceType': {'code': 'string',  
+            'instanceTypeCode': 'string',  
+            'instanceTypeName': 'string',  
+            'instanceVersion': 'string',  
+            'layout': {'code': 'string',  
+                        'id': int},  
+            'layoutCode': 'string',  
+            'layoutId': int,  
+            'layoutName': 'string',  
+            'lbInstances': [{'balanceMode': 'string',  
+                              'enabled': boolean,  
+                              'externalAddress': 'string',  
+                              'id': int,  
+                              'instanceId': int,  
+                              'loadBalancer': {'id': int},  
+                              'loadBalancerId': int,  
+                              'name': 'string',  
+                              'port': int,  
+                              'protocol': 'string',  
+                              'sslCert': 'string',  
+                              'sslRedirectMode': 'string',  
+                              'stickyMode': 'string',  
+                              'vipAddress': 'string',  
+                              'vipDirectAddress': 'string',  
+                              'vipHostname': 'string',  
+                              'vipName': 'string',  
+                              'vipPort': int,  
+                              'vipProtocol': 'string',  
+                              'vipScheme': 'string',  
+                              'vipShared': 'string',  
+            'loadBalancerId': int,  
+            'memory': int,  
+            'memoryDisplay': 'string',  
+            'metadata': {'ver': 'string',  
+            'name': 'string',  
+            'networkLevel': 'string',  
+            'plan': 'string',  
+            'ports': {},  
+            'powerScheduleType': ,  
+            'provisionType': 'string',  
+            'scheduleStatus': 'string',  
+            'servicePassword': 'maskedString',  
+            'serviceUsername': 'string',  
+            'shutdownDays': 'string',  
+            'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}]  
+            'sslCertId': int,  
+            'sslEnabled': boolean,  
+            'status': 'string',  
+            'statusMessage': 'string',  
+            'storage': int,  
+            'tags': 'string',  
+            'type': ,  
+            'userGroup': {'id': 'string',  
+            'userStatus': 'string',  
+'instanceContext': 'string',  
+'instanceType': {'code': 'string',  
+'internalIp': 'string',  
+'isDocker': boolean,  
+'layout': {'code': 'string',  
+'localScriptGitId': int,  
+'localScriptGitRef': 'string',  
+'logTag': 'string',  
+'maxCores': int,  
+'maxCpu': int,  
+'maxMemory': int,  
+'maxStorage': int,  
+'memoryDisplay': 'string',  
+'morpheus': {'apiAccessToken': 'string',  
+            'applianceHost': 'string',  
+            'appliancePort': 'string',  
+            'applianceScheme': 'string',  
+            'applianceSsl': boolean,  
+            'applianceUrl': 'string',  
+'morpheusUser': 'string',  
+'mounts': [],  
+'name': 'string',  
+'networkId': int,  
+'networkInterfaces': [{'id': 'string',  
+                      'ipAddress': 'string',  
+                      'ipMode': 'string',  
+                      'network': {'dhcpServer': ,  
+                                  'group': int,  
+                                  'Id': int,  
+                                  'name': 'string',  
+                                  'pool': int},  
+                      'networkInterfaceTypeId': int}],  
+'noAgent': boolean,  
+'platform': 'string',  
+'port': int,  
+'ports': [{'code': 'string',  
+          'displayName': 'string',  
+          'export': boolean,  
+          'exportName': 'string',  
+          'external': int,  
+          'index': int,  
+          'internal': int,  
+          'link': boolean,  
+          'loadBalance': boolean,  
+          'primaryPort': boolean,  
+          'protocol': 'string',  
+          'visible': boolean}],  
+'provisionType': 'string',  
+'publicKeyId': int,  
+'pythonAdditionalPackages': ,  
+'pythonArgs': ,  
+'pythonBinary': 'string',  
+'pythonScript': ,  
+'results': {},  
+'sequence': int,  
+'server': {'agentInstalled': boolean,  
+          'agentVersion': 'string',  
+          'apiKey': 'string',  
+          'category': ,  
+          'cloudConfig': {'agentInstall': agentInstallScript,  
+                          'finalizeServer': finalizeServerScript,  
+                          'meta': metaData,  
+                          'user': userData  
+                                  },  
+          'commType': 'string',  
+          'computeTypeCode': 'string',  
+          'computeTypeName': 'string',  
+          'configGroup': int,  
+          'configId': int,  
+          'configRole': 'string',  
+          'consoleHost': 'string',  
+          'consolePort': int,  
+          'consoleType': 'string',  
+          'consoleUsername': 'string',  
+          'createdByUser': {'accountId': int,  
+                            'displayName': 'string',  
+                            'email': 'string',  
+                            'firstName': 'string',  
+                            'id': int,  
+                            'lastName': 'string',  
+                            'linuxUsername': 'string',  
+                            'username': 'string',  
+                            'windowsUsername': 'string',  
+          'dataDevice': 'string',  
+          'dateCreated': 'string',  
+          'description': 'string',  
+          'displayName': 'string',  
+          'domainName': 'string',  
+          'externalId': 'string',  
+          'externalIp': 'string',  
+          'fqdn': 'string',  
+          'hostname': 'string',  
+          'id': int,  
+          'interfaces': [{'dhcp': boolean,  
+                          'domain': {'fqdn': 'string',  
+                                      'name': 'string',  
+                                      'ouPath': 'string'},  
+                          'interfaceId': int,  
+                          'ipAddress': 'string',  
+                          'ipMode': 'string',  
+                          'ipSubnet': 'string',  
+                          'ipv6Address': 'string',  
+                          'ipv6Subnet': 'string',  
+                          'macAddress': 'string',  
+                          'network': {'cidr': 'string',  
+                                      'cidrMask': 'string',  
+                                      'gateway': 'string',  
+                                      'name': 'string',  
+                                      'netmask': 'string',  
+                                      'vlanId': int},  
+                          'networkPosition': 'string',  
+                          'vlanId': int}],  
+          'internalId': int,  
+          'internalIp': 'string',  
+          'internalName': 'string',  
+          'internalSshUsername': 'string',  
+          'lastAgentUpdate': 'string',  
+          'lvmEnabled': boolean,  
+          'macAddress': 'string',  
+          'managed': boolean,  
+          'maxCores': int,  
+          'maxMemory': int,  
+          'maxStorage': int,  
+          'name': 'string',  
+          'nodePackageVersion': 'string',  
+          'osDevice': 'string',  
+          'osPassword': 'maskedString',  
+          'osType': 'string',  
+          'osTypeCode': 'string',  
+          'osUsername': 'string',  
+          'parentServerId': int,  
+          'plan': 'string',  
+          'platform': 'string',  
+          'platformVersion': 'string',  
+          'powerScheduleType': ,  
+          'powerState': 'string',  
+          'publicKeyId': int,  
+          'serialNumber': 'string',  
+          'serverModel': 'string',  
+          'serverType': 'string',  
+          'serverTypeCode': 'string',  
+          'serverTypeName': 'string',  
+          'serverVendor': 'string',  
+          'softwareRaid': boolean,  
+          'sourceImageId': int,  
+          'sshHost': 'string',  
+          'sshPort': int,  
+          'sshUsername': 'string',  
+          'status': 'string',  
+          'statusMessage': 'string',  
+          'tags': {},  
+          'toolsInstalled': boolean,  
+          'uniqueId': int,  
+          'uuid': 'string',  
+          'visibility': 'string',  
+          'volumes': [{'deviceName': 'string',  
+                        'displayOrder': int,  
+                        'id': int,  
+                        'maxStorage': int,  
+                        'name': 'string',  
+                        'rootVolume': boolean,  
+                        'unitNumber': 'string',  
+'serverId': 'string',  
+'serverName': 'string',  
+'shutdownDays': 'string',  
+'site': {'accountId': int,  
+        'active': boolean,  
+        'id': int,  
+        'integrations': [],  
+        'location': 'string',  
+        'name': 'string',  
+        'visibility': 'string',  
+        'zones': [{}],  
+'sshKey': 'string',  
+'state': {},  
+'storageController': int,  
+'tenant': 'string',  
+'tenantId': int,  
+'tenantSubdomain': 'string',  
+'type': 'string',  
+'user': {'accountId': int,  
+        'attributes': {samlAttributes},  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',  
+'userGroup': {'id': 'string',  
+'userId': int,  
+'userInitials': 'string',  
+'username': 'string',  
+'vm': boolean,  
+'volumes': [{'datastoreId': int,  
+            'id': int,  
+            'maxIOPS': int,  
+            'maxStorage': int,  
+            'name': 'string',  
+            'rootVolume': boolean,  
+            'size': int,  
+            'storageType': int,  
+            'vId': int}],  
+'zone': {'agentMode': 'string',  
+        'cloudTypeCode': 'string',  
+        'cloudTypeName': 'string',  
+        'code': 'string',  
+        'datacenterId': int,  
+        'domainName': 'string',  
+        'firewallEnabled': boolean,  
+        'location': 'string',  
+        'name': 'string',  
+        'regionCode': 'string',  
+        'scalePriority': int}}
+```
+```
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+## Spec Template Variables
+
+Spec Template Variables
+
+- **morpheus**
+  - getApiAccessToken()
+  - formatMemory(size, unit)
+  - applianceUrl
+  - applianceHost
+  - appliancePort
+  - applianceScheme
+  - applianceSsl
+  - morpheusHome
+  - morpheusUser
+  - publicKey
+  - privateKey
+  - cloudConfig
+- **cypher**
+  - read(key)
+  - write(key, value)
+  - delete(key)
+  - readUuid(key)
+  - readEncyptionKey(key)
+  - readPassword(key)
+- **archives**
+  - link(bucketName, filePath)
+- account
+- accountId
+- accountType
+- **apps - []**
+  - appContext
+  - description
+  - id
+  - name
+- **cloudConfig**
+  - agentInstall
+  - finalizeServer
+- **customOptions**
+  - key
+- **deployOptions**
+  - key
+- **evars**
+
+  - key
+- **group**
+  - code
+  - datacenterId
+  - location
+  - name
+- groupCode
+- groupName
+- **input**
+  - backup
+  - cloud
+  - computedHostName
+  - computedName
+  - copies
+  - domainOptions
+  - environmentVariables
+  - executionId
+  - expireDays
+  - group
+  - hostName
+  - instanceContext
+  - layout
+  - metadata
+  - name
+  - plan
+  - powerScheduleType
+  - securityGroups
+  - shutdownDays
+  - type
+  - version
+- **instance**
+  - adminPassword
+  - adminUsername
+  - apps - []
+    - appContext
+    - description
+    - id
+    - instances
+    - name
+  - assignedDomainName
+  - autoScale
+  - cloudConfig
+    - agentInstall
+    - finalizeServer
+  - configGroup
+  - configId
+  - configRole
+  - container
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - containers - []
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - cores
+  - createdByEmail
+  - createdByFirstName
+  - createdById
+  - createdByLastName
+  - createdByUser
+    - accountId
+    - attributes
+    - displayName
+    - email
+    - firstName
+    - id
+    - lastName
+    - linuxUsername
+    - username
+    - windowsUsername
+  - createdByUsername
+  - customOptions
+    - key
+  - deployGroup
+  - description
+  - displayName
+  - domainName
+  - environmentPrefix
+  - evars
+    - key
+  - expireDate
+  - firewallEnabled
+  - hostname
+  - id
+  - instanceContext
+  - instanceLevel
+  - instanceTypeCode
+  - instanceTypeName
+  - instanceVersion
+  - layoutCode
+  - layoutId
+  - layoutName
+  - memory
+  - metadata
+  - name
+  - networkLevel
+  - plan
+  - ports
+  - provisionType
+  - scheduleStatus
+  - servicePassword
+  - serviceUsername
+  - sslCertId
+  - sslEnabled
+  - status
+  - statusMessage
+  - storage
+  - tags
+  - templateOutput
+  - userStatus
+- platform
+- provisionType
+- **results**
+- sequence
+- **state**
+  - iacDrift
+  - stateDate
+  - stateList - []
+    - category
+    - code
+    - contentPath
+    - errorMessage
+    - iacDrift
+    - id
+    - input
+    - name
+    - output
+    - planPath
+    - resourceVersion
+    - stateContext
+    - stateDate
+    - stateId
+    - statePath
+    - stateType
+    - status
+    - statusMessage
+    - tags
+    - workingPath
+  - stateType
+- tenant
+- tenantId
+- tenantSubdomain
+- type
+- userId
+- userInitials
+- username
+
+</</div>
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json b/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
new file mode 100644
index 0000000..f301b9e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+  "title": "Cohesity",
+  "ordinal": 381,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.html",
+  "topic_cluster": {
+    "clustering_title": "Cohesity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md b/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
new file mode 100644
index 0000000..c8e5a91
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
@@ -0,0 +1,92 @@
+# Cohesity
+
+HPE Morpheus Enterprise integrates with Cohesity for selection as a Cloud backup target for compatible Cloud types and for adding Cohesity S3 storage servers and storage buckets. HPE Morpheus Enterprise integrates with your existing Cohesity appliance, which can then be set as the default backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. To utilize storage features, integrate a Cohesity S3 storage server and then create a Cohesity S3 storage bucket.
+
+This section discusses the process for integrating Cohesity with HPE Morpheus Enterprise, setting backup options during Instance provisioning, restoring Instances from Cohesity backup, and using Cohesity S3 storage.
+
+## Adding the integration
+
+Cohesity integrations are added in the backup integrations area of the UI (Backups > Integrations). If a Cohesity integration is not an option, you must download and add the Cohesity plugin to the HPE Morpheus Enterprise appliance. For additional information on adding a plugin, including how to access the Hewlett Packard Enterprise-maintained repository which includes the Cohesity plugin, see the [plugin section](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html) of this documentation.
+
+With the Cohesity plugin installed, navigate to Backups > Integrations to add a new Cohesity integration. Click + ADD and a modal appears for creating a new Cohesity backup provider.
+
+![../../_images/createBackupProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F640EDCF-693E-49D1-8ABA-8AC090325603-high.png)
+
+Provide the following information:
+
+- **NAME:** A name for the Cohesity provider in HPE Morpheus Enterprise UI
+- **ENABLED:** When marked, the Cohesity provider will be available for use
+- **HOST:** Enter the host name
+- **CREDENTIALS:** An API key is required for authentication. Select “Local Credentials” to enter the API key directly into this modal. Select “api key” under the “New Credentials” heading to enter the API key directly into this modal and save it in a chosen secure secret store for later use. If an API key has already been stored in an integrated secret store, you may also choose it here rather than directly entering the key into this modal
+- **SECRET STORE:** Optional and only visible if you’ve opted in the CREDENTIALS field to securely store your entered API key
+- **API KEY:** Only visible if authenticating through local credentials (that is, you haven’t selected a saved API key from the CREDENTIALS field). Enter the API key
+- **VISIBILITY:** Cohesity integrations with private visibility are consumable only by the Tenant in which the integration is created
+
+When finished, click SAVE. The new Cohesity backup provider should be successfully created.
+
+## Setting the Cloud Backup Provider
+
+Now that the Cohesity backup provider is created, it can be set as the default backup provider for supported Cloud types. To set this configuration on a Cloud, navigate to the Clouds list page (Infrastructure > Clouds) and edit a compatible Cloud (✎ icon). Expand the “Advanced Options” section and locate the BACKUP PROVIDER configuration. Set the Cohesity provider as the backup provider for the Cloud and click SAVE CHANGES.
+
+![../../_images/editCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AF02E7F0-F125-4FF5-BA08-A35DEE94F1CC-high.png)
+
+## Backup Options at Provision Time
+
+With Cohesity set up as the backup provider for a Cloud (or Clouds), additional backup options are made available when provisioning to the Cloud. These configurations are made from the AUTOMATION tab of the provisioning wizard (launched by clicking + ADD from the Instance list page at Provisioning > Instances). From the AUTOMATION tab, expand the “Backups” section. The BACKUP TYPE of “Cohesity Protection Group” should be preselected. Then, make the next two configurations:
+
+- **BACKUP NAME:** A name for the backup (often named for the Instance associated with the backup)
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group.
+
+![../../_images/noPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-593744EF-D461-44D1-9839-26105B9AA42E-high.png)
+
+If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+![../../_images/yesPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0811D470-3CF2-43F5-8689-CA8820605919-high.png)
+
+Once these configurations are provided, complete the provisioning wizard and the configured backup options are applied to the new Instance.
+
+## Creating Backups for Existing Instances
+
+In addition to creating Backups at provision time, as discussed in the previous section, Cohesity backups can be configured for existing Instances. Start from the Backups list page (Backups > Backups) and click + ADD. When the CREATE BACKUP modal appears, select “Instance” from the SELECT SOURCE tab and click NEXT. From the NAME/TYPE tab use the INSTANCE field, which is a typeahead field, to search for a compatible Instance. In the NAME field, enter a name for the new Backup and click NEXT. From the INFO tab, the following configurations are made:
+
+- **BACKUP TYPE:** Cohesity Protection Group
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group. If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+On clicking COMPLETE, the new Backup is successfully created.
+
+## Restoring from Cohesity Backups
+
+To restore an Instance from a Cohesity backup, begin at the Backups list page (Backups > Backups). From the list of Backups, click on the desired backup making sure to click the Backup name and not the name of a Backup Job. On the Backup detail page, note the BACKUP ARCHIVES section. Identify the correct restore point (if more than one are available) and click ACTIONS > Restore. The Instance will be successfully restored from backup.
+
+![../../_images/backupArchives.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6CF1441A-23C0-488D-B250-83D4CE2CAA76-high.png)
+
+## Using Cohesity S3
+
+To work with Cohesity S3, start by creating a Cohesity storage server object in HPE Morpheus Enterprise. To do so, navigate to Infrastructure > Storage > Servers and click + ADD. Make the following configurations:
+
+- **NAME:** A name for the storage server object in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description field
+- **ENABLED:** When marked, the storage server object is available for consumption in HPE Morpheus Enterprise
+- **TYPE:** Cohesity S3. When this type is selected, the required configuration fields appear
+- **ENDPOINT:** The endpoint of the cluster
+- **API KEY:** A valid API key for authentication
+
+Click SAVE CHANGES and the storage server object is created.
+
+![../../_images/createStorageServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F367EF34-C8AE-4D5E-83B2-6ECA4A797481-high.png)
+
+With the storage server created, Cohesity S3 buckets may be created. Buckets are created at Infrastructure > Storage > Buckers. Click + ADD and then Cohesity S3 Bucket. On the NEW BUCKET modal, first select a Cohesity S3 storage server from the STORAGE SERVICE dropdown menu. This will preload other configuration field dropdown menus, such as STORAGE DOMAIN and QOS. From this modal, the bucket can be set as a default backup target or as a default target for Virtual Images or deployment archives. Once finished, click SAVE CHANGES
+
+![../../_images/createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FB2BEBEB-06B5-4F1A-BCD3-E72DF8E016AD-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json b/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
new file mode 100644
index 0000000..9eec03c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+  "title": "Cisco ACI",
+  "ordinal": 512,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html",
+  "topic_cluster": {
+    "clustering_title": "Cisco ACI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md b/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
new file mode 100644
index 0000000..209c7c5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
@@ -0,0 +1,86 @@
+# Cisco ACI
+
+## Overview
+
+![ACI summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E24C5FDE-8C7F-44B1-B150-0FDDAB2B18CE-high.png)
+
+Add ACI as a network and security integration. Inventory your existing ACI configurations. Create networks, bridge domains, application profiles, tenants, endpoint groups, contexts, filters and contracts. Provision instances into new endpoint groups and define security groups that apply contracts on provision.
+
+From Morpheus below can be created:
+
+- Tenants
+- ANP’s
+- EPG’s
+- Contexts
+- Bridge Domains
+- Filters
+- Contracts
+
+NOTE
+
+Morpheus to ACI Sync Job Schedule: Every 5 minutes
+
+NOTE
+
+Morpheus connects to ACI APIC over port 443
+
+## Add Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Networks  >  Integrations
+2. Select +ADD > Networking > `Cisco ACI`
+3. Populate the following: 
+
+   NAME
+   :   ACI Integration Name/Label in HPE Morpheus Enterprise
+       :   This is unique to HPE Morpheus Enterprise and not part of authentication
+
+   URL
+   :   ACI fabric url, eg `https://apicdc.company.com`
+
+   USERNAME
+   :   ACI `aaaUser` name attribute
+
+   PASSWORD
+   :   ACI `aaaUser` pwd attribute
+
+   TENANT
+   :   Populates upon authentication, tenant selection not required
+4. Select ADD NETWORK INTEGRATION
+
+## Configure Cloud Network Mode
+
+### About this task
+
+For your ACI Integration to be available during provisioning, ACI needs to be defined on a Cloud or multiple Clouds `NETWORK MODE` advanced options.
+
+### Procedure
+
+1. Select an existing VMware vCenter Cloud
+2. Select EDIT
+3. Expand the Advanced Options section
+4. Select ACI Integration in `NETWORK MODE` dropdown
+5. Select SAVE
+
+## Instance Provisioning
+
+### About this task
+
+![ACI Instance provisioning options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+Once ACI is integration to a cloud, it can be used during instance provisioning:
+
+### Procedure
+
+1. From the EPG drop down, either an existing EPG can be selected or a new one can be created. It is the same for ANP, either create a new one or choose an existing.
+2. Under ACI security consumes and provides, contracts can be searched when you enter a name. When the provisioning wizard is completed, it will provision the instance and apply the ACI options and Security. This can be viewed under the instance page, or via REST API and CLI.
+
+## Blueprint Configuration
+
+![ACI Blueprint options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+- In a Blueprint, you can define the ANP and EPG of each Tier
+- Variables can be used for EPG and ANP names.
+- This could be useful to create blueprints for dev testing to isolate from prod networks.
+- This can be hybrid based on the VMM domains in APIC.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json b/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
new file mode 100644
index 0000000..4142b26
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+  "title": "Scaling Morpheus Nodes",
+  "ordinal": 27,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html",
+  "topic_cluster": {
+    "clustering_title": "Scaling Morpheus Nodes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md b/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
new file mode 100644
index 0000000..5558479
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
@@ -0,0 +1,40 @@
+# Scaling Morpheus Nodes
+
+Morpheus App nodes can be scaled to accommodate additional load. Appliance nodes can be scaled vertically in centralized architectures, and both vertically and horizontally in distributed architectures.
+
+## Vertical Scaling
+
+In all Appliance Architectures, Application nodes can be vertically scaled at any time, however a reconfigure must be performed for additional resources to be utilized by HPE Morpheus Enterprise on a node, which will result in the `morpheus-ui` restarting on the reconfiguring node.
+
+Morpheus configures memory/ram utilization for services during the `reconfigure` process. If additional memory/ram is added to a Host or VM running the Morpheus App, the additional memory/ram will not be utilized by the Morpheus Application until a `morpheus-ctl reconfigure` command is ran and the additional memory/ram is recognized.
+
+IMPORTANT
+
+When the `morpheus-ctl reconfigure` command detects changes on available memory/ram, it will restart the `morpheus-ui` service.
+
+The impact on Availability depends on the Morpheus Appliance Architecture.
+
+- Centralized Appliances
+  :   Morpheus will be unavailable while the `morpheus-ui` restarts.
+- Distributed Appliances
+  :   Zero-down time can be achieved by Reconfiguring one App Node at a time, with proper Front-End Load Balancer configuration.
+
+## Horizontal Scaling
+
+Additional Morpheus App Nodes can be added at any time to Fully Distributed Architectures.
+
+- Configure Shared Storage paths for the new App Node(s)
+- Install, but do not run the `morpheus-ctl reconfigure` command on the new App Node(s), using the same Morpheus version as the existing Appliance nodes.
+- Copy the `morpheus.rb` from an existing App Node to the new App Node(s)
+- Ensure permissions and network configuration for the new App Node(s) to access all MySQL and Elasticsearch nodes, and the RabbitMQ VIP.
+- Ensure permissions and network configuration for all required UI services and Integrations, such as network access to ESXi hosts over 443 for Hypervisor console and/or image transfers.
+- Add associated SSL files and configuration which is not on shared storage.
+- Reconfigure the new App Node(s) via `morpheus-ctl reconfigure`
+- Verify UI startup succeeded
+- Add New App Node(s) to Front End Morpheus UI Load Balancer pool.
+
+During `morpheus-ctl reconfigure`, the new App Node(s) will validate and be configured to use the existing tiers for the UI service. Upon successful reconfigure, the Morpheus service will be available on the App Node(s) with consistent data and capabilities.
+
+NOTE
+
+No services, including `morpheus-ui`, are required to be shut down on existing nodes when adding new App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json b/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
new file mode 100644
index 0000000..a23eea6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+  "title": "Alibaba",
+  "ordinal": 387,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md b/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
new file mode 100644
index 0000000..b90a2d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
@@ -0,0 +1,157 @@
+# Alibaba
+
+## Features
+
+- Brownfield discovery
+- Instance cloning
+- Security group creation and management
+- Docker and Kubernetes provisioning and management
+- Usage tracking
+- Two-way tag sync
+
+## Supported Regions
+
+- ap-northeast-1 (亚太东北 1 (东京)
+- ap-south-1 (亚太南部 1 (孟买)
+- ap-southeast-1 (亚太东南 1 (新加坡)
+- ap-southeast-2 (亚太东南 2 (悉尼)
+- ap-southeast-3 (亚太东南 3 (吉隆坡)
+- ap-southeast-5 (亚太东南 5 (雅加达)
+- cn-beijing (华北 2)
+- cn-chengdu (西南1（成都）)
+- cn-guangzhou (华南3（广州）)
+- cn-hangzhou (华东 1)
+- cn-heyuan (华南2（河源）)
+- cn-hongkong (香港)
+- cn-huhehaote (华北 5)
+- cn-qingdao (华北 1)
+- cn-shanghai (华东 2)
+- cn-shenzhen (华南 1)
+- cn-wulanchabu (华北6（乌兰察布）)
+- cn-zhangjiakou (华北 3)
+- eu-central-1 (欧洲中部 1 (法兰克福)
+- eu-west-1 (英国（伦敦）)
+- me-east-1 (中东东部 1 (迪拜)
+- us-east-1 (美国东部 1 (弗吉尼亚)
+
+## Integrate an Alibaba Cloud with HPE Morpheus Enterprise
+
+To add a new Cloud, navigate to Infrastructure > Clouds and click + ADD. Select “Alibaba Cloud” and click NEXT. Once the “ADD CLOUD” modal appears, configure the following:
+
+- **NAME:** A friendly name for the Cloud in HPE Morpheus Enterprise
+- **CODE:** A Cloud code used to reference this Cloud in HPE Morpheus Enterprise API
+- **LOCATION:** An optional field for tracking location data related to this Cloud
+- **VISIBILITY:** Public Clouds are available to all Tenants, Private Clouds are available to one selected Tenant
+- **TENANT:** If the Cloud visibility is set to “Private”, this field determines which Tenant the Cloud is exposed to
+- **ENABLED:** When marked, the Cloud is available as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** When marked, HPE Morpheus Enterprise is the source of truth for the expected power state of Instances. HPE Morpheus Enterprise tools should be used to control power state and HPE Morpheus Enterprise will override any unexpected power states (such as if an instance were powered on or off from the Alibaba web console)
+- **CREDENTIALS:** Select Local Credentials to enter authentication credentials on this modal, Existing Credentials to choose a pre-saved credential set, or New Credentials to enter authentication credentials on this modal and save them (in Infrastructure > Trust) for other uses later
+- **ACCESS KEY:** (When Local Credentials or New Credentials are selected) A valid Access Key for an Alibaba Cloud account
+- **SECRET KEY:** (When Local Credentials or New Credentials are selected) A valid Secret Key for an Alibaba Cloud account
+- **INVENTORY:** When marked, HPE Morpheus Enterprise will automatically onboard existing instances in the Alibaba Cloud account as unmanaged servers
+- **REGION:** Select the Alibaba Cloud region to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+- **VPC:** Select the Alibaba Cloud VPC to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Following Integration
+
+After the integration has been created, HPE Morpheus Enterprise will sync existing workloads (if you’ve opted to inventory), security groups, tags, and more. Synced workloads can be viewed from Infrastructure > Compute. If Plans aren’t immediately available within a few minutes after the integration is created, navigate to the Cloud detail page (Infrastructure > Clouds > Your Integrated Alibaba Cloud), click REFRESH and click “Daily”. Shortly thereafter, the Plans should be synced and selectable at provision time. Without manually syncing the Plans, you may be unable to provision to this Cloud until it undertakes its next daily sync overnight as Plan selection is required.
+
+You’re now able to provision new Instances and Apps to the Alibaba Cloud. HPE Morpheus Enterprise includes a default catalog that includes Alibaba images which can be provisioned out of the box. Additionally, you can begin to create your own custom library of Alibaba workloads by adding Virtual Images and building out Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json b/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
new file mode 100644
index 0000000..ff425be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+  "title": "Creating Network Using the ArubaCX Integration",
+  "ordinal": 433,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Network Using the ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md b/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
new file mode 100644
index 0000000..972066f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
@@ -0,0 +1,26 @@
+# Creating Network Using the ArubaCX Integration
+
+## Prerequisites
+
+Before starting to create networks using integration, ensure that a Bare metal cloud is created with the ‘Network Mode’ set to the integration. If the Bare metal cloud already exists then ensure that ‘Network Mode’ is set to integration.
+
+## About this task
+
+Perform the following to create the network:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network.
+3. Click the Add to add a new integration.
+4. Enter the following details for the network:
+   - **Group** for the network
+   - **Network Service** specifies the Network Integration to use
+   - **Name** for the network
+   - **Gateway, DNS** information if required
+   - **CIDR** for the subnet
+   - Primary **VLAN ID** for the network
+   - Check the **Private** checkbox if a private network
+   - **VLAN trunks** for the network (optional)
+   - Choose Network Pool to be one of the IP pools configured![Create network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-68DA56E3-0840-4CA8-B10F-718312751234-high.png)
+5. Click Save Changes to create the network.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json b/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
new file mode 100644
index 0000000..2f03952
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+  "title": "Code Integrations",
+  "ordinal": 100,
+  "parent_title": "Code",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html",
+  "topic_cluster": {
+    "clustering_title": "Code Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md b/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
new file mode 100644
index 0000000..595cc13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
@@ -0,0 +1,16 @@
+# Code Integrations
+
+The Provisioning ‣ Code ‣ Integrations section is where Code Integrations, such as Git and Github Repository Integrations, and Jenkins Build Service Integrations, can be created and managed.
+
+## Role Permissions
+
+Access and capabilities for the **Integrations** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json b/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
new file mode 100644
index 0000000..428b979
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+  "title": "Backups",
+  "ordinal": 253,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md b/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
new file mode 100644
index 0000000..9cebf2b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
@@ -0,0 +1,191 @@
+# Backups
+
+The HPE Morpheus Enterprise built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from HPE Morpheus Enterprise.
+
+HPE Morpheus Enterprise also integrates with external services to automate availability with other providers.
+
+## Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See HPE Morpheus Enterprise UI [Storage Documentation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+### Global Backups Settings
+
+HPE Morpheus Enterprise Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+### Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
+
+## Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See [`Policies`](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout. Many backup job types are supported including (but not limited to):
+
+- File Backup
+- Directory Backup
+- MySQL
+- MongoDB
+- LVM Snapshot
+- LVM Image
+- LVM Migration
+- Windows Migration
+- Postgres
+- Tar Directory Backup
+- Amazon VM Snapshot
+- VMWare VM Snapshot
+- Fusion VM Snapshot
+- Xen VM Snapshot
+- Veeam VMWare VM Backup
+- Veeam Hyper-V VM Backup
+- Google VM Snapshot
+- Commvault File/Directory Backup
+- Azure VM Snapshot
+- Morpheus Appliance
+- Openstack VM Snapshot
+- DigitalOcean VM Snapshot
+- Nutanix VM Snapshot
+- Softlayer VM Snapshot
+- Hyper-V VM Snapshot
+- VMWare VM Snapshot
+- SCVMM VM Snapshot
+- UpCloud VM Snapshot
+- Bluemix VM Snapshot
+- Alibaba VM Snapshot
+- Oracle Cloud VM Snapshot
+- KVM VM Snapshot
+- Container Backup
+- VM Backup
+- Object Storage Backup
+
+## Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
+
+![../_images/backupSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A241F036-0867-4093-88ED-6F98CE2D6BD9-high.png)
+
+## Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+### Create an Instance Backup
+
+#### About this task
+
+To create Instance backup:
+
+#### Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+#### Results
+
+NOTE
+
+On VMware Cloud types, HPE Morpheus Enterprise will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so HPE Morpheus Enterprise has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json b/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
new file mode 100644
index 0000000..361592e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+  "title": "Unable to Delete Tenant",
+  "ordinal": 356,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Delete Tenant",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md b/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
new file mode 100644
index 0000000..5ba4195
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
@@ -0,0 +1,22 @@
+# Unable to Delete Tenant
+
+Problem
+:   When trying to delete a tenant, a message stating manage resources must be removed or other error occurs and the tenant is not deleted. The tenant may be stuck in a deleting status or return to OK status after delete attempt.
+
+Cause
+:   All managed resources must be removed from a tenant in order for that tenant to be deleted. This includes instances and their underlying managed vm’s
+
+Solution
+:   1. Login or impersonate that an Admin user inside the tenant
+    2. Navigate to Infrastructure > Hosts
+    3. Under Hosts and VM’s, delete any managed resources
+
+       - Uncheck `remove infrastructure` when deleting a VM to only remove it from HPE Morpheus Enterprise but not from the underlying hypervisor/cloud
+       - You must check `remove associated instances` if the VM has an associated instance
+       - If the VM no longer exists but there is still a record in HPE Morpheus Enterprise, uncheck `remove infrastructure` and check `force delete`
+    4. Once all managed resources are removed from the tenant, the tenant can then be deleted
+    5. In certain situations other components may prevent a tenant from being deleted. If you have removed all managed resources from a tenant and the tenant still cannot be deleted, please contact HPE Morpheus Enterprise support
+
+WARNING
+
+Managed resources can also be removed by deleting instances, but be aware this will delete VM’s associated with the instance from the underlying hypervisor/cloud
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.json b/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
new file mode 100644
index 0000000..ab90324
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+  "title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+  "ordinal": 353,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.md b/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
new file mode 100644
index 0000000..7b1c1ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
@@ -0,0 +1,72 @@
+# HPE Morpheus Enterprise UI not loading after upgrade or reconfigure
+
+Problem:
+:   The HPE Morpheus Enterprise ui does not load after performing an upgrade.
+
+Common Causes:
+:   1. The morpheus-ui has not finished loading
+    2. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+    3. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+Solutions:
+:   1. The morpheus-ui has not finished loading.
+
+       An easy way to see when the ui is finished loading and running is to tail the ui current file and look for the morpheus logo with version and start time
+
+       ```
+       ```
+       morpheus-ctl tail morpheus-ui
+       ```
+       ```
+
+    NOTE
+
+    After running morpheus-ctl start morpheus-ui, the HPE Morpheus Enterprise ui takes around 3 minutes to run depending on hardware.
+
+    1. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+
+       The morpheus ui must be stopped prior to running morpheus-ctl reconfigure when upgrading. Sometimes running morpheus-ctl stop morpheus-ui will timeout and the ui is not actually stopped. If stopping the ui does timeout, run morpheus-ctl kill morpheus-ui prior to reconfigure, and be sure to run morpheus-ctl start morpheus-ui after reconfigure is completed. If you ran a reconfigure before stopping the ui, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl reconfigure  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
+
+       Wait for the ui to come up.
+    2. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+       If the ui fails to start and you see the error `Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by morpheus` it likely means morpheus was forced to restart or shut down while the database schema was being migrated during an upgrade, and the lock was not released. To release the lock, you will need to run a mysql query. You will need to install mysql-client on the morpheus appliance, and grab the password for morpheus mysql. The username and db name are both morpheus. The password to login to mysql can be found in the application.yml file located at `/opt/morpheus/conf/application.yml` Then run the following:
+
+       ```
+       ```
+       mysql -u morpheus -p -h 127.0.0.1 morpheus
+       ```
+       ```
+
+       At the prompt, enter the mysql password from the application.yml Then run:
+
+       ```
+       ```
+       DELETE FROM DATABASECHANGELOGLOCK;
+       ```
+       ```
+
+       Then restart morpheus-ui:
+
+       ```
+       ```
+       sudo morpheus-ctl restart morpheus-ui
+       ```
+       ```
+
+       If the restart timesout, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json b/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
new file mode 100644
index 0000000..3329433
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+  "title": "Images",
+  "ordinal": 252,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html",
+  "topic_cluster": {
+    "clustering_title": "Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md b/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
new file mode 100644
index 0000000..25b9a1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
@@ -0,0 +1,69 @@
+# Images
+
+Morpheus provides Images for ESXi, CentOS, Ubuntu and XenServer, and user can add their own Images.
+
+## Add Images
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab then click the Add Image button.
+4. From the Upload Virtual Image Wizard input the following information 
+
+   Name
+   :   Name of the Image.
+
+   Operating System
+   :   List of available operating systems.
+
+   Storage Provider
+   :   List of available storage providers.
+
+   Image Path
+   :   Path of the image.
+
+   Visibility
+   :   Private or Public
+
+   Account
+   :   List of accounts to allow permission to this image.
+5. Save Changes
+
+## Edit Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab
+4. Click the actions drop down and select edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
+
+## Convert Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Convert.
+
+## Download Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Download.
+
+## Remove Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Image tab.
+4. Click the Actions drop and select Remove.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json b/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
new file mode 100644
index 0000000..4895efd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+  "title": "Utilization: Utilization vs Cost",
+  "ordinal": 65,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html",
+  "topic_cluster": {
+    "clustering_title": "Utilization: Utilization vs Cost",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md b/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
new file mode 100644
index 0000000..eae4859
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
@@ -0,0 +1,30 @@
+# Utilization: Utilization vs Cost
+
+![../_images/8utilization.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-98D09465-88F7-420B-AEF8-80393CC3A8B7-high.png)
+
+The Utilization vs Cost dashboard is designed to reveal workloads which are underutilized (expensive and seldom-used) and which are very cost-efficient (inexpensive and frequently-used). Administrators can filter the workloads considered by the dashboard through the use of filters and potentially identify areas of cost savings by decommissioning seldom-used machines.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matching search terms)
+- Time period (Current, one-day average, one-week average, one-month average, three-month average, six-month average, or one-year average)
+- Type (virtual machines, hosts, or bare metal)
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **COUNT:** The total number of workloads that meet dashboard filters
+- **CLOUD COUNT:** The total number of Clouds represented by the selected workloads
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **AVERAGE UTILIZATION:** The computed average utilization figure for all workloads selected by dashboard filters
+
+## Utilization List
+
+In addition to the totals and graph displayed, two workload lists are given showing the least utilized workloads by cost (lowest utilization per cost dollar) and the least utilized workloads overall (lowest utilization overall). These workloads are listed with links to the Instance or server detail pages, along with other details related to price and resource utilization.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..863be5f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 521,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..1b84555
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,272 @@
+# HPE Alletra MP Storage
+
+## Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
+
+## Add HPE Alletra MP Storage
+
+### About this task
+
+The first step is to create a storage server in HPE Morpheus Enterprise. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in HPE Morpheus Enterprise
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
+
+## Create Datastore
+
+### About this task
+
+Add a Datastore to the Storage Server.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+### Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
+
+## Create Instance
+
+### About this task
+
+Create an Instance with the Datastore.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. In the Instances tab, Click the + ADD button
+3. From the ADD INSTANCE wizard input the following: 
+
+   - From the TYPE section: Select “HVM”
+   - Click NEXT
+
+     ![../../_images/create-instance-type.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - From the GROUP tab, input the following:
+
+     GROUP:
+     :   Select the Group for the Instance
+
+     CLOUD:
+     :   Select the Cloud for the Instance
+
+     NAME:
+     :   Name for the Instance in HPE Morpheus Enterprise
+   - Click NEXT
+
+     ![../../_images/create-instance-group.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - From the CONFIGURE tab, input the following:
+
+     LAYOUT:
+     :   Select the Layout for the Instance
+
+     PLAN:
+     :   Select the Plan for the Instance
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section
+
+     NETWORK:
+     :   Add Networks to the Instance
+
+     IMAGE:
+     :   Select the Image for the Instance
+
+     HOST:
+     :   Select the cluster host for the Instance
+
+     Other configurations may be added as needed.
+
+     ![../../_images/create-instance-configure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click NEXT
+   - Add Automation Tasks, if needed
+   - Click NEXT
+   - Review the Instance configuration
+   - Click COMPLETE![../../_images/create-instance-review.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+### Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
+
+## Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see [Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-9C460D6B-1616-47E0-9FF7-7AD7DD4ADDE3).
+
+### Viewing the Summary page
+
+The Summary tab displays system information, the capacity utilization of the system, and the number of ransomwares detected.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time that the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomwares detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
+
+### Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
+
+### Volumes tab
+
+#### Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
+
+#### Editing volumes
+
+##### About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+##### Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see [Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-C292527A-7464-4C79-9C27-A51681D8A157).
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json b/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
new file mode 100644
index 0000000..9153070
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+  "title": "Packages",
+  "ordinal": 311,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md b/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
new file mode 100644
index 0000000..5b58eca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
@@ -0,0 +1,130 @@
+# Packages
+
+## Overview
+
+Packages are code files used to define HPE Morpheus Enterprise resources, which can then be uploaded and used in any HPE Morpheus Enterprise appliance they may be needed in. HPE Morpheus Enterprise packages (.morpkg, .mpkg, or .mopkg) are added in the Administration > Integrations > Packages section of the UI. HPE Morpheus Enterprise packages contain Library and automation objects, such as Instance Types, Layouts, Node Types, Tasks, Spec Temples and Cluster Layouts. Following upload of a valid package, the defined HPE Morpheus Enterprise resources are immediately available for use in the appliance.
+
+The addition of `/administration/packages` is primarily targeted for uploading future HPE Morpheus Enterprise-provided packages, however users can create, distribute and/or import custom HPE Morpheus Enterprise packages too. This section goes over the process for writing and preparing packages for upload to a HPE Morpheus Enterprise appliance.
+
+## Role Permissions
+
+Access and capabilities for the **Packages** section is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Plugins`
+:   - None: Cannot access Admin: Plugins section
+    - Full: Access to Admin: Plugins and ability to upload HPE Morpheus Enterprise packages (`.morpkg`, `.mpkg`, or `.mopkg`)
+
+## Getting Started
+
+Packages consist of two primary parts, a `.json` manifest file (which sets some metadata about the package) and one or more `.scribe` files which define the resources to be added. These files are zipped and imported into HPE Morpheus Enterprise as one file (`.morpkg`, `.mpkg`, or `.mopkg`). Scribe files are written in HCL (Hashicorp Configuration Language) and follow referenced resource naming. In the next section, we will define the required attributes for both the `.json` manifest and the scribe files with examples.
+
+When uploading packages to HPE Morpheus Enterprise, keep in mind that the same packages can be reinstalled as many times as desired. When the same package is reinstalled, any local changes to those resources made in the HPE Morpheus Enterprise appliance will be overwritten. For example, if a Task has been created by package and changes are made locally to the Task config within HPE Morpheus Enterprise, subsequent uploads of the packages would overwrite those changes. A better method for making changes to package-sourced resources would be to update the package code, increase the version number, and upload the package once again. This ensures important local changes would not be overwritten by subsequent uploads. There is no warning given in the UI, changes are simply overwritten without notice.
+
+Additionally, it’s worth noting that while packages can be deleted (🗑 icon on the packages detail page), you will simply delete the package from the list. HPE Morpheus Enterprise will show a helpful list of resources added with the package if cleanup is desired but will not delete them.
+
+## Creating Packages
+
+As noted in the last section, a package consists of a `.json` manifest file and any number of `.scribe` files. We’ll first look at the manifest file, its purpose, and attributes that must be included in the JSON map.
+
+A typical package manifest looks like this:
+
+```
+```
+{  
+    "type": "scribe",  
+    "name": "morpheus-ubuntu-22.04-vmware",  
+    "code": "morpheus-ubuntu-22.04-vmware",  
+    "organization": "morpheus",  
+    "version": "20240415"  
+}
+```
+```
+
+The manifest includes each of the following attributes:
+
+- **TYPE:** Tells HPE Morpheus Enterprise to process all included files with the package as scribe files. Currently, this is the only supported type
+- **NAME:** This is the name for the package that will appear in HPE Morpheus Enterprise UI. The example manifest above came from a package that adds resources for an Ubuntu 22.04 library item to HPE Morpheus Enterprise, and is named to indicate that
+- **CODE:** Not visible in UI but exists for referencing the package via HPE Morpheus Enterprise API
+- **ORGANIZATION:** Appears only in the database but can be exposed via HPE Morpheus Enterprise API
+- **VERSION:** Listed in HPE Morpheus Enterprise UI and is useful for tracking changes over time to package-sourced resources
+
+Scribe files are quite a bit more complicated and have not yet been fully documented publicly. Nevertheless, we can show a couple examples here and give strategies for extracting additional examples from your own environment. Certain resources will require reference to other resources included with the scribe file. Here’s a simple scribe file creating a shell script-type “Hello World” Task:
+
+```
+```
+resource "task" "HelloWorld" {  
+  name = "HelloWorld"  
+  uuid = "2c2306e0-3b30-4886-b8a3-d1362c9b9490"  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  executeTarget = "resource"  
+  labels = [ "export" ]  
+  lastUpdated = "2024-04-19T19:18:40.000Z"  
+  options = [  
+    { optionType = { code = "shell.sudo" }, value = "on" },  
+    {  
+      content = { uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0" }  
+      optionType = { code = "script" }  
+    }  
+  ]  
+  taskType = { code = "script" }  
+}  
+resource "file-content" "ff5de589-75da-48ec-ba66-5fe5905397b0" {  
+  uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0"  
+  content = "echo \"Hello World\""  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  lastUpdated = "2024-04-19T19:15:47.000Z"  
+}
+```
+```
+
+In this case, the Task config was written locally in the Add/Edit Task modal within HPE Morpheus Enterprise rather than sourced from elsewhere (such as a Github repository). The Task content itself is a distinct resource and is referenced in the Task resource by UUID. Outside resources can also be referenced by HCL referenced resource naming such as in the following example where a `workload-type` resource references a `virtual-image` resource:
+
+```
+```
+resource "virtual-image" "vmware_vsphere_image_morpheus_almalinux_9_20240324" {  
+  code = "vmware_vsphere_image_morpheus_almalinux_9_20240324"  
+  category = "vmware.vsphere.image.morpheus.almalinux"  
+  name = "Morpheus AlmaLinux 9 XX-DATE-XX"  
+  imageType = "vmdk"  
+  remotePath = "https://s3-us-west-1.amazonaws.com/morpheus-images/vmware/20240324/almalinux-9/morpheus-almalinux-9-x86_64-20240324.ovf"  
+  imagePath = "vmware/20240324/almalinux-9"  
+  isCloudInit = true  
+  systemImage = true  
+  installAgent = true  
+  osType {  
+    code = "almalinux.9.64"  
+  }  
+  zoneType = "vmware"  
+}  
+resource "workload-type" "vmware_almalinux_9" {  
+  code = "vmware-almalinux-9"  
+  shortName = "almalinux"  
+  name = "AlmaLinux 9"  
+  ports = [22]  
+  containerVersion = "9"  
+  entryPoint = ""  
+  mountLogs = "/var/log"  
+  statTypeCode = "vm"  
+  logTypeCode = "vm"  
+  showServerLogs = true  
+  category = "almalinux"  
+  cloneType = "almalinux"  
+  priorityOrder = 0  
+  serverType = "vm"  
+  providerType = "vmware"  
+  containerPorts = [{code = "almalinux.22"}]  
+  actions = [{code = "generic-remove-node"}]  
+  checkTypeCode = "containerCheck"  
+  virtualImage = virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324  
+  provisionType = "vmware"  
+  backupType = "vmwareSnapshot"
+```
+```
+
+The specific virtual image is referenced as `virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324`.
+
+To go further, you can generate additional examples from your own environments. Use the [Import/Export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html#import-and-export) feature built into HPE Morpheus Enterprise and export your created resources into integrated Git repositories. When viewing the results in your repositories, you’ll see the resources are exported as scribe files.
+
+## Preparing and Uploading Packages
+
+To prepare the package, ensure the manifest and scribe files are gathered into one directory. You’ll then need to zip the contents of that directory with a valid extension (`.morpkg`, `.mpkg`, or `.mopkg`). In Linux, from outside the directory, you can use: `zip -j <package-name>.mpkg <directory-name>/*`. The package is now ready to be uploaded. Navigate to Administration > Integrations > Packages on any appliance and use the file picker tool to upload your new package file.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json b/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
new file mode 100644
index 0000000..e17bd93
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+  "title": "Storage Considerations",
+  "ordinal": 5,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md b/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
new file mode 100644
index 0000000..f5cb6e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
@@ -0,0 +1,47 @@
+# Storage Considerations
+
+Upon initial installation HPE Morpheus Enterprise takes up less than 10 GB of space, however HPE Morpheus Enterprise Services, Virtual Images, Backups, Logs, stats, and user-uploaded and imported data require adequate space on the HPE Morpheus Enterprise Appliance(s) based on appliance configuration and activity. HPE Morpheus Enterprise recommends at least 200 GB as a general figure to start from but storage needs will vary dramatically based on each specific use case. In some cases, significantly more space will be needed.
+
+IMPORTANT
+
+It is the customer’s responsibility to ensure adequate storage space per configuration and use case. The appliance should be properly monitored to ensure it does not run low on disk space.
+
+## Default Paths
+
+`/opt/morpheus`
+:   Morpheus Application and Services Files
+
+`/var/opt/morpheus`
+:   User, Application and Services Data, including default config Opensearch, RabbitMQ and Database data, default Virtual Image path, and working directory for Backups
+
+`/var/opt/morpheus/morpheus-ui` (HA Installations Only)
+:   In an HA Installation, a NFS share is required and mounted to this location. Virtual Images, Plugins, and other shared files are stored at this path to be accessible for all nodes
+
+`/home`
+:   Morpheus service account home data, such as configuration files
+
+`/var/log`
+:   Morpheus Service logs
+
+`/tmp`
+:   Storage for any temp files created by Morpheus or the operating system
+
+## Images
+
+Virtual Images can be uploaded to HPE Morpheus Enterprise Storage Providers for use across Clouds. By default when no Storage Provider has been added, images will write to `/var/opt/morpheus/morpheus-ui/vms`. Please ensure adequate space when uploading Images using local file paths.
+
+## Backups
+
+HPE Morpheus Enterprise can offload snapshots when performing backups to local or other Storage Providers. By default when no Storage Provider has been added, backups will write to `/var/opt/morpheus/bitcan/backups/`. When using none NFS Storage providers, the backup file(s) must be written to `/var/opt/morpheus/bitcan/working/` before they can be zipped, sent to the destination Storage provider such as S3, and removed from `/var/opt/morpheus/bitcan/working/`. Please ensure adequate space in `/var/opt/morpheus/bitcan/` when offloading Backups.
+
+NOTE
+
+The backup /working and /backups paths are configurable in morpheus.rb with bitcan[‘working\_directory’] = ‘$path’ and bitcan[‘backup\_directory’] = ‘/tmp’
+
+## VM Logs and Stats
+
+When using HPE Morpheus Enterprise with a locally-installed Elasticsearch configuration, VM, Container, Host and Appliance logs and stats are are stored in Elasticsearch. Please ensure adequate space in `/var`, specifically `/var/opt/morpheus/elasticsearch` in relation to the number of Instances reporting logs, log frequency, and log retention count. With partition space at 85% filled or higher (by default), Elasticsearch will enter an unhealthy state and the HPE Morpheus Enterprise appliance will not function properly.
+
+## HPE Morpheus Enterprise Services Logs
+
+Logs for services local to the HPE Morpheus Enterprise Appliance, such as the Morpheus UI, elasticsearch, rabbitmq, mysql, nginx and guacd are written to `/var/log/morpheus/`. Current logs are rotated nightly, zipped, and files older than 30 days are automatically removed. Misconfigured services, ports and permissions can cause excessive log file sizes.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json b/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
new file mode 100644
index 0000000..274915d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+  "title": "Terraform Blueprints",
+  "ordinal": 137,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md b/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
new file mode 100644
index 0000000..eca7c23
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
@@ -0,0 +1,42 @@
+# Terraform Blueprints
+
+Terraform Blueprints are one way that Terraform can be integrated and leveraged with HPE Morpheus Enterprise, with the other being the HPE Morpheus Enterprise Terraform provider which is not discussed in this section. HPE Morpheus Enterprise and Terraform are complimentary technologies which together can increase efficiency and simplify automation across cloud environments. For more on this relationship, see our [whitepaper](https://www2.morpheusdata.com/Morpheus-and-Terraform) on how HPE Morpheus Enterprise and Terraform are better together.
+
+Currently, HPE Morpheus Enterprise supports provisioning Apps based on Terraform Blueprints to VMware, Amazon, Azure, and Oracle Clouds with additional Cloud support coming in future releases. On first attempt to provision a Terraform App, HPE Morpheus Enterprise will automatically install Terraform. It is possible in some operating system configurations for this automated installation process to fail, requiring you to install Terraform manually. If needed, manual installation instructions and guidance are provided [here](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-installation).
+
+To create a new Terraform Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Terraform. NEXT
+
+![../../../_images/new_blueprint.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-65A40826-21ED-4A71-83F9-0951FA0B62B7-high.png)
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The Terraform Configuration section is where the Terraform template file (.tf) is added or linked to the Blueprint. Using a Config Type of “Terraform (.tf)” or “Terraform JSON (.tf.json)”, you can write or paste your configuration directly into the new Blueprint. Alternatively, you can pull in config files from an integrated Git repository using the “Git Repository” Config type.
+
+In the Terraform Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “Terraform (.tf)” or “Terraform JSON (.tf.json)” to create or paste configuration directly into the new Blueprint
+- **CONFIG:** Enter your configuration here
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section or HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+In the Terraform Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section of HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+Once finished, click COMPLETE.
+
+Your new Terraform Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json b/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
new file mode 100644
index 0000000..9dbfce6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+  "title": "Cancelling Workflow Tasks",
+  "ordinal": 117,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html",
+  "topic_cluster": {
+    "clustering_title": "Cancelling Workflow Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md b/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
new file mode 100644
index 0000000..eea23ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
@@ -0,0 +1,11 @@
+# Cancelling Workflow Tasks
+
+When a Workflow is running, HPE Morpheus Enterprise offers the capability of cancelling a Task and stopping any subsequent Tasks from starting. When viewed later in History or Executions, this leaves the Task and Workflow in a cancelled state. This is useful if you have a very long-running Task that you know will fail and wish to cancel or if you want to prevent a “retryable” Task from running again.
+
+To cancel a Workflow, open the execution. Within the running Task will be a cancel button, click the button to interrupt the Workflow. Once cancelled, see that the Workflow and Task are now considered to be in a cancelled state which is shown in the UI. At this point the cancel button becomes a retry button and the Task could be resumed if desired.
+
+NOTE
+
+Cancelling a Task doesn’t actually interrupt the process already running on the workloads themselves. It simply interrupts the Workflow and stops it from continuing. Behind the scenes, HPE Morpheus Enterprise allows the running process to complete or time out rather than risk corrupting data with a non-graceful interrupt.
+
+![../../_images/cancelTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-47300BA8-9B05-428D-835A-1975B04DE84E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json b/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
new file mode 100644
index 0000000..86aaf37
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+  "title": "Provisioning Workflow Execution Phases",
+  "ordinal": 113,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Workflow Execution Phases",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md b/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
new file mode 100644
index 0000000..f1ee446
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
@@ -0,0 +1,18 @@
+# Provisioning Workflow Execution Phases
+
+| Phase | Description | Usage Example | Notes |
+| --- | --- | --- | --- |
+| Configuration | Tasks are run prior to initial calls to the specified cloud API to initiate provisioning | Call to an external platform to dynamically generate a hostname prior to kicking off provisioning or dynamically altering configuration of a Catalog Item prior to provisioning |  |
+| Price | Price Phase Tasks are only invoked when the Workflow is tied to a Layout. Like the Configuration Phase, these Tasks are run prior to any calls made to the target Cloud API and allow pricing data to be overridden for the Workload being provisioned. A “spec” variable containing Instance config is passed into the Task and a specific return payload is expected in order to work properly. Any other pricing (such as on the Service Plan) is overridden. See the section below for a detailed example of this Phase being used. | An MSP customer calling out to a custom pricing API to deliver Instance pricing to their own customers. | See the section below on Price Phase implementation for a detailed setup example. |
+| Pre Provision | For VMs, Tasks are run after the VM is running and prior to any Tasks in the Provision phase. For containers, Tasks in this phase are run on the Docker host and prior to `docker run` | Prepare a Docker host to run containers | Pre Provision can be used for a Blueprint so it is added before a script which is set at the Provision phase executes. Pre Provision for scripts is mainly for Docker as you can execute on the host before the container is running. |
+| Provision | Like pre‐provision, Tasks for VMs are run after the VM is running. For containers, these Tasks are run on the containers once they are running on the host. For many users, this is the most commonly‐used phase. | Join the server to a domain | Tasks included with in the Provision phase are considered to be vital to the health of the Instance. If a Task in the Provision phase fails, the Workflow will fail and the Instance provisioning will also fail. Tasks not considered to be vital to the existence of the Instance should go in the Post Provision phase where their failure will not constitute failure of the Instance. |
+| Post Provision | Tasks are run after the entire provisioning process has completed | Disable UAC or Windows Firewall on a Windows box or join Active Directory | When adding a node to an Instance, Tasks in this phase will be run on all nodes in the Instance after the new node is provisioned. This is because Post Provision operations may need to affect all nodes, such as when joining a new node to a cluster. Tasks in Pre Provision and Provision phases would only be run on the new node in this scenario. |
+| Start Service | Tasks in this phase are intended to start the service associated with the Instance type. | Include a script to start the service associated with the Instance (such as MySQL) which will execute when the Start Service action is selected from the Instance detail page | Start services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Stop Service | Tasks in this phase intended to stop the service associated with the Instance type. | Include a script to stop the service associated with the Instance (such as MySQL) which will execute when the Stop Service action is selected from the Instance detail page | Stop services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Pre Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, prior to the deploy taking place. | Extract files from a deploy folder and move them to their final positions prior to deploy | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, after the deploy has completed | Update configuration files or inject connection details from the environment at completion of the deploy process | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Reconfigure | Tasks in this phase are run when the reconfigure action is made against an Instance or host | Rescan or restart the Instance after a disk is added |  |
+| Teardown | Tasks are run during VM or container destroy | Remove Active Directory objects prior to tearing down the Instance |  |
+| Scale Down | Tasks are run when a node is removed from an Instance. This does not apply to Clusters when a worker node is removed. |  |  |
+| Shutdown | Tasks are run immediately before the target is shutdown | Send an update on Instance power state to a CMDB |  |
+| Startup | Tasks are run immediately before the target is started | Send an update on Instance power state to a CMDB |  |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json b/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
new file mode 100644
index 0000000..8cdb917
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+  "title": "VDI Pools",
+  "ordinal": 271,
+  "parent_title": "Tools",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html",
+  "topic_cluster": {
+    "clustering_title": "VDI Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md b/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
new file mode 100644
index 0000000..ec68f5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
@@ -0,0 +1,383 @@
+# VDI Pools
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json b/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
new file mode 100644
index 0000000..9532aef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+  "title": "Workflows",
+  "ordinal": 112,
+  "parent_title": "Automation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html",
+  "topic_cluster": {
+    "clustering_title": "Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md b/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
new file mode 100644
index 0000000..63b2533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
@@ -0,0 +1,17 @@
+# Workflows
+
+Workflows are groups of Tasks, which are described in detail in the preceding section. Operational Workflows can be run on-demand against an existing Instance or server from the Actions menu on the Instance or server detail page. Additionally, they can be scheduled to run on a recurring basis through Morpheus Jobs (Provisioning > Jobs).
+
+Provisioning Workflows are associated with Instances at provision time (in the Automation tab of the Add Instance wizard) or after provisioning through the Actions menu on the Instance detail page. Provisioning Workflows assign Tasks to various stages of the Instance lifecycle, such as Provision, Post Provision, and Teardown. When the Instance reaches a given stage, the appropriate Tasks are run. Task results and output can be viewed from the History tab of the Instance or server detail page.
+
+**Subtopics**  
+
+- **[Provisioning Workflow Execution Phases](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html)**
+- **[Add Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html)**
+- **[Retrying Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html)**
+- **[Cancelling Workflow Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html)**
+- **[Price Phase Task Utilization](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html)**
+- **[Nesting Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html)**
+- **[Edit Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html)**
+- **[Delete Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json b/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
new file mode 100644
index 0000000..9836810
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+  "title": "Library Integrations",
+  "ordinal": 164,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Library Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md b/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
new file mode 100644
index 0000000..fbfcc38
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
@@ -0,0 +1,3 @@
+# Library Integrations
+
+The integrations section within HPE Morpheus Enterprise Library lists existing integrations and allows for the creation of new integrations which are related to automation technologies. A complete list of integrated third party technologies is available in the Administration section (Administration > Integrations). More detailed information about each HPE Morpheus Enterprise integration with third party technologies is included in our [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) section.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json b/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
new file mode 100644
index 0000000..c8afc81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+  "title": "Roles",
+  "ordinal": 275,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md b/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
new file mode 100644
index 0000000..4d42246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
@@ -0,0 +1,28 @@
+# Roles
+
+There are two Role types in HPE Morpheus Enterprise, Tenant Roles and User Roles. Understanding these Role types is key to effectively administering Role permissions in HPE Morpheus Enterprise. These two Role types are discussed in greater detail in this section.
+
+## Tenant Roles
+
+Tenant Roles set the maximum permission levels for Users in the Tenant. User Role permissions will not exceed the permissions of the Tenant Role.
+
+- Tenant Roles set the maximum permissions for a Tenant
+- User Roles in a Tenant cannot exceed the permissions of the Tenant Role
+- A Tenant Role can be assigned to one or multiple Tenants
+- Tenant Roles determine Cloud access for the child Tenant such that all Clouds in the parent Tenant which have visibility set to Public will show as options in the Tenant Role Cloud Access tab
+- Only parent Tenant Clouds given access in the Tenant Role will be accessible in the Subtenant
+
+IMPORTANT
+
+Tenant Roles cap permissions on all Subtenant User Roles. User Roles can be created in the Subtenant with lesser permissions than the Tenant Role allows. Tenant Roles are designed for a parent Tenant Admin to set max permissions for the Subtenant, and a child Tenant Admin to configure User Roles inside the Tenant.
+
+## User Roles
+
+User Roles determine feature, Group, and Instance Type access for all Users. In a multi-Tenant environment, there are two types of User Roles: Single-Tenant User Roles and Multi-Tenant User Roles.
+
+- **Single-Tenant User Roles:** These exist solely in the Tenant they are created in
+- **Multi-Tenant User Roles:** Parent Tenants can create Multi-Tenant User Roles. These Roles are automatically seeded into child Tenants and can be assigned to Users within that Tenant. Changes to Multi-Tenant User Roles made in the parent Tenant are propagated to all children. However, once a Multi-Tenant User Role is edited inside the child Tenant, it is no longer linked to the Multi-Tenant User Role and becomes its own unique single-Tenant Role. It will no longer receive propagated changes.
+
+NOTE
+
+Multi-Tenant User Roles are intended to make Subtenant User Role creation easier, so parent Tenant administrators do not have to re-create the same base Subtenant Users Roles for every Subtenant. Multi-Tenant User Roles are not a single Role across Tenants, but more like a template that creates new Subtenant User Roles that can then be managed in the Sub Tenant.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json b/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
new file mode 100644
index 0000000..117872b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+  "title": "Software Licenses",
+  "ordinal": 328,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html",
+  "topic_cluster": {
+    "clustering_title": "Software Licenses",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md b/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
new file mode 100644
index 0000000..3bb018e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
@@ -0,0 +1,53 @@
+# Software Licenses
+
+## Overview
+
+The License section is for automating the application of Licenses to Instances while provisioning. Licenses can be added to HPE Morpheus Enterprise and then attached to images. HPE Morpheus Enterprise will then apply the license to Instances provisioned using the images with license attached. Licenses can be configured for single or multiple Tenants.
+
+### Creating Licenses
+
+#### Procedure
+
+1. Select + Create License
+2. In the New License modal, enter the following: 
+
+   - License Type
+     :   Windows
+   - Name
+     :   Name of the License in HPE Morpheus Enterprise
+   - License Key
+     :   Enter the License Key
+   - Org Name
+     :   The Organization Name (if applicable) related to the license key
+   - Full Name
+     :   The Full Name (if applicable) related to the license key
+   - Version
+     :   The License Version
+   - Copies
+     :   The Number of copies available on the License
+   - Description
+     :   License description displayed in the Licenses list in HPE Morpheus Enterprise, helpful for identifying the License after creation
+   - Virtual Images
+     :   Search for existing Virtual Images by name and select to attach the image to the license.
+         :   NOTE
+
+             Virtual Images are synced from Clouds or added in the Library > Virtual Images section.
+   - Tenant Permissions
+     :   Search for and select the Tenant(s) the License will be available for. Multiple Tenants can be added.
+3. Save Changes
+
+### Provisioning with Licenses
+
+When a Virtual Image is added to a license, HPE Morpheus Enterprise will automatically apply the License to Instances configured with the Virtual Image during provisioning, including Instance Types with a Node Type that is configured with the Virtual Image, or if the image is selected when using generic Cloud Instances types (VMware, AWS, Nutanix, Openstack etc). Virtual Images can be removed from a License by editing the License.
+
+### Managing Licenses
+
+Created Licenses details are displayed in the License page, including the number of copies applied per License, the Tenants added to the License, and the Virtual Images attached to the License.
+
+The Name, Version, Copies, Description, Virtual Images and Tenant Permissions are editable but selecting the Actions dropdown on a License.
+
+NOTE
+
+License Types, Keys, Org Names and Full Names are not editable after a license has been created.
+
+License can also be removed using the Actions dropdown on a License.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json b/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
new file mode 100644
index 0000000..a6c83b3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+  "title": "Add Amazon ALB load balancer",
+  "ordinal": 491,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ALB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md b/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
new file mode 100644
index 0000000..25da5d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
@@ -0,0 +1,33 @@
+# Add Amazon ALB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ALB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-81281149-FB28-4485-B1B1-957E0FCE24AE-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json b/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
new file mode 100644
index 0000000..c365867
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+  "title": "Load Balancers",
+  "ordinal": 224,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md b/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
new file mode 100644
index 0000000..87c1dda
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
@@ -0,0 +1,9 @@
+# Load Balancers
+
+Infrastructure  >  Load Balancers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html)**
+- **[Orchestrating Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json b/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
new file mode 100644
index 0000000..cbf669e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+  "title": "Infrastructure",
+  "ordinal": 167,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md b/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
new file mode 100644
index 0000000..df9da42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
@@ -0,0 +1,15 @@
+# Infrastructure
+
+The heart of HPE Morpheus Enterprise is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html)**
+- **[Boot](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json b/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
new file mode 100644
index 0000000..9d110a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+  "title": "Prerequisites",
+  "ordinal": 247,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md b/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
new file mode 100644
index 0000000..a78c45a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
@@ -0,0 +1,39 @@
+# Prerequisites
+
+In order to work with HPE Morpheus Enterprise bare metal PXE boot capabilities, some initial setup configuration is required. First, on the HPE Morpheus Enterprise server, if you have a firewall enabled, make sure port 69 is open for TFTP. HPE Morpheus Enterprise actually uses port 6969 and during installation a redirect should have been set. To check this, SSH onto the Morpheus server and run the following:
+
+```
+```
+iptables -t nat -L -n -v
+```
+```
+
+If the redirect is still properly, the response should include the following:
+
+```
+```
+Chain PREROUTING (policy ACCEPT 69 packets, 9767 bytes)  
+pkts bytes target   prot opt in out source     destination  
+0     0 REDIRECT udp  --  *  *   0.0.0.0/0  0.0.0.0/0        udp dpt:69 redir ports 6969  
+0     0 DNAT     tcp  --  *  *   0.0.0.0/0  169.254.169.254  tcp dpt:80 to:192.168.1.156
+```
+```
+
+Next, in HPE Morpheus Enterprise, set a default PXE root password. This password is set in Administration > Settings > Provisioning. With the default root password set, set up the redirect on the DHCP server. In addition to the DNS and Gateway settings, add Boot Server Host Name which will be the name of the HPE Morpheus Enterprise Server and Bootfile Name which should be set to `pxelinux.0`. If you are using a Linux-based DHCP server, for example on CentOS, the dhcpd.conf configuration will look something like the following:
+
+```
+```
+allow booting;  
+allow bootp;  
+option option-128 code 128 = string;  
+option option-129 code 129 = text;  
+next-server xx.xx.xx.xx;  
+filename "pxelinux.0";
+```
+```
+
+NOTE
+
+Replace the dummy IP address in the example dhcpd.conf file above with your HPE Morpheus Enterprise appliance IP address.
+
+Once you have done this, when you boot a PXE-enabled machine on the network, it will be told to access the HPE Morpheus Enterprise server and request the `pxelinux.0` file. It will do this on port 69, the default for TFTP and will be redirected to 6969 once it hits the HPE Morpheus Enterprise server. If successful you will see the “HPE Morpheus Enterprise PXE Server” menu when you boot a server. This is the default menu defined in HPE Morpheus Enterprise and supports the shipped PXE images supplied with the product. By selecting any of the choices from the “HPE Morpheus Enterprise PXE Server menu”, the install files should be downloaded and the server configured as per the supplied kickstart files. At this point, back on the HPE Morpheus Enterprise appliance, you should see the MAC address for the new server appear in the “Discovered MAC Addresses” tab of the Infrastructure > Boot page.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..15e64bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 267,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json b/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
new file mode 100644
index 0000000..20a71c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+  "title": "Create a Single Tenant User Role",
+  "ordinal": 302,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html",
+  "topic_cluster": {
+    "clustering_title": "Create a Single Tenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md b/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
new file mode 100644
index 0000000..0359ccd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
@@ -0,0 +1,15 @@
+# Create a Single Tenant User Role
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Leave the “Multi-tenant Role” checkbox blank.
+6. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+7. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..94774be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 215,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..8cc514f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,13 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Floating IPs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E_2.html)**
+- **[Security Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json b/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
new file mode 100644
index 0000000..fec2900
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+  "title": "ITSM",
+  "ordinal": 487,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html",
+  "topic_cluster": {
+    "clustering_title": "ITSM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md b/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
new file mode 100644
index 0000000..9b0de0b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
@@ -0,0 +1,7 @@
+# ITSM
+
+**Subtopics**  
+
+- **[Service Now](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html)**
+- **[Cherwell](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html)**
+- **[Remedy](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json b/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
new file mode 100644
index 0000000..c96ea9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+  "title": "Image Types",
+  "ordinal": 148,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html",
+  "topic_cluster": {
+    "clustering_title": "Image Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md b/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
new file mode 100644
index 0000000..b8e2b6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
@@ -0,0 +1,7 @@
+# Image Types
+
+HPE Morpheus Enterprise provides a vast System Image repo with pre-configured images for every Cloud. All other images are User Images. User images can be added directly to HPE Morpheus Enterprise, or automatically synced from integrated clouds. It is important to configure synced User Images for metadata, including specifying the Platform and User Credentials, prior to provisioning. Provisioning a User Image that has not been configured may result in failed provisioning.
+
+IMPORTANT
+
+Synced User Images need to be configured prior to provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json b/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
new file mode 100644
index 0000000..6254140
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+  "title": "Feature Access Permissions",
+  "ordinal": 299,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md b/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
new file mode 100644
index 0000000..f6065b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
@@ -0,0 +1,257 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in HPE Morpheus Enterprise. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering HPE Morpheus Enterprise, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where HPE Morpheus Enterprise administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within HPE Morpheus Enterprise is done on this page. On the License tab information about the current HPE Morpheus Enterprise license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default HPE Morpheus Enterprise backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within HPE Morpheus Enterprise. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of HPE Morpheus Enterprise UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of HPE Morpheus Enterprise constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for HPE Morpheus Enterprise guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the HPE Morpheus Enterprise Health and HPE Morpheus Enterprise Logs tabs. | The Health pages provide an overview of HPE Morpheus Enterprise health, notifications from integrations, and the current HPE Morpheus Enterprise‐ui log. | This permission is recommended for those responsible for administering and troubleshooting HPE Morpheus Enterprise. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between HPE Morpheus Enterprise and the identity provider. | Full permission is recommended for those responsible for integrating HPE Morpheus Enterprise with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in HPE Morpheus Enterprise. HPE Morpheus Enterprise may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where HPE Morpheus Enterprise monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend HPE Morpheus Enterprise functionality. | This permission is recommended for those responsible for extending HPE Morpheus Enterprise functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within HPE Morpheus Enterprise, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via HPE Morpheus Enterprise API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of HPE Morpheus Enterprise UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | HPE Morpheus Enterprise includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within HPE Morpheus Enterprise when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with HPE Morpheus Enterprise and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for HPE Morpheus Enterprise Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where HPE Morpheus Enterprise Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize HPE Morpheus Enterprise deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. The "Group" permission level allows Users to see only the Load Balancers tied to Groups they can access. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating HPE Morpheus Enterprise with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in HPE Morpheus Enterprise. | This permission is recommended for appliance administrators. See other sections of HPE Morpheus Enterprise documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, EfficientIP SolidServer, Microsoft DNS, PowerDNS, Route 53, and more. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: Server Software | None, Read, Full | Determines access to the Software tab on server detail pages. The ‘Full’ permission level surfaces a SYNC button on the Software tab, users with ‘Read’ permission do not see the SYNC button. | The Software Tab of a server detail page is where the list of installed software packages for the server are shown. |  |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of HPE Morpheus Enterprise is available. | This permission is recommended for those responsible for defining HPE Morpheus Enterprise‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within HPE Morpheus Enterprise UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of HPE Morpheus Enterprise UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of HPE Morpheus Enterprise UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for HPE Morpheus Enterprise DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into HPE Morpheus Enterprise Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within HPE Morpheus Enterprise |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within HPE Morpheus Enterprise. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in HPE Morpheus Enterprise or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default HPE Morpheus Enterprise landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the HPE Morpheus Enterprise environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through HPE Morpheus Enterprise API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows HPE Morpheus Enterprise to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in HPE Morpheus Enterprise only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed HPE Morpheus Enterprise Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | HPE Morpheus Enterprise will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes HPE Morpheus Enterprise to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, List, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “List” permission allows only listing Cypher entries in HPE Morpheus Enterprise UI and API. The “Read” permission allows listing in addition to decrypting them via automation for used in scripts and Tasks. The “User” permission will allow access similar to “Read” though only for Cypher objects the user owns, in addition to allowing for creation of Cypher entries. The “Full” permission allows creation and “Read” access to all Cypher entries regardless of who created them. The “Full Decrypt” permission gives the same rights as “Full” with the added privilege of decrypting the secret values for plaintext viewing. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The HPE Morpheus Enterprise Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. HPE Morpheus Enterprise then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json b/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
new file mode 100644
index 0000000..4b03f8c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+  "title": "Infoblox",
+  "ordinal": 506,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html",
+  "topic_cluster": {
+    "clustering_title": "Infoblox",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md b/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
new file mode 100644
index 0000000..2fa6f09
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
@@ -0,0 +1,153 @@
+# Infoblox
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+- Use script variables like <%= variableX %> for evaluation of the key data in extended attributes
+
+## Adding Infoblox Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise Infoblox integration requires credentials for an Infoblox user account with API access granted, access to list the pools and zones you wish to work with, and rights to create and destroy records. See Infoblox documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network - Integrations`
+2. Select + ADD > IPAM > Infoblox
+3. Enter the following: 
+
+   ![../../_images/infoblox_settings_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-98F9FF7B-AC47-4C2E-B21B-FAE2E4D79468-high.png)
+
+   NAME
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable the Integration
+
+   URL
+   :   Infoblox wapi url. Example: <https://yourInfobloxHost/wapi/v2.10.5>
+
+       TIP
+
+       The target Infoblox host wapi version can be referenced at <https://yourInfobloxHost/wapidoc/>
+
+   USERNAME
+   :   Infoblox user username
+
+   PASSWORD
+   :   Infoblox user password
+
+   THROTTLE RATE
+   :   In milliseconds (ms)
+
+   DISABLE SSL SNI VERIFICATION
+   :   Leave selected to disable SSL SNI Verification
+
+   INVENTORY EXISTING
+   :   Mark this option to inventory existing network pools from Infoblox
+
+   NETWORK FILTER
+   :   Filter which networks are synced into HPE Morpheus Enterprise. Example: Network Filter: `network_view=default&*Building=work`
+
+   ZONE FILTER
+   :   Filter terms for Zone Records
+
+   TENANT MATCH ATTRIBUTE
+   :   This can be set to the name of the extended attribute in Infoblox where HPE Morpheus Enterprise will check for the id of a morpheus tenant. This allows for setting the tenant’s HPE Morpheus Enterprise id to an extended attribute field on a network view or network in Infoblox, and when the network or view is discovered by morpheus, it will be auto assigned to the right tenant.
+
+   IP MODE
+   :   Static IPs or DHCP Reservations
+
+   EXTRA ATTRIBUTES
+   :   Accepts a JSON input of custom attributes that can be saved on host records in Infoblox. These Must be first defined as extra attributes in Infoblox and values can be injected for the user creating the record and the date of assignment. The available injectable attributes are: userId, username, and dateCreated.
+
+       ```
+       ```
+       {  
+         "Date Assigned":"<%=dateCreated%>",  
+         "Requestor":"<%=username%>",  
+         "Request Number":"<%=userId%>"  
+       }
+       ```
+       ```
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the Infoblox IPAM integration will be created and the following will sync:
+
+- Infoblox networks will be synced in and populate in the Infrastructure - Network - IP Pools tab and in the Infoblox detail page under the NETWORK POOLS tab
+- Host Records will sync and populate in the Network Pool detail view (select an IP Pool name to view)
+- DNS Zones will sync and populate under Infrastructure - Network - Domains and in the Infoblox detail page under the HOSTS tab
+- DNS Zone Records will sync and populate
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Infoblox IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Infoblox IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time (if desired)
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP Pools or Infrastructure  >  Network  >  Services  >  Infoblox
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addhostrecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-06C4001C-7079-484B-93C0-F78B6A6000CE-high.png)
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+
+   DOMAIN
+   :   Select an Infoblox Zone
+
+   Create DNS Records
+   :   Select to create DNS A and PTR Records in Infoblox
+4. Select SAVE CHANGES
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select a Domain from Infrastructure  >  Network  >  Domains or Infrastructure  >  Network  >  Services  >  Infoblox  >  Zones
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addzonerecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9A893000-4821-4C0D-8205-5F43B0CBF5F3-high.png)
+
+   NAME
+   :   Name for the record, such as Hostname
+
+   Type
+   :   A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+
+   CONTENT
+   :   Content of the record, such as IP or A Record
+
+   TTL
+   :   Time To Live value
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json b/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
new file mode 100644
index 0000000..6f04bc1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+  "title": "3-Node HA Upgrade",
+  "ordinal": 23,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html",
+  "topic_cluster": {
+    "clustering_title": "3-Node HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md b/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
new file mode 100644
index 0000000..5d9c491
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
@@ -0,0 +1,301 @@
+# 3-Node HA Upgrade
+
+3-Node HA Appliances represent 3 App nodes with local RabbitMQ and Opensearch services clustered across the app nodes, and an external MySQL cluster.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be obtained from My HPE Software Center. Reach out to your account manager with any questions regarding access.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for any 3-node variations using externalized MySQL, Opensearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+WARNING
+
+Upgrades can add additional storage load on database nodes. Please refer to database storage requirements within 3nodeinstall before upgrading.
+
+### 3-Node HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3-Node HA configurations to v8.1.0.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. With the upgrade package downloaded and transferred to each application node, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once the Node 1 upgrade has completed and the UI is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work, consult the related article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/Configure-Morpheus-to-utilize-and-alternate-port-for-SSL?language=en_US).
+
+#### 3-Node Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the ui is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once Node 2 upgrade has completed and the ui is available, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### 3-Node HA CentOS / RHEL Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3 Node HA configurations to v8.1.0.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once Node 1 upgrade has completed and the UI is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the RPM package on Node 3 and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### 3-Node Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1. 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the u is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Then upgrade the RPM package on Node 3, then run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json b/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
new file mode 100644
index 0000000..7acd111
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+  "title": "Installing and Integrating an External Cypher Appliance",
+  "ordinal": 239,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html",
+  "topic_cluster": {
+    "clustering_title": "Installing and Integrating an External Cypher Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md b/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
new file mode 100644
index 0000000..c4d06f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
@@ -0,0 +1,55 @@
+# Installing and Integrating an External Cypher Appliance
+
+The external Cypher appliance runs on a small separate VM and supports a variety of base OS distributions. Credentials are securely passed to the external appliance and can be retrieved and consumed in specific places within HPE Morpheus Enterprise UI. The download URL for the installer can be retrieved from HPE Morpheus Enterprise [Hub](https://app.morpheushub.com/), replace the placeholder URL in the instructions below with the correct URL for the latest version of the Cypher appliance.
+
+Begin by provisioning and updating the VM for the Cypher appliance. Then, download the installer. The following steps go through the installation process on Ubuntu but, as mentioned in the previous paragraph, many popular distributions are supported.
+
+```
+```
+# An example URL is shown below, find the URL for the latest version and for the correct distro at |morpheus| Hub  
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-cypher_$version_amd64.deb
+```
+```
+
+Next, install and reconfigure the package.
+
+```
+```
+sudo dpkg -i morpheus-cypher_$version_amd64.deb  
+sudo morpheus-cypher-ctl reconfigure
+```
+```
+
+After the installation and reconfigure is complete, we need to record the generated API key so we can integrate the external Cypher store with HPE Morpheus Enterprise in a later step. We can get this from the logs with the following command:
+
+```
+```
+sudo morpheus-cypher-ctl tail  
+==> /var/log/morpheus-cypher/cypher/current <==  
+2022-02-02_15:22:27.84848 |  \/  (_) ___ _ __ ___  _ __   __ _ _   _| |_  
+2022-02-02_15:22:27.84848 | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|  
+2022-02-02_15:22:27.84848 | |  | | | (__| | | (_) | | | | (_| | |_| | |_  
+2022-02-02_15:22:27.84848 |_|  |_|_|\___|_|  \___/|_| |_|\__,_|\__,_|\__|  
+2022-02-02_15:22:27.84849   Micronaut (v3.2.2)  
+2022-02-02_15:22:27.84849  
+2022-02-02_15:22:28.09130 15:22:28.087 [main] INFO  i.m.context.env.DefaultEnvironment - Established active environments: [ec2, cloud]  
+2022-02-02_15:22:30.15129 15:22:30.151 [main] INFO  c.m.cypher.service.CypherService - Root Data: null  
+2022-02-02_15:22:30.83499 15:22:30.834 [main] INFO  c.m.cypher.service.CypherService - Initialized Root Token: c90xxxx00000xxxxxx000000xxxxx000 ... Write this down as it will only display once  
+2022-02-02_15:22:32.01282 15:22:32.012 [main] INFO  io.micronaut.runtime.Micronaut - Startup completed in 4749ms. Server Running: http://localhost:8080
+```
+```
+
+IMPORTANT
+
+The API key is only shown once when the appliance is first installed. Securely store this API key for later reference or you will be unable to integrate this Cypher appliance with any other HPE Morpheus Enterprise appliances.
+
+This completes the installation process, move to HPE Morpheus Enterprise UI to integrate the remote Cypher store with HPE Morpheus Enterprise. Cypher integrations are added in Infrastructure > Trust > Integrations. Click + ADD and then click Cypher. Configure the following:
+
+- **NAME:** A name for the Cypher integration in HPE Morpheus Enterprise
+- **ENABLED:** When checked, this Cypher integration is available for storing and retriving credentials
+- **API HOST:** The URL where your Cypher appliance can be reached (ex. <https://x.x.x.x/>)
+- **API KEY:** The API Key we retrieved and saved in the previous step
+
+![../../_images/addCypherInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37B0DB77-147F-4EA0-BD49-CB4DA1253ED4-high.png)
+
+Click SAVE CHANGES to save the new integration. Refer to the “Credentials” section above for details on storing new credential sets using the external appliance and how they can be called back in various places throughout the UI.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..172628d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 266,
+  "parent_title": "Tools",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..729fce8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json b/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
new file mode 100644
index 0000000..a9246e5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+  "title": "Add F5BigIP load balancer",
+  "ordinal": 495,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html",
+  "topic_cluster": {
+    "clustering_title": "Add F5BigIP load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md b/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
new file mode 100644
index 0000000..a9b0b20
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
@@ -0,0 +1,61 @@
+# Add F5BigIP load balancer
+
+## About this task
+
+NOTE
+
+- The HPE Morpheus Enterprise integration with F5 only supports basic authorization. Token-based authorization is not currently supported.
+- The F5 API handles SSL certificate installation by downloading the certificate from a URL the user provides. HPE Morpheus Enterprise provides the “Appliance URL” configured in global settings (Administration > Settings > Appliance) to satisfy that requirement. Make sure you have configured a valid URL in this field and that F5 can reach it.
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. Select **F5 BigP** from the drop-down list. 
+
+   The NEW LOAD BALANCER panel opens.   
+   ![F5 LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FBE17C69-EA72-449A-9EAC-9529F57EFA38-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   Select the load balancer group.
+
+   CLOUD
+   :   Select the load balancer cloud.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions
+
+   API HOST
+   :   Enter IP or resolvable host name url.
+
+   API PORT
+   :   Enter the API port number. Typically it will be `8443`.
+
+   USERNAME
+   :   Enter the API user name.
+
+   PASSWORD
+   :   Enter the API user password.
+
+   MANAGEMENT URL
+   :   Enter the management URL. For example, <https://10.30.20.31:8443/xui/>
+
+   Advanced Options (optional)
+   :   - ALLOW VIP ENTRY: Select this parameter to list the VIP pools.
+       - VIP POOL: Select from the drop-down list.
+       - VIRTUAL NAME: Enter a virtual name.
+       - POOL NAME: Enter a virtual name.
+       - SERVER NAME: Enter a server name.
+5. Click **Save Changes**.
+
+**Subtopics**  
+
+- **[Add Load Balancer to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html)**
+- **[F5 Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
new file mode 100644
index 0000000..16b3d31
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+  "title": "Catalog",
+  "ordinal": 82,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
new file mode 100644
index 0000000..ac0c927
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
@@ -0,0 +1,41 @@
+# Catalog
+
+The Catalog presents a simplified self-service view where users can select and deploy Instances, Blueprints or Workflows with pre-defined configuration in just a few clicks and without presenting an overwhelming list of options. Selections are presented as tiles and users can add items to a cart as if shopping on an eCommerce website. For users who tend to provision regularly from a small selection of Instance Types and configurations, the catalog is an easier option compared with the much more detailed and option-rich Instance provisioning wizard.
+
+## Configuring Catalog Item Access
+
+Within the Catalog, users are presented with selections based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items. Thus, administrators will need to enable access to some Catalog Items in order for users to make use of this view.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Catalog
+
+The catalog shows the complete list of predefined items available to the user for provisioning. Catalog items are not created here, however. For more on creating catalog items, see the Catalog Items tab in the HPE Morpheus Enterprise [Library section](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items) (Library > Blueprints > Catalog Items).
+
+![../../_images/catalog.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ED6FCF79-BB81-4C2B-B4A6-4DCB7357CFB5-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning. The catalog shows a complete list of items but the list can be filtered by entering search terms or by selecting a category. When adding or editing catalog items, an optional category may be set which aids in filtering for environments which have a lot of catalog items to select from.
+
+![../../_images/orderPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3AE2F03E-DBC7-4FC1-BED0-DB5F6B096D9F-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![../../_images/cart.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CE0F030E-A45D-4412-92D9-38608B669FC9-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can now be viewed from their respective list pages. Depending on whether you’ve ordered an Instance, App, or Workflow execution, navigate to the appropriate list page for your item to view it.
+
+## Order Detail
+
+![../../_images/orderHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D954DA2F-C2AD-4BD7-B7C3-02CE5AEF0719-high.png)
+
+The Order Detail page includes a complete list of orders and some basic details about them. If the item still exists, you can link through to the detail page for the item (whether that be Instance detail, App detail, or Execution detail). When the item name is not hyperlinked, the item has been deleted but the record of the order remains in the history.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json b/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
new file mode 100644
index 0000000..1e45815
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+  "title": "Boot",
+  "ordinal": 245,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html",
+  "topic_cluster": {
+    "clustering_title": "Boot",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md b/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
new file mode 100644
index 0000000..b9308bf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
@@ -0,0 +1,11 @@
+# Boot
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html)**
+- **[Mapping](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html)**
+- **[Boot Menus](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html)**
+- **[Answer Files](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html)**
+- **[Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..41014d7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 146,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..d8f112c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,9 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html)**
+- **[Image Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json b/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
new file mode 100644
index 0000000..a418a38
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+  "title": "Load Balancers",
+  "ordinal": 490,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md b/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
new file mode 100644
index 0000000..81b20a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
@@ -0,0 +1,13 @@
+# Load Balancers
+
+**Subtopics**  
+
+- **[Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html)**
+- **[Add Amazon ELB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html)**
+- **[Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html)**
+- **[Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html)**
+- **[Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html)**
+- **[Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html)**
+- **[Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html)**
+- **[Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html)**
+- **[Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..fb30f5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 33,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..f2596c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,27 @@
+# Proxies
+
+## Overview
+
+In many situations,companies deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this HPE Morpheus Enterprise provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. HPE Morpheus Enterprise is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the HPE Morpheus Enterprise appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and `no_proxy` are set appropriately.
+
+## Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within HPE Morpheus Enterprise we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
+
+## Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
+
+## Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprints as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, HPE Morpheus Enterprise will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the `No Proxy` rules for proxy exceptions.
+
+## Docker
+
+When provisioning Docker based hosts within a Proxy environment it is up to the user to configure the docker host proxy configuration manually. There are workflows that can be configured via the Automation engine to make this automatic when creating docker based hosts. Please see documentation on Docker and proxies for specific information.
+
+Proxy setups can vary widely from company to company, and it may be advised to contact support for help configuring morpheus to work in the proxy environment.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json b/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
new file mode 100644
index 0000000..5d7b4f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+  "title": "Monitoring and Completion",
+  "ordinal": 426,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring and Completion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md b/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
new file mode 100644
index 0000000..ce5774c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
@@ -0,0 +1,15 @@
+# Monitoring and Completion
+
+## Procedure
+
+1. Monitor job progress from the Job Executions tab.
+2. Execution time may range from 15 minutes to over one hour, depending on:
+   1. Number of servers
+   2. Deploy mode
+   3. Selected content
+   4. Firmware and driver versions on the target servers
+3. Upon completion, detailed logs are available in the Job Executions tab.
+
+   - Do not enter any values in Custom Config.
+   - Servers are not automatically rebooted as part of the update process.
+     - If a reboot is required to complete updates, it must be performed manually at a time appropriate for the hosted services.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json b/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
new file mode 100644
index 0000000..45089fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+  "title": "Ansible Tower",
+  "ordinal": 376,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Tower",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md b/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
new file mode 100644
index 0000000..2908b60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
@@ -0,0 +1,184 @@
+# Ansible Tower
+
+## Overview
+
+HPE Morpheus Enterprise supports Ansible Tower for configuration management. HPE Morpheus Enterprise accomplishes this by integrating with an existing instance running Ansible Tower (AT) 3.3.0-1 and earlier. The username and password required for integration can be a user with admin access or a user with project admin access
+
+HPE Morpheus Enterprise will import the current Inventory, Templates, Hosts, Groups and Projects. In the integration view it will add a Job tab which will have information of all the jobs executed from HPE Morpheus Enterprise.
+
+NOTE
+
+This integration will not import data of the jobs which are not executed from HPE Morpheus Enterprise.
+
+## Add Ansible Tower Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Ansible Tower”
+3. Populate the following fields: 
+
+   - Name: Name of the Ansible Tower Integration in HPE Morpheus Enterprise
+   - Enabled: To disable the integration, uncheck this option
+   - Ansible Tower URL: An HTTPS or HTTP Ansible Tower URL
+   - Username: The user HPE Morpheus Enterprise would use to communicate with Ansible Tower
+   - Password: Enter the password. Password is encrypted and saved in DB
+   - API Version: This drop down has one option (`v2`) for now but may have others in future
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Scope Ansible Tower Integration to a Cloud
+
+### About this task
+
+All instances provisioned in this cloud will have the Ansible Tower config option during provisioning. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Scope Ansible Tower Integration to a Group
+
+### About this task
+
+All instances provisioned in this Group will have the Ansible Tower config option during provisioning in any cloud part of the Group. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Tower Integration added, an Ansible Tower section will appear in the Config section of the provisioning wizard. By default, Ansible Tower is enabled, but can be disabled by expanding the Ansible Tower section and unchecking Enable Ansible Tower.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible Tower
+:   Select to bootstrap
+
+Inventory
+:   A list of Inventory available in Ansible Tower will appear in the drop down. Select an existing inventory. The instance will be added to the inventory selected.
+
+Ansible Group
+:   Enter the name of a new or an existing Group in the inventory selected above.
+
+Template
+:   Select an existing template or select the option ‘Create New Template’. If ‘Create New Template’ is selected below fields will appear and are mandatory
+    :   Template Name
+        :   Enter the template name
+
+        Project
+        :   Select an existing project from the drop down options
+
+        Playbook
+        :   Select a playbook from the dropdown to be associated with the template. Note: HPE Morpheus Enterprise doesn’t store a local copy of the playbooks visible in Ansible Tower. SCM or local path for playbooks should be maintained in Ansible Tower.
+
+Execute Mode
+:   Select one of the options from the dropdown
+    :   Limit to instance
+        :   This will execute the template on the instance provisioned.
+
+        Limit to Group
+        :   This will execute the template on all hosts attached to the group entered in the ‘Ansible Group’ field.
+
+        Run for all
+        :   This will execute the template on all hosts in the inventory
+
+        Skip execution
+        :   This will skip the execution of the template on the instance provisioned.
+
+## Scoping Ansible Tower Jobs to Tenant-Default Inventories
+
+Users in the Primary Tenant have an additional Inventory execution option when creating Ansible Tower Job-type Tasks. When making a selection in the Inventory field, “Use Tenant Default” may be selected rather than a specific Inventory. This is because Ansible Tower Jobs created in the Primary Tenant may be shared publicly to other Tenants through public Workflows or when associated with public Library items.
+
+![../../_images/ansibleTowerInventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-628F3A54-3E8C-4986-8502-5ADA96A0ACC6-high.png)
+
+When this option is selected and the Task is run in a Subtenant, it will automatically be run against the default Inventory which is configured for the Subtenant. The next section includes steps for associating Tenants and default Inventories.
+
+IMPORTANT
+
+An Ansible Tower Job configured to run against a Tenant-default Inventory will fail when run by a user whose Tenant does not have a default Inventory set.
+
+### Setting Default Inventories for Tenants
+
+When creating or editing Ansible Tower integrations, navigate to the Inventory tab to view all Inventories synced from the selected integration. Click “Permissions” inside the “MORE” action menu at the end of a row for the selected Invetory. Within the PERMISSIONS modal, there is a single typeahead field where a Tenant can be selected. Once the Tenant is selected, click SAVE CHANGES. Now back on the Inventory list view, you’ll see the default Tenant which is associated with each Inventory.
+
+NOTE
+
+Tenants may only be associated with one Inventory, though an Inventory can have multiple Tenant associations. If a Tenant is selected to be associated with a new Inventory, its association with a previous Inventory will automatically be removed.
+
+![../../_images/inventoryList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8724DEA8-C761-416C-81CA-D3F82E6177B8-high.png)
+
+## Ansible Tower Configuration
+
+When using an Ansible Tower task type or associating the Ansible Tower integration with a cloud/group, there are a few options that can be configured:
+
+- Inventory
+- Group
+- Job Template
+- Execute Mode
+
+### Prompt at Launch
+
+Some options used to configure your deployments have the related option of **Prompt at Launch** in Ansible Tower, which should be enabled on the template to be chosen in the **Job Template** field. If **Prompt at Launch** is not enabled, the values configured on the template in Ansible Tower will be used instead. **Prompt at Launch** can be seen below on the **Inventory** and **Limit** fields:
+
+![../../_images/ansibleTowerPromptAtLaunch.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4731D3C6-EE0D-46A5-A78C-DD7235B7A582-high.png)
+
+### Group
+
+The **Group** field is optional but a group can be entered into the field to associate the host to, in the target inventory. If the group is existing, then the instance will be associated as a host to that group. If the group does not exist, the group will be created and the instance will be associated as a host to that group.
+
+![../../_images/ansibleTowerGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-048E8C28-2E88-4711-B75F-2E8EEB9FA747-high.png)
+
+### Inventory
+
+When provisioning on a cloud with a configured Ansible Tower integration or using an Ansible Tower task type against an instance, the instance will be added as a host to the inventory chosen in the **Inventory** field. As mentioned, if specified, these instance will be associated with groups in the inventory as well. When using an inventory that syncs from a project, the instance will still be added as a host in the inventory, in addition to the sync’d inventory. This means that Ansible Tower will aggregate the manually added hosts from HPE Morpheus Enterprise with the sync’d project inventory. However, if the **Overwrite** option is enabled on the source for the project that contains the inventory, any hosts added by HPE Morpheus Enterprise **will be overwritten**. In some cases, a separate HPE Morpheus Enterprise inventory may be desired, if **Overwrite** is required on your sources.
+
+![../../_images/ansibleTowerOverwrite.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ECAFBE4F-9B9C-42E0-86EE-30B3860FFEBF-high.png)
+
+## Passing extra\_vars to Ansible Tower Job
+
+When provisioning or when running Ansible Tower Jobs as HPE Morpheus Enterprise Tasks, you may pass the `extra_vars` stack to the Tower Job. First, ensure the Job Template has extra variables “Prompt on Launch” enabled as shown below:
+
+![../../_images/towerExtraVars.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4C836374-5A94-4045-AE04-99B90A2F4F9F-high.png)
+
+The sample Playbook below is associated with the Tower Job Template.
+
+```
+```
+---  
+- hosts: all  
+vars:  
+  Opensource_Team: "Customer"  
+tasks:  
+- name: Print Hello World  
+  debug:  
+    msg:  
+    - "Hello World {{ Opensource_Team }}. Here are Morpheus extra_vars: {{ morpheus }}"
+```
+```
+
+After executing the Tower Job, we can see the variable stack surfaced into the results as defined in the Playbook:
+
+![../../_images/towerResults.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-47CAE600-317C-468B-B98F-69522E132DE4-high.png)
+
+## Use Case
+
+You have Job template(s) in Ansible Tower to do post build config after the OS is deployed. The playbook with roles and tasks to do post build will add specific users and groups, install required packages, remove packages, disable services, change config for ntp, resolv, hosts etc. You want to add the instance to an existing Group/Inventory in Tower.
+
+You can achieve this by adding the Ansible Tower Integration and then scope it to a Cloud or Group. While provisioning an instance, in the config stage you have the Ansible Tower section with option to select the post build job template, select the Inventory and provide an existing Group Name or if the Group doesn’t exist Morpheus will create it and submit for provisioning.
+
+Morpheus will provision the instance, once it is in the finalize state where the instance has an ip and has completed domain join if required, added user(s) or User Groups if specified then HPE Morpheus Enterprise will add the instance to the inventory and Group and run the Template which will do all the post build of the server.
+
+The output of the post build template execution can be see under Instance history.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..11fb345
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 219,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..e5c75db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,34 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+## Overview
+
+The IP Pools tab in the Networks section allows you to create HPE Morpheus Enterprise-type IP Pools (which is an IP address range HPE Morpheus Enterprise can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
+
+## To add a HPE Morpheus Enterprise Network Pool
+
+### Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in HPE Morpheus Enterprise.
+
+       Pool Type
+       :   Currently HPE Morpheus Enterprise-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from HPE Morpheus Enterprise
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+### Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json b/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
new file mode 100644
index 0000000..62d2525
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+  "title": "Executions",
+  "ordinal": 95,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html",
+  "topic_cluster": {
+    "clustering_title": "Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md b/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
new file mode 100644
index 0000000..d2b4d49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
@@ -0,0 +1,31 @@
+# Executions
+
+Executions contains the execution status and history from Task and Operational Workflow Executions run from Library > Automation > Tasks and Library > Automation > Workflows. Executions for Tasks and Workflows are split out to their own labeled tabs.
+
+NOTE
+
+Tasks and Workflows executed from a Job or from Instance or Host `Actions` do not populate in the Executions Section, and can be referenced from the History tab on the target resource. All task and Workflow executions can be referenced in Operations  >  Activity  >  History
+
+Execution results in the ui display:
+
+NAME
+:   Name of the Task or Workflow Executed
+
+TYPE
+:   Type of execution (Task or Workflow)
+
+START DATE
+:   Date and time of execution
+
+ETA/DURATION
+:   Estimate time of completion for executions in progress, or the total execution time for completed executions.
+
+RESULTS
+:   Result status of execution (Succeeded, Failed, In-Progress or Pending)
+
+Execution Detail (i)
+:   Click on the `i` to view process output results
+
+    NOTE
+
+    Job and automation executions can be expanded to show process details by clicking on the arrow icon immediately to the right of the NAME column.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..2e78645
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 195,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..9130857
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json b/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
new file mode 100644
index 0000000..23f9bc9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+  "title": "User Groups",
+  "ordinal": 309,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html",
+  "topic_cluster": {
+    "clustering_title": "User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md b/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
new file mode 100644
index 0000000..3542af6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
@@ -0,0 +1,49 @@
+# User Groups
+
+## Overview
+
+User Groups can be selected during provisioning to add each group members credentials to the Instance. User Groups can be configured for sudo access and in Linux will assign Group members to a groupId in linux.
+
+## Creating User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select + CREATE USER GROUP.
+4. Enter the following: 
+
+   NAME
+   :   Name of the User Group
+
+   DESCRIPTION
+   :   Optional User Group Description
+
+   SERVER GROUP
+   :   Name of the groupId to assign Group members to in linux.
+
+   SUDO ACCESS
+   :   Enable to give Group members sudo access
+
+   USERS
+   :   Search for and select existing Users to add to the User Group.
+5. Select SAVE CHANGES.
+
+## Editing User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select the ACTIONS dropdown next to the target User Group.
+4. Select EDIT
+5. Make changes, add or remove users from the group.
+6. Select SAVE CHANGES.
+
+## Adding a User Group when Provisioning
+
+### Procedure
+
+1. When provisioning, in the CONFIG section expand the USER section.
+2. Select an existing Group from the USER GROUP dropdown.
+3. Users will be created for members in the selected User Group on the provisioned Instance(s).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json b/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
new file mode 100644
index 0000000..3770747
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+  "title": "Local Storage - Boot Volume Selection During Instance Creation",
+  "ordinal": 454,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md b/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
new file mode 100644
index 0000000..a41e474
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
@@ -0,0 +1,9 @@
+# Local Storage - Boot Volume Selection During Instance Creation
+
+Table 1. Boot Volume Selection During Instance Creation
+
+        | S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Boot volume not found | Device UID mismatch or not yet discovered | - Confirm device discovery is complete - Verify the UID in the storage controller | - | Wait for discovery to complete and retry. |
+| 2 | `ResourceMissingAtURI` errors | Redfish device discovery is not complete | - Verify Redfish discovery status - Confirm the device is visible in Redfish inventory | - | Retry after a short wait. |
+| 3 | Script cannot find the device | UID format mismatch or missing disk link | - Verify `/dev/disk/by-id/` entries  - Confirm correct disk UID format | - | Ensure disk links are correctly mapped and retry. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..72b8412
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 170,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..8825b05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,13 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html)**
+- **[HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html)**
+- **[Kubernetes Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html)**
+- **[Docker Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html)**
+- **[EKS Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html)**
+- **[GKE Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html)**
+- **[OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json b/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
new file mode 100644
index 0000000..5bbbdd1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+  "title": "Deployments",
+  "ordinal": 99,
+  "parent_title": "Code",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html",
+  "topic_cluster": {
+    "clustering_title": "Deployments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md b/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
new file mode 100644
index 0000000..27f1af5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
@@ -0,0 +1,110 @@
+# Deployments
+
+NOTE
+
+In v5.3.2+, Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+
+The deployments section provides very useful PaaS like capabilities when it comes to deploying applications into the newly provisioned environment. These can be uploaded directly from the UI, pulled from a build server, pulled from a public or private Git repository or even via the API and the various plugins created, such as Jenkins, and Gradle to support continuous build / integration workflows.
+
+A deployment can be considered a set of versions that relate to a particular project or application being deployed. This allows one to keep track of a history of versions and easily reuse these deployment versions across Instances that may exist in different environments. An example might be to deploy a version from a deployment to a staging Instance and (once approved) also deployed into production.
+
+## Role Permissions
+
+Access and capabilities for the **Deployments** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+## Getting Started
+
+Getting started with deployments is easy. They can vary slightly for the application stack being deployed but the simplest phase of a deployment is adding a version and adding the appropriate files to the deployment archive that are needed for the application to run. This could be a single file like a WAR file for Tomcat, or it could be hundreds of files for stacks like Ruby on Rails.
+
+There are a few ways to create a deployment. The first is to use the Provisioning ‣ Code ‣ Deployments section of the application to create them. Simply add a new deployment and give it a name representing the application that is being deployed. Once a deployment is created select the deployment to view its versions (which will be empty to start). Next, it is time to add a version.
+
+When adding a version there are several options. There are 3 types represented by the UI. These include File, Fetch, and Git respectively. A File deployment allows the user to simply drag their files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees (If files exist in subfolders then only the Chrome browser is supported due to browser limitations at the time of this writing). This is also the common type that is represented when files are uploaded via the CLI, or available build tool integration plugins. Once the files have completed their upload simply save the version for use.
+
+### Git
+
+For performing git based deploys HPE Morpheus Enterprise supports both public and private repositories. To utilize a private git repository the add version dialog will display a public keypair that can be added to the git service for authentication purposes. Currently this keypair is shared across the account and not specifically scoped to the user so it may be advisable to connect this integration to a deployment account in git. From here either a ssh or `https` git url can be entered along with a git branch or tag name. Once the version is saved, this repository will be copied down into the deployment archive for use.
+
+### Fetch
+
+Fetch based deployments are pretty straightforward. Simply enter a url to a file representing the deployment. This can be a single file (in which case it will just be added to the deployment archive singularly) or it can be a zip file (which will automatically be expanded into the archive). HTTP Authentication options can also be entered if the url requires some form of basic authentication scheme for access by the appliance.
+
+## Configuring Library Items for Deployments
+
+In order to have the UI tools available to utilize Deployments with a provisioned Instance, the Library items must have certain configurations set. Once configured correctly, any Instance provisioned from the Library item would then have access to any of your Deployments.
+
+First, within the **Instance Type** (Library > Blueprints > Instance Types), ensure the SUPPORT DEPLOYMENTS attribute is marked. This is off by default so it will need to be manually enabled on all relevant Instance Types. Next, you’ll want to ensure you have the correct DEPLOY FOLDER configured on **Node Types** (Library > Blueprints > Node Types). This is the mount point which will be replaced by the contents of your Deployments. Finally, you will want the **Provisioning Workflows** associated with the Library item to have the proper Tasks configured within its Pre-Deploy and/or Deploy phases. Tasks in the Pre-Deploy phase are run as soon as the Deployment is triggered from the UI prior to any other Deploy actions taking place. This could be used, for example, to extract files from the deploy folder and move them to their final destinations before the primary deploy actions take place. Tasks in the Deploy phase are run after the deployment is completed, such as if you wanted to update configuration files or inject connection details from the environment after the completion of the deploy process.
+
+## Deploying to an Instance
+
+Now that the Deployment object and Library items are configured, it is easy to push that deployment out to any Instance provisioned within HPE Morpheus Enterprise by navigating to the specific Instance that it needs deployed to. On the Instance detail page there is a tab called Runtime and within it another tab labeled Deploy. From here simply add a deploy. The dialog will ask firstly from which deployment the deploy is from (or allow you to create a new one on the spot), and secondly which version to deploy (also with the option to add one on the fly). The next step of the wizard will display any configuration options that might be specific to the Instance type being deployed to (i.e. CATALINA\_OPTS for Tomcat or Java Command for java) as well as the file explorer and deployment type selections for review (or use when creating a new version on the fly). Fill in the required items then simply hit complete. The deploy will now be asynchronously sent off to all of the virtual machines or containers within the Instance in a rolling restart and the deployment status will be represented.
+
+TIP
+
+When deploying to an Instance, the custom configuration options that were entered during the previous deployment are automatically carried forward allowing one to edit them or leave them as is.
+
+## Rolling Backwards and Forwards
+
+Because of the tracked history of deployments kept within HPE Morpheus Enterprise, the deploy tab of Instance detail makes it easy to choose a previously run deployment and jump back to it in the event of a failed deployment. The history will automatically be updated and the configuration, as well as data from the previous deployment state of the Instance will be restored.
+
+## Offloading Storage
+
+Since a full history of the backup builds are kept in HPE Morpheus Enterprise, as the appliance grows it becomes necessary to change where these are stored. On a fresh install these are stored on the local appliance in `/var/opt/morpheus` or wherever the master account may have changed the configuration to point to. It is also possible to adjust the deployment archive store by creating a Storage Provider tied to an S3 compatible object store, Openstack Swift object store, or any other type of mountpoint provided. This option can be adjusted in Administration > Settings > Provisioning once a storage provider is created within the account.
+
+## Add Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the + Add button.
+5. Enter a Name for the deployment and a description (optional)
+6. Click the Save Changes button to save.
+
+## Add Version
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the Name of the deployment you would like to add a version to.
+5. Click the Add Version button.
+6. From the Add Version Wizard select the deployment type.
+7. Input the Version of the deployment.
+8. Depending on the type of deployment selected perform one of the following: 
+
+   Files
+   :   Drag files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees.
+
+   Fetch
+   :   Enter a url to a file representing the deployment.
+
+   Git
+   :   The add version dialog will display a public key pair that can be added to the git service for authentication purposes. Either a ssh or https git url can be entered along with a git branch or tag name.
+9. Click the Save Changes button to save.
+
+## Edit Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the ✎ icon on the row of the deployment you wish to edit, or click the Name of the deployment and then the Edit button from the deployment detail page.
+5. Modify information as needed
+6. Click the Save Changes button to save.
+
+## Delete Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the 🗑 icon on the row of the deployment you wish to delete, or click the Name of the deployment and then the DELETE button.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json b/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
new file mode 100644
index 0000000..7b0143a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+  "title": "Costing: Tag Costing",
+  "ordinal": 64,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tag Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md b/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
new file mode 100644
index 0000000..acc9871
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
@@ -0,0 +1,28 @@
+# Costing: Tag Costing
+
+![../_images/7tagcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3B425176-5841-4C03-B67D-F6B86603E1CD-high.png)
+
+The Tag Analysis dashboard creates groups of workloads based on the presence of specific tags and meeting other filters. This workload group can be analyzed for total cost and projected costs.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Tag key (all matched by search)
+- Metric (apply to see the top tag values by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+
+## Data Displayed
+
+The following aggregate totals (by tag) are compiled for workloads that meet set filters:
+
+- **TAGS:** The total number of unique tag keys for workloads meeting dashboard filters
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+
+## Tags List
+
+A list of each tag (key) represented on selected workloads is displayed in a list below the dashboard graphs. We also see the total number of workloads associated with the tag, the total memory, total storage, total CPU cores, and total price. If we click the “MORE” link at the end of each row, we can see a list of all tag values associated with the key.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json b/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
new file mode 100644
index 0000000..7b050f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+  "title": "Storage",
+  "ordinal": 453,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md b/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
new file mode 100644
index 0000000..a669869
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
@@ -0,0 +1,8 @@
+# Storage
+
+The topic describes troubleshooting procedures for storage.
+
+**Subtopics**  
+
+- **[Local Storage - Boot Volume Selection During Instance Creation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..21c2201
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 168,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..cd89611
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,119 @@
+# Groups
+
+## Overview
+
+### About this task
+
+Groups in HPE Morpheus Enterprise define what resources a user has access to. Group access is defined by User Roles. Clouds are added to groups, and a User can only access the Clouds that are in the Groups their Role(s) gives them access to. Resources such as Networks, Datastores, Resources Pools, and Folders have additional Group access settings.
+
+Policies applied to a Group will be enforced on all Instances provisioned or moved into that Group.
+
+NOTE
+
+Groups are not multi-tenant. A group only exists in the tenant is it is created in.
+
+The Groups view displays all current groups, includes search feature, and also enables the addition of new groups.
+
+To View Groups:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## CLI
+
+View all groups: `groups list` To use the group: `groups use <id>` or `groups use "group name"` Json output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
+
+## API
+
+View all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` View a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
+
+## Adding Groups
+
+### About this task
+
+![../../_images/add_group.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-314860C2-E6E2-4F71-9AC0-AEE0E9E53A08-high.png)
+
+To add a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
+
+## Managing Groups
+
+### About this task
+
+![../../_images/group_view.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4D1622A4-0DFF-47E7-AFF2-B9CBC2298957-high.png)
+
+To view a Group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+### Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Policies
+:   Lists and allows creation or management of Policies applied to the Group.
+
+## Edit Group
+
+### About this task
+
+To edit a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
+
+## Delete Group
+
+### About this task
+
+To delete a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
+
+## User Access
+
+IMPORTANT
+
+User access to Groups is determined by their user Role(s). Group access for Roles can be configured in the Group Access section of a Roles Settings.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json b/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
new file mode 100644
index 0000000..1da48b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 180,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md b/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
new file mode 100644
index 0000000..d260807
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total CEPH storage, which is presented as one large volume.
+
+HVM clusters must also live in HPE Morpheus Enterprise-type Clouds (See Infrastructure > Clouds). A pre-existing HPE Morpheus Enterprise Cloud may be used or a new Cloud could be created to handle HVM management.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..e3bfa73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 217,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..7312abd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,26 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+## Adding Network Groups
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in HPE Morpheus Enterprise
+       - Description: Details of the Network Group in HPE Morpheus Enterprise
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+
+   Tenant Permissions
+   :   - Resources with Public visibility will be available to users in any Tenant (subject to other RBAC controls). Resources with Private visibility are given only to individually selected Tenants. Select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json b/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
new file mode 100644
index 0000000..67fef6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+  "title": "Remedy",
+  "ordinal": 489,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html",
+  "topic_cluster": {
+    "clustering_title": "Remedy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md b/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
new file mode 100644
index 0000000..a86d3d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
@@ -0,0 +1,80 @@
+# Remedy
+
+## PreRequisites
+
+The user used for this integration need to be an Administrator in Remedy or have all the permissions to the form that is outlined in the table below.
+
+Table 1.
+
+      | API Endpoint | Action | BMC Form | Existing BMC Role |
+| --- | --- | --- | --- |
+| /api/arsys/v1/entry/CTM:People | GET | CTM:People | Contact People Admin |
+| /api/arsys/v1/entry/COM:Company?q=%27Status%27=%22Enabled%22&fields=values(Company) | GET | COM:Company | Atrium Foundation Admin |
+| /api/arsys/v1/entry/User | GET | User | User Administrator |
+| /api/arsys/v1/entry/Group | GET | Group | User Administrator |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | POST | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | PUT | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | GET | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | POST | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | PATCH | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | GET | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | DELETE | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | POST | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | PATCH | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | GET | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | DELETE | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | POST | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | PATCH | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | GET | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | DELETE | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | POST | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | PATCH | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | GET | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | DELETE | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/arsys/v1/entry/AST:ComputerSystem | GET | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | PUT | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | POST | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | GET | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | PUT | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | POST | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | GET | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | PUT | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | POST | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | GET | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | PUT | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | POST | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | GET | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | PUT | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | POST | AST:Memory | Asset Admin |
+| /api/jwt/login | POST |  |  |
+
+## Add Remedy Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Remedy` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   REMEDY HOST
+   :   Url of the Remedy Instance. e.g: <http://xx.xx.xx.xx:8008>
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Remedy user’s password
+
+   COMPANY
+   :   The dropdown will populate with values as soon as the auth using the above creds are successful
+
+   APPROVAL USER
+   :   Full name of the user as it appear in Remedy. E.g: userid ‘anish’ would have full name as “Anish Abraham”
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json b/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
new file mode 100644
index 0000000..159c8a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+  "title": "Image Catalog",
+  "ordinal": 405,
+  "parent_title": "Image Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html",
+  "topic_cluster": {
+    "clustering_title": "Image Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md b/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
new file mode 100644
index 0000000..c2d9ecc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
@@ -0,0 +1,22 @@
+# Image Catalog
+
+This section describes how to upload Bare Metal (BM) operating system images into Morpheus using a configurable image repository. HPE Morpheus supports multiple backend storage options, allowing administrators to centrally manage OS images and reuse them across bare metal provisioning workflows.
+
+Uploaded images are registered under Library > Virtual Images and are made available for bare metal instance provisioning.
+
+## Supported OS Image Sources
+
+HPE Morpheus supports uploading Bare Metal OS images from the following storage backends:
+
+- Local storage on the HPE Morpheus appliance
+- S3-compatible object storage
+- CIFS (Samba) file shares
+- NFS (v3) file shares
+
+Each backend option is configured as a File Share or Storage Bucket and referenced during image upload.
+
+**Subtopics**  
+
+- **[Uploading OS Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html)**
+- **[Windows OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E55D4270-ED77-4161-8712-45824C891713.html)**
+- **[Linux OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json b/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
new file mode 100644
index 0000000..8898128
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+  "title": "Getting started with HPE Morpheus Enterprise and Azure",
+  "ordinal": 362,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md b/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
new file mode 100644
index 0000000..96b117e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
@@ -0,0 +1,363 @@
+# Getting started with HPE Morpheus Enterprise and Azure
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with Microsoft Azure public cloud. By the end, you will integrate your first cloud with HPE Morpheus Enterprise, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our [Reddit user community forum](https://www.reddit.com/r/morpheusdata/).
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/latest/getting_started/requirements/requirements.html). In order to provision any new Instances, hosts, or applications (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a community edition license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License. For more, take a look at our community edition [welcome package](https://www.morpheusdata.com/community-welcome).
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to Groups and a user can only access Clouds that are in the Groups to which their roles give them access. More information on HPE Morpheus Enterprise Groups is [here](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html#groups). A deep dive into Groups goes beyond the scope of this guide but it’s often useful to create a Group that contains all Clouds for testing purposes. We will create that group now so that we can add our first Cloud into this Group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+Click SAVE CHANGES. Your Group is now ready to accept Clouds.
+
+![../../_images/1newGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-542A0791-5B19-4A90-A597-CF88E9A0B7F9-high.png)
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be on-prem, public clouds, or even bare metal. In this guide, we will focus on integrating and working with Microsoft Azure public cloud.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the Cloud list page which lists all configured Clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated Azure cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AZURE (PUBLIC)” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, we’re asked to provide Azure-specific details to connect to the cloud. HPE Morpheus Enterprise Azure integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET
+
+![../../_images/2createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-31D2E874-AE3E-4F65-B514-72258B2A437B-high.png)
+
+### Create App Registration
+
+#### About this task
+
+HPE Morpheus Enterprise authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with HPE Morpheus Enterprise has Owner or Contributor permissions on the specified Subscription.
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one using the steps below. If you already have one you wish to use, continue to the next section.
+
+#### Procedure
+
+1. Log into the Azure portal
+2. Select “Azure Active Directory”
+3. Select “App Registrations”
+4. Select “New Registration” 
+
+   ![../../_images/Default_Directory_App_registrations_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A57114C7-68E3-4BBA-B11D-51BC35609D3C-high.png)
+5. Next, give the app a name, specify Web app / API for the type (default) and enter any URL for the Sign-on URL:
+6. Click Create and your new App Registration will be created. 
+
+   ![../../_images/Register_an_application_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-55330F72-25B5-4408-8A33-43884CBF6D26-high.png)
+
+#### Results
+
+Now that we have our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration in the next section.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+![../../_images/morpheusAppReg_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3DD99466-18E6-40A5-A2C4-63B8D766487E-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select “Certificates & secrets” in the Manage section
+2. Select `+ New client secret` 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FEF1F839-2F89-43AA-A5F8-744B625725F0-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select an expiration duration
+6. Click Add 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-201809CC-7FE8-42EF-87DE-2FDE9015C0E9-high.png)
+7. Copy the newly-generated client secret value. 
+
+   IMPORTANT
+
+   Copy the client secret value before continuing as it will not be viewable again later.
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Copy.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-276863D1-39D2-4F67-8A52-511B32010C1B-high.png)
+8. Store/Paste client secret for use later when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have three of the four credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID which we will gather in the next section.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the Subscriptions section. The search function can help to locate these sections if they aren’t immediately apparent in the UI menu 
+
+   ![../../_images/azuresubscriptionssearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AE54CAA0-CE46-424A-ADB0-5F5C2E2521AF-high.png)
+2. In the Subscriptions section, copy the Subscription ID 
+
+   ![../../_images/Subscriptions_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2DA76817-C462-4B49-BCA8-DCBF83CA8860-high.png)
+3. Store/Paste for use as the Subscription ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory existing cloud resources, create resources or remove them.
+
+#### Procedure
+
+1. In the Subscriptions section in Azure, select the Subscription
+2. In the Subscription pane, select “Access Control (IAM)”
+3. Either Click :guilabel`+ Add`, and then “Add Role Assignment” OR simply select “Add a role assignment” 
+
+   ![../../_images/Azure_subscription_1_Access_control_IAM_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-68F85CA0-5206-4738-8FA9-11A40E6B4277-high.png)
+4. In the right pane, select “Owner” or “Contributor” Role type
+5. Search for the name of the App Registration used for the HPE Morpheus Enterprise integration
+6. Select the App Registration in the search results
+7. Select “Save” 
+
+   ![../../_images/Add_role_assignment_save.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-374258C1-E537-4439-BCE9-9F8918C369E4-high.png)
+
+#### Results
+
+You now have the required credentials and permissions to add an Azure Cloud integration into HPE Morpheus Enterprise. Continue on with the next sections of this guide to complete the integration from the HPE Morpheus Enterprise side.
+
+### Complete the Add Cloud Process in HPE Morpheus Enterprise
+
+If you’ve followed this guide from the start, you will already have a Cloud integration modal open in HPE Morpheus Enterprise UI. If you still need to open that wizard, navigate to Infrastructure > Clouds > + ADD > Azure (Public) and click NEXT. Fill in the following fields with the information gathered in the steps above:
+
+- Subscription ID
+- Tenant ID
+- Client ID
+- Client Secret
+- Location
+- Resource Group
+- Inventory Existing Instances
+- Inventory Level
+- Account Type
+
+Once valid credentials are populated in the appropriate fields, the LOCATION dropdown menu will be populated. Select an available region, this is also a helpful check to ensure you’ve correctly provided working credentials. In addition, we can scope the cloud integration to all resource groups in the region (All) or can select a specific resource group to limit HPE Morpheus Enterprise resource inventorying and creation to just that resource group.
+
+By checking INVENTORY EXISTING INSTANCES, HPE Morpheus Enterprise will automatically onboard existing cloud resources which are scoped to the region and resource group indicated. If this box is checked, we will also need to select either basic inventorying, which syncs name, IP addresses, platform types, power status, and sizing data (storage, CPU, and RAM) OR full (API heavy) inventorying which syncs resource utilization metrics (storage, CPU, and RAM) when available in addition to what we get with basic inventorying.
+
+To move on, expand the “Advanced Options” section.
+
+NOTE
+
+CSP accounts will also need to enter CSP TENANT ID, CSP CLIENT ID, and CSP CLIENT SECRET in the Advanced Options section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first Cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), **COSTING**, **DNS INTEGRATION**, **CMDB**, and **AGENT INSTALL MODE**.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” Groups if you wish to use the Group we configured earlier. Alternatively, you can create a new one here.
+
+![../../_images/3cloudGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0908B711-2897-4E7C-8C95-07D3BE88990B-high.png)
+
+Once you’ve selected or created the Group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new Cloud is now listed on the Cloud list page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the Cloud.
+
+#### Viewing Cloud Inventory
+
+Now that we’ve integrated our first Azure cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the Cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+#### Configuring Resource Pools
+
+With our Azure Cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  Resources tab. In here, we are able to see and control access to the various resource pools that have been configured in Azure. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise if it is not configured as active.
+
+![../../_images/4resourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7380FEF7-F20E-43FE-B217-9597FD1569DE-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any Group we’d like. We can also choose to make some or all of our resource pools available to every Group. Specific resource pools can also be defined as the default for each Group when needed.
+
+![../../_images/5resourcePoolGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BDAD86D8-81F9-4622-BB7D-FE2E1FCEFC1E-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+#### Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “Resources” tab to the “Data Stores” tab on our Cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![../../_images/6dataStore.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-971BB5E6-79F2-4447-9227-2000EAB24BEF-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific Groups. This ensures that the members of each Group are only able to consume the data stores they should have access to.
+
+#### Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all Clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific Cloud detail page so that networks from other Clouds are not shown.
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+Since this guide is focused on working within an Azure cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain Groups or Tenants.
+
+![../../_images/7cloudNetworks.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EB96C871-9B00-4B7B-9BBD-6800427665D5-high.png)
+
+#### Provisioning Your First Instance
+
+At this point, the groundwork is laid and we are ready to attempt our first new provisioning. As a first Instance, we’ll provision an Apache web server to our Azure cloud. HPE Morpheus Enterprise includes a very robust catalog of pre-configured Instance types. We’ll use one of these included catalog items for this guide but you’ll likely also need to prep your own custom images and Instance types to make available to your users. Much more on this can be found elsewhere in HPE Morpheus Enterprise documentation.
+
+Navigate to |ProIns|. If any Instances are currently provisioned, we will see them listed here. To start a new Instance we click + ADD to open the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/8createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-82D93BA5-71D0-4A63-9DBA-C13AE6E3C395-high.png)
+
+First, we’ll specify the Group to provision into which determines the Clouds available. If you’ve followed this guide to this point, you should at least have a Group that houses all of your Clouds which you can select here. This will allow us to select the Azure cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating Instances and available options is [here](https://docs.morpheusdata.com/en/latest/provisioning/instances/instances.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+![../../_images/9configureInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E9D875CD-D6C4-4D20-AD60-767C3A47671E-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your HPE Morpheus Enterprise user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click NEXT to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the Instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the Instance in the list to move to the Instance detail page. For now we will see a progress bar indicating that the Instance is being created and is starting up. The exact amount of time this process will take depends on selections made when provisioning the Instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the Instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+#### Creating Your First Library Item
+
+In the prior section, we manually provisioned our first Instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick Instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a HPE Morpheus Enterprise-provided image, you’ll want to ensure it’s configured. You will not be able to complete this section without selecting an available image. In this example we will use a CentOS image that was previously configured in the HPE Morpheus Enterprise library. If you need to configure your own images prior to starting this section, navigate to Library > Virtual Images and click + ADD. A deeper dive into image prep and virtual image configuration goes beyond the scope of this guide.
+
+Provisionable elements in HPE Morpheus Enterprise combine a Node Type(s), Layout(s), and an Instance Type. The [Overview section](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#overview) of HPE Morpheus Enterprise docs discusses these objects and how they work together in greater detail. Our first step here will be to create a Node Type which wrap the image itself with additional configuration, templates, and scripts. While not strictly required, creating the Node Type, Instance Type, and then the Layout is often a good workflow for creating Library items. That is the order we will follow in this guide.
+
+Navigate to Library > Blueprints > Node Types and click + ADD
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**: Example Azure CentOS 7
+- **SHORT NAME**: eac7 (Identifies the Node Type in HPE Morpheus Enterprise API/CLI)
+- **VERSION**: 7 (Ensures the correct Node Types are used when tying Layouts with multiple images to the same Instance Type)
+- **TECHNOLOGY**: Azure
+- **VM IMAGE**: Azure-Centos-7
+
+Click SAVE CHANGES
+
+![../../_images/10addNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A92C3DF6-A4AF-4C9E-8DFD-0ADC4CCEDC48-high.png)
+
+With the new Node Type created, we’ll now add a new Instance type which will be accessible from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click + ADD.
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click SAVE CHANGES. You could also provide a description, icon, and category for easier identification from the provisioning wizard later.
+
+![../../_images/11addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E5B46F39-E1FE-4EDF-9C6B-348A60C37A00-high.png)
+
+Now that we’ve created a new Instance type, access it by clicking on the name in the list of custom Instances you’ve created. In my case, I’ve given the name “Example Azure CentOS 7”.
+
+Once we’ve opened the new Instance type, by default, we should be on the “LAYOUTS” tab. Click + ADD LAYOUT. I’ve set the following fields on my example layout:
+
+- **NAME**: Example Azure CentOS 7
+- **VERSION**: 7 (This is the version number of the layout itself, which is labeled 7 in the example)
+- **TECHNOLOGY**: Azure
+- **Nodes**: Select the Node Type we created earlier, if desired you can specify multiple nodes
+
+Click SAVE CHANGES.
+
+![../../_images/12addLayout.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D60CF065-8C8D-4F3F-8068-61523120D1FE-high.png)
+
+At this point we’ve completed the setup work and can now provision the Instance we’ve created to our specifications. Navigate to |ProIns| and click + ADD. From the search bar we can search for the new Instance type we’ve created.
+
+![../../_images/13createCustomInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C1C05D91-5824-4DAD-8132-CF4EF2D46BD6-high.png)
+
+As before, we can select a Group and Cloud to provision this new Instance. Click NEXT. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new Instance type. Select a network and click NEXT. Once again we will also click NEXT through the “AUTOMATION” tab. Finally, click COMPLETE.
+
+As before when we provisioned a pre-existing Instance from the default catalog, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on the configuration and environmental factors but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the provisioning process has completed, open the Instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available, assuming the image and your custom catalog item were configured to seed user accounts and connect back to the HPE Morpheus Enterprise appliance.
+
+#### Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A Task could be a script added directly, scripts or Blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of Task types can be found in the [Automation section](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a Task, add the Task to a Workflow, and run the Workflow against a new and existing Instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click +NEW INTEGRATION and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus/-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE HPE Morpheus Enterprise AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus/-ansible-example.git.
+
+Click SAVE CHANGES. You’ll now see our new Ansible integration listed among any other configured integrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click + ADD. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+Now that we have a Workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring an instance to your needs. There are a number of other automation types that can be built into your Workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+#### Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume Azure public cloud. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/latest/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json b/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
new file mode 100644
index 0000000..1b3a197
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+  "title": "Requirements",
+  "ordinal": 172,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md b/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
new file mode 100644
index 0000000..3cc440c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json b/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
new file mode 100644
index 0000000..b6e604b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+  "title": "Overview",
+  "ordinal": 43,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md b/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
new file mode 100644
index 0000000..5bd67fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
@@ -0,0 +1,9 @@
+# Overview
+
+The HPE Morpheus Enterprise Agent is an important and powerful facet of HPE Morpheus Enterprise as an orchestration tool. Though it is not required, which is one unique capability of our platform versus some of our competitors, it is recommended for use as it brings many benefits. Not only does it provide statistics for the guest operating system and resource utilization, it also brings along with it monitoring and log aggregation capabilities. After an initial brownfield discovery, Users can decide to convert unmanaged VMs to managed.
+
+NOTE
+
+**Agent installation is not required to manage an Instance.** If you don’t have the Agent installed, we make every effort to aggregate stats. These will vary based on the Cloud and can be more limited or less accurate without utilizing HPE Morpheus Enterprise Agent.
+
+The HPE Morpheus Enterprise Agent is very lightweight and secure. It does not open any inbound network ports but rather only opens an outbound connection back to the HPE Morpheus Enterprise appliance over port 443 (HTTPS or WSS protocol). This allows for a bidirectional command bus where instructions can be sent to orchestrate a workload without needing access to things like SSH or WinRM. The tool can even be installed at provision time via technologies like Cloud-Init, such that the HPE Morpheus Enterprise appliance itself doesn’t even need direct network access to the VLAN under which the workload resides. By doing this we address many of the network security concerns that come with the use of an agent while demonstrating its security and analytics benefits. We can even use this statistical data at the guest OS level rather than the hypervisor level to provide extremely precise right-sizing recommendations.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json b/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
new file mode 100644
index 0000000..5c39a13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+  "title": "Operating Systems",
+  "ordinal": 165,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html",
+  "topic_cluster": {
+    "clustering_title": "Operating Systems",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md b/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
new file mode 100644
index 0000000..82afa61
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
@@ -0,0 +1,45 @@
+# Operating Systems
+
+Out of the box, many Operating Systems (also referred to as OS types) are seeded into HPE Morpheus Enterprise by default. OS types can be set on Virtual Images when they are created. If you don’t use any other features of OS types described here, they are still useful to set on Virtual Images to ensure only Workflows designed for the platform can be run against workloads provisioned from the image. It can also help ensure certain types of reporting and dashboard metrics are correct.
+
+IMPORTANT
+
+It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration. Read this section in full for complete detail on the use cases for the Operating System construct.
+
+## Permissions
+
+Access to Operating Systems is controlled by the `Library: Operating Systems` feature permission. Access levels are as follows:
+
+- **FULL:** Access to view, create, and edit Operating Systems
+- **READ:** Access to view Operating Systems only
+- **NONE:** No access to the Operating Systems section of the UI
+
+## Use Cases
+
+OS types can primarily be used in one of two use cases. The first is adding your own images to existing OS types. The upshot of doing this is to use built-in Instance Types (for example, the “UBUNTU” Instance Type) while replacing the included default images with your own gold master images for some or all provisioning technologies.
+
+View the existing OS types by navigating to Library > OperatingSystems. Here, a list of all OS types is shown. If this is a brand new appliance or if you’ve never added new Operating Systems, all shown here will be system default OS types. By clicking into any of the OS types for which HPE Morpheus Enterprise currently provides default images, you will see all of the Virtual Images for that OS type and the provisioning technology each image is compatible with.
+
+![../../_images/listOsImages.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-47C7B1DB-2DE5-4A66-B1A9-EAFC3B87601B-high.png)
+
+To add an existing Virtual Image to the currently-selected OS type, click + ADD. Select the image and optionally identify a provisioning technology or even a specific Cloud. When finished, click SAVE.
+
+NOTE
+
+When adding a Virtual Image to an OS type, only Virtual Images that have been saved with the same OS type (Operating System) configuration will be shown in the typeahead list.
+
+![../../_images/addOsImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-84DB6665-2DF9-46C0-9DB1-623644B30196-high.png)
+
+Once images are associated with a built-in OS type, they will be used when the situation warrants (a compatible provisioning target is selected or the correct Cloud is chosen, depending on how the OS type image was configured). It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration.
+
+The second use case is to add your own Operating System. New Operating Systems can be added by navigating to Library > OperatingSystems and clicking + ADD. OS types can be configured with highly granular detail allowing environments with similar Os types to distinguish them.
+
+![../../_images/createOsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-436A53AF-DF69-439A-83EE-7F9AB7045072-high.png)
+
+After creating the OS type, any new or existing Virtual Images can be associated to the newly created Operating System (Library > Virtual Images). Once Virtual Images have the Operating System association, you can return to the OS type and complete the association with the Operating System by clicking into the OS type and clicking + ADD.
+
+Once you have a custom Operating System loaded with your own gold master images, the OS type can be used with new Node Types going forward. To see how this works, navigate to Library > Blueprints > Node Types and click + ADD. Change the default technology for a new Node Type from the default “Docker” value to another technology, such as “VMware”. Notice that the option is given to associate the Node Type with either a specific image or with an OS type. By selecting an OS type, the Node Type will select the appropriate image at provision time based on technology and/or Cloud filters.
+
+![../../_images/createNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D7231A7E-44FC-46F2-BF5A-99020D46CF48-high.png)
+
+It’s important to note that more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Additionally, only one user image can be added per Operating System with an identical technology and/or Cloud configuration.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json b/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
new file mode 100644
index 0000000..38f1d08
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+  "title": "Importing HPE ProLiant Bare Metal Servers",
+  "ordinal": 415,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html",
+  "topic_cluster": {
+    "clustering_title": "Importing HPE ProLiant Bare Metal Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md b/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
new file mode 100644
index 0000000..fd9fc97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
@@ -0,0 +1,31 @@
+# Importing HPE ProLiant Bare Metal Servers
+
+## About this task
+
+Perform the following procedure to import HPE ProLiant Bare Metal Servers:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute, then select the Bare Metal tab.
+2. Click the + Bare Metal button, then select HPE Server.
+3. Select the Group you created earlier from the drop-down list and click Next.   
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-64D4C0D9-B1A4-4257-A316-81069FC4EF3A-high.png)
+4. Enter a Name for the server and click Next.   
+   ![Name](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B361D956-0808-4F91-9D2F-87F840898005-high.png)
+5. Enter the following iLO (Integrated Lights Out) details for the server:
+
+   - iLO IP Address
+   - iLO Username (typically "Administrator")
+   - iLO Administrator Password  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C4D9169E-91C8-4F6D-841A-B8DE6DAB8824-high.png)
+6. Leave the Pre-Provisioned Server option unselected, then click Next.
+7. Click Next to review your host configuration details.
+8. Click Complete to finalize the host creation.   
+   ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DB572274-C1F6-4461-9594-5436E0CBE9AB-high.png)  
+
+   The below image shows list of clouds available.   
+   ![clouds](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8F3FE3ED-1AEB-4AD5-808A-D9C7C54B1308-high.png)
+
+## Results
+
+the HPE ProLiant Bare Metal plugin automatically discovers and records all hardware details from the server using its Integrated Lights Out (iLO) management interface. This discovery process may take a few minutes, depending on the server and network conditions. After completion, the server becomes available (STATUS = `available`) in Morpheus for further provisioning and lifecycle operations.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json b/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
new file mode 100644
index 0000000..a488af3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+  "title": "Single Node/AIO Appliance Upgrades",
+  "ordinal": 22,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node/AIO Appliance Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md b/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
new file mode 100644
index 0000000..7279fdb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
@@ -0,0 +1,55 @@
+# Single Node/AIO Appliance Upgrades
+
+IMPORTANT
+
+Only appliances running Morpheus v6.0.0 or higher can upgrade to v8.1.0. Always backup your database before running any upgrade.
+
+The following covers upgrading Single Node or AIO (All-In-One) Appliance configurations.
+
+## Debian / Ubuntu
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on Ubuntu/Debian, download new deb package from My HPE Software Center and transfer it to your application node, stop the morpheus-ui, install the new deb package, then reconfigure.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
+
+## CentOS / RHEL / Amazon / SLES
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on CentOS, RHEL, Amazon or SLES, download the upgrade package from My HPE Software Center, transfer it to your application node, install the new rpm package, stop the morpheus-ui, reconfigure and then start the morpheus-ui:
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json b/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
new file mode 100644
index 0000000..0194a49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+  "title": "Script Templates",
+  "ordinal": 161,
+  "parent_title": "Templates",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html",
+  "topic_cluster": {
+    "clustering_title": "Script Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md b/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
new file mode 100644
index 0000000..46032ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
@@ -0,0 +1,75 @@
+# Script Templates
+
+Scripts are bash and Powershell scripts that can be attached to Node Types to always execute at the selected phase when that Node Type is provisioned, added to Workflows as Library Script Tasks, and/or executed ad-hoc on Instances.
+
+## Creating Scripts
+
+### Procedure
+
+1. Navigate to Library > Templates > Script Templates
+2. Select + ADD
+3. Enter the Following: 
+
+   NAME
+   :   Name of the Script in HPE Morpheus Enterprise
+
+   SCRIPT TYPE
+   :   - Bash
+       - Powershell
+
+   PHASE
+   :   Select which phase the Script will execute when attached to a Node Type. When a script is attached to a Node Type, it will execute according to the selcted phase:
+
+       Start Service
+       :   Any time the Instance action `Start Service` is executed
+
+       Stop Service
+       :   Any time the Instance action `Stop Service` is executed
+
+       Pre-Provision
+       :   - Containers: Script will execute against the container host before the container is provisioned
+           - Virtual Machines: Script will execute before any provision phase Scripts or Tasks
+
+       Provision
+       :   Script will execute once per new Instance node during the provision Phase. Provisioning will not be considered complete until all scripts and tasks in the provisioning phase are completed
+
+           NOTE
+
+           Any Script or Task set to the provision phase will be included in the total provision time and impact success/warn/failure provisioning status messages. As an example, your VM could be up and running but if your Script is in the provision phase and fails, provisioning will be marked as a failure.
+
+           Post-Provision
+           :   Script will execute once per new Instance node after the provision phase is completed. Scripts and Tasks in the Post-Provision phase will show execution status and history, but are not considered part of the provision and do not impact provisioning status.
+
+           Pre-Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The Script will run prior to the deployment file(s) being written
+
+           Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The script will run after the deployment file(s) are written
+
+           Reconfigure
+           :   Script will execute on target Instance any time a reconfigure is executed against the Instance.
+
+           Teardown
+           :   Script will execute on target Instance upon Instance deletion. Script will execute against target Instance prior to the deletion/removal of resources.
+
+   SCRIPT
+   :   Enter Bash or Powershell script.
+
+       NOTE
+
+       HPE Morpheus Enterprise variables are supported in Library Scripts using `<%= variable.var %>` format
+
+   RUN AS USER
+   :   By default Scripts are execute as `morpheus-node`. To execute as another User, populate `RUN AS USER` and ensure proper user permissions & group access
+
+   SUDO
+   :   Flag `SUDO` if sudo is required to execute the Script
+
+### Results
+
+To attach Scripts and templates that have been added to the Library to a Node Type, start typing the name and then select the script(s) and/or template(s).
+
+- Multiple scripts and templates can be added to a Node Type
+- Scripts and Templates can be added/shared among multiple Node Types
+- The execution phase can be set for Scripts in the Scripts section
+- Search will populate Scripts or Templates containing the characters entered anywhere in their name, not just the first letter(s) of the name
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json b/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
new file mode 100644
index 0000000..2ae688a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+  "title": "Git",
+  "ordinal": 480,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html",
+  "topic_cluster": {
+    "clustering_title": "Git",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md b/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
new file mode 100644
index 0000000..9547d74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
@@ -0,0 +1,26 @@
+# Git
+
+Git Repository integrations allow integration of public or private Git repositories in Github, GitLab or other services. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Each time code from your repositories is invoked, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Creating an Integration
+
+### About this task
+
+New Git integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need an access code for authentication with private repositories, public repositories can be integrated simply with a URL.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Git repository
+4. Configure the following: 
+
+   - NAME: A friendly name for the Git repository integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, code in this repository will be available for creating automation or other HPE Morpheus Enterprise constructs
+   - DEFAULT BRANCH: The default repository branch from which code should be sourced
+   - USERNAME: For private repositories, enter an account name (such as a Github username)
+   - PASSWORD: For Github and GitLab, password authentication is no longer supported but access tokens should go in this field.
+   - ACCESS TOKEN: Currently an unused field, access tokens should go in the Password field
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json b/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
new file mode 100644
index 0000000..8c8cbc0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+  "title": "EKS Clusters",
+  "ordinal": 199,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html",
+  "topic_cluster": {
+    "clustering_title": "EKS Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md b/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
new file mode 100644
index 0000000..25c485a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
@@ -0,0 +1,64 @@
+# EKS Clusters
+
+Provisions a new Elastic Kubernetes Service (EKS) Cluster in target AWS Cloud.
+
+NOTE
+
+EKS Cluster provisioning is different than creating a Kubernetes Cluster type in AWS EC2, which creates EC2 instances and configures Kubernetes, outside of EKS.
+
+HPE Morpheus Enterprise currently supports EKS in the following regions: `us-east-2`, `us-east-1`, `us-west-1`, `us-west-2`, `af-south-1`, `ap-east-1`, `ap-south-1`, `ap-northeast-3`, `ap-northeast-2`, `ap-southeast-1`, `ap-southeast-2`, `ap-northeast-1`, `ca-central-1`, `eu-central-1`, `eu-west-1`, `eu-west-2`, `eu-south-1`, `eu-west-3`, `eu-north-1`, `me-south-1`, `sa-east-1`, `us-gov-east-1`, `us-gov-west-1`
+
+## Create an EKS Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `EKS Cluster`
+4. Populate the following: 
+
+   LAYOUT
+   :   Select server layout for EKS Cluster
+
+   PUBLIC IP
+   :   Subnet Default
+       :   Use AWS configured Subnet setting for Public IP assignment
+
+       Assigned EIP
+       :   Assigned Elastic IP to Controller and Worker Nodes. Requires available EIP’s
+
+   CONTROLLER ROLE
+   :   Select Role for EKS Controller from synced role list
+
+   CONTROLLER SUBNET
+   :   Select subnet placement for EKS Controller
+
+   CONTROLLER SECURITY GROUP
+   :   Select Security Group assignment for EKS Controller
+
+   WORKER SUBNET
+   :   Select Subnet placement for Worker Nodes
+
+   WORKER SECURITY GROUP
+   :   Select Security Group assignment for Worker Nodes
+
+   WORKER PLAN
+   :   Select Service Plan (EC2 Instance Type) for Worker Nodes
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json b/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
new file mode 100644
index 0000000..62020ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+  "title": "User Role Permission Sections",
+  "ordinal": 296,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html",
+  "topic_cluster": {
+    "clustering_title": "User Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md b/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
new file mode 100644
index 0000000..ab36200
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
@@ -0,0 +1,34 @@
+# User Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Instance Types
+:   Controls User access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls User access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls User access for each report type in the Reports section (Operations > Reports). The user must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls User access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters)
+
+VDI Pools
+:   Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json b/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
new file mode 100644
index 0000000..89b51dc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+  "title": "Image Builder",
+  "ordinal": 265,
+  "parent_title": "Tools",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html",
+  "topic_cluster": {
+    "clustering_title": "Image Builder",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md b/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
new file mode 100644
index 0000000..8c767f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
@@ -0,0 +1,130 @@
+# Image Builder
+
+The Morpheus Image Builder tool creates vmdk, qcow2, vhd and raw Images from scratch. The Image Builder creates a blank VM in VMware, attaches an os iso, executes a boot script on the VM at startup via VNC which calls a preseed script which runs the unattended os installation and configuration. Morpheus then executes an ova export of the completed vmdk to target Storage provider, and converts the image to all other specified formats. The new Virtual Image records are automatically added to Morpheus and the Images are then available for use.
+
+## Requirements
+
+- DHCP must be enabled on the network specified for the VM in Morpheus, and network settings configured for DHCP in Morpheus
+  :   The blank VM must get network configuration via DHCP upon boot. Static IP assignment is not possible.
+- Hypervisor Console must be enabled on the Target Cloud
+  :   Morpheus utilizes VNC to pass the boot script to the VM.
+- VM must be able to reach and resolve the Morpheus appliance url over 443
+  :   The boot script calls to the Morpheus appliance to get the preseed script.
+- Valid Linux iso set for the Virtual Image. Windows is not supported.
+  :   The iso can exist in the target cloud or uploaded to Morpheus
+
+      NOTE
+
+      `cloud-init enabled` must be disabled on the iso Virtual Image settings.
+- Access to target ESXi host(s) over 443 and ESXi hostname dns resolution
+  :   - Same requirement as Hypervisor Console and Image upload/download to/from vCenter.
+- Valid Boot Script
+- Valid Pre-seed script
+- Valid Storage Provider configure for ova export of generated image.
+
+## Sample Scripts
+
+### Sample Boot Script
+
+```
+```
+<wait5><tab> text ks=<%=preseedUrl%><enter>
+```
+```
+
+NOTE
+
+`<%=preseedUrl%>` is a Morpheus variable that will populate with the Morpheus appliance url.
+
+### Sample Preseed Script
+
+```
+```
+# CentOS 7.x kickstart file - ks.cfg  
+#  
+# For more information on kickstart syntax and commands, refer to the  
+# CentOS Installation Guide:  
+# https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html  
+#  
+# For testing, you can fire up a local http server temporarily.  
+# cd to the directory where this ks.cfg file resides and run the following:  
+#    $ python -m SimpleHTTPServer  
+# You don't have to restart the server every time you make changes.  Python  
+# will reload the file from disk every time.  As long as you save your changes  
+# they will be reflected in the next HTTP download.  Then to test with  
+# a PXE boot server, enter the following on the PXE boot prompt:  
+#    > linux text ks=http://<your_ip>:8000/ks.cfg  
+# Required settings  
+lang en_US.UTF-8  
+keyboard us  
+rootpw password  
+authconfig --enableshadow --enablemd5  
+timezone UTC  
+# Optional settings  
+install  
+cdrom  
+user --name=cloud-user --plaintext --password password  
+unsupported_hardware  
+network --bootproto=dhcp  
+firewall --disabled  
+selinux --permissive  
+bootloader --location=mbr --append="biosdevname=0 net.ifnames=0"  
+text  
+skipx  
+zerombr  
+clearpart --all --initlabel  
+autopart --type=plain  
+firstboot --disabled  
+reboot  
+%packages --nobase --ignoremissing --excludedocs  
+openssh-clients  
+# Prerequisites for installing VMware Tools guest additions.  
+# Put in kickstart to ensure first version installed is from install disk,  
+# not latest from a mirror.  
+kernel-headers  
+kernel-devel  
+gcc  
+make  
+perl  
+curl  
+wget  
+bzip2  
+dkms  
+patch  
+net-tools  
+git  
+# Core selinux dependencies installed on 7.x, no need to specify  
+# Other stuff  
+sudo  
+nfs-utils  
+open-vm-tools  
+-fprintd-pam  
+-intltool  
+-biosdevname  
+# unnecessary firmware  
+-aic94xx-firmware  
+-atmel-firmware  
+-b43-openfwwf  
+-bfa-firmware  
+-ipw*-firmware  
+-irqbalance  
+-ivtv-firmware  
+-iwl*-firmware  
+-libertas-usb8388-firmware  
+-ql*-firmware  
+-rt61pci-firmware  
+-rt73usb-firmware  
+-xorg-x11-drv-ati-firmware  
+-zd1211-firmware  
+%end  
+%post  
+# configure vagrant user in sudoers  
+echo "%cloud-user ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers.d/cloud-user  
+chmod 0440 /etc/sudoers.d/cloud-user  
+cp /etc/sudoers /etc/sudoers.orig  
+sed -i "s/^\(.*requiretty\)$/#\1/" /etc/sudoers  
+# keep proxy settings through sudo  
+echo 'Defaults env_keep += "HTTP_PROXY HTTPS_PROXY FTP_PROXY RSYNC_PROXY NO_PROXY"' >> /etc/sudoers  
+%end
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json b/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
new file mode 100644
index 0000000..0796906
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+  "title": "AzureStorage",
+  "ordinal": 519,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html",
+  "topic_cluster": {
+    "clustering_title": "AzureStorage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md b/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
new file mode 100644
index 0000000..5fa5a13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
@@ -0,0 +1,30 @@
+# AzureStorage
+
+## To Add Azure Storage
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Storage
+2. Select + ADD
+3. From the New Storage Provider Wizard input the following: 
+
+   Name
+   :   Name of the storage provider.
+
+   Provider Type
+   :   Azure
+
+   Storage Account
+   :   Add Storage Account
+
+   Storage Key
+   :   Add Storage Key
+
+   Share Name
+   :   Add Share Name
+
+   Targets
+   :   - Default Backup Target
+       - Default Deployment Archive Target
+       - Default Virtual Image Store
+4. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json b/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
new file mode 100644
index 0000000..eb4d7f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+  "title": "Network Management",
+  "ordinal": 428,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md b/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
new file mode 100644
index 0000000..28f9549
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
@@ -0,0 +1,16 @@
+# Network Management
+
+At a high level, there are two network modes in which a cloud can be configured to operate:
+
+- Unmanaged network mode (`Unmanaged`).
+- Managed network mode (`ArubaCX-Int`).
+
+Network modes are created during cloud creation.
+
+![Network Mode](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-876273B4-9A6A-4398-B541-2C7FEE1F1A25-high.png)
+
+**Subtopics**  
+
+- **[Unmanaged Networks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html)**
+- **[Managed Networks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html)**
+- **[Networks Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json b/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
new file mode 100644
index 0000000..132c64a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+  "title": "Uninstall HPE Morpheus Enterprise Agent",
+  "ordinal": 49,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html",
+  "topic_cluster": {
+    "clustering_title": "Uninstall HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md b/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
new file mode 100644
index 0000000..fb06012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
@@ -0,0 +1,37 @@
+# Uninstall HPE Morpheus Enterprise Agent
+
+## Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+## Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json b/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
new file mode 100644
index 0000000..f1605bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+  "title": "Add NSX load balancer",
+  "ordinal": 501,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md b/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
new file mode 100644
index 0000000..5a3c420
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
@@ -0,0 +1,34 @@
+# Add NSX load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX lb](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D2AD8017-CB76-4284-91AE-2514167985CA-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   OPTIONS
+   :   **ENABLED**: Select this option to enable the NSX for the integration.
+   :   **ADMIN STATE**: Select this option to switch to admin state.
+
+   SIZE
+   :   From the drop-down list, select the size of the NSX to be provisioned.
+
+   TIER-1 GATEWAYS
+   :   From the drop-down list, select the Tier-1 gateway.
+
+   LOG LEVEL
+   :   From the drop-down list, select the log level for the logs.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json b/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
new file mode 100644
index 0000000..2cf9b6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+  "title": "Managing Apps",
+  "ordinal": 89,
+  "parent_title": "Apps",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md b/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
new file mode 100644
index 0000000..dc7be67
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
@@ -0,0 +1,85 @@
+# Managing Apps
+
+## App Status
+
+App Status is determined by the status of the Instances within the App or by the DELETE action. All Instances in an App must be in ‘Running’ status for the App status to equal ‘Running’.
+
+Table 1. App Statuses
+
+     | Status Icon | App Status | Status Reason |
+| --- | --- | --- |
+| ../../_images/running_icon.svg | Running | All Instance Statuses = Running |
+| ../../_images/failed_icon.svg | Failed | Any Instance Status = Failed |
+| ../../_images/pending_icon.svg | Pending | Any Instance Status = Pending |
+| ../../_images/pendingRemoval_icon.svg | Pending Removal | Any Instance Status = Pending Removal |
+| ../../_images/deploying_icon.svg | Provisioning | Any Instance Status = Provisioning |
+| ../../_images/removing_icon.svg | Removing | The DELETE action was trigger on the App |
+| ../../_images/unknown_icon.svg | Unknown | Any Instance Status = Unknown, or the App is empty |
+
+## Editing an App
+
+### About this task
+
+The EDIT action allows permissioned users to update an Apps metadata, Environment, Group and Owner.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select EDIT
+4. Update the following 
+
+   NAME
+   :   App Name
+
+   DESCRIPTION
+   :   App Description
+
+   ENVIRONMENT
+   :   App Environment
+
+   GROUP
+   :   App Group assignment
+
+   OWNER
+   :   User assigned as Owner of the App
+5. Select SAVE CHANGES
+
+## Deleting an App
+
+### About this task
+
+The DELETE action allows permissioned users to delete an App and, by default, all Instances within the App.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select DELETE
+4. The DELETE APP? confirmation modal will be displayed: 
+
+   Remove Instances
+   :   Deletes all Instances associated with the App - Enabled by Default
+
+   Preserve Backups
+   :   Preserves Backups of the Instances associated with the App - Disabled by Default
+
+   Preserve Volumes
+   :   Preserves Storage Volumes of the Instances associated with the App - Disabled by Default
+
+   Force Delete
+   :   Forces deletion of the App - Required when any Instances associated with the App are in “provisioning” state - WARNING Force deleting may cause orphaned infrastructure or resources. - Disabled by Default
+5. Select DELETE to proceed with deleting the App, or CANCEL to abort the delete action.
+
+## Exporting Configuration JSON
+
+### About this task
+
+To export an App Blueprint as JSON:
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select ACTIONS > Export
+4. The App export file will be downloaded to your computer as `{app_name}.json`
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json b/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
new file mode 100644
index 0000000..cfa601f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+  "title": "Compute Management",
+  "ordinal": 399,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html",
+  "topic_cluster": {
+    "clustering_title": "Compute Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md b/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
new file mode 100644
index 0000000..872d931
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
@@ -0,0 +1,22 @@
+# Compute Management
+
+The topic section describes how HPE Morpheus Enterprise orchestrates on-premises and HPE BMaaS Cloud resources. It covers the end-to-end lifecycle for physical servers, including installation, cloud configuration, on-boarding, and workload migration.
+
+Administrators perform the following tasks:
+
+- Define a Bare Metal Cloud
+- Configure unmanaged networks and resource pools
+- Import HPE ProLiant servers for centralized visibility
+- Manage greenfield (new) and brownfield (existing) server deployment
+- Convert Pre-Provisioned servers into managed HPE Morpheus instances
+
+Administrators use these procedures to enable consistent provisioning, lifecycle management, and governance for HPE ProLiant infrastructure within HPE Morpheus.
+
+**Subtopics**  
+
+- **[Adding HPE BMaaS Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html)**
+- **[Creating an HPE BMaaS Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html)**
+- **[Creating Resource Pools](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html)**
+- **[Image Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html)**
+- **[Provisioning a New Server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html)**
+- **[Importing Pre-Provisioned Server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json b/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
new file mode 100644
index 0000000..f7421ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+  "title": "Morpheus Agent OS Support",
+  "ordinal": 45,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent OS Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md b/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
new file mode 100644
index 0000000..f922ab4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
@@ -0,0 +1,119 @@
+# Morpheus Agent OS Support
+
+Table 1.
+
+           | Name | Bit Count | Category | Code | OS Family | OS Version | Platform | Vendor | Install Agent? |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Almalinux Linux 8 64‐bit | 64 | almalinux | almalinux.8.64 | almalinux | 8 | linux | almalinux | Yes |
+| Almalinux Linux 9 64‐bit | 64 | almalinux | almalinux.9.64 | almalinux | 9 | linux | almalinux | Yes |
+| amazon linux 2 64‐bit | 64 | amazonlinux | amazonlinux.2.64 | centos | 2 | linux | amazon | Yes |
+| centOS | 32 | centos | cent | rhel | all | linux | centos | Yes |
+| centOS 6 | 32 | centos | cent.6 | rhel | 6 | linux | centos | Yes |
+| centOS 6 64‐bit | 64 | centos | cent.6.64 | rhel | 6 | linux | centos | Yes |
+| centOS 64‐bit | 64 | centos | cent.64 | rhel | all | linux | centos | Yes |
+| centOS 7 | 32 | centos | cent.7 | rhel | 7 | linux | centos | Yes |
+| centOS 7 64‐bit | 64 | centos | cent.7.64 | rhel | 7 | linux | centos | Yes |
+| centOS 8 | 32 | centos | cent.8 | rhel | 8 | linux | centos | Yes |
+| centOS 8 64‐bit | 64 | centos | cent.8.64 | rhel | 8 | linux | centos | Yes |
+| centOS 8 Stream 64‐bit | 64 | centos | cent.8.stream.64 | rhel | 8 | linux | centos | Yes |
+| centOS 9 64‐bit | 64 | centos | cent.9.64 | rhel | 9 | linux | centos | Yes |
+| debian | 32 | debian | debian | debian | all | linux | debian | Yes |
+| debian 10 64‐bit | 64 | debian | debian.10.64 | debian | 10 | linux | debian | Yes |
+| debian 10.9 64‐bit | 64 | debian | debian.10.9.64 | debian | 10 | linux | debian | Yes |
+| debian 11 64‐bit | 64 | debian | debian.11.64 | debian | 11 | linux | debian | Yes |
+| debian 6 | 32 | debian | debian.6 | debian | 6 | linux | debian | Yes |
+| debian 6 64‐bit | 64 | debian | debian.6.64 | debian | 6 | linux | debian | Yes |
+| debian 64‐bit | 64 | debian | debian.64 | debian | all | linux | debian | Yes |
+| debian 7 | 32 | debian | debian.7 | debian | 7 | linux | debian | Yes |
+| debian 7 64‐bit | 64 | debian | debian.7.64 | debian | 7 | linux | debian | Yes |
+| debian 8 | 32 | debian | debian.8 | debian | 8 | linux | debian | Yes |
+| debian 8 64‐bit | 64 | debian | debian.8.64 | debian | 8 | linux | debian | Yes |
+| debian 9.13 64‐bit | 64 | debian | debian.9.13.64 | debian | 9 | linux | debian | Yes |
+| debian 9.4 64‐bit | 64 | debian | debian.9.4.64 | debian | 9 | linux | debian | Yes |
+| ESXi | 64 | esxi | esxi | NULL |  | ESXi | vmware | No |
+| ESXi 4 | 64 | esxi | esxi.4 | NULL | 4 | ESXi | vmware | No |
+| ESXi 5 | 64 | esxi | esxi.5 | NULL | 5 | ESXi | vmware | No |
+| ESXi 6 | 64 | esxi | esxi.6 | NULL | 6 | ESXi | vmware | No |
+| ESXi 7 | 64 | esxi | esxi.7 | NULL | 7 | ESXi | vmware | No |
+| ESXi 8 | 64 | esxi | esxi.8 | NULL | 8 | ESXi | vmware | No |
+| fedora | 32 | fedora | fedora | NULL | all | linux | fedora | Yes |
+| fedora 64‐bit | 64 | fedora | fedora.64 | NULL | all | linux | fedora | Yes |
+| linux | 64 | linux | linux | NULL | all | linux | linux | Yes |
+| linux 32‐bit | 32 | linux | linux.32 | NULL | all | linux | linux | No |
+| linux 64‐bit | 64 | linux | linux.64 | NULL | all | linux | linux | No |
+| mac os | 64 | mac | mac | darwin | all | osx | apple | Yes |
+| opensuse | 32 | opensuse | opensuse.32 | suse | all | linux | opensuse | Yes |
+| opensuse 15 64‐bit | 64 | opensuse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| opensuse 64‐bit | 64 | opensuse | opensuse.64 | suse | all | linux | opensuse | Yes |
+| oracle enterprise | 32 | oracle | oracle.32 | NULL | all | linux | oracle | Yes |
+| oracle enterprise 64‐bit | 64 | oracle | oracle.64 | NULL | all | linux | oracle | Yes |
+| oracle linux 64‐bit | 64 | oracle | oracle.linux.64 | NULL | all | linux | oracle | Yes |
+| oracle vm server | 64 | oracle | ovs | NULL | all | linux | oracle | No |
+| other 32‐bit | 32 | other | other.32 | NULL | all | other | other | No |
+| other 64‐bit | 64 | other | other.64 | NULL | all | other | other | No |
+| redhat | 32 | redhat | redhat | rhel | all | linux | redhat | Yes |
+| redhat 6 | 32 | redhat | redhat.6 | rhel | 6 | linux | redhat | Yes |
+| redhat 6 64‐bit | 64 | redhat | redhat.6.64 | rhel | 6 | linux | redhat | Yes |
+| redhat 64‐bit | 64 | redhat | redhat.64 | rhel | all | linux | redhat | Yes |
+| redhat 7 | 32 | redhat | redhat.7 | rhel | 7 | linux | redhat | Yes |
+| redhat 7 64‐bit | 64 | redhat | redhat.7.64 | rhel | 7 | linux | redhat | Yes |
+| redhat 8 | 32 | redhat | redhat.8 | rhel | 8 | linux | redhat | Yes |
+| redhat 8 64‐bit | 64 | redhat | redhat.8.64 | rhel | 8 | linux | redhat | Yes |
+| redhat 9 64‐bit | 64 | redhat | redhat.9.64 | rhel | 9 | linux | redhat | Yes |
+| Rocky Linux 8 | 32 | rocky | rocky.8 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 8 64‐bit | 64 | rocky | rocky.8.64 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 9 64‐bit | 64 | rocky | rocky.9.64 | rocky | 9 | linux | rocky | Yes |
+| solaris | 32 | solaris | solaris.32 | NULL | all | solaris | solaris | No |
+| solaris 64‐bit | 64 | solaris | solaris.64 | NULL | all | solaris | solaris | No |
+| suse enterprise | 32 | suse | suse | suse | all | linux | suse | Yes |
+| suse enterprise 11 | 32 | suse | suse.11 | suse | 11 | linux | suse | Yes |
+| suse enterprise 11 64‐bit | 64 | suse | suse.11.64 | suse | 11 | linux | suse | Yes |
+| suse enterprise 12 | 32 | suse | suse.12 | suse | 12 | linux | suse | Yes |
+| suse enterprise 12 64‐bit | 64 | suse | suse.12.64 | suse | 12 | linux | suse | Yes |
+| suse enterprise 15 | 32 | suse | suse.15 | suse | 15 | linux | suse | Yes |
+| suse enterprise 15 64‐bit | 64 | suse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| suse enterprise 64‐bit | 64 | suse | suse.64 | suse | all | linux | suse | Yes |
+| ubuntu | 32 | ubuntu | ubuntu | debian | all | linux | canonical | Yes |
+| ubuntu 12 | 32 | ubuntu | ubuntu.12.04 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 12 64‐bit | 64 | ubuntu | ubuntu.12.04.64 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 13 | 32 | ubuntu | ubuntu.13.10 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 13 64‐bit | 64 | ubuntu | ubuntu.13.10.64 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 14 | 32 | ubuntu | ubuntu.14.04 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 14 64‐bit | 64 | ubuntu | ubuntu.14.04.64 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 15 | 32 | ubuntu | ubuntu.15.10 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 15 64‐bit | 64 | ubuntu | ubuntu.15.10.64 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 16 | 32 | ubuntu | ubuntu.16.04 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 16 64‐bit | 64 | ubuntu | ubuntu.16.04.64 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 18.04 | 32 | ubuntu | ubuntu.18.04 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 18.04 64‐bit | 64 | ubuntu | ubuntu.18.04.64 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 20.04 | 32 | ubuntu | ubuntu.20.04 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 20.04 64‐bit | 64 | ubuntu | ubuntu.20.04.64 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 22.04 64‐bit | 64 | ubuntu | ubuntu.22.04.64 | debian | 22.04 | linux | canonical | Yes |
+| ubuntu 24.04 64‐bit | 64 | ubuntu | ubuntu.24.04.64 | debian | 24.04 | linux | canonical | Yes |
+| ubuntu 64‐bit | 64 | ubuntu | ubuntu.64 | debian | all | linux | canonical | Yes |
+| unknown | 64 | other | unknown | NULL | all | unknown | unknown | No |
+| windows | 64 | windows | windows | windows | all | windows | microsoft | Yes |
+| windows 10 | 32 | windows | windows.10 | windows | 10 | windows | microsoft | Yes |
+| windows 10 64‐bit | 64 | windows | windows.10.64 | windows | 10 | windows | microsoft | Yes |
+| windows 11 | 32 | windows | windows.11 | windows | 11 | windows | microsoft | Yes |
+| windows 11 64‐bit | 64 | windows | windows.11.64 | windows | 11 | windows | microsoft | Yes |
+| windows 7 | 32 | windows | windows.7 | windows | 7 | windows | microsoft | Yes |
+| windows 7 64‐bit | 64 | windows | windows.7.64 | windows | 7 | windows | microsoft | Yes |
+| windows 8 | 32 | windows | windows.8 | windows | 8 | windows | microsoft | No |
+| windows 8 64‐bit | 64 | windows | windows.8.64 | windows | 8 | windows | microsoft | Yes |
+| windows server 2003 | 64 | windows | windows.server.2003 | windows | 2003 | windows | microsoft | No |
+| windows server 2008 | 64 | windows | windows.server.2008 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2008 R2 | 64 | windows | windows.server.2008.r2 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2012 | 64 | windows | windows.server.2012 | windows | 2012 | windows | microsoft | Yes |
+| windows server 2016 | 64 | windows | windows.server.2016 | windows | 2016 | windows | microsoft | Yes |
+| windows server 2019 | 64 | windows | windows.server.2019 | windows | 2019 | windows | microsoft | Yes |
+| windows server 2022 | 64 | windows | windows.server.2022 | windows | 2022 | windows | microsoft | Yes |
+| windows server 2025 | 64 | windows | windows.server.2025 | windows | 2025 | windows | microsoft | Yes |
+| xen server 6.1 | 64 | xen | xenserver.6.1 | xen | 6.1 | linux | xen | No |
+| xen server 6.2 | 64 | xen | xenserver.6.2 | xen | 6.2 | linux | xen | No |
+| xen server 6.5 | 64 | xen | xenserver.6.5 | xen | 6.5 | linux | xen | No |
+| xen server 7.0 | 64 | xen | xenserver.7.0 | xen | 7.0 | linux | xen | No |
+
+NOTE
+
+Other Operating System types may be supported but are not tested.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json b/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
new file mode 100644
index 0000000..a13e290
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+  "title": "Known Limitations and Operational Considerations",
+  "ordinal": 456,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html",
+  "topic_cluster": {
+    "clustering_title": "Known Limitations and Operational Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md b/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
new file mode 100644
index 0000000..ae31592
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
@@ -0,0 +1,7 @@
+# Known Limitations and Operational Considerations
+
+Table 1. Known Limitations and Operational Considerations
+
+        | S.No | Topic | Description | Impact | Applicability | Operational Guidance |
+| --- | --- | --- | --- | --- | --- |
+| 1 | SATA Controller Initialization Delay During Importing HPE ProLiant Bare Metal Servers | During the bare-metal server import and hardware discovery process, if a server has one or more SATA controllers with no attached SATA disks, the system waits a minimum of **5 minutes per SATA controller** before continuing.  The wait time is cumulative and applies to each SATA controller detected without attached disks.  This behavior occurs during the initial hardware probing phase, before the server becomes available for provisioning in Morpheus. | 1. Increased time to complete bare-metal server discovery, import, and provisioning. 2. Delay proportional to the number of SATA controllers present without disks. 3. No impact once the server import process has completed. 4. No impact when SATA controllers have SATA disks attached. | This condition is typically observed in **lab** or **evaluation** environments where SATA controllers may be present but not populated with disks.  Standard **production** deployments are not expected to include unused SATA controllers. | Disabling an Embedded SATA Controller (HPE ProLiant)   1. Reboot the server. 2. Press **F9** to enter **System Utilities**. 3. Navigate to:  **System Configuration** → **BIOS/Platform Configuration (RBSU)** → **PCIe Device Configuration**. 4. For **each** embedded SATA controller that is not in use:     - Select the controller (for example, Embedded SATA Controller #1).    - Change the **SATA Device Disable** from **Auto** to **Disabled**. 5. Press F12 to save the changes and exit, followed by reboot. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json b/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
new file mode 100644
index 0000000..5664533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+  "title": "Zerto",
+  "ordinal": 385,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-66740846-A143-48D1-80FF-7314D86BE61A.html",
+  "topic_cluster": {
+    "clustering_title": "Zerto",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md b/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
new file mode 100644
index 0000000..dbf3a6d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
@@ -0,0 +1,56 @@
+# Zerto
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+## Overview
+
+By integrating HPE Morpheus Enterprise and Zerto, HPE Morpheus Enterprise will automatically bring in your pre-existing Zerto replication groups as well as allow you to create and edit replication groups from within HPE Morpheus Enterprise UI. Additionally, the Zerto integration can be set as the replication provider to existing compatible Clouds (such as VMware vCenter Clouds) to allow new workloads to be added to replication groups. If needed, new replication groups can also be created at provision time with the newly provisioned VMs added to them. The Zerto integration detail page also provides summary details for the integration as well as listing out replications and replication sites which are available to use with replication groups.
+
+## Adding a Zerto Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Zerto
+4. Fill in the following: 
+
+   Name
+   :   A friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled and made available for consumption in HPE Morpheus Enterprise
+
+   API URL
+   :   API URL for the Zerto Virtual Manager (ex. `API URL: https://xx.xx.xx.xx:9669`)
+
+   Username
+   :   Username for an admin Zerto service account
+
+   Password
+   :   Password for the provided user (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Restricts integration access to users in the current Tenant (subject to additional RBAC settings)
+
+           Public
+           :   The integration is accessible to all Tenants (option available to Master Tenant users only)
+5. Once complete, click SAVE
+
+### Results
+
+NOTE
+
+In addition to manually entering username and password credentials in this modal, users also have the option to use a stored username/password credential set, or manually enter credentials and have them stored for later use in the HPE Morpheus Enterprise secure credential store. See the CREDENTIALS configuration in the add/edit integration modal for all of these options.
+
+Once the integration is created, you can click into the integration detail page to see existing replication groups, summary data, and other information about replications and replication sites.
+
+## Setting a Replication Provider
+
+With the integration created, Zerto can be added as the replication provider for compatible Clouds. Edit an existing Cloud (click the EDIT button from the Cloud detail page) and expand the Advanced Options section. In the dropdown for Replication Provider, select the Zerto integration. Finally, save the Cloud to commit the changes.
+
+With the Cloud and the Zerto integration associated, you will now see additional replication options at provision time. When provisioning to the associated Cloud in the future, expand the Replication section from within the AUTOMATION tab of the provisioning wizard. Here you have the option of adding newly provisioned VMs to an existing replication group. Additionally, you may also create a brand new replication group from within the provisioning wizard itself if a new group is needed.
+
+![../../_images/zertoProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DC7C1357-FBBB-469E-A3EC-D2EFAA786192-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json b/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
new file mode 100644
index 0000000..1f93f80
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+  "title": "Building Catalog Workflows",
+  "ordinal": 142,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md b/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
new file mode 100644
index 0000000..7fd0896
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
@@ -0,0 +1,34 @@
+# Building Catalog Workflows
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Workflow. The modal window will appear to configure and add a new catalog Workflow.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this Workflow item will be available for selection in the Service Catalog
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **WORKFLOW:** Select an existing Workflow to be associated with this Catalog Item, new Workflows are created in Library > Automation
+- **CONTEXT:** Optionally restrict users to a specific target context, Instance, Server, or None
+- **CONFIG:** Enter an optional custom config JSON body. See [Workflows documentation](https://docs.morpheusdata.com/en/latest/library/automation/workflows.html#allow-custom-config) for a formatting example
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json b/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
new file mode 100644
index 0000000..bbb044d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+  "title": "Automation",
+  "ordinal": 103,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md b/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
new file mode 100644
index 0000000..2112cf3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
@@ -0,0 +1,13 @@
+# Automation
+
+Library  >  Automation
+
+The Automation section is composed of Tasks and Workflows. Tasks can be scripts added directly, scripts and blueprints from the Library section, recipes, playbooks, puppet agent installs, or http (api) calls. These Tasks are are combined into workflows, which can be selected to run at provision time or executed on existing instances via Actions  >  Run Workflow.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html)**
+- **[Scale Thresholds](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html)**
+- **[Power Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json b/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
new file mode 100644
index 0000000..bda1abd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+  "title": "User Settings",
+  "ordinal": 333,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md b/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
new file mode 100644
index 0000000..ceea0cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
@@ -0,0 +1,14 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your HPE Morpheus Enterprise username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
+
+![../../_images/user_settings500.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1A22C9CD-F310-4AEF-A818-55C0954C9C55-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json b/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
new file mode 100644
index 0000000..f179120
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+  "title": "Cluster Permissions",
+  "ordinal": 173,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md b/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
new file mode 100644
index 0000000..160cd6b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
@@ -0,0 +1,6 @@
+# Cluster Permissions
+
+- Cluster Permissions
+  :   Each Cluster has Group, Tenant and Service Plan access permissions settings (“MORE” > Permissions on the Clusters list page).
+- Namespace Permissions
+  :   Individual Namespaces also have Group, Tenant and Service Plan access permissions settings
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json b/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
new file mode 100644
index 0000000..b85d02f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+  "title": "Convert to Provisioned Node",
+  "ordinal": 420,
+  "parent_title": "Import Pre-Provisioned Servers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html",
+  "topic_cluster": {
+    "clustering_title": "Convert to Provisioned Node",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md b/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
new file mode 100644
index 0000000..2a61a7b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
@@ -0,0 +1,20 @@
+# Convert to Provisioned Node
+
+## About this task
+
+Perform the following to convert to Managed or create a new instance:
+
+## Procedure
+
+1. After the server is imported, go to Infrastructure > Compute > Bare Metal.
+2. Select the imported server.
+3. Click Convert to Managed. ![Convert to Managed](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3462CBDA-30E9-451B-9EDE-E68FA70DDA5F-high.png)
+4. Confirm the server details and click Execute. ![Convert to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8CCF2394-D2E1-4815-AEC2-8E706E61732D-high.png)
+
+   NOTE
+
+   Use the same OS credentials that were provided during the import step.
+
+## Results
+
+The Convert to Managed action creates a new instance, makes the selected server a fully provisioned node, and adds it to the new instance. It creates the association of this server with networks and volumes in HPE Morpheus, as present in the network switches and the storage array, respectively. In addition, it creates the association of the VLAN interfaces with the IP addresses on the host OS on the server.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json b/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
new file mode 100644
index 0000000..8785c1d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+  "title": "Instance Types",
+  "ordinal": 128,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md b/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
new file mode 100644
index 0000000..c37c8d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
@@ -0,0 +1,60 @@
+# Instance Types
+
+Adding an Instance Type creates a new Library item category. Multiple Layouts can be added to an Instance Type and these Layouts can have different Nodes attached. The Instance provisioning wizard will present the Layout options compatible with the selected Cloud. If Cloud selection is turned off, all Layouts will be presented for all Cloud types accessible by the User.
+
+![../../_images/instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C56262F7-FB82-4802-A8D8-DEE2D9FE3DB1-high.png)
+
+Name
+:   Name of the Instance Type in the provisioning Library
+
+Code
+:   A useful shortcode for provisioning naming schemes and export reference
+
+Description
+:   The description of the Instance Type shown in the Provisioning Library. (255 characters max)
+
+Category
+:   For filtering in Instance sections and provisioning wizard
+
+    - Web
+    - SQL
+    - NoSQL
+    - Apps
+    - Network
+    - Messaging
+    - Cache
+    - OS
+    - Cloud
+    - Utility
+
+Icon
+:   An identifiable icon to display in-line with your Instance Type in the provisioning wizard (Suggested dimensions: 150 x 51)
+
+Visibility
+:   - Private: Only accessible by assigned Accounts/Tenants
+    - Public: Accessible by all Accounts/Tenants
+
+Inputs
+:   Custom options presented to the user at provision time, Inputs are also created and stored in Morpheus Library
+
+Price Sets
+:   Associate a Price Set with the Instance Type, Price sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Instance Types become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Instance Type. If this Instance Type is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Instance Type Price Sets Demo**
+
+Environment Prefix
+:   Used for exportable environment variables when tying Instance Types together in App contexts. If not specified, a name will be generated
+
+Environment Variables
+:   Name and value pairs for environment variables to be loaded on initialization
+
+Enable Settings
+:   Allows for attachment of modifiable file templates to Node Types in a settings tab of the Instance after deployment
+
+Enable Scaling (Horizontal)
+:   Enables load balancer assignment and auto-scaling features
+
+Support Deployments
+:   Enables deployment features (Requires a data volume be configured on each version. Files will be copied into this location)
+
+Upon saving, this Instance Type will be available in the provisioning catalog, per User Role access. However, we still need to add Layouts to the Instance Type, and prior to creating a Layout, we will add a Node Type.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json b/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
new file mode 100644
index 0000000..0aabaf0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+  "title": "Open Telekom Cloud",
+  "ordinal": 467,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6B3D18B4-5885-4318-848F-DE294F57057B.html",
+  "topic_cluster": {
+    "clustering_title": "Open Telekom Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md b/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
new file mode 100644
index 0000000..553a400
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
@@ -0,0 +1,222 @@
+# Open Telekom Cloud
+
+Open Telekom Cloud is an Openstack-based public cloud offering. HPE Morpheus Enterprise offers a robust integration into OTC and supports many of its features, including those listed in the next section.
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- OBS buckets (create, manage, delete, and discovery)
+
+## Add an Open Telekom Cloud
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Open Telekom Cloud and click NEXT. Complete the ADD CLOUD modal, the remainder of this guide includes descriptions of the fields presented on this modal with advice on formatting needed values and where certain data can be located.
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity API URL, such as `https://iam.eu-de.otc.t-systems.com/v3`
+
+DOMAIN ID
+:   Note that this is the Domain ID and not the Domain Name. The Domain ID can be found via the CLI by typing `openstack domain list`. For default domains, “Default” can be used
+
+PROJECT
+:   OTC projects are groupings of resources and can include compute resources, storage or networking. Multiple projects may be nested under your account. Select the project to which HPE Morpheus Enterprise should onboard from (if desired) and provision
+
+REGION
+:   OTC Region
+
+USERNAME
+:   The username for the OTC service account that HPE Morpheus Enterprise will use. Ensure this account has sufficient cloud privileges to avoid interruption of work in HPE Morpheus Enterprise
+
+PASSWORD
+:   The password for the above service account
+
+IMAGE FORMAT
+:   Select QCOW, RAW or VMDK
+
+IMAGE STORE
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+INVENTORY EXISTING IMAGES
+:   When selected, HPE Morpheus Enterprise will automatically onboard existing cloud resources which can be converted to managed Instance if desired. View onboarded cloud resources in the Compute Section (Infrastructure > Compute)
+
+ENABLE HYPERVISOR CONSOLE
+:   Hypervisor console support for Openstack currently only supports `novnc`. Be sure the novnc proxy is configured properly in your Openstack environment
+
+### Service Endpoints
+
+If needed, update the following service endpoints. A complete listing of OTC API endpoints is [here](https://docs.otc.t-systems.com/endpoint/index.html).
+
+- COMPUTE SERVICE
+- IMAGE SERVICE
+- STORAGE SERVICE
+- NETWORK SERVICE
+- LOAD BALANCER SERVICE
+- OBJECT STORAGE SERVICE
+- SHARED FILE SYSTEM SERVICE
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Network and Router Creation
+
+Once an Open Telekom Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Open Telekom Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Open Telekom Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Open Telekom Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OTC project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json b/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
new file mode 100644
index 0000000..9aa6cdc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+  "title": "Host Features",
+  "ordinal": 176,
+  "parent_title": "Features",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md b/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
new file mode 100644
index 0000000..0384378
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
@@ -0,0 +1,21 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Intelligent vCPU placement to lock vCPU cores to the same NUMA node and L3 cache
+- Host hardware sensor data collection
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and data stores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Integration with HPE Morpheus Enterprise costing
+- Governance through HPE Morpheus Enterprise RBAC, Tenancy, and Policies
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json b/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
new file mode 100644
index 0000000..ea6a533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+  "title": "Prices",
+  "ordinal": 290,
+  "parent_title": "Plans",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html",
+  "topic_cluster": {
+    "clustering_title": "Prices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md b/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
new file mode 100644
index 0000000..dbc85b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
@@ -0,0 +1,85 @@
+# Prices
+
+Details on various price configurations are given here. When creating prices, it’s also necessary to understand how they will be applied. Specifically, this relates to the **INCUR CHARGES** configuration. Charges can be incurred “While Running”, “While Stopped”, or “Always”. It typically makes the most sense to have running and stopped prices for a given type (Cores, for example) OR to have an “Always” price (but not both). This is because the prices do not stack and the higher of a competing “Always” or running/stopped price will take precedence. This can lead to confusion over which price was applied and how a final cost total was computed. You should decide in advance for a given price type for a price set whether you wish to charge an “Always” rate or charge separately for running/stopped states.
+
+Price Types
+:   - Everything: One price for all resources Storage, CPU, Memory, and Disks
+    - Memory + CPU
+    - Memory Only (per MB)
+    - Cores Only (per core)
+    - Disk Only (per GB)
+    - Platform: Select from Windows, Linux (generic), or one of several specific Linux distributions
+    - Software/Service: Add prices for software licenses which may be included with your price sets
+    - Datastore (per GB)
+    - Load Balancer
+    - Load Balancer Virtual Server
+
+Price Units
+:   - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+Currency
+:   - AED
+    - ARS
+    - AUD
+    - BRL
+    - BWP
+    - CAD
+    - CHF
+    - CLF
+    - CLP
+    - COP
+    - DKK
+    - EUR
+    - GBP
+    - IDR
+    - ILS
+    - INR
+    - JOD
+    - JPY
+    - KRW
+    - MAD
+    - MNT
+    - MYR
+    - MXN
+    - NGN
+    - NOK
+    - NZD
+    - PLN
+    - ROL
+    - RUB
+    - SAR
+    - SEK
+    - SGD
+    - THB
+    - TRL
+    - USD
+    - USN
+    - VND
+    - XAF
+    - XCD
+    - XOF
+    - XPF
+    - ZAR (South African Rand)
+
+Cost
+:   The base cost of the resource(s). The Price will match the Cost unless a Price Adjustment is added.
+
+Price Adjustment
+:   - **None:** Default, no markup added and Price will match Cost
+    - **Fixed Markup:** A fixed amount added to the Cost. Price will equal Cost + Markup.
+    - **Percentage Markup:** Adds a percentage markup to Cost. Price equals Cost + (Cost x Markup %)
+    - **Custom Price:** Sets a Price independent from the Cost. If the Cost changes, a Custom Price will not.
+
+Price
+:   A computed value of the final price including the cost plus any applicable markup.
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json b/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
new file mode 100644
index 0000000..8bcf9ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+  "title": "Additional Configuration Options",
+  "ordinal": 29,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html",
+  "topic_cluster": {
+    "clustering_title": "Additional Configuration Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md b/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
new file mode 100644
index 0000000..02ebd47
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
@@ -0,0 +1,13 @@
+# Additional Configuration Options
+
+**Subtopics**  
+
+- **[Advanced morpheus.rb Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html)**
+- **[Load Balancer Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html)**
+- **[Offline Installations and Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html)**
+- **[Import Trusted Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html)**
+- **[Data Encryption](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html)**
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html)**
+- **[IPv6](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json b/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
new file mode 100644
index 0000000..63331b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+  "title": "Softlayer",
+  "ordinal": 470,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6C22C389-3D06-4DF0-B997-1CA161175182.html",
+  "topic_cluster": {
+    "clustering_title": "Softlayer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md b/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
new file mode 100644
index 0000000..63df293
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
@@ -0,0 +1,147 @@
+# Softlayer
+
+## Add a Softlayer Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   Softlayer Username
+
+API Key
+:   Softlayer User API Key, accessible in the Softlayer Portal under `Account  >  Users  >  View API Key
+
+Datacenter
+:   Datacenters will auto-populate upon successful authentication with the above credentials. Select appropriate Datacenter for this Cloud.
+
+Object Store
+:   Select the destination Object Store
+
+Inventory Existing Instances
+:   If enabled, existing Softlayer Instances will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json b/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
new file mode 100644
index 0000000..ce75533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+  "title": "Allow Custom Config",
+  "ordinal": 115,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md b/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
new file mode 100644
index 0000000..6c5266b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
@@ -0,0 +1,32 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on Operational Workflows, the user is shown a text area for custom configuration at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Workflow is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json b/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
new file mode 100644
index 0000000..4c4e145
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+  "title": "Supported Integration Versions",
+  "ordinal": 523,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Integration Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md b/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
new file mode 100644
index 0000000..ddefe44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
@@ -0,0 +1,56 @@
+# Supported Integration Versions
+
+Morpheus supports an extensive range of software integrations and versions past and present. Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+In addition, HPE Morpheus Enterprise is verified to work with, but not limited to:
+
+## Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 1. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+If you have any specific requirements please contact [support@morpheusdata.com](mailto:support%40morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json b/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
new file mode 100644
index 0000000..fa9e1d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+  "title": "VM Features",
+  "ordinal": 177,
+  "parent_title": "Features",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md b/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
new file mode 100644
index 0000000..4533659
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Guest and hypervisor console support for running workloads with selectable hypervisor console keyboard layouts
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore HVM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- HPE Morpheus Enterprise library and automation support
+- Integration with HPE Morpheus Enterprise costing features
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json b/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
new file mode 100644
index 0000000..4616578
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+  "title": "Uploading OS Images Using Local Storage",
+  "ordinal": 407,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md b/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
new file mode 100644
index 0000000..24fbb35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
@@ -0,0 +1,16 @@
+# Uploading OS Images Using Local Storage
+
+## Prerequisites
+
+- Ensure that Morpheus-app user owns the storage directory.
+- Ensure that Morpheus-app user has access to the storage path.
+
+## About this task
+
+Local storage allows OS images to be uploaded directly to the Morpheus appliance filesystem and is suitable for smaller environments or evaluation use cases.
+
+## Procedure
+
+1. Configure a Local Storage file share under Infrastructure > Storage > File Shares.
+2. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+3. Verify the image status is **Active**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json b/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
new file mode 100644
index 0000000..ef61712
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+  "title": "Option Lists",
+  "ordinal": 155,
+  "parent_title": "Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html",
+  "topic_cluster": {
+    "clustering_title": "Option Lists",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md b/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
new file mode 100644
index 0000000..a90e5be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
@@ -0,0 +1,468 @@
+# Option Lists
+
+Option Lists allow you to give the user more choices during provisioning to then be passed to scripts and/or automation. Option Lists, however, are pre-defined insofar as they are not free-form. They can be manually entered CSV or JSON, they can be dynamically compiled from REST calls via GET or POST requests, or populated by LDAP queries.
+
+![../../_images/newOptionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-90142EEF-2840-4A18-9295-9DFD5C795BC8-high.png)
+
+## Generic Option List Fields
+
+The displayed fields in the create/edit Option List modal depend on the TYPE value selected.
+
+NAME
+:   Name of the Option List
+
+DESCRIPTION
+:   Description of the Option List for reference in Option List list view
+
+TYPE
+:   - **REST:** REST API call to populate Option List
+    - **Manual:** Manually entered dataset, CSV or JSON
+    - **Morpheus API:** Call to internal HPE Morpheus Enterprise API to populate the Option List
+    - **LDAP:** Searches and returns a list of Active Directory objects
+    - **Plugin:** Sourced by custom-coded `DataSetProvider` plugins. See [developer documentation](https://developer.morpheusdata.com/docs#dataset-providers) for additional details
+
+VISIBILITY
+:   If the account currently signed in is not in the master tenant, visibility will automatically change to private
+
+## Manual Option List Fields
+
+DATASET
+:   Appears only for manual Option Lists. Add your CSV or JSON list to this field
+
+    NOTE
+
+    JSON entries must be formatted like the following example: `[{"name":"Test","value":1},{"name":"Testing","value":2}]`
+
+## Plugin Option List Fields
+
+OPTION LIST
+:   Select an Option List made available by a currently-integrated plugins
+
+## REST Option List Fields
+
+SOURCE URL
+:   A REST URL used to fetch list data which is cached in the appliance database
+
+REAL TIME
+:   When checked, a REST call will be made to update the Option List at the time its presented to the User
+
+IGNORE SSL ERRORS
+:   Do not fail API query for self-signed or invalid certs on REST call target
+
+INJECT SYSTEM AUTHORIZATION HEADER
+:   Select when calling back into the HPE Morpheus Enterprise API to automatically inject authorization headers
+
+USE OWNER AUTHORIZATION
+:   Select when calling back into the HPE Morpheus Enterprise API. When enabled, the Option List will be populated using the Option List owner's Role permissions rather than the logged in User's at execution time to ensure complete list population
+
+SOURCE METHOD
+:   GET or POST
+
+SOURCE HEADERS
+:   Custom HTTP Headers to include in the source request
+
+CREDENTIALS
+:   Use a stored credential set or manually enter credentials to access data requiring authentication. Currently, only basic auth is supported
+
+INITIAL DATASET
+:   Create an initial JSON or CSV dataset to be used as the collection for this option list. It should be a list containing objects with properties ‘name’ and ‘value’
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    for(var x=0;x < data.length; x++) {  
+      results.push({name: data[x].name,value:data[x].id});  
+    }
+    ```
+    ```
+
+REQUEST SCRIPT
+:   Create a JS script to prepare the request. Return a data object as the body for a POST request, and return an array containing properties ‘name’ and ‘value’ for a GET request. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’
+
+    **Example:**
+
+    ```
+    ```
+    results.push({name: 'userId', value : data.users})
+    ```
+    ```
+
+    In a GET request (SOURCE METHOD = GET), the value of the results variable is used to build out the request parameters. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1",value: "value1"}]
+    ```
+    ```
+
+    The request would be made to: `https://<someURL>?name1=value1`.
+
+    In a POST request (SOURCE METHOD = POST), the value of the results variable is used to build the body of the POST request. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1", value:"value1"}, {name:"name2", value:"value2"}]
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    {name:"name1", value:"value1"}, {name:"name2", value:"value2"}
+    ```
+    ```
+
+    An alternative method to building the POST request (SOURCE METHOD = POST), can be seen below. As well, we can access other **Inputs** that are available on the same form, when provisioning an Instance or Catalog Item. As seen below, the other Inputs can be accessed using the `data` variable. We can access another Input by calling its **Field Name**, which can be configured when editing the Input in Library > Options > Inputs. This allows using data from other Inputs to be used in this Input’s request.
+
+    In the example below the Input Field Name we’ll access is `myinputfieldname`, which we can get either the name (visible value for lists) or value from the item:
+
+    Name variable: `data.myinputfieldname` Value variable: `data.myinputfieldname_value`
+
+    ```
+    ```
+    var postBody = {};  
+    postBody["number"] = data.myinputfieldname_value;  
+    postBody["env"] = "all";  
+    results = postBody;
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    { "number": "123456", "env": "all" }
+    ```
+    ```
+
+## Morpheus API Option List Fields
+
+OPTION LIST
+:   A list of available object types to return
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    var i=0;  
+    results = [];  
+    for(i; i<data.length; i++) {  
+      results.push({name: data[i].name, value: data[i].value});  
+    }
+    ```
+    ```
+
+    Translation script inputs:
+
+    **Clouds**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `code: <String>`
+    - `description: <String>`
+    - `regionCode: <String>`
+    - `location: <String>`
+    - `zoneType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `cloud: <String>` // “public” or “private” value
+      - `code: <String>`
+
+    **Environments**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `code: <String>`
+    - `name: <String>`
+
+    **Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `name: <String>`
+    - `code: <String>`
+    - `uuid: <String>`
+    - `location: <String>`
+    - `datacenterId: <Number>`
+
+    **Instances**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `category: <String>`
+    - `description: <String>`
+    - `apiKey: <String>`
+    - `status: <String>`
+    - `hourlyPrice: <Number>`
+    - `hourlyCost: <Number>`
+    - `instanceType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `plan: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `site: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+
+    **Instances Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `instanceId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+    **Networks**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `category: <String>`
+    - `name: <String>`
+    - `status: <String>`
+    - `cloudId: <Number>`
+    - `groupId: <Number>`
+    - `networkType:<Object>`
+
+      - `id: <Number>`
+      - `code: <String>`
+      - `name: <String>`
+    - `externalId: <String>`
+    - `externalNetworkType: <String>`
+    - `networkDomain: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `networkPool: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `createdBy: <String>`
+
+    **Plans**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `storage: <Integer, bytes>`
+    - `memory: <Integer, bytes>`
+    - `cores: <Number>`
+
+    **Resource Pools**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `externalId: <String>`
+    - `name: <String>`
+    - `serverGroupId: <Number>`
+    - `status: <String>`
+    - `regionCode: <String>`
+    - `parentPoolId: <Number>`
+    - `type: <String>`
+
+    **Security Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `externalType: <String>`
+    - `externalId: <String>`
+    - `cloudId: <Number>`
+    - `scopeMode: <String>`
+    - `scopeId: <Number>`
+
+    **Servers**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `description: <String>`
+    - `category: <String>`
+    - `osType: <String>`
+    - `powerState: <String>`
+    - `lastStats: <String>`
+    - `zone: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `capacityInfo: <Object>`
+
+      - `maxStorage: <Integer, bytes>`
+      - `maxMemory: <Integer, bytes>`
+      - `maxCores: <Number>`
+      - `usedMemory: <Integer, bytes>`
+      - `usedStorage: <Integer, bytes>`
+    - `computeServerType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `nodeType: <String>`
+      - `vmHypervisor: <String>`
+      - `containerHypervisor: <String>`
+
+    **Servers Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `serverId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+REQUEST SCRIPT
+:   The request script is used differently for Morpheus API Option List types. A Morpheus API option list type will use an internal API to return a list of objects instead of performing HTTP(S) requests to the Morpheus API. Due to this approach, the results object will not be used to generate query parameters or a JSON body. The results object will instead be used to contain a map of accepted key:value pairs that can be used to filter, sort and order the list of objects that get returned.
+
+    Below is a list of accepted `key:value` pairs for each object type:
+
+    **Generic options available for all object types**
+
+    - `max: <integer>` // Maximum number of results to return. Default: 25
+    - `offset: <integer>` // Offset for returned results. Default: 0
+    - `sort: <string>` // Field to sort on. Default: ‘name’
+    - `order: <string>` // Order of returned values. Accepted values: ‘asc’, ‘desc’. Default: ‘asc’
+
+      **Example:**`results = {max: 5, order : 'desc'}`
+
+    **Networks**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only networks associated with this provision type
+    - `layoutId: <Number>` // Id of an Instance Layout, ignored if provisionTypeId is supplied, otherwise used to look up the provision type
+    - `poolId: <Number>` // Id of a network pool, filters to only networks within the specified network pool
+
+    **Instance Networks**
+
+    Contains same options for Networks Morpheus API but pre-filtered for Networks applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Plans**
+
+    - `zoneId` // Required. In order for plans to be returned and properly filtered, you must provide a `zoneId` and `siteId` as well as either a `layoutId` or `provisionTypeId`
+    - `siteId`
+    - `layoutId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only plans associated with this provision type
+
+    **Resource Pools**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `layoutId: <Number>` // Id of an Instance Layout, used to get the associated provision type and filter to that provision type
+
+    **Security Groups**
+
+    - `zoneId` // required
+    - `poolId`
+
+    **Clouds**
+
+    - `zoneId : <integer>` // Database ID of cloud to return
+    - `tenantId : <integer>` // Database ID of tenant where clouds are added. Filters to only clouds added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` // Database ID of cloud type. Filters to only clouds with the specified cloud type
+    - `siteId : <integer>` // Database ID of group. Filters to only clouds within the specified group
+    - `tagName : <string>` // Filters to clouds with servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to clouds with servers that have tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on cloud name and description
+
+      **Example:**`results = {tenantId: 1, siteId: 1, tagName: "morpheus"}`
+
+    **Instance Types Clouds**
+
+    Contains same options for Clouds Morpheus API type but pre-filtered for Clouds applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Instances**
+
+    - `appsId : <integer>` // Database ID of app to filter by. Returns instances linked to the app
+    - `tenantId : <integer>` // Database ID of tenant where instances are located. Filters to only instances within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the instance that contains the specified server
+    - `tagName : <string>` // Filters to instances with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to instances with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on instance name and description
+
+      **Example:**`results = {tenantId:1, phrase: "ha"}`
+
+    **Groups**
+
+    - `tenantId : <integer>` // Database ID of tenant where groups are located. Filters to only groups added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` Database ID of cloud type. Filters to only groups that contain clouds with the specified cloud type
+    - `zoneId : <integer>` // Database ID of cloud. Filters to only groups that contain the cloud with the specified ID
+    - `siteId : <integer>` // Database ID of group to return
+    - `phrase : <string>` // Fuzzy matches phrase on group name and location.
+
+    **Servers**
+
+    - `tenantId : <integer>` // Database ID of tenant where servers are located. Filters to only servers within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the server specified by the ID
+    - `siteZoneId : <integer>` // Database ID of cloud. Filters to servers contained within the specified cloud
+    - `serverType : <string>` // Type of server. Accepted values: ‘host’, ‘baremetal’, ‘vm’
+    - `siteId : <integer>` // Database ID of group. Filters to only servers contained within clouds that are added in the specified group
+    - `tagName : <string>` // Filters to servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to servers with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on server name and description.
+
+      **Example:**`results = {max: 50, siteZoneId : 3}`
+
+    **Instances Wiki**
+
+    Contains same options for Instances Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Servers Wiki**
+
+    Contains same options for Servers Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+## LDAP Option List Fields
+
+LDAP URL
+:   The URL pointing to the LDAP server
+
+USERNAME
+:   The fully qualified username (with @ suffix syntax) for the binding account
+
+PASSWORD
+:   The password for the above account
+
+LDAP Query
+:   The LDAP query to pull the appropriate objects. See the next section for an example use case
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+NOTE
+
+Option Lists are set on one or multiple `Select List` or `Typeahead` Inputs. The Input is then set on an Instance Type, Layout, Cluster Layout, and/or Operational Workflow for input during provisioning or execution.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
new file mode 100644
index 0000000..4ddd5ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+  "title": "Supported Locales",
+  "ordinal": 12,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Locales",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
new file mode 100644
index 0000000..2ad0ee4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
@@ -0,0 +1,28 @@
+# Supported Locales
+
+Morpheus supports a number of different UI locales, including:
+
+- English
+- French
+- German
+- Spanish
+- Chinese (Simplified)
+- Portuguese (Brazil)
+- Korean
+- Italian
+
+The full list of supported locales can be viewed within the Morpheus UI via the “Default Appliance Locale” select list within Administration Settings.
+
+## Switching Locales
+
+The language of text in the Morpheus UI can be changed by telling the Morpheus server which locale to use. A Locale is made up of a language code and a country code. For example “en\_US” is the code for US English, whilst “en\_GB” is the code for British English. When using the Morpheus UI software through a client, the Morpheus UI software server will send the UI text back to the client using the appropriate static Language Pack. All translations returned via Morpheus Internationalization have been made and approved prior to the Morpheus UI version release.
+
+**Via Locale Settings in the Morpheus UI:** An application wide default locale can be configured within the Master Tenant under Administration -> Settings -> Default Appliance Locale. An individual Morpheus user can configure a preferred locale within their user settings. Using a locale setting is the preferred method for switching the Morpheus UI language.
+
+**Via the Accept-Language HTTP header:** The Accept-Language request HTTP header advertises which languages the client is able to understand, and which locale variant is preferred. Most browsers will by default send a “Accept-Language” HTTP header when visiting websites. The value of Accept-Language will match the configured preference of the browser’s user language/locale settings. The Morpheus UI will automatically detect the Accept-Language header and return the UI text from the corresponding Language Pack where possible. If there is no matching Language Pack the English US language pack is displayed in the UI. If an application locale or user locale setting has been configured in the Morpheus UI, then this will override the user’s browser preferences.
+
+**Via the “lang” query parameter:** Morpheus has the capability to switch locales by passing a parameter called “lang” to the Morpheus UI request. For example, “operations/dashboard?lang=de” will switch the locale preference to German. Morpheus will automatically switch the user’s locale and store it in a cookie so subsequent requests will have the new header. If a user is unauthenticated then the user’s locale will be reset. To switch a locale back to English pass “?lang=en” as a query parameterin the Morpheus UI request.
+
+NOTE
+
+Many of Morpheus’ language packs are generated by our clients. For that reason, we cannot guarantee accuracy and completeness of the translation. As new UI elements are added, existing language sets may not have immediate updates to keep pace with application changes. If you would like to contribute to a new or existing language pack, contact your account team or Morpheus support. Contributed content will be included within the next application version.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json b/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
new file mode 100644
index 0000000..5507551
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+  "title": "Checks",
+  "ordinal": 257,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html",
+  "topic_cluster": {
+    "clustering_title": "Checks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md b/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
new file mode 100644
index 0000000..20de295
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
@@ -0,0 +1,87 @@
+# Checks
+
+The Monitoring system is composed of individual checks. A check is created for every container or vm that is provisioned through HPE Morpheus Enterprise . One interesting thing about these checks is they are type aware. There are several different built in check types that are selected based on the service or instance type that is being provisioned. These range from database type checks to web checks and message checks. They are highly configurable and also feature fallback check types for those more generic use cases.
+
+Checks can be customized to run custom queries, check queue sizes, or even adjust severity levels and check intervals. All of these things can be controlled from the Checks sub tab within Monitoring.
+
+## Health
+
+A Check can have one of four primary health states, which are Error, Healthy, Warning, and Unknown. Checks can also be muted, in which case they are effectively disabled and are not actively run to gather an updated health state. While Checks are muted, the availability percentage does not change regardless of the health of the workload being checked. The default view shows Checks in all health states but this view can be filtered to show just one health state. Change the view filter to “Happy” to see only Checks in a Healthy state, “Sad” to see only Checks in an Error state, “Warning” to see Checks in both a “Warning” and “Unknown” state, and “Muted” to see only muted Checks.
+
+When a Check test fails, the system automatically reattempts the Check after 30 seconds to eliminate false negatives. This will convert the Check into an error state and raise the appropriate severity incident depending on the grouping of the Check. When a Check recovers, it automatically goes into a Warning state. The Warning state will remain until 10 successful Check runs have completed.
+
+## Options
+
+All check types have several core options and some of these default options can be configured in Admin  >  Monitoring. This includes the default check interval time. By default a check is run every 5 minutes. This can however be changed to run as frequently as once every minute.
+
+- Max Severity: The maximum severity level impact for a created incident that can occur if the check fails (defaults to Critical).
+- Check Interval: The frequency with which a check is run (default 5 minutes).
+- Affects Availability: Whether or not this check impacts overall system availability calculations.
+
+## SSH Tunneling
+
+In many cases when it comes to monitoring databases, and services they may not be fronted on the public ip’s for external monitoring. To reach these safely, and securely HPE Morpheus Enterprise provides an SSH Tunneling mechanism for its check servers. This allows the check to be confirmed via an ssh port tunnel securely using a keypair.
+
+## Check Servers
+
+On a base installation of HPE Morpheus Enterprise a single check server is installed on the appliance. This is used for running any custom user checks. This service connects to the provided rabbitmq services and can be moved off or even scaled horizontally onto sets of check servers. All other checks that are related to provisioned containers or VMs are executed by the installed agent on the guest OS or Docker host.
+
+## Check types
+
+### Web Check
+
+A web check is useful to identify if a url is reachable and the text to match check criteria confirms if the website is loading with the expected values. The text to match character should be within the first few lines of the page source.
+
+Use case:
+:   Adding a check to make sure morpheus demo environment is functioning. The below check will login to the morpheus UI and look for a text Morpheus on the dashboard page.
+    :   Values to be added in Check:
+        :   - Name: “<enter name>”
+            - Type: Web Check
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Web Url: <https://demo.morpheusdata.com/operations/dashboard> (Note: this page will load only if my login is successful. Enter the login details in Username and password fields)
+            - Request Method: GET
+            - Basic Authentication: \* User: <username> \* Password: <password>
+            - Text to Match: “Morpheus” (Login to the url and on the page of dashboard, right click and select view page source. In the forst few lines, look for a text that you want this check to verify)
+            - Save Changes
+
+### Push API Check
+
+This check can be used to send an API call to morpheus from a platform to check if the push api is working. A push Check is not polled regularly by the standard monitoring system. Instead it is expected that an external API push updates as to the status of the check timed closely with the configured check interval setting. This is used to throttle the push from performing too many status updates.
+
+NOTE
+
+If a check is not heard from within the check intervals, It’s status will be updated to error and an incident will be raised as if it failed.
+
+Use Case:
+:   Send an API call from an app to make sure the API is not cluttered and can send checks in a 2 mins interval.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “Push API Check”
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Copy the curl command are schedule to send this via your API. For testing we used postman to send the api call at an interval of 4 mins.
+            - Save Changes
+
+### MySQL Check
+
+This check is used to run a query on a host running mysql.
+
+Use Case:
+:   Query localhost running mysql to query a table to check if there is any status as requested. If the status has a count of 1 then the check would pass else mark it as critical.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “MySQL Check”
+            - Interval: 5 mins (Select an interval)
+            - Check the box for affects availability
+            - Host: 127.0.0.1
+            - Port: 3306
+            - DB Name: morpheus
+            - User: <db user name>
+            - Password: <password>
+            - Query: “select count(\*) as count from request\_reference where status = ‘requested’;”
+            - Operator: Equal
+            - Check results: 1
+            - Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json b/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
new file mode 100644
index 0000000..c1a41a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+  "title": "Tenants",
+  "ordinal": 276,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md b/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
new file mode 100644
index 0000000..2c2c325
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
@@ -0,0 +1,71 @@
+# Tenants
+
+The Tenants page displays a list of all Tenants. This page enables users to Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, and the Created Date.
+
+Click the Tenant Name to drill into the Tenant View where you can again Edit or Delete the Tenant, as well as Create Users, Edit Users, and Delete Users users belonging to the Tenant.
+
+## Create Tenants
+
+### About this task
+
+To Create Tenants:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Create Tenant button.
+4. From the New Tenant wizard input: 
+
+   - Name
+   - Description (optional)
+   - Subdomain
+   - Base Role
+   - Currency
+5. Within the Advanced Options section, track customer data related to the Tenant if needed: 
+
+   - Account Number
+   - Account Name
+   - Customer Number
+6. Click the Save Changes
+
+## Edit Tenant
+
+### About this task
+
+To edit a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Edit the Edit Tenant settings.
+
+## Disabling Tenant
+
+### About this task
+
+When disabling a tenant, they are not able to login and cannot be impersonated by another tenant. However all of their information will still remain in HPE Morpheus Enterprise and they may still receive notifications and alerts.
+
+To disable a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Uncheck the `Enabled` box.
+
+## Delete Tenant
+
+### About this task
+
+To delete a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Delete trashcan icon on the row of the Tenant to delete.
+4. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.json b/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
new file mode 100644
index 0000000..abea101
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+  "title": "SSL Certificates",
+  "ordinal": 34,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.md b/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
new file mode 100644
index 0000000..39d265b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
@@ -0,0 +1,75 @@
+# SSL Certificates
+
+By default HPE Morpheus Enterprise generates a Self-Signed SSL Certificate. The Self-Signed SSL Certificate can be replaced with a Trusted CA Signed SSL Certificate.
+
+## Trusted CA Signed SSL Certificate Implementation
+
+### Procedure
+
+1. If you don’t already have your certificate, run an OpenSSL command to generate an SSL certificate request (.csr) and private key (.key). If you need help formatting the command, [DigiCert provides a helpful tool](https://www.digicert.com/easy-csr/openssl.htm)
+2. Submit your certificate request (.csr) and await approval of the request and return of the certificate (.crt)
+3. Copy the private key and certificate to `/etc/morpheus/ssl/your_fqdn_name.key` and `/etc/morpheus/ssl/your_fqdn_name.crt` respectively 
+
+   Extracting Certificates in PFX Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl pkcs12 -in example.pfx -nocerts -nodes -out priv.key  
+   # Extract the public key  
+   openssl pkcs12 -in example.pfx -clcerts -nokeys -out pub.crt  
+   # Extract the CA cert chain  
+   openssl pkcs12 -in example.pfx -cacerts -nokeys -chain -out ca.crt
+   ```
+   ```
+
+   Extracting Certificates in PEM Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key  
+   # Extract the public key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key
+   ```
+   ```
+4. Edit the configuration file `/etc/morpheus/morpheus.rb` and add the following entries: 
+
+   ```
+   ```
+   nginx['ssl_certificate'] = 'path to the certificate file'  
+   nginx['ssl_server_key'] = 'path to the server key file'
+   ```
+   ```
+
+   NOTE
+
+   Both files should be owned by root and only readable by root, also if the server certificate is signed by an intermediate then you should include the signing chain inside the certificate file. The key file needs to be decrypted for Morpheus to install it properly.
+5. Next simply reconfigure the appliance and restart nginx: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl restart nginx
+   ```
+   ```
+
+## Self-Signed SSL Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year Self-Signed SSL Certificate. Below details the process to regenerate the Certificate and Key files.
+
+### Regenerate both the Certificate and Key
+
+#### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
+
+### Regenerate only the Certificate
+
+#### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json b/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
new file mode 100644
index 0000000..6c45814
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+  "title": "HPE Morpheus Enterprise",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md b/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
new file mode 100644
index 0000000..a14aff7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
@@ -0,0 +1,20 @@
+# HPE Morpheus Enterprise
+
+IMPORTANT
+
+This user manual pertains to HPE Morpheus Enterprise Software. [Click here](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest) for the HPE Morpheus VM Essentials Software user manual.
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html)**
+- **[Personas](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html)**
+- **[Diagrams](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json b/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
new file mode 100644
index 0000000..7bc343c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+  "title": "Floating IPs",
+  "ordinal": 220,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html",
+  "topic_cluster": {
+    "clustering_title": "Floating IPs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md b/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
new file mode 100644
index 0000000..e53aa66
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
@@ -0,0 +1,32 @@
+# Floating IPs
+
+## Overview
+
+HPE Morpheus Enterprise supports sync and management of floating IP addresses for OpenStack, Huawei, and OTC Clouds. When these Clouds are integrated and floating IPs are present, HPE Morpheus Enterprise will automatically sync them in. Once synced, floating IPs are viewable from their own list page (Infrastructure > Network > Floating IPs) and related options are presented during provisioning, teardown, and from Instance detail pages.
+
+NOTE
+
+The Floating IPs tab is present only when supported Clouds are integrated and floating IPs are available. Additional Cloud support is planned for the future.
+
+## Floating IPs List Page
+
+All Floating IPs known to HPE Morpheus Enterprise can be viewed on the Floating IPs List Page (Infrastructure > Network > Floating IPs). From the Floating IPs list page we can see the following:
+
+- **IP ADDRESS**: The address for the floating IP synced from a supported Cloud
+- **CLOUD**: The Cloud integration the floating IP was synced from
+- **STATUS**: “Free” when the floating IP is available and “Assigned” when the floating IP is currently assigned to a workload
+- **VM**: For assigned floating IPs, the VM which currently has the floating IP attached
+
+Free floating IPs will have a gear icon (⚙) at the end of the row. Click the gear icon and select “Release Floating IP” to release from within the source cloud and remove the entry from the Floating IPs list.
+
+![../../_images/floatIpList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-65C72DC3-8755-45A9-978E-2E3F840D4F91-high.png)
+
+## Working with Floating IPs
+
+When provisioning to supported Clouds, HPE Morpheus Enterprise will give the option to attach a floating IP at provision time. From the CONFIGURE tab of the provisioning wizard for supported Clouds, select the desired floating IP.
+
+![../../_images/floatIpSet.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9514094E-8567-4571-ACFD-C334FA3A166C-high.png)
+
+During Instance teardown, HPE Morpheus Enterprise gives the option to release the floating IP.
+
+![../../_images/floatIpDelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5B05E0B0-B6AA-440E-947C-C9683D20BF9C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json b/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
new file mode 100644
index 0000000..4a345ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+  "title": "Uploading OS Images Using CIFS (Samba)",
+  "ordinal": 409,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using CIFS (Samba)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md b/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
new file mode 100644
index 0000000..e2d57ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using CIFS (Samba)
+
+## About this task
+
+CIFS (Samba) allows OS images to be stored on a shared Windows or Linux file server.
+
+## Procedure
+
+1. Configure a CIFS file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the Samba share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json b/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
new file mode 100644
index 0000000..3738f52
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+  "title": "Communication Data",
+  "ordinal": 9,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md b/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
new file mode 100644
index 0000000..c547e36
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
@@ -0,0 +1,101 @@
+# Communication Data
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency, Ports, and Protocols
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Open Search Check | Server Pull | Open Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | On‐demand when using a file or repository for Morpheus functions | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json b/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
new file mode 100644
index 0000000..9b498e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+  "title": "Cloud Foundry",
+  "ordinal": 391,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Foundry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md b/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
new file mode 100644
index 0000000..a616c69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
@@ -0,0 +1,441 @@
+# Cloud Foundry
+
+## Configuration
+
+### Adding PCF Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select CLOUD FOUNDRY from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   Cloud Foundry API Url
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+### Adding PCF Cloud From Infrastructure > Groups
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group
+3. Select the CLOUDS tab
+4. Scroll down to CLOUD FOUNDRY and select + ADD
+5. Populate the following: 
+
+   Name
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   Location
+   :   Description field for adding notes on the cloud, such as location.
+
+   Visibility
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   Select a Tenant if Visibility is set to Private to assign to Cloud to that Tenant. Multiple Tenants can be added by editing the cloud after creation.
+
+   API URL
+   :   Cloud Foundry API Url. Example `https://api.cf.morpheusdata.com`
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Review and then Select COMPLETE
+
+## Adding Spaces
+
+### About this task
+
+Cloud Foundry Spaces are referred to as Resource Pools in Morpheus. You can add a new Space by:
+
+### Procedure
+
+1. Navigating to the Cloud and selecting the Resources tab.
+2. Then, click :guilabel:‘+ Add Resource’.
+3. Give the Resource a Name
+4. Expand the Managers, Developers, and Auditors section to add specific Cloud Foundry users to the roles. When adding a user to these sections, use their Cloud Foundry email addresses.
+
+## Provisioning
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, as well as a generic Cloud Foundry Instance Type that will create a shell app used in conjunction with deployments. PCF Marketplace items can also be added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+## Deployments
+
+The Cloud Foundry App Instance Type is used in conjunction with deployments. Users do not have to pick deployment when creating a Cloud Foundry App Instance Type, but then Instance will only be a shell of a Cloud Foundry Application.
+
+A deployment in Morpheus can either point to a git hub repository or contain the actual manifest.yml and associated artifacts required for a Cloud Foundry deployment. During the deployment, Morpheus will gather up the files required. Therefore, if the deployment points to a git hub repository, Morpheus will fetch the files from git hub. Once the files are obtained, Morpheus will deploy the artifacts in a similar fashion to the Cloud Foundry cli. This includes parsing the manifest to obtain the parameters to create or update the Cloud Foundry application. Morpheus will ignore certain fields such as memory and disk size because they are dictated by the selected plan. Other fields are utilized such as routes. After parsing the manifest.yml file (including overwriting certain fields), Morpheus is ready to update or create the App in Cloud Foundry.
+
+After the App is configured, the artifacts references in the Morpheus deployment are uploaded to Cloud Foundry for the App. Note that when paths are referenced in the manifest.yml file, the paths continue to be relative to the manifest. So, a jar file under build/libs would need to be found under the build/libs directory.
+
+If Cloud Foundry services are specified in the manifest, they must already exist within Cloud Foundry. Morpheus App templates can be utilized to wire up Cloud Foundry services created by Morpheus. In this case, Morpheus will add all of the included service names defined in the App template to the manifest.yml services section. Therefore, multiple services can be used and wired up by Morpheus.”
+
+## Example
+
+To better understand how Morpheus parses the manifest.yml file, lets take a closer look at the Cloud Foundry ‘spring-music’ project. The project can be found here (<https://github.com/cloudfoundry-samples/spring-music>).
+
+The project contains the required manifest.yml file as well as the source code and build.gradle file to define how the project is to be built. After downloading the project to your local machine, build the project to generate the jar.
+
+Now, let’s take a look at the manifest.yml file:
+
+```
+```
+---  
+applications:  
+- name: spring-music  
+  memory: 1G  
+  random-route: true  
+  path: build/libs/spring-music.jar
+```
+```
+
+Using the Cloud Foundry docs (<https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html>), we can gain a better understanding of how this file is utilized by Cloud Foundry.
+
+- The `-name` parameter defines the name that will be given to the application in Cloud Foundry. Morpheus will overwrite this value with the name given to the Instance being created in Morpheus.
+- The `-memory` parameter (as well as the disk\_quota parameter if specified) will be overwritten by Morpheus based on the plan specified for the Instance.
+- The `-path` parameter defines, where relative to the manifest.yml file, your Cloud Foundry application can be found.
+- The `-random-route parameter`, as well as all other parameters described in the Cloud Foundry documentation will simply be passed through to Cloud Foundry.
+
+## Adding Marketplace Items
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds and select your Cloud Foundry Cloud
+2. Select the MARKETPLACE tab
+3. Select + ADD MARKETPLACE ITEM
+4. Select the HPE Morpheus Enterprise Instance Type to add the Marketplace Item to.
+5. Enter version
+6. Search for and select Marketplace Item
+7. Select SAVE CHANGES
+
+### Results
+
+A Node Type and layout will be created in the Library section and the layout will be automatically added to the Instance Type selected when adding the Marketplace Item.
+
+## Provisioning Instances
+
+### Seeded and Marketplace Items
+
+#### About this task
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, and PCF Marketplace items can also be easily added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select an Instance Type with a Cloud Foundry layout (MySQL, Redis and RabbitMQ plus Marketplace additions)
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select Version and Instance Configuration for a Cloud Foundry layout, ex: Cloud Foundry MySQL
+8. Select a Plan and available options for the Plan, or use the custom Plan
+9. Select a Space to add the Instance to
+10. Optionally configure advanced options
+11. Select NEXT
+12. Optionally configure Automation options
+13. Select NEXT
+14. Select COMPLETE
+
+#### Results
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
+
+### Cloud Foundry App Instance Type
+
+#### About this task
+
+IMPORTANT
+
+Add Deployments in Provisioning > Code > Deployments to be used when provisioning a Cloud Foundry App Instance Type.
+
+NOTE
+
+Minimal options are outlined below.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select the Cloud Foundry App Instance Type
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select a Plan and available options for the Plan, or use the custom Plan
+8. Select a Space to add the Instance to
+9. Select NEXT
+10. In the Deployments section, select a Deployment and Version to be deployed. These can be git repos or files added in Provisioning > Code > Deployments 
+
+    IMPORTANT
+
+    If services are specified in a git repo manifest, HPE Morpheus Enterprise assumes they are already exist in the PCF cloud with matching names.
+11. Select NEXT
+12. Select COMPLETE
+
+#### Results
+
+This will quickly create the Cloud Foundry Application, and then the deployment will follow which may take longer depending on the app configuration. The location will be updated with the route once it is configured.
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json b/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
new file mode 100644
index 0000000..c9c2d5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+  "title": "HPE Morpheus Enterprise Agent Key Features",
+  "ordinal": 44,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md b/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
new file mode 100644
index 0000000..eefe13c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
@@ -0,0 +1,64 @@
+# HPE Morpheus Enterprise Agent Key Features
+
+While optional, HPE Morpheus Enterprise Agent provides many benefits and features in areas of log aggregation, security, automation, monitoring, and more. This page contains the complete summary of its key features and benefits.
+
+## Logging
+
+The installed HPE Morpheus Enterprise Agent captures application logs and sends them back to the HPE Morpheus Enterprise appliance. The Agent buffers and compresses logs, sending them in chunks to minimize packet transfers. If desired, users may set up forwarding to an external syslog platform though for most users HPE Morpheus Enterprise internal logging functionality is sufficient. Agent logs can be viewed in the UI at Monitoring > Logs. Filtering and search tools are available, even supporting [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html). Logs may also be exported.
+
+## Monitoring and Guidance
+
+HPE Morpheus Enterprise provides robust monitoring into the workloads it manages. For example, from Instance detail pages, usage metrics are tracked on the Summary and Monitoring tabs. The available metrics are significantly improved when HPE Morpheus Enterprise Agent is installed on the workload. HPE Morpheus Enterprise will make a best effort to gather this information in the absence of an installed Agent but for some Cloud types this is not possible. The table below shows the usage metrics HPE Morpheus Enterprise can gather with and without the Agent (though the exact metric available without the Agent will vary by Cloud).
+
+Table 1.
+
+      |  |  |  |  |
+| --- | --- | --- | --- |
+| **Category** | **Statistic** | **With Agent** | **Without Agent** |
+| Memory | Max Memory | Yes | Yes |
+| Memory | Used Memory | Yes | No |
+| Memory | Cache Memory | Yes | No |
+| Storage | Max Storage | Yes | Yes |
+| Storage | Used Memory | Yes | No |
+| Processing | System CPU % | Yes | No |
+| Processing | User CPU % | Yes | Yes |
+| IOPS | Total IOPS | Yes | No |
+| IOPS | IOPS Read | Yes | No |
+| IOPS | IOPS Write | Yes | No |
+| Networking | Net TX Rate | Yes | No |
+| Networking | Net RX Rate | Yes | No |
+| Other | Agent Command Bus | Yes | No |
+| Other | Log Aggregation | Yes | No |
+| Other | Health & Monitoring | Yes | No |
+
+In addition to usage and monitoring, HPE Morpheus Enterprise also provides a useful guidance feature (Operations > Guidance). Guidance analyzes your managed workloads and makes cost-saving or performance recommendations. The effectiveness of this feature is greatly enhanced when HPE Morpheus Enterprise Agent is installed on your workloads.
+
+## Script Execution
+
+The HPE Morpheus Enterprise Agent initiates an outbound connection from the managed workload to the appliance over TCP port 443. This establishes a bidirectional command bus which allows HPE Morpheus Enterprise to orchestrate automation on managed machines without stored credentials. Many different [Task types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html) are supported and Tasks can be stacked into Operational or Provisioning Workflows to create logical automation routines. SSH or WinRM connectivity, as well as credentials, are required for Task execution when HPE Morpheus Enterprise Agent is not installed.
+
+## Setting File Templates
+
+File Templates are stored templated text files, primarily config files (for example, `my.cnf` or `morpheus.rb`). Users have access to the full map of HPE Morpheus Enterprise variables for injecting values custom to the specific workload at provision time. HPE Morpheus Enterprise Agent can transfer files generated from templates to managed nodes.
+
+## Firewall Management
+
+When “Local Firewall” is enabled for a Cloud (see the Advanced Options section on the Add/Edit Cloud modal), the HPE Morpheus Enterprise Agent can manage host or VM IP Table (firewall) rules for Linux workloads.
+
+## Summary and Additional benefits:
+
+- Installation is optional for provisioned and managed VMs
+- The Linux agent can be shrunk and should be less then 0.2% peak
+- Provides a command bus such that HPE Morpheus Enterprise doesn’t need credentials to access a box
+- Can still manage workflows if credentials are changed
+- SSH agent can be disabled and still get access to the box
+- Agent can be installed over Cloud-init, Windows unattend.xml, VMware Tools, SSH, WinRM, Cloudbase-Init, or manually
+- Makes a single, persistent connection over HTTPS websocket and runs as a service
+- Buffers and compresses logs, then sends them in chunks to minimize packets
+- Supports syslog forwarding
+- Accepts commands, executes commands, writes files, and manipulates firewalls
+- Significantly enhances Guidance recommendations through enhanced statistics
+
+NOTE
+
+The HPE Morpheus Enterprise Agent is required for managed Docker, Kubernetes, SCVMM, Hyper-V, KVM, and ESXi Hosts (for ESXi-only Cloud, not vCenter Clouds).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json b/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
new file mode 100644
index 0000000..9bcbc54
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+  "title": "Maintenance Mode",
+  "ordinal": 186,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md b/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
new file mode 100644
index 0000000..b85e91c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
@@ -0,0 +1,5 @@
+# Maintenance Mode
+
+HVM cluster hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. HPE Morpheus Enterprise UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
+
+![../../_images/enterMaintenance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-18F5E0CD-4DD0-4720-8DA0-E81B1048013B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..ce7efc8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 331,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..63918f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.json b/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
new file mode 100644
index 0000000..f7f12c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+  "title": "Node Types",
+  "ordinal": 130,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html",
+  "topic_cluster": {
+    "clustering_title": "Node Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.md b/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
new file mode 100644
index 0000000..e3d0ddf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
@@ -0,0 +1,96 @@
+# Node Types
+
+Node Types are the link between Images and Layouts.
+
+## Node Type Configuration Options
+
+The following fields are for all Technology types:
+
+Name
+:   Name of the Node Type in HPE Morpheus Enterprise
+
+Short Name
+:   The short name is a lowercase name with no spaces used for display in your container list
+
+Version
+:   Version for the Node Type. Examples: 7.5, 2012 R2, latest
+
+Technology
+:   Select associated Technology. This will filter the available configuration options, images and which Layouts the Node Type can be added to
+
+Environment Variables
+:   Add pre-set environment variables to the Node Type
+
+Category
+:   Node Types of differing categories within the same Layout can have differing sizing
+
+## Technology-Specific Options
+
+The Options fields will change depending on the Technology option selected. For VM provisioning technology options, select an image from the VM Image dropdown. This list is populated from the HPE Morpheus Enterprise Virtual Images section and will include images uploaded into HPE Morpheus Enterprise as well as synced images from added clouds.
+
+NOTE
+
+Amazon and Azure Marketplace Images can be added in the Virtual Images section for use as Node Types in custom library items.
+
+### Docker Options
+
+For Docker, type in the name and version of the Docker Image, then select the integrated registry.
+
+Service Ports
+:   To open ports on the node, enter the name and port to expose. The Load Balancer HTTP, HTTPS, or TCP setting is required when attaching to Load Balancers.
+
+    Defining an Exposed port will also create a hyperlink(s) on the container location (IP) in the VM or Container section of the associated Instance detail page.
+
+Scripts
+:   Search for and select one or multiple scripts to be executed when the Node Type is provisioned
+
+File Templates
+:   Search for and select one or multiple File Templates to be written when the Node Type is provisioned
+
+Example port configuration:
+
+![../../_images/node_ports.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EAA33A7C-4570-4FBD-857C-F9C400D588C2-high.png)
+
+### VMware Options
+
+HPE Morpheus Enterprise supports VMware-specific configurations related to Node Types targeted for VMware vCenter Clouds. Setting the TECHNOLOGY field on the Node Type to “VMware” reveals these fields.
+
+### vApp Properties
+
+Some VMware images may expect the user to provide values for vApp properties related to server configuration. HPE Morpheus Enterprise allows the user to set values for vApp properties on the Node Type, which can be static values or even HPE Morpheus Enterprise variables such as if we wanted to provide the next available IP address from a HPE Morpheus Enterprise IP pool or source a password from HPE Morpheus Enterprise Cypher. Consider the following example workflow for examining an OVA image, uploading it to HPE Morpheus Enterprise as a Virtual Image, and setting vApp properties on the Node Type.
+
+If you have an OVA that doesn’t have the properties laid out in a visible format, you can unzip it and inspect the OVF file to help set the vApp properties in HPE Morpheus Enterprise. For example, take a look at the screenshot below from an OVF file associated with an F5 image. There are four vApp properties I wish to set related to network and user configuration. The `userConfigurable` property should be toggled to `true` for any that may be set to `false`. The key is identified by the `key` property and, if desired, default values can be set via the `value` property. Save any changes to the OVF file.
+
+![../../_images/vappOvf.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-97074F85-A232-4095-9625-CEAF93C468A2-high.png)
+
+With changes saved, the image can be uploaded to HPE Morpheus Enterprise as a Virtual Image from which we can create and configure a Node Type. Below you can see the Virtual Image uploaded and revealed on the Virtual Images list page.
+
+![../../_images/vappVirtualImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-583CAD5E-6A57-49DB-AEAB-704F815F73D7-high.png)
+
+Next, create a new Node Type. After setting the TECHNOLOGY value to “VMware” the fields related to vApp Property configuration will be revealed. Select the uploaded Virtual Image as the “VM IMAGE” and set the key/value pairs in VAPP PROPERTIES. In this case, I’ve dynamically loaded the values using HPE Morpheus Enterprise variables.
+
+![../../_images/vappNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-871C2818-8DD3-478D-ADC4-613602524004-high.png)
+
+The rest of the process is the same as building out any other HPE Morpheus Enterprise library item. House the Node Type within a Layout and the Layout within an Instance Type. It should then be provisionable as any other Instance Type.
+
+### Extra Options
+
+When VMware Technology Type is selected, EXTRA OPTIONS will be available in the VMware VM Options section. These allow defining Advance vmx-file parameters during provisioning.
+
+Some Example include:
+
+```
+```
+tools.setinfo.sizeLimit : 1048576  
+vmci0.unrestricted : FALSE  
+isolation.tools.diskWiper.disable : TRUE
+```
+```
+
+NOTE
+
+Not all parameters can be set using extra config parameters. A sample reference list can be found at <http://www.sanbarrow.com/vmx/vmx-advanced.html#vmx>
+
+IMPORTANT
+
+Use caution when setting Extra Options. Malformed config files can break provisioning. Troubleshooting issues related to Extra Options defined are beyond the scope of HPE Morpheus Enterprise product support.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json b/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
new file mode 100644
index 0000000..8e74de4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+  "title": "Integrations",
+  "ordinal": 530,
+  "parent_title": "See Also",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md b/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
new file mode 100644
index 0000000..a931070
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
@@ -0,0 +1,9 @@
+# Integrations
+
+The Integrations section in Library > Integrationsis for adding and managing Automation Integrations. Existing Automation Integrations from Administration > Integrations are also populated and accessible from Library > Integrationsand vice-versa.
+
+`Provisioning: Automation Integrations` and `Admin: Integrations` are separate Role permissions, so Automations Integration access can be separated from the Administration Integrations section.
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json b/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
new file mode 100644
index 0000000..de45a88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+  "title": "Azure (Public)",
+  "ordinal": 389,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html",
+  "topic_cluster": {
+    "clustering_title": "Azure (Public)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md b/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
new file mode 100644
index 0000000..dc9427d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
@@ -0,0 +1,411 @@
+# Azure (Public)
+
+## Overview
+
+Morpheus offers a complete Integration with Microsoft Azure including the following:
+
+- Virtual Machine Sync, Create, Delete, Manage, RBAC, Tenant Permissions, Policies
+- Resource Group Sync, Create, Delete, RBAC, Tenant Permissions
+- Network Sync, Create, Delete, RBAC, Tenant Permissions
+- Subnet Sync, Create, Delete, RBAC, Tenant Permissions
+- Security Group Sync, Create, Delete, Tenant Permissions
+- Security Group Rule Sync, Create, Delete, Tenant Permissions
+- ARM Blueprints, Spec Templates, Deployment Logs Sync, Git/GitHub Integration
+- MSSQL Service Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- AKS Sync, Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Backup Create, Delete, Manage, RBAC, Policies
+- Storage Sync, Create, Delete, Manage, Browse, RBAC, Tenant Permissions, Policies
+- Marketplace Sync
+- Private Image Sync & Upload
+- Azure Marketplace Custom Library Item Support
+- Remote Console (SSH & RDP)
+- Lifecycle Management
+- Availability Set Support
+- Scale Set Sync, Create, Assign, Manage, Delete
+- Azure Load Balancer Create, Assign, Manage, Delete, RBAC, Tenant Permissions
+- Docker (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Kubernetes (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Service Plan Sync, Tenant Permissions, RBAC
+- Pricing Sync RBAC, Tenant Permissions, Markup
+- Costing Sync, Reporting, Invoicing
+- Reservations Sync, Guidance Recommendations
+- Azure Stack Support
+- Tag Bi-Directional Sync, Creation, Deletion Policy Enforcement
+- Cost Estimator
+- Azure US Gov Support
+- Azure China Support
+- Azure Germany Support
+- CSP Account Support
+
+## Requirements
+
+Morpheus Azure Integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET (Web App Key)
+
+The HPE Morpheus Enterprise appliance requires outbound HTTPS (443) access to the Azure endpoints. Depending on the type of cloud you choose when adding Azure, ensure the proper endpoints are allowed:
+
+**Global Azure Cloud**
+:   - <https://management.core.windows.net> (ServiceManagementUrl)
+    - <https://management.azure.com> (ResourceManagerUrl)
+    - <https://login.microsoftonline.com> (ActiveDirectoryAuthority)
+
+**US Gov Cloud**
+:   - <https://management.core.usgovcloudapi.net> (ServiceManagementUrl)
+    - <https://management.usgovcloudapi.net> (ResourceManagerUrl)
+    - <https://login.microsoftonline.us> (ActiveDirectoryAuthority)
+
+**Germany Cloud**
+:   - <https://management.core.cloudapi.de> (ServiceManagementUrl)
+    - <https://management.microsoftazure.de> (ResourceManagerUrl)
+    - <https://login.microsoftonline.de> (ActiveDirectoryAuthority)
+
+**China Cloud**
+:   - <https://management.core.chinacloudapi.cn> (ServiceManagementUrl)
+    - <https://management.chinacloudapi.cn> (ResourceManagerUrl)
+    - <https://login.chinacloudapi.cn> (ActiveDirectoryAuthority)
+
+## Credentials & Permissions
+
+Morpheus authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with Morpheus has Owner or Contributor permissions on the specified Subscription before contacting support.
+
+### Create an App Registration
+
+#### About this task
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one.
+
+TIP
+
+If you can’t find sections of the Azure portal discussed in this integration guide, such as App Registrations or Subscriptions, you may be able to find them under the “Favorites” section within the main hamburger menu, at the “All Resources” page from within the main hamburger menu, or by using the global search bar.
+
+#### Procedure
+
+1. Log into the Azure web console
+2. Select “App Registrations”, you may have to go to the “All Services” page to find it 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E7EF3195-082B-46D5-BE32-590BA7644633-high.png)
+3. Click “+ New registration” 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B7FEBDD8-32CB-479A-B49C-82A8F817992B-high.png)
+4. Next, give app a name, specify which accounts may access this API, specify Web for the Redirect URI type and enter any url for the Sign-on URL:
+5. Click Register and your new App Registration will be created. 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F16A233F-1112-4341-A19D-97F5B91E2A10-high.png)
+
+#### Results
+
+Now that we have (or already had) our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when Adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when Adding your Azure cloud in HPE Morpheus Enterprise 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-663FA392-839D-43E5-8C32-C50055985BCD-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select Certificates & secrets in the Manage Section
+2. Select `+ New client secret` 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B699A18D-B220-488B-989E-B67C83E2AA67-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select a duration
+6. Select Add 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-20277A74-BFD7-42BA-87B7-B249CAC4E4DD-high.png)
+7. Copy the newly generated Client Secret Value. It is important to copy the Client Secret Value now as it will not be displayed/available 
+
+   IMPORTANT
+
+   Copy the key value before continuing as it will not be displayed/available again.
+8. Store/Paste for use as the Client Secret when Adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have 3 of the 4 credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the main Subscriptions section. One way is to search for “Subscriptions” and select Subscriptions in the search results
+2. In the main “Subscriptions” section, copy the Subscription ID 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4B40A8B2-3C59-4AE4-8980-1DA3A3786918-high.png)
+3. Store/Paste for use as the Subscription ID when Adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration created/used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory/sync, create and/or remove resources.
+
+#### Procedure
+
+1. In the main Subscriptions section, click on the name of the Subscription
+2. With the Subscription detail open, select “Access Control (IAM)”
+3. Click “+ ADD” and then click “Add role assignment” from the pop-out menu 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8812BC0F-33DB-4F3D-8399-7EC297A6DC2E-high.png)
+4. Click on the tab for “Privileged administrator roles”
+5. Select Owner or Contributor and click “Next”
+6. Add Members to the Role Assignment by clicking “+ Select members”
+7. Select the App Registration from the search results and click Select 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-24AA7305-E9B5-428A-8FAE-ABC8F17CAE2E-high.png)
+8. Click “Review + Assign”
+
+## Add an Azure Cloud Integration
+
+### About this task
+
+To add a new Azure Cloud integration into HPE Morpheus Enterprise using the credentials created/collected from the previous section, perform the following:
+
+### Procedure
+
+1. In HPE Morpheus Enterprise, navigate to Infrastructure > Clouds and select + ADD 
+
+   ![../../../_images/Clouds_Morpheus_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DC3EC6CE-40F3-4AFA-9B6E-5CCAFE1DC9DE-high.png)
+2. Select “AZURE (PUBLIC)” from the Cloud Types list and click NEXT 
+
+   ![../../../_images/Clouds_Morpheus1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4F7C2657-7339-46B0-82DB-A517DB5B0D73-high.png)
+3. Populate the Following 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   CLOUD TYPE
+   :   - Global (Azure Cloud)
+       - US Gov (Azure US Government)
+       - German (Azure German Cloud)
+       - China (Azure China Cloud)
+
+   SUBSCRIPTION ID
+   :   The target Azure Subscription ID obtained from the previous section
+
+   TENANT ID
+   :   The Directory (tenant) ID obtained from the previous section
+
+   CREDENTIALS
+   :   If available, select a pre-stored Client ID and Client Secret set. Alternatively, select “Local Credentials” to enter the Client ID and Client Secret without storing them for later access. “client id and secret” under the “New Credentials” heading can also be selected so your Client ID and Client Secret will stored for later use in either the HPE Morpheus Enterprise credential store or in an integrated third party secret store
+
+   CLIENT ID
+   :   The Application (client) ID obtained from the previous section
+
+   CLIENT SECRET
+   :   The Application (client) Secret obtained from the previous section
+
+   LOCATION
+   :   Once valid credentials are populate above and HPE Morpheus Enterprise is able to successfully authenticate with Azure, the available locations/regions will populate.
+
+   REGION
+   :   Scope the Cloud to either “All” regions or a selected Azure region
+
+   RESOURCE GROUP
+   :   - Select “All” to scope the Cloud to all available Resource Groups in the specified location/region.
+       - Select a single Resource Group to limit HPE Morpheus Enterprise resource creation, selection and discovery to just this Resource Group.
+
+   INVENTORY EXISTING INSTANCES
+   :   Check to enable discovery/inventory of existing VM’s in the scoped Region and Resource Group(s)
+
+   ACCOUNT TYPE
+   :   Standard, EA or CSP
+
+       NOTE
+
+       For CSP Accounts, also enter CSP TENANT ID, CSP CLIENT ID and CSP CLIENT SECRET in the Advanced Options section. In order to enable cost sync for CSP accounts, the “CSP CUSTOMER” checkbox must be marked and “COSTING” should be set to “Costing” rather than “Costing and Reservations”.
+
+       For the CSP Client Secret, enter the Web App Key rather than the Native App Key. This should be accessed from the Microsoft Partner Center rather than the Azure web console. If this is not, Plans may sync but Price Sets and Prices would not.
+
+       ![../../../_images/addAzureCloudMorpheusS1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B917D3E3-342A-4DB9-9377-A0F20BB69D1F-high.png)
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+   AZURE COSTING MODE
+   :   Standard, CSP, or Azure Plan
+
+       Example configurations but choose what is applicable to the tenant:
+
+       Table 1. Example Azure Costing Configurations
+
+            | Account Type | Azure Costing Mode | Notes |
+       | --- | --- | --- |
+       | Standard (Pay as you go) | Standard |  |
+       | EA (Enterprise Agreement) | Standard |  |
+       | CSP (Cloud Solution Provider) | CSP | CSP Tenant, ID, Client ID, and Client Secret required |
+       | CSP (Cloud Solution Provider) | Azure Plan (Microsoft Customer Agreement) | CSP Tenant, ID, Client ID, and Client Secret required on the primary cloud |
+4. Once done configuring the Cloud, select NEXT. NOTE all specified values except the Subscription ID can be changes after the Cloud is created.
+5. Next select an existing Group to add the Azure Cloud to, or create a new Group, then select NEXT 
+
+   ![../../../_images/Clouds_MorpheusAddGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6C5E021D-A3B6-4AE2-9A7E-A7E1FD6A001C-high.png)
+6. Review the configuration and then select COMPLETE 
+
+   ![../../../_images/Clouds_MorpheusComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-57620E9D-45F0-4D5E-AEAB-F5496EDF994F-high.png)
+
+### Results
+
+Your new Azure Cloud integration will be created and begin to sync.
+
+NOTE
+
+The initial sync of an Azure Cloud can take some time due to Marketplace data sync.
+
+![../../../_images/Clouds_MorpheusNewCloudAdded.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E14BF630-7826-4A29-A728-7EE6BCEA365F-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json b/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
new file mode 100644
index 0000000..d9ba05c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+  "title": "HVM Clusters",
+  "ordinal": 174,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md b/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
new file mode 100644
index 0000000..4052eba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
@@ -0,0 +1,14 @@
+# HVM Clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, HPE Morpheus Enterprise can create a cluster of hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by HPE Morpheus Enterprise Tenant capabilities, a highly-granular RBAC and policy engine, and Instance Type library with automation workflows.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.json b/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
new file mode 100644
index 0000000..5fe81ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+  "title": "GKE Clusters",
+  "ordinal": 200,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html",
+  "topic_cluster": {
+    "clustering_title": "GKE Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.md b/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
new file mode 100644
index 0000000..f7ba949
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
@@ -0,0 +1,69 @@
+# GKE Clusters
+
+Provisions a new Google Kubernetes Engine (GKE) Cluster in target Google Cloud.
+
+NOTE
+
+Ensure proper permissions exist for the Google Clouds service account to create, inventory and manage GKE clusters.
+
+## Create an GKE Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `GKE Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the GKE Cluster
+
+   RESOURCE NAME
+   :   Name for GKE Cluster resources/hosts
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+
+   LAYOUT
+   :   Select cluster layout for GKE Cluster
+
+   RESOURCE POOL
+   :   Specify an available Resource Pool from the selected Cloud
+
+   GOOGLE ZONE
+   :   Specify Region for the cluster
+
+   VOLUMES
+   :   Cluster hosts volume size and type
+
+   NETWORKS
+   :   Select GCP subnet(s) and config
+
+   WORKER PLAN
+   :   Service Plan for GKE worker nodes
+
+   RELEASE CHANNEL
+   :   Regular, Rapid, Stable or Static
+
+   CONTROL PLANE VERSION
+   :   Select from available synced GKE k8’s versions
+
+   NUMBER OF WORKERS
+   :   Number of worker nodes to be provisioned
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json b/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
new file mode 100644
index 0000000..90b4d9d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+  "title": "Costing: Group Costing",
+  "ordinal": 59,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Group Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md b/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
new file mode 100644
index 0000000..5dd931e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
@@ -0,0 +1,32 @@
+# Costing: Group Costing
+
+![../_images/2groupcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BC2102C2-6D1A-4EC2-8F51-173EAE0CE091-high.png)
+
+The Group Costing dashboard aggregates cost totals for all Groups that meet filters set on the dashboard. This allows administrators to sort Groups by their total costs and anticipate monthly total costs by Group.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- Group (all matched by search)
+- Group (selected from dropdown)
+- Cloud
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Groups that meet set filters:
+
+- **GROUPS:** The total number of Groups that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Groups meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Groups meeting dashboard filters
+
+## Group List
+
+Each Group that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Group:
+
+- **NAME:** The name given to the Group in HPE Morpheus Enterprise at the time of creation
+- **LOCATION:** The Group location (if available)
+- **DATACENTER:** The Group datacenter (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Group listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Group listed
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.json b/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
new file mode 100644
index 0000000..6879a75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+  "title": "Provisioning into OpenShift",
+  "ordinal": 208,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning into OpenShift",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.md b/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
new file mode 100644
index 0000000..d42cbf0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
@@ -0,0 +1,31 @@
+# Provisioning into OpenShift
+
+In addition to adding a new cluster type (as covered in the previous sections), the HPE Morpheus Enterprise OpenShift plugin also adds the "OpenShift" Instance Type to the provisioning wizard. Through this, new virtualized Instances can be provisioned to the OpenShift cluster. Use the following steps to provision a new virtual machine into the cluster.
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select OPENSHIFT and click NEXT
+4. On the Group tab, select a Group and Cloud. These selections will be filtered to include only Groups which can access Clouds that contain OpenShift clusters
+5. Still on the Group tab, provide a Name for the new Instance and click NEXT
+6. On the Configure tab, set the following configurations:
+
+   - Layout: The "Openshift VM" Layout is included by default. Additional Layouts can be created within the Blueprints section (Library > Blueprints > Layouts) by selecting the "Openshift" Layout technology and associating the Layout with the "Openshift" Instance Type. See the Blueprints section of this user manual for more information on building Library items
+   - Plan: Plans of various sizes and levels of customizability can be created in Administration > Plans & Pricing. By default, a single Plan specifying 2 CPU cores and 4 GB memory is seeded when adding the plugin
+   - Resource Pool: Select the desired OpenShift cluster
+   - Volumes: Select the proper number and size volumes
+   - Networks: Networks correspond to NetworkAttachedDefinitions (NADs) in OpenShift. This list includes all NADs and names them by "<namespace>/<NAD name>" to make it easier to select a network within the intended namespace (Project). Users may select multiple NADs while provisioning but they must be from the same namespace
+
+     IMPORTANT
+
+     The first network interface chosen as part of Instance deployment will be treated as the primary interface and is expected to be reachable from the HPE Morpheus Enterprise appliance.
+   - Image: Select from all synced virtual images. Note that only custom user images are synced from OpenShift, we do not sync from the large library of default images that ship with OpenShift
+   - Project: Select the proper namespace. Bear in mind it's currently up to the user to select a valid namespace based on the network selected. If you choose an invalid namespace for the chosen network, provisioning will fail. In the future, this select list may provide automatic filtering to prevent invalid configuration but, for now, the user must make a valid selection
+7. Still on the Configure tab, other configurations common to many Instance Types can also be made. When finished, click NEXT
+8. On the Automation tab, choose to run automation Tasks or associate Workflows with the new Instance. Other common automation configurations can also be made, such as scale or backup configurations. Click NEXT
+9. On the Review tab, click COMPLETE
+
+The new OpenShift VM will soon be running based on the configurations given. Its status can be monitored from the OpenShift cluster detail page discussed in the previous section or from the Instances list page.
+
+NOTE
+
+Instance/VM console access is only supported if the VM is available on the network and reachable by HPE Morpheus Enterprise over the SSH port for Linux or the RDP port for Windows.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json b/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
new file mode 100644
index 0000000..4a986f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+  "title": "OneLogin",
+  "ordinal": 284,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html",
+  "topic_cluster": {
+    "clustering_title": "OneLogin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md b/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
new file mode 100644
index 0000000..69a05ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
@@ -0,0 +1,43 @@
+# OneLogin
+
+By integrating OneLogin with HPE Morpheus Enterprise, users can access HPE Morpheus Enterprise with their existing credentials set up within the OneLogin platform. Additionally, administrators can manage user access including Role assignment and enabling or disabling users from within the OneLogin platform. As employees are onboarded, change positions, or leave the company, additional user management within the HPE Morpheus Enterprise platform is not necessary.
+
+## Adding OneLogin Identity Source Integration
+
+To begin, log into OneLogin with an administrator account to gather some needed pieces of information. From the top menu bar, select Administration. From the admin panel, click Developers > APICredentials. Click the button labeled “New Credential”. Provide a name for the new API credentials and select “Manage Users” as the permissions type. Store the credentials somewhere they can be retrieved in the next step.
+
+![../../_images/oneLoginKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3244CCDD-7F2B-4DF3-B4E6-4BA4B0686C60-high.png)
+
+Back in HPE Morpheus Enterprise, navigate to the Tenant which will integrate with OneLogin. Identity providers are integrated on a per-Tenant basis in HPE Morpheus Enterprise. From the selected Tenant, click IDENTITY SOURCES. The list of currently-integrated identity providers is here. Click + ADD IDENTITY SOURCE to start a new integration for OneLogin. Fill in the fields below:
+
+- **TYPE:** OneLogin
+- **NAME:** A name for the identity source integration in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the identity source
+- **ONELOGIN SUBDOMAIN:** The subdomain from your OneLogin portal URL. For example, “morpheus-dev” if your portal is accessed at morpheus-dev.onelogin.com. Incorrect subdomains will cause login attempts to HPE Morpheus Enterprise to fail
+- **ONELOGIN REGION:** Specify US or EU region
+- **API CLIENT SECRET:** OneLogin API client secret which was gathered earlier in this walkthrough
+- **API CLIENT ID:** OneLogin API client ID which was gathered earlier in this walkthrough
+- **REQUIRED ROLE:** Enter a role which OneLogin users logging into HPE Morpheus Enterprise must have to gain access to HPE Morpheus Enterprise
+- **DEFAULT ROLE:** The default HPE Morpheus Enterprise Role applied to users created from the OneLogin integration if no other role mapping is specified in other Role Mappings fields
+- **ROLE MAPPINGS:** All existing HPE Morpheus Enterprise Roles will be listed with fields to enter OneLogin Roles to create a mapping. Users with OneLogin roles matching the role mappings will be assigned the appropriate Role(s) in HPE Morpheus Enterprise when signing in
+- **ENABLE ROLE MAPPING PERMISSION:** When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the core integration fields (such as the API keys)
+- **MANUAL ROLE ASSIGNMENT:** When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+Select SAVE CHANGES and the OneLogin Integration will be added.
+
+Users can now login to HPE Morpheus Enterprise with OneLogin credentials. The first login will create a user in HPE Morpheus Enterprise matching the username, email and password from OneLogin. If a REQUIRED ROLE is specified in the Identity Source settings, only users with that Role in OneLogin will be able to login to HPE Morpheus Enterprise.
+
+IMPORTANT
+
+OneLogin users will not authenticate in HPE Morpheus Enterprise if there is an existing HPE Morpheus Enterprise User with matching username or email address.
+
+You can now test the integration by logging in with user credentials which have been configured in OneLogin. On the first login, a new user will be created with the same username, email address, and password as contained in OneLogin. On subsequent logins, HPE Morpheus Enterprise will sync with OneLogin to make sure the user hasn’t been disabled or if its Role(s) have changed in OneLogin which would affect its corresponding Roles in HPE Morpheus Enterprise.
+
+The HPE Morpheus Enterprise identity source integration is interacting with the OneLogin APIs in the list below. This reference may be needed to ensure HPE Morpheus Enterprise is integrating using an API key with sufficient privileges. In a situation where troubleshooting is needed, first confirm these APIs can be accessed using the provided key.
+
+- `/auth/oauth2/token` - Generate Token
+- `/api/1/users/$user_id/roles` - Get Roles
+- `/api/1/login/auth` - Create Session
+- `/api/1/users/$user_id` - Get User
+- `/api/1/roles/$role_id` - Get Role
+- `/api/1/roles?name=$role_name` - Find Role
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json b/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
new file mode 100644
index 0000000..d07e8ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+  "title": "Capacity: Capacity Planning",
+  "ordinal": 66,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity: Capacity Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md b/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
new file mode 100644
index 0000000..508bf98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
@@ -0,0 +1,9 @@
+# Capacity: Capacity Planning
+
+![../_images/capacityPlanning.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-54937FF3-952A-40DE-8C06-8E193416776A-high.png)
+
+The capacity planning dashboard shows both realtime use and predicted future use in key metrics of memory, storage and CPU use over a pre-defined period. Choose to show this across the entire appliance (all Tenants and Clouds) or scoped to just a single Tenant or a single Cloud. This can help to plan for future hardware needs, plan for changing public Cloud spend, or identify over/under utilization of certain resources.
+
+## Filters
+
+Leave unfiltered to show data across all Tenants and Clouds. Optionally choose to filter down to all Clouds in one specific Tenant or a single Cloud. The trend line predicts future use of resources based on recent past utilization.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json b/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
new file mode 100644
index 0000000..9551393
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+  "title": "Agent Install Methods",
+  "ordinal": 47,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Methods",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md b/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
new file mode 100644
index 0000000..0c4dcc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
@@ -0,0 +1,100 @@
+# Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+## For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+## SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+## WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+## VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+## Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+## Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+## Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+## Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json b/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
new file mode 100644
index 0000000..197e341
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+  "title": "Key Features",
+  "ordinal": 397,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html",
+  "topic_cluster": {
+    "clustering_title": "Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md b/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
new file mode 100644
index 0000000..6bd9df8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
@@ -0,0 +1,106 @@
+# Key Features
+
+HPE BMaaS for Morpheus Enterprise provides centralized discovery, provisioning, lifecycle management, and monitoring for HPE ProLiant bare-metal infrastructure. The key features of HPE BMaaS are as follows:
+
+- Automated Server Discovery and Inventory
+
+  - Server Import: Imports HPE ProLiant servers into Morpheus using iLO IP addresses and credentials.
+  - Hardware Inventory Discovery: Automatically collects detailed hardware data, including:
+
+    - Server model and generation
+    - CPU, memory, and storage configurations
+    - Network interfaces and adapters
+    - Firmware and driver versions
+  - Service Plan Mapping: Maps discovered hardware to Morpheus Service Plans to align metering, consumption tracking, and billing.
+  - Metadata Management: Maintains updated server metadata to ensure operational visibility and support capacity planning.
+- Resource Pool and Bare Metal Cloud Management
+
+  - Create a Bare Metal Cloud per tenant to represent dedicated HPE ProLiant infrastructure.
+  - Organize servers within the cloud into Resource Pools for multi-site deployments and infrastructure segmentation.
+  - Allocate servers to specific groups, environments, or use cases.
+  - Apply policies, access control, and governance at the cloud or resource pool level.
+- Bare Metal Instance Provisioning
+
+  - Provision bare metal instances directly from available HPE ProLiant servers.
+  - Support for:
+
+    - Local disk RAID configuration during deployment
+    - Automated OS installation
+    - Post-install configuration and customization
+  - Associate instances with user-defined groups, clouds, and resource pools.
+- Operating System Deployment
+
+  - Deploy Windows Server and Linux operating systems using ISO images stored in the Morpheus Virtual Image Library.
+  - Supported unattended installation mechanisms:
+
+    - Windows Setup (AutoUnattend)
+    - RHEL / Oracle Linux Kickstart
+    - Ubuntu Autoinstall (cloud-init)
+  - Consistent and repeatable OS deployments across environments.
+- Image Management
+
+  - Centralized catalog of bootable OS images.
+  - Support for multiple image storage backends:
+
+    - Storage > File Shares
+
+      - CIFS (Samba Windows File Sharing): Windows-compatible network file sharing
+      - Local Storage: Direct storage on the server
+      - Network File System version 3 (NFSv3): Linux network file sharing
+    - Storage > Buckets
+
+      - S3-compatible object storage (for example, using MinIO): Object storage through S3 API
+    - Images can be reused across multiple provisioning workflows.
+- Greenfield (New Server) Provisioning
+
+  - Provision brand-new, unconfigured HPE ProLiant servers into Morpheus-managed bare metal instances.
+  - Perform full end-to-end lifecycle automation, including:
+
+    - Server discovery
+    - Power control and boot orchestration
+    - RAID and storage configuration
+    - Network configuration
+    - Operating system deployment
+  - Enable zero-touch deployment from factory-fresh hardware to production-ready servers.
+  - Ensure consistent, repeatable provisioning aligned with organizational standards.
+- Brownfield (Pre-Provisioned Server) Import
+
+  - Import existing physical servers into Morpheus as Pre-Provisioned resources
+  - Convert imported servers into fully managed Morpheus instances.
+  - Add additional imported servers as nodes to an existing instance.
+- Firmware and Driver Lifecycle Management
+
+  - Execute firmware and driver inventory and updates using HPE Service Pack for ProLiant (SPP).
+  - Run updates through Morpheus Jobs and Workflows.
+  - Target firmware only, drivers only, or both.
+  - Support for:
+
+    - Dry Run (inventory only)
+    - Deploy (apply updates)
+- Monitoring and Metering
+
+  - Monitor real-time hardware health and operational status through iLO integration.
+  - Surface system alerts and hardware events inside HPE Morpheus Enterprise.
+  - Meter resource consumption for reporting and charge-back or show-back.
+- Networking Integration
+
+  - Automated VLAN and switch port configuration in managed mode.
+  - Flexible network attachment to physical or bonded interfaces.
+  - Support for:
+
+    - Unmanaged networks
+    - Managed networks using HPE Aruba CX switches
+- Storage Integration
+
+  - Use local server storage for OS installation.
+  - Integrate with HPE Alletra MP storage arrays for remote SAN volumes.
+  - Create, attach, detach, resize, and delete volumes from HPE Morpheus Enterprise.
+- Integration with Morpheus Core Platform Capabilities
+
+  Bare metal instances benefit from native Morpheus platform features, including:
+  - SSH and RDP access
+  - Morpheus agent (morphd) deployment
+  - Workflow automation and lifecycle scripts
+  - Policy-based governance
+  - Role-based access control
+  - Multi-group and multi-cloud support
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json b/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
new file mode 100644
index 0000000..48a3ff5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+  "title": "Single Node Installation",
+  "ordinal": 16,
+  "parent_title": "Installation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md b/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
new file mode 100644
index 0000000..9c339db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
@@ -0,0 +1,439 @@
+# Single Node Installation
+
+## Single Node Install Overview
+
+In a Single Host/All-in-one configuration, all components required for Morpheus are automatically installed and configured during the Morpheus `reconfigure` command.
+
+![../../../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+Appliance Host
+:   - Application
+      :   - Morpheus App
+    - Web Server/Proxy
+      :   - NGINX
+    - Database
+      :   - MySQL
+    - Messaging
+      :   - RabbitMQ
+    - Search
+      :   - Opensearch
+    - Console
+      :   - Guacamole
+    - Monitoring
+      :   - Check Server
+
+### Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - MySQL: `/var/log/morpheus/mysql`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## Single Node Install on CentOS
+
+NOTE
+
+Appliance Package links are available at <https://app.morpheushub.com> in the downloads section.
+
+### Quick Install
+
+#### Procedure
+
+Install the Appliance package and run `sudo morpheus-ctl reconfigure`.
+
+#### Results
+
+That is it. After the reconfigure completes, HPE Morpheus Enterprise will start and be available at `https://your_machine_name` in a minute or few.
+
+### Step-by-step Install Instructions
+
+#### Procedure
+
+1. Ensure the HPE Morpheus Enterprise Appliance host meets the minimum [requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)
+2. Download the target version `.rpm` package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-appliance-$version.rpm
+   ```
+   ```
+3. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-appliance-$version.rpm
+   ```
+   ```
+4. Next install the rpm package 
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-appliance-x.x.x-1.x86_64.rpm
+   ```
+   ```
+5. By default the appliance\_url uses the machines hostname, ie `https://your_machine_name`. The default url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. Additional Appliance configuration options are available below. 
+
+   Appliance Configuration Options
+
+   Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+   NOTE
+
+   Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps if simply appending a port to your `appliance_url` value doesn’t work.
+
+   ```
+   ```
+   app['encryption_key_suffix'] = '$suffix'  
+     # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+   appliance_url 'https://morpheus.appliance-url.com'  
+     # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+     # The appliance_url cannot exceed 64 characters  
+     # The appliance_url must not contain a trailing `/`.  
+   bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+   bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+   opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+   opensearch['auth_user'] = 'morpheus-es-user'  
+   opensearch['enable'] = true  
+   opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+   opensearch['host'] = "127.0.0.1"  
+   opensearch['port'] = "9200"  
+   opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+   opensearch['use_tls'] = false  
+   ↓ The following opensearch settings are only valid for Internal/Embedded opensearch services  
+   opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+   opensearch['memory_alloc_arena_max'] = 2  
+   opensearch['memory_map_max'] = 65536  
+   opensearch['memory_map_threshold'] = 131072  
+   opensearch['memory_top_pad'] = 131072  
+   opensearch['memory_trim_threshold'] = 131072  
+   opensearch['open_files'] = 204800  
+   opensearch['secure_mode'] = false  
+   opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   opensearch['xmx'] = 0.25  
+   guacd['guacamole_enabled'] = false  
+   guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+   logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+   logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+   logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+   mysql['enable'] = true  
+   mysql['host'] = {'127.0.0.1' => 3306}  
+   mysql['use_tls'] = false  
+   mysql['morpheus_db_user'] = 'morpheus-db-user'  
+   mysql['morpheus_password'] = 'morpheus-db-password'  
+   mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+   mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+   ↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+   mysql['tmp_dir'] = '/tmp/mysql'  
+   mysql['log_dir'] = '/var/log/morpheus/mysql'  
+   mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+   mysql['max_connections'] = 151  
+   mysql['max_allowed_packet'] = 67108864  
+   mysql['mysql_connect_timeout'] = 60000  
+   mysql['mysql_max_reconnects'] = 2  
+   mysql['mysql_queries_before_retry_source'] = 0  
+   mysql['mysql_seconds_before_retry_source'] = 300  
+   nginx['cache_max_size'] = '5000m'  
+   nginx['enable'] = true  
+   nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+   nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+   nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+   nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+   nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+   nginx['loading_pages']['max_loops'] = 60 # seconds  
+   nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+   nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+   nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+   nginx['log_format_name'] = 'custom'  
+   nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+   nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+   nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+   nginx['ssl_company_name'] = "Morpheus, LLC"  
+   nginx['ssl_country_name'] = "US"  
+   nginx['ssl_email_address'] = "personal@email.com"  
+   nginx['ssl_locality_name'] = "San Mateo"  
+   nginx['ssl_organizational_unit_name'] = "DevOps"  
+   nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+   nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+   nginx['ssl_session_timeout'] = "5m"  
+   nginx['ssl_state_name'] = "CA"  
+   nginx['worker_connections'] = 10240  
+   nginx['workers'] = integer calculated from number of cpus  
+   nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   rabbitmq['enable'] = true  
+   rabbitmq['host'] = '127.0.0.1'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+   rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+   rabbitmq['vhost'] = 'morpheus'  
+   ↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+   rabbitmq['heartbeat'] = nil  
+   rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+   rabbitmq['nodename'] = 'rabbit@localhost'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['use_tls'] = false  
+   repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+   ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+   ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+   ui['kerberos_config'] = nil  
+   ui['kerberos_login_config'] = nil  
+   ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+   ui['max_memory_mb'] = nil  
+   ui['memory_alloc_arena_max'] = 2  
+   ui['memory_map_max'] = 65536  
+   ui['memory_map_threshold'] = 131072  
+   ui['memory_top_pad'] = 131072  
+   ui['memory_trim_threshold'] = 131072  
+   ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+   ui['support_links'] = {  
+     'name' => ['url', 'i18n'],  
+     'name1' => ['url1', i18n1'],  
+     'name2' => ['url2', i18n2']  
+   } #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+   ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+   ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   ui['xmx'] = 0.25
+   ```
+   ```
+6. After all configuration options have been set, run: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus.rb` and running `sudo morpheus-ctl reconfigure` again. Appliance and other services may need to be restarted depending on configuration changes.
+7. Once the installation is complete the morpheus-ui service will automatically start up and be available shortly. To monitor the UI startup process, run `morpheus-ctl tail morpheus-ui` and look for the ascii logo accompanied by the install version and start time: 
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2021  
+   timestamp: ****************************************
+   ```
+   ```
+
+#### Results
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on Debian/Ubuntu
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on Ubuntu or Debian a few preparatory items should be addressed first.
+
+### Procedure
+
+First make sure the apt repository is up to date by running `sudo apt-get update`. It is advisable to verify the assigned hostname of the machine is self-resolvable. 
+
+IMPORTANT
+
+If the machine is unable to resolve its own hostname `nslookup hostname` some installation commands will be unable to verify service health during installation and fail.
+
+### Results
+
+1. Next simply download the relevant `.deb` package for installation. This package can be acquired from <https://app.morpheushub.com> downloads section.
+
+   TIP
+
+   Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package/morpheus-appliance_x.x.x-1_amd64.deb`
+
+1. Next we must install the package onto the machine and configure the morpheus services:
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+2. Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl stop morpheus-ui  
+   sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   The morpheus-ui can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on RHEL
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on RHEL/RedHat a few prerequisite items are required.
+
+### Procedure
+
+1. Configure firewalld to allow access from users on 443 (Or remove firewall if not required).
+2. Make sure the machine is self resolvable to its own hostname.
+3. For RHEL 7.x, the Optional RPMs repo needs to be added for Reconfigure to succeed. It does not need to be added For RHEL 8.x, as the Optional RPMs repo is now part of the appstream repo that is enabled by default in RHEL 8.x. 
+
+   - RHEL 7.x Amazon:`yum-config-manager --enable rhel-7-server-rhui-optional-rpms`
+   - RHEL 7.x:`yum-config-manager --enable rhel-7-server-optional-rpms`
+
+### Results
+
+NOTE
+
+For Amazon users a Redhat subscription is not required if the appropriate yum REGION repository is added instead as demonstrated above.
+
+The RedHat Enterprise Linux server needs to be registered and activated with Redhat subscription. The server optional rpms repo needs to be enabled as well.
+
+To check if the server has been activated please run the subscription-manager version. Subscription manager will return the version plus the python dependency version.
+
+If the server has not been registered and activated then the subscription manager version will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: This system is currently not registered  
+subscription management server: 0.9.51.24.-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+When a server has been registered and activated with Redhat the subscription manager will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: Red Hat Subscription Management  
+subscription management server: 0.9.51.24-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+If the subscription manager re-turns the message `This system is currently not registered` please follow the below steps to register the server.
+
+TIP
+
+To register the server you will need to have sudo permissions [Member of the Wheel group] or root access to the server. You will also need your Redhat registered email address and password.
+
+subscription-manager register
+
+```
+```
+sudo subscription-manager register  
+Username: redhat@example.com  
+Password: . subscription-manager auto --attach
+```
+```
+
+NOTE
+
+This can take a minute to complete
+
+```
+```
+sudo subscription-manager attach --auto  
+Installed Product Current Status: Product Name: Red Hat Enterprise Linux  
+Server Status: Subscribed
+```
+```
+
+To check to see if the RHEL server has the Red Hat Enterprise Linux 7 Server - Optional (RPMs) repo enabled please run the following command to return the repo status.
+
+TIP
+
+To check the server repos you will need to have sudo permissions [Member of the Wheel group] or root access to the server.
+
+```
+```
+sudo yum repolist all | grep "rhel-7-server-optional-rpms" rhel-7-server-optional-rpms/7Server/x86_64 disabled
+```
+```
+
+If the repo status was returned as disabled then you will need to enable the repo using the subscription manager like below.
+
+```
+```
+sudo subscription-manager repos --enable rhel-7-server-optional-rpms  
+Repository 'rhel-7-server-optional-rpms' is enabled for this system.
+```
+```
+
+The message `Repo 'rhel-7-server-optional-rpms' is enabled for this system.` will appear after enabling the repo. This will confirm that the repo has been enabled.
+
+Next simply download the relevant `.rpm` package for installation. This package can be acquired from morpheushub.com.
+
+TIP
+
+Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package.rpm`
+
+Next we must install the package onto the machine and configure the morpheus services:
+
+```
+```
+sudo rpm -i morpheus-appliance_x.x.x-1_amd64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+```
+```
+sudo morpheus-ctl reconfigure  
+sudo morpheus-ctl stop morpheus-ui  
+sudo morpheus-ctl start morpheus-ui
+```
+```
+
+NOTE
+
+The `morpheus-ui` can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json b/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
new file mode 100644
index 0000000..f2f0492
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+  "title": "Installation",
+  "ordinal": 14,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html",
+  "topic_cluster": {
+    "clustering_title": "Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md b/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
new file mode 100644
index 0000000..5758df4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
@@ -0,0 +1,8 @@
+# Installation
+
+**Subtopics**  
+
+- **[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html)**
+- **[Single Node Installation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html)**
+- **[HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)**
+- **[3 Node HA Install Example](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json b/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
new file mode 100644
index 0000000..2af6b6c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+  "title": "Rubrik",
+  "ordinal": 384,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.html",
+  "topic_cluster": {
+    "clustering_title": "Rubrik",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md b/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
new file mode 100644
index 0000000..18dd225
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
@@ -0,0 +1,80 @@
+# Rubrik
+
+The embedded HPE Morpheus Enterprise Rubrik Backup integration allows syncing, creation, and management of Rubrik Backups for vCenter Clouds. New Rubrik integrations are created in Backups > Integrations and, once created, can be set as the backup provider for existing vCenter Clouds. The latest versions of the Rubrik plugin support Rubrik CDM as well as Rubrik RSC (Rubrik Cloud Security). From a HPE Morpheus Enterprise standpoint, the primary difference between the two is in how they are authenticated. CDM-based integrations are created with API key authentication whereas RSC-based integrations are created with a client ID and client secret. Once the integration is created, the feature set as used through HPE Morpheus Enterprise is identical.
+
+## Features
+
+- Backup sync & association
+- SLA Domain sync & selection
+- Backup creation, deletion & restore
+- Restore Backups over existing VMs
+- Restore Backups as new Instances
+
+## Adding Rubrik Integration
+
+### About this task
+
+NOTE
+
+The Rubrik backup service is currently only supported on the VMware Cloud type.
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Rubrik
+4. Fill in the following: 
+
+   Rubrik CDM Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (api key), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   API Token
+   :   If manually entering credentials, this field will be visible. Enter the API key
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+
+   Rubrik RSC Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server. Each Rubrik customer will have a unique host URL (for example: `https://morpheusdata.my.rubrik.com`)
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (client id and secret), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   Client ID
+   :   If manually entering credentials, this field will be visible. Enter the client ID for authentication. If needed, add a service account to obtain credentials (for example: `https://morpheusdata.my.rubrik.com/service_accounts`). Keep in mind the service account will need to have sufficient privileges to interface with the Rubrik API to execute all HPE Morpheus Enterprise functionality listed in the “Features” section above
+
+   Client Secret
+   :   If manually entering credentials, this field will be visible. Enter the client secret for authentication
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json b/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
new file mode 100644
index 0000000..287201c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+  "title": "Incidents",
+  "ordinal": 259,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html",
+  "topic_cluster": {
+    "clustering_title": "Incidents",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md b/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
new file mode 100644
index 0000000..c665596
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
@@ -0,0 +1,9 @@
+# Incidents
+
+Incident management is very important in any IT Operations environment. The ability to notify the appropriate people of an outage that requires immediate attention is critical to reducing recovery time and even preventing potential customer facing impacts. Because of this, HPE Morpheus Enterprise provides incident management features as well as external integrations out of the box.
+
+Incidents can be found in the Monitoring- > Incidents section. When a check fails, an incident is automatically raised. These can vary in severity based on the user configured check severities as well as the group hierarchy (representative of redundancy).
+
+Incidents are also grouped. If an application is impacted and multiple checks fail for that application they automatically get grouped together in one Incident that can fluctuate or escalate in severity as time progresses. These incidents can be muted so as not to affect availability and they can also be resolved manually with an option to detail resolution information.
+
+There are also integrations and API’s for integrating with existing corporate workflows when it comes to incident management.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json b/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
new file mode 100644
index 0000000..7ed82ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+  "title": "Cluster Packages",
+  "ordinal": 163,
+  "parent_title": "Templates",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md b/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
new file mode 100644
index 0000000..c49bb49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
@@ -0,0 +1,21 @@
+# Cluster Packages
+
+Cluster Packages are created and can then be associated with Cluster Layouts. Cluster Packages themselves are created from Spec Templates. The Spec Templates and Cluster Layouts sections of HPE Morpheus Enterprise docs include more information on creating those constucts and show the steps to deploy sample builds.
+
+## Creating a Cluster Package
+
+Navigate to the Cluster Packages List page (Library > Templates > Cluster Packages). System Cluster Packages are listed here. These are included as part of HPE Morpheus Enterprise pre-built Cluster Layouts and cannot be edited or viewed. User-created Cluster Layouts are also listed here and these may be edited. To begin creating a new Cluster Package, click + ADD and configure the following:
+
+- **NAME:** A friendly name for the Cluster Package in HPE Morpheus Enterprise
+- **CODE:** An identifying code for the Cluster Package for use with HPE Morpheus Enterprise API and CLI
+- **DESCRIPTION:** An optional description for the Cluster Package
+- **PACKAGE VERSION:** A version designation for the Cluster Package
+- **ICON:** An identifying icon for the Cluster Package, this will appear in a list with other packages associated with a Cluster Layout
+- **DARK MODE IMAGE:** An alternate icon for the Cluster Package used when the dark theme is enabled on the HPE Morpheus Enterprise appliance
+- **TYPE:** A type selection for the package, see dropdown for options
+- **PACKAGE TYPE:** A one-word descriptor for the package such as “calico”, “prometheus”, etc.
+- **ENABLED:** When marked, this Cluster Package is available to be set on Cluster Layouts
+- **REPEAT INSTALL:** When marked, if the package install initially fails, the installation will be attempted again
+- **SPEC TEMPLATES:** Use the Typeahead field to select relevant Spec Templates to build the Cluster Package
+
+![../../_images/cluster-packages.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D5D3548C-0254-4864-A53B-0147E5742FBC-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json b/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
new file mode 100644
index 0000000..317b251
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+  "title": "Import Pre-Provisioned Servers",
+  "ordinal": 419,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html",
+  "topic_cluster": {
+    "clustering_title": "Import Pre-Provisioned Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md b/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
new file mode 100644
index 0000000..9e30b06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
@@ -0,0 +1,29 @@
+# Import Pre-Provisioned Servers
+
+## About this task
+
+Perform the following to add a bare metal server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute > Bare Metal.
+2. Click Add Bare Metal Server.
+3. Select the Pre-Provisioned server.
+4. Complete the remaining server details and click Save.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-961F7EE2-166C-4B30-A63A-5C6CF0D638BC-high.png)  
+
+   NOTE
+
+   **For Windows**: When importing a Pre-Provisioned Windows server, select Windows OS. This is required because some import operations are specific to Windows.
+
+   During import, the HPE BMaaS validates the association between the provided iLO IP and OS IP by executing commands on the host OS. The supplied OS credentials must have elevated privileges:
+   - **Linux OS**: The user must have sudo privileges.
+   - **Windows OS**: The user must be in the Administrators group.
+
+## Results
+
+Once the server is imported, it should be ready to be converted into a fully provisioned node.
+
+**Subtopics**  
+
+- **[Convert to Provisioned Node](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json b/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
new file mode 100644
index 0000000..f1593d8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+  "title": "logback config",
+  "ordinal": 37,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html",
+  "topic_cluster": {
+    "clustering_title": "logback config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md b/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
new file mode 100644
index 0000000..0612f8b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
@@ -0,0 +1,888 @@
+# logback config
+
+NOTE
+
+This doc is for 5.4.4+ versions that use `logback.xml`. 5.4.3 and earlier versions use `logback.groovy` with a different syntax that is not compatible with this doc. Please refer to 5.4.3 and earlier documentation for `logback.groovy` configuration details.
+
+The log output for the morpheus-ui service is configured in the logback.xml file. Log output levels can be updated when more or less log output is desired.
+
+## Setting Log Levels
+
+To change a log level, edit the logback configuration file in /opt/morpheus/conf/logback.xml and save. The changes will be reflected within the configured `scanPeriod`, 30 seconds by default.
+
+Levels:
+:   - **OFF** (no log output)
+    - **ERROR** (includes error logs)
+    - **WARN** (includes warn and error logs)
+    - **INFO** (includes info, warn and error logs)
+    - **DEBUG** (includes info, warn, error and debug logs)
+    - **TRACE** (includes info, warn, error, debug and trace logs)
+
+WARNING
+
+Use DEBUG and/or TRACE levels with caution. DEBUG & TRACE levels can produce many logs that can consume disk space quickly. Only use DEBUG and/or TRACE levels when needed and target them for specific services.
+
+## Example Logback Settings
+
+Below are sample log configuration settings. This is not a complete list. Additional log names/paths can typically be determined from the standard INFO, WARN and ERROR logs.
+
+ACI
+:   ```
+    ```
+    <logger name="com.morpheus.integration.NetworkServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciNetworkService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>
+    ```
+    ```
+
+Amazon
+:   ```
+    ```
+    <logger name="com.morpheus.compute.amazon.AmazonComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AmazonComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.costing.AmazonCostingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AmazonProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Azure
+:   ```
+    ```
+    <logger name="com.morpheus.Azure.ServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.AzureSqlServerProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.azure.AzureComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureCostingService" level="DEBUG"/>
+    ```
+    ```
+
+Chef
+:   ```
+    ```
+    <logger name="com.morpheus.automation.ChefClientService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefTaskService" level="DEBUG"/>
+    ```
+    ```
+
+DNS
+:   ```
+    ```
+    <logger name="com.morpheus.dns.MicrosoftDnsService" level="DEBUG"/>
+    ```
+    ```
+
+General
+:   ```
+    ```
+    <logger name="com.morpheus.InstanceService" level="DEBUG"/>  
+    <logger name="com.morpheus.util.ApiUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.AppService" level="DEBUG"/>  
+    <logger name="com.morpheus.MorpheusComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.RpcService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractBoxProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ProgressUpdater" level="DEBUG"/>
+    ```
+    ```
+
+Google
+:   ```
+    ```
+    <logger name="com.morpheus.compute.google.GoogleComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.GoogleComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.GoogleProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Hyper-V
+:   ```
+    ```
+    <logger name="com.morpheus.compute.hyperv.HypervComputeService" level="DEBUG" />  
+    <logger name="com.morpheus.compute.HypervComputeUtility" level="DEBUG" />
+    ```
+    ```
+
+IBM Cloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.softlayer.SoftlayerComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.SoftlayerComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Kubernetes
+:   ```
+    ```
+    <logger name="com.morpheus.app.KubernetesAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.KubernetesResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.KubernetesComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.host.KubernetesHostService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.KubernetesProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.KubernetesStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Monitoring
+:   ```
+    ```
+    <logger name="com.morpheus.monitoring.MonitorCheckService" level="DEBUG"/>
+    ```
+    ```
+
+Network
+:   ```
+    ```
+    <logger name="com.morpheusdata.infoblox.InfobloxProvider" level="DEBUG"/>  
+    <logger name="com.morpheus.network.InfobloxNetworkPoolService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.network.PluginNetworkPoolService" level="DEBUG"/>
+    ```
+    ```
+
+Nutanix
+:   ```
+    ```
+    <logger name="com.morpheus.compute.nutanix.NutanixComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.NutanixComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.NutanixProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Openstack
+:   ```
+    ```
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.OpenStackProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.OpenStackSFSStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Option Types
+:   ```
+    ```
+    <logger name="com.morpheus.OptionSourceService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeListService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeService" level="DEBUG"/>
+    ```
+    ```
+
+Remote Console
+:   ```
+    ```
+    <logger name="com.morpheus.remote.MorpheusGuacamoleWebsocketHandler" level="DEBUG"/>
+    ```
+    ```
+
+SCVMM
+:   ```
+    ```
+    <logger name="com.morpheus.compute.scvmm.ScvmmComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ScvmmComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.ScvmmProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+ServiceNow
+:   ```
+    ```
+    <logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="DEBUG"/>  
+    <logger name="com.morpheus.integrations.ServiceNowUtility" level="DEBUG"/>
+    ```
+    ```
+
+Tasks
+:   ```
+    ```
+    <logger name="com.morpheus.task.AnsibleTowerTaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.TaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.WinrmTaskService" level="DEBUG"/>
+    ```
+    ```
+
+Terraform
+:   ```
+    ```
+    <logger name="com.morpheus.app.AbstractResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.TerraformProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Usage
+:   ```
+    ```
+    <logger name="com.morpheus.AccountPriceService" level="DEBUG"/>
+    ```
+    ```
+
+vCloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VcloudDirectorProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.VcdComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Veeam
+:   ```
+    ```
+    <logger name="com.morpheus.backup.VeeamBackupService" level="DEBUG"/>
+    ```
+    ```
+
+Vmware
+:   ```
+    ```
+    <logger name="com.morpheus.compute.VmwareComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.vmware.VmwareComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VmwareProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+vRO
+:   ```
+    ```
+    <logger name="com.morpheus.automation.VroService" level="DEBUG"/>
+    ```
+    ```
+
+## All core logger paths
+
+Expand below to see all core HPE Morpheus Enterprise logger paths set to INFO level.
+
+### All core logger paths
+
+```
+```
+<logger name="com.bertramlabs.plugins.AccountsAuthService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AccountsService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.ActiveDirectoryUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AzureSamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomApiUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomExternalUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.DefaultUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.JumpCloudUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.LdapUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OktaUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OneLoginUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.PingUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.SamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.UserSourceAuthenticationProvider" level="INFO"/>  
+<logger name="com.morpheus.AbstractComputeService" level="INFO"/>  
+<logger name="com.morpheus.AbstractPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.AccountBudgetService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationObjectService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.AccountInvoiceService" level="INFO"/>  
+<logger name="com.morpheus.AccountPriceService" level="INFO"/>  
+<logger name="com.morpheus.AccountResourceService" level="INFO"/>  
+<logger name="com.morpheus.AccountUsageService" level="INFO"/>  
+<logger name="com.morpheus.ActivityService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AbstractAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AmazonConvertibleRiAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.CostAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.UtilizationAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.WorkloadAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.AnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.api.AbstractApiService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.CommandService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.DownloadService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.UploadService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.AppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.HelmAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.MorpheusAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.ScribeResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAzurermResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformGoogleResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformVsphereResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceClientService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceDelayedJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceHealthService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceLicenseService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceStorageService" level="INFO"/>  
+<logger name="com.morpheus.approval.ApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.RemedyApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.ServiceNowApprovalService" level="INFO"/>  
+<logger name="com.morpheus.AppService" level="INFO"/>  
+<logger name="com.morpheus.ArchiveService" level="INFO"/>  
+<logger name="com.morpheus.AsyncService" level="INFO"/>  
+<logger name="com.morpheus.AuditLogService" level="INFO"/>  
+<logger name="com.morpheus.automation.AbstractConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleTowerService" level="INFO"/>  
+<logger name="com.morpheus.automation.ChefService" level="INFO"/>  
+<logger name="com.morpheus.automation.ConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.HelmService" level="INFO"/>  
+<logger name="com.morpheus.automation.PuppetService" level="INFO"/>  
+<logger name="com.morpheus.automation.SaltStackService" level="INFO"/>  
+<logger name="com.morpheus.automation.VroService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupExecutionInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStatus" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStorageService" level="INFO"/>  
+<logger name="com.morpheus.backup.DirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.FileBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.KarmanStorageProviderBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmImageBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmSnapshotBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusApplianceBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusContainerBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MysqlBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.SqlserverBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.TarDirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.BootMacService" level="INFO"/>  
+<logger name="com.morpheus.builds.AbstractBuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.BuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.JenkinsBuildsService" level="INFO"/>  
+<logger name="com.morpheus.CapacityService" level="INFO"/>  
+<logger name="com.morpheus.CatalogCartService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemTypeService" level="INFO"/>  
+<logger name="com.morpheus.certificate.AbstractCertificateService" level="INFO"/>  
+<logger name="com.morpheus.certificate.MorpheusCertificateService" level="INFO"/>  
+<logger name="com.morpheus.CertificateService" level="INFO"/>  
+<logger name="com.morpheus.ChefClientService" level="INFO"/>  
+<logger name="com.morpheus.cm.ChangeManagementService" level="INFO"/>  
+<logger name="com.morpheus.cm.CherwellCmService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.AbstractCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.CmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.RemedyCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="INFO"/>  
+<logger name="com.morpheus.code.AbstractCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.CodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GitCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GithubCodeService" level="INFO"/>  
+<logger name="com.morpheus.compliance.NVDSyncService" level="INFO"/>  
+<logger name="com.morpheus.compliance.PackageManagementService" level="INFO"/>  
+<logger name="com.morpheus.compute.cisco.UcsComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.CloudPluginComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeApiService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.compute.IpmiService" level="INFO"/>  
+<logger name="com.morpheus.compute.KubernetesComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.MaasComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ManualComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.OneviewComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.SelfManagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.standard.StandardComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.unmanaged.UnmanagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VmwareComputeService" level="INFO"/>  
+<logger name="com.morpheus.ComputeService" level="INFO"/>  
+<logger name="com.morpheus.container.ActivemqContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.container.ElasticsearchContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.JavaContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.MysqlContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.NodeContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.PostgresContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.RedisContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.SqlserverContainerService" level="INFO"/>  
+<logger name="com.morpheus.ContainerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ContainerService" level="INFO"/>  
+<logger name="com.morpheus.costing.AbstractCostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingInterface" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.StandardCostingService" level="INFO"/>  
+<logger name="com.morpheus.CurrencyConversionService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherGORMDatastoreService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherService" level="INFO"/>  
+<logger name="com.morpheus.DashboardService" level="INFO"/>  
+<logger name="com.morpheus.DatastoreService" level="INFO"/>  
+<logger name="com.morpheus.DataViewService" level="INFO"/>  
+<logger name="com.morpheus.DbSchedulerService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.CloudFoundryAppDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DefaultDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DockerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.GrailsDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.IisDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.JbossDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.KubernetesDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.NodeDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.ServerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.VmDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.DeploymentService" level="INFO"/>  
+<logger name="com.morpheus.discovery.AbstractDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DatastoreCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostBalancingDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ReservationRecommendationDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ShutdownDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.SizeDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.dns.AbstractDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.BindDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.ConsulDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.DNSProvider" level="INFO"/>  
+<logger name="com.morpheus.dns.DnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.MicrosoftDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PluginDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PowerDnsService" level="INFO"/>  
+<logger name="com.morpheus.ElasticCleanupService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentVariableService" level="INFO"/>  
+<logger name="com.morpheus.ExecuteScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.ExecutionRequestService" level="INFO"/>  
+<logger name="com.morpheus.export.AccountInvoiceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.CodeRepositoryExportService" level="INFO"/>  
+<logger name="com.morpheus.export.DeploymentExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExecuteScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExportService" level="INFO"/>  
+<logger name="com.morpheus.export.InstanceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AdminIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AutomationIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.BackupIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.CertificateIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.DeployIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.NetworkIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerExpertService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerInstancesExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkDomainExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkPoolExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkRouterExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkSecurityGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.PowerScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServicePlanExportService" level="INFO"/>  
+<logger name="com.morpheus.export.TaskExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ThresholdExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.WorkflowExportService" level="INFO"/>  
+<logger name="com.morpheus.FileCopyRequestService" level="INFO"/>  
+<logger name="com.morpheus.GlobalSearchService" level="INFO"/>  
+<logger name="com.morpheus.host.AbstractHostService" level="INFO"/>  
+<logger name="com.morpheus.host.DockerHostService" level="INFO"/>  
+<logger name="com.morpheus.host.ExternalKubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.KubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.SwarmHostService" level="INFO"/>  
+<logger name="com.morpheus.HttpClientService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubQueueService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubSyncService" level="INFO"/>  
+<logger name="com.morpheus.imagebuild.ImageBuildService" level="INFO"/>  
+<logger name="com.morpheus.ImageCacheService" level="INFO"/>  
+<logger name="com.morpheus.instance.InstanceUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.InstanceService" level="INFO"/>  
+<logger name="com.morpheus.InstanceTypeService" level="INFO"/>  
+<logger name="com.morpheus.integration.AbstractIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.CherwellIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.GitRepoService" level="INFO"/>  
+<logger name="com.morpheus.integration.RemedyIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.RunDeckIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.SalesForceIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.ScribeService" level="INFO"/>  
+<logger name="com.morpheus.integration.ServiceNowIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.TerraformService" level="INFO"/>  
+<logger name="com.morpheus.jobs.AbstractJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.JobExecutor" level="INFO"/>  
+<logger name="com.morpheus.jobs.KubernetesJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.SecurityScanExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.TaskJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.WorkflowJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.JobService" level="INFO"/>  
+<logger name="com.morpheus.KeyPairService" level="INFO"/>  
+<logger name="com.morpheus.library.LayoutService" level="INFO"/>  
+<logger name="com.morpheus.LicenseService" level="INFO"/>  
+<logger name="com.morpheus.LoadBalancerPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.LocalizationService" level="INFO"/>  
+<logger name="com.morpheus.LocalRepoService" level="INFO"/>  
+<logger name="com.morpheus.log.AbstractLogService" level="INFO"/>  
+<logger name="com.morpheus.log.LogRhythmLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SplunkLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SyslogLogService" level="INFO"/>  
+<logger name="com.morpheus.LogService" level="INFO"/>  
+<logger name="com.morpheus.maint.UpdateService" level="INFO"/>  
+<logger name="com.morpheus.MarketplaceClientService" level="INFO"/>  
+<logger name="com.morpheus.MarshallService" level="INFO"/>  
+<logger name="com.morpheus.MetadataTagService" level="INFO"/>  
+<logger name="com.morpheus.migration.AbstractMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.HypervisorMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.LvmMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.MigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.WindowsMigrationService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlerterService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlertRuleService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AvailabilityService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.CheckAgentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.IncidentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorAppService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorChartingService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckManagementService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitoringService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MorpheusMonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.NewRelicService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.ServiceNowService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusComputeService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusPackageService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusSecurityService" level="INFO"/>  
+<logger name="com.morpheus.MotdService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AviLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.BluecatNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.BootService" level="INFO"/>  
+<logger name="com.morpheus.network.CitrixNetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.CloudPluginNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulService" level="INFO"/>  
+<logger name="com.morpheus.network.F5BigIpLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.F5LineRateLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.FirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.FortiADCLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.HaproxyLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InfobloxNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.IPAMProvider" level="INFO"/>  
+<logger name="com.morpheus.network.KubernetesRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.LoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.LocalFirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkConfigService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkServicesService" level="INFO"/>  
+<logger name="com.morpheus.network.NutanixNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PaloAltoNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.PhpipamNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PluginNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PxeService" level="INFO"/>  
+<logger name="com.morpheus.network.SolarWindsNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.StealthNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.NetworkDomainService" level="INFO"/>  
+<logger name="com.morpheus.OauthProviderService" level="INFO"/>  
+<logger name="com.morpheus.OperationEventService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourcePluginService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourceService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeListService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeService" level="INFO"/>  
+<logger name="com.morpheus.os.LinuxOsService" level="INFO"/>  
+<logger name="com.morpheus.os.WindowsOsService" level="INFO"/>  
+<logger name="com.morpheus.PermissionService" level="INFO"/>  
+<logger name="com.morpheus.plugin.AbstractPluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.BackupProviderPluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupJobImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupRestoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupResultImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationGroupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationSiteImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeServerInterfaceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeZoneFolderImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusDatastoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusAccountInvoiceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusCostingImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.cypher.MorpheusCypherImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusAccountInventoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusIntegrationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusCloudImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputePortImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeServerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeLayoutFactoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeSetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeZonePoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContainerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContextImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusInstanceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOperationNotificationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOsTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusPermissionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusProcessImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusReportImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusServicePlanImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusSnapshotImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStatsImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusTaskImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusUsageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageLocationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusWikiPageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainRecordImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolIpImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolRangeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkSubnetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.provisioning.MorpheusProvisionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.web.MorpheusWebRequestImplService" level="INFO"/>  
+<logger name="com.morpheus.policy.AbstractPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.BackupStoragePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.MotdPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.NetworkPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.PolicyServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageBucketQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageServerQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageShareQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.TagCompliancePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.WorkflowPolicyService" level="INFO"/>  
+<logger name="com.morpheus.PolicyService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.PriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.PricePlanService" level="INFO"/>  
+<logger name="com.morpheus.ProcessService" level="INFO"/>  
+<logger name="com.morpheus.ProfileService" level="INFO"/>  
+<logger name="com.morpheus.project.ProjectService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractBoxProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.CloudPluginProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerEngineProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ExternalProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.HelmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.IProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.KubernetesProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.MaasProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ManualProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.OneviewProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ScribeProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SelfManagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.StandardProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SwarmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.TerraformProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UcsProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UnmanagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.WorkflowProvisionService" level="INFO"/>  
+<logger name="com.morpheus.ProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.ProxyService" level="INFO"/>  
+<logger name="com.morpheus.ReferenceService" level="INFO"/>  
+<logger name="com.morpheus.report.AbstractReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonCoverageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonSavingsReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonUtilizationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CostReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InvoiceReportService" level="INFO"/>  
+<logger name="com.morpheus.report.MigrationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.PluginReportService" level="INFO"/>  
+<logger name="com.morpheus.report.ReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TenantUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TimeSeriesCostReportService" level="INFO"/>  
+<logger name="com.morpheus.RoleService" level="INFO"/>  
+<logger name="com.morpheus.RpcService" level="INFO"/>  
+<logger name="com.morpheus.scale.AbstractScaleService" level="INFO"/>  
+<logger name="com.morpheus.scale.MorpheusScaleService" level="INFO"/>  
+<logger name="com.morpheus.ScaleService" level="INFO"/>  
+<logger name="com.morpheus.scribe.ScribeLibraryService" level="INFO"/>  
+<logger name="com.morpheus.ScriptConfigService" level="INFO"/>  
+<logger name="com.morpheus.sdn.AbstractSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.MorpheusSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.OvsService" level="INFO"/>  
+<logger name="com.morpheus.sdn.VethSdnService" level="INFO"/>  
+<logger name="com.morpheus.security.AbstractSecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.security.ScapScanService" level="INFO"/>  
+<logger name="com.morpheus.security.SecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.SecurityGroupService" level="INFO"/>  
+<logger name="com.morpheus.SequenceService" level="INFO"/>  
+<logger name="com.morpheus.ServerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ServerService" level="INFO"/>  
+<logger name="com.morpheus.ServicePlanService" level="INFO"/>  
+<logger name="com.morpheus.SettingsService" level="INFO"/>  
+<logger name="com.morpheus.SetupService" level="INFO"/>  
+<logger name="com.morpheus.SiteService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotService" level="INFO"/>  
+<logger name="com.morpheus.StatsService" level="INFO"/>  
+<logger name="com.morpheus.StatusService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.BasicStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.CephStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.EcsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.IsilonStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.KubernetesStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.NfsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.QnapFileStationService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageVolumeService" level="INFO"/>  
+<logger name="com.morpheus.storage.ThreeParStorageService" level="INFO"/>  
+<logger name="com.morpheus.StorageProviderService" level="INFO"/>  
+<logger name="com.morpheus.SubAccountService" level="INFO"/>  
+<logger name="com.morpheus.task.AbstractTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTowerTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ChefTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerTemplateTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.EmailTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ExecutableTaskInterface" level="INFO"/>  
+<logger name="com.morpheus.task.GroovyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.HttpTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JavascriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JRubyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.LocalScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PuppetTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PythonTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.RestartTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ShellTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskConfigService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskService" level="INFO"/>  
+<logger name="com.morpheus.task.VroTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WinrmTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WriteAttributesTaskService" level="INFO"/>  
+<logger name="com.morpheus.trust.AbstractCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialProvider" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CypherCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.InternalCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.PluginCredentialService" level="INFO"/>  
+<logger name="com.morpheus.UsageLimitService" level="INFO"/>  
+<logger name="com.morpheus.UserGroupService" level="INFO"/>  
+<logger name="com.morpheus.UserManagementService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiAppService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiGatewayService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiPoolService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImagePriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImageService" level="INFO"/>  
+<logger name="com.morpheus.WikiPageService" level="INFO"/>  
+<logger name="com.morpheus.worker.DistributedWorkerService" level="INFO"/>  
+<logger name="com.morpheus.ZoneFolderService" level="INFO"/>  
+<logger name="com.morpheus.ZoneMarketplaceService" level="INFO"/>  
+<logger name="com.morpheus.ZonePoolService" level="INFO"/>  
+<logger name="com.morpheus.ZoneRegionService" level="INFO"/>  
+<logger name="com.morpheus.ZoneService" level="INFO"/>
+```
+```
+
+## Audit logs
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+2. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+3. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+4. Once the service has stopped enter the following at the xml prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+5. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..29375d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 279,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..4490d3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,12 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html)**
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json b/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
new file mode 100644
index 0000000..85d46c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+  "title": "Virtual Machines",
+  "ordinal": 211,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md b/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
new file mode 100644
index 0000000..4c9b64f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
@@ -0,0 +1,22 @@
+# Virtual Machines
+
+![../../_images/infra_compute_header_vms_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-354FC170-C67F-4589-B0CA-75A62F884A32-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+The Virtual Machines tab lists all managed and unmanaged VMs across HPE Morpheus Enterprise. Managed VMs are either provisioned by HPE Morpheus Enterprise, or are inventoried/discovered VMs that have been converted to managed. Unmanaged VMs are typically inventoried/discovered VMs from Cloud integrations.
+
+## Virtual Machine Change Cloud
+
+Change Cloud functionality allows a server to be reassociated to a new Cloud, which may be necessary at times for easier record keeping in HPE Morpheus Enterprise. In order to use this feature, the user must have “Infrastructure: Move Servers” permission set to “Full.”
+
+Changing Clouds might be necessary, for example, when moving a VM from one vCenter datacenter to another. We can use this tool to update the Cloud association in HPE Morpheus Enterprise as well. Other scenarios may include migrating workloads from private Cloud to public Cloud or even creating a brand new VM in a new Cloud which represents an identical workload to something pre-existing but which will be retired.
+
+NOTE
+
+For VMware Clouds, Cloud reassignment occurs automatically when a server is migrated from one cluster to another or from one resource pool to another within the same cluster. Following the next Cloud sync, HPE Morpheus Enterprise will reflect the migration made in vCenter. In this scenario, you should not try to use the manual change Cloud tools. In fact, you will receive a warning in HPE Morpheus Enterprise logs if you attempt to do so.
+
+To change Clouds, navigate to the VM detail page (Infrastructure > Compute > Virtual Machines > selected VM), click on the ACTIONS menu, and click Change Cloud. You can select the new target Cloud here and optionally select a new VM which the current one should be merged into. The important thing to keep in mind is that this tool is for HPE Morpheus Enterprise record keeping only. **It is not a tool which does migration work for you.** See the embedded video below for a demonstration of this feature.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json b/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
new file mode 100644
index 0000000..298783f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+  "title": "SSL Certificates",
+  "ordinal": 241,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md b/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
new file mode 100644
index 0000000..70d0220
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
@@ -0,0 +1,3 @@
+# SSL Certificates
+
+SSL certificates authenticate the identity of web servers and encrypt the data being transmitted. HPE Morpheus Enterprise stores SSL certificates to simplify administration and application of SSL certificates to HPE Morpheus Enterprise-managed resources.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json b/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
new file mode 100644
index 0000000..dbd971c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+  "title": "Unable to Provision a Custom Image",
+  "ordinal": 357,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Provision a Custom Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md b/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
new file mode 100644
index 0000000..69d4a98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
@@ -0,0 +1,22 @@
+# Unable to Provision a Custom Image
+
+## About this task
+
+Prior to provisioning an custom image, the image must be configured in the Library > Virtual Images section by selecting Edit on the Actions dropdown of the Virtual Image.
+
+In the Edit Virtual Image pane:
+
+## Procedure
+
+1. Select “Cloud Init Enabled?” only if the Virtual Image is a linux image with cloud init installed.
+2. Enter the username and password that are set on the Virtual Image.
+
+## Results
+
+NOTE
+
+When using Static IP’s or IP Pools in VMware, VMware tools must also be installed on the template in order for HPE Morpheus Enterprise to set the static IP address when provisioning.
+
+NOTE
+
+HPE Morpheus Enterprise agents only support 64-bit vm’s prior to versions 2.12.3 and 3.0.2
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..b61ff2b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 509,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..0b39167
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,177 @@
+# ArubaCX Network Integration
+
+## Overview
+
+The ArubaCX network plugin is implemented as a HPE Morpheus Enterprise `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by HPE Morpheus Enterprise and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. HPE Morpheus Enterprise integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
+
+## Features
+
+- Network - Create or Delete OVS Port Group.
+
+## Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+### Server Network Configuration (Netplan)
+
+#### Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
+
+### Switch Configuration
+
+#### Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
+
+## Adding ArubaCX Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
+
+## Add ArubaCX Integration to a Cluster
+
+### Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json b/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
new file mode 100644
index 0000000..8215eb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+  "title": "Task Types",
+  "ordinal": 108,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md b/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
new file mode 100644
index 0000000..fe77622
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
@@ -0,0 +1,25 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| ansible | Ansible | Runs an Ansible playbook. Ansible Integration required | Ansible Repo (Git) | Local, Resource | Existing Ansible Integration | Library: Tasks |
+| ansibletower | Ansible Tower | Relays Ansible calls to Ansible Tower | Tower Integration | Local, Remote, Resource | Existing Ansible Tower Integration | Library: Tasks |
+| chef | Chef bootstrap | Executes Chef bootstrap and run list. Chef Integration required | Chef Server | Resource | Existing Chef Integration | Library: Tasks |
+| conditional | Conditional Workflow | Allows the user to set JavaScript logic. If it resolves to `true`, HPE Morpheus Enterprise will run the Operational Workflow set as the “IF OPERATIONAL WORKFLOW” and if it resolves to `false`, HPE Morpheus Enterprise will run the “ELSE OPERATIONAL WORKFLOW” | N/A (JavaScript logic must be locally sourced, Tasks housed within the associated Workflows may have different sourcing options depending on their types.) | Local | Existing Operational Workflows | Library: Tasks |
+| email | Email | Send an email from a Workflow | Task Content | Local | SMTP Configured | Library: Tasks |
+| groovy | Groovy script | Executes Groovy Script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| http | HTTP | Executes REST call for targeting external API’s. | Local | Local | None | Library: Tasks |
+| javascript | Javascript | Executes Javascript locally (on HPE Morpheus Enterprise app node) | Local | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| jruby | jRuby Scirpt | Executes Ruby script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| libraryscript | Library Script | Creates a Task from an existing Library Script (Library > Templates > Script Templates) | Library Script | Resource | Existing Library Script | Library: Tasks |
+| template | Library Template | Creates a Task from an existing Library Template (Library > Templates > Spec Templates) | Library Template | Resource | Existing Library Templates | Library: Tasks |
+| nestedworkflow | Nested Workflow | Embeds a Workflow into a Task which allows the Workflow to be nested within other Workflows for situations when common Task sets are frequently used in Workflows | N/A | Local | N/A | Library: Tasks |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| puppet | Puppet Agent Install | Executes Puppet Agent bootstrap, writes `puppet.conf` and triggers agent checkin. Puppet Integration required | Puppet Master | Resource | Existing Puppet Integration | Library: Tasks |
+| python | Python Script | Executes Python Script locally | Local, Repository, Url | Local | `virtualenv` installed on Appliance Nodes | Library: Tasks, Tasks ‐ Script Engines |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
+| vro | vRealize Orchestrator Workflow | Executes vRO Workflow on the Target Resource | vRO Integration | Local, Resource | Existing vRO Integration | Library: Tasks |
+| wa | Write Attributes | Add arbitrary values to the Attributes map of the target resource | N/A | Local | Provide map of values as valid JSON | Library: Tasks |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json b/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
new file mode 100644
index 0000000..4a4d4e8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+  "title": "Uploading OS Images",
+  "ordinal": 406,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md b/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
new file mode 100644
index 0000000..6c3623a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
@@ -0,0 +1,15 @@
+# Uploading OS Images
+
+## Prerequisites
+
+- Image upload and deployment performance depend on network bandwidth and storage backend performance.
+- File permissions on shared storage must allow Morpheus read access.
+- OS images must be bootable and compatible with the target bare metal hardware.
+- Server reboots and virtual media behavior depend on hardware management interfaces (for example, iLO).
+
+**Subtopics**  
+
+- **[Uploading OS Images Using Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html)**
+- **[Uploading OS Images Using S3-Compatible Object Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html)**
+- **[Uploading OS Images Using CIFS (Samba)](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html)**
+- **[Uploading OS Images Using NFS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json b/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
new file mode 100644
index 0000000..00d9d60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+  "title": "How to un-manage an Instance/VM/Host",
+  "ordinal": 350,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html",
+  "topic_cluster": {
+    "clustering_title": "How to un-manage an Instance/VM/Host",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md b/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
new file mode 100644
index 0000000..d5fcfc8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
@@ -0,0 +1,63 @@
+# How to un-manage an Instance/VM/Host
+
+## Description
+
+A managed VM (and associated Instance) needs to be unmanaged and returned to Discovered type.
+
+## Solution
+
+### About this task
+
+Delete the record from the Infrastructure  >  Compute (! not from Provisioning - Instances) selection with the following configuration in the Delete modal:
+
+- `Remove Infrastructure` UNCHECKED
+- `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+- `Force Delete` UNCHECKED
+
+The most important items to be aware of when “un-managing” an Instance/VM/Host are:
+
+### Procedure
+
+1. The “Remove from Infrastructure” flag when deleting a VM or Host in HPE Morpheus Enterprise determines if the actual VM is deleted from the target Infrastructure. 
+
+   - Checking “Remove Infrastructure” means you WANT TO DELETE THE ACTUAL VM. Typing “DELETE” in the confirmation field is required when “Remove From Infrastructure” is enabled.
+   - Unchecking “Remove Infrastructure” means you only want to delete the record in HPE Morpheus Enterprise but leave the actual VM untouched.
+2. Deleting an Instance will always remove Infrastructure. 
+
+   IMPORTANT
+
+   REPEAT: Deleting an Instance from the `Provisioning` section will always remove the VM aka Infrastructure.
+3. After removing the record from HPE Morpheus Enterprise, the VM must be in a Cloud with Inventory enabled to automatically be re-discovered.
+
+## Process
+
+### About this task
+
+Steps to delete a managed VM from HPE Morpheus Enterprise and, when necessary, remove the associated Instance:
+
+### Procedure
+
+1. Navigate to the VM (not Instance) detail page at Infrastructure  >  Compute - VMs 
+
+   NOTE
+
+   VM’s inside an Instance can be navigated to inside the Instance Details page by selecting the VM in the `VM's` seciton on the Instance Details page.
+2. Select DELETE
+3. Configure the DELETE HOST modal with the following settings: 
+
+   ![../_images/delete_host_modal.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7627FF0E-DEA9-4A41-8E6B-E1E752BA731F-high.png)
+   - `Remove Infrastructure` UNCHECKED
+   - `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+   - `Force Delete` UNCHECKED
+
+   IMPORTANT
+
+   If you have to type DELETE that means the `Remove Infrastructure` flag is selected and you are confirming deletion of the actual VM. Ensure `Remove Infrastructure` is UNCHECKED when you want to leave the VM intact!
+4. Select DELETE
+5. The VM and associated Insatnce will be removed from HPE Morpheus Enterprise but the actual VM will remain.
+6. Wait up to 5 min or click REFRESH on the associated Clouds details page to force a cloud sync. 
+
+   NOTE
+
+   `Inventory` must be enabled on the associated cloud for the VM to automatically be re-discovered by HPE Morpheus Enterprise.
+7. The VM is now back in HPE Morpheus Enterprise as discovered/unmanaged. To managed and create a new Instance from the VM, select ACTIONS : Convert To Managed.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json b/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
new file mode 100644
index 0000000..b6aef3b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+  "title": "Overview",
+  "ordinal": 147,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md b/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
new file mode 100644
index 0000000..872bf07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
@@ -0,0 +1,17 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. HPE Morpheus Enterprise includes a rich catalog of pre-configured System Images available for every cloud type. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into HPE Morpheus Enterprise via local file or url. Amazon and Azure Marketplace images can also be added to the Virtual Images Section.
+
+Understanding the process of prepping images for consumption in HPE Morpheus Enterprise is a very important step toward building an effective HPE Morpheus Enterprise environment. In addition to the information contained in this section on Virtual Images, it may be helpful to see a complete image prep example walkthrough. Our getting started guide for HPE Morpheus Enterprise and VMware includes [a section on preparing images](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html#prepping-an-image) that may provide a helpful example.
+
+TIP
+
+HPE Morpheus Enterprise includes a wide catalog of system image types as examples to show how the product can be used and to give users a starting point for implementing their own library. The included images are not intended to be production-ready images. HPE Morpheus Enterprise always recommends its users create their own gold images which meet their required specifications.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. HPE Morpheus Enterprise syncs in as much meta-data as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json b/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
new file mode 100644
index 0000000..ba3aeb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+  "title": "Configuring Tenants and Resources for Multi-Tenancy",
+  "ordinal": 278,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md b/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
new file mode 100644
index 0000000..1284531
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
@@ -0,0 +1,264 @@
+# Configuring Tenants and Resources for Multi-Tenancy
+
+A very common scenario for Managed Service Providers (MSPs) is the need to provide access to resources on a customer-by-customer basis. Several administrative features are available in HPE Morpheus Enterprise to ensure customer resources are properly scoped and isolated. With its built-in multi-tenancy capabilities and white label support, managed service providers have a wide range of capabilities when it comes to managing customer Tenants and users.
+
+## Tenants
+
+There are essentially two types of Tenants in HPE Morpheus Enterprise
+
+- Master Tenant
+- Sub Tenants
+
+During the initial setup of a HPE Morpheus Enterprise Appliance, the Master Tenant is created. All Tenants created in addition to this Master Tenant are Subtenants. There is only one Master Tenant, though its child Tenants can create child Tenants of their own. The Master Tenant may scope resources to all other Tenants while any Subtenants which have children of their own may only scope resources to their immediate children Tenants.
+
+### Creating Tenants
+
+#### About this task
+
+The Master Tenant is created during the initial appliance setup. Additional sub-Tenants can be created in the Administration > Tenants section.
+
+The Tenants page displays a list of all Tenants. This page enables users to: Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, Status (active or inactive) and the Created Date. Click the Tenant Name to drill into the Tenant View where you can edit or delete the Tenant, as well as create, edit and delete users belonging to the Tenant.
+
+NOTE
+
+At least one Tenant in addition to the Master Tenant is required to scope resources across Tenants.
+
+To create a new sub-Tenant
+
+#### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the +Create Tenant button.
+4. From the New Tenant wizard input \* Name (Required) \* Description \* Base Role \* Currency (for pricing)
+
+#### Results
+
+The Base Role defines a role set from which all roles created within the Tenant will inherit.
+
+NOTE
+
+In prior versions, we could set Limits when creating a Subtenant. These could restrict the amount of storage, memory, and CPUs that can be collectively provisioned by all users in the Tenant. In more recent versions, this functionality has been rolled into Policies (Administration > Policies). When creating a Policy, we are able to specify a Tenant to which the Policy should apply.
+
+Click the Save Changes button.
+
+![The Create Tenant dialog box is shown](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-16DD7A70-0CA9-44E3-8361-DBA158D96416-high.png)
+
+### Viewing Tenants
+
+To View an individual Tenant page, select the Tenant name from the main Tenants section.
+
+![../../_images/viewtenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-39DE1887-6BEA-45F1-B234-9F2921BD663A-high.png)
+
+From inside the Tenant view, we can edit or delete the Tenant, as well as click into any of the Tenant’s users.
+
+### Tenant Users
+
+To create a new user within the Tenant:
+
+Click the CREATE USER button, then from the New User wizard input the fields below:
+
+- First Name
+- Last Name
+- Username
+- Email
+- Role
+- Password
+- Confirm Password
+
+Click Save Changes.
+
+NOTE
+
+Users are specific to each Tenant. Users created in the Master Tenant or other sub-Tenants will only have access to the Tenant they are created in.
+
+### Impersonate Tenant User
+
+HPE Morpheus Enterprise allows admin users in parent Tenants to impersonate any user in their child Tenants to see HPE Morpheus Enterprise as if they are that user. To impersonate a user, you must be logged in as a user with the “Impersonate User” feature enabled in the assigned role.
+
+From inside a Tenant detail page (containing the list of that Tenant’s users), and in the specific user’s ACTIONS drop down, select “Impersonate”.
+
+![../../_images/configuring_multi_tenancy-9583a.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-071C08CB-F499-4A7F-BFCA-87B4C6B6D08F-high.png)
+
+This will log you in as that user in their respective Tenant. To log out of the impersonate users Tenant, select the username in the header, and then select “Quit Impersonating”
+
+![../../_images/configuring_multi_tenancy-d229b.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C13E674E-CE80-485D-B60E-0F33BD0BE2F7-high.png)
+
+## Resources
+
+In the Master Tenant, resources can be configured with private or public visibility:
+
+- Private Visibility: Only available to the assigned Tenant.
+- Public Visibility (option available in Master Tenant only): Available across all Tenants
+
+Resources in the Master Tenant can also be assigned directly to Subtenants. When a resource is assigned to a Subtenant, it is only available for that Subtenant, and its visibility is automatically set to private. Public visibility is not an option for any resource assigned to or created in a Subtenant.
+
+From the Master Tenant, the following resources can be configured for public visibility across all Tenants, or assigned to individual sub-Tenants
+
+- Clouds
+- Hosts
+- Virtual Machines
+- Networks
+- Datastores
+- Resource Pools
+- Folders
+- Virtual Images
+- Library Instance Types
+- Pricing
+- Policies
+- Workflows
+- Roles
+
+NOTE
+
+Virtual Image Blueprints can be made available to multiple select Tenants when set to private.
+
+### Cloud Visibility & Assignment
+
+#### About this task
+
+To set the visibility of a Cloud to Public (shared across all Tenants) or Private (only available to the assigned Tenant):
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-349e2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF8023AD-C31F-4FF1-A51C-AE47C55EA399-high.png)
+
+When a cloud is set to Public visibility, it is available to be added to Subtenants. All Subtenants created after a Master Tenant cloud is set to public will automatically have clouds with public visibility added, and a group will be created for each available cloud matching the cloud name in the new Subtenant(s).
+
+For Tenants created prior to a Master Tenant cloud being set to public visibility, the Subtenant will have the option to add that cloud but it will not automatically be added.
+
+While the cloud will be available for Subtenants, the resources available in that cloud to the Subtenant(s) depends on the visibility or assignment of the individual resources.
+
+NOTE
+
+A Subtenant user must have sufficient role permissions and cloud access to add publicly available clouds. Master Tenant clouds settings cannot be edited from Subtenants.
+
+### Assign a Cloud to an Tenant
+
+IMPORTANT
+
+When assigning a Cloud to a Tenant, all resources for that Cloud will only be available to the assigned Tenant. If a cloud is created in the Master Tenant and assigned to a sub-Tenant, it will no longer be available for use by the Master Tenant or any other sub-Tenants, although it can be assigned back to the Master Tenant, or to another sub-Tenant.
+
+It may be preferable for service providers to share or assign their cloud resources, such as specific hosts, networks, resources pools and datastores, across sub-Tenants, rather than an entire cloud.
+
+### To assign a cloud from the Master Tenant to a Sub-Tenant
+
+#### Procedure
+
+1. Navigate to Infrastructure, Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Tenant” drop down, select the Tenant to assign the cloud to. The visibility will automatically be set to “Private” when a cloud is assigned to a sub-Tenant.
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-c907d.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1741E74F-481B-4D67-A2B0-B338A4958C9E-high.png)
+
+When a cloud is assigned to a sub-Tenant, or assigned to the Master Tenant with private visibility, that cloud and all of its resources are only available to the assigned Tenant. The Master Tenant still maintains control and visibility, and can edit the cloud settings or re-assign the cloud.
+
+### Individual Resource Visibility & Assignment
+
+Similar to clouds, individual resources from the Master Tenant can be set to public and available to sub-Tenants, or assigned to sub-Tenants.
+
+By default, any host, virtual machine, bare metal server, network, resource pool, datastore or blueprint added, created or inventoried by an Tenant is assigned to that Tenant. If these resources are in the Master Tenant, they can be assigned to sub Tenants. Assigning one of these resources will make it unavailable to the Master Tenant, but it will still be visible and editable by the Master Tenant. This allows Master Tenant resources to be isolated for use by sub-Tenants while still under the control of the Master Tenant.
+
+Resources assigned to sub-Tenants from the Master Tenant will be visible and available for use by that sub-Tenant, however they cannot be edited or re-assigned by the sub-tenant.
+
+### Set the Visibility of a Host, Virtual Machine or Bare metal Server to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. Select Edit in the resource page to bring up the config modal
+5. From the “Visibility” drop down, select either “Public” or “Private”
+6. Select Save Changes
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-d738d.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A6C1B836-5DF2-47CE-A78A-0A94A1A777C0-high.png)
+
+Assigning a Host, Virtual Machine, or Bare Metal server to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. From the “Actions” dropdown in the the resource page, select Assign Tenant
+5. In the Assign Tenant modal, select the Tenant to assign the resource to.
+6. Select Execute in the modal
+
+![../../_images/configuring_multi_tenancy-3c39f.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0DC2CDEE-E498-4EF1-B0B5-B54260A82FF7-high.png)
+
+The resource will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+### Set the Visibility of a Network to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-bc333.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9AB26FDA-4C5C-4F4C-ACD5-1013B6D3F162-high.png)
+
+### Assign a Network to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Tenant” drop down, select an Tenant to assign the network to.
+4. Select Save Changes in the lower the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-9f15c.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FC41C95A-2672-476A-B22E-2C2541407BB8-high.png)
+
+The Network will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+Set the Visibility or assign a datastore to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Storage
+2. Select the “Data Stores” tab
+3. Select Edit from the “Actions” dropdown in the datastores row
+4. From the “Visibility” drop down, select either “Public” or “Private”
+5. From the “Tenant” drop down, select the Tenant to assign the datastore to.
+
+   NOTE
+
+   If assigned to a sub-tenant, the visibility will be automatically set to private.
+6. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-1e978.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-77B5C886-86F4-40C1-A0D1-DE6EDDA1EBBB-high.png)
+
+### Set the Visibility or assign a Virtual Image to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Provisioning, Virtual Images
+2. Select Edit from the “Actions” dropdown in the Virtual Images row
+3. From the “Visibility” drop down, select either “Public” or “Private”. Public will share the
+4. From the “Tenant” field, start typing the name of the Tenant to assign the Virtual Image to. Matching Tenants will populate, then select the Tenant to add. 
+
+   NOTE
+
+   Virtual Images can be set to Private, but accessible to more that one Tenant
+
+#### Results
+
+#. Repeat step 4 for all Tenants requiring access to the virtual image. .. To remove access for an Tenant, click the “x” next to the Tenant name #. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-d9abe.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-453CA12C-D7A9-4CFE-83D3-B133334EE8C4-high.png)
+
+The Virtual Image will now be available for use by the assigned Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json b/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
new file mode 100644
index 0000000..2977108
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+  "title": "Chef",
+  "ordinal": 377,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html",
+  "topic_cluster": {
+    "clustering_title": "Chef",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md b/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
new file mode 100644
index 0000000..00b0a69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
@@ -0,0 +1,74 @@
+# Chef
+
+## Overview
+
+HPE Morpheus Enterprise integrates with one or multiple Chef servers to be used for bootstrapping while provisioning or as tasks in workflows in the Automation section. These workflows can then be run during provisioning in the provisioning wizard Automation pane, or on an existing Instance by selecting Run Workflows from the Actions menu on the Instance detail page. Workflows can also be added to Instances in the blueprint and app sections.
+
+## Add Chef Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Chef”
+3. Populate the following fields: 
+
+   - Name: Name of the Chef Integration in HPE Morpheus Enterprise
+   - Chef Endpoint: url of chef server api endpoint in <https://api.example.com> format. Do not add /organization/xxxx here, which is populated in the Chef Organization field
+   - Chef Version: 12.3.0 by default, can be changed to use a different/more recent version of chef
+   - Chef Organization: Chef Server Organization
+   - Chef User: Chef Server User
+   - User Private Key: The private key of the user with access to this chef server
+   - Organization Validator: Validator key for the organization
+4. Save Changes
+
+### Results
+
+The added Chef Integration is now available for use in HPE Morpheus Enterprise. The Chef Integration can be added to Clouds or Groups to auto-bootstrap nodes and specify Environment, Node ID, Runlist, Attributes and Tags when creating instances. The Chef integration can also be selected in the Chef Server dropdown when creating a Chef Bootstrap-type Task.
+
+NOTE
+
+Integrating Chef with HPE Morpheus Enterprise enables a user to bootstrap a node using Chef Bootstrap-type Tasks or Chef associations with Clouds or infrastructure Groups. It does not enable users to update run-lists on the Chef server for nodes which have already been bootstrapped.
+
+## Scope Chef Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Scope Chef Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Chef Integration added, a Chef section will appear in the Config section of the provisioning wizard. By default, Chef is enabled, but can be disabled by expanding the Chef section and unchecking Enable Chef.
+
+Chef Integration Provisioning options:
+
+Enable Chef
+:   Select to bootstrap
+
+Chef Environment
+:   Populate Chef environment, or leave as \_default
+
+Chef Node ID
+:   Defaults to instance name, configurable.
+
+Chef Runlist
+:   Add Runlist
+
+CHEF ATTRIBUTES
+:   Add Chef Attributes
+
+CHEF TAGS
+:   Add Chef tags
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json b/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
new file mode 100644
index 0000000..0660f9f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+  "title": "Activity",
+  "ordinal": 78,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md b/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
new file mode 100644
index 0000000..eef1bb5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
@@ -0,0 +1,61 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. HPE Morpheus Enterprise defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, and so on. This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+## Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+### To View a Recent Activity report:
+
+#### Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+#### Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
+
+### Review
+
+To review the item the activity occurred on, click the name of the activity and it will go to a new page and display that item.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, Groups, and Monitoring Checks.
+
+### To Filter:
+
+#### Procedure
+
+1. Click the filter drop down of type of filter you want to apply.
+2. Select the appropriate filter.
+
+## Alarms
+
+The ALARMS section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus Enterprise but synced and displayed for visibility in HPE Morpheus Enterprise.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
+
+## History
+
+The HISTORY section shows Process History from Instances and Apps processes. This is an aggregate view of the `History` tab in Instance and App details pages.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for HPE Morpheus Enterprise services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json b/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
new file mode 100644
index 0000000..6952f5e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+  "title": "Task Results",
+  "ordinal": 111,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html",
+  "topic_cluster": {
+    "clustering_title": "Task Results",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md b/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
new file mode 100644
index 0000000..eb0eaa2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
@@ -0,0 +1,161 @@
+# Task Results
+
+## Overview
+
+Using Task results, the output from any preceding Tasks within the same Workflow phase is available to be called into additional Tasks. The results are stored on the `results` variable. Since results are available to all Tasks, we can use results from any or all prior Tasks so long as they are executed within the same provision phase.
+
+In script type tasks, if a RESULT TYPE is set, HPE Morpheus Enterprise will store the output on the `results` variable. It’s important to understand that the result type indicates the format of the Task output HPE Morpheus Enterprise should expect. HPE Morpheus Enterprise will parse that output into a Groovy map which can be retrieved and further parsed by resolving the `results` variable. If the RESULT TYPE is incorrectly set, HPE Morpheus Enterprise may not be able to store the Task results correctly. Jump to the section on [Script Config Examples](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1AAB6E42-CAE7-456C-85D2-FC3E917F731C.xml) to see how script results are processed in various example cases.
+
+## Results Types
+
+- Single Value
+  :   Entire task output is stored in `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable.
+- Key/Value pairs
+  :   Expects `key=value,key=value` output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+- JSON
+  :   Expects `key:value,key:value` json formatted output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+
+IMPORTANT
+
+The entire output of a script is treated as results, not just the last line. Ensure formatting is correct for the appropriate result type. For example, if Results Type is `json` and the output is not fully json compatible, the result would not return properly.
+
+IMPORTANT
+
+Task results are not supported for Library Script task types
+
+## Script Config Examples
+
+Single Value using Task Code
+:   Source Task Config
+    :   - NAME: Var Code (single)
+        - CODE: singleExample
+        - RESULT TYPE: Single Value
+        - SCRIPT: `echo "string value"`
+
+    Source Task Output: `string value`
+
+    Results Task Config (using task code in variable)
+    :   - NAME: N/A
+        - CODE: N/A
+        - RESULT TYPE: N/A
+        - SCRIPT: `echo "single: <%=results.singleExample%>"`
+
+    Results Task Output: `single: string value`
+
+Single Value using Task Name
+:   Source Task Config
+    :   NAME
+        :   Var Code
+
+        CODE
+        :   none
+
+        RESULT TYPE
+        :   Single Value
+
+        SCRIPT
+        :   `echo "string value"`
+
+    Source Task Output
+    :   `string value`
+
+    Results Task using task name in variable
+    :   Results Task Script
+        :   `echo "task name: <%=results["Var Code"]%>"`
+
+        Results Task Output
+        :   `task name: test value`
+
+Key/Value Pairs
+:   Source Task Config
+    :   NAME
+        :   Var Code (keyval)
+
+        CODE
+        :   keyvalExample
+
+        RESULT TYPE
+        :   Key/Value pairs
+
+        SCRIPT
+        :   `echo "flash=bang,ping=pong"`
+
+    Source Task Output
+    :   `flash=bang,ping=pong`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "keyval: <%=results.keyvalExample%>"`
+
+        Results Task Output
+        :   `keyval: [flash:bang, ping:pong]`
+
+    Results Task for a single value)
+    :   Results Task Script
+        :   `echo "keyval value: <%=results.keyvalExample.flash%>"`
+
+        Results Task Output
+        :   `keyval value: bang`
+
+JSON
+:   Source Task Config
+    :   NAME
+        :   Var Code (json)
+
+        CODE
+        :   jsonExample
+
+        RESULT TYPE
+        :   JSON
+
+        SCRIPT
+        :   `echo "{\"ping\":\"pong\",\"flash\":\"bang\"}"`
+
+    Source Task Output
+    :   `{"ping":"pong","flash":"bang"}`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "json: <%=results.jsonExample%>"`
+
+        Results Task Output
+        :   `json: [ping:pong, flash:bang]`
+
+    Results Task for a single value
+    :   Results Task Script
+        :   `echo "json value: <%=results.jsonExample.ping%>"`
+
+        Results Task Output
+        :   `json value: pong`
+
+    Multiple Task Results
+    :   Results Task Script
+        :   ```
+            ```
+            echo "single: <%=results.singleExample%>"  
+            echo "task name: <%=results["Var Code"]%>"  
+            echo "keyval: <%=results.keyvalExample%>"  
+            echo "keyval value: <%=results.keyval.flash%>"  
+            echo "json: <%=results.jsonExample%>"  
+            echo "json value: <%=results.jsonExample.ping%>"
+            ```
+            ```
+
+        Results Task Output
+        :   ```
+            ```
+            single: string value  
+            task name: string value  
+            keyval: [flash:bang, ping:pong]  
+            keyval value: bang  
+            json: [ping:pong, flash:bang]  
+            json value: pong
+            ```
+            ```
+
+## Workflow Config
+
+Add one or multiple tasks with Results Type configured to a workflow, and the results will be available to all tasks in the same phase of the workflow via the `<%=results.variables%>` during the workflow execution.
+
+- Task Results are only available to tasks in the same workflow phase
+- Task Results are only available during workflow execution
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json b/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
new file mode 100644
index 0000000..817185b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+  "title": "Answer Files",
+  "ordinal": 251,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html",
+  "topic_cluster": {
+    "clustering_title": "Answer Files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md b/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
new file mode 100644
index 0000000..2ab924e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
@@ -0,0 +1,51 @@
+# Answer Files
+
+Answer files are like lists of answers for questions that you know the setup program is going to ask but the user is not prepared to answer. They contain one or more sections, and each section contains one or more properties in the form name=value. Morpheus provides Answer Files for ESXi, CentOS, Ubuntu and XenServer, and user can add their own.
+
+## Add Answer Files
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab then click the Add Answer File button.
+4. From the New Answer File Wizard input the following information 
+
+   Name
+   :   Name of the answer file.
+
+   Description(optional)
+   :   Description of the new answer file.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Script Name
+   :   Name of the new answer file.
+
+   Script Version
+   :   Version of the new answer file.
+
+   Script
+   :   The script for the new answer file.
+5. Save
+
+## Edit Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab
+4. Click the edit icon on the row of the answer file you wish to edit.
+5. Modify information as needed.
+6. Save Changes
+
+## Delete Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab.
+4. Click the delete icon on the row of the answer file you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json b/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
new file mode 100644
index 0000000..f16e3d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+  "title": "Overview",
+  "ordinal": 315,
+  "parent_title": "Policies",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md b/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
new file mode 100644
index 0000000..1a8b36e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
@@ -0,0 +1,3 @@
+# Overview
+
+Policies add governance, ease of use, cost-savings, and auditing features to HPE Morpheus Enterprise. HPE Morpheus Enterprise enables end users to create Policies scoped to Users, Roles, Groups, Clouds, Tenants, Networks, Plans, and Global scoping to give Admins full control and governance over their environments. The available scoping will vary from one Policy type to another. See the section below for information on each Policy type and guides for more complex Policy implementation.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json b/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
new file mode 100644
index 0000000..3a8435b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+  "title": "Costing",
+  "ordinal": 73,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html",
+  "topic_cluster": {
+    "clustering_title": "Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md b/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
new file mode 100644
index 0000000..c8f0b7b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
@@ -0,0 +1,7 @@
+# Costing
+
+**Subtopics**  
+
+- **[Budgets](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html)**
+- **[Invoices](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json b/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
new file mode 100644
index 0000000..59b6f4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+  "title": "Task Configuration",
+  "ordinal": 109,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html",
+  "topic_cluster": {
+    "clustering_title": "Task Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md b/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
new file mode 100644
index 0000000..62e1553
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
@@ -0,0 +1,322 @@
+# Task Configuration
+
+## Ansible Playbook
+
+![ansible](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FCAE649B-4E95-4F5B-A897-78C6A01F895D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ANSIBLE REPO:** Select existing Ansible Integration
+- **GIT REF:** Specify tag or branch (Option, blank assumes default)
+- **PLAYBOOK:** Name of playbook to execute, both `playbook` and `playbook.yml` format supported
+- **TAGS:** Enter comma separated tags to filter executed tasks by (ie `--tags`)
+- **SKIP TAGS:** Enter comma separated tags to run the playbook without matching tagged tasks (ie `--skip-tags`)
+
+IMPORTANT
+
+Using different Git Refs for multiple Ansible Tasks in same Workflow is not supported. Git Refs can vary between Workflows, but Tasks in each Workflow must use the same Git Ref.
+
+## Ansible Tower Job
+
+![ansibletower](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AF431C26-FA58-4140-8DAA-09CCA119F769-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TOWER INTEGRATION:** Select an existing Ansible Tower integration
+- **INVENTORY:** Select an existing Inventory, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Inventory
+- **GROUP:** Enter a group name, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Group if it exists. If it does not exist, HPE Morpheus Enterprise will create the Group
+- **JOB TEMPLATE:** Select an existing job template to associate with the Task
+- **SCM OVERRIDE:** If needed, specify an SCM branch other than that specified on the template
+- **EXECUTE MODE:** Select Limit to Instance (template is executed only on Instance provisioned), Limit to Group (template is executed on all hosts in the Group), Run for all (template is executed on all hosts in the Inventory), or Skip Execution (to skip execution of the template on the Instance provisioned)
+
+## Chef bootstrap
+
+![chef](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-531590A7-AFBE-40A7-BBBF-D4E7EB32974A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **CHEF SERVER:** Select existing Chef integration
+- **ENVIRONMENT:** Populate Chef environment, or leave as `_default`
+- **RUN LIST:** Enter Run List, eg `role[web]`
+- **DATA BAG KEY:** Enter data bag key (will be masked upon save)
+- **DATA BAG KEY PATH:** Enter data bag key path, eg `/etc/chef/databag_secret`
+- **NODE NAME:** Defaults to Instance name, configurable
+- **NODE ATTRIBUTES:** Specify attributes inside the `{}`
+
+## Conditional Workflow
+
+![../../_images/conditional.svg](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C6A92829-120A-43A5-AAFA-221E3A1C89EF-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **LABELS:** A comma separated list of Labels for organizational purposes. See elsewhere in HPE Morpheus Enterprise docs for additional details on utilizing Labels
+- **CONDITIONAL (JS):** JavaScript logic which determines the Operational Workflow which is ultimately run. If it resolves to `true`, the “If” Workflow is run and if it resolves to `false` the “Else” Workflow is run
+- **IF OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `true`
+- **ELSE OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `false`
+
+## Groovy script
+
+![groovy](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DA7C204B-DFAC-493A-A877-21B026F00D4D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the Groovy script if not sourcing it from a repository
+
+## Email
+
+![email](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9C895BAB-4D33-430F-8250-668229AB3E8A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **SOURCE:** Choose local to draft or paste the email directly into the Task. Choose Repository or URL to bring in a template from a Git repository or another outside source
+- **EMAIL ADDRESS:** Email addresses can be entered literally or HPE Morpheus Enterprise automation variables can be injected, such as `<%=instance.createdByEmail%>`
+- **SUBJECT:** The subject line of the email, HPE Morpheus Enterprise automation variables can be injected into the subject field
+- **CONTENT:** The body of the email is HTML. HPE Morpheus Enterprise automation variables can be injected into the email body when needed
+- **SKIP WRAPPED EMAIL TEMPLATE:** The HPE Morpheus Enterprise-styled email template is ignored and only HTML in the Content field is used
+
+TIP
+
+To whitelabel email sent from Tasks, select SKIP WRAPPED EMAIL TEMPLATE and use an HTML template with your own CSS styling
+
+## HTTP (API)
+
+![http](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3D6C1D43-48AE-4C22-AB38-7FF3748A8812-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **URL:** An HTTP or HTTPS URL as the HTTP Task target
+- **HTTP METHOD:** GET (default), POST, PUT, PATCH, HEAD, or DELETE
+- **AUTH USER:** Username for username/password authentication
+- **PASSWORD:** Password for username/password authentication
+- **BODY:** Request Body
+- **HTTP HEADERS:** Enter requests headers, examples below:
+
+|  |  |
+| --- | --- |
+| Authorization | Bearer token |
+| Content‐Type | application/json |
+
+- **IGNORE SSL ERRORS:** Mark when making REST calls to systems without a trusted SSL certificate
+
+## Javascript
+
+![javascript](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-20848F50-8905-4E2C-B84A-2964DB407179-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Javascript contents to execute
+
+## jRuby Script
+
+![jruby](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6DDC7639-A017-4555-A527-0F3DD5216833-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the jRuby script is entered here if it’s not being called in from an outside source
+
+## Library Script
+
+![libraryscript](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C1C0F695-54E0-43B9-90F3-A1112041085D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Search for an existing script in the typeahead field
+
+## Library Template
+
+![template](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-296B3993-FE5F-4AB8-B8AE-71D293861775-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TEMPLATE:** Search for an existing template in the typeahead field
+
+## Nested Workflow
+
+![../../_images/nestedworkflow.svg](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-949F99E1-949C-499A-980C-1AB5753BA11D-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **OPERATIONAL WORKFLOW:** The Workflow to be embedded as a Task for reference inside other Workflows
+
+## Powershell Script
+
+![powershell](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-69279397-D83C-4B50-9330-CA25F54BE9B0-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **VERSION:** Select the version of Powershell this Task should run in. Powershell 5 is the default selection, Powershell 6 or 7 must be installed on the target to select those versions
+- **ELEVATED SHELL:** Run script with administrator privileges
+- **IP ADDRESS:** IP address of the PowerShell Task target
+- **PORT:** SSH port for PowerShell Task target (5985 default)
+- **USERNAME:** Username for PowerShell Task target
+- **PASSWORD:** Password for PowerShell Task target
+- **Content:** Enter script to execute if not calling the script in from an outside source
+
+NOTE
+
+Setting the execution target to local requires Powershell to be installed on the HPE Morpheus Enterprise appliance box(es). [Microsoft Documentation](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.2) contains installation instructions for all major Linux distributions and versions.
+
+## Puppet Agent Install
+
+![puppet](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D625B993-30CE-4020-ACA7-B098CF811E3F-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **PUPPET MASTER:** Select Puppet Master from an existing Puppet integration
+- **PUPPET NODE NAME:** Enter Puppet node name. Variables supported eg. `<%= instance.name %>`
+- **PUPPET ENVIRONMENT:** Enter Puppet environment, eg. `production`
+
+## Python Script
+
+![python](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AB6EBB6F-6FB7-48D7-A2F6-EB4F4012B5A8-high.png)
+
+IMPORTANT
+
+Python Tasks use virtual environments. For this reason, `virtualenv` must be installed on your appliances in order to work with Python Tasks. See the information below for more detailed steps to install `virtualenv` on your HPE Morpheus Enterprise appliance node(s).
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Python script to execute is entered here if not pulled in from an outside repository
+- **COMMAND ARGUMENTS:** Optional arguments passed into the Python script. Variables supported eg. `<%= instance.name %>`
+- **ADDITIONAL PACKAGES:** Additional packages to be installed after `requirements.txt` (if detected). Expected format for additional packages: ‘packageName==x.x.x packageName2==x.x.x’, the version must be specified
+- **PYTHON BINARY:** Optional binary to override the default Python binary
+
+NOTE
+
+When troubleshooting errors in Python scripts using line numbers reported in HPE Morpheus Enterprise UI (such as in Task execution histories), you must subtract four line numbers to arrive at the correct line in the Python document. This is because HPE Morpheus Enterprise injects four lines at execution time to add HPE Morpheus Enterprise environment variables.
+
+**Enterprise Proxy Considerations**
+
+Additional considerations must be made in enterprise proxy environments where Python Tasks are run with additional package download requirements. These additional packages are downloaded using `pip` and may not obey global HPE Morpheus Enterprise proxy rules. To deal with this, create or edit the pip configuration file at `/etc/pip.conf`. Your configuration should include something like the following:
+
+```
+```
+[global]  
+proxy = http://some-proxy-ip.com:8087
+```
+```
+
+For more information, review the Pip documentation on using proxy servers [here](https://pip.pypa.io/en/stable/user_guide/#using-a-proxy-server).
+
+**CentOS 7 / Python 2.7 (RHEL system Python)**
+
+With a fresh install of HPE Morpheus Enterprise on a default build of CentOS 7, Python Tasks will not function due to the missing requirement of `virtualenv`.
+
+If you attempt to run a python task, you will get an error similar to the following:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-8ae51ebf-749c-4354-b6e4-11ce541afad5/bin/python: command not found
+```
+```
+
+In order to run HPE Morpheus Enterprise Python Tasks in CentOS 7, install `virtualenv`: `yum install python-virtualenv`
+
+If you require `python3`, you can specify the binary to be used while building the virtual environment. In a default install, do the following: `yum install python3`. Then, in your HPE Morpheus Enterprise Python Task, specify the binary in the PYTHON BINARY field as “/bin/python3”. This will build a virtual environment in `/tmp` using the `python3` binary, which is equivalent to making a virtual environment like so: `virtualenv ~/venv -p /bin/python3`.
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+**CentOS 8 and Python**
+
+In CentOS 8, Python is not installed by default. There is a `platform-python` but that should not be used for anything in userland. The error message with a default install of CentOS 8 will be similar to this:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-cffc9a8f-c40d-451d-956e-d6e9185ade33/bin/python: command not found
+```
+```
+
+The default `virtualenv` for CentOS 8 is the python3 variety, for HPE Morpheus Enterprise to use Python Tasks, do the following: `yum install python3-virtualenv`
+
+If Python2 is required, do the following: `yum install python2` and specify `/bin/python2` as the PYTHON BINARY in your HPE Morpheus Enterprise Task.
+
+This will build a `virtualenv` in `/tmp` using the `python2` binary, which is equivalent to making a `virtualenv` like so: `virtualenv ~/venv -p /bin/python2`
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+## Restart
+
+![restart](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12DFE21D-BC68-4969-B496-340CA3E40690-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+
+## Shell Script
+
+![shellscript](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-66BC263C-CF8F-4199-B05B-99D786BF9288-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SUDO:** Mark the box to run the script as `sudo`
+- **CONTENT:** Script to execute is entered here if not pulled in from an outside repository
+
+TIP
+
+When the EXECUTE TARGET option is set to “Local” (in other words, the Task is run on the appliance itself), two additional fields are revealed: GIT REPO and GIT REF. Use GIT REPO to set the PWD shell variable (identifies the current working directory) to the locally cached repository (ex. /var/opt/morpheus-node/morpheus-local/repo/git/76fecffdf1fe96516e90becdab9de) and GIT REF to identify the Git branch the Task should be run from if the default (typically main or master) shouldn’t be used. If these options are not set, the working folder will be /opt/morpheus/lib/tomcat/temp which would not allow scripts to reference file paths relative to the repository (if needed).
+
+## vRealize Orchestrator Workflow
+
+![vro](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ABE75AA7-6B9F-46FE-9A67-D463924B577D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **vRO INTEGRATION:** Select an existing vRO integration
+- **WORKFLOW:** Select a vRO workflow from the list synced from the selected integration
+- **PARAMETER BODY (JSON):**
+
+## Write Attributes
+
+![wa](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C48074E2-3DB2-4459-98D0-AC5282256582-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ATTRIBUTES:** A JSON map of arbitrary values to write to the attributes property of the target resource
+
+TIP
+
+This is often useful for storing values from one phase of a Provisioning Workflow for access in another phase. See the video demo below for a complete example.
+
+There are a number of ways that a JSON payload can be statically drafted within a Write Attributes Task or called into the Task as a result from a prior Task. Consider the following examples:
+
+To pass in a static JSON map with static values, use the format shown below.
+
+```
+```
+{  
+  "my_key1": "my_value1",  
+  "my_key2": "my_value2"  
+}
+```
+```
+
+To pass in a static JSON map with dynamic values seeded from prior Task results, ensure the RESULT TYPE value of one or more of the prior Tasks in the Workflow phase is set to “Single Value” and refer to the values within the JSON map as shown in the next example. Note that “taskCode1” and “taskCode2” refer to the CODE field value for the Task whose output you wish to reference.
+
+```
+```
+{  
+  "my_key1": "<%=results.taskCode1%>",  
+  "my_key2": "<%=results.taskCode2%>"  
+}
+```
+```
+
+To pass in a dynamic JSON map returned from a prior Task, format your Write Attributes Task as shown in the next example. Ensure that the RESULT TYPE value for the Task returning a JSON map is set to “JSON”. Note that “taskCode” in the example refers to the CODE field value for the Task being referenced. In order for the JSON map to be set correctly and able to be referenced from future Tasks, you must set the “instances” key and call the `encodeAsJSON()` Groovy method as shown in the example.
+
+```
+```
+{  
+  "instances": <%=results.taskCode?.encodeAsJSON()%>  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json b/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
new file mode 100644
index 0000000..c977db8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+  "title": "Containers",
+  "ordinal": 212,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md b/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
new file mode 100644
index 0000000..e69c877
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
@@ -0,0 +1,9 @@
+# Containers
+
+![../../_images/infra_compute_header_containers_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ECD57864-C48E-460D-A2E1-5B01CC0F8610-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Container Type Cloud
+
+The containers tab lists all Containers associated with HPE Morpheus Enterprise Instances accessible to the user. Note additional system level containers from Kubernetes and Docker Clusters are not listed here but are accessible in Cluster detail sections.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json b/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
new file mode 100644
index 0000000..b2768a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+  "title": "Plugins",
+  "ordinal": 312,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md b/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
new file mode 100644
index 0000000..ccc0256
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
@@ -0,0 +1,23 @@
+# Plugins
+
+## Overview
+
+HPE Morpheus Enterprise is extendable with custom plugins for Task types, UI tabs, reports, approvals, cypher, and more. Plugins are added from the Plugins tab of the Integration page under Administration (Administration > Integrations > Plugins). Simply browse for a local plugin file (.jar) to add it to the UI. Custom plugins can also be edited or deleted by clicking on the pencil or trash can icons in the corresponding row.
+
+HPE Morpheus Enterprise maintains a repository of internally-developed and vetted plugins at HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/). These plugins can be downloaded and added to HPE Morpheus Enterprise using the instructions in the prior paragraph. Alongside the download link, you can also find helpful readme information that discusses how the plugin can be used and which versions of HPE Morpheus Enterprise it’s compatible with.
+
+With at least one plugin integrated, HPE Morpheus Enterprise will show details on each plugin from the Plugins List View. The following information is displayed:
+
+- **NAME:** The name given to the plugin
+- **DESCRIPTION:** A description value (if any) coded into the plugin
+- **FILE NAME:** The .jar filename
+- **VERSION:** The plugin version number
+- **STATUS:** The status of the plugin, such as “loaded” when the plugin is ready for use
+- **STATUS MESSAGE:** A status message (if any) for the plugin
+- **ENABLED:** If the plugin is enabled, a check mark appears here. Disabled plugins are also grayed out
+
+Additional information about each plugin can be viewed by clicking on the pencil (edit) icon. Most of the information in this modal is read-only but you can enable or disable plugins from this pane.
+
+Please visit the [Morpheus Developer Portal](https://developer.morpheusdata.com) for Plugin Architecture SDK documentation and help getting started with custom Plugin development.
+
+![../../_images/plugins_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E806E13E-76E4-477E-BE44-5A16FC97B809-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json b/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
new file mode 100644
index 0000000..343a7fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+  "title": "Troubleshooting",
+  "ordinal": 344,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md b/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
new file mode 100644
index 0000000..8185892
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
@@ -0,0 +1,20 @@
+# Troubleshooting
+
+- [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+**Subtopics**  
+
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7_2.html)**
+- **[Ansible Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html)**
+- **[Attaching Logs to Case](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html)**
+- **[CLI Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html)**
+- **[Cannot Login](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html)**
+- **[How to un-manage an Instance/VM/Host](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html)**
+- **[MySQL Too many connections error](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html)**
+- **[HPE Morpheus Enterprise Agent Install Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html)**
+- **[HPE Morpheus Enterprise UI not loading after upgrade or reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html)**
+- **[Remote Console](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html)**
+- **[SSL Self-signed Certificate Regeneration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html)**
+- **[Unable to Delete Tenant](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html)**
+- **[Unable to Provision a Custom Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json b/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
new file mode 100644
index 0000000..d6ccaf9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+  "title": "Options",
+  "ordinal": 152,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html",
+  "topic_cluster": {
+    "clustering_title": "Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md b/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
new file mode 100644
index 0000000..5816a40
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
@@ -0,0 +1,11 @@
+# Options
+
+Options are user-defined custom inputs that are used throughout HPE Morpheus Enterprise. Depending on the type of Input being created, users may need to create only an Input, or it might need to be paired with an Option List. Option Lists are static or dynamic lists of selections that would be associated with an Input if the user must make choices from a select list or typeahead field. This section discusses how to create different types of Inputs depending on the situation and powerful tools the user can take advantage of, such as dynamically filtered cascading inputs, logically generated Option Lists called from local or remote sources, and more.
+
+**Subtopics**  
+
+- **[Forms](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html)**
+- **[Inputs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html)**
+- **[Option Lists](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html)**
+- **[LDAP Query Variables](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html)**
+- **[Creating an Option List Based on an LDAP Query](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json b/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
new file mode 100644
index 0000000..584b9f1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 451,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md b/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
new file mode 100644
index 0000000..b110063
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
@@ -0,0 +1,6 @@
+# Firmware and Driver Lifecycle Management
+
+| S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Morpheus / iLO fails to initialize the server after the SPP update | Server provisioning fails with errors similar to:  - `Base.1.18.ResourceMissingAtURI` - `Drives/64515 not found` - `HTTP null` - Storage object lists drive URIs that cannot be resolved | 1. Verify storage drive URIs:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Systems/1/Storage/<controller> | jq    ```    ``` 2. Validate drive URI exists:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Chassis/<chassis>/Drives/<id> | jq    ```    ``` 3. Confirm SPP was applied recently | Morpheus / iLO logs | Typically caused by stale Redfish drive references after SPP. |
+| 2 | After SPP, Redfish drive tree mismatch | Storage object shows drive count and IDs, but drive URIs return ResourceMissingAtURI | Perform a **Full Cold Power Cycle** (not reboot):   1. Power OFF the server (OS or iLO) 2. Remove both power cables 3. Wait 60 seconds 4. Reconnect power cables 5. Power ON the server | iLO event log, Smart Array logs | Required for Gen11/Gen12 after firmware updates. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json b/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
new file mode 100644
index 0000000..65528c1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+  "title": "Automation Integrations",
+  "ordinal": 531,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md b/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
new file mode 100644
index 0000000..432a272
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
@@ -0,0 +1,14 @@
+# Automation Integrations
+
+- Ansible
+- Ansible Tower
+- Chef
+- Puppet
+
+NOTE
+
+Automation integrations can be added and managed in Administration > Integrations as well. Adding and editing Integrations in Library > Integrationsand Administration > Integrations are the same dataset and additions and updates are reflected in both sections.
+
+NOTE
+
+Role access for `Integrations: Ansible` determines user access to Ansible Integration detail page, which contains Ansible command line and execution access.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json b/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
new file mode 100644
index 0000000..022a1c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+  "title": "Add Load Balancer to Instance",
+  "ordinal": 496,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer to Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md b/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
new file mode 100644
index 0000000..ff258f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
@@ -0,0 +1,11 @@
+# Add Load Balancer to Instance
+
+Load Balancers can be added to Instances during Provisioning or to existing Instances. For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+NOTE
+
+For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+**Subtopics**  
+
+- **[Add Load Balancer during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json b/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
new file mode 100644
index 0000000..73366b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+  "title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+  "ordinal": 352,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md b/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
new file mode 100644
index 0000000..ad768c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
@@ -0,0 +1,172 @@
+# HPE Morpheus Enterprise Agent Install Troubleshooting
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+### For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+### SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+### VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+### Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+### Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+### Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+### Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
+
+## Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+### Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+### Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
+
+## Uninstall HPE Morpheus Enterprise Agent
+
+### Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+### Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
+
+## CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json b/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
new file mode 100644
index 0000000..67a1eff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+  "title": "HPE Morpheus Enterprise Blueprints",
+  "ordinal": 136,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md b/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
new file mode 100644
index 0000000..7b1dd23
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
@@ -0,0 +1,191 @@
+# HPE Morpheus Enterprise Blueprints
+
+HPE Morpheus Enterprise App Blueprints allow pre-configured full multi-tier application deployments for multiple environments. Blueprints can be provisioned from the Provisioning > Apps section and can be fully configured for one click provisioning. Blueprints can be built within the `Builder` section or by code in the `Raw` section. Blueprints can also be exported as YAML or JSON and created with the HPE Morpheus Enterprise API and CLI.
+
+A unique capability of the YAML/JSON based Morpheus blueprint structure is the ability to have multiple configurations per instance being provisioned within the app blueprint. This can be a scoped configuration that acts as overrides based on selected cloud, group, and/or environment the app is being provisioned in as a target. For example. maybe the “development” environment doesn’t need as many horizontally scaled nodes as the “production” environment. Another great aspect of this configuration markup is a blueprint can be defined as a hybrid cloud blueprint. This makes the app blueprint structure very powerful and in some ways better than alternative infrastructure as code orchestrators. For Example, ARM is locked into Azure, while CloudFormation is locked into AWS. Even Terraform does not allow a tf file to expand its bounds beyond a specific provider type.
+
+## Basic Blueprint Structure
+
+In a Morpheus App Blueprint there are a few structural concepts to be aware of. Firstly there is a concept of a Tier. A Tier is a grouping of instances within an app blueprint. Tiers can be used for a variety of things including sequenced booting of instances or even properly creating endpoint groups and security group contexts in network security tools like Cisco ACI. An example of a Tier structure might be a `Web` tier and a `Database` tier. These tiers can also be marked as connected such that network communication rules can appropriately be defined. A basic 2 Tier blueprint skeleton might look something like this:
+
+```
+```
+name: Tier Example  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers:  
+      - Database  
+    tier:  
+      bootOrder: 1  
+    instances:  
+  Database:  
+    tier:  
+      bootOrder: 0  
+    instances:
+```
+```
+
+This example has defined 2 tiers as yaml properties under the tiers object. They are called Web and Database. A Tier can optionally define its connected tiers which are bi-directional even though only one tier has to define them. This is the linkedTiers array and simply lists the connected tiers by tier name. A Boot Order can also optionally be defined under a nested `{"tier": {"bootOrder": 1}}` object structure.
+
+## Configuration Scopes
+
+Another capability of Morpheus App Blueprint structure is its configuration scoping. This allows properties to be overridden based on the apps target environment or even target group and cloud. For example. Maybe we want to use a larger plan size in production vs. development
+
+An example of that can be done using “environments” overrides.
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              code: container-128  
+         environments:  
+           Production:  
+             groups:  
+               All Clouds Demo:  
+                 clouds:  
+                   AWS Cali:  
+                     plan:  
+                       code: container-256
+```
+```
+
+Note the new environments object. The object graph of the morpheus blueprint structure gets merged and flattened at provision time based on the scope of the configurations provided as well as the users target cloud, group, and environment selection. In the Above example, a selective override was done for the AWS Cali cloud when using a Production Environment and deploying to the group All Clouds Demo. This specific example changes the plan to a larger size. Scoped configurations have various levels of precedence. Cloud is the lowest level of precedence. a cloud configuration in a group is the next level higher and finally an environment configuration in a group in a cloud is the highest level of scoped precedence.
+
+## Getting Started
+
+To get started, it may be best to look at a simple App Blueprint configuration. Docker templates are less complex than virtual machine based templates so lets look at a Blueprint that deploys a single Nginx container to a target cloud:
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers: []  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+                id: 206  
+            volumes:  
+              - rootVolume: true  
+                name: root  
+                size: 1  
+            backup:  
+              createBackup: false  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              id: 68  
+              code: container-128  
+            ports:  
+              - name: HTTP  
+                port: 80  
+                lb: HTTP
+```
+```
+
+Theres some useful things to look at in the above docker example. One is there are different objects based on the different available configuration options for the target provision type. These options are actually data driven and can be extracted from the Inputs api in the morpheus api doc. That is a useful resource to look at while building morpheus blueprints or by using the morpheus-cli which provides prompts for helping build custom morpheus app blueprints.
+
+![../../../_images/templates_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-06C21D16-B31C-492D-9170-EAC44622138F-high.png)
+
+## Creating Morpheus App Blueprints
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Enter a NAME for the Blueprint and select NEXT
+4. Optionally add a Description, Category, and Image for the Blueprint.
+
+### Add Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + to add a Tier
+2. Select or enter a Tier Name.
+3. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+
+### Add Instances to Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in a Tier to add an Instance
+2. Select an Instance Type
+3. Optionally add a name for the Instance. Instances with blank names will automatically be named based off the App name.
+
+#### Results
+
+TIP
+
+You can use the variable `${app.name}` in your instance naming convention to reference the name of the application you’re deploying.
+
+### Add Configurations to Instances
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in an Instance to add a Configuration
+2. Select at least one option from Group, Cloud or Environment.
+3. Select `ADD CONFIG` to create the configuration
+4. Populate the Configuration 
+
+   - Configurations can be fully partially or populated
+   - Fields can be locked or hidden by selecting the Lock icon next to the Field. Locking prevents the field from being editable when provisioning an App using the Blueprint while hidden fields are not revealed to the user at all
+   - ALLOW EXISTING INSTANCE will allow users to add existing Instances to the App when using the blueprint
+
+### Save
+
+Once all desired Tiers, Instances and Configurations are added, select Save. The Blueprint will be created, can be edited after saving, and will available in the Apps section for provisioning.
+
+NOTE
+
+Blueprints are not provisioned when created. To provision a Blueprint, use Provisioning > Apps.
+
+### RAW
+
+#### About this task
+
+Blueprints can be create, edited or Exported in the RAW section when creating or editing a blueprint.
+
+![../../../_images/templates_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2F7949E9-D5DB-4089-970D-854F88DA140D-high.png)
+
+To Export a Blueprint as JSON or YAML:
+
+#### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Edit an existing App by clicking on the pencil icon
+3. On the Edit Blueprint modal, select the Raw tab
+4. Select YAML or JSON from the dropdown in the top right
+5. Click the Export button
+6. Select the configurations to include in the export by selecting or deselecting configurations as needed. Selected configurations will be highlighted
+7. Click the DOWNLOAD CONFIGURATION button
+8. The Blueprint export file will be downloaded to your computer as `{app_name}-config.json or {app_name}-config.yaml`
+
+## Provisioning
+
+To provision a Blueprint, navigate to Provisioning > Apps and select the Blueprint when creating an App. See the [App section](https://docs.morpheusdata.com/en/latest/provisioning/apps/apps.html) of HPE Morpheus Enterprise docs for more on provisioning Apps.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
new file mode 100644
index 0000000..2aeccb2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+  "title": "Costing: User Costing",
+  "ordinal": 61,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: User Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
new file mode 100644
index 0000000..dc8c05f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
@@ -0,0 +1,31 @@
+# Costing: User Costing
+
+![../_images/4usercosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-19673F2B-9D42-4067-BC83-078B0046D28B-high.png)
+
+The User Costing dashboard allows administrators to analyze costs for a group of Users that meet specific filters. Once the group is selected, total costs by User for the current month and projected totals are displayed. Administrators can identify their costliest Users and anticipate the total cost by User for budgeting purposes.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- User (all matched by search)
+- Group
+- Cloud
+- Period (Current month, last three months, last six months, or last 12 months)
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Users that meet set filters:
+
+- **USERS:** The total number of Users that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Users meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Users meeting dashboard filters
+
+## User List
+
+Each User that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual User:
+
+- **USERNAME:** The username given to the User in HPE Morpheus Enterprise at the time of creation
+- **MONTH TO DATE:** The current month-to-date spend for the individual User listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual User listed
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json b/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
new file mode 100644
index 0000000..7d4f294
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+  "title": "Docker Registry",
+  "ordinal": 478,
+  "parent_title": "Containers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Registry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md b/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
new file mode 100644
index 0000000..6acbe73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
@@ -0,0 +1,39 @@
+# Docker Registry
+
+## Overview
+
+Without any additional configuration, HPE Morpheus Enterprise can provision images from Docker’s public hub at <https://hub.docker.com/> using their public API.
+
+However, many organizations maintain private Docker registries for security measures. Additional public and private Docker registries can be added to Morpheus.
+
+## Adding a Docker Registry Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click “New Integration”
+3. Select the Docker Repository Type
+4. Add the following: 
+
+   Name
+   :   Name for the Registry in HPE Morpheus Enterprise
+
+   Repository url
+   :   Docker Registry url or IP address
+
+   Username
+   :   Username if private registry
+
+   Password
+   :   Password if private registry
+5. Save Changes
+
+### Results
+
+NOTE
+
+You must either have signed certificates for your registry or configure your docker host(s) to accept insecure registries
+
+## Provisioning an Instance from Docker Registry
+
+Docker images from the Integrated Registry can be provisioned using the generic Docker Instance Type, or by adding images to Node Types for custom Library Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json b/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
new file mode 100644
index 0000000..891639e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+  "title": "Tenant Users",
+  "ordinal": 277,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md b/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
new file mode 100644
index 0000000..6a0b90d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
@@ -0,0 +1,86 @@
+# Tenant Users
+
+The Tenant View displays a list of users belonging to the Tenant and their Name, Username, Email, and Role.
+
+From this page: Create, Edit, and Delete users within the Tenant.
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Create Tenant User
+
+### About this task
+
+To create a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name on the row of the Tenant where the user will be added.
+4. Click + ADD USER
+5. From the New User wizard, input the fields below: 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email address
+   - Role (to be inherited by the user)
+   - Password
+   - Any default Windows or Linux credentials
+
+### Results
+
+Click SAVE CHANGES
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Edit a Tenant User
+
+### About this task
+
+To edit a User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the specific Tenant name from the row of available Tenants.
+4. Click the Edit pencil icon for your selected Tenant.
+5. Edit User information 
+
+   NOTE
+
+   Name, Username, Passwords and e-mail addresses cannot be edited on Users created from Identity Source Integrations.
+
+### Results
+
+Click SAVE CHANGES
+
+## Delete Tenant User
+
+### About this task
+
+To delete a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name from the row for the Tenant containing the user.
+4. Click the Delete trashcan icon of the row of the user to delete.
+5. Confirm
+
+## Subtenant User Login
+
+Child Tenant Users can have the same Username as the User on the parent Tenant or any other Tenant. Subtenant Users will now have to login using the subdomain prefix.
+
+IMPORTANT
+
+Subtenant users will no longer be able to login from the main login page without specifying their subdomain.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json b/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
new file mode 100644
index 0000000..aac3039
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+  "title": "Persona Access",
+  "ordinal": 342,
+  "parent_title": "Personas",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html",
+  "topic_cluster": {
+    "clustering_title": "Persona Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md b/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
new file mode 100644
index 0000000..11f5238
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
@@ -0,0 +1,30 @@
+# Persona Access
+
+## Configuring Persona Access
+
+### About this task
+
+Access to Personas is controlled by a user’s Role. Additionally, Persona access can be configured on the Tenant Role to set maximum Persona access for any user in the Tenant. By default, new Roles and Roles that existed prior to the creation of Personas will only have access to the Standard Persona. If desired, new Roles can be configured to have access to one or both Personas and existing Roles can be edited in the same way.
+
+TIP
+
+It’s recommended to set access to all Personas to “None” if you intend not to use Personas at all. Under this configuration, HPE Morpheus Enterprise gives access only to the Standard Persona and hides the Persona selection menu from the user. New Roles and Roles that existed prior to creation of the Personas feature are pre-configured in this way.
+
+Edit Persona access on a Role with the following steps:
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Select the desired Role to edit
+3. Go to the Personas tab
+4. Allow access to one or both Personas as needed, changes are saved automatically
+
+### Results
+
+![../_images/1rolePerms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B7E6E923-4BC1-45EC-8A41-9862C023911F-high.png)
+
+## Accessing Alternate Personas
+
+Switch Personas by clicking on your name in the upper-right corner of the application window. If your Role gives you access to any additional Personas, they will be listed here.
+
+![../_images/2switchPersona2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-79453DE4-A795-4FEB-9670-0F214A7163FF-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json b/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
new file mode 100644
index 0000000..3ca9cd5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+  "title": "Troubleshooting",
+  "ordinal": 248,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md b/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
new file mode 100644
index 0000000..dcadadf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
@@ -0,0 +1,9 @@
+# Troubleshooting
+
+If you do not get the Morpheus boot menu, there are a few things to check:
+
+- First, make sure the filename is correct. It must be `pxelinux.0`
+- Next, check the TFTP server is responding by using a TFTP client to get the `pxelinux.0` file from the HPE Morpheus Enterprise server using the same host name as you have configured in the DHCP server configuration. Do this test on a machine on the same network as the machines you are trying to boot using PXE
+- Leave the port number as 69 (the default) as this will also check the redirect is working
+- If a GET call on the default port does not work, and the client allows (most do) try using port 6969. If this works, then the redirect is wrong
+- If it will not work on either, check you can access the HPE Morpheus Enterprise server from the network you are on and also check there are no firewalls between the test network and the HPE Morpheus Enterprise Server
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json b/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
new file mode 100644
index 0000000..b37d468
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+  "title": "Logs",
+  "ordinal": 255,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md b/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
new file mode 100644
index 0000000..108a442
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
@@ -0,0 +1,176 @@
+# Logs
+
+## Overview
+
+The logging architecture backing HPE Morpheus Enterprise uses the latest and greatest technologies and standards to be able to service large amounts of log traffic as well as facilitate easy viewing. Utilizing Opensearch behind the scenes and buffered log transmission protocols HPE Morpheus Enterprise provides a highly efficient and highly scalable solution for capturing log data from anything provisioned via the system. By utilizing common formats (syslog) it is also very easy to forward logs to external third party log services.
+
+### Configuration
+
+Logging configuration can be setup in the Administration > Settings > Logs section. There are useful settings here, including customizing the retainment policy (7 days by default). This could be expanded to years for PCI compliance purposes or other requirements an organization might have.
+
+NOTE
+
+When increasing the retainment policy of the logging system, it may be necessary to scale out the Opensearch cluster. Please refer to the relevant information with regards to scaling Opensearch and advanced installation options for externalizing the Opensearch cluster.
+
+The Log administration section also provides options for setting custom syslog forward rules. These rules are applied on each individual host therefore keeping the HPE Morpheus Enterprise appliance itself out of the data plane. For information on different syslog formatting rules please refer to the [rsyslog](http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/) documentation.
+
+### Usage
+
+HPE Morpheus Enterprise automatically sets up and configures logging for all of the standard catalog items provisioned through morpheus. This includes both Docker containers as well as virtual machines. Simply view instance-specific logs in instance detail via the “Logs” tab.
+
+There are several filtering capabilities built into the logging UI with more being added continually. Easily toggle log level filters from the dropdown or change the date range filter using the handy date filter component. A chart is also displayed above logs representing the log counts by level over the selected time range (default last 24 hours). A handy pattern search is also available with some rather capable features based on Lucene search syntax.
+
+TIP
+
+It may be useful to review the [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html) for powerful use cases.
+
+There are several other places logs can be viewed. Not only can they be viewed across an application in app detail but also across all instances in the account. The main level `Logs` section provides an ability to query all logs produced by the system. It is also possible to view host-specific logs on a docker host by viewing the host detail page via `Infrastructure`.
+
+NOTE
+
+New features are on the roadmap for the main logs section including saved searches, and handy charting dashboards for garnering insights out of log data.
+
+## Exporting Logs
+
+### Log Settings
+
+There are three main log areas in HPE Morpheus Enterprise
+
+- Agent Logs
+- HPE Morpheus Enterprise Server Logs
+- Activity / Audit Logs
+
+## Agent Logs
+
+When Instances are deployed through HPE Morpheus Enterprise, the installed Agent captures application logs and sends them back to the HPE Morpheus Enterprise server.
+
+In most cases, the built-in HPE Morpheus Enterprise logging features are sufficient for tracking and reviewing Agent logs. However, if needed, HPE Morpheus Enterprise supports integration with advanced logging systems. See the [log integration section](https://docs.morpheusdata.com/en/latest/logs/logging.html#integrations) above for more information.
+
+## HPE Morpheus Enterprise Server Logs
+
+### About this task
+
+The main HPE Morpheus Enterprise application log is in `/var/log/morpheus/morpheus-ui` and the latest log file is named current. This log is archived every 24hrs. There are a number of other log files for the individual infrastructure components as well.
+
+If you wish to export these to an external syslog platform, do the following:
+
+### Procedure
+
+1. Once you have configured your syslog destination (edit rsyslog.conf), create a morpheus-syslog.conf file in the `/etc/rsyslog.d` directory and add the following entries 
+
+   ```
+   ```
+   module(load="imfile" PollingInterval="10")  
+   input(type="imfile" File="/var/log/morpheus/morpheus-ui/current" Tag="morpheus-ui" ReadMode="2" Severity="info" StateFile="morpheus-ui")  
+   input(type="imfile" File="/var/log/morpheus/check-server/current" Tag="check-server" ReadMode="2" Severity="info" StateFile="check-server")  
+   input(type="imfile" File="/var/log/morpheus/guacd/current" Tag="guacd" ReadMode="2" Severity="info" StateFile="guacd")  
+   input(type="imfile" File="/var/log/morpheus/opensearch/current" Tag="opensearch" ReadMode="2" Severity="info" StateFile="opensearch")  
+   input(type="imfile" File="/var/log/morpheus/mysql/current" Tag="mysql" ReadMode="2" Severity="info" StateFile="mysql")  
+   input(type="imfile" File="/var/log/morpheus/nginx/current" Tag="nginx" ReadMode="2" Severity="info" StateFile="nginx")  
+   input(type="imfile" File="/var/log/morpheus/rabbitmq/current" Tag="rabbitmq" ReadMode="2" Severity="info" StateFile="rabbitmq")
+   ```
+   ```
+2. Restart rsyslog
+
+### Results
+
+The log files will now be forwarded to the destination you have defined.
+
+This configuration is valid for an ‘all-in-one’ HPE Morpheus Enterprise server. If the infrastructure components are running on separate servers /clusters, you will need to create the relevant redirects for the logs on those boxes.
+
+## Activity Log
+
+### About this task
+
+The final log type that may require export is the HPE Morpheus Enterprise Activity log. This tracks system changes made by users, for example create and delete instances etc.
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, you should edit the following file: `logback.xml` located at `/opt/morpheus/conf/logback.xml`.
+2. Add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+3. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+4. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+5. Once the service has stopped enter the following at the shell prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+6. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
+
+## morpheus-ssl nginx logs
+
+NOTE
+
+Morpheus does not put a logrotate in for Morpheus-ssl access logs
+
+svlogd will only rotate the current file, nginx is setup to write the access logs to separate files and not stdout.
+
+Implementation of a log rotate is left up to up to end users for files outside of the services. This is done in case end users have a log management solution.
+
+Below is what a suggested configuration looks like for the file `/etc/logrotate.d/morpheus-nginx`:
+
+```
+```
+/var/log/morpheus/nginx/morpheus*access.log {  
+        daily  
+        rotate 14  
+        compress  
+        delaycompress  
+        missingok  
+        notifempty  
+        create 644 morpheus-app morpheus-app  
+        postrotate  
+                [ ! -f /var/run/morpheus/nginx/nginx.pid ] || kill -USR1 `cat /var/run/morpheus/nginx/nginx.pid`  
+        endscript  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json b/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
new file mode 100644
index 0000000..8c70075
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+  "title": "Getting started with Morpheus and AWS",
+  "ordinal": 360,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with Morpheus and AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md b/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
new file mode 100644
index 0000000..a04b02f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
@@ -0,0 +1,212 @@
+# Getting started with Morpheus and AWS
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with AWS. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get Morpheus installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, Morpheus needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, Morpheus will automatically set up a lab license on installation. A lab license is a time-unlimited license for Morpheus that limits you to 25 managed and discovered workloads. If you have a timed trial or a paid license, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in Morpheus define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on Morpheus groups is available in the [Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html#GUID-E0307462-456B-4D4E-82E3-0BD04A42F824) section. A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling Morpheus through Morpheus API or Morpheus CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![../../_images/1groupConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in Morpheus consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with AWS.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of Morpheus but soon we will see our integrated AWS cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AMAZON” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, give your cloud a “NAME”. Select your Amazon region and enter your credentials in the “ACCESS KEY” and “SECRET KEY” fields. We can also set a number of advanced options here that may be relevant to your AWS use case.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, Morpheus will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first AWS cloud, we can stop for a moment to review what Morpheus gives us from the cloud detail page. We can see that Morpheus gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our AWS cloud configured, Morpheus will automatically sync in available resource pools and data stores.
+
+Resource pools, once Morpheus has had time to ingest them, will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in Amazon. For example, we can restrict access to a specific resource pool within Morpheus completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within Morpheus.
+
+![../../_images/1resourcePools.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5EDE80B8-04C2-42AD-95C9-11EA1E8E8331-high.png)
+
+Often our clients will want to make specific blocks of resources available to certain groups. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![../../_images/2editResourceGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3D217ABE-3194-420B-A2D6-DD5262F136EC-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into Morpheus. Depending on the number of clouds Morpheus has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![../../_images/1networksSection.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html) section of Morpheus Docs.
+
+![../../_images/2addIPAM.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![../../_images/3addIPPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within the AWS cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  NETWORKS tab. Just as with resource pools, we have the ability to make certain networks inactive in Morpheus, or scope them to be usable only for certain groups or tenants.
+
+![../../_images/1cloudNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1A883CF2-9673-460A-B1AC-A1CB858CD226-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, Morpheus comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with the images included in Morpheus by default but have guides in Morpheus Docs for [Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html#GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798) which are consumable in Morpheus.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our AWS cloud.
+
+Navigate to |ProIns|. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/1createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the AWS cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, Morpheus will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+- **SECURITY GROUPS**
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of Morpheus docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends selections made when provisioning the instance. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, Morpheus allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click +ADD.
+
+![../../_images/1addNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: Amazon
+- **AMI IMAGE**: Morpheus Redis 3.0 on Ubuntu 14.04.3 v2
+
+![../../_images/2nodeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B58E92CB-BAAC-4B7B-A743-4E04B13DC487-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![../../_images/3addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![../../_images/4instanceTypeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![../../_images/5openInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: Amazon
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to |ProIns| and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+As before when we manually provisioned an instance, Morpheus will now begin to spin up the new VM. Once the privisioning process has completed, open the instance detail page in Morpheus and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+## Automation and Configuration Management
+
+Morpheus automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the Morpheus Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in [Automation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html). Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![../../_images/1newIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+ NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![../../_images/2configureIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![../../_images/3taskConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![../../_images/4executeTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![../../_images/5newWorkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![../../_images/6automationInProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see Morpheus executing the tasks that were contained in our workflow.
+
+This is just one example of using Morpheus to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) guide in Morpheus docs.
+
+## Conclusion
+
+At this point you should be up and running in Morpheus, ready to consume AWS. This guide only scratches the surface, there is a lot more to see and do in Morpheus. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json b/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
new file mode 100644
index 0000000..02c4a11
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+  "title": "Morpheus DB Migration",
+  "ordinal": 26,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus DB Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md b/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
new file mode 100644
index 0000000..2d8f77c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
@@ -0,0 +1,80 @@
+# Morpheus DB Migration
+
+If your new installation is part of a migration or you need to move the data from your original Morpheus database, this is easily accomplished by using a stateful dump.
+
+To begin this, stop the Morpheus UI on your original Morpheus server:
+
+```
+```
+[root@app-server-old ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Once this is done you can safely export. To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file:
+
+```
+```
+[root@app-server-old ~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---------------this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Take note of the first `morpheus_password` as it will be used to invoke a dump. Morpheus provides embedded binaries for this task. Invoke it via the embedded path and specify the host. In this example we are using the morpheus database on the MySQL listening on localhost. Enter the password copied from the previous step when prompted:
+
+```
+```
+[root@app-server-old ~] /opt/morpheus/embedded/mysql/bin/mysqldump -u morpheus -h 127.0.0.1 morpheus -p > /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+This file needs to be pushed to the new Morpheus Installation’s backend. Depending on the GRANTS in the new MySQL backend, this will likely require moving this file to one of the new Morpheus frontend servers.
+
+Once the file is in place it can be imported into the backend. Begin by ensuring the Morpheus UI service is stopped on all of the application servers:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Then you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server-new ~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The data from the old appliance is now replicated on the new appliance. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl start morpheus-ui
+```
+```
+
+With the migration complete, you will also need to update the stored password for the appliance backup job as the destination appliance will have a different dynamically-generated MySQL password. We can update that password value by altering the backup directly in the HPE Morpheus Enterprise database.
+
+```
+```
+select * from backup where `name` ='Morpheus Appliance';  
+UPDATE `morpheus`.`backup` SET `ssh_host` = '127.0.0.1', `target_password` = 'its-a-secret' WHERE `id` = '1';
+```
+```
+
+IMPORTANT
+
+After the migration it is important to reset the unique ID of the Morpheus Appliance. This will ensure your new installation will communicate correctly with the Morpheus Hub.
+
+The final step is to generate a new unique ID for the Morpheus Appliance. Firstly run the following SQL command on the database for the new installation:
+
+```
+```
+UPDATE appliance_instance SET hub_unique_id = NULL;
+```
+```
+
+Secondly, re-apply your Morpheus license key within the Morpheus UI via the “Upgrade A License” action within Administration -> Settings -> License
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json b/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
new file mode 100644
index 0000000..80fe9d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 190,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md b/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
new file mode 100644
index 0000000..1bf317e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
@@ -0,0 +1,13 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HPE Morpheus Enterprise HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the HVM cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give HPE Morpheus Enterprise access to NFS.
+
+Start by navigating to the Storage tab of the HVM cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in HPE Morpheus Enterprise and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in HPE Morpheus Enterprise. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
+
+![../../_images/addNfsDatastore.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-90F23A24-CA56-4100-94CD-13EA1247EBD5-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json b/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
new file mode 100644
index 0000000..a28377c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+  "title": "Post-Provisioning",
+  "ordinal": 417,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html",
+  "topic_cluster": {
+    "clustering_title": "Post-Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md b/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
new file mode 100644
index 0000000..ebf5251
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
@@ -0,0 +1,20 @@
+# Post-Provisioning
+
+After provisioning the instance:
+
+- The new instance appears under Provisioning > Instances.
+
+    
+  ![Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EB7CC689-A95F-43C0-8F65-D43E35C97D7B-high.png)
+- To monitor provisioning progress, select the instance from the list.   
+  ![Summary](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AA864681-E71F-4DAA-BC8C-9594A4F366CC-high.png)
+
+  Once provisioning completes successfully, review the tabs as required.
+- To access the instance console, click the Console tab
+- After successful provisioning, verify that the instance and its corresponding bare metal host are listed in:
+  - Under Provisioning > Instances.  
+    ![Provisioning Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-49E0E201-4ED4-41C1-A8F4-D31630076D56-high.png)
+  - Under Infrastructure > Bare Metal.   
+    ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1647C09E-6E21-4A92-A088-1AC8E3A64B52-high.png)
+  - Go to the Instances page to view the instance Status, Health, CPU, Memory, and Storage details.   
+    ![Details](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-55629E53-1010-42C1-BE7F-DCF13B743BBE-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json b/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
new file mode 100644
index 0000000..f17ccda
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+  "title": "Base Cluster Details",
+  "ordinal": 178,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md b/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
new file mode 100644
index 0000000..b96c467
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the HVM cluster solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, a host must be a pre-existing Ubuntu 22.04 box with environment and host system requirements contained in this section. HPE Morpheus Enterprise handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to HPE Morpheus Enterprise are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json b/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
new file mode 100644
index 0000000..e88da4b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+  "title": "Usage",
+  "ordinal": 76,
+  "parent_title": "Costing",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md b/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
new file mode 100644
index 0000000..448d41f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
@@ -0,0 +1,35 @@
+# Usage
+
+The Operations  >  Costing  >  Usage section shows billing information for Instances and hosts that have pricing configured on their Service Plan.
+
+IMPORTANT
+
+Pricing must be enabled in Administration > Settings > Provisioning and Service Plans configured with price sets in Administration > Plans & Pricing for pricing to show in the Usage section.
+
+## View Usage
+
+All Instances, discovered resources, virtual images, snapshots are listed by default, with the most recent usage information showing first. When additional details are available, usage records will display a small arrow on the left side of the row. Click this arrow to expand the details for that usage record. Details can include more granular cost breakdowns, such as specific CPU, memory, and/or storage costs for containers (Instances).
+
+Usage records can be filtered by Cloud, type and date:
+
+Cloud
+:   Default view is for all Clouds. Select a Cloud to show Instance, host and other usage for only one Cloud.
+
+Date
+:   Default view shows most current Usage. Select the Date filter to scope to a different date range.
+
+Type
+:   All usage record types are shown by default, select a specific type to filter the list to just one
+
+Example:
+:   Below is an example of a discovered instance from AWS, which shows different usage periods and the pricing that would be related. In this case, the compute and storage are used to calculate the Usage Price when the instance is **Running** but only the storage when the instance is **Stopped**:
+
+    ![../_images/usage_example.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E455650E-5DD7-40E6-BF40-5449281F27C2-high.png)
+
+## API & CLI
+
+Usage information can also be extracted via the HPE Morpheus Enterprise API and CLI, including the ability to extract usage per Tenant.
+
+NOTE
+
+Appropriate Role permissions for Operations: Usage are required to view the Usage section.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json b/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
new file mode 100644
index 0000000..5a9f577
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+  "title": "Morpheus Agent",
+  "ordinal": 42,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md b/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
new file mode 100644
index 0000000..c2b8200
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
@@ -0,0 +1,17 @@
+# Morpheus Agent
+
+- [Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)
+- [Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)
+- [Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)
+- [CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html)**
+- **[HPE Morpheus Enterprise Agent Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html)**
+- **[Morpheus Agent OS Support](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html)**
+- **[Agent Installation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html)**
+- **[Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)**
+- **[Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)**
+- **[Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)**
+- **[CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json b/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
new file mode 100644
index 0000000..87bf337
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+  "title": "Personas",
+  "ordinal": 339,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html",
+  "topic_cluster": {
+    "clustering_title": "Personas",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md b/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
new file mode 100644
index 0000000..0dac526
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
@@ -0,0 +1,11 @@
+# Personas
+
+Personas are alternate views in HPE Morpheus Enterprise UI. A user’s access to the various Personas is controlled by Role permissions. At present, there are four Persona types: Standard, API, Service Catalog, and Virtual Desktop. The Standard Persona is the typical full HPE Morpheus Enterprise UI experience. The Service Catalog Persona is a simplified view where users are presented with pre-configured Instance types, Blueprints, and Workflows to choose from based on their Role. The Virtual Desktop Persona allows administrators to grant user access to remote workstations and applications. The API persona allows almost no access to HPE Morpheus Enterprise UI, it offers API access only for service accounts.
+
+The rest of this section goes through the use of the Service Catalog Persona and Virtual Desktop Persona in greater detail, including how administrators can curate catalog item and virtual desktop selections for their users.
+
+**Subtopics**  
+
+- **[Service Catalog Persona](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html)**
+- **[Virtual Desktop Persona](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html)**
+- **[Persona Access](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..30a78bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 221,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..dfd4c5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,116 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+## Overview
+
+The Domains section is for creating and managing domains for use in HPE Morpheus Enterprise. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
+
+## Adding Domains
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in HPE Morpheus Enterprise
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across HPE Morpheus Enterprise. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. HPE Morpheus Enterprise will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+### Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
+
+## Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group and Tenant access permissions.
+
+NOTE
+
+Only resources assigned to the Master Tenant can be set as Publicly visible. If the Tenant assigned is not the Master Tenant, visibility will automatically change to private. Additionally, only Master Tenant users can set visibility for domains. Domains originating in a subtenant will always be private to that subtenant.
+
+### Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
+
+### Tenant Permissions
+
+When set to public, all Tenants will have visibility into the domain and can join their Instances to the domain. When set to private, users can select specific Tenants which should have access to the domain.
+
+## Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from HPE Morpheus Enterprise by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
+
+## Setting the default domain on a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Setting the default domain on a Network
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Selecting a Domain while provisioning an instance
+
+### Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..09e042a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 192,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..22cab75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json b/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
new file mode 100644
index 0000000..853bee8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+  "title": "Compute",
+  "ordinal": 449,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md b/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
new file mode 100644
index 0000000..30ec9a7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
@@ -0,0 +1,8 @@
+# Compute
+
+The topic describes troubleshooting procedures for compute.
+
+**Subtopics**  
+
+- **[OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json b/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
new file mode 100644
index 0000000..e368a20
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+  "title": "Add HaProxy container load balancer",
+  "ordinal": 500,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html",
+  "topic_cluster": {
+    "clustering_title": "Add HaProxy container load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md b/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
new file mode 100644
index 0000000..f3e0cc5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
@@ -0,0 +1,33 @@
+# Add HaProxy container load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **HaProxy Container**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Container LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-56213FAB-222F-45BB-A5DD-748546C526A1-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   RESOURCE POOL
+   :   From the drop-down list, select the resource pool.
+
+   HOST
+   :   From the drop-down list, select the host.
+
+   PLAN
+   :   From the drop-down list, select the plan (size of HaProxy container to be provisioned).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json b/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
new file mode 100644
index 0000000..6459881
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+  "title": "Tenancy",
+  "ordinal": 372,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html",
+  "topic_cluster": {
+    "clustering_title": "Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md b/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
new file mode 100644
index 0000000..f7cb036
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
@@ -0,0 +1,268 @@
+# Tenancy
+
+HPE Morpheus Enterprise appliances may be multi-tenanted, that is, they may contain multiple isolated environments known as Tenants. Successfully building a multi-Tenanted HPE Morpheus Enterprise environment requires creating and pulling together multiple constructs. This guide aims to describe the pieces needed to create functioning Tenants with Users, identity integrations, Roles, Groups, and whitelabeling. We will also share a Cloud and Library item from the Master Tenant which is provisionable from the new Subtenant.
+
+On installation, a single Tenant is created. This Tenant is often referred to as the Master Tenant and has some special properties that additional created Tenants (known as Subtenants) do not have. Tenants manage their own workloads, may have their own custom whitelabeling, and also have their own users and integrations. The Master Tenant may (or may not) share down integrations, Library items, Roles, and more but Subtenants are fully isolated from each other.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The Master Tenant creates and controls all Subtenants.
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants
+- Subtenants cannot share their resources with other Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant
+
+## Tenant Roles
+
+### About this task
+
+Before even creating the Tenant, we need to understand what a Tenant Role is and ensure that a Tenant Role with correct rights permissions exists. Tenant Roles set the maximum feature permissions levels for any User in the Subtenant and also give (or revoke) access to Clouds, Library items, Tasks, Workflows, and other things integrated or created in and shared from the Master Tenant. Only Master Tenant administrators have the ability to create Tenant Roles.
+
+NOTE
+
+User Roles within the Tenant may be created with lesser permissions than the Tenant Role allows but we will discuss User Roles further in a later section.
+
+In a new environment, the only Tenant Role will be the included “Tenant Admin” Role but this Role is not editable. It’s advisable to create your own Tenant Roles so they may be edited as needed. To get started, we can create a new Tenant Role and copy from the pre-existing “Tenant Admin” Role.
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Click + CREATE ROLE
+3. Set a NAME, TYPE (Tenant Role), and COPY FROM ROLE (Tenant Admin)
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/addTenantRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9D86F36B-590B-424C-A1E6-13B6779D961F-high.png)
+
+Once created, click into the new Role and edit feature permissions if you wish. Remember the Tenant Role is setting the maximum available Role permissions for each feature that Users within the Tenant can have. We’ll worry about scoping resources to the Subtenant (such as Clouds) in a later section.
+
+With a Tenant Role created, we can move on to creating the Tenant itself.
+
+## Create a Tenant
+
+### About this task
+
+We’ll now create a Tenant and apply the Tenant Role we’ve just created.
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Click CREATE TENANT
+3. Name your Tenant and set the Tenant Role in the BASE ROLE field
+4. Click SAVE CHANGES
+
+### Results
+
+The NAME and BASE ROLE are the most important settings and the only two required. See the Tenants section of HPE Morpheus Enterprise documentation to learn more about other settings which may be applied when adding or editing Tenants.
+
+![../../_images/addTenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-702D1FEA-8C54-4BBA-AEC7-7C1575EC9D28-high.png)
+
+With the Tenant created, the rest of the guide will pertain to configuring the new Tenant and demonstrating how to provision new workloads using resources shared down from the Master Tenant.
+
+## Users and User Roles
+
+### About this task
+
+In the prior steps we’ve created a new Tenant and associated our created Tenant Role with it. If you click into the new Tenant you’ll notice that there are currently no users so the new Tenant is still unusable. We could go ahead and create a new User but if this is a new HPE Morpheus Enterprise environment, the new Tenant will not have any User Roles to apply to the new User we wish to create.
+
+To remedy this problem, we can add a “Multi-Tenant User Role” from the Master Tenant. This is essentially a Role Template from which a Role is created and seeded down to each Tenant. Only Master Tenant administrators can create Multi-Tenant User Roles. After creation, edits can be made and permission changes will be filtered down to the child Role that exists within each Subtenant. However, it’s important to know that should the child Role ever be edited in the Subtenant, the link back to the Multi-Tenant User Role will be broken and it will become like any other User Role created in the Subtenant. To prevent this situation, Master Tenant administrators can set a “MULTITENANT LOCKED” option to restrict such edits in the Subtenant.
+
+New Multi-Tenant User Roles are created in Administration > Roles:
+
+### Procedure
+
+1. Click + CREATE ROLE
+2. Provide a NAME, TYPE (User Role), COPY FROM ROLE (if desired)
+3. Mark the boxes to set MULTITENANT ROLE and MULTITENANT LOCKED
+4. Click SAVE CHANGES
+
+### Results
+
+After saving the Role, it will appear in the Master Tenant and will also be seeded down to the Tenant we’ve already created since it is a Multi-Tenant User Role. We’ve also locked the Role so that Subtenant users cannot edit it and thus unlink it from future permissions edits made in the Master Tenant. Keep in mind that no matter what permissions we set, Users in the Subtenant will not be able to exceed permissions set on the Tenant Role as discussed in a prior section. If desired, you can click into this User Role now and edit its permissions to suit your needs.
+
+![../../_images/addUserRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-870C9D97-516B-4D34-8339-550FCB2EA699-high.png)
+
+At this point we’re ready to add a User which will make the Tenant usable. We can create one in the new Tenant by navigating to the Tenant list page (Administration > Tenants) and selecting the Tenant. There are a number of configurations to make when creating a user but when selecting the User’s Role you should see the previously-created Multi-Tenant User Role.
+
+![../../_images/addUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E03CE619-CA56-4601-95F4-61D3F0A0EE7B-high.png)
+
+After saving the new User, we can make the first test of the new Tenant by impersonating the User and entering the Tenant. In the list of Users on the Tenant detail page, click the gear (⚙) icon at the end of the User’s row and select “Impersonate.” You should end up inside the new Tenant operating as the new user. This can be confirmed by making note of the updated name given in the upper-right portion of the application window. To quit impersonating, click on the name and select “Quit Impersonating.”
+
+At this point we’ve created a User manually but it’s important to point out that HPE Morpheus Enterprise can also use an existing identity integration, such as Microsoft Active Directory, to manage User creation and Role assignment. Expand the section below to see an example use case or continue on if you’d prefer to administer your Users directly in HPE Morpheus Enterprise. The complete integration guide elsewhere in HPE Morpheus Enterprise docs also includes common Active Directory troubleshooting steps should those be needed.
+
+Microsoft Active Directory Example
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in‐built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following:
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES.
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Whitelabeling
+
+HPE Morpheus Enterprise allows each Tenant to be customized with its own look and feel through whitelabeling features. Your organization can replace the stock HPE Morpheus Enterprise logo and color scheme with your own logos and colors. Whitelabel settings are held in Administration > Settings > Whitelabel and are mostly self-explanatory. Upload logos and set custom hexadecimal colors in each field. When done, be sure to set the “Enable Whitelabel” configuration and click SAVE all the way at the bottom of the page. If needed, review a more detailed explanation of each [whitelabel setting](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#whitelabel) in HPE Morpheus Enterprise documentation.
+
+![../../_images/whitelabelSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-458BDDBC-723A-4A05-9745-372AC60C08DD-high.png)
+
+## Scoping Clouds to Tenants
+
+### About this task
+
+With the Tenant now created and seeded with a User and Roles, we’re ready to look at how to set up useful provisioning resources. Of course, Tenants are complete (yet isolated) HPE Morpheus Enterprise environments which can create their own Cloud integrations or utilize integrations with other third party technologies (assuming they haven’t been restricted from doing so by the Tenant Role). However, Master Tenant administrators may also choose to share integrations created in the Master Tenant down to Subtenant users.
+
+Many constructs in HPE Morpheus Enterprise have a “Visibility” attribute when viewed from the Master Tenant. This attribute controls whether the construct is “Private” (in other words reserved for a selected Tenant) or Public (available to all Tenants). In our example, we’re going to expose an Amazon AWS Cloud integrated in the Master Tenant down to our newly-created Subtenant. To set the Cloud visibility, use the following steps:
+
+### Procedure
+
+1. Navigate to the Clouds list page (Infrastructure > Clouds)
+2. Edit the Cloud by clicking the pencil icon (✎) in its row
+3. Toggle the VISIBILITY attribute to “Public”
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/editCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BED65BE1-AF4D-4EC6-9680-03FADB9422C3-high.png)
+
+The Cloud is now exposed to the Subtenant but we also need to expose a Resource Pool (A VPC, in Amazon parlance) for Subtenant users to provision into. We do this from the Cloud detail page (Infrastructure > Clouds) > Click on selected Cloud.
+
+1. Select the Resources subtab
+2. Click ACTIONS next to the selected Resource Pool (VPC)
+3. Click Edit
+4. Expand the “Tenant Permissions” section
+5. Set Visibility to Public (alternatively, you could keep the Private visibility and add the new Tenant in the next field)
+6. Click SAVE CHANGES
+
+![../../_images/addResourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7E26EBB1-E238-4E5A-9BE2-ACEB243DDDE0-high.png)
+
+Repeat the same process for Networks and Security Groups, both of which are contained in the Networks subtab of the Cloud detail page.
+
+## Groups
+
+### About this task
+
+The last thing to take a look at before Library items and provisioning are Groups. Groups define which resources a User can access. Group access is defined by the User Role and many resources have a Group access component which allows administrators to control User access to things like Clouds, Networks, Datastores, Resource Pools, Folders and more.
+
+Groups exist solely within the Tenant that creates them, they cannot be shared down from Master Tenant to Subtenants. In order to create a Group for our new Tenant, impersonate the User we’ve created in previous steps. Once working in the Tenant, use the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Groups
+2. Click + CREATE
+3. Set a NAME for the Group and click SAVE CHANGES
+
+### Results
+
+We’ll now add the shared Cloud to the Group:
+
+1. Click on the name of the Group to access the Group detail page
+2. Click on the Clouds tab
+3. Click + ADD
+4. Use the typeahead field to select the shared Cloud
+5. Click SAVE CHANGES
+
+![../../_images/addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DA5D5406-4991-4E35-B064-4B94E55FE9C3-high.png)
+
+At this point the basic configuration steps are complete and we will attempt a provisioning test using built-in Instance Types which are preinstalled with HPE Morpheus Enterprise.
+
+## Provisioning Test
+
+### About this task
+
+At this point, you can conduct a test by attempting to provision one of the basic Instance Types shipped with HPE Morpheus Enterprise for demonstration purposes. To test, we’ll provision a basic Ubuntu box to our AWS Cloud.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Ubuntu Instance Type
+4. Click NEXT
+5. Select the Group and Cloud noting that only resources shared with the Subtenant are selectable
+6. Name the Instance
+7. Click NEXT
+8. On the CONFIGURE tab, select a Resource Pool, Network, and Security Group once again noting that only resources shared with the Subtenant are selectable
+9. Click NEXT
+10. Click NEXT once again
+11. Click COMPLETE
+
+### Results
+
+![../../_images/createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-96B45365-D416-4CFC-9A46-6ADCC0455916-high.png)
+
+After a minute or two, the Instance should be fully provisioned.
+
+## Exposing Custom Instance Types to Subtenants
+
+Master Tenant administrators can also share custom Library items down to Subtenants. Do do this, navigate to Library > Blueprints and select an Instance Type. Click the pencil (✎) icon in the row for the selected Instance Type to edit it. As we’ve done before, update the VISIBILITY setting to Public. In addition, ensure the User Role for the Subtenant User grants access to the selected Instance Type. Once configurations have been made, conduct a similar test to the previous section. When you attempt to provision a new Instance, the new Instance Type should be selectable and the User should be able to provision the custom Instance Type in the same was as the default Instance Type was provisioned in the previous step.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json b/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
new file mode 100644
index 0000000..d10ef5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+  "title": "Virtual Desktop Persona",
+  "ordinal": 341,
+  "parent_title": "Personas",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Desktop Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md b/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
new file mode 100644
index 0000000..b966448
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
@@ -0,0 +1,64 @@
+# Virtual Desktop Persona
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json b/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
new file mode 100644
index 0000000..31ce5f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+  "title": "Invoices",
+  "ordinal": 75,
+  "parent_title": "Costing",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html",
+  "topic_cluster": {
+    "clustering_title": "Invoices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md b/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
new file mode 100644
index 0000000..a7dae77
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
@@ -0,0 +1,135 @@
+# Invoices
+
+HPE Morpheus Enterprise offers highly-granular costing data through invoices. Invoice views are highly customizable, allowing for nearly unlimited combinations of output columns and filtering. Invoices are based on monthly periods and allow you to slice costs in a highly granular way, as well as predict final monthly costs before the end of the period. As with other HPE Morpheus Enterprise UI pages that support advanced table customization, these views can be saved to provide easy access to costing views specific to varying business needs. By default, the invoice list page will show the last three months’ invoices across all clouds and invoice types but the list can be modified to target differing time periods or resource groupings. Read on in this section to discover the meaning of various invoice types and how this tool can be used to create targeted costing views.
+
+## Invoices for Public vs On-Prem Clouds
+
+HPE Morpheus Enterprise supports live cost syncing for many public clouds, including all of the most commonly-used public clouds like Amazon AWS, Microsoft Azure, and Google Cloud Platform. For these clouds, costing sync is enabled through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). When live costs are synced from public clouds, invoices will be generated for this activity including month-to-date costs, projected monthly totals, historical cost data, and a lot more which is discussed in the following sections.
+
+Additionally, HPE Morpheus Enterprise has implemented a costing service for on-prem clouds to closely mirror the live costing experience through a public cloud. As with public clouds, this costing service is enabled for on-prem clouds through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). Change the setting to “Sync Costing” and save the changes to the cloud integration. From this point, costs will be aggregated into invoices for on-prem clouds in the same way as public clouds including complete line item listings, current costs for the month, month-end projections, and much more as discussed in the next sections.
+
+## Invoice List Page
+
+The invoices list page shows high-level aggregate data on a group of invoices and allows you to locate a specific invoice for a deeper look. By default, invoices from the last three months across all clouds and types are shown here. Depending on settings, this page can automatically refresh itself so the list of displayed invoices and the aggregate information on them is up to date.
+
+![../_images/1listInvoices.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7D08D7CC-C9FD-4013-9B64-78A4F9C8B639-high.png)
+
+### Aggregated Invoice Data
+
+The following aggregate totals are displayed for all invoices picked up by set filters:
+
+- **Periods:** The total number of months in the period determined by your start and end date filters. If no start and end dates are set, a three month period will be shown. If a one-month period is selected, the name of that month (ex. Aug 2020) is shown
+- **Total Invoices:** The total number of invoices captured by current filters
+- **MTD Cost:** The combined month-to-date cost for all invoices captured by current filters
+- **Total Cost:** The expected total month-end cost for all invoices captured by current filters
+
+## Creating Views
+
+### About this task
+
+Invoice list views are highly-customizable allowing for virtually limitless combinations of output columns and filtering. A common set of output columns is provided in a default view but users can add and remove columns from a large list of data points and even save multiple views for easy access to different data sets. Any of your stored views can be set as the default to be displayed each time the invoices list page is active.
+
+To create a new invoices view:
+
+### Procedure
+
+1. Click the gear icon (⚙)
+2. Click on one or more columns from the “Columns” list to add or remove an output field
+3. Click “+ add view”
+4. Provide a name and a description value for your new view
+5. If desired, mark the box to set the new view as your default view so it appears automatically each time the invoices list page is accessed
+6. Click SAVE
+
+### Results
+
+![../_images/2createViews.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E081EF68-3B0E-4A5A-8CFE-8E8B47D87BAD-high.png)
+
+### Available Output Columns
+
+When creating an invoices view, there are many output columns available to select. Consult the list below for more details on each of the available columns:
+
+#### Available Output Columns: Expand for Complete List
+
+- **Invoice ID:** The unique ID in HPE Morpheus Enterprise for the invoice
+- **Type:** The invoice type; Cloud, Container, Group, Server, Instance, Resource, User, or Volume
+- **Ref ID:** An ID for the reference object tied to the invoice (server, instance, cloud, etc.). Reference IDs are reused across invoice types so invoices referring to identical Ref IDs may not necessarily refer to the same reference object
+- **Reference:** The name of the reference object (server, cloud, user, group, etc.) tied to the invoice
+- **Cloud ID:** The internal ID for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Cloud:** The name for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Instance ID:** The internal ID for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Instance:** The name for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Server ID:** The internal ID for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Server:** The name for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Cluster ID:** The internal ID for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Cluster:** The name for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Plan ID:** The internal ID for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Plan:** The name for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Group ID:** The internal ID for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **Group:** The name for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **User ID:** The internal ID for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **User:** The name for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **Tenant ID:** The internal ID for the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Tenant:** The name of the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Period:** The monthly period during which the invoice was generated
+- **Interval:** The length of the invoice billing period, currently all invoices are generated at a one-month interval
+- **Start Date:** The start date and time for the invoice period, typically the first of the month at midnight
+- **End Date:** The end date and time for the invoice period, typically the last day of the month at midnight
+- **Ref Start:** The date and time the reference object is created or the start of the invoicing period if the reference object existed prior to the start of the invoicing period
+- **Ref End:** The date and time the reference object is decommissioned or the end of the invoicing period if the reference object still existed at the end of the period
+- **Compute Cost:** The actual compute costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Cost:** The actual storage costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Cost:** The actual network costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Cost:** The actual additional costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Cost:** The actual month-to-date costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Cost:** The actual total costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Cost:** Compute costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Cost:** Storage costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Cost:** Network costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Cost:** Additional costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Cost:** Month-to-date costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Cost:** Total costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Compute Price:** The actual compute price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Price:** The actual storage price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Price::** The actual network price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Price:** The actual additional price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Price:** The actual month-to-date price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Price:** The actual total price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Price:** Compute price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Price:** Storage price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Price:** Network price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Price:** Additional price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Price:** Month-to-date price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Price:** Total price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Active:** Indicates whether or not the reference object is currently existing and active
+- **Date Created:** The date and time the invoice is created
+
+## Invoice Types
+
+Invoices can reference any of the HPE Morpheus Enterprise workload element types or resource reference types in the list below. Some invoice types are broader and may account for resource costs calculated in other narrower invoice types. For instance, a container-type invoice returns costs for a single node of an Instance while an Instance-type invoice for the same period may be including costs for that same single node. The invoices list view can be filtered to show just one type or all types. Complete descriptions of each invoice type are included below:
+
+- Cloud: In HPE Morpheus Enterprise, a Cloud is any connection into a public cloud, private cloud, hybrid cloud, or bare metal server
+- Container: A single node of a service, in other words, a single node of a HPE Morpheus Enterprise Instance. This could be a virtual machine or Docker container which is part of a HPE Morpheus Enterprise-managed Instance
+- Group: In HPE Morpheus Enterprise, Groups define which resources a user has access to through their role. Clouds are added to Groups and users access Clouds to which their roles give access
+- Server: A server refers to any individual host, virtual machine, or bare metal server that is inventoried or managed by HPE Morpheus Enterprise. This can include servers which are parts of HPE Morpheus Enterprise-managed Instances or inventoried servers from integrated Clouds
+- Instance: A set of containers or virtual machines which correlate to a single horizontally-scalable entity. This could be a single VM or it could be many VMs operating as a service
+- Resource: Resource-type invoices are generated when HPE Morpheus Enterprise cannot determine that the referenced costs belong to any of the other resource reference types in this list
+- User: User-type invoices aggregate the costs of resources owned by a specific HPE Morpheus Enterprise user during the invoicing period
+- Volume: When possible, costs will be tied to known volumes and a volume-type invoice is generated as a result
+
+## Invoice Detail Page
+
+### Summary
+
+The summary tab of the invoice detail page displays a great deal of reference information about the resource identified by the invoice. This will vary depending on the type of resource. In addition, total and projected costs are displayed along with cost breakdowns for compute, storage, network, and other categories. Month-to-date totals and final month projections are given.
+
+### History
+
+The history tab displays the costs and prices for the associated resource over time. This tab is especially valuable for resources that have existed through at least a few invoicing periods to show changes over time. In addition, cost breakdowns for compute, storage, network, and other categories are shown for each invoicing period. These costs can be displayed visually through graphs.
+
+![../_images/4invoiceHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-66262EA5-76D1-41C6-AE62-C1CF505E9976-high.png)
+
+### Line Items
+
+For supported resource types, HPE Morpheus Enterprise includes a tab to display all costing line items. This provides the user with a complete list of line items that make up the costing totals on the invoice.
+
+![../_images/5invoiceLineItem.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-035126CA-FDE7-492E-842A-094558CB1655-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json b/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
new file mode 100644
index 0000000..a0689f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+  "title": "Overview",
+  "ordinal": 246,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md b/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
new file mode 100644
index 0000000..d710e5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise provides a simple-to-use Bare Metal boot capability based on PXE. When a server boots and is redirected to the HPE Morpheus Enterprise server for the installation files, they can be configured to be simply passed an OS or Hypervisor (in which case HPE Morpheus Enterprise will see them as Bare Metal servers with no further detail) or they can be brought on as Virtual Machines or Docker Hosts. Installation of the HPE Morpheus Enterprise Agent can also be done during the initial configuration stage.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json b/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
new file mode 100644
index 0000000..f93a713
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+  "title": "VMware Fusion",
+  "ordinal": 475,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-98351F93-76B4-480B-91F1-58E3E3492651.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Fusion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md b/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
new file mode 100644
index 0000000..e3aba07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
@@ -0,0 +1,152 @@
+# VMware Fusion
+
+## Add a VMware Fusion Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select VMware Fusion, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   VMWARE FUSION HOST
+   :   IP or URL of VMware Fusion Host
+
+   WORKING PATH
+   :   Existing folder HPE Morpheus Enterprise will write to on Host
+
+   USERNAME
+   :   Host Username
+
+   PASSWORD
+   :   Host Password
+
+   BRIDGE NAME
+   :   Will auto-populate upon successful authentication with the Fusion Host (E.X. ‘EN0: ETHERNET’)
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.json b/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.json
new file mode 100644
index 0000000..21ee7d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+  "title": "Restarting the HPE Morpheus Enterprise Agent",
+  "ordinal": 48,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9B75C475-9243-4444-BF22-C43480298274.html",
+  "topic_cluster": {
+    "clustering_title": "Restarting the HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.md b/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.md
new file mode 100644
index 0000000..73b4ff6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9B75C475-9243-4444-BF22-C43480298274.md
@@ -0,0 +1,15 @@
+# Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+## Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+## Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json b/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
new file mode 100644
index 0000000..9a3d6e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+  "title": "Requirements",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md b/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
new file mode 100644
index 0000000..4a575ed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
@@ -0,0 +1,17 @@
+# Requirements
+
+HPE Morpheus Enterprise Software is a software-based appliance installation capable of orchestrating many clouds and hypervisors. Before an installation is started it is important to understand some of the base requirements.
+
+In the simplest configuration HPE Morpheus Enterprise needs one Appliance Server. The Appliance Server, by default, contains all the components necessary to orchestrate both VMs and containers. To get started some base requirements are recommended:
+
+**Subtopics**  
+
+- **[Base Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)**
+- **[Storage Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html)**
+- **[Network Connectivity](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html)**
+- **[Components](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html)**
+- **[SELinux](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html)**
+- **[OpenSearch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html)**
+- **[Supported Locales](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json b/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
new file mode 100644
index 0000000..e9e15c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+  "title": "Upgrades & Maintenance",
+  "ordinal": 19,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrades & Maintenance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md b/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
new file mode 100644
index 0000000..9f09ed5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
@@ -0,0 +1,9 @@
+# Upgrades & Maintenance
+
+**Subtopics**  
+
+- **[Upgrading](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html)**
+- **[morpheus-ctl tips](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html)**
+- **[Morpheus DB Migration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html)**
+- **[Scaling Morpheus Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html)**
+- **[Morpheus UI war files](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..a600d99
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 329,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..c93c1e5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,38 @@
+# License
+
+## Overview
+
+HPE Morpheus Enterprise requires a valid license for provisioning new Instances, Apps and Hosts, and converting existing Instances and Hosts to managed. Licenses can be applied and updated in this section, and the current license status can be checked.
+
+NOTE
+
+HPE Morpheus Enterprise is licensed for a certain number of concurrent workload elements (WLEs) that may be managed or inventoried at any one time. See our [Knowledge Base](https://support.morpheusdata.com/s/article/What-is-a-Workload-Element-or-WE-for-purposes-of-Morpheus-licensing?language=en_US) for specific information on the types of WLEs that count against HPE Morpheus Enterprise licensing.
+
+## Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
+
+## Upgrade License Key
+
+### About this task
+
+To add a new or update an existing License:
+
+### Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+### Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
+
+## Request new License
+
+To request a new license, use the [My HPE Software Center](https://myenterpriselicense.hpe.com) or contact your account manager.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json b/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
new file mode 100644
index 0000000..3258363
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+  "title": "vRealize Orchestrator",
+  "ordinal": 380,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html",
+  "topic_cluster": {
+    "clustering_title": "vRealize Orchestrator",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md b/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
new file mode 100644
index 0000000..a7681fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
@@ -0,0 +1,185 @@
+# vRealize Orchestrator
+
+The vRealize Orchestrator (vRO) Integration provided for HPE Morpheus Enterprise enables users to easily trigger existing workflows that may already exist in vRealize Orchestrator. Not only can the user trigger these workflows, but they can also be chained easily into non-vRO workflows and process both output and input parameters of a workflow.
+
+## Adding the Integration
+
+Setting up the vRO integration involves some steps which vary depending on the authentication model being used.
+
+NAME
+:   Name of the integration
+
+API URL
+:   Typically, the API URL is run on port 8283. A sample API URL may look like the following example: `https://vrahost.com:8283/`
+
+AUTH TYPE
+:   Chosen based on the authentication provider configured on vRO
+
+CREDENTIALS
+:   Choose `Local Credentials` to enter credentials for this integration or choose to create/use an existing credentials
+
+USERNAME
+:   Username that will be configured on the integration that can authenticate with vRO
+
+PASSWORD
+:   Password that will be configured on the integration for the username that can authentication with vRO
+
+Tenant Token
+:   The domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`
+
+    NOTE
+
+    At times, this can vary depending on how authentication and role assignments for the user have been set up for vRO.
+
+CLIENT ID
+:   The ID used and obtained from the vRO server, typically used when using `OAuth 2.0` Auth Type
+
+### Basic Auth Type
+
+The `Basic` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `vSphere` Authentication Provider. When vRO is configured with this provider, users login to vRO using their vSphere/vCenter credentials, which HPE Morpheus Enterprise will use the same.
+
+NOTE
+
+The `CLIENT ID` field can contain any value. It will be unused with the `Basic` Auth Type
+
+Example of a configured `vSphere` Authentication Provider from the vRO Control Center:
+
+![../../_images/vsphere_auth_provider.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A89B217A-D71D-497C-9346-6E62C493B2B7-high.png)
+
+Example of a configured `Basic` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/basic_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4B3F0F89-D9C0-49D3-B0CE-52017F8F3ADE-high.png)
+
+### OAuth 2.0 Auth Type
+
+The `OAuth 2.0` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `VIDM` option or other OAuth provider.
+
+When using `OAuth 2.0`, the Client ID must be gathered first. This can be found by browsing a file on the actual VRA server using SSH. On the vRA server, run the following command: `grep -i cafe_cli= /etc/vcac/solution-users.properties | sed -e 's/cafe_cli=//'`
+
+Be sure to fill in the tenant token as the domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`.
+
+Example of a configured `OAuth 2.0` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/oauth_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-709086F0-E900-49AD-8D31-0CFD87259E9A-high.png)
+
+### vRA Auth Type
+
+The `vRA` Auth Type should be used when the vRA identity provider is configured for your vRO. The `vRA` Auth Type and `OAuth` Auth Type fields requirements are the same, execept when using `vRA` Auth Type the `Client ID` is no longer needed.
+
+## Using vRealize Orchestrator
+
+One of the first things HPE Morpheus Enterprise does when it is tied into a vRO integration is sync all available workflows by category. These workflows become available when creating a new HPE Morpheus Enterprise task in Library > Automation. HPE Morpheus Enterprise allows a user to map these vRO workflows into the task engine. The task engine allows users to design workflows that chain tasks in order or operate at different phases of a provisioning request. For more information on tasks, please read the Automation documentation.
+
+Creating a task for vRO is simple.
+
+First, go to Library > Automationand create a new task. Enter a Name and a Code, the Code can be used later to reference the results of tasks. Choose a task type of `vRealize Orchestrator Workflow`. A dropdown will appear allowing one to first select the active vRO Integration you would like to use. Once that is selected, a list of workflows becomes available.
+
+NOTE
+
+The next part is where things can get a bit tricky. The parameter body (expected in JSON) format can be a bit difficult to track down. One way is to use the Network Chrome inspector when kicking off a sample workflow from the vRO HTML5 client and grabbing the parameter JSON. Another is to query the API yourself and look at the samples from historical run history.
+
+An example payload for the SSH / Run SSH Command Workflow would look like this:
+
+```
+```
+{  
+    "parameters": [  
+        {  
+            "name": "hostNameOrIP",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "x.x.x.x"  
+                }  
+            }  
+        },  
+        {  
+            "name": "port",  
+            "type": "number",  
+            "value": {  
+                "number": {  
+                    "value": 22  
+                }  
+            }  
+        },  
+        {  
+            "name": "cmd",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "echo \"Hello <%=instance.name%>\""  
+                }  
+            }  
+        },  
+        {  
+            "name": "encoding",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        },  
+        {  
+            "name": "username",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "myuser"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passwordAuthentication",  
+            "type": "boolean",  
+            "value": {  
+                "boolean": {  
+                    "value": true  
+                }  
+            }  
+        },  
+        {  
+            "name": "password",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "password"  
+                }  
+            }  
+        },  
+        {  
+            "name": "path",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "\/var\/lib\/vco\/app-server\/conf\/vco_key"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passphrase",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        }  
+    ]  
+}
+```
+```
+
+Note that all HPE Morpheus Enterprise variables can be injected into the parameter body. In the above example we inject the instance name into the sample command with `<%=instance.name%>` but other values can be used, such as `<%= server.sshHost %>` for the hostname and `<%= server.sshPort %>` for the port. Additional variable examples can be found here: [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+Adding this task to a workflow allows the result parameters to be referenced in subsequent tasks called throughout the workflow. For example, a local script task type could reference the output text of the above ssh command by injecting the following results map: `echo "results.vro: <%=results.vro.find{it.name == 'outputText'}?.value?.string?.value%>"` With this example, `vro` refers back to the “Code” of the vRO task that would contain the ouput we wish to referece. More information on Task Results can be found here: [Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)
+
+Additional output/map examples referencing a previous task with the “Code” of `vrossh`:
+
+- Print all output: `echo '<%=results.vrossh.encodeAsJson().toString() %>'`
+- Print the `outputText` variable/output: `echo "results.vrossh.outputText: <%=results.vrossh.find{it.name == 'outputText'}?.value?.string?.value%>"`
+- Print the `errorText` variable/output: `echo "results.vrossh.errorText: <%=results.vrossh.find{it.name == 'errorText'}?.value?.string?.value%>"`
+- Print the `result` variable/output, returned as a string: `echo "results.vrossh.result: <%=results.vrossh.find{it.name == 'result'}?.value?.string?.value%>"`
+- Print the `exitcode` variable/output, returned as a number: `echo "results.vrossh.exitcode: <%=results.vrossh.find{it.name == 'exitcode'}?.value?.number?.value%>"`
+
+There are very powerful options available for chaining results and injecting variables relevant to the instance being provisioned or even custom inputs from an operational workflow. Please reference the rest of the Automation documentation for examples.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
new file mode 100644
index 0000000..2b629aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+  "title": "Syslog",
+  "ordinal": 503,
+  "parent_title": "Logs",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.html",
+  "topic_cluster": {
+    "clustering_title": "Syslog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
new file mode 100644
index 0000000..9755802
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
@@ -0,0 +1,10 @@
+# Syslog
+
+## Adding Syslog Integration
+
+### Procedure
+
+1. Navigate to Administration > Settings > Logs
+2. Expand the HPE Morpheus Enterprise logging section
+3. Add the Syslog forwarding rules
+4. Select QUICK ADD
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json b/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
new file mode 100644
index 0000000..8a46f0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+  "title": "Add Amazon ELB load balancer",
+  "ordinal": 492,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ELB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md b/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
new file mode 100644
index 0000000..9f0b30b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
@@ -0,0 +1,33 @@
+# Add Amazon ELB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ELB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz ELB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C14F7BC3-0BDA-4CF2-A85A-19B1C1EF8694-high.jpg)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..6c95de7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 319,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..00459d1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,142 @@
+# Health
+
+## HPE Morpheus Enterprise Health
+
+![../../_images/morpheusHealth500.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BB8CA295-BF75-426C-941D-EBB1FB9233DC-high.png)
+
+The HPE Morpheus Enterprise Health section provides an overview of the health of your HPE Morpheus Enterprise appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or HPE Morpheus Enterprise memory usage is above 95%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Opensearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+### Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be accessing. By default, HPE Morpheus Enterprise does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the HPE Morpheus Enterprise official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by HPE Morpheus Enterprise processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by HPE Morpheus Enterprise processes (see the Knowledge Base article linked in the TIP box below for more information on how HPE Morpheus Enterprise claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
+
+TIP
+
+It’s common to see a high percentage of system memory being used [due to the way Morpheus allocates and manages memory](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US). If HPE Morpheus Enterprise is performing well, high system memory use is not necessarily an indicator that any action needs to be taken.
+
+### Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Opensearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
+
+## HPE Morpheus Enterprise Logs
+
+The HPE Morpheus Enterprise logs section aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
+
+![../../_images/healthlogs.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..575630b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 216,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..bd2dd8e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,116 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+## Overview
+
+The Networks section is for configuring networks across all clouds in HPE Morpheus Enterprise. Existing networks from Clouds added in HPE Morpheus Enterprise will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, HPE Morpheus Enterprise allows administrators to restrict management of HPE Morpheus Enterprise-created Networks through Role permissions.
+
+## Configuring Networks
+
+### DHCP
+
+#### About this task
+
+To configure a network for DHCP:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+#### Results
+
+IMPORTANT
+
+The DHCP flag tells HPE Morpheus Enterprise this network has a DHCP server assigning IP Addresses to hosts. HPE Morpheus Enterprise does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in HPE Morpheus Enterprise , but no DHCP server actually on the network will in most cases cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
+
+### Static and IP Pools
+
+#### About this task
+
+To configure a network for Static IP Assignment:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured HPE Morpheus Enterprise or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your HPE Morpheus Enterprise appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+#### Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
+
+### Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
+
+### Group and Tenant Access
+
+Networks can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection. **Tenant Permissions** control which Tenants may see the Network. Public visibility allows access to the Network for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
+
+### Guest Console SSH Tunnel
+
+In some scenarios, instances that are segregated from the HPE Morpheus Enterprise appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the HPE Morpheus Enterprise web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by HPE Morpheus Enterprise but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in HPE Morpheus Enterprise to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
+
+### Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..6ca648c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 264,
+  "parent_title": "Tools",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..2e2dc72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,53 @@
+# Archives
+
+## Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html)). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
+
+## Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in HPE Morpheus Enterprise
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether HPE Morpheus Enterprise is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
+
+![../_images/archivelist.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C069FB35-5152-45DA-B2FE-5C7DDE5F3563-high.png)
+
+## Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, HPE Morpheus Enterprise will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
+
+## Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
+
+![../_images/archivedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3A823ED0-F545-4405-AC60-EAF927081936-high.png)
+
+## File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
+
+![../_images/filedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json b/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
new file mode 100644
index 0000000..b3e15fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+  "title": "Apps",
+  "ordinal": 87,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md b/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
new file mode 100644
index 0000000..c9a2ff0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
@@ -0,0 +1,10 @@
+# Apps
+
+Apps allow instances having general relationships to be grouped in a clean and organized manner. App functionality enables full control of which instances belong in an app as well setting Firewall and Access Control List (ACL) rules. Use Apps to structure all necessary components into a single place. Add checks and groups for web servers, database nodes, etc.
+
+Apps can be created from Blueprints, which are made in Library > Blueprints > App Blueprints or from Existing Apps.
+
+**Subtopics**  
+
+- **[Creating Apps](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html)**
+- **[Managing Apps](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..7ad3a38
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 268,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..de3253d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,24 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
+    - When migrating to NFS-backed datastores, setting `async` on the NFS server may improve performance
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json b/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
new file mode 100644
index 0000000..365fc50
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+  "title": "Bluecat",
+  "ordinal": 513,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html",
+  "topic_cluster": {
+    "clustering_title": "Bluecat",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md b/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
new file mode 100644
index 0000000..a7e0024
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
@@ -0,0 +1,58 @@
+# Bluecat
+
+## Overview
+
+HPE Morpheus Enterprise integrates with Bluecat IPAM to scope pools to networks for static IP assignment from Bluecat to your HPE Morpheus Enterprise Instances.
+
+## Adding Bluecat to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select Bluecat
+4. Enter in the following information 
+
+   Name
+   :   Name of the Bluecat Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Uncheck to disable sync with the Bluecat endpoint
+
+   URL
+   :   URL of the Bluecat server, ex: `http://10.30.20.10`
+
+   Username
+   :   Username of Bluecat API User. API and root level propagating read access required, read/write access required for target Networks and Domains.
+
+   Password
+   :   Bluecat User password
+
+   Network Filter
+   :   Optionally enter a comma-separated list of `entityIds` for config(s), block(s) or network(s) (ex. `entityId1,entityId2...`) to filter the synced IP pools, networks and domains
+5. Click SAVE CHANGES
+
+### Results
+
+The Bluecat Integration will be saved, IP pools will sync in and populate under Infrastructure  >  Network  >  IP Pools, and Domains will populate in Infrastructure  >  Network  >  Domains. Pools and Domains can also be found in the Bluecat Integration details page, which can be accessed by clicking on the name of the added Bluecat Integration in Infrastructure  >  Network  >  Services.
+
+IMPORTANT
+
+Quick Deployments must be enabled in Bluecat for HPE Morpheus Enterprise to create instantly available DNS records when using Bluecat DNS.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Bluecat IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Bluecat IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network- Networks`
+2. Select a Network name and EDIT, or select ACTIONS - Edit
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json b/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
new file mode 100644
index 0000000..e049eea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+  "title": "Using Volume",
+  "ordinal": 447,
+  "parent_title": "Volume Consumption",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html",
+  "topic_cluster": {
+    "clustering_title": "Using Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md b/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
new file mode 100644
index 0000000..96dd5dc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
@@ -0,0 +1,14 @@
+# Using Volume
+
+## About this task
+
+Perform the following to use the configured volume:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Click Add.
+3. After selecting the HPE BareMetal ILO server for type and specifying the cloud, group, and a name for the instance, click Next to advance to the Configure section.
+4. Click on the + sign next to Volumes to add a volume to this instance.
+5. Specify a name for the volume, desired size, volume type to indicate whether it is a replicated volume or not, the datastore to create it in, and whether it’s a shared volume.   
+   ![Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-090D059F-2321-4377-B832-EEAF50ED173E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json b/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
new file mode 100644
index 0000000..5dd72cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+  "title": "Creating Policies",
+  "ordinal": 317,
+  "parent_title": "Policies",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md b/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
new file mode 100644
index 0000000..67f62e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
@@ -0,0 +1,80 @@
+# Creating Policies
+
+Policies can be created in three different locations.
+
+- Administration > Policies
+- Infrastructure  >  Groups  >  Group  >  Policies
+- Infrastructure  >  Clouds  >  Cloud  >  Policies
+
+Policies can be disabled and re-enabled at anytime.
+
+IMPORTANT
+
+Precedence is applied to matching or conflicting Policies in the following order: Cloud > Group > Role > User > Global.
+
+## To create a Global Policy:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under Filter next to scope select Global
+5. Select SAVE CHANGES
+
+## To create a Policy for a User:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select User a drop down menu will appear below allowing you to select a user
+5. Select SAVE CHANGES
+
+## To create a Policy for a Role:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select Role a drop down menu will appear below allowing you to select a Role
+5. For `APPLY INDIVIDUALLY TO EACH USER IN ROLE`
+   :   - Select for Max Resource/Quota Policies to be calculated per user
+       - Leave unselected to calculate by total usage of all users within that Role.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Cloud:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Cloud the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created or moved into the Group after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select a Cloud by clicking on the name of the Cloud to go to the Cloud Detail page.
+3. Select the `POLICIES` tab in the Cloud Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Type sections below for Configuration options.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Group:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Group the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group by clicking on the name of the Group to go to the Group Detail page.
+3. Select the `POLICIES` tab in the Group Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Types sections below for Configuration options.
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json b/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
new file mode 100644
index 0000000..a0e24d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+  "title": "Workloads: Instance Type Usage",
+  "ordinal": 67,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Type Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md b/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
new file mode 100644
index 0000000..de3d9ee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Type Usage
+
+![../_images/9instancetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Instance Type Usage dashboard organizes workloads meeting dashboard filters by their Instance type. In additional to counts, administrators can view resource consumption and cost figures by Instance type groupings as well.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance type name (all matching search terms, Morpheus-default Instance types are not included when using the search filter)
+- Metric (apply to see the top Instance types by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **TYPES:** The total number of Instance types represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Type Usage List
+
+Each Instance type represented in the dashboard is listed below the graph. For each Instance type shown, we see the number of Groups the Instance type is represented in, the number of Clouds the Instance type has been provisioned into, and the total amount of memory allotted to workloads of each Instance type.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json b/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
new file mode 100644
index 0000000..a073868
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+  "title": "Data Encryption",
+  "ordinal": 36,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html",
+  "topic_cluster": {
+    "clustering_title": "Data Encryption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md b/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
new file mode 100644
index 0000000..5905180
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
@@ -0,0 +1,69 @@
+# Data Encryption
+
+By default, Morpheus encrypts sensitive data in the Database using AES encryption mode with GCM. Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files such as `morpheus-secrets.json` and `morpheus.rb` are in plain text as they are only accessible by root.
+
+Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files can be set to an encrypted string using the HPE Morpheus Enterprise crypto utility to generate ENC strings and then using `ENC(string)` as the value in the configuration file.
+
+Additionally a custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 hash, which is used to generate the AES encryption key.
+
+## Generate ENC Strings for morpheus-secrets.json
+
+### About this task
+
+System generated passwords are set in `/etc/morpheus/morpheus-secrets.json`. These entries can be updated to ENC strings with the following steps:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string migrate` which will output ENC() strings for the passwords in morpheus-secrets.json
+2. Update the desired password strings in the `morpheus-secrets.json` config file with the matching ENC() string.
+3. Save `morpheus-secrets.json`
+4. Run `morpheus-ctl reconfigure`
+
+## Generate ENC Strings for custom morpheus.rb entries
+
+### About this task
+
+ENC() strings can be generated for sensitive data set in morpheus.rb, such as the password to an external service.
+
+To generate ENC(0) strings for morpheus.rb entries:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string string $clear_text '$suffix'` which will output strings for the passwords in morpheus-secrets.json 
+
+   - Replace `$clear_text` with the string to be encrypted
+   - If a suffix is defined in morpheus.rb (as described in the next section), replace `$suffix` with your suffix.
+
+   NOTE
+
+   It is advisable to disable bash history logging by running `unset HISTFILE` before running the morphesu-ctl get-crypto-string command and then `set HISTFILE=$HOME/.bash_history` to reenable.
+2. Update the desired password strings in the `morpheus.rb` config file with the matching string output, using `ENC($output)` format 
+
+   - Example: `mysql['morpheus_password'] = 'ENC($ZI5DnaO0quhxKe$kDFD+U2ZeJUuYiNC$F1+czPNyo+3lAdq7V0gcrWwHnkINYqr13cUGrDVyog==)'`
+3. Save `morpheus.rb`
+4. Run `morpheus-ctl reconfigure`
+
+## Encrypted Key Suffix
+
+### About this task
+
+A custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 Hash, which is used in the generation of the system AES encryption key.
+
+DANGER
+
+Setting a custom Encryption Key Suffix affects all data encrypted by HPE Morpheus Enterprise, including database and cypher data. Encryption Key Suffix is required in the event data needs to be migrated or recovered. Once the Encryption Key Suffix is set, data cannot be recovered without it. Store any Encryption Key Suffix externally where it can be referenced for future scenarios.
+
+IMPORTANT
+
+The Encryption Key Suffix cannot be changed or removed after being set. Changing or removing an existing Encryption Key Suffix will prevent data access. If an existing suffix is altered in the morpheus.rb file, it must be restore to its original value.
+
+### Procedure
+
+1. Add `app['encryption_key_suffix'] = '$suffix'` to `/etc/morpheus/morpheus.rb`, replacing `$suffix` with your suffix. 
+
+   DANGER
+
+   Once an Encryption Key Suffix is set and applied via reconfigure, it cannot be altered or removed and data cannot be migrated or recovered without it.
+2. Run `morpheus-ctl reconfigure` 
+
+   - Reconfigure will generate a new encryption key using the suffix and set (ENC) values for the service password in application.yml
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json b/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
new file mode 100644
index 0000000..08e593b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+  "title": "Integrating Hashicorp Vault",
+  "ordinal": 238,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating Hashicorp Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md b/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
new file mode 100644
index 0000000..ee8c9e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
@@ -0,0 +1,27 @@
+# Integrating Hashicorp Vault
+
+The Hashicorp Vault integration is not included with HPE Morpheus Enterprise by default. Download the plugin from HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/) and add the plugin to HPE Morpheus Enterprise through the [Plugins](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) section. This allows users to store credential sets completely outside of HPE Morpheus Enterprise and in Hashicorp Vault, which may be required by your organization’s IT policies.
+
+NOTE
+
+The plugin space is universal and not specific to Tenants. If Subtenant users have access to Administration > Integrations > Plugins, any integrated plugins will be available in all Tenants across the appliance. In most cases, it makes sense to restrict access to this section from Subtenant users through the associated Tenant Role. Instead integrate plugins from the Primary Tenant and expose them to various Subtenants as needed.
+
+Once downloaded, plugins are added to HPE Morpheus Enterprise in Administration > Integrations > Plugins. Simply browse your local filesystem for the JAR file downloaded from HPE Morpheus Enterprise Exchange and its capabilities will immediately be added to the appliance. After adding the plugin, configure access for the plugin to your Vault server. Do this by clicking the Edit (pencil) button in the row for the Vault plugin. Supply a URL for your Vault server and an access token, then save your changes.
+
+NOTE
+
+When creating a Vault integration, it’s recommended that you use a long-lived token. If the token suddenly becomes invalid, HPE Morpheus Enterprise will be unable to write new credential sets to Vault and will be unable to edit or delete any existing ones. Additionally, you won’t be able to use Vault-stored credential sets elsewhere in HPE Morpheus Enterprise, such as when creating new Cloud integrations or populating REST-based Option Lists which require authentication. Should this happen, simply obtain a new token, edit the Vault integration, update the token, and save your changes.
+
+With the plugin added, a new integration type will appear in Infrastructure > Trust > Integrations. Click + ADD, then “Hashicorp Vault Credentials” to get started. The fields in the list below are available for configuration but it’s possible that no configuration will be necessary. If you do not enter a new API URL and TOKEN value, these are taken from the plugin configuration set a moment ago. Similarly, The Vault Secret Engine and Secret Path can be left at default values (or empty) if those values are acceptable. If you need to override the defaults or the URL/token set on the plugin, you may do so here.
+
+- **NAME:** A friendly name for the Vault integration in HPE Morpheus Enterprise
+- **ENABLED:** When marked, this Vault integration will be available to have credentials written to it
+- **API URL:** The URL for the Vault server (ex. <http://xx.xx.xx.xx:8200>)
+- **TOKEN:** A valid API token for the server (see note below)
+- **HASHICORP VAULT SECRET ENGINE:** Select KV Engine version 1 or 2, additional engines may be available in the future
+- **ENGINE MOUNT:** If desired, enter a custom engine mount. By default, if left empty, credentials are written to the “secret/” engine mount
+- **SECRET PATH:** If desired, enter a custom path and HPE Morpheus Enterprise will write new credential sets to that path. By default, if left empty, new credentials are written to “morpheus-credentials/”
+
+When done, click SAVE CHANGES.
+
+With the above process finished, this Vault integration will be available as a storage target when creating new credential sets. In Infrastructure > Trust > Credentials, after clicking + ADD and selecting the type of credential set to add, select the new Vault integration in the CREDENTIAL STORE field (default selection is “Internal”).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json b/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
new file mode 100644
index 0000000..db66587
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+  "title": "UpCloud",
+  "ordinal": 472,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.html",
+  "topic_cluster": {
+    "clustering_title": "UpCloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md b/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
new file mode 100644
index 0000000..8b66f6a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
@@ -0,0 +1,264 @@
+# UpCloud
+
+## Overview
+
+UpCloud is a cloud hosting provider that offers both Linux and Windows virtual machines on their MAXIOPS infrastructure which is billed as I.A.A.S ( infrastructure-as-a-service ). They have datacenters based in the UK, USA, Germany, Netherlands, Singapore and Finland. Servers can be created a lightning fast 45 seconds with their faster than SSD technology.
+
+## Features
+
+- Virtual Machine Provisioning
+- Containers
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Inventory
+- Cloudinit
+
+## Requirements
+
+### About this task
+
+An UpCloud User with API, Server and Storage permissions is required.
+
+To enable API access for a Main Account UpCloud User:
+
+### Procedure
+
+1. Login to UpCloud
+2. Select My Account  >  User Accounts
+3. Select Change on the target user
+4. Check the box for API connections: Allow API connections from
+5. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+6. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+7. Save
+
+### Results
+
+To Enable API, API, Server and Storage permissions for a SubAccount User:
+
+When creating or editing a Sub Account UpCloud user:
+
+1. Check the box for API connections: Allow API connections from
+2. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+3. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+4. Save
+
+## Adding an UpCloud Cloud
+
+### Configure
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud Button
+3. Select UpCloud from the Add Cloud modal
+4. Select NEXT
+5. Enter the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   USERNAME
+   :   UpCloud User Account Username
+
+   PASSWORD
+   :   UpCloud User Account Password
+
+   ZONE
+   :   Select UpCloud Datacenter to scope cloud to
+
+   INVENTORY
+   :   - Off: Existing UpCloud Servers will not be inventoried in HPE Morpheus Enterprise
+       - Basic: Existing Servers are Inventoried with Power state, Memory and Cores statistics synced.
+       - Full: Existing Servers are Inventoried with Power state, Memory and Cores statistics, plus IP Addresses, Storage Info, and Console VNC Information.
+
+   NOTE
+
+   Full Inventory level recommended. Basic Inventory level can reduce Cloud Sync times when inventorying Datacenters with large amounts of servers. Credentials need to be added by editing the Virtual Machine in order to connect.
+
+   The Cloud can now be added to a Group or configured with additional Advanced options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+### Group
+
+A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+- USE EXISTING: Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+- CREATE NEW: Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+
+### Review
+
+Confirm all settings are correct and select COMPLETE.
+
+The UpCloud Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of:
+
+- UpCloud Servers will added as Virtual Machines (if Inventory is enabled)
+- UpCloud Templates (My Templates) will sync and be added to Library > Virtual Images.
+
+NOTE
+
+The Console tab will only appear for Inventoried Servers if Inventory Level is set to Full
+
+## Provisioning to UpCloud
+
+Instances and Apps can be created using the private Images synced from UpCloud or from the HPE Morpheus Enterprise provided Image Catalog.
+
+## Provision a synced Image
+
+Images synced from UpCloud can be provisioned by using:
+
+- The UPCLOUD Instance Type and selecting the Image from the Image dropdown in the configure section when provisioning and Instance, App, or creating an App Blueprint.
+- Creating custom Library Instance Types and selecting a synced Image when creating a Node Type for the custom Instance Type.
+
+IMPORTANT
+
+Synced images should be configured prior to provisioning by editing the Image in the Library > Virtual Images section.
+
+## Provision a HPE Morpheus Enterprise provided UpCloud Image
+
+HPE Morpheus Enterprise provides a number of pre-configured Images that are available in the default HPE Morpheus Enterprise Catalog when provisioning and Instance, App, or creating an App Blueprint. UpCloud Images are included in the following Instance Types in the default HPE Morpheus Enterprise catalog.
+
+- ACTIVEMQ
+- APACHE
+- CASSANDRA
+- DEBIAN
+- ELASTICSEARCH
+- GRAILS
+- JAVA
+- MONGO
+- MYSQL
+- NGINX
+- PHP
+- RABBITMQ
+- REDIS
+- OMCAT
+- UBUNTU
+- WINDOWS
+- GRAILS
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json b/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
new file mode 100644
index 0000000..cd7a367
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+  "title": "Layouts",
+  "ordinal": 129,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html",
+  "topic_cluster": {
+    "clustering_title": "Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md b/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
new file mode 100644
index 0000000..c1aa3e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
@@ -0,0 +1,94 @@
+# Layouts
+
+Layouts are attached to Instance Types. A Layout can only be attached to a single Instance Type and a single Technology. An Instance Type can have one or many Layouts attached to it, allowing for a single Instance Type to work with any Technology type. Node Types are added to Layouts. A Layout can have one or many node types attached to it. Node types can be shared across Layouts of matching Technology types.
+
+IMPORTANT
+
+Once an Instance Type is defined on a Layout and saved, the Instance Type setting and Technology selections on the Layout cannot be changed.
+
+## Layout List View
+
+The default page for Layouts is the Layout list view. Select + ADD to create a new Layout. Layouts can also be created from an Instance Type detail page.
+
+The following fields are displayed for each Layout:
+
+- **INSTANCE TYPE:** Select the Instance Type to associate with the Layout. This attribute is automatically set and not shown when creating the Layout from an Instance Type detail page
+- **NAME:** Links to the Layout detail page
+- **VERSION**
+- **DISPLAY ORDER:** Determines the Layout display order in the provisioning wizard when adding an Instance of the associated Instance Type
+- **DESCRIPTION**
+
+NOTE
+
+The order of Layouts given when an Instance Type is being provisioned is in high-to-low order of the Layout Display Order property. Bear in mind this is reversed from how Service Plans are ordered, which is in low-to-high order based on the Display Order value.
+
+The Actions menu in each row reveals the following options:
+
+- **Permissions:** Scope the Layout to Group(s) to narrow the list of available groups for a chosen Instance Type at provision time
+- **Edit:** Edit the Layout
+- **Delete:** Delete the Layout
+
+NOTE
+
+A Layout that is in use cannot be deleted.
+
+Available Filters:
+
+- **Technology:** Display Layouts by selected Cloud technology
+- **Instance Type:** Display Layouts by the associated Instance Type
+
+## Layout Detail View
+
+The Layout Detail view shows details on the Layout including Name, Short Name, Version, and Category. It also lists all associated Node Types.
+
+- Select a Layout Name from the list page or Instance Type detail page to get to a Layout detail page.
+
+## Layout Configuration Options
+
+Instance Type
+:   Select the Instance Type to add to the new Layout. Custom Instance Types must already be created and one Layout cannot be added to multiple instance types. The Instance Type also cannot be changed after creation.
+
+    NOTE
+
+    Layouts cannot be added to Morpheus pre-defined Instance Types
+
+Name
+:   The name the Layout presents as in the Configuration Options dropdown of the provisioning wizard
+
+Version
+:   The version number or name for the Layout. Layouts in an Instance Type with the same version will all show under the Configuration Options dropdown when that version is selected while provisioning
+
+Description
+:   Description of the Layout, viewable on the Layout list view
+
+Creatable
+:   When checked, this Layout will be selectable at provision time for the associated Instance Type (assuming the Layout is otherwise compatible with provisioning conditions). Instance Types with no Creatable Layouts will not be selectable from the provisioning wizard
+
+Technology
+:   Technology determines which Cloud this layout will be available for and which Node Types can be added to it
+
+Minimum Memory
+:   Defines the minimum amount of memory required for this Layout. Only Service Plans that meet the defined memory minimum will be available during provisioning when this Layout is selected. Custom memory values must also meet this minimum. Entering a minimum memory value of zero (the default value) indicates no minimum. This minimum memory value will override any Virtual Image minimum memory requirements
+
+Workflow
+:   Select a Workflow which will be associated as the Provisioning Workflow for Instances provisioned using this Layout. If a Workflow is defined, it is not shown to the user at provision time and will be run in addition to any Workflows set on the Instance Type, in Workflows Policies, defined in App Blueprints, or selected manually at provision time.
+
+Supports Convert to Managed
+:   Enabled to allow users to select this layout when converting a Discovered workload to Managed
+
+Enable Scaling (Horizontal)
+:   Enables Instances with this layout to use scaling features
+
+Environment Variables
+:   Custom environment variables to be added to the Instance when provisioned
+
+Inputs
+:   Search for and select one or multiple Inputs to add to the Layout. Inputs (except for Hidden Inputs) will appear in Provisioning, App, Blueprint, and Cloning wizards when this layout is selected
+
+Nodes
+:   Single or multiple nodes can be added to a Layout by searching for and selecting the Node(s)
+
+Price Sets
+:   Associate a Price Set with the Layout, Price Sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Layouts become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Layout. If this Layout is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Layout Price Sets Demo**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json b/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
new file mode 100644
index 0000000..c66c4bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+  "title": "Supported Software Versions",
+  "ordinal": 396,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Software Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md b/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
new file mode 100644
index 0000000..11461cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
@@ -0,0 +1,15 @@
+# Supported Software Versions
+
+**Required Software**
+
+Ensure your environment uses the following software versions before you proceed. Features and behavior may vary across different releases.
+
+- HPE Morpheus Enterprise: Version 8.1.0
+- HPE BMaaS: Version 1.0.0
+
+**Managed Networking and External Storage Requirements**
+
+Install the following integrations only if your environment requires managed networking or external storage:
+
+- HPE ArubaCX Network Integration: Version 1.9.0
+- HPE Alletra MP Integration: Version 1.9.0
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.json b/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
new file mode 100644
index 0000000..644e0ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+  "title": "CentOS/RHEL 7 Images",
+  "ordinal": 50,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html",
+  "topic_cluster": {
+    "clustering_title": "CentOS/RHEL 7 Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.md b/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
new file mode 100644
index 0000000..256607e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
@@ -0,0 +1,3 @@
+# CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json b/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
new file mode 100644
index 0000000..8e5efdf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+  "title": "Distributed Workers",
+  "ordinal": 313,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.html",
+  "topic_cluster": {
+    "clustering_title": "Distributed Workers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md b/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
new file mode 100644
index 0000000..93a690c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
@@ -0,0 +1,146 @@
+# Distributed Workers
+
+## Overview
+
+The HPE Morpheus Enterprise distributed worker is installed using the same package as the VDI Gateway worker. Organizations which have already deployed VDI Gateway(s) can use the same worker for both purposes if desired, you’d simply need to update configuration in `/etc/morpheus/morpheus-worker.rb` and run a reconfigure. When creating a distributed worker or VDI Gateway object in HPE Morpheus Enterprise UI, an API key is generated. Adding one or both types of API keys to the worker configuration file determines if the worker is running in VDI gateway and/or distributed worker mode.
+
+### Supported Cloud Types
+
+The following Cloud/Zone types support Distributed Workers
+
+- vmware
+- vmwareCloudAws
+- nutanix
+- openstack
+- xenserver
+- macstadium
+
+## Installation
+
+A distributed worker VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+Package URLs for the distributed worker are available at <https://app.morpheushub.com> in the downloads section.
+
+NOTE
+
+The distributed worker requires that the HPE Morpheus Enterprise appliance has a trusted SSL certificate. This can be accomplished by configuring a public trusted SSL certificate on the HPE Morpheus Enterprise appliance (or load balancer) or ensure the certificate and chain are added to the Java Keystore of the Distributed Worker to trust the certificate.
+
+### Requirements
+
+Table 1. Supported Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE SLES | 12 |
+| Ubuntu | 18.04, 20.04, 22.04 |
+
+- **Memory:** 4 GB RAM minimum recommended
+- **Storage:** 10 GB storage minimum recommended. Storage is required for installation packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity **to** the HPE Morpheus Enterprise appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise worker package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+IMPORTANT
+
+In order to proxy VMware vCenter Cloud traffic through a Distributed Worker, you must have a static public DNS entry for the internal IP address of the vCenter appliance. If this is not done, everything may appear to be working properly when configuring the Cloud but problems will arise at provision time. This is not a HPE Morpheus Enterprise limitation but is a limitation of the VMware SDK client which does not natively support proxies.
+
+Download the appropriate package from HPE Morpheus Enterprise Hub based on your target Linux distribution and version for installation in a directory of your choosing. The package can be removed after successful installation.
+
+```
+```
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+```
+```
+
+Validate the package checksum as compared with the values indicated on Hub. For example:
+
+```
+```
+sha256sum morpheus-worker-$version.distro
+```
+```
+
+Next, install the package using your selected distribution’s package installation command and your preferred options. Example, for RPM:
+
+**rpm**:
+
+```
+```
+$ sudo rpm -ihv morpheus-worker-$version.$distro  
+Preparing...                          ################################# [100%]  
+Updating / installing...  
+   1:morpheus-worker-x.x.x-1.$distro    ################################# [100%]  
+Thank you for installing Morpheus Worker!  
+Configure and start the Worker by running the following command:  
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+## Configuration
+
+With the package installed, we need to add a new distributed worker in HPE Morpheus Enterprise UI. Distributed workers are added in Administration > Integrations > Distributed Workers. To create one, populate the following fields:
+
+- **NAME:** A name for the distributed worker in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the distributed worker
+- **PROXY HOSTS:** A comma-delimited list of global proxy hosts, any endpoint listed here will be proxied through the HPE Morpheus Enterprise worker. For VMware, you must list the host addresses for any vCenter you wish to proxy through the worker. Xen hosts and PowerVC hosts must be listed here as well. Other Cloud types which are supported by the HPE Morpheus Enterprise worker need only have the worker configured on the Edit Cloud modal (Infrastructure > Clouds > Selected Cloud > Editbutton)
+- **ENABLED:** When marked, the selected worker is available for use
+
+IMPORTANT
+
+The proxy host URL entered in the Worker configuration must match the URL set in the Cloud configuration. That is, if you use the URL in the Cloud configuration you must also use it in the Worker configuration. The reverse is also true, if an IP address is used in the Cloud configuration, that should be used in the Worker configuration as well. There are also configuration considerations that must be made for proxying vCenter Cloud traffic through a Distributed Worker. See the “IMPORTANT” box in the “Requirements” section for additional details.
+
+After clicking SAVE CHANGES, an API key is generated and displayed. Make note of this as it will be needed in a later configuration step.
+
+![../../_images/createWorker.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C9464126-F50C-4309-9A8F-892576EBC646-high.png)
+
+With the worker configured in HPE Morpheus Enterprise, the next step is to update supported Cloud integrations which should be proxied through the worker. Select the desired Cloud from the Clouds List Page (Infrastructure > Clouds) and click EDIT from the chosen Cloud’s Detail Page. Within the Connection Options section, choose a configured worker from the WORKER dropdown menu. Click SAVE CHANGES.
+
+![../../_images/addWorkerToCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-42AD2A2E-CE88-4F15-AECE-FC70A4C7B574-high.png)
+
+With the API key in hand and configuration complete in HPE Morpheus Enterprise UI, head back to the worker box. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following:
+
+```
+```
+worker_url = 'https://gateway_worker_url' # This is the worker URL the Morpheus appliance can resolve and reach on 443  
+worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of Morpheus appliance which the worker can reach on port 443  
+worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from Morpheus Appliance VDI Pools > VDI Gateways configuration. For worker only mode, a value is still required but can be any value, including the 'API KEY FOR THIS GATEWAY' default template value  
+worker['worker_key'] = 'DISTRIBUTED WORKER KEY' # Distributed Worker API Key from Administration > Integrations > Distributed Workers configuration  
+worker['proxy_address'] = 'http://proxy.address:1234' # For environments in which the worker must go through a proxy to communicate with the Morpheus appliance or other resources, configure the address  
+worker['no_proxy'] = 'vcenter.example.com,192.168.xx.xx' # A comma-separated list of resources that should be accessed directly and not through the proxy
+```
+```
+
+NOTE
+
+By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+
+After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services:
+
+```
+```
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+TIP
+
+If the reconfigure process fails due to a missing dependency, add the repo that the missing dependency can be found in and run
+
+NOTE
+
+Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+
+Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+## Highly-Available (HA) Deployment
+
+If desired, multiple distributed worker nodes may be associated to the same HPE Morpheus Enterprise appliance to eliminate a single point of failure should a distributed worker node go down. Configure each distributed worker node using the same worker key (process described in the prior section) and add redundancy using as many additional workers nodes as needed. When multiple worker nodes are using the same worker key, proxy calls will always go through the primary worker node when possible. The primary node is the first worker node configured using a specific worker key. When necessary, automatic failover will take place and another active worker node will be used. While proxy calls will always try to use the primary node when available, HPE Morpheus Enterprise Agent communications can be balanced equally across worker nodes by placing a VIP in front of your distributed workers.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json b/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
new file mode 100644
index 0000000..cb15dc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+  "title": "Base Requirements",
+  "ordinal": 4,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html",
+  "topic_cluster": {
+    "clustering_title": "Base Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md b/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
new file mode 100644
index 0000000..0ecfcbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
@@ -0,0 +1,38 @@
+# Base Requirements
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x, 9.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+| Rocky | 8, 9 |  |
+
+- **Memory:**[16 GB recommended](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US) for default installations. 8 GB minimum required with 4 GB+ available storage swap space
+- **Storage:** 200 GB storage minimum (see Storage Considerations below)
+- **CPU:** 4-core, 1.4 GHz (or better), 64-bit CPU recommended for all-in-one systems. For a distributed-tier installation, it’s recommended each tier have 2-core, 1.4 GHz (or better), 64-bit CPU
+- Network connectivity from your users to the appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise appliance package
+- HPE Morpheus Enterprise service nodes must be configured to use accurate NTP servers. A service node may be an app node, database node, RabbitMQ, or Elasticsearch node (see HPE Morpheus Enterprise system architecture details further on in the installation section for more details)
+- Required repository access:
+  :   - Prior to installing the HPE Morpheus Enterprise Appliance you will need to ensure that the target server or virtual machine has access to the base YUM/DNF or APT repositories
+      - A RHEL 8 server requires the `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repository be enabled and accessible
+      - A RHEL 7 server requires access to Optional RPMs repo. The repository need to be enabled and accessible
+- An appliance license is required for any operations involving provisioning
+- Current major web browsers supporting modern standards, such as Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge are supported
+- Internet Connectivity (optional)
+  :   - Access to `https://www.hpe.com/support/hpesc`, `https://share.morpheusdata.com`, and `https://d2u3hdjdxt56gx.cloudfront.net` (the share.morpheusdata.com cloudfront domain that share package requests will redirect to) over port 443 required on app nodes when reconfiguring to download embedded packages and plugins.
+      - Access to `https://morpheus-images.morpheusdata.com`, `https://registry.morpheusdata.com`, and `https://playbooks.morpheusdata.com` To download HPE Morpheus Enterprise’ system images and playbooks.
+      - Offline installation requires installing the supplemental package in addition to the regular installation package. Local yum/apt repo access still required for offline installations.
+
+NOTE
+
+Access to `yum` and `apt` repos is still required for offline installations.
+
+- VM and Host Agent Install (optional)
+  :   - Inbound connectivity access from provisioned VMs and container hosts on port 443 (Agent install and communication). Port 80 may be required for older `apt` distros.
+      - An Appliance URL that is accessible/resolvable to all managed hosts. It is necessary for all hosts that are managed by HPE Morpheus Enterprise to be able to communicate with the appliance server ip on port 443. This URL is configured under Administration > Settings.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json b/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
new file mode 100644
index 0000000..539822d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+  "title": "Creating a Storage Server",
+  "ordinal": 439,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md b/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
new file mode 100644
index 0000000..16c50f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
@@ -0,0 +1,19 @@
+# Creating a Storage Server
+
+## About this task
+
+This procedure guides you through creating a storage server.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > Servers.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage HVM for type, specify the URL for the storage array, and the credentials.
+5. Click the Save Changes to create the storage server.   
+   ![Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-27BC7480-6D59-4328-A9E6-34871F98D44A-high.png)
+
+## Results
+
+The added storage server appears under Servers.   
+![storage server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-34DE4590-20A0-495D-BF21-0EC690472E30-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json b/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
new file mode 100644
index 0000000..0c5896f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+  "title": "Cluster Layouts",
+  "ordinal": 144,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md b/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
new file mode 100644
index 0000000..46d619e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
@@ -0,0 +1,13 @@
+# Cluster Layouts
+
+HPE Morpheus Enterprise includes many different types of Cluster Layouts out-of-the-box which support a number of provisioning technologies. Many of these HPE Morpheus Enterprise-provided Cluster Layouts may also be cloned for use in creating custom layouts. Edit or delete user-created Cluster Layouts using the pencil (✎) or trash can (🗑) icons next to the desired layout on the Cluster Layouts list page. See the next section for an
+
+![../../_images/clusterLayouts.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-828B4DE9-16E1-4F18-9F19-FDC0410DB2C6-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise now syncs available (non-preview) AKS k8s versions daily. Existing synced versions that are no longer supported by Azure are automatically disabled. The table below includes available AKS versions at time of v8.0.7 release.
+
+**Subtopics**  
+
+- **[Creating Custom Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json b/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
new file mode 100644
index 0000000..6bb5460
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+  "title": "2 Factor Authentication",
+  "ordinal": 334,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md b/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
new file mode 100644
index 0000000..971f3d3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
@@ -0,0 +1,21 @@
+# 2 Factor Authentication
+
+HPE Morpheus Enterprise supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+## Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and HPE Morpheus Enterprise will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
+
+## Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
+
+## Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json b/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
new file mode 100644
index 0000000..1c77169
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+  "title": "Troubleshooting and Diagnostics",
+  "ordinal": 448,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting and Diagnostics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md b/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
new file mode 100644
index 0000000..fbf5d97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
@@ -0,0 +1,30 @@
+# Troubleshooting and Diagnostics
+
+This section provides a structured approach to diagnose and resolve common issues encountered during compute, OS imaging, networking, and storage operations.
+
+Use the following details to obtain the accurate troubleshooting details:
+
+- Identify the symptom: locate the closest match in the table or subsection.
+- Confirm the likely cause: check the listed items using the provided tools and logs.
+- Apply the suggested fix: perform the recommended actions.
+- Collect diagnostic information: if the issue persists, gather logs and screenshots for support escalation.
+
+When reporting an issue, you require the following diagnostics details:
+
+- **System Details**
+  - Hostname / Device ID
+  - OS version and build
+  - BIOS/Firmware version
+- **Event Details**
+  - Date and time of failure
+  - Step at which failure occurred
+  - Any error messages or codes
+- **Logs**
+  - Relevant log files for the failed component
+  - Screenshots of errors (if applicable)
+
+**Subtopics**  
+
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html)**
+- **[Networking](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json b/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
new file mode 100644
index 0000000..9256343
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+  "title": "Catalog Items",
+  "ordinal": 138,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog Items",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md b/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
new file mode 100644
index 0000000..c4d5986
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
@@ -0,0 +1,19 @@
+# Catalog Items
+
+The Self Service catalog (Library > Blueprints > Catalog Items) is where administrators can create easily-deployable items for consumption by users operating under the “Service Catalog” Persona in HPE Morpheus Enterprise. Catalog items can be fully-configured HPE Morpheus Enterprise Instances or Blueprints, complete with user input through HPE Morpheus Enterprise Inputs, automation Workflows, and more. The catalog items are presented in a simplified interface for ease of deployment without sacrificing configurability for administrators. All available catalog items are built in the Self Service area and users will see relevant items in their catalogs based on Role permissions.
+
+NOTE
+
+For more on Personas and using the Service Catalog persona, see the Personas sections of our documentation.
+
+Access is granted to the Self Service section through the Library: Catalog Items Role permission. Users with Read rights can view the catalog while users with full rights can create and edit catalog items. Users without any rights to Self Service will not be able to access the page at all.
+
+Additionally, a user’s Role determines access to the standard and/or service catalog persona and which service catalog items are available for a user under the service catalog persona. See the Roles section of HPE Morpheus Enterprise documentation for more information on administering Roles.
+
+**Subtopics**  
+
+- **[Viewing the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html)**
+- **[Building Catalog Instances](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html)**
+- **[Building Catalog Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html)**
+- **[Building Catalog Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html)**
+- **[Editing and Deleting from the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json b/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
new file mode 100644
index 0000000..ea10a0b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+  "title": "Identity Management",
+  "ordinal": 486,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md b/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
new file mode 100644
index 0000000..c22faf9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
@@ -0,0 +1,9 @@
+# Identity Management
+
+**Subtopics**  
+
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6_2.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96_2.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E_2.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F_2.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json b/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
new file mode 100644
index 0000000..aa2c10a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+  "title": "Containers",
+  "ordinal": 477,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md b/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
new file mode 100644
index 0000000..238e5d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
@@ -0,0 +1,5 @@
+# Containers
+
+**Subtopics**  
+
+- **[Docker Registry](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json b/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
new file mode 100644
index 0000000..48442ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+  "title": "Commvault",
+  "ordinal": 382,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.html",
+  "topic_cluster": {
+    "clustering_title": "Commvault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md b/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
new file mode 100644
index 0000000..63daf1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
@@ -0,0 +1,97 @@
+# Commvault
+
+HPE Morpheus Enterprise integrates with Commvault for selection as a Cloud backup target. Compatible Clouds include VMware and OpenStack. HPE Morpheus Enterprise integrates with your existing Commvault appliance, which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Commvault with HPE Morpheus Enterprise, sharing a Commvault integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Commvault integration as the default backup target for compatible clouds
+- Select Commvault integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Commvault Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Services
+2. Select + ADD
+3. Select Commvault
+4. Fill in the following: 
+
+   Name
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enable the Commvault integration
+
+   Host
+   :   IP or Hostname of the Commvault server.
+
+   Port
+   :   Port number configured to access the Commvault server
+
+       TIP
+
+       Enter the port to connect with the Commvault web server, by default this is port 81. For more, see [Commvault port requirement documentation](https://documentation.commvault.com/11.24/essential/7102_port_requirements_for_commvault.html).
+
+   Username
+   :   Admin Username for Commvault
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. SAVE
+
+## Set Commvault as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Commvault integrations are supported as backup target for VMware and OpenStack Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware or OpenStack Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Commvault integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProviders.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-81075293-A540-4075-BAC0-19F608D18FA8-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Commvault is set as the backup provider, Commvault will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Commvault backup type
+- **Backup Server:** Select the desired server synced from the Commvault backup provider associated with the Cloud
+- **Backup Set:** Select a configured backup set synced from the Commvault backup provider associated with the Cloud
+- **Storage Policy:** Gold, Silver, or Bronze. Select the applicable SLA or retention policy for the workload being provisioned. The meanings of these retention tiers are configurable in Commvault
+- **Backup Name:** A name for the backup in HPE Morpheus Enterprise, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7E2EA78B-D0ED-4017-A07E-8815E86AB7D3-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Commvault
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
new file mode 100644
index 0000000..a4e96ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+  "title": "Overview",
+  "ordinal": 292,
+  "parent_title": "Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
new file mode 100644
index 0000000..00eb1cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
@@ -0,0 +1,11 @@
+# Overview
+
+Within HPE Morpheus Enterprise is a wide array of role based access control capabilities. These roles can be managed within the Admin > Roles section of the HPE Morpheus Enterprise UI as well as through the API or CLI. They are designed to be robust enough to fit within a wide array of enterprise and managed service provider scenarios so they can be a bit hard to grasp at first, but should make sense once a few simple concepts are explained. There are two types of roles within HPE Morpheus Enterprise called Tenant and User based roles. Both sets of roles allow restrictions to be imposed on a user at the feature access level. Entire sections within the appliance UI can be hidden based on the specified access levels for features within HPE Morpheus Enterprise. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full. Instance Type access is also common among both role types which allow the administrator to restrict which service catalog items they are allowed to provision within HPE Morpheus Enterprise .
+
+There are several handy tricks for creating new roles within HPE Morpheus Enterprise and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the HPE Morpheus Enterprise UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
new file mode 100644
index 0000000..0ff3b60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+  "title": "Linux OS Imaging",
+  "ordinal": 413,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html",
+  "topic_cluster": {
+    "clustering_title": "Linux OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
new file mode 100644
index 0000000..60e2809
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
@@ -0,0 +1,95 @@
+# Linux OS Imaging
+
+This section describes the supported Linux distributions and guides for deploying Linux on bare metal using Morpheus. It includes validated OS versions, required virtual image settings, boot loader configuration for unattended installation, and troubleshooting steps for common deployment issues (see Section Troubleshooting for more details).
+
+The following Linux distributions have been validated for deployment:
+
+- Red Hat Enterprise Linux (RHEL) and derivatives
+
+  - RHEL 9.5
+  - Oracle Linux 8.10
+  - Oracle Linux 9.5
+- Ubuntu Server
+
+  - Ubuntu Server 22.04.5 LTS
+  - Ubuntu Server 24.04.3 LTS
+
+## Virtual Image Configuration
+
+When adding a Linux ISO to Library > Virtual Images, ensure the following settings:
+
+- Operating System: Select the appropriate OS (e.g., RHEL 9, Oracle Linux 9, Ubuntu 22.04, Ubuntu 24.04)
+- Is Cloud Init Enabled: Checked
+- Advanced
+
+  - VM Tools Installed: Checked
+
+## Boot Prompt Configuration - RHEL and Oracle Linux
+
+Unmodified RHEL and Oracle Linux ISOs include a default boot menu entry: `Test this media & install OS`.
+
+This entry performs a **full media verification** before installation.
+
+NOTE
+
+- The media check does not cause installation failure.
+- It can, however, delay deployment by 30–60 minutes, particularly in remote or virtual media environments.
+- Skipping the media check is recommended to reduce installation time.
+
+**Supported Options**
+
+- Preferred: Modify the ISO
+  - Adjust the ISO boot loader to remove or bypass the media check from the default boot entry.
+  - Ensures faster, fully unattended deployment.
+- Alternative: Manual Boot Selection
+  - At boot: Select `Install OS` (without media test).
+  - Do NOT select `Test this media & install OS`.
+- **Reference**
+  - Grub menu example (for clarity):
+  - `0 → Install Red Hat Enterprise Linux 9.5`
+  - `1 → Test this media & install Red Hat Enterprise Linux 9.5`
+  - Default entry index `1` triggers the media check.
+- Changing the default to `0` or manually selecting `Install OS` skips verification.
+
+  
+![Test media and install](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-65FC9E75-A386-4A4A-A6BE-591A95640685-high.png)
+
+## Boot Prompt Configuration - Ubuntu Server
+
+Ubuntu Server requires kernel boot parameters to enable unattended installation using cloud-init autoinstall.
+
+Unmodified ISOs do not automatically perform unattended installation.
+
+## Required Manual Step (Unmodified ISO)
+
+At the GRUB boot menu:
+
+- Highlight the default Ubuntu entry.
+- Press **e** to edit.
+- Append the following kernel parameters: `autoinstall ds=nocloud`
+- Boot with the modified entry.
+- Example Boot Entry:
+
+  ```
+  ```
+  menuentry "Ubuntu" {  
+      set gfxpayload=keep  
+      linux   /casper/vmlinuz quiet autoinstall ds=nocloud ---  
+      initrd  /casper/initrd  
+  }
+  ```
+  ```
+
+This enables cloud-init–based unattended installation.
+
+## Licensing and Registration
+
+After installation, register the OS to receive updates and support.
+
+Table 1. License and Registration
+
+     | Distribution | Registration Reference | Notes |
+| --- | --- | --- |
+| RHEL | [Red Hat Subscription-Manager Registration Guide](https://access.redhat.com/solutions/253273?utm_source=chatgpt.com) | Use `subscription-manager` to register and attach subscriptions. |
+| Oracle Linux | [Registering Oracle Linux System with ULN](https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/registering-oracle-linux-system-uln.html?utm_source=chatgpt.com) | Use the `uln_register` tool to register with Oracle Unbreakable Linux Network. |
+| Ubuntu | [Ubuntu 24.04 LTS Release Notes](https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890) | Ubuntu does not require mandatory registration. An optional Ubuntu Pro subscription provides extended security maintenance and support. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
new file mode 100644
index 0000000..f330fce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+  "title": "Networking",
+  "ordinal": 452,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html",
+  "topic_cluster": {
+    "clustering_title": "Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
new file mode 100644
index 0000000..16fe6b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
@@ -0,0 +1,15 @@
+# Networking
+
+| S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Cloud Network Mode Configuration | Cloud can operate in **Unmanaged** or **Managed (ArubaCX-Int)** network modes. This choice is made during cloud creation under **Advanced Options**. | Verify the correct network mode selected during cloud creation. | Morpheus UI log | Use Unmanaged for external network control; use Managed for Morpheus-managed ArubaCX switches. |
+| 2 | Unmanaged Network - Default Setup | In Unmanaged mode, Morpheus creates a minimal configuration: a default Resource Pool and a default unmanaged network. The default network is **untagged** and uses **DHCP**. | Ensure the DHCP server exists and the network is configured for an untagged VLAN. | Morpheus UI log | This allows instances to boot with connectivity without extra network configuration. |
+| 3 | Unmanaged Network - Additional VLANs | Users can create additional VLANs/networks as required. | Check VLAN configuration and availability in provisioning options. | Morpheus UI log | Additional networks can be consumed by bare-metal instances. |
+| 4 | Managed Network - ArubaCX Integration | Managed mode uses ArubaCX switches and requires the ArubaCX plugin. | Confirm the ArubaCX plugin is loaded in Morpheus. | Morpheus UI log | Managed networks allow Morpheus to configure VLANs on switches automatically. |
+| 5 | Adding HPE ArubaCX Plugin | The plugin must be loaded to enable managed network features. Follow the procedure Adding HPE BMaaS Integration to load the plugin JAR. | Verify plugin status in Morpheus. | Morpheus UI log | Required before creating network integrations. |
+| 6 | Creating ArubaCX Network Integration | Integration defines switch credentials and switch pairs (typically 2 per rack). | Verify switch IPs, username, and password are correct. | Morpheus UI log | One integration is needed per rack (switch pair). |
+| 7 | Creating Managed Networks | Networks represent VLANs and include attributes like subnet, gateway, DNS, and IP allocation method. | Ensure VLAN ID, trunks, and subnet are correct. | Morpheus UI log | Primary VLAN is untagged, VLAN trunks are tagged. |
+| 8 | Private Network Option | Private networks do not configure a primary VLAN on the uplink, making them inaccessible outside the cloud. | Confirm if the network should be private or public. | Morpheus UI log | Used for internal workload networks only. |
+| 9 | Network Consumption During Provisioning | Networks are attached to physical or bonded interfaces. Primary VLAN is untagged, trunk VLANs are tagged. | Check interface type (physical or bond) and correct VLAN assignment. | Morpheus UI log | Supports Static Bond, LACP Bond, and Switch Independent Bond. |
+| 10 | Bond Interface Configuration | Bond interfaces require two physical ports to form an aggregated link. | Ensure both physical ports are available and correctly mapped. | Morpheus UI log | Bonding provides bandwidth aggregation and redundancy. |
+| 11 | Virtual Network Interfaces | Virtual networks allow tagged VLANs to be configured as IP interfaces on the server OS. | Verify if tagged networks require an IP interface. | Morpheus UI log | If not needed, do not configure the virtual interface. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..9c1167f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 218,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..b4a6e2a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,41 @@
+# Routers
+
+## Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. HPE Morpheus Enterprise supports the creation of the following router types depending on networks that are currently configured:
+
+- Amazon Internet Gateway
+- Huawei Router
+- Neutron Router
+- NSX Edge Gateway
+- NSX Edge Logical Router
+- NSX Cloud Tier0 Gateway
+- NSX Cloud Tier1 Gateway
+- NSX Tier0 Gateway
+- NSX Tier1 Gateway
+- Open Telekom Router
+
+## Create New Router
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
+
+## Editing Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
+
+## Deleting Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
new file mode 100644
index 0000000..8ab0655
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+  "title": "Avamar",
+  "ordinal": 386,
+  "parent_title": "Backups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.html",
+  "topic_cluster": {
+    "clustering_title": "Avamar",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
new file mode 100644
index 0000000..0d510b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
@@ -0,0 +1,57 @@
+# Avamar
+
+HPE Morpheus Enterprise integrates with an existing Avamar appliance which can then be set as the preferred backup solution for any compatible Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Avamar with Morpheus. Once the integration is complete, when editing or adding compatible Clouds, set the Avamar integration as the backup provider for the Cloud. At provision time, set Avamar backup configurations for the workload. When necessary, restore Instances from Avamar backup.
+
+IMPORTANT
+
+Avamar API must be installed on Avamar server (not installed by default)
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Avamar integration as the default backup target for compatible Clouds
+- Select Avamar integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Avamar Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Avamar
+4. Fill in the following: 
+
+   Name
+   :   Name for the Avamar integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When checked, the integration is selectable as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Avamar API server
+
+   Port
+   :   Port number configured to access the Avamar server
+
+   Username
+   :   Admin username for Avamar
+
+   Password
+   :   Password for the user provided. Choose to enter credentials locally or use a securely-stored credential set saved previously
+
+   Tenant
+   :   Avamar Tenant/Domain scoping for the integration
+
+   Hypervisor
+   :   Avamar Hypervisor scoping for the integration
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that adds the integration
+
+           Public
+           :   Available to Subtenants (Master Tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json b/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
new file mode 100644
index 0000000..3c9abf9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+  "title": "Costing: Tenant Costing",
+  "ordinal": 60,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tenant Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md b/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
new file mode 100644
index 0000000..587cdf6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
@@ -0,0 +1,31 @@
+# Costing: Tenant Costing
+
+![../_images/3tenantcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D08A61BD-C24A-4D73-82C0-45BAEBC26DCB-high.png)
+
+The Tenant Costing dashboard aggregates costing totals across all Tenants that meet the filters set on the dashboard. This information helps administrators track the current spend of each Tenant for the current monthly period. It also helps identify the costliest Tenants and to anticipate month-end costs for each individual Tenant.
+
+## Filters
+
+Filter the Tenants pulled into the dashboard by one or more of the following fields:
+
+- Tenant (all matched by search)
+- Cloud
+- Tenant (selected from dropdown)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Tenants that meet set filters:
+
+- **TENANTS:** The total number of Tenants that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Tenants meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Tenants meeting dashboard filters
+- **LAST MONTH:** The total spend in the prior month for all Tenants meeting dashboard filters
+
+## Tenant List
+
+Each Tenant that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Tenant:
+
+- **NAME:** The name given to the Tenant in HPE Morpheus Enterprise at the time of creation
+- **DESCRIPTION:** The Tenant description (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Tenant listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Tenant listed
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json b/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
new file mode 100644
index 0000000..d32ae8f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+  "title": "AWS",
+  "ordinal": 388,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html",
+  "topic_cluster": {
+    "clustering_title": "AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md b/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
new file mode 100644
index 0000000..7e4453a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
@@ -0,0 +1,959 @@
+# AWS
+
+## Overview
+
+AWS is the Amazon public cloud, offering a full range of services and features across the globe in various datacenters. AWS provides businesses with a flexible, highly scalable, and low-cost way to deliver a variety of services using open standard technologies as well as proprietary solutions. This section of documentation will help you get HPE Morpheus Enterprise and AWS connected to utilize the features below:
+
+## Features
+
+- Instance, Service, Infrastructure Provisioning & Synchronization
+- EKS Cluster Creation & Synchronization
+- HPE Morpheus Enterprise Kubernetes, Docker & KVM Cluster Creation
+- ELB Classic Load Balancer Creation & Synchronization
+- ELB Application Load Balancer (ALB) Creation & Synchronization
+- Security Group Creation & Synchronization
+- Security Group Rule Creation & Synchronization
+- Network Synchronization
+- VPC Creation & Synchronization
+- CloudFormation Provisioning & Resource Synchronization
+- Terraform Provisioning & Resource Synchronization
+- Pricing & Costing Synchronization
+- MetaData Tag Creation & Synchronization
+- S3 Bucket Creation & Synchronization
+- Route53 Automation & Synchronization
+- IAM Profile Synchronization and Assignment
+- RDS Support
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Remote Console (SSH & RDP)
+- Lifecycle Management and Resize
+- Restore from Snapshots
+- Elastic IP Assignment
+- Network Pools
+- Enhanced Invoice Costing
+
+## Requirements
+
+AWS IAM Security Credentials
+:   Access Key Secret Key Sufficient User Privileges (see [MinimumIAMPolicies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html#GUID-4A622A6F-E3FD-431B-B748-EF492C316D40) section for more info)
+
+Security Group Configuration for Agent Install, Script Execution, and Remote Console Access
+:   - Typical Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389 (22 & 3389 required for Console. 22 & 5985 required for agent-less comms)
+    - Typical Outbound to HPE Morpheus Enterprise Appliance: 443 (Required for Agent install & comms)
+
+    NOTE
+
+    These are required for HPE Morpheus Enterprise agent install, communication, and remote console access for windows and linux. Other configurations, such as docker instances, will need the appropriate ports opened as well. Cloud-init Agent Install mode does not require incoming access for port 22.
+
+Network(s)
+:   IP assignment required for Agent install, Script Execution, and Console if the HPE Morpheus Enterprise Appliance is not able to communicate with AWS instances private ip’s.
+
+## Adding an AWS Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud
+3. Select AWS
+4. Enter the following:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+#### About this task
+
+REGION
+:   Select AWS Region for the Cloud. AWS Clouds may also be scoped to all regions.
+
+ACCESS KEY
+:   Access Key ID from AWS IAM User Security Credentials.
+
+SECRET KEY
+:   Secret Access Key associated with the Access Key ID.
+
+USE HOST IAM CREDENTIALS
+:   Check to use use Host IAM Credentials
+
+ROLE ARN
+:   Supports security token service (STS) to AssumeRole by entering an AWS Role ARN
+
+EXTERNAL ID
+:   When required to AssumeRole, included the needed External ID
+
+INVENTORY
+:   Basic
+    :   HPE Morpheus Enterprise will sync information on all EC2 Instances in the selected VPC the IAM user has access to, including Name, IP Addresses, Platform Type, Power Status, and overall resources sizing for Storage, CPU and RAM, every 5 minutes. Inventoried EC2 Instances will appear as Unmanaged VM’s.
+
+    Full
+    :   In addition to the information synced from Basic Inventory level, HPE Morpheus Enterprise will gather Resource Utilization metrics for Memory, Storage and CPU utilization per VM.
+
+    Off
+    :   Existing EC2 Instances will not be inventoried
+
+    NOTE
+
+    Cloud Watch must be configured in AWS for HPE Morpheus Enterprise to collect Memory and Storage utilization metrics on inventoried EC2 instances.
+
+USE VPC
+:   Specify if the target account is using EC2-VPC or EC2-Classic Platform. In almost all cases, VPC should be selected, and then select the target VPC from the synced available VPC’s list, or All VPC’s.
+
+#### Procedure
+
+The AWS cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+IMAGE TRANSFER STORE
+:   S3 bucket for Image transfers, required for migrations into AWS.
+
+EBS ENCRYPTION
+:   Enable or disable encryption of EBS Volumes
+
+COSTING KEY
+:   For Gov Cloud pricing only, key for standard managing cost account
+
+COSTING SECRET
+:   For Gov Cloud pricing only, secret for standard managing cost account
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+KMS KEY ID
+:   For specify an AWS KMS key for encrypting EBS Volumes when volume encryption is enabled
+
+## Provisioning and Keypairs
+
+During provisioning, users do not need to create or select a keypair as you would do when provisioning directly from the AWS console. If needed, HPE Morpheus Enterprise will create an AWS keypair without input from the user. In the AWS console and in the HPE Morpheus Enterprise Keypairs Section (Infrastructure > Trust > Key Pairs) you will see these keypairs listed. HPE Morpheus Enterprise will also inventory other keypairs which are created in your integrated AWS clouds and these will be listed out in the HPE Morpheus Enterprise Keypairs section.
+
+These created keypairs are not accessible to the user as you do not see them at creation time and they are encrypted as stored in the HPE Morpheus Enterprise database. To have access to the Instance after provisioning, the user should have his or her user created during provisioning. This is done by creating a Linux user in HPE Morpheus Enterprise [User Settings](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html#linux-settings) and associating a keypair with the user. If you don’t currently have a keypair to use, HPE Morpheus Enterprise can generate one for you in the Keypairs section.
+
+![../../../_images/userKeypair.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A382092A-E8E1-4130-835B-6700A0619EDB-high.png)
+
+With your user set in HPE Morpheus Enterprise User Settings, ensure that your user is being created during Instance provisioning. On the CONFIGURE tab of the Instance provisioning wizard, mark the “CREATE YOUR USER” box. This is normally checked by default if a user is configured in HPE Morpheus Enterprise User Settings but you can confirm that here.
+
+![../../../_images/createUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5670B0FB-6FFF-4925-860C-C8117AA15A1C-high.png)
+
+It’s worth noting that adding your user to the provisioned workload does not replace the keypair used by HPE Morpheus Enterprise during provisioning. Instead it adds the public key for your user to the authorized keys file on the workload which allows you to access it. You can confirm this by catting out the authorized key file on any of your HPE Morpheus Enterprise-provisioned workloads (~/.ssh/authorized\_keys). You will at least see two keys, one for the HPE Morpheus Enterprise service user and one for your own user.
+
+NOTE
+
+In general it should not cause problems if HPE Morpheus Enterprise-generated keypairs are deleted from the AWS console or from the HPE Morpheus Enterprise keypairs section. You would not lose console access to the VM. If needed, however, HPE Morpheus Enterprise will create more keypairs and there is currently no functionality to automatically remove these keypairs. They can be safely ignored, generally speaking there is no need to manually delete them.
+
+## Enhanced Invoice Costing Configuration
+
+AWS cloud integrations in HPE Morpheus Enterprise will sync highly-granular costing data through the use of AWS Costing & Utilization Reports (CUR). If desired, users can turn on costing in the HPE Morpheus Enterprise Cloud configuration without linking a CUR to use AWS Cost Explorer instead. HPE Morpheus Enterprise version 4.2.3 also simplified the way CUR reports can be selected or created in order to sync costing data. The section below discusses setting up enhanced costing through CUR reports both in 4.2.3 and versions prior. For additional details on setting up costing with AWS GovCloud, see the next section.
+
+NOTE
+
+Even with a costing report configured in the Cloud integration as described below, the COSTING value must also be set to “Costing and Reservations” in order for enhanced invoice data to be brought into HPE Morpheus Enterprise. Confirm this setting by editing the Amazon Cloud integration, and checking the COSTING value in the Advanced Options panel before continuing.
+
+**v4.2.3 and Above**
+
+In HPE Morpheus Enterprise 4.2.3+, edit the Amazon cloud integration or create a new Amazon Cloud to get started. On the Create/Edit Cloud modal, open the advanced options section. The relevant fields for configuring invoice costing are shown below:
+
+![../../../_images/0billingFields.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6603376C-13FF-4A08-BCE0-30DD28A95B76-high.png)
+
+In the example case above, a new report and a new S3 bucket are created but HPE Morpheus Enterprise will also sync in buckets and reports that meet the required parameters if they already exist. For reports to be synced they must meet the requirements listed below:
+
+- Hourly time granularity
+- Include resource IDs
+- GZIP compression
+- CSV format
+
+If you don’t currently have a report meeting those criteria, you can create one by selecting “New Report” from the REPORT NAME dropdown menu. A new S3 bucket can be created in similar fashion if needed. You may also want to review the section below on configuration for HPE Morpheus Enterprise 4.2.2 and below to note policies that will be applied to your selected bucket and Cost Explorer permissions required for the AWS cloud user associated with the HPE Morpheus Enterprise Cloud integration.
+
+In the end, the following fields must be filled in order to complete the process:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+Using the HPE Morpheus Enterprise interface to create a CUR, and optionally a new S3 bucket, the IAM user requires permissions in AWS to be successful. By default, only the root user will have access to billing (including CUR), but billing can be enabled for IAM users following Amazon’s documentation for [Activating IAM Access](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/control-access-billing.html). Once IAM access is activated, policies need to be assigned to the user being configured on the cloud in HPE Morpheus Enterprise. If the user is an administrator of the AWS account, no additional policies are needed. Below are some example policies needed for different scenarios:
+
+Creating a new CUR and new S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:PutBucketPolicy",  
+              "s3:CreateBucket",  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Creating a new CUR and using an existing S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Using an existing CUR
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+IMPORTANT
+
+The user configured on the cloud will need access to the objects in the S3 bucket configured on the CUR. If creating the CUR via the HPE Morpheus Enterprise UI, this should be done automatically. If an existing CUR report or existing S3 bucket was selected, ensure the user has permissions to access the objects in the configured S3 bucket. Alternatively, the **COSTING KEY** and **COSTING SECRET** can be used to configure a different user that has access to the S3 bucket.
+
+**v4.2.2 and Below**
+
+Begin by logging into the [AWS Billing Console](https://console.aws.amazon.com/billing/home?#/), then click Create report.
+
+![../../../_images/1billingConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6DE8607B-F2EC-42DB-ABD4-570B5A337D97-high.png)
+
+Include a name for your report and mark the box to “Include resource IDs”. HPE Morpheus Enterprise uses these resource IDs to map costs to various resources. Click Next.
+
+![../../../_images/2reportConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BAA21B68-8956-49FD-958B-97FC16160E26-high.png)
+
+On the following page, begin by identifying an S3 bucket to house reports. Click Configure near the top of the page and select an existing bucket or create a new one.
+
+![../../../_images/4chooseBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7D2040F4-3B7E-4CE5-82C7-2373F73C9F42-high.png)
+
+After identifying the bucket, you must mark the box to accept the default policy being applied to the bucket. Click Save.
+
+![../../../_images/5confirmPolicy.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5BDEF27D-8DC9-4554-A3D0-DAC2B41DEEEE-high.png)
+
+The default policy applied to the bucket is below:
+
+```
+```
+{  
+  "Version": "2008-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:GetBucketAcl",  
+        "s3:GetBucketPolicy"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name"  
+    },  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:PutObject"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name/*"  
+    }  
+  ]  
+}
+```
+```
+
+After choosing a bucket, accepting the default policy, and saving the change, you’re brought back to the report delivery page. By default, CUR reports are saved to a folder at the path `my-report-name/date-folder`. If this bucket already contains CUR reports, you may want to specify a prefix path in the “Report path prefix” field. Outside of this field, use the default values as shown in the screenshot below, then click Next.
+
+![../../../_images/6completeDelivery.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DBCE8764-455B-450D-9C77-F16E527402D5-high.png)
+
+On the following page, make your final review and click Review and Complete. Following this, you will see your newly configured report in the list of CUR report(s).
+
+In addition, the AWS cloud user associated with the integration in HPE Morpheus Enterprise needs IAM policy permission to access Cost Explorer. Attach a policy like the one below to this cloud user:
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Action": [  
+        "ce:DescribeReportDefinitions",  
+        "ce:DescribeCostCategoryDefinition",  
+        "ce:ListCostCategoryDefinitions"  
+      ],  
+      "Resource": [  
+        "*"  
+      ]  
+    }  
+  ]  
+}
+```
+```
+
+NOTE
+
+If the Cost Explorer permissions are granted at the master account level, the user will see all costs for each member account; if granted at the member account, only the costs for that member account are available.
+
+With the AWS console configuration steps complete, we can move back into HPE Morpheus Enterprise. Keep in mind it is only necessary to set up one AWS cloud for Costing since we process all records in the CUR report.
+
+Once back in HPE Morpheus Enterprise, add or edit the relevant AWS cloud integration (Infrastructure > Clouds > + ADD OR click the pencil icon in the row for the chosen AWS integration). Expand the Advanced Options drawer and complete the following fields:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+![../../../_images/7morphConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C5CA9E0D-35CE-4209-BAD7-B2091E1795EC-high.png)
+
+Save changes to your cloud integration.
+
+IMPORTANT
+
+It may take as long as one hour for HPE Morpheus Enterprise to process the next CUR report.
+
+### Global (Costing Aggregator Only) (v5.5.1+)
+
+Costing can be created for specific clouds individually, following the steps previously mentioned. If the same account is added multiple times, using different regions, the same CUR file is available to be selected (if the configured user has access). However, this can become a tedious process in needing to configure the CUR on each cloud added to HPE Morpheus Enterprise. However, HPE Morpheus Enterprise has a region of Global (Costing Aggregator Only), which can be chosen at the time of adding a cloud. This region is not designed for deploying workloads, it is here primarily for syncing costs. This means that the AWS account added as a cloud in HPE Morpheus Enterprise as a Global region can sync the cost for all the other regions of the same account added as clouds into HPE Morpheus Enterprise. When using AWS Organizations, if the AWS account added as a global region is the management account (formerly known as master account) and consolidated billing is enabled, costs for **all** accounts can be sync’d using the Global region. This means when any AWS and/or regions in the organization are added as clouds in HPE Morpheus Enterprise, the appropriate costs are applied to them automatically. It does require that **Costing** is enabled on the cloud to see the costs but a Costing Report does not need to be chosen. This enables the use of one cloud added as Global to sync all costs and apply to all AWS clouds added in HPE Morpheus Enterprise. Additionally, some costs in AWS are not region specific, for example the Global and No Region regions. These costs do not apply to the regions of the clouds added in HPE Morpheus Enterprise. With the Global region added as a cloud in HPE Morpheus Enterprise, you would be able to see these costs that are applicable to your accounts.
+
+## Costing and AWS GovCloud
+
+### About this task
+
+AWS GovCloud delivers Amazon public cloud infrastructure and features in a way that complies with U.S. government standards for security. GovCloud accounts are applied for and must be associated with a pre-existing standard AWS account and the usage and billing data for the GovCloud account is rolled up into that of the standard AWS account. For that reason, Amazon recommends creating a new standard account solely to house the GovCloud account if usage and billing must be tracked separately.
+
+Since GovCloud accounts do not have access to billing data directly, HPE Morpheus Enterprise must be able to access it through the associated standard account. You could do this by creating the HPE Morpheus Enterprise cloud integration through the standard account itself or by integrating the GovCloud account and supplying an Access Key and Secret Key for the standard account when configuring costing. When needed, add the additional credentials for the standard commercial account as described below:
+
+### Procedure
+
+1. Add a new AWS Cloud or edit an existing one
+2. Expand the Advanced Options section
+3. Complete the following fields in addition to other required fields needed to set up costing as described in the previous section: 
+
+   - COSTING KEY: The AWS Key ID for an IAM user with sufficient access who is associated with the standard commercial account
+   - COSTING SECRET: The AWS Secret Key for an IAM user with sufficient access who is associated with the standard commercial account
+   - LINKED ACCOUNT ID: The AWS account number for the standard commercial account in which the IAM user referenced in the prior bullets resides
+4. Save the changes to the AWS Cloud integration
+
+### Results
+
+When credentials are configured correctly, you will be able to select an existing Costing and Usage Report (CUR) from the appropriate S3 bucket if it already exists. If not, you can create one directly from the add/edit AWS Cloud modal in HPE Morpheus Enterprise.
+
+![../../../_images/8govcloudCosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AC3216FF-1BBA-4E49-808F-3B612BC88276-high.png)
+
+## AWS Reserved Instances and Savings Plans
+
+Amazon AWS public cloud offers Reserved Instances (RI) and Savings Plans, which allow organizations with consistent use patterns to reduce cloud spend significantly. HPE Morpheus Enterprise analyzes AWS cloud usage and spend, which allows it to make intelligent recommendations that can lead to significant savings. This data can be reviewed in the Reservation Recommendations and Savings Plan Recommendations tables on any AWS Cloud detail page (Infrastructure > Clouds > Selected Amazon Cloud).
+
+Savings Plans potentially offer greater than 70% savings in exchange for a commitment to consistent usage levels for a 1- or 3-year term. HPE Morpheus Enterprise provides Savings Plan guidance based on learned analytics; allowing you to analyze Savings Plans based on different term commitments and upfront costs to choose the best savings plan.
+
+![../../../_images/savingsPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ED40B92B-4283-4FD5-9536-06034CC07CC0-high.png)
+
+Reserved Instances (RI) provide a discounted hourly rate and optional capacity reservation for EC2 instances. AWS billing automatically applies your RI-discounted rate when the attributes of EC2 instance usage match attributes of an active RI. HPE Morpheus Enterprise provides RI guidance based on learned analytics.
+
+![../../../_images/ri.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A93A0997-98E0-4177-91AF-1CC07D579581-high.png)
+
+To retrieve Reserved Instances and Savings Plans data, the user configured on the cloud will require access to **Cost Explorer**. Below is an example IAM policy with Cost Explorer access:
+
+### Cost Explorer Policy
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "ce:*"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+## AWS IAM Permissions
+
+Below are the AWS IAM Permissions required for HPE Morpheus Enterprise services.
+
+### autoscaling
+
+```
+```
+"autoscaling:AttachInstances",  
+"autoscaling:AttachLoadBalancerTargetGroups",  
+"autoscaling:CreateAutoScalingGroup",  
+"autoscaling:DeleteAutoScalingGroup",  
+"autoscaling:DeleteLaunchConfiguration",  
+"autoscaling:DeletePolicy",  
+"autoscaling:DescribeAutoScalingGroups",  
+"autoscaling:DescribeLaunchConfigurations",  
+"autoscaling:DescribeLoadBalancers",  
+"autoscaling:DescribePolicies",  
+"autoscaling:DetachInstances",  
+"autoscaling:PutScalingPolicy",  
+"autoscaling:UpdateAutoScalingGroup",
+```
+```
+
+### cloudformation
+
+```
+```
+"cloudformation:CreateStack",  
+"cloudformation:DeleteStack",  
+"cloudformation:DescribeStackEvents",  
+"cloudformation:DescribeStackResources",  
+"cloudformation:DescribeStacks",  
+"cloudformation:GetTemplate",  
+"cloudformation:UpdateStack",  
+"cloudformation:ValidateTemplate",
+```
+```
+
+### cloudwatch
+
+```
+```
+"cloudwatch:DeleteAlarms",  
+"cloudwatch:DescribeAlarms",  
+"cloudwatch:GetMetricStatistics",  
+"cloudwatch:PutMetricAlarm",
+```
+```
+
+### costexplorer
+
+```
+```
+"ce:*",
+```
+```
+
+### Cost and Usage Reports
+
+```
+```
+"cur:DescribeReportDefinitions",  
+"cur:PutReportDefinition",
+```
+```
+
+### ec2
+
+```
+```
+"ec2:AllocateAddress",  
+"ec2:AssignPrivateIpAddresses",  
+"ec2:AssociateAddress",  
+"ec2:AttachInternetGateway",  
+"ec2:AttachNetworkInterface",  
+"ec2:AttachVolume",  
+"ec2:AuthorizeSecurityGroupEgress",  
+"ec2:AuthorizeSecurityGroupIngress",  
+"ec2:CancelExportTask",  
+"ec2:CancelImportTask",  
+"ec2:CopyImage",  
+"ec2:CopySnapshot",  
+"ec2:CreateEgressOnlyInternetGateway",  
+"ec2:CreateImage",  
+"ec2:CreateInstanceExportTask",  
+"ec2:CreateInternetGateway",  
+"ec2:CreateKeyPair",  
+"ec2:CreateNatGateway",  
+"ec2:CreateNetworkAcl",  
+"ec2:CreateNetworkAclEntry",  
+"ec2:CreateNetworkInterface",  
+"ec2:CreateRoute",  
+"ec2:CreateSecurityGroup",  
+"ec2:CreateSnapshot",  
+"ec2:CreateSubnet",  
+"ec2:CreateTags",  
+"ec2:CreateVolume",  
+"ec2:CreateVpc",  
+"ec2:DeleteEgressOnlyInternetGateway",  
+"ec2:DeleteInternetGateway",  
+"ec2:DeleteKeyPair",  
+"ec2:DeleteNatGateway",  
+"ec2:DeleteNetworkAcl",  
+"ec2:DeleteNetworkAclEntry",  
+"ec2:DeleteNetworkInterface",  
+"ec2:DeleteRoute",  
+"ec2:DeleteSecurityGroup",  
+"ec2:DeleteSnapshot",  
+"ec2:DeleteSubnet",  
+"ec2:DeleteTags",  
+"ec2:DeleteVolume",  
+"ec2:DeleteVpc",  
+"ec2:DeregisterImage",  
+"ec2:DescribeAccountAttributes",  
+"ec2:DescribeAddresses",  
+"ec2:DescribeAvailabilityZones",  
+"ec2:DescribeClassicLinkInstances",  
+"ec2:DescribeClientVpnConnections",  
+"ec2:DescribeClientVpnEndpoints",  
+"ec2:DescribeConversionTasks",  
+"ec2:DescribeEgressOnlyInternetGateways",  
+"ec2:DescribeExportTasks",  
+"ec2:DescribeImageAttribute",  
+"ec2:DescribeImages",  
+"ec2:DescribeImportImageTasks",  
+"ec2:DescribeImportSnapshotTasks",  
+"ec2:DescribeInstances",  
+"ec2:DescribeInstanceStatus",  
+"ec2:DescribeInstanceTypes",  
+"ec2:DescribeInternetGateways",  
+"ec2:DescribeKeyPairs",  
+"ec2:DescribeNatGateways",  
+"ec2:DescribeNetworkAcls",  
+"ec2:DescribeNetworkInterfaceAttribute",  
+"ec2:DescribeNetworkInterfaces",  
+"ec2:DescribeRegions",  
+"ec2:DescribeRouteTables",  
+"ec2:DescribeSecurityGroupReferences",  
+"ec2:DescribeSecurityGroups",  
+"ec2:DescribeSnapshotAttribute",  
+"ec2:DescribeSnapshots",  
+"ec2:DescribeStaleSecurityGroups",  
+"ec2:DescribeSubnets",  
+"ec2:DescribeTags",  
+"ec2:DescribeTransitGateways",  
+"ec2:DescribeTransitGatewayVpcAttachments",  
+"ec2:DescribeVolumeAttribute",  
+"ec2:DescribeVolumes",  
+"ec2:DescribeVolumeStatus",  
+"ec2:DescribeVpcAttribute",  
+"ec2:DescribeVpcClassicLink",  
+"ec2:DescribeVpcClassicLinkDnsSupport",  
+"ec2:DescribeVpcEndpoints",  
+"ec2:DescribeVpcEndpointServices",  
+"ec2:DescribeVpcPeeringConnections",  
+"ec2:DescribeVpcs",  
+"ec2:DescribeVpnGateways",  
+"ec2:DetachInternetGateway",  
+"ec2:DetachNetworkInterface",  
+"ec2:DetachVolume",  
+"ec2:DisassociateAddress",  
+"ec2:GetPasswordData",  
+"ec2:ImportImage",  
+"ec2:ImportInstance",  
+"ec2:ImportKeyPair",  
+"ec2:ImportSnapshot",  
+"ec2:ImportVolume",  
+"ec2:ModifyImageAttribute",  
+"ec2:ModifyInstanceAttribute",  
+"ec2:ModifyNetworkInterfaceAttribute",  
+"ec2:ModifySnapshotAttribute",  
+"ec2:ModifySubnetAttribute",  
+"ec2:ModifyVolumeAttribute",  
+"ec2:RebootInstances",  
+"ec2:RegisterImage",  
+"ec2:ReleaseAddress",  
+"ec2:ReplaceNetworkAclAssociation",  
+"ec2:ReplaceNetworkAclEntry",  
+"ec2:ResetImageAttribute",  
+"ec2:ResetInstanceAttribute",  
+"ec2:ResetNetworkInterfaceAttribute",  
+"ec2:ResetSnapshotAttribute",  
+"ec2:RevokeSecurityGroupEgress",  
+"ec2:RevokeSecurityGroupIngress",  
+"ec2:RunInstances",  
+"ec2:StartInstances",  
+"ec2:StopInstances",  
+"ec2:TerminateInstances",  
+"ec2:UnassignPrivateIpAddresses",  
+"ec2:UpdateSecurityGroupRuleDescriptionsEgress",
+```
+```
+
+### eks
+
+```
+```
+"eks:*",
+```
+```
+
+### elasticloadbalancing
+
+```
+```
+"elasticloadbalancing:AddTags",  
+"elasticloadbalancing:ApplySecurityGroupsToLoadBalancer",  
+"elasticloadbalancing:AttachLoadBalancerToSubnets",  
+"elasticloadbalancing:CreateListener",  
+"elasticloadbalancing:CreateLoadBalancer",  
+"elasticloadbalancing:CreateRule",  
+"elasticloadbalancing:CreateTargetGroup",  
+"elasticloadbalancing:DeleteListener",  
+"elasticloadbalancing:DeleteLoadBalancer",  
+"elasticloadbalancing:DeleteRule",  
+"elasticloadbalancing:DeleteTargetGroup",  
+"elasticloadbalancing:DescribeLoadBalancers",  
+"elasticloadbalancing:DescribeRules",  
+"elasticloadbalancing:DescribeTargetGroups",  
+"elasticloadbalancing:ModifyListener",  
+"elasticloadbalancing:ModifyTargetGroupAttributes",  
+"elasticloadbalancing:RegisterTargets",  
+"elasticloadbalancing:SetSecurityGroups",  
+"elasticloadbalancing:SetSubnets",
+```
+```
+
+### elasticsearch
+
+```
+```
+"es:DescribeElasticsearchDomains",  
+"es:ListDomainNames",
+```
+```
+
+### iam
+
+```
+```
+"iam:ListGroups",  
+"iam:ListInstanceProfiles",  
+"iam:ListRoles",
+```
+```
+
+### kms
+
+```
+```
+"kms:Decrypt",  
+"kms:GenerateDataKey",
+```
+```
+
+### rds
+
+```
+```
+"rds:AddRoleToDBCluster",  
+"rds:AddTagsToResource",  
+"rds:ApplyPendingMaintenanceAction",  
+"rds:AuthorizeDBSecurityGroupIngress",  
+"rds:CopyDBClusterSnapshot",  
+"rds:CopyDBParameterGroup",  
+"rds:CopyDBSnapshot",  
+"rds:CreateDBCluster",  
+"rds:CreateDBClusterSnapshot",  
+"rds:CreateDBInstance",  
+"rds:CreateDBInstanceReadReplica",  
+"rds:CreateDBSecurityGroup",  
+"rds:CreateDBSnapshot",  
+"rds:DeleteDBCluster",  
+"rds:DeleteDBInstance",  
+"rds:DeleteDBSecurityGroup",  
+"rds:DeleteDBSnapshot",  
+"rds:DescribeAccountAttributes",  
+"rds:DescribeCertificates",  
+"rds:DescribeDBClusterParameterGroups",  
+"rds:DescribeDBClusterParameters",  
+"rds:DescribeDBClusters",  
+"rds:DescribeDBClusterSnapshotAttributes",  
+"rds:DescribeDBClusterSnapshots",  
+"rds:DescribeDBEngineVersions",  
+"rds:DescribeDBInstances",  
+"rds:DescribeDBLogFiles",  
+"rds:DescribeDBParameterGroups",  
+"rds:DescribeDBParameters",  
+"rds:DescribeDBSecurityGroups",  
+"rds:DescribeDBSnapshotAttributes",  
+"rds:DescribeDBSnapshots",  
+"rds:DescribeDBSubnetGroups",  
+"rds:DescribeEngineDefaultClusterParameters",  
+"rds:DescribeEngineDefaultParameters",  
+"rds:DescribeEventCategories",  
+"rds:DescribeEvents",  
+"rds:DescribeOptionGroupOptions",  
+"rds:DescribeOptionGroups",  
+"rds:DescribeOrderableDBInstanceOptions",  
+"rds:ListTagsForResource",  
+"rds:ModifyDBCluster",  
+"rds:ModifyDBClusterParameterGroup",  
+"rds:ModifyDBClusterSnapshotAttribute",  
+"rds:ModifyDBInstance",  
+"rds:ModifyDBParameterGroup",  
+"rds:ModifyDBSnapshotAttribute",  
+"rds:PromoteReadReplica",  
+"rds:RebootDBInstance",  
+"rds:RemoveTagsFromResource",  
+"rds:RestoreDBClusterFromSnapshot",  
+"rds:RestoreDBClusterToPointInTime",  
+"rds:RestoreDBInstanceFromDBSnapshot",  
+"rds:RestoreDBInstanceToPointInTime",  
+"rds:RevokeDBSecurityGroupIngress",  
+"rds:StartDBInstance",  
+"rds:StopDBInstance",
+```
+```
+
+### route53
+
+```
+```
+"route53:ChangeResourceRecordSets",  
+"route53:GetHostedZone",  
+"route53:ListHostedZones",  
+"route53:ListResourceRecordSets",
+```
+```
+
+### s3
+
+```
+```
+"s3:AbortMultipartUpload",  
+"s3:CreateBucket",  
+"s3:DeleteBucket",  
+"s3:DeleteObject",  
+"s3:DeleteObjectVersion",  
+"s3:GetBucketLocation",  
+"s3:GetBucketPolicy",  
+"s3:GetObject",  
+"s3:GetObjectVersion",  
+"s3:ListAllMyBuckets",  
+"s3:ListBucket",  
+"s3:ListBucketMultipartUploads",  
+"s3:ListBucketVersions",  
+"s3:ListMultipartUploadParts",  
+"s3:PutBucketPolicy",  
+"s3:PutObject",
+```
+```
+
+### Systems Manager
+
+```
+```
+"ssm:GetParameters",
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json b/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
new file mode 100644
index 0000000..3bb8f25
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+  "title": "Cannot Login",
+  "ordinal": 348,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html",
+  "topic_cluster": {
+    "clustering_title": "Cannot Login",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md b/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
new file mode 100644
index 0000000..d8cc326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
@@ -0,0 +1,34 @@
+# Cannot Login
+
+## Forgot password
+
+If a user forgets their password, they can use the FORGOT PASSWORD? link on the login page. They can then enter their username or email address to send a reset password email to the email address defined on the user.
+
+If the default or user added SMTP server is not functioning or blocked, a System Admin user can impersonate that user and update their password.
+
+If the System Admin user password needs to be reset and the default or user added SMTP server is not functioning or blocked, please contact Morpheus support for assistance.
+
+## Sub-Tenant user cannot login after 3.4.0 upgrade
+
+HPE Morpheus Enterprise v3.4.0 added support for all subtenant users to login via the main tenant url using subtenant id or subdomain prefix, ie `tenantId\username` or `subdomain\username`.
+
+NOTE
+
+Tenant subdomains can be defined by editing Tenant settings and updating the SUBDOMAIN field.
+
+IMPORTANT
+
+Subtenant local users will no longer be able to login from main login url without using their subtenant id or subdomain prefix.
+
+The login requirements were added in v3.4.0 to allow subtenant users with identity source integration generated user accounts to be able to login to the master tenant, gain API and CLI access, and remove the requirement for usernames to be unique across all tenants.
+
+Previously subtenant users that had local/morpheus generated user accounts could login to their tenant via the master tenant url, while subtenant users that had identity source integration generated user accounts had to use the subtenant specific login url.
+
+In v3.4.0+ all subtenant users can login via the master tenant url by specifying their tenant id or subdomain prefix, `\`, then username. Subtenants can still use the tenant specific login url as well.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `acme` and tenant id `58`. When logging in from the main login url, I now need to enter in: `acme\subuser` and the password. Alternatively the tenant ID can be used, ie `58\subuser`
+
+## Active Directory user suddenly cannot Login
+
+In HPE Morpheus Enterprise v3.4.0 and prior, OU changes in Active Directory can disable logins for AD users who had previously authenticated/have existing user accounts in HPE Morpheus Enterprise. If an Active Directory user cannot login to HPE Morpheus Enterprise after their OU was changed in AD, please contact Morpheus support for a resolution. The OU association for the user(s) can also be manually updated in the database. This issue is resolved in HPE Morpheus Enterprise versions 3.4.1 and higher.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json b/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
new file mode 100644
index 0000000..0b364d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+  "title": "Execute Scheduling",
+  "ordinal": 124,
+  "parent_title": "Automation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md b/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
new file mode 100644
index 0000000..32fac17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
@@ -0,0 +1,36 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for Jobs, including Task, Workflow and Backup Jobs. Jobs, which are discussed in greater detail in [another section](https://docs.morpheusdata.com/en/4.2.0/provisioning/jobs/jobs.html#jobs) of HPE Morpheus Enterprise docs, combine either a Task or Workflow with an Execute Schedule to run the selected Task or Workflow at the needed time. Backup Jobs are a special type of Job configured in the Backups section which also use Execute Schedules to time backup runs as needed.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). HPE Morpheus Enterprise execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+## Create Execution Schedules
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that references the time interval is often helpful
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+VISIBILITY
+:   Master Tenant administrators may share Execute Schedules with Subtenants by setting the visibility to Public
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json b/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
new file mode 100644
index 0000000..766a175
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+  "title": "Network Connectivity",
+  "ordinal": 6,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Connectivity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md b/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
new file mode 100644
index 0000000..b5f60e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
@@ -0,0 +1,7 @@
+# Network Connectivity
+
+HPE Morpheus Enterprise primarily operates via communication with its Agent that is installed on all managed VMs or docker hosts. This is a lightweight agent responsible for aggregating logs and stats and sending them back to the client with minimal network traffic overhead. It also is capable of processing instructions related to provisioning and deployments instigated by the appliance server.
+
+The HPE Morpheus Enterprise Agent exists for both Linux and Windows-based platforms and opens NO ports on the guest operating system. Instead it makes an outbound SSL (HTTPS/WSS) connection to the appliance server. This is what is known as the `appliance url` during configuration (in Administration > Settings). When the Agent is started it automatically makes this connection and securely authenticates. Therefore, it is necessary for all VMs and docker based hosts that are managed by HPE Morpheus Enterprise to be able to reach the appliance server IP on port 443.
+
+HPE Morpheus Enterprise has numerous methods to execute Agent installation, including zero open port methods.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json b/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
new file mode 100644
index 0000000..25e1ce7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+  "title": "Overview",
+  "ordinal": 274,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md b/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
new file mode 100644
index 0000000..a6c325a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
@@ -0,0 +1,11 @@
+# Overview
+
+A Tenant in HPE Morpheus Enterprise is an isolated environment with unique users and workloads. The Master Tenant is the default Tenant in HPE Morpheus Enterprise, created upon installation. All other Tenants outside of the Master Tenants are Subtenants. These terms are useful in differentiating the Master Tenant (which has a few special privileges) from Subtenants for the sake of discussion but within the product, all Tenants are known simply as Tenants.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The first layer of new Tenants (subtenants) is created from the Master Tenant. Created Tenants may have Tenants of their own
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants. Subtenants may only assign resources to its first layer of children Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant from a higher level Tenant
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json b/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
new file mode 100644
index 0000000..62e70a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+  "title": "Remote Storage",
+  "ordinal": 455,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md b/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
new file mode 100644
index 0000000..c001297
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
@@ -0,0 +1,14 @@
+# Remote Storage
+
+Table 1. Remote Storage
+
+        | S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Failure to Integrate HPE Alletra MP Plugin | Issues during plugin loading or integration of the HPE Alletra MP plugin in the Morpheus Enterprise environment. | - Confirm that the plugin `.jar` file is properly loaded as per section 5.2 “Adding HPE BMaaS Integration”. - Check if the correct credentials and URL for the storage array are used. | - **Plugin Logs**: Look for errors during plugin loading. - **System Logs**: Check for authentication or configuration failures. | - Ensure compatibility between the plugin version and Morpheus Enterprise. - Network/firewall issues may prevent communication with the storage array. |
+| 2 | Storage Server Creation Failure | Failure when adding a new storage server (URL, credentials, or type mismatch). | - Verify the URL and credentials for accessing the storage array. - Ensure the correct type (“HPE Alletra Block Storage HVM”) is selected. | - **Storage Server Logs**: Check for error messages related to server creation (authentication issues, network problems). | - An incorrect URL or credentials can prevent server creation. - Make sure the storage server is accessible and reachable from the Morpheus interface. |
+| 3 | Datastore Creation Failure | Issues while creating a datastore, such as selecting an incorrect storage server, or specifying incompatible resource pools or protocols. | - Verify that the storage server was created successfully. - Ensure correct datastore type and resource pool selection. - Ensure "FC" is selected for protocol. | - **Datastore Logs**: Check for errors when trying to create the datastore (incorrect type, wrong resource pool). | - Mismatched storage configuration or resource pool selection can lead to datastore creation failures. - Confirm network configurations for FC protocol. |
+| 4 | Volume Creation Issues | Errors when creating volumes, including failure to assign the correct size, volume type (replicated/unreplicated), or datastore. | - Ensure the storage server is selected correctly. - Verify the volume size and type are correct. - Confirm the datastore is properly associated. | - **Volume Logs**: Errors related to volume creation (incorrect parameters, missing datastore). | - Volume size can only be increased - check the requirements. - Ensure correct replication type (CPP/APP) based on the storage array setup. |
+| 5 | Volume Deletion Failure | Unable to delete volumes due to them being attached to servers or due to incorrect permission settings. | - Confirm the volume is detached from all servers. - Ensure you have the necessary permissions to delete the volume. | - **Volume Deletion Logs**: Look for errors related to detachment or permission issues during deletion. | - Volumes can only be deleted once detached. - Ensure no active processes are using the volume. |
+| 6 | Volume Resize Failure | Unable to resize a volume, typically due to a lack of rescan on the server OS or exceeding size limits. | - Confirm the server OS has rescanned the volume. - Ensure the new size does not exceed any system or storage limits. | - **Volume Resize Logs**: Look for errors when attempting to resize (e.g., "resize failed" messages). | - Resize operations are only allowed for volume increases, not reductions. - Ensure the OS is aware of the new size after the resize. |
+| 7 | Volume Consumption Issues During Provisioning | Difficulty attaching volumes during instance provisioning (shared/unshared, existing/new, replicated/unreplicated). | - Ensure the correct volume type (shared/unshared) is specified. - Verify replication settings (CPP/APP) are correct. - Check if the volume exists and is accessible. | - **Provisioning Logs**: Check for errors related to volume attachment (invalid volume, replication mismatch). | - Volumes must be properly configured before provisioning. - Shared volumes should be attached to all servers within the instance. |
+| 8 | FC Protocol Issues | Issues with FC protocol during volume creation or consumption (e.g., failed attachments or slow response). | - Check if the storage server and datastore are properly configured for FC. - Confirm FC switches and network paths are properly set up. | - **Fibre Channel Logs**: Look for errors indicating FC connectivity or protocol issues. | - FC issues may be related to network misconfigurations or cable/connectivity problems. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json b/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
new file mode 100644
index 0000000..5c6e4c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+  "title": "Jobs",
+  "ordinal": 90,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md b/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
new file mode 100644
index 0000000..bd27473
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
@@ -0,0 +1,12 @@
+# Jobs
+
+Jobs are for scheduled execution of Automation Tasks and Workflows. Jobs can be set to execute on a schedule, at one specific point in time, and/or execute manually (on-demand). Jobs are linked to existing Tasks or Workflows, and allow for custom configuration options. Jobs can be associated with Instances, Servers, or have no association, such as a job for an SSH task.
+
+Jobs allow for scheduled execution of nearly anything as Tasks Types include Bash, Powershell, HTTP/API, Ansible, Chef, Puppet, Groovy, Python, jRuby, Javascript, and library scripts and templates, which can be configured for resource, remote, or local execution targets. If you need something to execute on a schedule, HPE Morpheus Enterprise Jobs can deliver.
+
+Jobs are configured in the `JOBS` tab, and the `JOB EXECUTIONS` tab contains Job execution history with result output.
+
+**Subtopics**  
+
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html)**
+- **[Job Executions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json b/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
new file mode 100644
index 0000000..eda2916
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+  "title": "3Par",
+  "ordinal": 518,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html",
+  "topic_cluster": {
+    "clustering_title": "3Par",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md b/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
new file mode 100644
index 0000000..16769ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
@@ -0,0 +1,32 @@
+# 3Par
+
+## Adding 3Par Storage Server
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json b/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
new file mode 100644
index 0000000..67c0ae7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+  "title": "Core Functionality",
+  "ordinal": 40,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html",
+  "topic_cluster": {
+    "clustering_title": "Core Functionality",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md b/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
new file mode 100644
index 0000000..5d033b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
@@ -0,0 +1,8 @@
+# Core Functionality
+
+**Subtopics**  
+
+- **[Morpheus Discovery](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html)**
+- **[Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html)**
+- **[VMware Support Statement](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..6199a71
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 373,
+  "parent_title": "Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..3d79f12
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,19 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333_2.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html)**
+- **[Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html)**
+- **[DNS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html)**
+- **[Identity Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html)**
+- **[ITSM](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB_2.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_3.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
+- **[Supported Integration Versions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json b/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
new file mode 100644
index 0000000..2751abf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+  "title": "MySQL Too many connections error",
+  "ordinal": 351,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html",
+  "topic_cluster": {
+    "clustering_title": "MySQL Too many connections error",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md b/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
new file mode 100644
index 0000000..f96a623
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
@@ -0,0 +1,57 @@
+# MySQL Too many connections error
+
+If you see the following error in the HPE Morpheus Enterprise UI logs:
+
+```
+```
+SqlExceptionHelper - Data source rejected establishment of connection,  message from server: "Too many connections"
+```
+```
+
+it means the number connections between HPE Morpheus Enterprise application and mysql have reached the max\_connections limit set in mysql (default is 151), or the max\_active setting, which limits the number of connections on the HPE Morpheus Enterprise end (default is 150), and the limit needs to be raised, either in HPE Morpheus Enterprise or mysql, or both depending on the number of connections and configuration.
+
+NOTE
+
+The max\_connections setting in mysql and the maximum used connections between an app node and mysql can be viewed in the HPE Morpheus Enterprise ui in the Administration - Health section under Database.
+
+IMPORTANT
+
+In Single HPE Morpheus Enterprise app node configurations, the `max_active` setting on the app node must be less than the `max_connections` setting in mysql.
+
+IMPORTANT
+
+In HA configurations, the `max_active` setting is per app node, and the `max_connections` setting in mysql must be greater than all app nodes `max_active` values combined, ie `(max_active` \* $number\_of\_app\_nodes) <= max\_connections``.
+
+## HPE Morpheus Enterprise `max_active` setting
+
+Edit `/etc/morpheus/morpheus.rb` and add `mysql[‘max_active’] = $value` replacing `$value` with desired desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql. For example, to set max\_active at 150:
+
+```
+```
+mysql[‘max_active’] = 150
+```
+```
+
+Replacing 100 with the desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql.
+
+Run `morpheus-ctl reconfigure` for the setting to be applied. Reconfigure will not restart the ui unless additional ram has been added to the appliance host since the previous reconfigure. To edit the max\_active without a reconfigure, update the `max_active` setting in `/opt/morpheus/conf/application.yml`. Please note the default setting of 150 will be applied upon the next reconfigure unless `max_active` is defined as instructed above in the `morpheus.rb` file.
+
+## mysql `max_connections` setting
+
+IMPORTANT
+
+Customers are responsible for configuring and maintaining external databases used by HPE Morpheus Enterprise. This explains how to set the `max_connections` setting, but the value for the setting needs to be established by a customers qualified db admin.
+
+In mysql prompt,
+
+run `mysql> SET GLOBAL max_connections = $value;`
+
+This will immediately write the variable, however it is only a temporary setting that will be overwritten upon restart of the mysql service.
+
+To persist the `max_connections` setting, edit my.cnf, and add `max_connections = $value` replacing `$value` with desired value, ie to set max\_connections at 300 in in my.cnf, add:
+
+```
+```
+max_connections = 300
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.json b/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
new file mode 100644
index 0000000..79a6568
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+  "title": "Role Types",
+  "ordinal": 293,
+  "parent_title": "Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html",
+  "topic_cluster": {
+    "clustering_title": "Role Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.md b/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
new file mode 100644
index 0000000..be60dc5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
@@ -0,0 +1,31 @@
+# Role Types
+
+## Tenant Roles
+
+A Tenant based role (formerly called an Account based role) is used to ensure access control enforcement across an entire tenant with many sub-users. This allows the subtenant to manage their own set of internal user based roles without worrying master tenant involvement in setting them up. The master tenant is the only tenant able to create and manage these types of roles. When editing a Tenant, a singular tenant role can be assigned to the account. Users within the tenant can be assigned roles but those user based roles will never be able to supersede the level of access granted by the tenant role. This allows a super administrator the ability to restrict access at the department or organization level without having to worry about per user access control within said tenant.
+
+Tenant roles also have an additional section not in User based roles related to Cloud Access. Cloud Access allows the master tenant the ability to assign cloud integration resources to specific subtenants or groups of subtenants. An example would be granting access to a specific VMware cluster only to a subset of tenants using the tenant based role control.
+
+## User Roles
+
+User roles can be created by any tenant given permission at the tenant role level. These allow tenants to manage their own sets of users and their levels of access. They also allow tenants to control which users have access to specific “Groups” for provisioning into within HPE Morpheus Enterprise. Groups are not cross tenant and therefore need to be controlled within the individual tenant in HPE Morpheus Enterprise.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within HPE Morpheus Enterprise. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+NOTE
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
+
+## Multi-Tenant User Role Lock
+
+As discussed above, Multi-Tenant User Roles are made available within all Subtenants and can be thought of as ‘canned’ user role sets provided to the Subtenant. Master Tenant administrators can prevent changes to these ‘canned’ user roles by marking the box labeled ‘MULTITENANT LOCKED’ when creating or editing the role. In addition to preventing Subtenant administrators from modifying permissions of the role copied down to their Subtenant, this option also ensures Master Tenant administrators can propagate new changes to that role. Modification of the role by the subtenant (if allowed) breaks the link back to the Master Tenant and the copy of the role within the Subtenant will become its own unlinked role.
+
+NOTE
+
+Multi-tenant role lock applies only to permission sets on the Features, Report Types, Personas and VDI Pools tabs. Permissions in other tabs (such as Groups, Instance Types, Blueprints or Catalog Item Types) tabs are not locked. Similarly, changes made to the role on these tabs in the master tenant are not synced down.
+
+## Editing User Roles in other Tenants
+
+Administrators in the Primary Tenant have the unique ability to edit feature permissions for User Roles that exist within other Tenants (Subtenants). In order to view the Roles within the Tenant, navigate to the Tenant detail page (Administration > Tenants) and select the Roles tab. Click the pencil (✎) icon to the right of a Role in the list to edit basic information, such as the name and description of the Role. Click on the name of the Role to view its complete permission set and edit the permissions if desired. This will update the feature access rights of users in the selected Tenant which have the Role.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json b/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
new file mode 100644
index 0000000..0367a64
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+  "title": "Azure Stack",
+  "ordinal": 390,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Stack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md b/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
new file mode 100644
index 0000000..46d1026
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
@@ -0,0 +1,300 @@
+# Azure Stack
+
+## Overview
+
+Azure Stack is Microsoft’s Azure Cloud for on-premises environments. Azure Stack contains the core Azure services, allowing organizations to take advantage of Azure’s offerings with the security, compliance, and financial benefits of hosting it in their own data-centers.
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Group Sync & Selection
+- Network Sync & Selection
+- Security Group Sync & Selection
+- Storage Account Sync & Selection
+- Marketplace Search and Provisioning
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Availability Set Support
+- Azure Load Balancers
+- Azure Storage
+- Docker Host Provisioning & Management
+- Service Plan Sync
+- Pricing Sync with markup options
+- Cost Estimator
+
+Combine these features with public Azure and HPE Morpheus Enterprise can provide a single pane of glass and self service portal for managing instances scattered across both Azure offerings.
+
+## Requirements
+
+### Azure Stack Accessibility
+
+By default, the Azure Stack management url’s are not accessible from an external network. Port mappings and DNS must be configured for communication between the HPE Morpheus Enterprise Appliance and Azure Stack.
+
+IMPORTANT
+
+In order to communicate with Azure Stack, HPE Morpheus Enterprise must be able to reach the internal Azure Stack network. The Azure Stack Portal needs to be exposed to the HPE Morpheus Enterprise Appliances’ network with corresponding entries added to DNS.
+
+One option to expose the Internal Azure Stack network to the HPE Morpheus Enterprise Appliances network is to use the `Expose-AzureStackPortal.ps1` powershell script from <https://gallery.technet.microsoft.com/scriptcenter/Expose-the-Azure-Stack-7ef68b19>. An Azure Stack Port Mapping Tool is also available.
+
+Below is a sample output from the script for reference:
+
+```
+```
+[Admin Portal] Created port mappings on 10.30.23.120 to 192.168.102.8  
+[Admin Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Admin Portal] DNS: 10.30.23.120 - adminportal.local.azurestack.external adminmanagement.local.azurestack.external  
+[Tenant Portal] Created port mappings on 10.30.23.121 to 192.168.102.10  
+[Tenant Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Tenant Portal] DNS: 10.30.23.121 - portal.local.azurestack.external management.local.azurestack.external  
+[Blob Storage] Created port mappings on 10.30.23.122 to 192.168.102.4  
+[Blob Storage] Ports: 80 443  
+[Blob Storage] DNS: 10.30.23.122  *.blob.local.azurestack.external  
+VERBOSE: DNS delegation/forwarding is optional, change the DNS records on MAS-DC01 manually (dnsmgmt.msc from Host).  
+[DNS Delegation] Created port mappings on 10.30.23.120 to 192.168.200.224  
+[DNS Delegation] Ports: 53 (TCP/UDP)  
+[DNS Delegation] DNS: local.azurestack.external NS 10.30.23.120  
+[DNS Delegation] Change records on MAS-DC01 manually `if` you plan to use DNS forwarding.  
+[DNS Delegation] Change records back to the original internal IPs before running this script again.  
+VERBOSE: App Service detected and external IPs specified, creating mappings.  
+[App Service API] Created port mappings on 10.30.23.123 to 192.168.102.17  
+[App Service API] Ports: 443  
+[App Service API] DNS: 10.30.23.123  api.appservice.local.azurestack.external  
+[App Service Apps] Created port mappings on 10.30.23.124 to 192.168.102.15  
+[App Service Apps] Ports: 80 443 21 990  
+[App Service Apps] DNS: 10.30.23.124  *.appservice.local.azurestack.external
+```
+```
+
+### Azure Stack Resources
+
+The following resources need to be created and configured inside Azure Stack for successful provisioning:
+
+- Resource Group(s)
+- Virtual Network(s)
+- Storage Account(s)
+- Network Security Group(s)
+
+  - Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389
+  - Outbound ports open to HPE Morpheus Enterprise Appliance: 80, 443
+
+NOTE
+
+Proper Network and Network Security Group configuration is required for HPE Morpheus Enterprise agent install, communication, and remote console access. Other configurations, such as docker instances, will need the appropriate ports opened as well.
+
+### Required Credentials & Permissions
+
+Credentials to integrate HPE Morpheus Enterprise with Azure Stack are located in both the public Azure Portal and the Private Azure Stack Portal. The Azure Active Directory Application used must be an owner of the Azure Stack subscription.
+
+Azure Portal:
+:   - Azure Active Directory Application Credentials
+    - Directory ID
+    - Management URL
+    - Identity Resource URL
+    - Application ID
+    - Key Value
+
+Azure Stack Portal:
+:   - Azure Stack Subscription ID
+    - Active Directory App from Azure portal added as owner of the Azure Stack Subscription in Azure Stack.
+
+## Adding an Azure Stack Cloud
+
+### Configure
+
+#### Procedure
+
+1. In the HPE Morpheus Enterprise UI, navigate to Infrastructure  >  Clouds and Select + CREATE CLOUD
+2. Select AZURE STACK (PRIVATE) from the Clouds list and select NEXT
+3. In the Configure section, enter: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   IDENTITY URL
+   :   <https://login.microsoftonline.com>
+
+   MANAGEMENT URL\*
+   :   Azure AD Azure Stack Administrator app or Microsoft Azure Stack Administrator app url. Example: <https://adminmanagement.local.azurestack.external/>
+
+   IDENTITY RESOURCE URL
+   :   Azure AD Azure Stack Administrator App ID URI Example: <https://adminmanagement.xxxxxxx.onmicrosoft.com/4a80e607-4259-4ac6-83e2-2fabeaf2eh83>
+
+   BASE DOMAIN
+   :   This should match the base domain in your Management url. Example: local.azurestack.external
+
+   SUBSCRIPTION ID
+   :   Subscription ID from Azure Stack portal (this is different from the Subscription ID in you Azure portal used when configuring Azure Stack)
+
+   TENANT ID
+   :   This is the Directory ID from the Azure AD directory
+
+   CLIENT ID
+   :   Application ID of Azure AD app with Azure Stack permissions granted, and has been added as an owner of the Azure Stack subscription (in the Azure Stack portal).
+
+   CLIENT SECRET
+   :   Key Value of Application ID used above
+
+       NOTE
+
+       Once all credentials are entered and validated, the Location and Resource Group fields will populate.
+
+   Location
+   :   Select an Azure Stack region for the cloud to scope to. This typically will be “local”.
+
+   Resource Group
+   :   Select All or a single Resource Group to scope the cloud to. Selecting a single Resource Group will only sync resources in that Resource Group and disable Resource Group selection during provisioning. All will sync all resources and allow specifying the Resource Group during provisioning.
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise.
+4. The Azure Stack cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+   NOTE
+
+   All fields and options can be edited after the Cloud is created.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+5. Once all options are configured, select NEXT to add the cloud to a Group. 
+
+   GROUP
+   :   A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+   USE EXISTING
+   :   Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+
+   CREATE NEW
+   :   Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+6. Confirm all settings are correct and select COMPLETE. The Azure Stack Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of: 
+
+   - Virtual Machines (if Inventory Existing Instances is enabled)
+   - Networks
+   - Virtual Images/Blueprints
+   - Network Security Groups
+   - Storage Accounts
+   - Marketplace Catalog
+   - Availability Sets
+
+   TIP
+
+   Synced Networks can be configured or deactivated from the Networks section in this Clouds detail page, or in the Infrastructure  >  Networks section.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json b/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
new file mode 100644
index 0000000..8d32a7a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+  "title": "Scale Thresholds",
+  "ordinal": 122,
+  "parent_title": "Automation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html",
+  "topic_cluster": {
+    "clustering_title": "Scale Thresholds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md b/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
new file mode 100644
index 0000000..7e9a0ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
@@ -0,0 +1,55 @@
+# Scale Thresholds
+
+Scale Thresholds are pre-configured settings for auto-scaling Instances. When adding auto-scaling to an instance, existing Scale Thresholds can be selected to determine auto-scaling rules.
+
+## Creating Scale Thresholds
+
+### Procedure
+
+1. Navigate to Library > Automation > Scale Thresholds
+2. Select + ADD
+3. Populate the following:
+
+### Results
+
+NAME
+:   Name of the Scale Threshold
+
+AUTO UPSCALE
+:   Enable to automatically upscale per Scale Threshold specifications
+
+AUTO DOWNSCALE
+:   Enable to automatically downscale per Scale Threshold specifications
+
+MIN COUNT
+:   Minimum node count for Instance. Auto-scaling will not downscale below MIN COUNT, and will auto upscale if the MIN COUNT is not met)
+
+MAX COUNT
+:   Maximum node count for Instance. Auto-scaling will not upscale past MAX COUNT, and will auto downscale if MAX COUNT is exceeded.
+
+ENABLE MEMORY THRESHOLD
+:   Check to set auto-scaling by specified memory utilization threshold (%)
+
+MIN MEMORY
+:   Enter MIN MEMORY % for triggering downscaling.
+
+MAX MEMORY
+:   Enter MAX MEMORY % for triggering upscaling.
+
+ENABLE DISK THRESHOLD
+:   Check to set auto-scaling by specified disk utilization threshold (%)
+
+MIN DISK
+:   Enter MIN DISK % for triggering downscaling.
+
+MAX DISK
+:   Enter MAX DISK % for triggering upscaling.
+
+ENABLE CPU THRESHOLD
+:   Check to set auto-scaling by specified overall CPU utilization threshold (%)
+
+MIN CPU
+:   Enter MIN CPU % for triggering downscaling.
+
+MAX CPU
+:   Enter MAX CPU % for triggering upscaling.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json b/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
new file mode 100644
index 0000000..00e649a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+  "title": "Apps",
+  "ordinal": 256,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md b/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
new file mode 100644
index 0000000..35f5e79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
@@ -0,0 +1,18 @@
+# Apps
+
+App monitors are very useful for seeing an aggregation of failures or impact based on a set of checks and groups. App monitors typically correlate to Apps provisioned from HPE Morpheus Enterprise Blueprints but can also be manually created and organized. They can be great for visualizing the customer impact a failure might have or even keeping up on a screen in a NOC. To create an App monitor:
+
+Name
+:   A friendly name for the new app monitor in HPE Morpheus Enterprise
+
+Description
+:   An optional description value to identify the app monitor
+
+Max Severity
+:   The maximum severity incident a failed app may create. This setting overrides check and group max severity settings
+
+Affects Availability
+:   When checked, this failed app impacts system-wide availability calculations
+
+App Checks
+:   Use the typeahead field to select as many checks as needed to complete the app monitor. Checks are created in Monitoring > Checks and must exist prior to creating the app monitor
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json b/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
new file mode 100644
index 0000000..2535caf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+  "title": "Trust",
+  "ordinal": 235,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md b/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
new file mode 100644
index 0000000..e06ab74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
@@ -0,0 +1,15 @@
+# Trust
+
+The Trust section is where credentials, SSH keypairs, and SSL certificates are stored. In addition, related integrations to outside technologies can be made in this section as well. Integration types include HPE Morpheus Enterprise Cypher and Hashicorp Vault for externalized credential storage. Continue onto the next section for more on standing up an external Cypher credential store.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html)**
+- **[Integrating Hashicorp Vault](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html)**
+- **[Installing and Integrating an External Cypher Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html)**
+- **[Add SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html)**
+- **[Delete SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html)**
+- **[Trust Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json b/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
new file mode 100644
index 0000000..f454a4d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+  "title": "Add Workflow",
+  "ordinal": 114,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html",
+  "topic_cluster": {
+    "clustering_title": "Add Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md b/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
new file mode 100644
index 0000000..98f263f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
@@ -0,0 +1,21 @@
+# Add Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar
+2. Select Automation from the sub-navigation menu
+3. Click the Workflows tab to show the Workflows tab panel
+4. Click the + Add dropdown and select a Workflow type (Operational or Provisioning, see the section above for more on Workflow type differences)
+5. From the New Workflow Wizard input a name for the workflow
+6. Optionally input a description and a target platform
+7. Add Tasks and Inputs using the typeahead fields, Tasks must be added to the appropriate phases for Provisioning Workflows
+8. If multiple tasks are added to the same execution phase, their execution order can be changed by selecting the grip icon and dragging the task to the desired execution order
+9. For multi-Tenant environments, select Public or Private visibility for the Workflow
+10. For Operational Workflows, optionally mark “Allow Custom Config” from the Advanced Options section if needed. See the next section for more on this selection
+11. Click the SAVE CHANGES button to save
+
+## Results
+
+NOTE
+
+When setting Workflow visibility to Public in a multi-Tenant environment, Tenants will be able to see the Workflow and also execute it directly from the Workflows list (if it’s an Operational Workflow). They will not be able to edit or delete the Workflow.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..4557fc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 308,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..52fe71d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,183 @@
+# Users
+
+## Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Tenant
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. From the Actions menu in each User row, the option is given to Impersonate the User, Edit, or Remove the User.
+
+In HPE Morpheus Enterprise 4.2.1 and higher, click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role create/edit page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in HPE Morpheus Enterprise, as it is synced from the Identity Source.
+
+## Create User
+
+### About this task
+
+Users can be created from Administration > Users or Administration > Tenants > (selected Tenant) > Users tab`.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+### Procedure
+
+1. Navigate to either Administration > Users or Administration > Tenants > Select a Tenant``.
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive Provisioning and Policy email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s).
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into HPE Morpheus Enterprise, but their user data will remain.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+
+### Results
+
+NOTE
+
+Instance Resource Limits for a user are now configured through [Policies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html#GUID-B0152179-D5F5-49E3-9CDD-E6BD2573DC0F)
+
+1. Select SAVE CHANGES.
+
+## Edit User
+
+### About this task
+
+User settings can be edited from Administration > Users, Administration > Tenants > Select a Tenant > Userstab`, or from User Settings.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in HPE Morpheus Enterprise, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click ACTIONS on the row of the user to edit.
+4. Select EDIT in the ACTIONS dropdown.
+5. Make changes.
+6. Select SAVE CHANGES.
+
+### Results
+
+To edit a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to edit.
+5. Select **EDIT** in the ACTIONS dropdown.
+6. Make changes.
+7. Select SAVE CHANGES.
+
+## User Settings
+
+### About this task
+
+Additional settings for a User can be found in the User Settings section, including:
+
+- User Photo
+- Default Group
+- Default Cloud
+- API Access
+
+To access User Settings:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings
+
+### Results
+
+To edit the User you are currently logged in as from User Settings:
+
+1. Select your name in the header
+2. Select User Settings
+3. Make changes.
+4. Select SAVE.
+
+## API Access
+
+### About this task
+
+API and CLI Access Tokens can be regenerated from the User Settings section.
+
+To regenerate a CLI or API Access Token:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings.
+3. Select API ACCESS under the Windows Settings section.
+4. Select ACTIONS for the Client ID the token will be generated for.
+5. Select Regenerate.
+6. Copy the Generated Access Token. 
+
+   IMPORTANT
+
+   The Access Token will be masked after User Setting are saved.
+7. Select SAVE.
+
+## Delete User
+
+### About this task
+
+To delete a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Select ACTIONS on the row of the user to delete.
+4. Select REMOVE in the ACTIONS dropdown.
+5. Confirm
+
+### Results
+
+To delete a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to delete.
+5. Select **REMOVE** in the ACTIONS dropdown.
+6. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
new file mode 100644
index 0000000..2a9c4b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+  "title": "Ansible",
+  "ordinal": 375,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
new file mode 100644
index 0000000..4327991
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
@@ -0,0 +1,295 @@
+# Ansible
+
+## Overview
+
+Ansible is a configuration management engine that is rapidly growing in popularity in the IT and DevOPS community. While it lacks some of the benefits at scale that solutions such as Chef or Puppet offer. It is very easy to get started and allows engineers to develop tasks in a simplistic markup language known as YAML. HPE Morpheus Enterprise integrates with an existing repository of playbooks as the master in a master-slave Ansible architecture.
+
+HPE Morpheus Enterprise not only supports Ansible but greatly enhances Ansible to do things that it could not do in its native form. For example, Ansible can now be configured to run over the HPE Morpheus Enterprise agent communication bus. This allows playbooks to be run against instances where SSH/WinRM access may not be feasible due to networking restrictions or other firewall constraints. Instead it can run over the HPE Morpheus Enterprise Agent which only requires port 443 access back to the HPE Morpheus Enterprise appliance URL.
+
+This integration supports both Linux-based and Windows platforms for playbook execution and can also be configured to query secrets from HPE Morpheus Enterprise Cypher services (similar to Vault).
+
+## Requirements
+
+- Minimum Ansible Version Requirement is 2.7.x
+- For agentless non-commandbus, sshpass is required
+- For Windows non-agent command bus, pywinrm is required
+- `Integrations: Ansible` User Role Permission required for access to Ansible Details Pages and Ansible tabs in Groups and Clouds
+- Calling HPE Morpheus Enterprise Cypher secrets into Ansible scripts requires the Python `requests` module which is not part of the Python standard library. For Ubuntu 18.04 or 20.04 run `sudo apt install python-requests` or `sudo apt install python3-requests`, respectively. For RHEL/CentOS, run `sudo yum install python2-requests`
+
+NOTE
+
+Installing Ansible on the HPE Morpheus Enterprise appliance is a requirement. In some cases, this is handled automatically but in certain situations you may have to install manually. See the section below on [troubleshooting Ansible](https://docs.morpheusdata.com/en/latest/troubleshooting/Ansible_Troubleshooting.html) for installation steps.
+
+## Add Ansible Integration
+
+### Procedure
+
+1. Navigate to Library > Integrationsand select + New Integration
+2. Select Integration Type “Ansible”
+3. Populate the following fields: 
+
+   Name
+   :   Name of the Ansible Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enabled by default
+
+   Ansible Git URL
+   :   https or git url format of the Ansible Git repo to use
+
+   Keypair
+   :   For private Git repos, a keypair must be added to HPE Morpheus Enterprise and the public key added to the git account.
+
+   Playbooks Path
+   :   Path of the Playbooks relative to the Git url.
+
+   Roles Path
+   :   Path of the Roles relative to the Git url.
+
+   Group Variable Path
+   :   Path of the Group Variables relative to the Git url.
+
+   Host Variables Path
+   :   Path of the Host Variables relative to the Git url.
+
+   Use Ansible Galaxy
+   :   Install roles defined in `requirements.yml`
+
+   Enable Verbose Logging
+   :   Enable to output verbose logging for Ansible task history
+
+   Use Morpheus Agent Command Bus
+   :   Enable for Ansible Playbooks to be executed via Morpheus Agent Command Bus instead of SSH
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Ansible on Windows
+
+When executing Ansible playbooks on Windows platforms, a few requirements must be met:
+
+- `pywinrm` may need to be installed on the HPE Morpheus Enterprise Appliance via `pip install pywinrm`
+- An Ansible Integration must be scoped to a Group or Cloud for Ansible to execute on Windows, as HPE Morpheus Enterprise assumes Ansible local when no group or cloud is scoped to Ansible. The playbooks do not need to be executed solely in the Group or Cloud, one just needs to be scoped to an Ansible Integration for Ansible Windows to run properly.
+
+## Scope Ansible Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Cloud, a new “ANSIBLE” tab will appear on the Cloud details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Scope Ansible Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Group, a new “ANSIBLE” tab will appear on the Group details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Integration added, an Ansible section will appear in the Config section of the provisioning wizard. By default, Ansible is enabled, but can be disabled by expanding the Ansible section and unchecking Enable Ansible.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible
+:   Select to bootstrap
+
+Ansible Group
+:   Ansible Inventory Group. Use existing group or enter a new group name to create a new group. Leaving this field blank will place instance in the “unassigned” inventory group.
+
+    NOTE
+
+    An instance can belong to multiple groups by separating group names with a comma
+
+Playbook
+:   Playbook(s) to run. The .yml extension is optional.
+
+## Running Playbooks
+
+Playbooks can also be run on all inventory groups, individual groups, or added as a task and ran with workflows.
+
+To run Ansible on all or a single inventory group, in the Ansible tab of the HPE Morpheus Enterprise Group page, select the Actions dropdown and click Run.
+
+In the Run Ansible modal, you can then select all or an individual group, and then all or a single Playbook, as well as add custom tags.
+
+Playbook’s can also be added as tasks to workflows in the Library > Automationsection, and then selected in the Automation pane during provisioning of new instances, when creating app blueprints, or ran on existing instances using the Actions  >  Run Workflow on the Instance or Host pages.
+
+## Using variables
+
+HPE Morpheus Enterprise variables can be used in playbooks.
+
+Use Case:
+:   Create a user as instance hostname during provisioning.
+    :   Below is the playbook. Add this playbook to a task and run it as a workflow on the instance.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['instance']['hostname'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['instance']['hostname'] }}` is the format of using HPE Morpheus Enterprise Variables
+
+    Create a user with a name which you enter during provisioning using a custom Instance type.
+    :   This instance type has a Text Input that provides a text box to enter a username. The fieldName of the Input in this case would be username. Below is the playbook.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['customOptions']['username'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['customOptions']['username'] }}` will be the format.
+
+## Using Secrets
+
+Another great feature with using Ansible and HPE Morpheus Enterprise together is the built in support for utilizing some of the services that HPE Morpheus Enterprise exposes for automation. One of these great services is known as Cypher (please see documentation on [Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html) for more details). Cypher allows one to store secret data in a highly encrypted way for future retrieval. Referencing keys stored in cypher in your playbooks is a matter of using a built-in lookup plugin for ansible.
+
+```
+```
+- name: Add a user  
+  win_user:  
+    name: "myusername"  
+    password: "{{ lookup('cypher','secret=password/myusername') }}"  
+    state: present
+```
+```
+
+By using the `{{ lookup('cypher','secret=password/myusername') }}` syntax. One can grab the value directly out of the key for use. This lookup plugin also supports a few other fancy shortcuts. In this above example the password/ mountpoint is capable of autogenerating passwords if they have not previously been defined and storing them within cypher for reference later.
+
+Another capability is accessing properties from within a key in cypher. The value of a key can also be a JSON object which can be referenced for properties within. For example:
+
+```
+```
+{{ lookup('cypher','secret=secret/myjsonobject:value') }}
+```
+```
+
+This would grab the value property off the nested json data stored within the key.
+
+Cypher is very powerful for storing these temporary or permanent secrets that one may need to orchestrate various tasks and workflows within Ansible.
+
+## Custom Inventory Entries
+
+With Morpheus it is possible to add custom inventory entries that exist outside of morpheus host/server entry. This is global across cloud or group and is done on the integration details page of the Ansible integration. To add a custom inventory entry navigate to Library > Integrations> (Your specific Ansible integration). Click on the `ACTIONS` button, then click `EDIT INVENTORY`. Inventory should be in the default Ansible ini format.
+
+![../../_images/ansible_inventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0099BB05-0B08-41BB-856E-5403C2315926-high.png)
+
+## Using Ansible over the HPE Morpheus Enterprise Agent Command Bus
+
+In many environments, there may be security restrictions on utilizing SSH or WinRM to run playbooks from an Ansible server on the appliance to a target machine. This could be due to being a customer network (in the environment of an MSP ), or various security restrictions put in place by tighter industries (i.e. Government, Medical, Finance).
+
+Ansible can get one in trouble in a hurry. It is limited in scalability due to its fundamental design decisions that seem to bypass concepts core to all other configuration management frameworks (i.e. Chef and Puppet). Because of its lack of an agent, the Ansible execution binary itself has to handle all the load and logic of executing playbooks on all the machines in the inventory of an Ansible project. This differs from other tools where the workload is distributed across the agents of each vm. Because of this (reaching out) approach, Ansible is very easy to get started with, but can be quite a bit slower as well as harder to scale up. However, HPE Morpheus Enterprise offers some solutions to help mitigate these issues and increase scalability while, at the same time improving security.
+
+### How does the HPE Morpheus Enterprise Agent Command Bus Work?
+
+One of the great things about HPE Morpheus Enterprise is it’s Agent Optional approach. This means that this functionality can work without the Agent, however the agent is what adds the security benefits being represented here. When an instance is provisioned (or converted to managed) within HPE Morpheus Enterprise, an agent can be installed. This agent opens a secure websocket back to the HPE Morpheus Enterprise appliance (over port 443). This agent is responsible for sending back logs, guest statistics, and a command bus for automation. Since it is a WebSocket, bidirectional communication is possible over a STOMP communication bus.
+
+When this functionality is enabled on an Ansible integration, a connection\_plugin is registered with Ansible of type morpheus and morpheus\_win. These direct bash or powershell commands, in their raw form, from Ansible to run over a HPE Morpheus Enterprise api. The Ansible binary sends commands to be executed as an https request over the API utilizing a one time execution lease token that is sent to the Ansible binary. File transfers can also be enacted by this API interface. When HPE Morpheus Enterprise receives these commands, they are sent to the target instances agent to be executed. Once they have completed a response is sent back and updated on the ExecutionRequest within HPE Morpheus Enterprise. Ansible polls for the state and output on these requests and uses those as the response of the execution. This means Ansible needs zero knowledge of a machines target ip address, nor its credentials. These are all stored and safely encrypted within HPE Morpheus Enterprise.
+
+It has also been pointed out that this execution bus is dramatically simpler than utilizing pywinrm when it comes to orchestrating Windows as the winrm configurations can be cumbersome to properly setup, especially in tightly secured Enterprise environments.
+
+## Using Ansible Galaxy
+
+HPE Morpheus Enterprise can use a `requirements.yml` file to define Ansible roles to download prior to running your playbook. Place `requirements.yml` into the root of your Git repository and make sure Use Ansible Galaxy is checked in the integration. Roles will be installed in the root of the repository if a directory is not defined in Roles Path.
+
+- Example requirements.yml:
+
+```
+```
+- src: https://github.com/geerlingguy/ansible-role-java  
+  name: java
+```
+```
+
+- Example playbook.yml:
+
+```
+```
+- hosts: all  
+  gather_facts: true  
+  roles:  
+    - java
+```
+```
+
+## Troubleshooting Ansible
+
+- When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in the ui logs in /var/log/morpheus/morpheus-ui/current​ which can be tailed by running `morpheus-ctl tail morpheus-ui`.
+- Verify Ansible is installed on the HPE Morpheus Enterprise Appliance.
+
+  Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+  If Ansible is not installed, follow these instructions to install, or use your preferred installation method:
+
+  Ubuntu:
+
+  ```
+  ```
+  sudo apt-get install software-properties-common  
+  sudo apt-add-repository ppa:ansible/ansible  
+  sudo apt-get update  
+  sudo apt-get install ansible
+  ```
+  ```
+
+  CentOS:
+
+  ```
+  ```
+  sudo yum install epel-release  
+  sudo yum install ansible
+  ```
+  ```
+
+  Then create the working Ansible directory for HPE Morpheus Enterprise:
+
+  ```
+  ```
+  mkdir -p /opt/morpheus/.ansible/tmp  
+  chown -R morpheus-local. /opt/morpheus/.ansible  
+  chmod -R 775 /opt/morpheus/.ansible
+  ```
+  ```
+- Validate the git repo is authorizing and the paths are configured correctly.
+
+  The public and private ssh keys need to be added to the HPE Morpheus Enterprise appliance via “Infrastructure > Keys& Certs” and the public key needs to be added to the git repo via user settings. If both are set up right, you will see the playbooks and roles populate in the Ansible Integration details page.
+- The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+- When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+- If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..2c05cb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 332,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json b/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
new file mode 100644
index 0000000..dc9294e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+  "title": "Administration",
+  "ordinal": 272,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md b/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
new file mode 100644
index 0000000..4869263
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
@@ -0,0 +1,16 @@
+# Administration
+
+There are several administrative integrations built into HPE Morpheus Enterprise that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html)**
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users & User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56_2.html)**
+- **[Policies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json b/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
new file mode 100644
index 0000000..2fbb096
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+  "title": "Volume Consumption",
+  "ordinal": 446,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Consumption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md b/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
new file mode 100644
index 0000000..88ee28d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
@@ -0,0 +1,23 @@
+# Volume Consumption
+
+Consumption of volume is typically done through compute instance provisioning, where the user can specify volumes to attach to, whether existing volumes or new volumes to be created. It can also be done using the reconfigure action.
+
+## Instance Provisioning
+
+During instance provisioning, the user can specify volumes to be attached to the servers within the instance. There are various types of volumes user can specify.
+
+## Sharing
+
+Volumes can be shared or unshared (attached to a specific server only). Specifying a shared volume means a single volume is attached to all the servers within that instance. Specifying an unshared volume means a volume is created for each server within the instance and exported to the corresponding server.
+
+## Existing vs New
+
+The user can specify a new volume to be created or specify to attach to an existing volume. Existing volume is applicable only to shared volumes.
+
+## Replicated vs Unreplicated
+
+When creating new volumes, the user can specify that the volume is unreplicated or replicated. Depending on the storage array deployed and the HA configuration, replicated volumes can be specified as CPP (classic peer persistence) or APP (active peer persistence).
+
+**Subtopics**  
+
+- **[Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
new file mode 100644
index 0000000..762ea8c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+  "title": "Overview",
+  "ordinal": 57,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
new file mode 100644
index 0000000..4428a55
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The HPE Morpheus Enterprise Analytics engine gives administrators the tools to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. Analytics dashboards can be organized into three primary categories based on their measurement intentions: costing, utilization, and workloads. Each dashboard type is discussed in further detail below.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json b/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
new file mode 100644
index 0000000..20cbf6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+  "title": "SolarWinds IPAM",
+  "ordinal": 514,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html",
+  "topic_cluster": {
+    "clustering_title": "SolarWinds IPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md b/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
new file mode 100644
index 0000000..6abe903
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
@@ -0,0 +1,90 @@
+# SolarWinds IPAM
+
+## Features
+
+- Automate static IP assignment across environments using Solarwinds IPAM
+- Network pool sync: Network pools can be set on networks in HPE Morpheus Enterprise for automated IP allocation and record creation
+- Optional Network Pool allocation and record sync. `Inventory Existing` option syncs all individual IP records and corresponding status. Inventory is not required for provisioning
+- Grid and list displays with IP record overlays and color coding for static, available, reserved and transient status
+- Manual IP Host record creation from Network Pool detail pages
+
+## Adding SolarWinds to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select SolarWinds
+4. Enter in the following information 
+
+   Name
+   :   Name of the SolarWinds Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable sync with the SolarWinds endpoint
+
+   URL
+   :   URL of the SolarWinds server, ex: `http://10.30.20.10:17778`
+
+   Username
+   :   Username of SolarWinds API User. See the NOTE box below for information on minimum rights requirements
+
+   Password
+   :   SolarWinds User password
+5. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+At minimum you will need credentials for a user with API and root-level propagating read access, as well as read/write access for target networks and domains. For a quicker solution, you can also use an account with the Power User role in situations where you aren’t concerned with providing only the minimum required access.
+
+## Consuming SolarWinds in HPE Morpheus Enterprise
+
+On saving your new integration, SolarWinds networks will be synced and can be viewed by navigating to Infrastructure  >  Network  >  IP POOLS. They’re also viewable from the detail section of the SolarWinds integration at Infrastructure  >  Network  >  INTEGRATIONS  >  (your SolarWinds integration)  >  NETWORK POOLS.
+
+![../../_images/networkpools.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4DA0027F-E1C3-4F28-80BC-929C5E44ADA2-high.png)
+
+Host records can also be viewed here by clicking on the name of a SolarWinds network.
+
+![../../_images/hostrecords.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-374CAAAE-F29E-46E2-93D5-F1B68E9A6477-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise SolarWinds integration does not support zone record syncing despite the presence of the ZONES tab on the integration detail page. This is a UI feature carried over from other networking integrations and is not supported at this time.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available SolarWinds IP in an IP/Network Pool and create the corresponding DNS records. HPE Morpheus Enterprise will also remove the records upon teardown. To enable this, add an SolarWinds IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL typeahead field, search for and select the name of the selected IP/Network Pool. 
+
+   - Gateway, DNS, and CIDR must be populated for static/pool IP assignment
+   - Select ALLOW IP OVERRIDE, if desired, to allow selecting between DHCP, static IP address entry, and pool address selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP POOLS
+2. Click + ADD
+3. Enter the following 
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/createhost1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7ACA8930-1EBE-46C3-93A0-FF538FFF439B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..a53e540
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 175,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..9e7f925
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json b/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
new file mode 100644
index 0000000..3c71183
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+  "title": "vCloud Director",
+  "ordinal": 473,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.html",
+  "topic_cluster": {
+    "clustering_title": "vCloud Director",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md b/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
new file mode 100644
index 0000000..9f7ecac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
@@ -0,0 +1,314 @@
+# vCloud Director
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Datastores
+- Brownfield VM management and migration
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- IP Pool Support
+- Multi-NIC Interfaces
+- Kubernetes and Docker
+- Proxy Support
+- Image Builder
+- Monthly estimated pricing and usage tracker
+- Custom plan discovery and utilization at provision time
+
+## Configuration
+
+### Add vCD Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select VCLOUD DIRECTOR from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   NOTE
+
+   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. You do not need both despite the fact that all four of those fields are indicated as required fields.
+
+   API URL
+   :   vCloud Director API Url
+       :   Example: `https://org.vcd.company.com`
+
+   CREDENTIALS
+   :   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. These may be locally entered (select Local Credentials), locally entered and stored securely for future use (select “username and password” or “api token, tenant” from within the “New Credentials” section), or a pre-existing credential set may be selected from the HPE Morpheus Enterprise secure credential store. Depending on the selection, additional fields will appear (or some may disappear) to facilitate your choice
+
+   USERNAME
+   :   vCD Organization Administrator or System Administrator User
+
+       - User must have an Organizational Administrator or System Administrator Role
+       - Username must be in the format of <name>@<org>
+       - When using a user with the System Administrator role, give the username in the format of <username>@system. Additionally, ensure this user has permission set correctly, such as to view objects created by the organization administrator if needed. Otherwise, things like catalogs and vApps created by the Organization Administrator might not be visible to HPE Morpheus Enterprise
+       - In some cases, it may not be advisable to use the system administrator user. This is because some environments will have API access turned off for the system administrator for security reasons as the user would be able to remove key pieces of infrastructure. If your system administrator user does have API access and you understand the risks, you can authenticate HPE Morpheus Enterprise with this user
+
+   PASSWORD
+   :   Password for the user indicated above
+
+   API TOKEN
+   :   A generated API token for the service account user
+
+   TENANT
+   :   The Tenant to which the service account user authenticates
+
+   ORG
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   VDC
+   :   Select VDC. Dropdown populates upon successful authorization.
+
+   API VERSION
+   :   Full version required which much be in the “xx.x” format. When applicable, do not drop a trailing “0” (Ex. `31.0`). HPE Morpheus Enterprise will attempt to discover the API version, which would make this field optional. However, vCD allows disabling of the API versions API. In such an environment, the user would need to specify the API version here
+
+   CATALOG
+   :   Optionally select a vCD catalog to store HPE Morpheus Enterprise artifacts or use the default “morpheus\_auto” catalog
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise
+
+   Enable Hypervisor Console
+   :   Mark to use VNC hypervisor console for the HPE Morpheus Enterprise console rather than the default SSH or RDP connection methods
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+## How to create vCloud Director templates for Morpheus
+
+### To create a Windows Template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build.
+
+#### Procedure
+
+1. Apply any service packs / updates to the operating system.
+2. Set the Network location to Private the below PowerShell will set the location. 
+
+   ```
+   ```
+   Get-NetConnectionProfile | Set-NetconnectionProfile -NetworkCategory private
+   ```
+   ```
+3. Configure WinRM to allow remote management and open the firewall. 
+
+   - To do this, under local computer Administrator, open a command prompt and run `winrm quickconfig`
+4. Install VMware tools
+5. Install .Net at least 4.5
+6. Enable remote PowerShell this can be done in PowerShell. 
+
+   ```
+   ```
+   Enable-PSremoting
+   ```
+   ```
+7. Shutdown the virtual machine and convert to a template. 
+
+   NOTE
+
+   Do not run sysprep
+
+### To create a Linux Centos template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install vmware tools
+6. Install git by running `yum install git`
+7. epel-release
+8. selinux set to permissive (enforced can cause problems with cloud-init)
+
+### To create a Linux Ubuntu template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Ensure you have set a root password
+4. Install cloud-init by running `sudo apt install cloud-init`
+5. Install cloud-utils-growpart `sudo apt install cloud-utils`
+6. Install desired hypervisor drivers (Virto, Open-VM Tools)
+7. Install git by running `sudo apt install git`
+8. As Debian 9 includes network manager ensure this is disabled. Change the below file
+
+#### Results
+
+```
+```
+/etc/NetworkManager/NetworkManager.conf
+```
+```
+
+to the following:
+
+```
+```
+managed=false
+```
+```
+
+We also recommend disabling network manager and setting the network adapter to eth0 rather than the automatically assigned name. See a more detailed guide on VMware image prep [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware_templates.html?highlight=vmware%2520image%2520prep#creating-a-centos-rhel-7-image).
+
+To import your template into vCloud director you will need to login as either an administrator or organisation administrator.
+
+Once logged into vCloud director you will then need select `Manage Organizations` and then select your organization.
+
+From within the organisation click on `Catalogues` > select an existing catalogue or create a new catalogue.
+
+NOTE
+
+Please note once you connect HPE Morpheus Enterprise to your vCD environment, it will create a catalogue called Auto HPE Morpheus Enterprise. This is a working catalogue and is ignored by HPE Morpheus Enterprise when searching for images, so any images in the catalogue will not be synced into HPE Morpheus Enterprise
+
+Open the catalogue and select the import template from vCenter and then browse the data stores for your templates. Select your template and the type in a new name and description then check the copy template into vCloud director.
+
+Once you click ok the import process will begin. When the import has completed the template will appear in HPE Morpheus Enterprise within Library > Virtual Images
+
+If the image does not appear within the virtual images you may need to use the filters to filter the virtual images by the vmware ( vmdk / ovf / ova) type.
+
+You may also need to refresh the cloud. To do this go to Infrastructure  >  Clouds > select the vCloud Director cloud > selectRefresh.
+
+​
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.json b/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
new file mode 100644
index 0000000..567aad3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+  "title": "phpIPAM",
+  "ordinal": 507,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html",
+  "topic_cluster": {
+    "clustering_title": "phpIPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.md b/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
new file mode 100644
index 0000000..251c04e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
@@ -0,0 +1,30 @@
+# phpIPAM
+
+## Configuration
+
+### Procedure
+
+1. Within phpIPAM dashboard, enable api in Administration > phpIPAMsettings > featuresettings. Toggle API switch to `on` and save.
+2. Go to Admin > API > create API key.
+3. Create unique App ID.
+4. Enable `read/write/admin` access under App Permissions.
+5. Under App Security select `SSL with User Token`.
+
+## Add phpIPAM integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select + ADD > IPAM > phpIPAM
+3. Enter the following: 
+
+   - Name
+   - URL
+     :   Add `/api/` to end of URL ex. `http://10.30.20.196/api/`
+   - App ID
+     :   From phpIPAM API Key
+   - Username
+   - Password
+   - Enable or Disable SSL SNI Verification
+   - Enter Network Filter
+4. Select SAVE IPAM INTEGRATION
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json b/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
new file mode 100644
index 0000000..e4722e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+  "title": "Creating an HPE BMaaS Cloud",
+  "ordinal": 401,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an HPE BMaaS Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md b/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
new file mode 100644
index 0000000..37477ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
@@ -0,0 +1,38 @@
+# Creating an HPE BMaaS Cloud
+
+## About this task
+
+Creating an HPE BMaaS Cloud integrates physical infrastructure into the Morpheus management plane, establishing a logical boundary for bare-metal resources to enable group-based policies and proxy configurations. This setup allows for onboarding HPE ProLiant servers for automated provisioning and lifecycle management.
+
+To create an **HPE BMaaS Cloud** in Morpheus for HPE ProLiant bare-metal operations, follow this procedure:
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds in the Morpheus interface.
+2. Click the + Add button.
+3. Locate and select the HPE BMaaS Cloud type as HPE Bare Metal (BMaaS), and then click Next.  
+   ![Create Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C875F0A7-EDDE-42E3-B87B-DE90F18B9A51-high.png)
+4. Enter the name, code, Labels, Location, and complete any additional required details for the cloud.   
+   ![Cloud Configure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0C50D8A2-3CA6-416E-AA73-0DA3FA82167B-high.png)
+5. **Optional:**  In Provisioning Command, select a Proxy for provisioned bare metal instances if required, then click Next.  
+   ![Provisioning Command](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-172BEA46-96D8-4D0D-83D8-B0D6428A0ED5-high.png)
+6. For the group, you may either select Use Existing or Create New: 
+
+   - To use an existing group, choose Use Existing and select the desired group from the drop-down list.   
+     ![Existing Group](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6EC50EB8-DE0B-43B4-A168-B43E3A87CAB5-high.png)
+   - To create a new group, select Create New and follow the on-screen prompts.   
+     ![Create New](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-213FFFF2-8183-4E33-A2A3-9437A433373E-high.png)
+7. Click Next to review your cloud configuration details, then click Complete to finalize cloud creation.
+
+   NOTE
+
+   By default, the Network Mode is set to Unmanaged for the created Bare metal cloud. If you need to use ArubaCX integration, modify the Bare metal cloud and set the Network Mode to the ArubaCX-Integration.
+
+## Results
+
+After completion, the newly created group appears in the list of groups.   
+![Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3917DB5B-D58F-4FFF-A06C-40BD5401CFE7-high.png)
+
+**Subtopics**  
+
+- **[Default Unmanaged Network Support](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json b/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
new file mode 100644
index 0000000..2447d1c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+  "title": "Templates",
+  "ordinal": 158,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html",
+  "topic_cluster": {
+    "clustering_title": "Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md b/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
new file mode 100644
index 0000000..d59d839
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
@@ -0,0 +1,11 @@
+# Templates
+
+Templates can be created directly in HPE Morpheus Enterprise and/or sourced from version control, depending on the type. They can be used to help users consume IaC technologies, generate configuration files, utilize scripts or store security scan packages. Once stored, they can be used with provisioned Instances, configured as part of Tasks or Workflows, or run regularly as part of security scan Jobs. Each section below discusses template types in greater detail.
+
+**Subtopics**  
+
+- **[Spec Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html)**
+- **[File Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html)**
+- **[Script Templates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html)**
+- **[Security Packages](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ED404402-F168-4635-ADEB-02609465196E.html)**
+- **[Cluster Packages](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.json b/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
new file mode 100644
index 0000000..5f64dbd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+  "title": "Automation Integrations",
+  "ordinal": 374,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.md b/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
new file mode 100644
index 0000000..722aa7e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
@@ -0,0 +1,10 @@
+# Automation Integrations
+
+**Subtopics**  
+
+- **[Ansible](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html)**
+- **[Ansible Tower](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html)**
+- **[Chef](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html)**
+- **[Puppet](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html)**
+- **[Terraform](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html)**
+- **[vRealize Orchestrator](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json b/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
new file mode 100644
index 0000000..4b8c6c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+  "title": "Guidance",
+  "ordinal": 71,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html",
+  "topic_cluster": {
+    "clustering_title": "Guidance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md b/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
new file mode 100644
index 0000000..0328692
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
@@ -0,0 +1,93 @@
+# Guidance
+
+## Overview
+
+The Operations  >  Guidance section shows recommendations for resource and cost optimization. By analyzing the CPU, RAM, and Storage activity of Instances and Hosts, HPE Morpheus Enterprise can recommend actions for sizing and power state. Guidance is customizable to show recommendations based on 30, 60, or 90 day periods, this dropdown toggle is visible on the Guidance list page (Operations > Guidance). Guidance thresholds are also customizable, they can be edited in Administration > Settings > Guidance.
+
+### Configuration
+
+#### About this task
+
+Guidance is configured per Cloud and is turned off by default.
+
+To turn on HPE Morpheus Enterprise Guidance for a Cloud:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click EDIT
+3. Expand the Advanced Options section in the Edit Cloud modal
+4. In the Guidance dropdown, select Manual
+5. Click SAVE CHANGES
+
+#### Results
+
+Guidance recommendations will begin to appear in the guidance section when generated.
+
+NOTE
+
+It will take approximately seven days before HPE Morpheus Enterprise gathers sufficient data to make guidance recommendations.|morpheus| Guidance is significantly improved when the Agent is installed on provisioned workloads. When the Agent is not installed, HPE Morpheus Enterprise still makes a best effort to provide relevant guidance recommendations.
+
+Once Guidance has been turned on for a Cloud, HPE Morpheus Enterprise will determine if a guidance recommendation should be made once every 30 minutes. In the event that no recommendations can be made, no entry will be added to the list of suggested guidances. As the guidance list continues to grow, sorting and filtering may become necessary to focus on the recommendations that are relevant to the user at the time.
+
+It’s important to note that acting on recommendations is entirely manual at this time. In many cases, Morpheus provides one-click action to take the recommended steps but Guidance recommendations cannot be taken automatically. This is a feature that is being explored for a future update but has not been tagged for any specific release version at this time. In addition, it’s recommended that HPE Morpheus Enterprise Agent be installed to maximize the benefits of Guidance. While Guidance will still work without installing the Agent, the greatly-enhanced statistics provided by the Agent will significantly improve Guidance recommendations.
+
+To see more detail on a Guidance recommendation in your list, click on the (i) button at the far right side of each list row. This will open a detail modal that gives additional information on the Guidance entry. In some cases, such as with sizing and shutdown recommendations, the user can simply click the “EXECUTE” button to take the recommended action as shown below.
+
+![The execute button allows the user to immediately take action on a sizing recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6493DA77-2790-4079-9636-57D2B389DBCD-high.png)
+
+Other types of Guidance recommendations, such as reserve compute recommendations, must be taken in the cloud and Morpheus does not offer the execute button.
+
+![The execute button is not present on a reserve compute recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-88431DCD-48BE-4414-BC59-89F31565FE07-high.png)
+
+NOTE
+
+The IGNORE button will remove the recommendation from the UI. Subsequent recommendations of the same type will NOT display for the same object (VM, Cloud etc) again unless the original recommendation is resolved.
+
+### Recommendations
+
+To view and act on Guidance recommendations, navigate to Operations  >  Guidance.
+
+The Guidance list contains the following details:
+
+Severity Icon
+:   Indicates the severity of the recommended action.
+
+Type
+:   Recommended action Type
+
+Metric
+:   Guidance Metric used for recommended action.
+
+Action
+:   Recommended Action for the Instance or Host, such as “Reduce Host memory” or “Shutdown Instance”
+
+RESOURCE
+:   The Instance or Host targeted
+
+SAVINGS
+:   Shows projected Monthly Costs savings if recommended action is taken.
+
+DATE
+:   Date and Time stamp the recommended action was generated.
+
+Information Link
+:   Click to view details on the recommendation.
+
+NOTE
+
+Guidance Actions are not automatically triggered at this time.
+
+### Filters
+
+Search
+:   Search for Guidance recommendations
+
+Type
+:   Filter by Sizing or Shutdown Guidance Types.
+
+Severity
+:   Filter by Guidance Severity of All, Info, Warning, or Critical.
+
+Metric
+:   Filter by All, Memory, CPU, or Power Guidance Metrics.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json b/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
new file mode 100644
index 0000000..8359902
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+  "title": "AWS Route53",
+  "ordinal": 483,
+  "parent_title": "DNS",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html",
+  "topic_cluster": {
+    "clustering_title": "AWS Route53",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md b/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
new file mode 100644
index 0000000..3ca30c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
@@ -0,0 +1,78 @@
+# AWS Route53
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with Amazon Route 53 to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in Route 53 Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add Route 53 Integration
+
+### About this task
+
+Route 53 can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   Route 53
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   REGION
+   :   AWS Region for the Integration
+
+   ACCESS KEY
+   :   AWS User IAM Access Key
+
+   SECRET KEY
+   :   AWS User IAM Secret Key
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, Route 53 Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring Route 53 with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..b04ffa2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 110,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..08e0745
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1,40 @@
+# Task Management
+
+## Adding Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary signficiantly based on the selected Task type. More details on each Task type are contained in the preceding sections.
+6. Once done, click SAVE CHANGES
+
+### Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference HPE Morpheus Enterprise variables which pertain to the specific Instance the Task is being run against. HPE Morpheus Enterprise includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and HPE Morpheus Enterprise will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus Enterprise API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
+
+![../../_images/taskvars.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BA459071-AEAD-4E96-8DB9-FD67DDE9ABC5-high.png)
+
+## Editing Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
+
+## Deleting Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json b/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
new file mode 100644
index 0000000..3d61acb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+  "title": "Kubernetes Blueprints",
+  "ordinal": 135,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md b/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
new file mode 100644
index 0000000..863a6fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
@@ -0,0 +1,39 @@
+# Kubernetes Blueprints
+
+HPE Morpheus Enterprise allows you to store Kubernetes configuration YAML files for easy deployment on-demand. Kubernetes Blueprints can be built by pulling in Kubernetes spec stored as a HPE Morpheus Enterprise Spec Template object, those tracked under version control in a Git repository, or you can write them directly in the New Blueprint modal.
+
+To create a new Kubernetes Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Kubernetes. NEXT
+
+In the Cluster Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Complete the Kubernetes Configuration section as follows depending on your Config Type selection.
+
+To consume a HPE Morpheus Enterprise Spec Template containing Kubernetes spec:
+
+- **CONFIG TYPE:** “Kubernetes Spec”
+- **SPEC TEMPLATE:** Use the typeahead field to locate the desired Spec Template
+
+To draft or paste configuration directly in the New Blueprint modal:
+
+- **CONFIG TYPE:** “Kubernetes Yaml Spec”
+- **CONFIG:** Enter your YAML configuration template here
+
+To consume YAML configuration files tracked in a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new Kubernetes Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json b/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
new file mode 100644
index 0000000..7001fe1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+  "title": "LDAP Query Variables",
+  "ordinal": 156,
+  "parent_title": "Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html",
+  "topic_cluster": {
+    "clustering_title": "LDAP Query Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md b/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
new file mode 100644
index 0000000..8bad4f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
@@ -0,0 +1,29 @@
+# LDAP Query Variables
+
+The current user and dependant parameters are loaded into the query using the <%=phrase%> syntax.
+
+```
+```
+LDAP Query Variables (Example <%=user.email%>)
+```
+```
+
+```
+```
+ user {  
+    accountId,  
+    attributes,  
+    displayName,  
+    email,  
+    firstName,  
+    id,  
+    lastName,  
+    linuxUsername,  
+    username,  
+    windowsUsername  
+ }  
+ customOptions {  
+    fieldName  
+ }
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..ee7b858
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 107,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..6f710f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,60 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
+
+## Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A HPE Morpheus Enterprise-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the HPE Morpheus Enterprise appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
+
+## Execute Options
+
+- **Continue on Error:** When marked, Workflows containing this Task will continue and will remain in a successful state if this Task fails
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) HPE Morpheus Enterprise will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
+
+## Source Options
+
+Task configuration code may be entered in a number of ways depending on the Task type. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing. Not every Task type supports every sourcing type listed here.
+
+- **Local:** The Task configuration code is written directly in HPE Morpheus Enterprise in a large text area. HPE Morpheus Enterprise includes syntax highlighting for supported Task languages for easier debugging and script writing
+- **Repository:** Source the Task configuration code from an integrated Git or Github repository. This requires a pre-existing integration with a Github or other Git-based repository. See the [relevant integration guides](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for full details on creating such an integration. Specify the path to the appropriate file through the WORKING PATH field. The appropriate branch may also be specified (if a branch other than ‘main’ is required) in the BRANCH/TAG field. To reference a tag from this field, use the following syntax: `refs/tags/<tag-name-here>`. Unless otherwise specified, Task config is sourced fresh from the repository each time the Task is invoked which ensures the latest code is always used
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
+
+## Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. If the Task is to be part of an Operational Workflow, mark the same box on the Workflow rather than on the Task to see the text area at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json b/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
new file mode 100644
index 0000000..2db7b05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+  "title": "Boot Volume Selection During Instance Creation for Local Storage",
+  "ordinal": 437,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md b/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
new file mode 100644
index 0000000..76cf228
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
@@ -0,0 +1,47 @@
+# Boot Volume Selection During Instance Creation for Local Storage
+
+During Morpheus instance creation, the provisioning workflow will **delete existing logical volumes**, **create a boot volume**, and then **identify the correct disk device** using the device’s unique identifier (UID).
+
+The boot volume is determined by matching the device UID found in the storage controller to the corresponding Linux device path.
+
+## Log Details
+
+When creating a Morpheus instance, you may see the following log entries:
+
+```
+```
+[2026-02-09 02:45:39,023] ... Deleting all logical volumes on server  
+[2026-02-09 02:45:42,887] ... Attempting to create boot volume  
+[2026-02-09 02:45:43,470] ... Waiting for device discovery complete. Success  
+[2026-02-09 02:45:44,442] ... GET /redfish/v1/.../Drives/2556 -> error: ResourceMissingAtURI ... Retrying in 10 seconds...  
+[2026-02-09 02:45:44,442] ... Boot volume for server created with unique identifier: 600508B1001C40706B7600592D4A5C5A
+```
+```
+
+The logs show:
+
+- Logical volumes are cleared on the server.
+- Morpheus creates a new boot volume.
+- The system waits for Redfish device discovery to complete.
+- If a drive is not yet visible, it may return `ResourceMissingAtURI` and retry.
+- Once the boot volume is created, it logs the unique device identifier.
+- How Boot Volume is Determined.
+
+For OS installation, the boot volume is identified based on the **device UID**. Depending on the server storage controller, the device UID format differs
+
+Table 1. UID Format
+
+       | Storage Device | Name | RAID Type | Identifiers.DurableNameFormat | Identifiers.DurableName |
+| --- | --- | --- | --- | --- |
+| HPE MegaRAID (MR216i-o) Storage Controller | BootVolume | RAID1 | NAA | 600508B1001C40706B7600592D4A5C5A |
+| HPE NVMe SHIELD (NS204i) Boot Device | BootVolume | RAID1 | EUI | 1234:5678:9ABC:DEF0 |
+
+## Finding the Device Path
+
+Once the device UID is known (from the storage controller), the provisioning script searches for the matching device in `/dev/disk/by-id/`
+
+The script looks for the **first entry that contains the UID** (or a stripped version of the UID). These entries are **stable identifiers** that point to the actual Linux block device.
+
+Once a match is found, the script resolves the symbolic link to determine the real boot device path, which will be in the form: `/dev/sdX`
+
+This `/dev/sdX` path is then used for OS installation.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json b/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
new file mode 100644
index 0000000..ff42c88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+  "title": "Unisys Stealth",
+  "ordinal": 515,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html",
+  "topic_cluster": {
+    "clustering_title": "Unisys Stealth",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md b/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
new file mode 100644
index 0000000..397366f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
@@ -0,0 +1,182 @@
+# Unisys Stealth
+
+## Introduction
+
+Unisys Stealth is a network security tool for safeguarding sensitive information across shared networks. By creating pre-defined communities of interest (COIs) and curating user access to these groups, the need to create separate networks for handling restricted data is reduced.
+
+HPE Morpheus Enterprise includes a full integration with Stealth allowing administrators to create and manage COIs, work with configurations and roles, and provision new endpoints into COIs.
+
+## Stealth Concepts
+
+- **Communities of Interest (COIs):** A collection of endpoints cryptographically separated so they can only communicate to each other
+- **Endpoints:** Any system or device with a Stealth agent
+- **Configuration:** Tells the endpoints which authorization methods and services to use for obtaining COI membership
+- **Role:** Defines COI membership. Users and groups are assigned to a role which grants access to that role’s COIs
+- **Filters:** Customizes Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints
+
+## Integrating Stealth with HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Click + ADD
+3. Complete the following fields: 
+
+   - NAME: A name for this Stealth integration in HPE Morpheus Enterprise
+   - API HOST: The address for the server hosting Stealth (ex: <https://x.x.x.x:8448>)
+   - USERNAME: A username for the portaladmin, or the user who logs into the web console
+   - PASSWORD: A password for the account
+   - MANAGER USERNAME: A username for the manager account
+   - MANAGER PASSWORD: A password for the manager account
+4. Click ADD SECURITY INTEGRATION
+
+### Results
+
+![../../_images/add_stealth.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E5EFDABE-E6AE-4E24-A24A-E39E52F95B1D-high.png)
+
+## Summary View
+
+The default view when accessing a Stealth integration in HPE Morpheus Enterprise is the Summary view. In addition to basic information about the Stealth server itself, we can see system status, license and service information.
+
+![../../_images/stealth_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2EDC17EA-E415-404A-936D-E6FCC06BD235-high.png)
+
+## Endpoints
+
+Endpoints are any system or device with a Stealth agent. Stealth endpoints can be provisioned in HPE Morpheus Enterprise in the same way other cloud resources are provisioned. With Stealth integrated, workloads provisioned on the appointed networks are assigned Stealth configuration and a Stealth role during the provisioning process. Based on a user’s assigned roles and COIs assigned to those roles, only workloads on the appointed COIs will be visible to the user. Additionally, workloads can only see other workloads within their COI.
+
+NOTE
+
+Machines on the same network which are not Stealth-managed will be able to see and communicate with each other but will not be able to see workloads which are assigned to a Stealth COI.
+
+### Endpoints View
+
+The endpoints view will display all available Stealth-managed resources. Endpoints are not created here but will be synced into this view as they are created (through HPE Morpheus Enterprise provisioning or outside creation). Stealth-managed endpoints can be deleted by clicking the trash can icon at the end of each row in this view.
+
+The following fields are exposed in the endpoints list view:
+
+- **DISPLAY NAME**
+- **NAME**
+- **DESCRIPTION**
+
+## Configurations
+
+Configurations in Stealth are the top-level construct and house COIs, roles, groups, users and endpoints. Your Stealth integration will include at least one configuration but often they will include more.
+
+Configurations are primarily created and managed from the Stealth console but we can opt to remove them from HPE Morpheus Enterprise by clicking the trash can icon at the end of each row on the configurations list page. Configurations are selected along with a Stealth role at provision time in HPE Morpheus Enterprise.
+
+### Configurations View
+
+The following fields are exposed in the configurations list view:
+
+- **NAME:** The name of the configuration
+- **DESCRIPTION:** A description value for the configuration
+
+## Roles
+
+Users are placed into roles which are associated with COIs. A user’s role(s) determine which COIs he or she will be able to see and access. Roles are synced into HPE Morpheus Enterprise once the integration process is complete and can be viewed in the Roles list view. Roles can also be created from the HPE Morpheus Enterprise integration as described later in this section.
+
+### Roles View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the role
+- **DESCRIPTION:** A description value for the role
+
+NOTE
+
+More detail on each item in the roles list can be revealed by clicking on the (i) icon in each row, including the COIs associated with the role.
+
+### Creating Stealth Roles
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > Roles
+2. Click + CREATE ROLE
+3. Complete the following fields: 
+
+   - NAME: The name for the new role
+   - DESCRIPTION: A description value for the new role
+   - CONFIGURATION: Select an existing Stealth configuration to associate with the role
+   - ROLE TYPE: Identifies how the role is used. Can be Global (for roles used to isolate endpoints and users), Service (for roles used by endpoints in service mode to access an authorization service) or WorkGroup (for roles used by endpoints in normal operation)
+   - FILTER SET: Choose a filter set to apply to the role to allow or deny clear text communication with non-Stealth-managed endpoints
+   - COIs: Select the COIs to be associated with the role
+   - PROVISION CHANGES:
+4. Click ADD ROLE
+
+#### Results
+
+![../../_images/add_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FE9AB72A-8680-480B-98F5-3795480217A0-high.png)
+
+## COIs (Communities of Interest)
+
+COIs exist within configurations and create a logical separation between endpoints in separate COIs. Communication between endpoints in the COI is encrypted and those outside the COI are unable to see or access endpoints despite being on the same network.
+
+On completing the integration, HPE Morpheus Enterprise will sync in existing COIs. COIs can also be created from HPE Morpheus Enterprise UI which is described later in this section. COIs are deleted by clicking on the trash can icon at the end of each row in the COIs list view.
+
+### COIs View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the COI
+- **DESCRIPTION:** A description value for the COI
+
+### Creating Stealth COIs
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > COIs
+2. Click + CREATE COI
+3. Complete the following fields: 
+
+   - NAME: The name for the new COI
+   - DESCRIPTION: A description value for the new COI
+   - TYPE: Workgroup or Service
+   - DIRECTION: Default (enables COI to accept inbound and initiate outbound tunnels), Initiate (restricts the COI to only initiate outbound tunnels), or Accept (restricts the COI to only accept inbound tunnels)
+4. Click CREATE COI
+
+#### Results
+
+![../../_images/create_coi.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EA1DA1E2-1AB6-494A-A776-013769EB3C4D-high.png)
+
+## Filters
+
+Filters customize Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints.
+
+Filters are synced into HPE Morpheus Enterprise when integrating with Stealth and are viewable from the filters list view. They are created and managed from within the Stealth console itself.
+
+When accessing the filters list view, all filter sets are displayed. Each filter set can be expanded to view the individual filters within. Information on each filter is displayed once the filter set has been expanded to reveal the individual filters.
+
+## Provisioning with Stealth
+
+In order to provision new Stealth-managed endpoints, Stealth must be integrated with HPE Morpheus Enterprise as described above. In addition, Stealth must be selected as the Security Server for the cloud you’re provisioning into. Security servers can be selected at the time a new Cloud integration is created or by editing an existing Cloud integration.
+
+### Choosing a Cloud Security Server
+
+#### About this task
+
+Assuming the Cloud is already integrated with HPE Morpheus Enterprise, use the steps below to set the security server and activate Stealth prompts at provision time. The steps to set the security server during the time the cloud is initially integrated with HPE Morpheus Enterprise is very similar.
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds > (Your Selected Cloud)
+2. Click EDIT
+3. Click on Advanced Options to reveal additional selections
+4. In the dropdown for SECURITY SERVER, choose an existing Stealth integration
+
+### Provisioning to a Stealth-enabled Cloud
+
+#### About this task
+
+Once we have selected our Stealth integration as the security server for at least one Cloud in HPE Morpheus Enterprise, new Instances (endpoints) can be provisioned and managed by Stealth.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Instance Type, Cloud, and Group making sure to choose a Cloud that has been set up for an existing Stealth integration
+4. On the Configure tab of the provisioning wizard, choose a Stealth Configuration and a Stealth Role according to the needs of the machine(s) being provisioning
+5. Once the provisioning process is complete, the new Stealth-managed endpoints will be available and restricted based on the Stealth implementation
+
+#### Results
+
+![../../_images/provision_endpoint.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C5EBFD40-8381-4497-9E9F-05EEC4AB65F6-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..cf2d998
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 505,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..9dde7d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,15 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[Infoblox](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html)**
+- **[phpIPAM](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html)**
+- **[NSX](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html)**
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
+- **[NSX Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html)**
+- **[Cisco ACI](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html)**
+- **[Bluecat](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html)**
+- **[SolarWinds IPAM](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html)**
+- **[Unisys Stealth](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html)**
+- **[EfficientIP SOLIDserver](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json b/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
new file mode 100644
index 0000000..e39a5b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+  "title": "Hyper-V",
+  "ordinal": 458,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.html",
+  "topic_cluster": {
+    "clustering_title": "Hyper-V",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md b/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
new file mode 100644
index 0000000..e5c69ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
@@ -0,0 +1,179 @@
+# Hyper-V
+
+Hyper-V is the virtualized server computing environment introduced by Microsoft. Hyper-V is consumed by HPE Morpheus Enterprise as a private cloud offering and is a common hypervisor technology in data centers. HPE Morpheus Enterprise provides an avenue to aggregate Hyper-V resources together to allow efficient and seamless deployment of applications as a virtual machine (VM) or Docker host in the world of Hyper-V.
+
+## Features
+
+- Virtual Machine Provisioning
+- Discovery of Existing Instances
+- Containers
+- Backups / Snapshots
+- Resources Groups
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Veeam Integration
+- Lifecycle Management and Resize
+- Unique Kerberos Authentication
+
+## Getting Started
+
+To get started, a few prerequisites must first be met. The Hyper-V host must be installed with its firewall enabled and it can either be joined to a domain or standalone. The Hyper-V host must also have the external network of Hyper-V configured and it can share this network with the management operating system. A user account that is part of the local administrators group on the Hyper-V host is also required. This document covers Hyper-V 2008 and Hyper-V 2012.
+
+## Understanding WinRM
+
+HPE Morpheus Enterprise uses WinRM to communicate to the Hyper-V host for deployment of the HPE Morpheus Enterprise Agent. The HPE Morpheus Enterprise Agent allows for the host dashboard to be populated with information in the form of graphs that cover CPU, Network, Storage, and memory consumption. Furthermore, this Agent provides logging and monitoring capabilities.
+
+If Windows Remote Management (WinRM) is not installed and configured, WinRM scripts do not run and the WinRM command line tool cannot perform data operations or allow for the HPE Morpheus Enterprise Agent to be installed. WinRM uses HTTP port 5985 or HTTPS port 5986 for communications.
+
+To better understand all of the default settings of WinRM please refer to the [following page](https://msdn.microsoft.com/en-us/library/aa384372%28v=vs.85%29.aspx) in Microsoft documentation.
+
+## Native Authentication
+
+To configure WinRM with default settings (WINRM\_NATIVE)
+
+Type the following command at a command prompt:
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the Runas command at a command prompt.
+
+When the tool displays `Make these changes [y/n]?`, type `y`.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. By default Kerberos is enabled and if domain authentication is not being used we want to disable that. Issue the below commands to setup basic authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth '@{Basic="true"}'  
+$ winrm set winrm/config/service '@{AllowUnencrypted="true"}'  
+$ winrm set winrm/config/service/Auth '@{Kerberos="false"}'
+```
+```
+
+## Domain Authentication
+
+To configure WinRM with Domain Authentication (WINRM\_INTERNAL)
+
+Type the following command at a command prompt
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the runas command at a command prompt.
+
+When the tool displays Make these changes [y/n]?, type y.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. Issue the below commands to setup domain authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth @{Basic="true"}  
+$ winrm set winrm/config/service @{AllowUnencrypted="false"}  
+$ winrm set winrm/config/service/Auth @{Kerberos="true"}
+```
+```
+
+Kerberos authentication will also need to be configured on the HPE Morpheus Enterprise appliance to support Windows domain accounts to access the remote host with WINRM\_INTERNAL connection type.
+
+On the HPE Morpheus Enterprise appliance the krb5-user package must be installed.
+
+For Ubuntu the command is as follows:
+
+```
+```
+$ sudo apt-get install krb5-user
+```
+```
+
+For Centos the command is as follows:
+
+```
+```
+$ sudo yum install krb5-workstation pam_krb5 -y
+```
+```
+
+Create a file in /etc called krb5.conf and replace the domain name with the name of the domain to be used. In this case we used HPE Morpheus Enterprise .com as the domain.
+
+```
+```
+[libdefaults]  
+        default_realm = |morpheus| .COM  
+            dns_lookup_kdc = true  
+            verify_ap_req_nofail = false  
+        default_tgs_enctypes = rc4-hmac  
+        default_tkt_enctypes = rc4-hmac  
+[realms]  
+        |morpheus| .COM = {  
+                kdc = win-ad.|morpheus| .COM:88  
+                admin_server = win-ad.|morpheus| .COM:749  
+     }  
+[domain_realm]  
+    .|morpheus| .COM = |morpheus| .COM  
+        |morpheus| .COM = |morpheus| .COM  
+[login]  
+     krb4_convert = true  
+     krb4_get_tickets = false
+```
+```
+
+After creation of the krb5.conf a keytab file is also required. See below for instructions on how to create a keytab file. <http://www.itadmintools.com/2011/07/creating-kerberos-keytab-files.html>
+
+## Adding Hyper-V as a Private Cloud
+
+The Hyper-V host is prepared for HPE Morpheus Enterprise to communicate with it via WinRM so the Hyper-V private cloud is ready to be configured. Create a group and then create a HPE Morpheus Enterprise cloud for Hyper-V. Populated the information as show in Figure 1: specific for the environment being configured.
+
+![../../../_images/hyperv1_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-23A922A0-C860-4705-AA64-BF5363B4B77A-high.png)
+
+NOTE
+
+The working path, vm path, and disk path should be created on the Hyper-V host by the Hyper-V administrator. If these paths are not created they will need to be setup and the Hyper-V settings will need to adjusted to reference them.
+
+![../../../_images/hyperv2_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F3DBACFA-EE94-4CE0-AF6F-D79405736F55-high.png)
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Hyper-V or create a new one. These are managed from the Admin > Plans& Pricing section.
+
+![../../../_images/hyperv3_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F6FDCC9D-AFEE-4EF5-B32C-A8B200171F83-high.png)
+
+## Docker
+
+So far this document has covered how to add the Hyper-V cloud integration and has enabled users the ability to provision virtual machine-based instances via the Add Instance catalog under the Provisioning menu. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into Hyper-V (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there click + ADD CLUSTER to add a Hyper-V Docker Host. A cluster is created when adding Docker hosts, even when only one host is needed.
+
+HPE Morpheus Enterprise views a Docker host just like any other hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Admin | Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..bb83cff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 196,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..26127e2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..2884888
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 187,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..2ee05f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json b/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
new file mode 100644
index 0000000..0e71c88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+  "title": "Deployment",
+  "ordinal": 479,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md b/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
new file mode 100644
index 0000000..f22ebd8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
@@ -0,0 +1,6 @@
+# Deployment
+
+**Subtopics**  
+
+- **[Git](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html)**
+- **[Github](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json b/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
new file mode 100644
index 0000000..034ac31
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+  "title": "Instances",
+  "ordinal": 83,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md b/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
new file mode 100644
index 0000000..feeff07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
@@ -0,0 +1,26 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self service features and spinning up both VMs and containers. In HPE Morpheus Enterprise it may be advisable to cover the definition of a few terms used within the application so as to reduce confusion. These concepts are also covered in greater detail in the [Provisioning Concepts](https://docs.morpheusdata.com/en/latest/provisioning/concepts/concepts.html) section.
+
+Instance
+:   A set of containers or virtual machines that can correlate to a single horizontally-scalable entity or a service suite, like a database. It is important to note that an Instance can contain one or more containers/VMs depending on the Instance type and configuration.
+
+Container
+:   Typically a docker container provisioned via a HPE Morpheus Enterprise Docker host.
+
+Virtual Machine
+:   A virtualized compute server provisioned onto various hypervisor hosts.
+
+The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, instance type, or category.
+
+NOTE
+
+Instances listed are determined by group access and role permissions. When filtered to show Instances of “All Statuses”, any Instances which are in a state of pending removal due to a delayed delete policy in place are not shown under this filter. Instead you must filter for “Pending Removal” to see these Instances and prevent deletion, if desired.
+
+The Instance list contains important information about each instance, including the instance name, environment tag, instance type icon, IP address and port info, Instance version, the number of virtual machines or containers in the instance, the group the instance is in, and the cloud or clouds the instance is in.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html)**
+- **[Instance Details](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json b/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
new file mode 100644
index 0000000..bac4fab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+  "title": "Components",
+  "ordinal": 7,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html",
+  "topic_cluster": {
+    "clustering_title": "Components",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md b/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
new file mode 100644
index 0000000..20686cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
@@ -0,0 +1,13 @@
+# Components
+
+The Appliance Server automatically installs several components for the operation of HPE Morpheus Enterprise. This includes:
+
+- RabbitMQ (Messaging)
+- MySQL (Logistical Data store)
+- Opensearch (Logs / Metrics store)
+- Tomcat (HPE Morpheus Enterprise Application)
+- Nginx (Web frontend)
+- Guacamole (Remote console service for clientless remote console)
+- Check Server (Monitoring Agent for custom checks added via UI)
+
+All of these are installed in an isolated way using chef zero to `/opt/morpheus`. It is also important to note these services can be offloaded to separate servers or clusters as desired. For details check the installation section and high availability.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..2c0ebe6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 474,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..32b9f4c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,591 @@
+# VMware vCenter
+
+## Overview
+
+VMware is a very common cloud integration choice supported by HPE Morpheus Enterprise . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so HPE Morpheus Enterprise covers a broad feature set in vCenter.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Affinity Groups
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
+
+## VMware Permissions
+
+When integrating VMware vCenter with HPE Morpheus Enterprise, users must supply credentials for a vCenter account and HPE Morpheus Enterprise will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that HPE Morpheus Enterprise can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict HPE Morpheus Enterprise only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a HPE Morpheus Enterprise Cloud integration.
+
+### Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my HPE Morpheus Enterprise integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
+
+### Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows HPE Morpheus Enterprise to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in HPE Morpheus Enterprise, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, HPE Morpheus Enterprise will look into this folder to onboard VMware images into HPE Morpheus Enterprise.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
+
+### Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in HPE Morpheus Enterprise without running into permissions errors.
+
+## Creating a HPE Morpheus Enterprise VMware Image
+
+HPE Morpheus Enterprise comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within HPE Morpheus Enterprise.
+
+NOTE
+
+A HPE Morpheus Enterprise appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple HPE Morpheus Enterprise Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via HPE Morpheus Enterprise.
+
+## Creating a Windows Image
+
+### Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
+
+### Image Preparation
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+#### Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and HPE Morpheus Enterprise Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+#### Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
+
+## Creating a CentOS/RHEL 7 Image
+
+### About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+### Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within HPE Morpheus Enterprise , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
+
+### Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+## Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+### Prepare The New CentOS 8/RHEL8 Image
+
+#### Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
+
+### SELinux Settings
+
+#### About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+#### Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
+
+### Network Interfaces
+
+#### About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+#### Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
+
+### Final VMWare Tasks
+
+#### Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the HPE Morpheus Enterprise side
+4. Refresh the HPE Morpheus Enterprise Cloud to allow the new template to sync
+
+## Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
+
+## A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json b/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
new file mode 100644
index 0000000..e9dc772
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+  "title": "Overview",
+  "ordinal": 202,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md b/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
new file mode 100644
index 0000000..034a7d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
@@ -0,0 +1,9 @@
+# Overview
+
+The OpenShift integration adds a new Cluster type, which can be added to HPE Morpheus Enterprise from the Clusters list page (Infrastructure > Clusters). Once a pre-existing OpenShift cluster is integrated, HPE Morpheus Enterprise can onboard any currently-running virtualized workloads along with the cluster hosts, network objects, storage objects, and virtual images needed to provision additional virtualized workloads. In addition to a new Cluster type, the OpenShift integration adds a new Instance Type to the provisioning wizard, which is used to provision new Instances to any integrated Clusters.
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise and is not part of the product by default. Information on accessing the plugin and adding it to the HPE Morpheus Enterprise appliance is included in a subsequent section.
+
+NOTE
+
+The OpenShift integration with HPE Morpheus Enterprise is currently limited to support of virtualized workloads only. There is not currently support for container-based workloads.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json b/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
new file mode 100644
index 0000000..5e000a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+  "title": "Policies",
+  "ordinal": 314,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html",
+  "topic_cluster": {
+    "clustering_title": "Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md b/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
new file mode 100644
index 0000000..83e5849
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
@@ -0,0 +1,8 @@
+# Policies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html)**
+- **[Creating Policies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json b/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
new file mode 100644
index 0000000..002232f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+  "title": "Workloads: Instance Usage",
+  "ordinal": 68,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md b/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
new file mode 100644
index 0000000..8e59914
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Usage
+
+![../_images/10instanceusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-70A9C315-58C0-4BF7-94E0-3F370A17D1E4-high.png)
+
+The Instance Usage dashboard shows Instance counts, resource utilization, and cost breakdowns by Cloud. Administrators can set filters to limit the workloads that are considered for dashboard analysis and then see the results given by Cloud groupings.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Usage List
+
+All Clouds represented in the dashboard are listed here. For each Cloud, we see the total Instance count, total memory allotted, total storage allotted, total CPU cores, and the total price.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json b/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
new file mode 100644
index 0000000..bb73ebc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+  "title": "HA Installation Overview",
+  "ordinal": 17,
+  "parent_title": "Installation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html",
+  "topic_cluster": {
+    "clustering_title": "HA Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md b/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
new file mode 100644
index 0000000..94b277a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
@@ -0,0 +1,47 @@
+# HA Installation Overview
+
+HPE Morpheus Enterprise provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability (HA) configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the HPE Morpheus Enterprise HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the HPE Morpheus Enterprise appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Messaging Tier. Each of these tiers have their own recommendations for High availability deployments.
+
+IMPORTANT
+
+This is a sample configuration only. Customer configurations and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment.
+
+## Application Tier
+
+The application tier is easily installed with the same apt or yum repository package that HPE Morpheus Enterprise is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. They can be configured across all regions and placed behind a central load-balancer or geo-based load balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is shared storage, which is necessary when it comes to maintaining deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. Alternatively, a simple NFS cluster can also be used to handle the shared storage structure. Alternatively, supported (Platform as a Service) PaaS offerings can be used that provide a NFS compatible shared storage, eliminating the need to manage the underlying infrastructure.
+
+## Transactional Database Tier
+
+The Transactional Database tier consists of a MySQL compatible database. It is recommended that a lockable clustered configuration be used, such as a Galera cluster, which can also provide high availability. Alternatively, supported PaaS offerings can be used that provide a mySQL compatible database, eliminating the need to manage the underlying infrastructure.
+
+## Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an Opensearch cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a java based system and does require a sizable chunk of memory for larger data sets. Alternatively, supported PaaS offerings can be used that provide an Opensearch compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. Alternatively, supported PaaS offerings can be used that provide a RabbitMQ compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## HA Installation Architectures
+
+3-Node HA (Recommended)
+:   In this architecture, all tiers are deployed on three machines by HPE Morpheus Enterprise during the installation, with the exception of the Transactional Database Tier. This provides HA not just for the HPE Morpheus Enterprise Application Tier but all underlying tiers that support HPE Morpheus Enterprise. The Transactional Database Tier will remain external, either as a separate cluster or PaaS, following the supported services. An external MySQL cluster must still be set up outside of the HPE Morpheus Enterprise app nodes.
+
+Distributed HA
+:   In this architecture, the tiers do not need to reside on the same machines, each can be hosted by a supported cluster or PaaS offering. This provides flexibility and reuse of already existing technologies such as RabbitMQ or Opensearch. Each tier should be architected to provide HA following the vendor’s documentation, to ensure no downtime for the HPE Morpheus Enterprise Application Tier.
+
+## Supported PaaS Offerings
+
+The Morpheus Application Tier can be deployed to any public or private cloud. Morpheus has underlying technologies that support the Application Tier, which can be automatically installed and embedded on the applications nodes. Alternatively, the services can be provided externally and not be embedded. Many cloud providers have Platform as a Service (PaaS) offerings of these underlying technologies but some are not native or don’t provide the performance required. Below is a list of PaaS offerings that are supported to be used for Morpheus:
+
+Table 1. PaaS Offering Support
+
+       | Cloud | Messaging (RabbitMQ) | Log (Opensearch) | Database (mySQL) | Shared Storage (NFS) |
+| --- | --- | --- | --- | --- |
+| AWS | Amazon MQ | Amazon OpenSearch | Amazon Aurora | Elastic File System |
+| GCP | N/A | N/A | mySQL Instance | Cloud Filestore |
+| Azure | N/A | N/A | N/A | Storage Account |
+| OCI | N/A | N/A | N/A | N/A |
+| Alibaba | N/A | N/A | N/A | N/A |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json b/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
new file mode 100644
index 0000000..92a4f44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+  "title": "Upgrading Overview",
+  "ordinal": 21,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md b/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
new file mode 100644
index 0000000..454b217
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
@@ -0,0 +1,190 @@
+# Upgrading Overview
+
+IMPORTANT
+
+Known issue with embedded Opensearch upgrade: When upgrading to v5.4.8+, v5.4.9 or v5.5.1, there is a potential issue with embedded Opensearch clustering on rolling upgrades and existing data migration for all embedded Opensearch architechtures. Refer to the Release Notes for additional informaiton.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Upgrade Requirements
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and VM node packages from the package-repo when appliance free space is needed.
+
+IMPORTANT
+
+BACKUP YOUR DATABASE before the upgrade! You can use the [appliance backup job in Morpheus](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#create-a-backup-job), then [rollback and restore your appliance](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#restoring-an-appliance-from-backup) if needed. Make sure you download the backup before you do the upgrade!
+
+- For firewall/proxy/acl considerations, the domain for Appliance, Supplemental and Agent packages was changed recently to <https://downloads.morpheusdata.com> from <https://downloads.gomorpheus.com>. Please update ACL’s to allow access to <https://downloads.morpheusdata.com> when necessary.
+
+### v8.1.0 Compatibility & Breaking Changes
+
+When installing and upgrading to HPE Morpheus Enterprise v8.1.0, refer to the following to ensure compatibility.
+
+#### Breaking Changes
+
+- 7.0.8, 8.0.0: On first ui startup after upgrade, HPE Morpheus Enterprise will normalize all IPv6 records within HPE Morpheus Enterprise-type pools. There will be a warning in appliance logs warning how many records will be normalized. This takes between 5-15 minutes per 1m records
+- 7.0.8, 8.0.0: Updated the AccountUsage table in the appliance database to accept LONGTEXT data type to prevent data from oversetting the table in specific scenarios. Note that this schema change will take time for databases with large numbers of account usage records
+- 6.3.0: Version 6.3.0 is the first version to require Plugin API 1.0.0+. Small changes will need to be made in order to make plugins created for prior versions of HPE Morpheus Enterprise compatible with 6.3.0+. See the [related article in our KnowledgeBase](https://support.morpheusdata.com/s/article/Making-plugins-compatible-with-Morpheus-6-3-0?language=en_US) on the small changes that will need to be made to ensure plugin compatibility
+- 6.2.2, 6.0.7 v8.0.7 contains embedded MySQL v8 upgrade when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1. BACKUP YOUR DATABASE PRIOR TO UPGRADE when using embedded MySQL (all-in-one appliances)
+- 6.2.2, 6.0.7 Minimum v6.x required to upgrade to v8.0.7 for environments using embedded RabbitMQ. Environments running 5.5.x or earlier using embedded RabbitMQ must upgrade to v6.0.0 - v6.0.6, or 6.1.0 - 6.2.1 prior to upgrading to v8.0.7
+- 6.2.2, 6.0.7 Rolling upgrades for HA environments using embedded RabbitMQ and/or embedded Elasticsearch services are not supported when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1
+- 6.1.1 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records when upgrading from any version other than 6.0.3
+- 6.1.1 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades from any version other than 6.0.3 are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.1.1: NSX-V networking integration support is removed and no longer supported as of HPE Morpheus Enterprise 6.1.1
+- 6.0.3 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records.
+- 6.0.3 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.0.0: NSX-V support is deprecated though still supported as of HPE Morpheus Enterprise 6.0.0. It will be removed and unsupported in 6.1.1 and higher.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, many third party integrations have been moved out of the core installer package and converted to HPE Morpheus Enterprise plugins. As a result, during the upgrade process your appliance will need to be able to access share.morpheusdata.com, the online repository for all HPE Morpheus Enterprise plugins. Where this is not possible, users may instead apply the supplemental installer package which is also available at HPE Morpheus Enterprise Hub alongside the main installer package.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, older service specific system provided Instance Types and Layouts were deprecated and disabled. Updating to 6.0.0 will not affect existing Instances that are associated with the disabled types, however existing catalog item configurations, blueprints and api requests that use disabled Instance Types and layouts will need to be updated.
+- 5.5.2: VM Node Packages: Due to build java version requiremnets, the i386.deb and i386.rpm (32-bit) VM Node Packages can no longer be updated, and remain on v3.2.9.
+- 5.4.12: Guacd: Guacd is now complied iwth libssh2-1.10.0 on all platforms. Appliances on SLES15 may need openssl-devel manually installed for guacd to succesfully compile.
+- 5.4.12: Session Manager: Morpheus features a new session manager that was necessary in order to resolve expiring connections from the agents due to a Spring framework update. This new session manager no longer requires Sticky Sessions and they can now be turned off at the load balancer if so desired. However, keeping them on is totally reasonable as well as it reduces overall system load. Rolling restarts no longer kick you out of your session if sticky sessions are off as it distributes your session data across the morpheus nodes in an HA environment. Additionally, overall system load is reduced as a result of the new session manager.
+- 5.4.9: HPE Morpheus Enterprise 5.4.9 adds the “Provisioning: State” Role permission. This permission determines access to the State tab for Terraform-backed Instances and is set to “None” by default. On upgrade, only System Admin users will be able to see the State tab for these Instances. For other users who should have this access, edit their Roles to include “Provisioning: State” permissions.
+- 5.4.5: Warning: Database indexes added for account\_usage and metadata\_tag tables. Customers with very large account\_usage and/or metadata\_tag tables (10 million+) may experience slower initial morpheus-ui loading time after upgrading to 5.4.5, as well as additional database load.
+- 5.4.5: ‘AVI Load Balancer’ renamed to ‘NSX Advanced Load Balancer’
+- 5.4.5: Cloud Types disabled by default: Dell, HPE (NOT HPE Oneview), Supermicro and Cloud Foundry. Users would still be able to re-enable this clouds in the appliance settings. Does not affect existing Clouds.
+- 5.4.5: A10 Load Balancer type has been disabled, and will no longer be an option when adding new Load Balancers. This does not affect existing Load Balancers.
+- 5.4.5: HPE Morpheus Enterprise Cluster type “Combo Cluster” renamed to “KVM/Docker Cluster”
+- 5.4.5: Greenfield managed vm’s (provisioned with HPE Morpheus Enterprise) can no longer be deleted in HPE Morpheus Enterprise without removing the actual vm/infrastructure. Restriction does not apply to brownfield vm’s that have been converted to managed.
+- 5.4.4: The Venafi and AppDynamics integrations are deprecated in v5.4.4 and will be removed in v5.4.5. AppDynamic will return as a plugin at a later date.
+- 5.4.4: The morpheus-ui logging configuration file has changed from logback.groovy to logback.xml in v5.4.4 (/opt/morpheus/conf/logback.xml). The logback.groovy file from previous versions can be removed, and any updates to logback.groovy will not result in any logging configuration changes.
+- 5.4.3: vCloud Director: Support for integrations with vCD 9 ended
+- 5.4.3: HPE Morpheus Enterprise Worker/Gateway v5.4.3 packages are now available. Existing Worker & Gateway nodes must be upgraded to v5.4.3 for compatibility with HPE Morpheus Enterprise v5.4.3 Appliances.
+- 5.4.2: vCloud Director: vCD 9.x will no longer be supported by Morpheus
+- 5.4.2: ServiceNow: Instance and Blueprint specific exposures will be removed from ServiceNow plugin support. More advanced configurations of Instances and Blueprints, in addition to Workflows, can be exposed utilizing Catalog Items
+- 5.4.2: After upgrading, it is recommended that you manually perform one “Daily” refresh Amazon Clouds to ensure availability of Amazon Service Plans for each region. To manually refresh a Cloud, navigate to Infrastructure > Clouds > (Selected Amazon Cloud) and select “Daily” from the REFRESH dropdown menu. If this is not done, HPE Morpheus Enterprise may not show Amazon Service Plans in the provisioning wizard until after Midnight UTC following the upgrade when the next automatic Daily sync would run.
+- 5.3.3: Support for OpenStack v2 Identity API is removed
+- 5.3.2+: The local code repository path moved from `/var/opt/morpheus/morpheus-ui/repo` to `/var/opt/morpheus/morpheus-local/repo` to reduce potential shared storage issues and performance restrictions. The reconfigure process creates the folders and sets the paths in application.yml, no manual intervention is needed unless symlinks exisit on `/var/opt/morpheus/morpheus-ui/repo/git` which will need to be removed prior to reconfiguring - 5.3.2+ The deprecated `/var/opt/morpheus/morpheus-ui/repo` path will be automatically deleted in a future release but can be manually recursively deleted at any time for storage reclamation.
+- 5.3.2+: Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+- 5.2.9: OpenStack v2 Identity API is deprecated as of v5.2.9 (and is removed as of v5.3.3)
+- 5.2.6, 5.3.1: Appliance & Agent java version updated to `8u292-b10`. jdk8u292 disables TLS 1.0 and 1.1 by default
+- 5.2.3+: `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repo access required for RHEL 8+ Appliances, replacing the previous PowerTools/powertools requirement
+- 5.2.1 & 4.2.5: API: Metadata: Metadata tags now referred to as `tags` and labels now referred to as `labels`. Previously metadata tags were referred to as `metadata` and labels were referred to as `tags`
+- 5.0.0+: When upgrading to 5.0.0+ from 4.x.x, any bearer tokens that have been generated are deleted which requires users to request new bearer tokens
+- 4.2.4: For appliances with externalized MySQL databases, due to MySQL deprecation of the “EDT” timezone you may need to update your database timezone to UTC or another compatible value. If this is not done, you will receive errors referencing timezone and HPE Morpheus Enterprise will not start. HPE Morpheus Enterprise should handle this change automatically for all-in-one appliances.
+- 4.2.1+: Tasks: Python: Virtual environment are now used for Python Tasks. Note: `virtualenv` is required on all Appliance App nodes
+- 4.2.1+: Puppet: HPE Morpheus Enterprise integration now supports version 6+. Puppet versions prior to 6 are no longer supported
+- 4.2.1+: Clouds: VirtualBox, VirtuSteam, and MetaCloud Cloud Types are no longer supported or available
+- 4.2.1+: Appliance: OS: Ubuntu 14.04 has reached its end of life (EOL) and is no longer supported as a Morpheus Appliance Host Operating System. Any HPE Morpheus Enterprise Appliance running on 14.04 must be upgraded to 16.04, 18.04, 20.04, 22.04 or 24.04 BEFORE upgrading to 4.2.1+. Upgrades on 14.04 will not succeed
+
+#### HPE Morpheus Enterprise Application OS
+
+HPE Morpheus Enterprise can be installed on the following platforms. Please note the table below is for HPE Morpheus Enterprise Application OS support, not HPE Morpheus Enterprise Agent OS Support.
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| CentOS | 7.x (deprecated). 8.x (stream) 9.x (stream) |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+
+#### Services
+
+##### v8.1.0 Service Versions & Compatibility
+
+Table 2. v8.1.0 Service Versions and Compatibility
+
+      | Service | Compatible Branch | Current Installer Version | Updated in v8.1.0 |
+| --- | --- | --- | --- |
+| Plugin API | 1.3.0 | 1.3.0 |  |
+| Morpheus Worker | 5.4.8+ |  |  |
+| MySQL | v8.0 | v8.0.40 | Yes |
+| MySQL (FIPS) | v8.0 | v8.0.36 |  |
+| OpenSearch | v8.9+ | v8.15.5 |  |
+| RabbitMQ | v3.5-3.13 | v3.13.7 |  |
+| Tomcat |  | v9.0.106 |  |
+| Nginx |  | v1.26.2 |  |
+| OpenSSL |  | 1.1.1w, 1.0.2u (FIPS) |  |
+| Java |  | 17.0.14+7 |  |
+| Java (MacOS Agent) |  | 11.0.14+9 |  |
+
+##### HPE Morpheus Enterprise Agent & Node Package Versions
+
+Table 3. v8.1.0 Agent & Node Package Versions
+
+     | Package | Version | v8.1.0 changes from v8.0.13 |
+| --- | --- | --- |
+| Morpheus Node and VM Node Packages | 3.3.11 | Updated to 3.3.11 |
+| Morpheus Linux Agent | v3.1.0 | Updated to v3.1.0 |
+| Morpheus Windows Agent | v2.6.1.0 | No changes |
+| Morpheus macOS Agent | v2.4.0 | No changes |
+
+##### HPE Morpheus Enterprise Software Upgrade Paths
+
+Depending on the specific changes from version to version, HPE Morpheus Enterprise may support rolling upgrades for multi-node HA appliances. For some version hops, specific changes such as database schema modifications may make the upgrade unsuitable for a rolling upgrade. Use this table to confirm if a rolling upgrade will be possible in each case. Instructions for both rolling and non-rolling upgrades are contained in this documentation.
+
+Table 4. v8.1.0 Upgrade Paths
+
+                   | From Version | To 8.0.1 | To 8.0.2 | To 8.0.3 | To 8.0.4 | To 8.0.5 | To 8.0.6 | To 8.0.7 | To 8.0.8 | To 8.0.9 | To 8.0.10 | To 8.0.11 | To 8.0.12 | To 8.0.13 | To 8.1.0 | To 8.1.1 | To 8.1.2 |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Versions 6.0.0 - 7.0.11 | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.0 | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.1 | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.2 | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.3 | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.4 | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.5 | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.6 | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.7 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.8 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.9 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.10 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.11 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.12 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.13 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.1.0 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ |
+| 8.1.2 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ |
+
+#### Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 5. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json b/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
new file mode 100644
index 0000000..66fe34c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+  "title": "Puppet",
+  "ordinal": 378,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html",
+  "topic_cluster": {
+    "clustering_title": "Puppet",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md b/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
new file mode 100644
index 0000000..da0f82e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
@@ -0,0 +1,61 @@
+# Puppet
+
+Each HPE Morpheus Enterprise Puppet integration ties to a specific Puppet Master and makes it easy to install the Puppet Agent onto target Instances and Servers. Once integrated, we can trigger the agent installation by creating Puppet Agent Install Tasks through HPE Morpheus Enterprise automation or at provision time when spinning up instances in Clouds associated with a Puppet integration.
+
+## Add Puppet Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click + NEW INEGRATION
+3. Select Integration type “Puppet”
+4. Populate the following fields 
+
+   - Name: A friendly name for this Puppet integration in HPE Morpheus Enterprise
+   - Enabled: When marked, this Puppet integration will be available to users at provision time and when creating Tasks
+   - Puppet Master (Hostname): The resolvable DNS name to the Puppet Master, communicating on port 443 by default
+   - Allow Immediate Execution: Yes or No (See additional details below)
+5. Click SAVE CHANGES 
+
+   ![../../_images/new_puppet_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-89930173-D087-4C3D-AD78-83569C611401-high.png)
+
+### Allow Immediate Execution
+
+When adding or editing a Puppet integration, users have the option to “Allow Immediate Execution”. Using this feature will connect to the Puppet Master after the Puppet Agent is installed and force configuration application immediately. This is an optional convenience feature, if it’s not used, the Puppet Master will still apply configuration to the node on its own schedule. Using this feature requires supplying SSH credentials. If you do not wish to provide SSH credentials to HPE Morpheus Enterprise select “No” to opt out of this feature and they do not need to be provided.
+
+## Associating a Puppet Integration with a Cloud
+
+### About this task
+
+By associating a Puppet Integration with a Cloud, users are able to automatically install the Puppet Agent, select a Puppet environment, and supply a Puppet Node Name at provision time. The integration association is made when adding or editing a Cloud integration in HPE Morpheus Enterprise.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Identify the Cloud to associate with Puppet and edit it by clicking on the pencil icon at the right end of the row
+3. In the EDIT CLOUD modal, expand the Advanced Options section
+4. In the CONFIG MANAGEMENT dropdown, choose the Puppet integration
+5. Save changes to the Cloud integration
+
+## Creating Puppet Agent Install Tasks
+
+### About this task
+
+Puppet Agent Install Tasks automate the process of installing the Puppet Agent, selecting the Puppet environment, and supplying the Puppet Node Name. We can run this Task on-demand as needed for individual Instances or servers or add them to workflows to build a Puppet Agent installation step into larger automation suites.
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Select the Tasks tab
+3. Click + ADD
+4. From the “Type” field, select Puppet Agent Install
+5. Complete the fields as needed to target a specific Puppet Master and to identify Puppet environment and node names
+6. Save changes
+
+### Results
+
+![../../_images/puppet_task.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F59908B8-FAEC-4C47-859E-087396FDCB98-high.png)
+
+## Installing Puppet Agent at Provision Time
+
+With a Puppet integration associated with a Cloud (as described above), users can opt to install the Puppet Agent at provision time. When provisioning into an associated Cloud, a new “Puppet” section will appear on the CONFIGURE tab of the provisioning wizard. Here users can select a specific Puppet Master, select the Puppet environment, and select a Puppet node name. During provisioning, the Puppet Agent will be automatically installed and configured for the selected Master.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json b/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
new file mode 100644
index 0000000..4cc8b48
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+  "title": "Provisioning Concepts",
+  "ordinal": 81,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md b/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
new file mode 100644
index 0000000..70f85a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
@@ -0,0 +1,31 @@
+# Provisioning Concepts
+
+HPE Morpheus Enterprise is a powerful infrastructure-agnostic Cloud Application Management Platform. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+HPE Morpheus Enterprise refers to itself as a CAMP (Cloud Application Management Platform) as opposed to a (Cloud Management Platform). While that may seem minor, it actually is a big deal. Many CMP applications start at the IaaS layer and work up to the application layer (often needing additional PaaS architectures to fill out the model). HPE Morpheus Enterprise was designed from a middle-ground perspective. As such, some concepts are a bit different. This provides a more complete platform that allows for greater capabilities out of the box as will be seen when these concepts are covered.
+
+## Instances
+
+HPE Morpheus Enterprise starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in Amazon AWS. In HPE Morpheus Enterprise, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines or several Docker containers.
+
+For example, in the HPE Morpheus Enterprise Instance wizard, MongoDB is an option and contains several Instance configurations. One of these configurations is a full MongoDB cluster consisting of either seven virtual machines or seven Docker containers. Rather than representing these directly as seven individual “instances”, HPE Morpheus Enterprise groups them together into a singular Instance of a service that contains multiple containers or virtual machines within it. This even allows for Instance actions that can be performed to expand capacity on an Instance (either horizontally or vertically). In the past, a database server may have been representative of a singular server, but this model has drastically changed in a big data world. This same concept also can apply to something like a simple Apache web server where there are 10 copies of a web server which are horizontally scaled out to handle traffic.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. HPE Morpheus Enterprise simply helps simplify the management model for tracking these services.
+
+## Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, HPE Morpheus Enterprise will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance. Node is just a generic naming representation when referring to these types of items. The public HPE Morpheus Enterprise developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was since updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as Virtual Machines. In fact, one can even think of a Docker Host as a Hypervisor (which we do).
+
+## Hosts / Servers
+
+This concept is mostly tailored to users of HPE Morpheus Enterprise who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of HPE Morpheus Enterprise that is quite powerful. This singular concept is what allows HPE Morpheus Enterprise to ingest “brownfield” environments. We do not need to start clean. HPE Morpheus Enterprise can be integrated into existing environments and manage existing virtual machines. The way HPE Morpheus Enterprise does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of HPE Morpheus Enterprise and the HPE Morpheus Enterprise Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
+
+## Apps
+
+On top of all the previous concepts, HPE Morpheus Enterprise provides an Apps layer. An App is a collection of Instances linked together via application tiers. Tiers allow the user to define segregated sections of connectivity between the various elements (Instances) within an application. Once these Instances are all linked together in an application concept, this may affect Instance environments and provide service discovery capabilities for them to cross connect. There are several service discovery aspects within HPE Morpheus Enterprise as well as integrations with services.
+
+## App Blueprints
+
+An App Blueprint allows a user to define an application structure for easy reproducibility and deployment into various environments. They can be used to mix and match various Instance types to provision an application dependent on multiple layers of services.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json b/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
new file mode 100644
index 0000000..00a4f78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+  "title": "Credentials",
+  "ordinal": 236,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md b/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
new file mode 100644
index 0000000..c94eaea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials can be securely stored internally on the appliance or stored in an external Cypher integration, more information about setting up and integrating with an external Cypher store are in the next section. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in HPE Morpheus Enterprise UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json b/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
new file mode 100644
index 0000000..3328672
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+  "title": "Plans",
+  "ordinal": 288,
+  "parent_title": "Plans",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md b/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
new file mode 100644
index 0000000..99d9776
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
@@ -0,0 +1,118 @@
+# Plans
+
+Plans types include Service Plans and Price Plans. Service Plans determine the memory, storage and cores configuration during provisioning and reconfigure.
+
+## Service Plans
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
+
+### Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in HPE Morpheus Enterprise
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. See [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
+
+### Create Service Plan
+
+#### About this task
+
+HPE Morpheus Enterprise offers a few distinct types of service plans, each with different data fields to track and valid Price Set types which can be associated. For more on Service Plan configuration, see the preceding section.
+
+Price Sets can be added to the Plan at creation time so often it makes sense to create the Prices and associate them with Price Sets before creating the Plan. Additional instructions for creating Prices and Price Sets are in the next section. With the Price Sets ready, continue with the instructions below to create Price Plans of various types.
+
+#### Procedure
+
+1. Navigate to Administration > Plans & Pricing (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. On the Price Sets tab, associate all relevant Price Sets with the Plan. The desired Price Sets must already exist. If needed, you may save the Plan at this point and come back to associate Price Sets later
+5. Click SAVE CHANGES
+
+### Add Price Set(s) to Plan
+
+#### Procedure
+
+1. Select a Price Unit to list available Price Sets which have the selected Price Unit. Available Price Sets are filtered to show only those which are relevant for the Plan type you’ve selected
+2. Select a Price Set from the list and click + ADD
+3. Add additional Price Sets if desired (multiple Price Sets can be associated with a Plan)
+4. Added Price sets can be removed from a Plan by clicking the 🗑 icon
+5. Once all Price Sets have been added, select SAVE CHANGES
+
+#### Results
+
+TIP
+
+The +ADD button must be clicked after selecting a Price Set or it will not be added to a Plan.
+
+### Service Plan Permissions
+
+Group and Tenant Access permissions determine availability of a Service Plan.
+
+- Group Access determines what Groups the Service Plan will be available in for Provisioning and Reconfigure.
+- Group Access settings only apply to the Tenant they are configured in, as Groups are not multi-tenant.
+- For multi-tenant environments, the Master Tenant can set Tenant Permissions to determine if the Service Plan is available to all Tenants (public visibility) or assign the Service Plan to one or multiple Tenants.
+
+### Removing Plans
+
+Plans can be removed by navigating to the Service Plans list page (Administration > Plans & Pricing > Plans), opening the ACTIONS menu for a Plan, and then selecting “Remove”. Removing a Plan makes it no longer visible, however, it does not hard delete the Plan as the record must remain for any existing associations’ usage and price tracking. Synced Plans should be deactivated rather than removed.
+
+## Load Balancer Price Plans
+
+Load Balancer Price Plans configure pricing for Load Balancers and Load Balancer Virtual Servers.
+
+Load Balancer Price Plan Configuration:
+
+- **NAME:** The name of the Load Balancer Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **LOAD BALANCER TYPE:** Select the load balancer type the Price Plan should be associated with
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Load Balancer Price Sets may be associated with Load Balancer-type and Load Balancer Virtual Server-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Virtual Image Price Plans
+
+Virtual Image Price Plans configure pricing for Virtual Images. Pricing is associated per Price and Price Set configurations, but in general applies to Images with location records in the Price Plans specified Cloud type. Virtual Image Price Plans are for setting pricing for Virtual Image storage, not for adding pricing to resources that use Virtual Images associated with Virtual Image Price Plans. Virtual Image Price Plans do not apply to uploaded Virtual Images that have not been copied to a location in the specified Cloud type yet.
+
+Virtual Image Price Plan Configuration:
+
+- **NAME:** The name of the Virtual Image Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Virtual Image Pricing applies to Virtual Images with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Virtual Image Price Sets may be associated with Storage-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Snapshot Price Plans
+
+Snapshot Price Plan Configuration:
+
+- **NAME:** The name of the Snapshot Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Snapshot Pricing applies to Snapshots with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Snapshot Price Sets must have at least one Storage-type Price but may also have Datastore-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json b/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
new file mode 100644
index 0000000..1db270e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+  "title": "Navigation Updates",
+  "ordinal": 529,
+  "parent_title": "See Also",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html",
+  "topic_cluster": {
+    "clustering_title": "Navigation Updates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md b/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
new file mode 100644
index 0000000..cea3df9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
@@ -0,0 +1,38 @@
+# Navigation Updates
+
+[  ](https://www.youtube.com/embed/B46qgEwoblY)
+
+v8.0.7 contains major changes to the UI navigation structure. The following table lists updated paths for affected sections.
+
+NOTE
+
+API endpoints are not affected by the UI navigation changes
+
+Table 1.
+
+     | Target | Old Path | New Path |
+| --- | --- | --- |
+| Blueprints | provisioning > blueprints | library > blueprints |
+| Automation | provisioning > automation | library > automation |
+| Tasks | provisioning > automation > tasks | library > automation > tasks |
+| Workflows | provisioning > automation > workflows | library > automation > workflows |
+| Executions | provisioning > automation > executions | provisioning > executions |
+| Scale Thresholds | provisioning > automation > scale thresholds | library > automation > scale thresholds |
+| Power Scheduling | provisioning > automation > power scheduling | library > automation > power scheduling |
+| Execute Scheduling | provisioning > automation > execute scheduling | library > automation > execute scheduling |
+| Automation Integrations | provisioning > automation > integrations | library > integrations |
+| Security Packages | provisioning > jobs > security packages | library > templates > security packages |
+| Virtual Images | provisioning > virtualimages | library > virtualimages |
+| Library | provisioning > library | library |
+| Instance Types | provisioning > library > instance types | library > blueprints > instance types |
+| Layouts | provisioning > library > layouts | library > blueprints > layouts |
+| Node Types | provisioning > library > node types | library > blueprints > node types |
+| Option Types (Inputs) | provisioning > library > option types | library > options > inputs |
+| Option Lists | provisioning > library > option lists | library > options > option types |
+| File Templates | provisioning > library > file templates | library > templates > file templates |
+| Scripts | provisioning > library > scripts | library > templates > script templates |
+| Spec Templates | provisioning > library > spec templates | library > templates > spec templates |
+| Cluster Layouts | provisioning > library > cluster layouts | library > blueprints > cluster layouts |
+| Catalog/Self Service | tools > selfservice | library > blueprints > catalog items |
+| Service Catalog | service catalog persona | provisioning > catalog& service catalog persona |
+| Logs | logs | monitoring > logs |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json b/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
new file mode 100644
index 0000000..f72679e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+  "title": "Getting started with HPE Morpheus Enterprise and VMware",
+  "ordinal": 361,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md b/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
new file mode 100644
index 0000000..afad186
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
@@ -0,0 +1,514 @@
+# Getting started with HPE Morpheus Enterprise and VMware
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of HPE Morpheus Enterprise with VMWare. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in HPE Morpheus Enterprise that is beyond the scope of this guide. For more, consult the complete HPE Morpheus Enterprise documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/4.1.0/getting_started/requirements/requirements.html#requirements). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a lab license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on HPE Morpheus Enterprise groups is [here](https://docs.morpheusdata.com/en/4.1.1/infrastructure/groups/groups.html#groups). A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![The new group dialog box showing a name for the group filled in](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with VMWare vCenter.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated vCenter cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “VMWARE VCENTER” and click the “NEXT” button.
+
+![The list of clouds available to integrate with, vCenter is selected](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-37B199A3-DCEC-41E4-AE0B-8BE8A37EA55B-high.png)
+
+On the “CONFIGURE” tab, we’re asked to set the initial connection strings into vSphere. The **API URL** should be in the following format: <https:/>/<URL>/sdk. The **USERNAME** should be in [user@domain](mailto:user%40domain) format.
+
+![The create cloud dialog box with relevant fields filled](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-670B6AE2-46C2-4917-A452-B8D72082823E-high.png)
+
+HPE Morpheus Enterprise allows vCenter clouds to be scoped to the **VDC** and **CLUSTER** or even the specific **RESOURCE POOL** if you choose. Once you’ve entered your URL and credentials, these dropdown menus will become populated.
+
+The **RPC MODE** setting determines how HPE Morpheus Enterprise will connect to VMs and make configuration and scripting calls if [Morpheus Agent](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent) is not installed. In a VMware environment, it is recommended to select **Vmware Tools** but WinRM/SSH are able to be used to configure the guest directly. If using WinRM, ensure it is configured on the virtual image, discusssed below.
+
+Additionally, we can opt to **INVENTORY EXISTING INSTANCES** to begin polling VMs for statistics and rightsizing recommendations as well as **ENABLE HYPERVISOR CONSOLE** to use native vSphere console with port 443 connectivity between HPE Morpheus Enterprise and ESXi hosts.
+
+To move on, expand the “Advanced Options” section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), and **AGENT INSTALL MODE**.
+
+![The advanced options section of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5564447E-D7BC-4DE8-832D-D63909A3B49E-high.png)
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+![The group tab of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-21078778-ABE2-4EC9-A236-0F982B727DDB-high.png)
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first VMware cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our VMware cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in vCenter. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise.
+
+![The list of synced resource pools in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5E044CF2-DC63-48CA-BFE5-FB99E8B3CA6B-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![The edit resource pools dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12509E33-3DEA-47DD-8838-3D4B76599043-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “RESOURCES” tab to the “DATA STORES” tab on our cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![The list of synced data stored in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9D16EAEE-4391-4B7B-B0FA-D46DB90A3E59-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific groups. This ensures that the members of each group are only able to consume the data stores they should have access to.
+
+![The edit data stores dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-14F14768-224B-4188-A052-48C37F755907-high.png)
+
+## Configuring Folders
+
+Still within the “RESOURCES” tab, within the “FOLDERS” subtab we see the folders discovered from the vCenter Cloud. Edit folder configurations by selecting “ACTIONS” from the end of the row, then clicking “Edit”. Consider the following configurations for specific folders:
+
+- **DEFAULT:** If selected, this folder will be pre-selected when provisioning new Instances to this Cloud (See the Folder option on the CONFIGURE tab of the Instance provisioning wizard)
+- **IMAGE TARGET:** HPE Morpheus Enterprise will look in the image target folder(s) to onboard VMware images
+
+After saving the changes, you’ll see any folders set as default or image target indicated in the folders list.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![The list of configured neworks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+![The add IPAM integration dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a HPE Morpheus Enterprise-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, HPE Morpheus Enterprise will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, HPE Morpheus Enterprise will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![Creating a |morpheus|-type IP pool](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within a VMware cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain groups or tenants.
+
+![Viewing networks on the cloud detail page](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D8873C52-F566-49ED-AE8C-825EA4B169B1-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, HPE Morpheus Enterprise comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with images included in HPE Morpheus Enterprise by default in this guide but it’s important to discuss how to prep custom images as well.
+
+### Creating a Windows Image
+
+The following versions of Windows Server are supported:
+
+- 2008 R2
+- 2012
+- 2012 R2
+- 2016
+- 2019
+- 2022
+
+To start, create a new Windows VM in vCenter using a base version of your selected Windows build.
+
+NOTE
+
+It’s recommended to make the VMDK drive as small as possible for your purposes as this generally speeds cloning and deploy times. Morpheus provisioning and post-deploy scripts allow to to expand the drive to any size that you need.
+
+Once the VM is created, ensure VMware Tools is installed on the operating system. This will ensure the virtual machine can communicate correctly with vCenter but also if the cloud was configured to use `RPC MODE` of `Vmware Tools`, and the HPE Morpheus Enterprise agent is not installed, HPE Morpheus Enterprise can communicate with the virtual machine directly for tasks and other processes.
+
+NOTE
+
+If the cloud was configured to use `RPC MODE` of `SSH/WinRM`, it will be necessary to configure WinRM on the virtual machine. Ensure WinRM is allowed from your Morpheus appliance through the local Windows firewall. Also, run the following command to enable WinRM in the guest: `winrm quickconfig`
+
+Next, install .NET 4.5.2 or higher as a [requirement](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/agentInstallation.html#agent-install-requirements) for the Morpheus agent.
+
+Finally, choose a method that will be used to customize the operating system:
+
+- Guest Customization
+- Sysprep
+- Cloudbase-Init
+
+#### Using Guest Customization (Recommended)
+
+HPE Morpheus Enterprise can utilize the vCenter guest customizations feature, creating its own customization specification and applying it at deployment. There are no other changes needed in the guest operating system when using this method. Turn off the virtual machine and convert it to a template Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **VMware Guest Customization?** is checked.
+
+#### Using Windows Sysprep
+
+HPE Morpheus Enterprise can inject an unattend file via CD-ROM to override the default sysprep process when preparing a virtual machine. Run the following command from the guest operating system to sysprep the operating system: `C:\Windows\System32\sysprep /oobe /generalize /shutdown` The unattend file created on the virtual machine can be ignored, no changes will be needed. Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Sysprepped/Generalized Image?** is checked.
+
+NOTE
+
+If **VMware Guest Customization?** is enabled on the virtual image or if using static IP addresses or IP pools when provisioning, ensure a Sysprep has not been performed in the guest. In such cases, a guest customization will always be performed.
+
+#### Using Cloudbase-init
+
+IMPORTANT
+
+Some admins may struggle with using Cloudbase-Init, especially if they are not familiar with cloud-init (used in Linux). It is recommended to use either **Guest Customization** or **Windows Sysprep** if the admins are more famililar with those tools.
+
+HPE Morpheus Enterprise can inject a cloud-init file via CD-ROM to override the default sysprep process when preparing a virtual machine, if the Cloudbase-Init service is installed. Download Cloudbase-Init from <https://cloudbase.it> for your appropriate architecture. Run the installer and keep the default settings. Below is an example of the final settings page: ![Cloudbase-Init settings](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ABBCBC9E-8CE1-4EE2-B15D-EC25F255D11A-high.png) At the end of the installer, options will be available to sysprep and shutdown the virtual machine. Checkmark both boxes and click **Finish**: ![Cloudbase-Init sysprep](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-14880EC6-E2C4-486D-AEA8-D66AE8573877-high.png) Once started, the sysprep process should continue until the virtual machine shutsdown. ![Cloudbase-Init progress](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A52DA0FA-2608-4AE6-B741-DC4B98D23778-high.png) Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Is Cloud Init Enabled?** is checked.
+
+### Creating a CentOS/RHEL Image
+
+Create a new machine in vCenter and install a base version of your preferred Linux distro.
+
+NOTE
+
+If you are using cloud-init as part of your image, you will need to ensure your virtual machine has a cdrom.
+
+Before installing the operating system, set up a single ext or xfs partition without a swap disk. Next, install the distro applying any updates to the operating system or security updates. Once the operating system is running and updated, install the following:
+
+```
+```
+yum install cloud-init  
+yum install cloud-utils-growpart  
+yum install open-vm-tools  
+yum install git  
+yum install epel-release
+```
+```
+
+Set selinux to permissive as the enforced setting can cause problems with cloud-init:
+
+```
+```
+sudo vi /etc/selinux/config
+```
+```
+
+#### Cloud-Init
+
+We’ll get started by installing cloud-init using the following command:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+NOTE
+
+The above command will install some core dependencies for cloud-init and automation later as you work with your provisioned instances. For example, we install Git here as it is used for Ansible automation. If you had no plans to use Ansible, this installation could be skipped. The dracut-modules-growroot is responsible for resizing the root partition upon initial boot which was potentially adjusted during provisioning.
+
+One key benefit of using cloud-init is that we don’t have to lock credentials into the blueprint. We recommend configuring a default cloud-init user that will get created automatically when the VM is booted by cloud-init. We can define that default user in Administration > Settings > Provisioning > Cloud-Init
+
+#### Network Interfaces
+
+As of CentOS 7, network interface naming conventions have changed. You can check this by running ifconfig and noting that the primary network interface has some value similar to “ens2344”. The naming is dynamic and typically set based on hardware ID. We don’t want this to fluctuate when provisioning this blueprint in our VMware environments. To accomplish this end, we will rename the interface back to “eth0” using the steps below.
+
+First, adjust the bootloader to disable interface naming:
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The next step is to adjust network scripts in CentOS. Start by confiming the presence of a file called /etc/sysconfig/network-scripts/ifcfg-eth0. Once confirmed, run the following script:
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to confirm there is a new ifcfg-eth0 config created to replace the old config file. Confirm this config exists after running and if not you will have to build your own:
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+For more on CentOS/RHEL image prep, including additional configurations for specific scenarios, take a look at the [VMware image prep](https://docs.morpheusdata.com/en/4.1.1/integration_guides/Clouds/vmware/vmware_templates.html#gotchas) page in HPE Morpheus Enterprise Docs.
+
+#### Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Disable assignment of new styled names for network interfaces (instead of `ens###` they will be `eth#`):
+
+```
+```
+sudo sed -i -e 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"/' /etc/default/grub
+```
+```
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our vCenter cloud.
+
+Navigate to Provisioning > Instances. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![Selecting an instance type to provision](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the vCenter cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [here](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in Administration > Plans & Pricing.
+- **VOLUMES and DATASTORES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click “NEXT”.
+
+![The configure tab of the create instance dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B494FF9C-4564-4F58-B523-3D6661254037-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click “COMPLETE”.
+
+![Confirming the instance to be provisioned](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BD9754FE-0F3F-45CD-BE37-86185EF667BF-high.png)
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends on your environment and selections made when provisioning the instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisiioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+![Monitoring privisioning progress on the instance detail page](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6CD6B5F1-88DE-44D1-9E25-29FB61D81345-high.png)
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click “+ADD”.
+
+![Adding a new node type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: VMware
+- **VM IMAGE**: HPE Morpheus Enterprise Redis 3.0 on Ubuntu 14.04.3 v2
+
+NOTE
+
+Within the “VMware VM Options” section you should add anything that will always be used for this node, regardless of the specific deployment details. This can include LDAP Authentication, bash scripts that should run on installation, among other things.
+
+![Configuring options for the new node](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0C9573F1-448E-41A1-B2CD-B8F3D6111B7B-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![Adding a new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![Configuring the new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![Opening our newly created instance type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: VMware
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+![Configuring the new layout](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-70C1E76A-8246-418B-956B-D8542254955E-high.png)
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to Provisioning > Instances and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+![Searching for our custom instance type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-905B43B4-EABB-4271-A555-97203C7A87E5-high.png)
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+![Configuring the newlt created instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8D733786-5795-4A40-A81F-F832B79E3B71-high.png)
+
+As before when we manually provisioned an instance, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on your environment but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the privisioning process has completed, open the instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+![Confirming creation of the new instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C9C8D9D2-E462-48F1-B679-A96B28ABAED3-high.png)
+
+## Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in the [Automation section](https://docs.morpheusdata.com/en/4.1.1/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![Adding a new automation integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![Configuring the new Ansible integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to Library > Automation, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![Configuring the new task](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to Provisioning > Instances and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![Executing the new task](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in Library > Automationwe will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![Creating a workflow for our task](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to Provisioning > Instances and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![Running the new workflow on provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+## Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume VMware. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/4.1.1/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json b/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
new file mode 100644
index 0000000..def763c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+  "title": "Blueprint Development Overview",
+  "ordinal": 127,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprint Development Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md b/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
new file mode 100644
index 0000000..862eeef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
@@ -0,0 +1,5 @@
+# Blueprint Development Overview
+
+When provisioning, the User selects an INSTANCE TYPE from the provisioning wizard. At this stage, we can present custom INPUTS to the User which alter deployment in ways the administrator predetermines. Based on the selected Cloud technology and Version, the User is presented with applicable LAYOUTS selections. LAYOUTS can take advantage of Workflows which automate Tasks and can utilize a wide range of DevOps automation technologies. One or more NODE TYPES is associated with the LAYOUT. NODE TYPES are the bridge between LAYOUTS and Images. NODE TYPES can also take advantage of File Templates for custom configuration and Scripts which can be queued to run at any stage of the Instance lifecycle.
+
+![../../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json b/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
new file mode 100644
index 0000000..ac485f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+  "title": "Labels",
+  "ordinal": 102,
+  "parent_title": "Library",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md b/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
new file mode 100644
index 0000000..6f4259d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
@@ -0,0 +1,45 @@
+# Labels
+
+Labels Video Demo
+
+Labels are a categorization feature designed to allow easier filtering of list views in the HPE Morpheus Enterprise Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Workflows
+- Jobs
+- Instance Types
+- Instances
+- Layouts
+- Node Types
+- Servers
+- Virtual Images
+- Inputs
+- Option Lists
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists anywhere in the current Tenant. When a label is removed from a construct and no other constructs also have that label, HPE Morpheus Enterprise will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+![../_images/labels.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EF84CC50-D2E4-4906-9051-655D7B15CE65-high.png)
+
+## Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
+
+## Running Automation Against Label Targets
+
+The HPE Morpheus Enterprise automation constructs Jobs, Tasks, and Workflows can be run against Instance Labels or Server Labels. When creating the Job or executing the Task or Workflow, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
+
+![../_images/executeLabel.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FC1AD46A-80E3-46F9-95D0-3D679C53E596-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json b/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
new file mode 100644
index 0000000..56a3102
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+  "title": "Remote Console",
+  "ordinal": 354,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Console",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md b/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
new file mode 100644
index 0000000..6e1dce8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
@@ -0,0 +1,204 @@
+# Remote Console
+
+HPE Morpheus Enterprise has a built in Remote Console for Instances, Hosts, Virtual Machines and Bare Metal. The following information reviews the Roles Settings, Protocols, and Requirements necessary to configure and troubleshoot Remote Console access.
+
+## Role Settings
+
+User Role settings determine if the Console tab or `Open Console` Action appear for a user, and if a login prompt is presented or the user is automatically logged in when using the Console.
+
+- Remote Console (None, Provisioned, Full)
+  :   None
+      :   The user will not have access to remote console.
+
+      Provisioned
+      :   The user will only have remote console access for Instances they provisioned.
+
+      Full
+      :   The user will have remote console access for all instances they have access to.
+- Remote Console: Auto Login (No, Yes)
+  :   No
+      :   A login prompt will be present in the console for Linux platforms, and the main login screen will present for Windows platforms.
+
+      Yes
+      :   HPE Morpheus Enterprise will automatically login to the remote console using the credentials defined on the VM or Host. For provisioned Instances, the credentials are defined either from the credentials defined on the Virtual Image used, added via cloud-init or VMware Tools using the global cloud-init settings (Administration - Provisioning) or the Linux or Windows settings defined in User Settings. For Instances created when converting a VM or Host to managed, the credentials are entered when converting to managed. These credentials can be changed by editing the underlying VM or Host of the Instance.
+
+NOTE
+
+If the credentials defined on the VM or Host are not valid, and the `Remote Console: Auto Login` Role setting is set to `Yes`, the console will not be able to connect and no console window or login prompt will be presented. The credentials on the underlying VM or Host must be edited or `Remote Console: Auto Login` Role setting can be set to `No` for a login prompt to present in the console. Credentials cannot be changed from an Instance view, only in the Infrastructure VM or Host view.
+
+## Protocols
+
+Platform Type and Cloud Settings determines the protocol and port used for Remote Console connections.
+
+- SSH
+  :   The SSH protocol will be used for Linux and OSX platform types, and 22 is the default port used.
+- RDP
+  :   The RDP (Remote Desktop) protocol will be used for Windows platform types over port 3389 by default.
+- VNC
+  :   The VNC protocol will be used for all platform types in Clouds with the `Hypervisor Console` option enabled in cloud settings. VNC connection are made directly to the Hypervisor Host over port 443.
+
+NOTE
+
+Alternative ports can be configured per VM or Host by editing the VM or Host and editing the Port field in the RPC host section.
+
+### SSH
+
+For all Linux and OSX platform types, HPE Morpheus Enterprise will use the SSH protocol via port 22 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will SSH using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for SSH Connectivity
+
+- SSH Enabled on the target VM or Host
+- Port 22 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+### RDP
+
+For all Windows platform types, HPE Morpheus Enterprise will use the RDP protocol via port 3389 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will RDP using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for RDP Connectivity
+
+- Remote Access enabled on the target VM or Host and Remote Desktop enabled in the Windows Firewall settings. If the VM or Host is on a different network than the HPE Morpheus Enterprise appliance, public access for Remote Desktop must be enabled in the Firewall settings.
+- Port 3389 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+NOTE
+
+If Remote Console: Auto Login is set to No in a users Role permissions, Allow connections only from computers running Remote Desktop with Network Level Authentication in the Windows System Properties  >  Remote settings must be DISABLED for Remote Console to connect.
+
+### VNC (VMware Hypervisor Console)
+
+When the `Hypervisor Console` option is enabled in cloud settings, the VNC protocol will be used for all platform types that Cloud.
+
+When using VNC Hypervisor Console, the HPE Morpheus Enterprise Appliance connects directly to the host the VM is on, not directly to the VM.
+
+HPE Morpheus Enterprise features Remote Console support directly to hypervisors. To enable this feature a few prerequisites must be met:
+
+- The HPE Morpheus Enterprise Appliance must have network access to the host the VM is on over 443.
+- The HPE Morpheus Enterprise Appliance must be able to resolve the hypervisor hostnames.
+
+NOTE
+
+VNC connections for VMs and Hosts in VMware type clouds are made directly to the ESXi hosts, not vCenter.
+
+Unlike SSH and RDP, valid credentials do not need to be set on the VM or Host records in HPE Morpheus Enterprise for VNC hypervisor console connections. An IP address is also not required on the VM or Host for VNC hypervisor console connections. HPE Morpheus Enterprise will be able to connect to the VM or Host as soon as the `Host (Hypervisor)` record is set, which can be viewed in the Info section on the VM or Host detail page.
+
+NOTE
+
+- Auto-login is not supported for Hypervisor Console. Auto-login role settings do not apply to console connecting when using Hypervisor Console. Please note Hypervisor Console sessions persist on the ESXi host and once a user manually logs in to the VM they will continue to be logged in, even if the console tab/window in HPE Morpheus Enterprise is closed, until they manually log out.
+- Copy and Paste and Text selection in Linux terminals is not supported when using VNC (VMware Hypervisor Console).
+- In HPE Morpheus Enterprise versions 3.2.0 and higher, a newer Guacamole version is installed that is not compatible with MacOS Platform Types over VNC.
+
+## Copy and Paste
+
+### About this task
+
+NOTE
+
+Copy and Paste for Text is supported for SSH and RDP protocols only. Use of this functionality requires the Role permission of “VDI: Copy/Paste” set to Full.
+
+To Copy text from the console:
+
+### Procedure
+
+1. Select text in the Console window.
+2. Click the COPY button at the top of the Console window.
+3. The selected text is copied to the users clipboard.
+
+### Results
+
+To Paste text into console:
+
+1. Copy text on the local computer to you clipboard
+2. Right click into the “Paste Text Here” field at the top of the Console window. The field will the display “Text Copied, Use Console to Paste.”
+3. Right click into the console window.
+4. The text is pasted into the VM.
+
+## Guacamole
+
+### Overview
+
+HPE Morpheus Enterprise uses Apache Guacamole, a clientless remote console. Guacamole is installed on the HPE Morpheus Enterprise Appliance during the initial reconfigure. In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+The Guacamole proxy daemon, guacd, is used for all Remote Console connections and must be running for Remote Console functionality.
+
+### Troubleshooting guacd
+
+#### About this task
+
+If all console connections are not functioning, the Guacamole proxy daemon (guacd) process may not be running or have a stuck process preventing console connections. This is evident when only the header appears in the console tab/window, and no console window appears below the header and no connection status is show in the console header. The following commands can be used on the HPE Morpheus Enterprise Appliance to restore console functionality.
+
+`morpheus-ctl status`
+:   Lists all local HPE Morpheus Enterprise services including guacd and their states. If guacd is stopped, it will need to be started again for Remote Console to function.
+
+`morpheus-ctl start guacd`
+:   Starts the guacd process
+
+`morpheus-ctl stop guacd`
+:   Stops the guacd process
+
+`morpheus-ctl kill guacd`
+:   Forcefully kills the guacd process
+
+`morpheus-ctl restarts guacd`
+:   Restarts the guacd process
+
+`morpheus-ctl tail guacd`
+:   Tails the guacd current and state logs, located by default at `/var/log/morpheus/guacd/`. This log is useful when troubleshooting console connections, guacamole service status, and to determine the protocol being used for the Remote Console connection.
+
+If guacd continues to stop even after being started, or if guacd is running and no properly configured console connections are functioning, there may be a stuck guacd or multiple guacd processes running, which will need to killed and guacd started again.
+
+To kill all guacd processes on the HPE Morpheus Enterprise Appliance and start guacd again:
+
+#### Procedure
+
+1. Kill the morpheus gaucd proccess: `morpheus-ctl kill guacd`
+2. Grep for all running guacd processes: `sudo ps -aux | grep guacd` and note the guacd pid(s) (minus the process from the grep)
+3. Kill all running guacd processes: `kill -9 pid` replacing pid with the pid(s) of the target processes
+4. Start guacd again: `morpheus-ctl start guacd`
+5. Tail the guacd logs to verify guacd is started and listening: `morpheus-ctl tail guacd` The log output will resemble below when guacd is properly running: 
+
+   ```
+   ```
+   guacd[16899]: INFO:       Guacamole proxy daemon (guacd) version 0.9.14 started  
+   guacd[16899]: INFO:       Listening on host 127.0.0.1, port 4822
+   ```
+   ```
+6. Additional information in the guacd logs appears when HPE Morpheus Enterprise is making a console connection. A successful conneciton will resemble: 
+
+   ```
+   ```
+   guacd[24725]: INFO: Creating new client for protocol "ssh"  
+   guacd[24725]: INFO: Connection ID is "$24f67856-f050-4a17-83eb-9101g0cd8869"  
+   guacd[24743]: INFO: Current locale does not use UTF-8. Some characters may not render correctly.  
+   guacd[24743]: INFO: User "@63102f19-eff4-412e-b1f9-718405f55782" joined connection "$24f67856-f050-4a17-83eb-9101g0cd8869" (1 users now present)  
+   guacd[24743]: INFO: Auth key successfully imported.  
+   guacd[24743]: INFO: SSH connection successful.
+   ```
+   ```
+
+### Guacamole Version
+
+#### About this task
+
+In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole version 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+Note Guacamole version 0.9.14 is not compatible with MacOS Platform Types over VNC on ESXi v6.0 or prior (6.5 is supported). If necessary, the guacamole version can be reverted to 0.9.9.
+
+To revert the guacamole version from 0.9.14 to 0.9.9.
+
+#### Procedure
+
+1. Kill guacd - `morpheus-ctl kill guacd`
+2. Check if any guacd processes are still running `ps -aux | grep guac`
+3. If so, kill the processes `kill -9 pid` with id being the actual process id, like 16101.
+4. Go to the guac 0.9.9 directory: `cd /var/opt/morpheus/guacamole-server-0.9.9`
+5. Run: `make install`
+6. Start guacd: `morpheus-ctl start guacd`
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json b/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
new file mode 100644
index 0000000..6e7d00a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+  "title": "Setting an Optional Landing URL",
+  "ordinal": 306,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html",
+  "topic_cluster": {
+    "clustering_title": "Setting an Optional Landing URL",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md b/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
new file mode 100644
index 0000000..66ef113
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
@@ -0,0 +1,5 @@
+# Setting an Optional Landing URL
+
+On login, by default, Users will land on the Dashboard page (Operations > Dashboard). However, User and Tenant Roles may have custom landing URLs set. Setting a custom landing URL on the Tenant Role will apply globally to all Users within the Tenant. Landing URLs set on the User Role will supersede the landing URL set on the Tenant Role (if any). No Tenant Role is applied to the Master Tenant so the custom landing URL can only be set on the User Role for these Users.
+
+To set a custom landing URL, create or edit a Role. Set the custom landing URL in the “LANDING URL” field. For example, set `/provisioning/instances` and the Users having that Role will land on the Instances list page each time they log in. Other paths may be used depending on the desired landing page.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json b/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
new file mode 100644
index 0000000..6f31e0b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+  "title": "Storage Management",
+  "ordinal": 436,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md b/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
new file mode 100644
index 0000000..ffda7a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
@@ -0,0 +1,14 @@
+# Storage Management
+
+There are two types of storage that are available for an instance to consume. One is the local storage available on the compute server used to create an instance. The other is the remote storage (SAN), using the Alletra MP storage array.
+
+At present, there is no support for the management of the local storage through HPE Morpheus. They are used to install the OS image, and any storage available beyond that is up to the user to configure and use. They cannot be managed from HPE Morpheus.
+
+The remote storage is fully manageable. The user can create/update/delete volumes and manage their attachment to compute servers.
+
+**Subtopics**  
+
+- **[Boot Volume Selection During Instance Creation for Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html)**
+- **[Volume Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html)**
+- **[Volume Consumption](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json b/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
new file mode 100644
index 0000000..14c8da2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+  "title": "Xen Server",
+  "ordinal": 476,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.html",
+  "topic_cluster": {
+    "clustering_title": "Xen Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md b/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
new file mode 100644
index 0000000..af4f227
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
@@ -0,0 +1,152 @@
+# Xen Server
+
+## Add a Xen Server Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select Xen, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   IP or URL of Xen Host. ex: xenserver.domain.com
+
+   CUSTOM PORT
+   :   Port for non standard xen server clouds
+
+   USERNAME
+   :   Xen Host Username
+
+   PASSWORD
+   :   Xen Host Password
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json b/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
new file mode 100644
index 0000000..f039ecc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+  "title": "Provisioning the Cluster",
+  "ordinal": 181,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md b/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
new file mode 100644
index 0000000..75803cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
@@ -0,0 +1,27 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, this example is starting with three provisioned Ubuntu 22.04 boxes. I also have a HPE Morpheus Enterprise-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+![../../_images/createHpevmCluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F721FD37-B1E8-48D5-A817-E9A23048CACD-high.png)
+
+HPE Morpheus Enterprise gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in HPE Morpheus Enterprise, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+![../../_images/createClusterTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-15EB662D-9111-4C88-826F-235318761007-high.png)
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. When Ceph initializes, it needs to be pointed to an initial data device. Configure this in the **DATA DEVICE** field. At this time, only one device may be given but in the near future, an update will allow for multiple devices to be configured which would be added to the total Ceph storage as one large volume. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-model` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY**configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+Click NEXT to move to the Review tab for final review, and COMPLETE to kick off cluster provisioning.
+
+![../../_images/createClusterBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus Enterprise will run scripts to install KVM, install Ceph, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json b/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
new file mode 100644
index 0000000..32b6262
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+  "title": "Terraform",
+  "ordinal": 379,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md b/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
new file mode 100644
index 0000000..f368f84
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
@@ -0,0 +1,499 @@
+# Terraform
+
+## Requirements
+
+### Role Access
+
+- In order to see the Terraform App Blueprint type option and create Terraform App Blueprints in Library > Blueprints > App Blueprints, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+- In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+- Existing Terraform Blueprints must be added before they can be provisioned from Provisioning > Apps.
+- In order to provision Terraform Apps, the user must have Role permissions for Provisioning: Apps set to Full.
+
+### Github/Git Repo
+
+- To use .tf files from a Git repo, a Git or Github integration needs to be configured in Administration > Integrations. If one is not configured, .tf or .tf.json files can be manually drafted in HPE Morpheus Enterprise and added to Terraform App Blueprints but they could not be sourced from version control repositories.
+
+### Supported App Provisioning Targets
+
+- VMware
+- Amazon AWS
+- Microsoft Azure
+- Google Cloud Platform (GCP)
+- Oracle Cloud
+
+NOTE
+
+Additional clouds are planned for later releases.
+
+## Terraform Installation
+
+The first time you attempt to provision a Terraform App, you may come across an error indicating that Terraform is not installed:
+
+```
+```
+bash: line 1: terraform: command not found
+```
+```
+
+### Command Not Found Error Screenshot
+
+![../../_images/1commandNotFound.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-544D6493-88F5-42A8-A371-34CBF5087BB9-high.png)
+
+This likely means you’ve not yet configured Terraform Settings within HPE Morpheus Enterprise global settings. Navigate to Administration > Settings > Provisioning and scroll down to the Terraform Settings section. By default, the Terraform Runtime field is set to “Manual”. When set this way, HPE Morpheus Enterprise will attempt to use Terraform as installed on the appliance box and it may not be currently installed. To have HPE Morpheus Enterprise manage the Terraform installation process for you and manage Terraform versioning on a per-App basis, set the Terraform Runtime to “Auto”. You should also set the Default Terraform Version field as well. When a version is set on a Terraform Spec Template or Terraform App Blueprint, that version will supersede the default version indicated in global settings.
+
+### Configured Terraform Runtime Screenshot
+
+![../../_images/2configuredTfRuntime.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1F6CCDC8-4ED4-49DD-ABF3-DE0929CF7011-high.png)
+
+IMPORTANT
+
+HPE Morpheus Enterprise appliances which do not have access to the Internet will need to leave Terraform Runtime settings on “Manual” and ensure Terraform is installed appropriately on the appliance. Install Terraform in the /usr/sbin/terraform directory and make sure it’s owned by the morpheus-local user.
+
+## Creating Terraform App Blueprints
+
+### About this task
+
+In order to provision Terraform apps, Terraform App Blueprints must be created first.
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Name the Blueprint and select Terraform type. 
+
+   NOTE
+
+   In order to see the Terraform Blueprint type option, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+4. Select NEXT
+5. Configure the following: 
+
+   NAME
+   :   Friendly name for the App Blueprint in HPE Morpheus Enterprise
+
+   DESCRIPTION
+   :   Description for your App Blueprint shown in the Apps list (optional)
+
+   CATEGORY
+   :   A category for your App (optional)
+
+   IMAGE
+   :   Add reference icon for your App Blueprint to make it more identifiable at provision time (optional)
+
+   CONFIG TYPE (select Terraform Specs, Terraform (.tf), Terraform.json, or Git Repository)
+
+   Terraform (.tf)
+
+   CONFIG
+   :   Draft or paste in .tf content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform (.tf.json)
+
+   CONFIG
+   :   Draft or paste in .tf.json content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform Specs
+
+   SPEC TEMPLATE
+   :   Using the typeahead field, select all Terraform-type Spec Templates which make up your App. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+
+   Git Repository
+
+   SCM INTEGRATION
+   :   Select a Github or Git integration that has been added in Administration > Integrations and which contains relevant .tf files. Integrations must be pre-existing prior to creating the App Blueprint.
+
+   Repository
+   :   Select a repository which contains relevant .tf files from the Github or Git integration selected in the prior step.
+
+   BRANCH OR TAG
+   :   Select the Git branch containing the desired version of .tf files for the App. “master” is chosen by default if no value is entered.
+
+   WORKING PATH
+   :   Enter the repo path for the .tf file(s). `./` is default if no value is entered.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+6. Select COMPLETE
+
+### Results
+
+HPE Morpheus Enterprise will scan the blueprint to check for validity and will surface any errors which need correcting before the App Blueprint can be saved. Your Terraform App is ready to be provisioned from Provisioning > Apps.
+
+## Cloud Profiles
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+## Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+### Create a Terraform Profile
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+#### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+## Provisioning Terraform Apps
+
+### About this task
+
+NOTE
+
+Terraform App Blueprints must be added to Library > Blueprints > App Blueprints before they can be provisioned. At least one Terraform App Blueprint must exist before Terraform Apps can be provisioned from Provisioning > Apps.
+
+NOTE
+
+In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select + ADD
+3. Choose an existing Terraform App Blueprint
+4. Select NEXT
+5. Enter a NAME for the App and select the Group, Default Cloud and Environment (optional)
+6. Select NEXT
+7. Configure the following sections: 
+
+   App Settings
+
+   BACKEND TYPE
+   :   Internal is the default selection and the most secure choice. This sends the Terraform state back to the appliance via HTTP loopback to be stored in the appliance database. Users may also select Local which will write Terraform state to the local filesystem first before being stored in the database and removed from the local filesystem. If unsure, use the default Internal value. Backend Type selection is currently only available for Terraform Apps. Selecting Backend Type for Terraform Instance Types is a planned future feature addition.
+
+   VALIDATE PLAN
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not perform its typical validation to ensure the Terraform spec is valid. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   RUN APPLY
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not apply the plan at completion of the App wizard. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   Terraform Variables Populate any required or optional variables here. Variables whose values are stored in an associated tfvars file sourced from HPE Morpheus Enterprise Cypher are masked from the user. Variables stored in any Terraform Cloud Profile associated with the selected Cloud also are automatically masked. Other variables will be presented in the Terraform Variables section for user entry and any configured default values on the Terraform spec will be pre-loaded. Advanced Options
+
+   REFRESH MODE
+   :   Set an interval at which HPE Morpheus Enterprise should automatically check the App for drift from the Terraform spec. If set to Manual, HPE Morpheus Enterprise will never perform automatic checks and the user must do so when desired. The results of drift checks are reported on the App detail page and users may apply the plan at any time to bring the App back into alignment with the Terraform spec.
+
+   INITIAL STATE
+   :   Paste in existing Terraform state to onboard an existing Terraform App for HPE Morpheus Enterprise management. Though the field is small, it will accept large, multiline Terraform state. When creating an App from existing state, users may want to skip plan validation or may not want to apply right away. Opt out of these functions by unmarking the corresponding box in the App Settings section.
+
+   NOTE
+
+   Terraform state import is a new feature. At this time, some state file components may break the import process. This feature is being iterated on rapidly to increase coverage to as many application types and conditions as possible.
+
+   Terraform Preview Review the Terraform App components here, including any providers invoked, variables surfaced from the App spec, resources to be created, and .tf files utilized. There is no user input to be entered into this section.
+8. Select NEXT
+9. HPE Morpheus Enterprise will now validate the App (unless the user has opted out of this check) and surface any errors which would cause provisioning issues. If all is well, click COMPLETE
+
+### Results
+
+TIP
+
+Review the App in the Terraform Preview section. If any config data needs to be edited, select the RAW tab, edit the config, and then select the BUILDER tab once again. The config changes from the RAW edit will be updated in the preview section for further review. Permanent edits can be made by editing the App Blueprint, pushing .tf changes to your code repository, or Terraform Spec Templates (depending on how the .tf files are sourced for your App Blueprint).
+
+The Terraform App will begin to provision.
+
+Once provisioning is completed, note the State tab in the App details page (Provisioning > Apps > select the App). This tab contains subsections related to state management which is discussed in greater detail in the next section.
+
+## Terraform App State Management
+
+State management is handled from the State Tab of the Terraform App detail page (Provisioning > Apps > selected App). With the tab selected, the Terraform command field will be present regardless of the selected subsection. Use this field to send Terraform commands to your apps just like using Terraform from the command line. Press return on the keyboard or click on the “play” button to the right of the text field to execute the commmand.
+
+TIP
+
+“terraform” is automatically entered for each command as printed along the left edge of the text field. Thus, you don’t need to enter “terraform” with each command sent. Entering “state” or “plan” is equal to entering “terraform state” or “terraform plan” from the command line.
+
+![../../_images/appDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5AB2D1E8-EFB9-43FA-82CE-0229BA99CD63-high.png)
+
+When Terraform commands are executed against the application, HPE Morpheus Enterprise provides progress bars and command output in the UI. Command output is shown underneath the Terraform command field. Users can dismiss individual output windows by clicking the “x” button in the upper-right of each window. All command output can be dismissed by clicking the blue “x” button to the right of the command field itself.
+
+Within the ACTIONS reside four selections: Refresh State, Apply State, Edit Inputs, and Edit STATE. Selecting Refresh State is equivalent to using the “terraform plan” command from the command line. This will read the existing state of any existing objects which are part of the App and compare their current configuration against the prior state. Any differences will be noted in the output. If differences are discovered, the App is considered to be in a “drift” state. This drift status is shown in the UI when the user is viewing the “State” subsection (which is described in greater detail in the next section). The output of the Refresh State command, including detailed information about changes Terraform would make to App objects to in order to realign them with the App spec are shown in the UI.
+
+![../../_images/planOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E81EA071-D055-4481-B6FF-CE9642A07B68-high.png)
+
+The Apply State selection brings up a modal which allows the user to view the App spec once again. This includes being able to view and edit Terraform variables if needed. After making any needed edits, click NEXT and HPE Morpheus Enterprise will validate the App once again, just like it did at provision time. On the next tab of the wizard, HPE Morpheus Enterprise will show the user and planned changes that would be executed if the user completes the modal. An output will be shown as if “terraform plan” were run from the command line. Make note of any App objects which would be created, altered, or destroyed if the actions are accepted as HPE Morpheus Enterprise would immediately take them if desired. When ready, click COMPLETE. This will execute all planned changes as if the user had run “terraform apply -auto-approve” from a terminal session.
+
+Edit Inputs allows for editing of Input values without going through the process of applying state. Edit State displays the state in a large text area for direct editing.
+
+### State Subsection
+
+The State Subsection shows the current drift state of the App. This includes when HPE Morpheus Enterprise has last checked for drift and whether the App is currently in a “Drift” or “No Drift” state. If the App is currently in a Drift state, users can select Refresh State from the ACTIONS menu to identify which objects and attributes have deviated from the App configuration.
+
+![../../_images/stateSubsection.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6BEDAC1D-B4E0-4E17-83F3-7A3AD9036241-high.png)
+
+### Specs Subsection
+
+The Specs Subsection will show the user all HPE Morpheus Enterprise Spec Templates (Library > Templates > Spec Templates) which make up the App. Users may even edit Spec Template config directly from this view by clicking the Edit (pencil) icon to the right of each Spec Template listed.
+
+TIP
+
+Editing a Spec Template here will detach it from the source object, essentially making it a brand new object that exists only here. All future updates to that Spec Template would have to be made here going forward. In most cases, it’s advisable to edit the Spec Template directly at the source. For example, if this Spec Template were sourced from an integrated version control repository (ex. Github), it’s likely the best option to make a new commit into your repository and then let Terraform handle the process of bringing your App in line with the new specifications.
+
+![../../_images/editSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4FB5CB67-B878-424C-BA28-531EEB556CB0-high.png)
+
+### Plan Subsection
+
+This section displays the output of the most recent “terraform plan” run against your App. This will either indicate that your infrastructure (App) matches the configuration or it will indicate that a drift of some sort has taken place.
+
+### Input Subsection
+
+This section lists all Terraform inputs, such as variables, which are relevant to the App. Variable values are shown unless they are flagged as sensitive in your configuration. All variables sourced from a HPE Morpheus Enterprise Cypher tfvars mount will automatically be masked.
+
+### Output Subsection
+
+This section lists all configured Terraform output.
+
+## Terraform Instance Type Example
+
+Terraform Spec can also be used within the HPE Morpheus Enterprise Instance Type construct in addition to App Blueprints and Apps. Expand the section below to see a complete end-to-end example of a Terraform Instance Type from drafting new Spec Templates through to provisioning.
+
+### Terraform Instance Type Example
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+**AWS Subnet by Count**
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+**AWS Terraform Default Vars**
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+**AWS Provider Role Assume**
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+**AWS Terrform Locals**
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+**AWS VPC**
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json b/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
new file mode 100644
index 0000000..8f077a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+  "title": "File Shares",
+  "ordinal": 231,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md b/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
new file mode 100644
index 0000000..60fc81c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
@@ -0,0 +1,495 @@
+# File Shares
+
+File Shares are for Backup, Archives, Deployment and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
+
+## Supported File Share Types
+
+- Azure
+- CIFS (Samba Windows File Sharing)
+- Dell EMC ECS Share
+- Dell EMC Isilon Share
+- Local Storage
+- NFSv3
+
+## Azure File Shares
+
+### About this task
+
+To Add an Azure File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name for the file share in HPE Morpheus Enterprise.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the file share
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name or, to add a new Share, enter a new name and mark the Create Bucket box below
+
+   CREATE BUCKET
+   :   Mark if the share entered in SHARE NAME does not exist and needs to be created
+
+   DEFAULT BACKUP TARGET
+   :   Sets this file share as the default backup target when creating Backups. If selected, the option to UPDATE EXISTING BACKUPS will appear. Mark to update existing backups to this file share
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this file share as the default storage target when creating deployment archives
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this file share as the default storage target when uploading Virtual Images from the Virtual Images section or when importing Images from Instance Actions
+
+   RETENTION POLICY
+   :   None
+       :   Files in the share will not be automatically deleted or backed up
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the file share
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup target
+
+               BACKUP BUCKET
+               :   Search for and then select the desired backup bucket
+
+       DELETE OLD FILES
+       :   This option will delete files from this share after a set amount of days
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the share
+6. Select SAVE CHANGES
+
+### Results
+
+The file share will be created and displayed in the file shares tab.
+
+- To browse, upload, download, or delete files from this file share, select the name of the share from the File Shares tab.
+- To edit the file share, select the edit icon or select the name of the share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Re-pointing a file share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a file share, select the trash icon or select the name of the file share and click DELETE.
+
+  WARNING
+
+  When deleting a file share, all Deployment versions and Backups associated with the file share will be deleted.
+
+## CIFS File Shares
+
+### About this task
+
+To Add a CIFS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC Isilon File Shares
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Local Storage File Shares
+
+### About this task
+
+IMPORTANT
+
+Local Storage refers to local to the HPE Morpheus Enterprise Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app.morpheus-app /path` on the HPE Morpheus Enterprise Appliance.
+
+NOTE
+
+HPE Morpheus Enterprise will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## NFSv3 File Shares
+
+### About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save HPE Morpheus Enterprise will create a persistent mount owned by `morpheus-app.morpheus-app` on the HPE Morpheus Enterprise Appliance for the NFSv3 File Share. The HPE Morpheus Enterprise appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before HPE Morpheus Enterprise is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
new file mode 100644
index 0000000..d14de0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+  "title": "Full HA Upgrade",
+  "ordinal": 24,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html",
+  "topic_cluster": {
+    "clustering_title": "Full HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
new file mode 100644
index 0000000..5607a75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
@@ -0,0 +1,301 @@
+# Full HA Upgrade
+
+Full HA configurations represent multiple app nodes with external (non-system) MySQL, RabbitMQ and Opensearch Clusters or Services.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Overview
+
+When upgrading to v8.1.0 only services local to the Morpheus App node(s) will be upgraded. For fully distributed configurations (Full HA) where MySQL, RabbitMQ and Opensearch are external, the upgrade process will not upgrade these services.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for externalized MySQL, Elasticsearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+### Full HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.0.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Elasticsearch and RabbitMQ services are external to the App nodes. The following steps assume 3 app nodes, adjust accordingly.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### Full HA Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch the UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui  
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with ``morpheus-ctl tail morpheus-ui``.
+   ```
+   ```
+4. Once App Node 2 upgrade has completed and the UI is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`.
+2. Download the upgrade package from My HPE Software Center and transfer to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. Once App Node 2 upgrade has completed and the ui is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### Full HA RPM Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.0.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Opensearch and RabbitMQ services are external to the App nodes.
+
+#### Full HA Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.0. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.0 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.0 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+2. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 2 upgrade has completed and the UI is available, upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json b/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
new file mode 100644
index 0000000..c925d64
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+  "title": "Analytics",
+  "ordinal": 56,
+  "parent_title": "Operations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html",
+  "topic_cluster": {
+    "clustering_title": "Analytics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md b/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
new file mode 100644
index 0000000..2442f92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
@@ -0,0 +1,18 @@
+# Analytics
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html)**
+- **[Costing: Cloud Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html)**
+- **[Costing: Group Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html)**
+- **[Costing: Tenant Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html)**
+- **[Costing: User Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html)**
+- **[Costing: Workload Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html)**
+- **[Costing: Budget Analysis](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html)**
+- **[Costing: Tag Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html)**
+- **[Utilization: Utilization vs Cost](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html)**
+- **[Capacity: Capacity Planning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html)**
+- **[Workloads: Instance Type Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html)**
+- **[Workloads: Instance Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html)**
+- **[Workloads: Blueprint Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html)**
+- **[Workloads: Apps Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json b/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
new file mode 100644
index 0000000..4a2c80c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+  "title": "Monitoring Groups",
+  "ordinal": 258,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md b/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
new file mode 100644
index 0000000..1ccf715
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
@@ -0,0 +1,22 @@
+# Monitoring Groups
+
+Group monitors can only contain checks and can be edited or created in Monitoring  >  Groups. Besides simply adding and removing checks to a group there are a few other useful options that can be customized in a group:
+
+Name
+:   A friendly name for the group monitor in HPE Morpheus Enterprise
+
+Min Checks
+:   This specifies the minimum number of checks within the group that must be happy to keep the group from becoming unhealthy
+
+Max Severity
+:   The maximum severity incident a failed check may create. This setting overrides a check’s max severity setting
+
+Affects Availability
+:   If checked, a failing group monitor impacts system-wide availability calculations
+
+Checks
+:   Use the typeahead field to select pre-existing checks for the group monitor. If check(s) need to be created, this can be done in Monitoring > Checks
+
+NOTE
+
+Some useful information can also be seen on the detail page of a check. For example, the average response time of all checks within the group, or an aggregated check history can be viewed.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json b/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
new file mode 100644
index 0000000..c982018
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+  "title": "Overview",
+  "ordinal": 126,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md b/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
new file mode 100644
index 0000000..39712ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
@@ -0,0 +1,18 @@
+# Overview
+
+The Blueprints section is used to compose provisioning catalogs. The Blueprints section is composed of:
+
+- Instance Types
+- Layouts
+- Node Types
+- App Blueprints
+- Catalog Items
+- Cluster Layouts
+
+Additionally, items from Options and Templates sections are incorporated to call in custom options for users, IaaS spec files, scripts, and more. See Options and Templates within HPE Morpheus Enterprise Library for more information on creating or sourcing the items below from version control. In some cases, they may need to be pre-existing for the most efficient creation of Blueprints.
+
+- Inputs
+- Option Lists
+- File Templates
+- Scripts
+- Spec Templates
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json b/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
new file mode 100644
index 0000000..9b54aed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+  "title": "Add Load Balancer during Provisioning",
+  "ordinal": 497,
+  "parent_title": "Add Load Balancer to Instance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md b/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
new file mode 100644
index 0000000..5471a5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
@@ -0,0 +1,55 @@
+# Add Load Balancer during Provisioning
+
+## About this task
+
+In the Instance Provisioning wizard, Load Balancers can be configured in the Automation > LoadBalancer section.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select + ADD.
+3. Select an Instance Type that supports scaling. (ENABLE SCALING (HORIZONTAL) flagged on Instance Type configuration)
+4. Proceed with Instance configuration to the Automation section.
+5. Fill in the following: 
+
+   VIP ADDRESS
+   :   Define IP Address for the Virtual Server
+       :   - Example: 10.30.23.191
+
+   VIP PORT
+   :   Define port for the Virtual Server
+       :   - Example: 80
+
+   VIP HOSTNAME
+   :   Define hostname that will resolve to the VIP IP.
+       :   - Example: jwDemoHaApp59.den.example.com
+
+   VIRTUAL SERVICE NAME
+   :   Define name for the Virtual Service. Defaults to `${instance.name}`
+
+   BALANCE MODE
+   :   Specify balance mode for the VIP
+       :   - Least Connections
+           - Round Robin
+
+   STICKY MODE
+   :   Specify sticky session options for the VIP
+       :   - Source IP
+           - Cookie
+
+   SHARED VIP ADDRESS
+   :   Select if VIP is shared, then enter DIRECT VIP ADDRESS
+
+   SSL CERT
+   :   SSL Certificate that will be applied to the VIP.
+       :   - No SSL
+           - Select existing Certificate from Infrastructure  >  Keys & Certs or from a Trust Provider Integration.
+
+       USE EXTERNAL ADDRESS FOR BACKEND NODES
+       :   - Select if traffic from LB to Backend Nodes needs to be sent to the External Addresses, or leave deselected to use Internal Addresses for Backed Nodes.
+6. Optionally configure auto-scaling configuration in the `Scale` section
+7. Select NEXT and provision the Instance.
+
+## Results
+
+After all nodes in the Instance are provisioned, the LB configuration will be added to the Instance and Virtual Servers, Services and Servers will be created and configured on the NetScaler. The Load Balancer settings and status will be visible in the Instance details page LOAD BALANCER section, with additional details, links, and configurations options available in the `SCALE` tab.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json b/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
new file mode 100644
index 0000000..74208aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+  "title": "Image Prep (Windows)",
+  "ordinal": 191,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md b/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
new file mode 100644
index 0000000..5ec2621
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
@@ -0,0 +1,102 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and HPE Morpheus Enterprise Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in HPE Morpheus Enterprise that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in HPE Morpheus Enterprise. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in HPE Morpheus Enterprise, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to HPE Morpheus Enterprise. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+![../../_images/provisionMvmInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9DE2A41A-C675-4E94-819C-7DB350F6B8DA-high.png)
+
+On the GROUP tab, select the Group and Cloud containing the target HVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+![../../_images/groupTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5C1016FB-39ED-4A2E-9D73-3CE2F1C29456-high.png)
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+![../../_images/configTabTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8B62B5BD-FAF8-40F3-84C6-E905D7E4E72F-high.png)
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, HPE Morpheus Enterprise will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the HPE Morpheus Enterprise appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in HPE Morpheus Enterprise. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+![../../_images/importImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FBFB8AA8-171F-4668-BD6A-CAE4F5870AA8-high.png)
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to HPE Morpheus Enterprise API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in HPE Morpheus Enterprise. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. HPE Morpheus Enterprise library items can now be created from this image by adding new Node Types, Layouts, and Instance Types. The complete steps for building a library item go beyond the scope of this particular guide but more detail on that process is available elsewhere in HPE Morpheus Enterprise UI documentation. Once the library items are created, new Instances may be provisioned complete with HPE Morpheus Enterprise Agent installed.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json b/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
new file mode 100644
index 0000000..b7ba0da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+  "title": "Configuring Access with Clouds, Groups, and Roles",
+  "ordinal": 371,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Access with Clouds, Groups, and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md b/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
new file mode 100644
index 0000000..dfb7bc7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
@@ -0,0 +1,55 @@
+# Configuring Access with Clouds, Groups, and Roles
+
+As you get started, it’s vital to understand constructs such as Clouds and Groups as they are implemented in HPE Morpheus Enterprise. Deploying an effective strategy for dividing organizational resources and people groups under these constructs will ensure all parties have convenient access to the resources they need. Map currently-existing strategies for splitting resources and controlling costs into HPE Morpheus Enterprise and your teams will have access only to resources allocated to their department.
+
+This guide discusses the constructs of Clouds, Groups, Roles, Users, and Policies while also presenting an example use case for allocating resources and distributing access under these umbrellas. We’ll end up with a permissions structure represented by the diagram below and step through each part of the implementation process.
+
+![../../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+## Clouds
+
+Clouds have broad meaning in HPE Morpheus Enterprise and can be integrations into public clouds, private clouds, or bare metal servers. You can read more about Clouds in HPE Morpheus Enterprise Docs [here](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/clouds.html).
+
+In our example case, the organization has an Azure account and three separate departmental projects consolidated under separate resource groups. The HPE Morpheus Enterprise integration with Azure public cloud allows users to scope the Cloud to one specific resource group, if desired. We will do so in this case because it will allow us to restrict our users to the appropriate Azure resource groups in a later step. In the screenshot below, note how I am scoping the HPE Morpheus Enterprise Azure Cloud to a specific resource group when adding or editing the Cloud. This process will be repeated two additional times to create the three HPE Morpheus Enterprise Clouds we need. Complete details on integrating HPE Morpheus Enterprise with Azure public cloud are [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/azure/azure.html) in HPE Morpheus Enterprise Docs.
+
+![../../_images/1configCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-04D720D8-D7A9-44B8-8585-DBDEDD802C3D-high.png)
+
+## Groups
+
+[Groups](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html) in HPE Morpheus Enterprise allow administrators to determine which Clouds their users have access to. Part of defining a Role, which we’ll see in the next section, is selecting which Groups are associated with the Role. One or multiple Clouds are added to each Group and passed to users through their assigned Roles.
+
+When creating a Cloud, it must be added to a Group. Additionally, Clouds can be added to a Group at any time from the Clouds tab on the Group detail page (Infrastructure > Groups > Specific Group). In the example case diagrammed above, one Cloud (Azure cloud account scoped to a specific resource group) is associated with each Group but often Groups will contain many Clouds. In the screenshot below, I am adding an Azure Cloud to a Group that is currently empty.
+
+![../../_images/2addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0AB9B625-EF46-4CA2-B797-B86D533F52B4-high.png)
+
+## Roles
+
+HPE Morpheus Enterprise Roles determine user access to many things, including application features, Groups, configured Instance Types, configured Blueprints, Personas, and Catalog Item configurations for the Service Catalog Persona. It’s important to note that a user can have multiple Roles and will take the most permissive rights across all of these Roles. In many cases, this greatly simplifies Role configuration for administrators as it prevents the need to create highly-specific individual Roles that can suit every case. To illustrate this for our example case, I will create a set of Roles to handle Group access for my users and another set of Roles to give access to the correct feature permissions.
+
+For this example case, I’ll start by creating one Role for each of the three Groups we created in the previous step. By default, a new Role will have all feature permissions set to “None” as shown below meaning we can skip directly to the Group Access tab.
+
+![../../_images/3roleFeatureAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E0F14807-7823-4651-8193-7E2F04ADC12E-high.png)
+
+On the Group Access tab, I will toggle the Global Access setting to Custom and give access only to one Group as shown in the next image. By doing this for each of our Groups created in the last section, we can easily control Group access for each user by applying one or more of our Group Roles to their user which we will do in the next section.
+
+![../../_images/4roleGroupAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1F85B206-FDB4-478F-BCEC-96E7184EF31F-high.png)
+
+In addition to Roles for handling Group access, we need additional Role sets which will control our feature access. For example, we might have highly permissive feature access for administrators and more restrictive ones for developers or other users who have specific responsibilities requiring access to just a few specific areas of the UI. These additional Roles are created in the same way as the Group Roles we just created but all Group access will be set to “None” and the appropriate feature access will be configured on the “Feature Access” tab.
+
+## Users
+
+With the groundwork laid in the previous steps, we can easily configure permissions for any user accounts we might add to HPE Morpheus Enterprise. In the screenshot below, I’m adding a user account for a developer at my organization. I’ve applied one Role to handle correct Group access for this user and I’ve applied the “Developer” role to give only the feature access needed for this user to carry out his or her responsibilities.
+
+![../../_images/5newUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-295DFC03-0A0D-4350-B2DB-30692FE51851-high.png)
+
+## Policies
+
+One final consideration for this example case is policy application. HPE Morpheus Enterprise enables administrators to place fine-grained governance scoped to specific users, Roles, Groups, Clouds, Tenants, or globally. You can read more about policies in HPE Morpheus Enterprise docs [here](https://docs.morpheusdata.com/en/latest/administration/policies/policies.html) but we will also create some that apply to the example case discussed in this guide.
+
+Policies are created from the Administration menu in the Policies section. In the screenshot below, I’ve created a new policy and chosen to scope it to a Group. In this case, I’m creating a maximum VMs policy but there are many other types which are listed in our documentation linked above.
+
+![../../_images/6policies.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-21C24B9B-7C14-48A8-AB21-9D31F5DF44DC-high.png)
+
+## Conclusion
+
+At this point, we’ve completed implementation of the access structure. As new users are added, we can easily give them the Group and feature access they need. We can also easily add or edit the policies that are in place or add new Clouds and distribute access to existing users. The key is understanding the relationship between the HPE Morpheus Enterprise constructs discussed in this guide. Armed with that understanding, the example case presented here can be expanded to suit the needs of large-scale enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json b/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
new file mode 100644
index 0000000..955a6d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+  "title": "Resources",
+  "ordinal": 213,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html",
+  "topic_cluster": {
+    "clustering_title": "Resources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md b/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
new file mode 100644
index 0000000..0f65db6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
@@ -0,0 +1,1018 @@
+# Resources
+
+![../../_images/infra_compute_header_resources_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F4C1D71D-FBE1-47F2-A56D-36C1E419CA22-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Resource Type Cloud
+
+Resources represent objects that do not map to VM or Container types in HPE Morpheus Enterprise, such as IAC resources from Terraform, Cloudformation or ARM Templates like VPC’s, Gateways, Users, Policies, Brokers, API’s, Endpoints, Directories, ACL’s, Routes… well anything really. All resources created from IAC Templates map to iac provider resource types and HPE Morpheus Enterprise maintains a resource object record from the mapped resource.
+
+Expand the **Resource Types** table below to see all Resource types that will be mapped to Resource objects in HPE Morpheus Enterprise:
+
+## Resource Types
+
+The following Resource Types are mapped when provisioning IAC templates including Terraform and CloudFormation templates.
+
+| ICON | RESOURCE NAME | PROVIDER | RESOURCE TYPE | MORPHEUS TYPE |
+| --- | --- | --- | --- | --- |
+| ../../_images/aws-resource.png | Accessanalyzer Analyzer | terraform | accessanalyzerAnalyzer | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate | terraform | acmCertificate | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate Validation | terraform | acmCertificateValidation | accountResource |
+| ../../_images/aws-resource.png | Acmpca Certificate Authority | terraform | acmpcaCertificateAuthority | accountResource |
+| ../../_images/azure-securitycenter.png | Advanced Threat Protection | terraform | AdvancedThreatProtection | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api | cloudFormation | Api | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Authorizer | cloudFormation | Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Deployment | cloudFormation | Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Domain Name | cloudFormation | DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration | cloudFormation | Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration Response | cloudFormation | IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Mapping | cloudFormation | ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Model | cloudFormation | Model | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route Response | cloudFormation | RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Stage | cloudFormation | Stage | accountResource |
+| ../../_images/aws-ec2.png | Ami | terraform | ami | accountResource |
+| ../../_images/aws-ec2.png | Ami Copy | terraform | amiCopy | accountResource |
+| ../../_images/aws-ec2.png | Ami From Instance | terraform | amiFromInstance | accountResource |
+| ../../_images/aws-ec2.png | Ami Launch Permission | terraform | amiLaunchPermission | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-resource.png | API | terraform | API | accountResource |
+| ../../_images/azure-resource.png | API Authorization Server | terraform | APIAuthorizationServer | accountResource |
+| ../../_images/azure-resource.png | API Backend | terraform | APIBackend | accountResource |
+| ../../_images/azure-resource.png | API Certificate | terraform | APICertificate | accountResource |
+| ../../_images/azure-resource.png | API Diagnostic | terraform | APIDiagnostic | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Account | terraform | apiGatewayAccount | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Api Key | terraform | apiGatewayApiKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Authorizer | terraform | apiGatewayAuthorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Base Path Mapping | terraform | apiGatewayBasePathMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Client Certificate | terraform | apiGatewayClientCertificate | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Deployment | terraform | apiGatewayDeployment | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Part | terraform | apiGatewayDocumentationPart | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Version | terraform | apiGatewayDocumentationVersion | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Domain Name | terraform | apiGatewayDomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Gateway Response | terraform | apiGatewayGatewayResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration | terraform | apiGatewayIntegration | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration Response | terraform | apiGatewayIntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method | terraform | apiGatewayMethod | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Response | terraform | apiGatewayMethodResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Settings | terraform | apiGatewayMethodSettings | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Model | terraform | apiGatewayModel | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Request Validator | terraform | apiGatewayRequestValidator | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Resource | terraform | apiGatewayResource | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Rest Api | terraform | apiGatewayRestApi | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Stage | terraform | apiGatewayStage | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan | terraform | apiGatewayUsagePlan | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan Key | terraform | apiGatewayUsagePlanKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Vpc Link | terraform | apiGatewayVpcLink | accountResource |
+| ../../_images/azure-resource.png | API Group | terraform | APIGroup | accountResource |
+| ../../_images/azure-resource.png | API Group User | terraform | APIGroupUser | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider AD | terraform | APIIdentityProviderAD | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Facebook | terraform | APIIdentityProviderFacebook | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Google | terraform | APIIdentityProviderGoogle | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Microsoft | terraform | APIIdentityProviderMicrosoft | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Twitter | terraform | APIIdentityProviderTwitter | accountResource |
+| ../../_images/azure-resource.png | API Logger | terraform | APILogger | accountResource |
+| ../../_images/azure-resource.png | API Management | terraform | APIManagement | accountResource |
+| ../../_images/azure-resource.png | API Named Value | terraform | APINamedValue | accountResource |
+| ../../_images/azure-resource.png | API OpenID Provider | terraform | APIOpenIDProvider | accountResource |
+| ../../_images/azure-resource.png | API Operation | terraform | APIOperation | accountResource |
+| ../../_images/azure-resource.png | API Operation Policy | terraform | APIOperationPolicy | accountResource |
+| ../../_images/azure-resource.png | API Policy | terraform | APIPolicy | accountResource |
+| ../../_images/azure-resource.png | API Product | terraform | APIProduct | accountResource |
+| ../../_images/azure-resource.png | API Product API | terraform | APIProductAPI | accountResource |
+| ../../_images/azure-resource.png | API Product Group | terraform | APIProductGroup | accountResource |
+| ../../_images/azure-resource.png | API Product Policy | terraform | APIProductPolicy | accountResource |
+| ../../_images/azure-resource.png | API Property | terraform | APIProperty | accountResource |
+| ../../_images/azure-resource.png | API Schema | terraform | APISchema | accountResource |
+| ../../_images/azure-resource.png | API Subscription | terraform | APISubscription | accountResource |
+| ../../_images/azure-resource.png | API User | terraform | APIUser | accountResource |
+| ../../_images/azure-resource.png | API Version Set | terraform | APIVersionSet | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api | terraform | apigatewayv2Api | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api Mapping | terraform | apigatewayv2ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Authorizer | terraform | apigatewayv2Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Deployment | terraform | apigatewayv2Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Domain Name | terraform | apigatewayv2DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration | terraform | apigatewayv2Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration Response | terraform | apigatewayv2IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Model | terraform | apigatewayv2Model | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route | terraform | apigatewayv2Route | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route Response | terraform | apigatewayv2RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Stage | terraform | apigatewayv2Stage | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Vpc Link | terraform | apigatewayv2VpcLink | accountResource |
+| ../../_images/azure-appconfiguration.png | App Configuration | terraform | AppConfiguration | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | App Cookie Stickiness Policy | terraform | appCookieStickinessPolicy | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Analytics Item | terraform | AppInsightsAnalyticsItem | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights API Key | terraform | AppInsightsAPIKey | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Web Test | terraform | AppInsightsWebTest | accountResource |
+| ../../_images/azure-resource.png | App Service | terraform | AppService | accountResource |
+| ../../_images/azure-resource.png | App Service Active Slot | terraform | AppServiceActiveSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate | terraform | AppServiceCertificate | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate Order | terraform | AppServiceCertificateOrder | accountResource |
+| ../../_images/azure-resource.png | App Service Environment | terraform | AppServiceEnvironment | accountResource |
+| ../../_images/azure-resource.png | App Service Host Binding | terraform | AppServiceHostBinding | accountResource |
+| ../../_images/azure-resource.png | App Service Network Swift Connection | terraform | AppServiceNetworkSwiftConnection | accountResource |
+| ../../_images/azure-resource.png | App Service Plan | terraform | AppServicePlan | accountResource |
+| ../../_images/azure-resource.png | App Service Slot | terraform | AppServiceSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Source Control Token | terraform | AppServiceSourceControlToken | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Policy | terraform | appautoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Scheduled Action | terraform | appautoscalingScheduledAction | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Target | terraform | appautoscalingTarget | accountResource |
+| ../../_images/azure-compute.png | Application Definition | terraform | ApplicationDefinition | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-applicationinsights.png | Application Insights | terraform | ApplicationInsights | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/aws-resource.png | Appmesh Mesh | terraform | appmeshMesh | accountResource |
+| ../../_images/aws-resource.png | Appmesh Route | terraform | appmeshRoute | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Node | terraform | appmeshVirtualNode | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Router | terraform | appmeshVirtualRouter | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Service | terraform | appmeshVirtualService | accountResource |
+| ../../_images/aws-appsync.png | Appsync Api Key | terraform | appsyncApiKey | accountResource |
+| ../../_images/aws-appsync.png | Appsync Datasource | terraform | appsyncDatasource | accountResource |
+| ../../_images/aws-appsync.png | Appsync Function | terraform | appsyncFunction | accountResource |
+| ../../_images/aws-appsync.png | Appsync Graphql Api | terraform | appsyncGraphqlApi | accountResource |
+| ../../_images/aws-appsync.png | Appsync Resolver | terraform | appsyncResolver | accountResource |
+| ../../_images/aws-athena.png | Athen Named Query | cloudFormation | NamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Database | terraform | athenaDatabase | accountResource |
+| ../../_images/aws-athena.png | Athena Named Query | terraform | athenaNamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Workgroup | terraform | athenaWorkgroup | accountResource |
+| ../../_images/azure-automation.png | Automation Account | terraform | AutomationAccount | accountResource |
+| ../../_images/azure-automation.png | Automation Certificate | terraform | AutomationCertificate | accountResource |
+| ../../_images/azure-automation.png | Automation Credential | terraform | AutomationCredential | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Config | terraform | AutomationDSCConfig | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Node Config | terraform | AutomationDSCNodeConfig | accountResource |
+| ../../_images/azure-automation.png | Automation Job Schedule | terraform | AutomationJobSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Module | terraform | AutomationModule | accountResource |
+| ../../_images/azure-automation.png | Automation Runbook | terraform | AutomationRunbook | accountResource |
+| ../../_images/azure-automation.png | Automation Schedule | terraform | AutomationSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Boolean | terraform | AutomationVariableBoolean | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Datetime | terraform | AutomationVariableDatetime | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Int | terraform | AutomationVariableInt | accountResource |
+| ../../_images/azure-automation.png | Automation Variable String | terraform | AutomationVariableString | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Attachment | terraform | autoscalingAttachment | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Group | terraform | autoscalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Lifecycle Hook | terraform | autoscalingLifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Notification | terraform | autoscalingNotification | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Policy | terraform | autoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Schedule | terraform | autoscalingSchedule | accountResource |
+| ../../_images/azure-compute.png | Availability Set | terraform | AvailabilitySet | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener | cloudFormation | Listener | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Certificate | cloudFormation | ListenerCertificate | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Rule | cloudFormation | ListenerRule | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Target Group | cloudFormation | TargetGroup | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh | cloudFormation | Mesh | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Node | cloudFormation | VirtualNode | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Router | cloudFormation | VirtualRouter | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Service | cloudFormation | VirtualService | accountResource |
+| ../../_images/aws-elb.png | AWS Application Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Group | cloudFormation | AutoScalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Launch Configuration | cloudFormation | LaunchConfiguration | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Lifecycle Hook | cloudFormation | LifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Policy | cloudFormation | ScalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Scheduled Action | cloudFormation | ScheduledAction | accountResource |
+| ../../_images/aws-elb.png | AWS Elastic Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-elasticsearch-service.png | AWS Elasticsearch Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-sdb.png | AWS SDB Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Resource Policy | cloudFormation | ResourcePolicy | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Rotation Schedule | cloudFormation | RotationSchedule | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret | cloudFormation | Secret | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret Target Attachment | cloudFormation | SecretTargetAttachment | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set | cloudFormation | ConfigurationSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set Event Destination | cloudFormation | ConfigurationSetEventDestination | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Filter | cloudFormation | ReceiptFilter | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule | cloudFormation | ReceiptRule | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule Set | cloudFormation | ReceiptRuleSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Template | cloudFormation | Template | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Subscription | cloudFormation | Subscription | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic | cloudFormation | Topic | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic Policy | cloudFormation | TopicPolicy | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue | cloudFormation | Queue | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue Policy | cloudFormation | QueuePolicy | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Geo Match Set | cloudFormation | GeoMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rate Based Rule | cloudFormation | RateBasedRule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Regex Pattern Set | cloudFormation | RegexPatternSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL Association | cloudFormation | WebACLAssociation | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-workspaces.png | AWS Workspace | cloudFormation | Workspace | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/aws-backup.png | Backup Plan | terraform | backupPlan | accountResource |
+| ../../_images/azure-backup.png | Backup Policy File Share | terraform | BackupPolicyFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Policy VM | terraform | BackupPolicyVM | accountResource |
+| ../../_images/azure-backup.png | Backup Protected File Share | terraform | BackupProtectedFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Protected VM | terraform | BackupProtectedVM | accountResource |
+| ../../_images/aws-backup.png | Backup Selection | terraform | backupSelection | accountResource |
+| ../../_images/azure-backup.png | Backup Storage Account | terraform | BackupStorageAccount | accountResource |
+| ../../_images/aws-backup.png | Backup Vault | terraform | backupVault | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/aws-resource.png | Batch Compute Environment | terraform | batchComputeEnvironment | accountResource |
+| ../../_images/aws-resource.png | Batch Job Definition | terraform | batchJobDefinition | accountResource |
+| ../../_images/aws-resource.png | Batch Job Queue | terraform | batchJobQueue | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Registration | terraform | BotChannelRegistration | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Slack | terraform | BotChannelSlack | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Direct Line | terraform | BotDirectLine | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/aws-resource.png | Budgets Budget | terraform | budgetsBudget | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/aws-resource.png | Cloud9 Environment Ec2 | terraform | cloud9EnvironmentEc2 | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack | terraform | cloudformationStack | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set | terraform | cloudformationStackSet | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set Instance | terraform | cloudformationStackSetInstance | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Distribution | terraform | cloudfrontDistribution | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Origin Access Identity | terraform | cloudfrontOriginAccessIdentity | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Public Key | terraform | cloudfrontPublicKey | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Cluster | terraform | cloudhsmV2Cluster | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Hsm | terraform | cloudhsmV2Hsm | accountResource |
+| ../../_images/aws-cloudtrail.png | Cloudtrail | terraform | cloudtrail | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Dashboard | terraform | cloudwatchDashboard | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Permission | terraform | cloudwatchEventPermission | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Rule | terraform | cloudwatchEventRule | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Target | terraform | cloudwatchEventTarget | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination | terraform | cloudwatchLogDestination | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination Policy | terraform | cloudwatchLogDestinationPolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Group | terraform | cloudwatchLogGroup | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Metric Filter | terraform | cloudwatchLogMetricFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Resource Policy | terraform | cloudwatchLogResourcePolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Stream | terraform | cloudwatchLogStream | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Subscription Filter | terraform | cloudwatchLogSubscriptionFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Metric Alarm | terraform | cloudwatchMetricAlarm | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Project | terraform | codebuildProject | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Source Credential | terraform | codebuildSourceCredential | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Webhook | terraform | codebuildWebhook | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Repository | terraform | codecommitRepository | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Trigger | terraform | codecommitTrigger | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy App | terraform | codedeployApp | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Config | terraform | codedeployDeploymentConfig | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Group | terraform | codedeployDeploymentGroup | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline | terraform | codepipeline | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline Webhook | terraform | codepipelineWebhook | accountResource |
+| ../../_images/aws-codestar.png | Codestarnotifications Notification Rule | terraform | codestarnotificationsNotificationRule | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool | terraform | cognitoIdentityPool | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool Roles Attachment | terraform | cognitoIdentityPoolRolesAttachment | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Provider | terraform | cognitoIdentityProvider | accountResource |
+| ../../_images/aws-resource.png | Cognito Resource Server | terraform | cognitoResourceServer | accountResource |
+| ../../_images/aws-resource.png | Cognito User Group | terraform | cognitoUserGroup | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool | terraform | cognitoUserPool | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Client | terraform | cognitoUserPoolClient | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Domain | terraform | cognitoUserPoolDomain | accountResource |
+| ../../_images/aws-resource.png | Config Aggregate Authorization | terraform | configAggregateAuthorization | accountResource |
+| ../../_images/aws-resource.png | Config Config Rule | terraform | configConfigRule | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Aggregator | terraform | configConfigurationAggregator | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder | terraform | configConfigurationRecorder | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder Status | terraform | configConfigurationRecorderStatus | accountResource |
+| ../../_images/aws-resource.png | Config Delivery Channel | terraform | configDeliveryChannel | accountResource |
+| ../../_images/aws-resource.png | Config Organization Custom Rule | terraform | configOrganizationCustomRule | accountResource |
+| ../../_images/aws-resource.png | Config Organization Managed Rule | terraform | configOrganizationManagedRule | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Account | terraform | CosmosDBAccount | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Cassandra Keyspace | terraform | CosmosDBCassandraKeyspace | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Database | terraform | CosmosDBGremlinDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Graph | terraform | CosmosDBGremlinGraph | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Collection | terraform | CosmosDBMongoCollection | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Database | terraform | CosmosDBMongoDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Container | terraform | CosmosDBSQLContainer | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Database | terraform | CosmosDBSQLDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Table | terraform | CosmosDBTable | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/aws-resource.png | Cur Report Definition | terraform | curReportDefinition | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/aws-vpc.png | Customer Gateway | terraform | customerGateway | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory | terraform | DataFactory | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Data Lake Storage | terraform | DataFactoryDataLakeStorage | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Integration Runtime | terraform | DataFactoryIntegrationRuntime | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Dataset | terraform | DataFactoryMySQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Link | terraform | DataFactoryMySQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Pipeline | terraform | DataFactoryPipeline | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Dataset | terraform | DataFactoryPostgreSQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Link | terraform | DataFactoryPostgreSQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Link | terraform | DataFactorySQLServerLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Table | terraform | DataFactorySQLServerTable | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Trigger Schedule | terraform | DataFactoryTriggerSchedule | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Account | terraform | DataLakeAnalyticsAccount | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Firewall Rule | terraform | DataLakeAnalyticsFirewallRule | accountResource |
+| ../../_images/azure-storage.png | Data Lake Filesystem | terraform | DataLakeFilesystem | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store | terraform | DataLakeStore | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store File | terraform | DataLakeStoreFile | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store Firewall Rule | terraform | DataLakeStoreFirewallRule | accountResource |
+| ../../_images/azure-datashare.png | Data Share Account | terraform | DataShareAccount | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Project | terraform | DatabaseMigrationProject | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Service | terraform | DatabaseMigrationService | accountResource |
+| ../../_images/azure-databricks.png | Databricks Workspace | terraform | DatabricksWorkspace | accountResource |
+| ../../_images/aws-resource.png | Datapipeline Pipeline | terraform | datapipelinePipeline | accountResource |
+| ../../_images/aws-resource.png | Datasync Agent | terraform | datasyncAgent | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Efs | terraform | datasyncLocationEfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Nfs | terraform | datasyncLocationNfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location S3 | terraform | datasyncLocationS3 | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Smb | terraform | datasyncLocationSmb | accountResource |
+| ../../_images/aws-resource.png | Datasync Task | terraform | datasyncTask | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Cluster | terraform | daxCluster | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Parameter Group | terraform | daxParameterGroup | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Subnet Group | terraform | daxSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | Db Cluster Snapshot | terraform | dbClusterSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Event Subscription | terraform | dbEventSubscription | accountResource |
+| ../../_images/aws-rds.png | Db Instance | terraform | dbInstance | accountResource |
+| ../../_images/aws-rds.png | Db Instance Role Association | terraform | dbInstanceRoleAssociation | accountResource |
+| ../../_images/aws-rds.png | Db Option Group | terraform | dbOptionGroup | accountResource |
+| ../../_images/aws-rds.png | Db Parameter Group | terraform | dbParameterGroup | accountResource |
+| ../../_images/aws-rds.png | Db Security Group | terraform | dbSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | Db Snapshot | terraform | dbSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Subnet Group | terraform | dbSubnetGroup | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host | terraform | DedicatedHost | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host Group | terraform | DedicatedHostGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Network Acl | terraform | defaultNetworkAcl | accountResource |
+| ../../_images/aws-vpc.png | Default Route Table | terraform | defaultRouteTable | accountResource |
+| ../../_images/aws-vpc.png | Default Security Group | terraform | defaultSecurityGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Subnet | terraform | defaultSubnet | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc | terraform | defaultVpc | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc Dhcp Options | terraform | defaultVpcDhcpOptions | accountResource |
+| ../../_images/aws-resource.png | Devicefarm Project | terraform | devicefarmProject | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/aws-resource.png | Directory Service Conditional Forwarder | terraform | directoryServiceConditionalForwarder | accountResource |
+| ../../_images/aws-resource.png | Directory Service Directory | terraform | directoryServiceDirectory | accountResource |
+| ../../_images/aws-resource.png | Directory Service Log Subscription | terraform | directoryServiceLogSubscription | accountResource |
+| ../../_images/azure-compute.png | Disk Encryption Set | terraform | DiskEncryptionSet | accountResource |
+| ../../_images/aws-resource.png | Dlm Lifecycle Policy | terraform | dlmLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Dms Certificate | terraform | dmsCertificate | accountResource |
+| ../../_images/aws-resource.png | Dms Endpoint | terraform | dmsEndpoint | accountResource |
+| ../../_images/aws-resource.png | Dms Event Subscription | terraform | dmsEventSubscription | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Instance | terraform | dmsReplicationInstance | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Subnet Group | terraform | dmsReplicationSubnetGroup | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Task | terraform | dmsReplicationTask | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS AAAA Record | terraform | DNSAAAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CAA Record | terraform | DNSCAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS PTR Record | terraform | DNSPTRRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster | terraform | docdbCluster | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Instance | terraform | docdbClusterInstance | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Parameter Group | terraform | docdbClusterParameterGroup | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Snapshot | terraform | docdbClusterSnapshot | accountResource |
+| ../../_images/aws-resource.png | Docdb Subnet Group | terraform | docdbSubnetGroup | accountResource |
+| ../../_images/aws-directconnect.png | Dx Bgp Peer | terraform | dxBgpPeer | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection | terraform | dxConnection | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection Association | terraform | dxConnectionAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway | terraform | dxGateway | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association | terraform | dxGatewayAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association Proposal | terraform | dxGatewayAssociationProposal | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface | terraform | dxHostedPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface Accepter | terraform | dxHostedPrivateVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface | terraform | dxHostedPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface Accepter | terraform | dxHostedPublicVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface | terraform | dxHostedTransitVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface Accepter | terraform | dxHostedTransitVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Lag | terraform | dxLag | accountResource |
+| ../../_images/aws-directconnect.png | Dx Private Virtual Interface | terraform | dxPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Public Virtual Interface | terraform | dxPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Transit Virtual Interface | terraform | dxTransitVirtualInterface | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Global Table | terraform | dynamodbGlobalTable | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table | terraform | dynamodbTable | accountResource |
+| ../../_images/aws-dynamodb.png | DynamoDB Table | cloudFormation | Table | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table Item | terraform | dynamodbTableItem | accountResource |
+| ../../_images/aws-ec2.png | Ebs Default Kms Key | terraform | ebsDefaultKmsKey | accountResource |
+| ../../_images/aws-ec2.png | Ebs Encryption By Default | terraform | ebsEncryptionByDefault | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot | terraform | ebsSnapshot | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot Copy | terraform | ebsSnapshotCopy | accountResource |
+| ../../_images/aws-ec2.png | Ebs Volume | terraform | ebsVolume | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Availability Zone Group | terraform | ec2AvailabilityZoneGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Capacity Reservation | cloudFormation | CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Capacity Reservation | terraform | ec2CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Authorization Rule | cloudFormation | ClientVpnAuthorizationRule | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Endpoint | cloudFormation | ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Endpoint | terraform | ec2ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Network Association | terraform | ec2ClientVpnNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Route | cloudFormation | ClientVpnRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Target Network Association | cloudFormation | ClientVpnTargetNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Customer Gateway | cloudFormation | CustomerGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 DHCP Options | cloudFormation | DHCPOptions | accountResource |
+| ../../_images/aws-ec2.png | EC2 Egress Only Internet Gateway | cloudFormation | EgressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP | cloudFormation | EIP | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP Association | cloudFormation | EIPAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Fleet | cloudFormation | EC2Fleet | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Fleet | terraform | ec2Fleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Flow Log | cloudFormation | FlowLog | accountResource |
+| ../../_images/aws-ec2.png | EC2 Host | cloudFormation | Host | accountResource |
+| ../../_images/aws-ec2.png | EC2 Instance | cloudFormation | Instance | instance |
+| ../../_images/aws-ec2.png | EC2 Internet Gateway | cloudFormation | InternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Launch Template | cloudFormation | LaunchTemplate | accountResource |
+| ../../_images/aws-ec2.png | EC2 Nat Gateway | cloudFormation | NatGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl | cloudFormation | NetworkAcl | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl Entry | cloudFormation | NetworkAclEntry | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface | cloudFormation | NetworkInterface | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Attachment | cloudFormation | NetworkInterfaceAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Permission | cloudFormation | NetworkInterfacePermission | accountResource |
+| ../../_images/aws-ec2.png | EC2 Placement Group | cloudFormation | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route Table | cloudFormation | RouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Egress | cloudFormation | SecurityGroupEgress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Spot Fleet | cloudFormation | SpotFleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet | cloudFormation | Subnet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Cidr Block | cloudFormation | SubnetCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Network Acl Association | cloudFormation | SubnetNetworkAclAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Route Table Association | cloudFormation | SubnetRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter | terraform | ec2TrafficMirrorFilter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter Rule | terraform | ec2TrafficMirrorFilterRule | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Session | terraform | ec2TrafficMirrorSession | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Target | terraform | ec2TrafficMirrorTarget | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway | terraform | ec2TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway | cloudFormation | TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Attachment | cloudFormation | TransitGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment | terraform | ec2TransitGatewayPeeringAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment Accepter | terraform | ec2TransitGatewayPeeringAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route | terraform | ec2TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route | cloudFormation | TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table | terraform | ec2TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table | cloudFormation | TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Association | terraform | ec2TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Association | cloudFormation | TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Propagation | terraform | ec2TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Propagation | cloudFormation | TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment | terraform | ec2TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway VPC Attachment | cloudFormation | TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment Accepter | terraform | ec2TransitGatewayVpcAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume | cloudFormation | Volume | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume Attachment | cloudFormation | VolumeAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC | cloudFormation | VPC | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Cidr Block | cloudFormation | VPCCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC DHCP Options Association | cloudFormation | VPCDHCPOptionsAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint | cloudFormation | VPCEndpoint | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Connection Notification | cloudFormation | VPCEndpointConnectionNotification | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service | cloudFormation | VPCEndpointService | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service Permissions | cloudFormation | VPCEndpointServicePermissions | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Gateway Attachment | cloudFormation | VPCGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Peering Connection | cloudFormation | VPCPeeringConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection | cloudFormation | VPNConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection Route | cloudFormation | VPNConnectionRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway | cloudFormation | VPNGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway Route Propagation | cloudFormation | VPNGatewayRoutePropagation | accountResource |
+| ../../_images/aws-resource.png | Ecr Lifecycle Policy | terraform | ecrLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository | terraform | ecrRepository | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository Policy | terraform | ecrRepositoryPolicy | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Capacity Provider | terraform | ecsCapacityProvider | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Cluster | terraform | ecsCluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Service | terraform | ecsService | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Service | cloudFormation | Service | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Task Definition | terraform | ecsTaskDefinition | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Task Definition | cloudFormation | TaskDefinition | accountResource |
+| ../../_images/aws-efs.png | Efs File System | terraform | efsFileSystem | accountResource |
+| ../../_images/aws-efs.png | EFS FileSystem | cloudFormation | FileSystem | accountResource |
+| ../../_images/aws-efs.png | Efs Mount Target | terraform | efsMountTarget | accountResource |
+| ../../_images/aws-efs.png | EFS Mount Target | cloudFormation | MountTarget | accountResource |
+| ../../_images/aws-vpc.png | Egress Only Internet Gateway | terraform | egressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | Eip | terraform | eip | accountResource |
+| ../../_images/aws-ec2.png | Eip Association | terraform | eipAssociation | accountResource |
+| ../../_images/aws-eks.png | EKS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-eks.png | Eks Cluster | terraform | eksCluster | accountResource |
+| ../../_images/aws-eks.png | Eks Fargate Profile | terraform | eksFargateProfile | accountResource |
+| ../../_images/aws-eks.png | Eks Node Group | terraform | eksNodeGroup | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | cloudFormation | Application | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | terraform | elasticBeanstalkApplication | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | cloudFormation | ApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | terraform | elasticBeanstalkApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | cloudFormation | ConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | terraform | elasticBeanstalkConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | terraform | elasticBeanstalkEnvironment | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | cloudFormation | Environment | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Cluster | cloudFormation | CacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Cluster | terraform | elasticacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Parameter Group | terraform | elasticacheParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Parameter Group | cloudFormation | ParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Replication Group | terraform | elasticacheReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Replication Group | cloudFormation | ReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Security Group | terraform | elasticacheSecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Subnet Group | terraform | elasticacheSubnetGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Subnet Group | cloudFormation | SubnetGroup | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain | terraform | elasticsearchDomain | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain Policy | terraform | elasticsearchDomainPolicy | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Pipeline | terraform | elastictranscoderPipeline | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Preset | terraform | elastictranscoderPreset | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb | terraform | elb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb Attachment | terraform | elbAttachment | accountResource |
+| ../../_images/aws-emr.png | EMR Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-emr.png | Emr Cluster | terraform | emrCluster | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Fleet Config | cloudFormation | InstanceFleetConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Instance Group | terraform | emrInstanceGroup | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Group Config | cloudFormation | InstanceGroupConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Security Configuration | terraform | emrSecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Security Configuration | cloudFormation | SecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Step | cloudFormation | Step | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Domain | terraform | EventGridDomain | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Event Subscription | terraform | EventGridEventSubscription | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Topic | terraform | EventGridTopic | accountResource |
+| ../../_images/azure-messaging.png | Event Hub | terraform | EventHub | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Authorization Rule | terraform | EventHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Consumer Group | terraform | EventHubConsumerGroup | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Disaster Recovery Config | terraform | EventHubDisasterRecoveryConfig | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace | terraform | EventHubNamespace | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace Authorization Rule | terraform | EventHubNamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Authorization | terraform | ExpressRouteCircuitAuthorization | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Firewall | terraform | Firewall | accountResource |
+| ../../_images/azure-network.png | Firewall Application Rule Collection | terraform | FirewallApplicationRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Network Rule Collection | terraform | FirewallNetworkRuleCollection | accountResource |
+| ../../_images/aws-vpc.png | Flow Log | terraform | flowLog | accountResource |
+| ../../_images/aws-resource.png | Fms Admin Account | terraform | fmsAdminAccount | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/aws-fsx.png | Fsx Lustre File System | terraform | fsxLustreFileSystem | accountResource |
+| ../../_images/aws-fsx.png | Fsx Windows File System | terraform | fsxWindowsFileSystem | accountResource |
+| ../../_images/azure-resource.png | Function App | terraform | FunctionApp | accountResource |
+| ../../_images/azure-resource.png | Function App Slot | terraform | FunctionAppSlot | accountResource |
+| ../../_images/aws-resource.png | Gamelift Alias | terraform | gameliftAlias | accountResource |
+| ../../_images/aws-resource.png | Gamelift Build | terraform | gameliftBuild | accountResource |
+| ../../_images/aws-resource.png | Gamelift Fleet | terraform | gameliftFleet | accountResource |
+| ../../_images/aws-resource.png | Gamelift Game Session Queue | terraform | gameliftGameSessionQueue | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault | terraform | glacierVault | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault Lock | terraform | glacierVaultLock | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Accelerator | terraform | globalacceleratorAccelerator | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Endpoint Group | terraform | globalacceleratorEndpointGroup | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Listener | terraform | globalacceleratorListener | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Database | terraform | glueCatalogDatabase | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Table | terraform | glueCatalogTable | accountResource |
+| ../../_images/aws-glue.png | Glue Classifier | terraform | glueClassifier | accountResource |
+| ../../_images/aws-glue.png | Glue Connection | terraform | glueConnection | accountResource |
+| ../../_images/aws-glue.png | Glue Crawler | terraform | glueCrawler | accountResource |
+| ../../_images/aws-glue.png | Glue Job | terraform | glueJob | accountResource |
+| ../../_images/aws-glue.png | Glue Security Configuration | terraform | glueSecurityConfiguration | accountResource |
+| ../../_images/aws-glue.png | Glue Trigger | terraform | glueTrigger | accountResource |
+| ../../_images/aws-glue.png | Glue Workflow | terraform | glueWorkflow | accountResource |
+| ../../_images/aws-resource.png | Guardduty Detector | terraform | guarddutyDetector | accountResource |
+| ../../_images/aws-resource.png | Guardduty Invite Accepter | terraform | guarddutyInviteAccepter | accountResource |
+| ../../_images/aws-resource.png | Guardduty Ipset | terraform | guarddutyIpset | accountResource |
+| ../../_images/aws-resource.png | Guardduty Member | terraform | guarddutyMember | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Admin Account | terraform | guarddutyOrganizationAdminAccount | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Configuration | terraform | guarddutyOrganizationConfiguration | accountResource |
+| ../../_images/aws-resource.png | Guardduty Threatintelset | terraform | guarddutyThreatintelset | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Hadoop Cluster | terraform | HDInsightHadoopCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight HBase Cluster | terraform | HDInsightHBaseCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Kafka Cluster | terraform | HDInsightKafkaCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight ML Services Cluster | terraform | HDInsightMLServicesCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Query Cluster | terraform | HDInsightQueryCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight R Cluster | terraform | HDInsightRCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Spark Cluster | terraform | HDInsightSparkCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Storm Cluster | terraform | HDInsightStormCluster | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-storage.png | HPC Cache | terraform | HPCCache | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/aws-iam.png | IAM Access Key | cloudFormation | AccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Access Key | terraform | iamAccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Account Alias | terraform | iamAccountAlias | accountResource |
+| ../../_images/aws-resource.png | Iam Account Password Policy | terraform | iamAccountPasswordPolicy | accountResource |
+| ../../_images/aws-iam.png | IAM Group | cloudFormation | Group | accountResource |
+| ../../_images/aws-resource.png | Iam Group | terraform | iamGroup | accountResource |
+| ../../_images/aws-resource.png | Iam Group Membership | terraform | iamGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy | terraform | iamGroupPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy Attachment | terraform | iamGroupPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Instance Profile | terraform | iamInstanceProfile | accountResource |
+| ../../_images/aws-resource.png | IAM Instance Profile | cloudFormation | InstanceProfile | accountResource |
+| ../../_images/aws-iam.png | IAM Managed Policy | cloudFormation | ManagedPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Openid Connect Provider | terraform | iamOpenidConnectProvider | accountResource |
+| ../../_images/aws-iam.png | Iam Policy | terraform | iamPolicy | accountResource |
+| ../../_images/aws-resource.png | IAM Policy | cloudFormation | Policy | accountResource |
+| ../../_images/aws-resource.png | Iam Policy Attachment | terraform | iamPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Role | terraform | iamRole | accountResource |
+| ../../_images/aws-resource.png | IAM Role | cloudFormation | Role | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy | terraform | iamRolePolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy Attachment | terraform | iamRolePolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam Saml Provider | terraform | iamSamlProvider | accountResource |
+| ../../_images/aws-resource.png | Iam Server Certificate | terraform | iamServerCertificate | accountResource |
+| ../../_images/aws-iam.png | Iam Service Linked Role | terraform | iamServiceLinkedRole | accountResource |
+| ../../_images/aws-resource.png | IAM Service Linked Role | cloudFormation | ServiceLinkedRole | accountResource |
+| ../../_images/aws-iam.png | Iam User | terraform | iamUser | accountResource |
+| ../../_images/aws-resource.png | IAM User | cloudFormation | User | accountResource |
+| ../../_images/aws-iam.png | IAM User Group Addition | cloudFormation | UserToGroupAddition | accountResource |
+| ../../_images/aws-resource.png | Iam User Group Membership | terraform | iamUserGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam User Login Profile | terraform | iamUserLoginProfile | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy | terraform | iamUserPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy Attachment | terraform | iamUserPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam User Ssh Key | terraform | iamUserSshKey | accountResource |
+| ../../_images/azure-compute.png | Image | terraform | Image | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Target | terraform | inspectorAssessmentTarget | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Template | terraform | inspectorAssessmentTemplate | accountResource |
+| ../../_images/aws-resource.png | Inspector Resource Group | terraform | inspectorResourceGroup | accountResource |
+| ../../_images/aws-ec2.png | Instance | terraform | Instance | instance |
+| ../../_images/aws-vpc.png | Internet Gateway | terraform | internetGateway | accountResource |
+| ../../_images/azure-iot-central-application.png | IOT Central Application | terraform | IOTCentralApplication | accountResource |
+| ../../_images/aws-resource.png | Iot Certificate | terraform | iotCertificate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub | terraform | IOTHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Access Policy | terraform | IOTHubAccessPolicy | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Consumer Group | terraform | IOTHubConsumerGroup | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS | terraform | IOTHubDPS | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS Certficiate | terraform | IOTHubDPSCertficiate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Queue | terraform | IOTHubEndpointQueue | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Storage | terraform | IOTHubEndpointStorage | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Topic | terraform | IOTHubEndpointTopic | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Fallback Route | terraform | IOTHubFallbackRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Route | terraform | IOTHubRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Shared Access Policy | terraform | IOTHubSharedAccessPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy | terraform | iotPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy Attachment | terraform | iotPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Role Alias | terraform | iotRoleAlias | accountResource |
+| ../../_images/aws-resource.png | Iot Thing | terraform | iotThing | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Principal Attachment | terraform | iotThingPrincipalAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Type | terraform | iotThingType | accountResource |
+| ../../_images/aws-resource.png | Iot Topic Rule | terraform | iotTopicRule | accountResource |
+| ../../_images/aws-ec2.png | Key Pair | terraform | keyPair | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault | terraform | KeyVault | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Analytics Application | terraform | kinesisAnalyticsApplication | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Firehose Delivery Stream | terraform | kinesisFirehoseDeliveryStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | terraform | kinesisStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | cloudFormation | Stream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream Consumer | cloudFormation | StreamConsumer | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Video Stream | terraform | kinesisVideoStream | accountResource |
+| ../../_images/aws-resource.png | Kms Alias | terraform | kmsAlias | accountResource |
+| ../../_images/aws-resource.png | Kms Ciphertext | terraform | kmsCiphertext | accountResource |
+| ../../_images/aws-resource.png | Kms External Key | terraform | kmsExternalKey | accountResource |
+| ../../_images/aws-resource.png | Kms Grant | terraform | kmsGrant | accountResource |
+| ../../_images/aws-resource.png | Kms Key | terraform | kmsKey | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Cluster | terraform | KustoCluster | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database | terraform | KustoDatabase | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database Principal | terraform | KustoDatabasePrincipal | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Event Data Connection | terraform | KustoEventDataConnection | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | cloudFormation | Alias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | terraform | lambdaAlias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | cloudFormation | EventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | terraform | lambdaEventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | cloudFormation | Function | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | terraform | lambdaFunction | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function Event Invoke Config | terraform | lambdaFunctionEventInvokeConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | terraform | lambdaLayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | cloudFormation | LayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version Permission | cloudFormation | LayerVersionPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | terraform | lambdaPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | cloudFormation | Permission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Provisioned Concurrency Config | terraform | lambdaProvisionedConcurrencyConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Version | cloudFormation | Version | accountResource |
+| ../../_images/aws-ec2.png | Launch Configuration | terraform | launchConfiguration | accountResource |
+| ../../_images/aws-ec2.png | Launch Template | terraform | launchTemplate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb | terraform | lb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Cookie Stickiness Policy | terraform | lbCookieStickinessPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener | terraform | lbListener | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Certificate | terraform | lbListenerCertificate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Rule | terraform | lbListenerRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Ssl Negotiation Policy | terraform | lbSslNegotiationPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group | terraform | lbTargetGroup | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group Attachment | terraform | lbTargetGroupAttachment | accountResource |
+| ../../_images/aws-resource.png | Licensemanager Association | terraform | licensemanagerAssociation | accountResource |
+| ../../_images/aws-resource.png | Licensemanager License Configuration | terraform | licensemanagerLicenseConfiguration | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Domain | terraform | lightsailDomain | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Instance | terraform | lightsailInstance | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Key Pair | terraform | lightsailKeyPair | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip | terraform | lightsailStaticIp | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip Attachment | terraform | lightsailStaticIpAttachment | accountResource |
+| ../../_images/azure-compute.png | Linux VM Scale Set | terraform | LinuxVMScaleSet | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Backend Server Policy | terraform | loadBalancerBackendServerPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Listener Policy | terraform | loadBalancerListenerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Policy | terraform | loadBalancerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-network.png | Local Network Gateway | terraform | LocalNetworkGateway | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-machinelearning.png | Machine Learning Workspace | terraform | MachineLearningWorkspace | accountResource |
+| ../../_images/aws-resource.png | Macie Member Account Association | terraform | macieMemberAccountAssociation | accountResource |
+| ../../_images/aws-resource.png | Macie S3 Bucket Association | terraform | macieS3BucketAssociation | accountResource |
+| ../../_images/aws-vpc.png | Main Route Table Association | terraform | mainRouteTableAssociation | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-compute.png | Managed Application | terraform | ManagedApplication | accountResource |
+| ../../_images/azure-compute.png | Managed Disk | terraform | ManagedDisk | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-database.png | MariaDb Configuration | terraform | MariaDbConfiguration | accountResource |
+| ../../_images/azure-database.png | MariaDb Database | terraform | MariaDbDatabase | accountResource |
+| ../../_images/azure-database.png | MariaDb Firewall Rule | terraform | MariaDbFirewallRule | accountResource |
+| ../../_images/azure-database.png | MariaDb Server | terraform | MariaDbServer | accountResource |
+| ../../_images/azure-database.png | MariaDb Virtual Network Rule | terraform | MariaDbVirtualNetworkRule | accountResource |
+| ../../_images/azure-compute.png | Marketplace Agreement | terraform | MarketplaceAgreement | accountResource |
+| ../../_images/aws-resource.png | Media Convert Queue | terraform | mediaConvertQueue | accountResource |
+| ../../_images/aws-resource.png | Media Package Channel | terraform | mediaPackageChannel | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/aws-resource.png | Media Store Container | terraform | mediaStoreContainer | accountResource |
+| ../../_images/aws-resource.png | Media Store Container Policy | terraform | mediaStoreContainerPolicy | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/aws-mq.png | MQ Broker | cloudFormation | Broker | accountResource |
+| ../../_images/aws-mq.png | Mq Broker | terraform | mqBroker | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration | cloudFormation | Configuration | accountResource |
+| ../../_images/aws-mq.png | Mq Configuration | terraform | mqConfiguration | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration Association | cloudFormation | ConfigurationAssociation | accountResource |
+| ../../_images/azure-database.png | MS SQL Database | terraform | MSSQLDatabase | accountResource |
+| ../../_images/azure-database.png | MS SQL Elastic Pool | terraform | MSSQLElasticPool | accountResource |
+| ../../_images/azure-database.png | MS SQL Security Alert Policy | terraform | MSSQLSecurityAlertPolicy | accountResource |
+| ../../_images/azure-database.png | MS SQL Server | terraform | MSSQLServer | accountResource |
+| ../../_images/azure-database.png | MS SQL Vm | terraform | MSSQLVm | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment | terraform | MSSQLVulnerabilityAssessment | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment Rule Baseline | terraform | MSSQLVulnerabilityAssessmentRuleBaseline | accountResource |
+| ../../_images/aws-resource.png | Msk Cluster | terraform | mskCluster | accountResource |
+| ../../_images/aws-resource.png | Msk Configuration | terraform | mskConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Configuration | terraform | MySQLConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Database | terraform | MySQLDatabase | accountResource |
+| ../../_images/azure-database.png | MySQL Firewall Rule | terraform | MySQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | MySQL Server | terraform | MySQLServer | accountResource |
+| ../../_images/azure-database.png | MySQL Virtual Network Rule | terraform | MySQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-messaging.png | Namespace Authorization Rule | terraform | NamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Nat Gateway | terraform | NatGateway | accountResource |
+| ../../_images/aws-vpc.png | Nat Gateway | terraform | natGateway | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster | terraform | neptuneCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Instance | terraform | neptuneClusterInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Parameter Group | terraform | neptuneClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Snapshot | terraform | neptuneClusterSnapshot | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster Parameter Group | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Event Subscription | terraform | neptuneEventSubscription | accountResource |
+| ../../_images/aws-neptune.png | Neptune Parameter Group | terraform | neptuneParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Subnet Group | terraform | neptuneSubnetGroup | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Pool | terraform | NetAppPool | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/aws-vpc.png | Network Acl | terraform | networkAcl | accountResource |
+| ../../_images/aws-vpc.png | Network Acl Rule | terraform | networkAclRule | accountResource |
+| ../../_images/azure-network.png | Network DDos Protection Plan | terraform | NetworkDDosProtectionPlan | accountResource |
+| ../../_images/azure-network.png | Network Gateway | terraform | NetworkGateway | accountResource |
+| ../../_images/azure-network.png | Network Interface | terraform | NetworkInterface | accountResource |
+| ../../_images/aws-vpc.png | Network Interface | terraform | networkInterface | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Gateway Backend Address Pool Association | terraform | NetworkInterfaceApplicationGatewayBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Security Group Association | terraform | NetworkInterfaceApplicationSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Attachment | terraform | networkInterfaceAttachment | accountResource |
+| ../../_images/azure-network.png | Network Interface Backend Address Pool Association | terraform | NetworkInterfaceBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Nat Rule Association | terraform | NetworkInterfaceNatRuleAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Security Group Association | terraform | NetworkInterfaceSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Sg Attachment | terraform | networkInterfaceSgAttachment | accountResource |
+| ../../_images/azure-network.png | Network Packet Capture | terraform | NetworkPacketCapture | accountResource |
+| ../../_images/azure-network.png | Network Profile | terraform | NetworkProfile | accountResource |
+| ../../_images/azure-network.png | Network Security Group | terraform | NetworkSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Network Security Rule | terraform | NetworkSecurityRule | accountResource |
+| ../../_images/azure-network.png | Network Watcher | terraform | NetworkWatcher | accountResource |
+| ../../_images/azure-network.png | Network Watcher Flow Log | terraform | NetworkWatcherFlowLog | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub | terraform | NotificationHub | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Authorization Rule | terraform | NotificationHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Namespace | terraform | NotificationHubNamespace | accountResource |
+| ../../_images/aws-resource.png | Opsworks Application | terraform | opsworksApplication | accountResource |
+| ../../_images/aws-resource.png | Opsworks Custom Layer | terraform | opsworksCustomLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Ganglia Layer | terraform | opsworksGangliaLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Haproxy Layer | terraform | opsworksHaproxyLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Instance | terraform | opsworksInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Java App Layer | terraform | opsworksJavaAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Memcached Layer | terraform | opsworksMemcachedLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Mysql Layer | terraform | opsworksMysqlLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Nodejs App Layer | terraform | opsworksNodejsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Permission | terraform | opsworksPermission | accountResource |
+| ../../_images/aws-resource.png | Opsworks Php App Layer | terraform | opsworksPhpAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rails App Layer | terraform | opsworksRailsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rds Db Instance | terraform | opsworksRdsDbInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Stack | terraform | opsworksStack | accountResource |
+| ../../_images/aws-resource.png | Opsworks Static Web Layer | terraform | opsworksStaticWebLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks User Profile | terraform | opsworksUserProfile | accountResource |
+| ../../_images/aws-resource.png | Organizations Account | terraform | organizationsAccount | accountResource |
+| ../../_images/aws-resource.png | Organizations Organization | terraform | organizationsOrganization | accountResource |
+| ../../_images/aws-resource.png | Organizations Organizational Unit | terraform | organizationsOrganizationalUnit | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy | terraform | organizationsPolicy | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy Attachment | terraform | organizationsPolicyAttachment | accountResource |
+| ../../_images/azure-network.png | Packet Capture | terraform | PacketCapture | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Adm Channel | terraform | pinpointAdmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Channel | terraform | pinpointApnsChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Sandbox Channel | terraform | pinpointApnsSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Channel | terraform | pinpointApnsVoipChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Sandbox Channel | terraform | pinpointApnsVoipSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint App | terraform | pinpointApp | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Baidu Channel | terraform | pinpointBaiduChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Email Channel | terraform | pinpointEmailChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Event Stream | terraform | pinpointEventStream | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Gcm Channel | terraform | pinpointGcmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Sms Channel | terraform | pinpointSmsChannel | accountResource |
+| ../../_images/azure-compute.png | Placement Group | terraform | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | Placement Group | terraform | placementGroup | accountResource |
+| ../../_images/azure-network.png | Point To Site VPN Gateway | terraform | PointToSiteVPNGateway | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Configuration | terraform | PostgreSQLConfiguration | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Database | terraform | PostgreSQLDatabase | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Firewall Rule | terraform | PostgreSQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Server | terraform | PostgreSQLServer | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Virtual Network Rule | terraform | PostgreSQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-power-bi.png | PowerBI | terraform | PowerBI | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-network.png | Private Endpoint | terraform | PrivateEndpoint | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Proxy Protocol Policy | terraform | proxyProtocolPolicy | accountResource |
+| ../../_images/azure-network.png | Public IP | terraform | PublicIP | accountResource |
+| ../../_images/azure-network.png | Public IP Prefix | terraform | PublicIPPrefix | accountResource |
+| ../../_images/aws-resource.png | Qldb Ledger | terraform | qldbLedger | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight Group | terraform | quicksightGroup | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight User | terraform | quicksightUser | accountResource |
+| ../../_images/aws-resource.png | Ram Principal Association | terraform | ramPrincipalAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Association | terraform | ramResourceAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share | terraform | ramResourceShare | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share Accepter | terraform | ramResourceShareAccepter | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster | terraform | rdsCluster | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Endpoint | terraform | rdsClusterEndpoint | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Instance | terraform | rdsClusterInstance | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Parameter Group | terraform | rdsClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster ParameterGroup | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-rds.png | RDS DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group | cloudFormation | DBSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group Ingress | cloudFormation | DBSecurityGroupIngress | accountResource |
+| ../../_images/aws-rds.png | RDS DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | RDS Event Subscription | cloudFormation | EventSubscription | accountResource |
+| ../../_images/aws-rds.png | Rds Global Cluster | terraform | rdsGlobalCluster | accountResource |
+| ../../_images/aws-rds.png | RDS Option Group | cloudFormation | OptionGroup | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Redis Cache | terraform | RedisCache | accountResource |
+| ../../_images/azure-recovery.png | Redis Firewall Rule | terraform | RedisFirewallRule | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | terraform | redshiftCluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Parameter Group | cloudFormation | ClusterParameterGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group | cloudFormation | ClusterSecurityGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group Ingress | cloudFormation | ClusterSecurityGroupIngress | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Subnet Group | cloudFormation | ClusterSubnetGroup | accountResource |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json b/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
new file mode 100644
index 0000000..0ae42cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+  "title": "Tenants",
+  "ordinal": 273,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md b/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
new file mode 100644
index 0000000..d32178c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
@@ -0,0 +1,9 @@
+# Tenants
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html)**
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html)**
+- **[Tenant Users](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html)**
+- **[Configuring Tenants and Resources for Multi-Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json b/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
new file mode 100644
index 0000000..8a009da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+  "title": "Cloud Access Levels",
+  "ordinal": 298,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Access Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md b/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
new file mode 100644
index 0000000..8a35df7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
@@ -0,0 +1,13 @@
+# Cloud Access Levels
+
+When creating or editing a Tenant Role, Master Tenant administrators can choose which publicly-visible Clouds to share with Tenants having the current Role. Access can be completely restricted or administrators can choose between Read and Full access.
+
+## Read Access
+
+Master Tenant administrators can opt to give other Tenants read-level access to any integrated Clouds through the Tenant Role. A read-only Cloud allows the Master Tenant to assign resources for viewing by Subtenant users but not allow them to perform any actions or provision new Instances.
+
+With read-level access, Subtenant users will have access to the Cloud detail page (Infrastructure > Clouds). From the Summary subtab on the Cloud detail page, high-level information on Cloud resources are shown regardless of specific resources that have been shared with the Subtenant. Other metrics, such as costing, resource percentages (CPU, Memory, and Storage), VM counts and host counts will only be populated when servers in the Cloud have been assigned to the Tenant.
+
+## Full Access
+
+With full access, Subtenant users also have access to the Cloud detail page (Infrastructure > Clouds > Specific Cloud) and see the same level of detail as Subtenants with read-only rights. However, with full access, Subtenant users can also perform many actions including the addition of Clusters, Hosts, and VMs, changing networks, and more. This cloud will also be selectable as a provisioning target for Subtenant users when deploying Instances or Apps.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json b/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
new file mode 100644
index 0000000..8ae503d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+  "title": "Image Management",
+  "ordinal": 404,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html",
+  "topic_cluster": {
+    "clustering_title": "Image Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md b/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
new file mode 100644
index 0000000..0318c05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
@@ -0,0 +1,7 @@
+# Image Management
+
+The topic describes about image catalog and uploading various images.
+
+**Subtopics**  
+
+- **[Image Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json b/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
new file mode 100644
index 0000000..258b976
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+  "title": "Mapping",
+  "ordinal": 249,
+  "parent_title": "Boot",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Mapping",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md b/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
new file mode 100644
index 0000000..fd59117
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
@@ -0,0 +1,51 @@
+# Mapping
+
+## Add Mapping
+
+### Procedure
+
+1. Select the Mapping tab then click the Add Mapping button.
+2. From the New Mapping Wizard input the following information: 
+
+   Match Pattern
+   :   Mac address separated by ‘:’ or an ip address filter
+
+   Description(optional)
+   :   Description of the new mapping.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Operating System
+   :   List of operating systems for the mapping.
+
+   Boot Image
+   :   Lists available PXE boot images.
+
+   Answer File
+   :   Lists available answer files.
+
+   Cloud
+   :   Lists the available clouds.
+
+   Server Mode
+   :   List of server modes:: unmanaged, Managed, Bare metal host, Container host, VM host, and Container & VM host.
+3. Save
+
+### Results
+
+Once the mapping is added, and the target host is powered on, the {morpheus} PXE menu will load and PXE boot will start.
+
+## Edit Mapping
+
+### Procedure
+
+1. Click the edit icon on the row of the mapping you wish to edit.
+2. Modify information as needed.
+3. Click the Save Changes button to save.
+
+### Results
+
+Delete Mapping
+
+1. Click the delete icon on the row of the mapping you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json b/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
new file mode 100644
index 0000000..307406f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+  "title": "Managed Networks",
+  "ordinal": 430,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html",
+  "topic_cluster": {
+    "clustering_title": "Managed Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md b/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
new file mode 100644
index 0000000..7f4a0c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
@@ -0,0 +1,13 @@
+# Managed Networks
+
+The managed network mode is used when the network infrastructure is to be managed by Morpheus. In this case, the user can select ArubCX-Int during the cloud creation.
+
+## Adding HPE ArubaCX Plugin
+
+In the managed network mode, the Aruba CX switches are supported as managed switches. To enable that, the ArubaCX plugin needs to be loaded.
+
+You can load the ArubaCX plugin jar using the Administration > Integrations.
+
+**Subtopics**  
+
+- **[Creating ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..1845212
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 53,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..1d52a7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,12 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2277183A-E315-4439-A885-C111A77C7154.html)**
+- **[Reports](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html)**
+- **[Analytics](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html)**
+- **[Costing](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html)**
+- **[Approvals](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json b/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
new file mode 100644
index 0000000..6a28a0b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+  "title": "Whitelabel",
+  "ordinal": 322,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html",
+  "topic_cluster": {
+    "clustering_title": "Whitelabel",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md b/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
new file mode 100644
index 0000000..4b31d70
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
@@ -0,0 +1,114 @@
+# Whitelabel
+
+## Whitelabel Settings
+
+### Overview
+
+HPE Morpheus Enterprise Tenants can be WhiteLabeled with custom Logos, Colors, Copy, and custom CSS. Sub-Tenants can be individually white-labeled, or the Master Tenant Whitelabel can apply to all Sub-Tenants.
+
+Enable Whitelabel
+:   Turns on the configured Whitelabel settings. Disabling will return the Appliance to the default colors and logos, but the configured options will remain saved and will apply if Whitelabel is re-enabled.
+
+Appliance Name
+:   Replaces HPE Morpheus Enterprise in page titles.
+
+Header Logo
+:   Top left header logo. Uploaded image is resized to 38 pixels high with a proportional width at that height.
+
+Disable Support Menu
+:   Enable this flag to hide the support dropdown menu in the header.
+
+Support Menu Links
+:   Customize support links. Label Code can be used for translations and is optional. Be sure to specify fully qualified url if linking to external sites.
+
+Security Banner
+:   The Security Banner section in `/admin/settings#!whitelabel` displays content on the login screen for Security and Consent messaging and warnings.
+    :   - Applicable at Global and Tenant levels
+        - Security Banner input field accepts plain text and markdown
+        - Content is displayed below login section in scoped `/login/auth` pages.
+
+Footer Logo
+:   Footer Logo in bottom left. Uploaded image is resized to 27 pixels high with a proportional width at that height.
+
+Login Logo
+:   Logo shown on Login screen. Uploaded image is resized to 192 pixels wide with an unbound height proportional to that locked width.
+
+Favicon
+:   Must be a .ico file type.
+
+Reset
+:   When selected and Whitelabel settings are saved, associated logo is returned to blank default value.
+
+### Colors
+
+Update Colors by entering HEX value or selecting the Color Selector pop-up next to each filed and selecting a color.
+
+- Header Background
+- Header Foreground
+- Nav Background
+- Nav Foreground
+- Nav Hover
+- Primary Button Bg
+- Primary Button Fg
+- Primary Button Hover Bg
+- Primary Button Hover Fg
+- Footer Background
+- Footer Foreground
+- Login Background
+
+### Override CSS
+
+Override CSS settings by entering CSS in Override CSS field.
+
+Example: (this will add one continues background image to the Header)
+
+```
+```
+header #topHeader {  
+        background-image: url(http://image_url.png);  
+        }  
+header {  
+        background-image: url(http://image_url.png);  
+        }
+```
+```
+
+### Copy
+
+Add custom Copyright String, Terms of Use, Privacy Policy contained in the Footer text and links in the App and on the login page and emails.
+
+Available Copy fields
+
+- Copyright String
+- Terms and Privacy String
+- Terms of Use
+- Privacy Policy
+
+  NOTE
+
+  Terms of Use and Privacy Policy Footer links will load internal pages at `https://applaince_url/privacy-policy` and `https://applaince_url/terms-of-use` displaying the entered info as plain text. The Terms and Privacy String will update the legal text displayed on the HPE Morpheus Enterprise login page. This field takes any custom HTML markup allowing you to link to the internal legal pages or to your own outside legal pages if you prefer.
+
+### ​UI Loading Page
+
+When the HPE Morpheus Enterprise UI is restarted or loading, a default “Morpheus is Loading” page is displayed. This page can be changed by adding the following to `/etc/morpheus/morpheus.rb` and adjusting the values.
+
+NOTE
+
+`morpheus-ctl reconfigure` must be ran for any chnages to `/etc/morpheus/morpheus.rb` to take effect.
+
+```
+```
+nginx['web_root_internal'] = "/opt/morpheus/embedded/nginx/html"  
+nginx['loading_pages']['max_loops'] = 6 * 10 # 10 secs per loop x 6 times to get 60 seconds * 10 to get to 10 minutes  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['iteration_time'] = 10_000  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json b/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
new file mode 100644
index 0000000..d7d3985
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+  "title": "Monitoring the Cluster",
+  "ordinal": 207,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md b/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
new file mode 100644
index 0000000..916ba43
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
@@ -0,0 +1,20 @@
+# Monitoring the Cluster
+
+After onboarding the cluster into HPE Morpheus Enterprise, a new Cluster object is added to the Clusters list page. Clicking into the Cluster reveals the Cluster detail page. Note the following subtabs and the cluster details we can monitor in each:
+
+- **Nodes:** Master and worker nodes making up the cluster are shown here. Click into any of them to see a node detail page
+- **VMs:** A list of all virtual machines within the scope of the OpenShift cluster are shown. When creating or editing the cluster, an option is given to inventory all existing instances. If selected, all running virtual machines will be onboarded and shown here even if they were provisioned outside of HPE Morpheus Enterprise. If this option is not selected, then only the OpenShift virtual machines provisioned through HPE Morpheus Enterprise are shown. High level details about each virtual machine are also shown, such as power state and resource usage. Click into any virtual machine to see a detail page with additional options
+- **Virtual Images:** A list of virtual images synced to HPE Morpheus Enterprise is shown. Only custom user images are synced, images which are part of the large OpenShift default catalog are not synced. Click into any virtual image to see a detail page and to edit configurations for any images, if necessary
+
+  IMPORTANT
+
+  Virtual Images used for provisioning OpenShift workloads from HPE Morpheus Enterprise must be updated to set appropriate properties prior to use. Edit the Virtual Image to uncheck the "Install Agent?" configuration and check either "Is Cloud Init Enabled?" or "Sysprepped/Generalized Image" depending on the workload-type. Ensure the OpenShift template has VirtIO drivers and QEMU VM agent tools installed. For Windows images, only the "Sysprepped/Generalized Image" option is currently supported. Do not use the Cloudbase-init option until support is added. For Linux-based images, HPE Morpheus Enterprise expects standardized NIC names (eth0, eth1, etc) on templates so that cloud-init can reliably apply network configuration. For Windows templates, HPE Morpheus Enterprise relies on OpenShift standard interface naming (ex. Ethernet Instance 0) in templates. Currently on Windows Instances, configuration of the first network interface is supported as part of deployment via Sysprep.
+- **Networks:** NetworkAttachmentDefinitions (NADs) define virtual network interfaces that can be attached to VMs, acting as network bridges
+
+IMPORTANT
+
+Edit and update synced network objects (OpenShift NADs) in HPE Morpheus Enterprise with appropriate IPv4/IPv6 configuration details (DHCP, Gateway, DNS, Subnet, etc.)
+
+TIP
+
+IP Pools can be associated with the network definitions synced from OpenShift. These can be Morpheus-type IP Pools created within the HPE Morpheus Enterprise UI or can be IP Pools sourced from IPAM integrations. If IP Pools are used, HPE Morpheus Enterprise can manage IP addresses across the Instance lifecycle (claim a free address at provision time, release an address at teardown, etc)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json b/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
new file mode 100644
index 0000000..973bf0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+  "title": "Agent Installation",
+  "ordinal": 46,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md b/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
new file mode 100644
index 0000000..abb2477
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
@@ -0,0 +1,185 @@
+# Agent Installation
+
+There are many methods to install the HPE Morpheus Enterprise Agent on supported targets. All Agent installation methods are executing a script on the target that calls back to the HPE Morpheus Enterprise appliance over port 443.
+
+IMPORTANT
+
+All Agent installation methods require the Target (VM or Host) to resolve and reach the appliance URL over port 443. In addition to the main Appliance URL (in Administration > Settings), additional Appliance URLs can be set per cloud in the Advanced Options section of the Create/Edit Cloud modal. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+## Basic Installation Steps
+
+### Procedure
+
+1. An Agent installation method is used to get the install script onto the target VM or Host
+2. The Agent installation script is executed on the target VM or Host, installing the Agent and all dependencies
+3. The Agent is started and makes a websocket connection to the configured Appliance URL over port 443 using the target VM or Host API key
+
+### Results
+
+It is important to note these are three separate steps with varying requirements. The first requires a path to get the script on the target. The second requires successful execution of the Agent installation script. The third requires a successful websocket connection. Requirements for the successful execution of each step are covered in the sections below.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Modes
+
+Agent Installation Method is determined by:
+
+- The AGENT INSTALL MODE setting on target Cloud: - SSH / WinRM / Guest Execution - Cloud Init / Unattend (when available)
+- Platform / OS type on Virtual Image or target (VM or Host)
+- Virtual Image configuration
+- RPC Mode setting (VMware Clouds only)
+
+## Agent Installation Methods
+
+The Morpheus Agent can be installed with a variety of automated methods. It is important to note these methods simply get the Agent install script to the target. Successful execution of the Agent install script is not directly related to the Agent install method.
+
+SSH
+:   HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+    `curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+WinRM
+:   HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+VMware Tools
+:   HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+Cloud-Init
+:   HPE Morpheus Enterprise executes agentInstall.sh via cloud-init runcmd
+
+Cloudbase-Init
+:   HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+Windows Unattend
+:   HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+Manual
+:   User executes agentInstall.sh or agentInstall.ps1 manually on the VM or Host. These scripts can be obtained on the VM or Host detail page via Actions > DownloadAgent Script
+
+### SSH
+
+#### Process
+
+HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+`curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+#### Requirements
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+#### Process
+
+HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+#### Requirements
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install
+
+### VMware Tools
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+#### Requirements
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init, Guest Customizations, or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install.
+
+### Cloud-Init
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh via Cloud-Init runcmd
+
+#### Requirements
+
+- Cloud-Init is installed on Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Cloud-Init User is configured in the Administration > Settings > Provisioning section
+
+### Cloudbase-init
+
+#### Process
+
+HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+#### Requirements
+
+- Cloudbase-Init is installed on the Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Windows Administrator password defined in the Administration > Settings > Provisioning section
+
+### Windows Unattend
+
+#### Process
+
+HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+#### Requirements
+
+VMware
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “FORCE GUEST CUSTOMIZATION?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record when using DHCP
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+Nutainx/SCVMM/Openstack
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “ENABLED SYSPREP?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+### Manual
+
+#### Process
+
+- From the VM or Host record page (`/infrastructure/servers/${id}`) run ACTIONS > `Download Agent Script`
+- This is will generate an Agent install script based off the target OS and platform, Appliance URL, and API key
+- Manually execute the downloaded script on the Target VM or Host
+
+## Agent Install Requirements
+
+Table 1.
+
+          |  |  |  |  |  |  |  |  |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Agent Installation Requirements | | | | | | | |
+| Requirement | Agent Installation Method | | | | | | |
+| SSH | WINRM | VMWARE TOOLS | CLOUD‐INIT | CLOUDBASE‐INIT | UNATTEND | MANUAL |
+| Target (vm/host) to resolve and reach Appliance URL over 443 | YES | YES | YES | YES | YES | YES | YES |
+| Target (vm/host) to resolve and reach Appliance URL over 80 | Ubuntu 14.04 Only |  | Ubuntu 14.04 Only | Ubuntu 14.04 Only |  |  | Ubuntu 14.04 Only |
+| Websockets enabled when using load balancer | YES | YES | YES | YES | YES | YES | YES |
+| Access to Target VM/Host on port 22 | YES | NO | NO | NO | NO | NO | NO |
+| Access to Target VM/Host on port 5985 | NO | YES | NO | NO | NO | NO | NO |
+| Vmware Tools installed and flagged on Virtual Image | NO | NO | YES | NO | NO | YES | NO |
+| Syspreped Image and Sysprep Enabled flagged on Virtual Image (Nutanix, Openstack, SCVMM) | NO | NO | NO | NO | NO | YES | NO |
+| Force Guest Customizations flagged on Virtual Image | NO | NO | DHCP | NO | NO | DHCP | NO |
+| Cloud‐Init installed and flagged on Virtual Image | NO | NO | NO | YES | YES | NO | NO |
+| Global Cloud‐Init user populated in Administration > Settings > Provisioning | NO | NO | NO | YES | NO | NO | NO |
+| Windows Administrator Password populated in Administration > Settings > Provisioning | NO | NO | NO | NO | YES | YES | NO |
+| Access to configured YUM or APT repos | NO but will cause delay in Agent Install | N/A | NO but will cause delay in Agent Install | NO but will cause delay in Agent Install | N/A | N/A | NO but will cause delay in Agent Install |
+| .net >=4.5.2 (Windows, Morpheus >= 4.1.2) | N/A | YES | YES | N/A | YES | YES | YES |
+| User with Sudo Access set on Virtual Image (Greenfield) | YES | N/A | YES | NO | N/A | N/A | N/A |
+| Administrator User (SID 500) set on Virtual Image (Greenfield) | N/A | YES | YES | N/A | NO | N/A | N/A |
+| User with Sudo Access set on VM/Host Record (Brownfield) | YES | N/A | YES | N/A | N/A | N/A | N/A |
+| Administrator User (SID 500) set on VM/Host Record (Brownfield) | N/A | YES | YES | N/A | N/A | N/A | N/A |
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../../../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json b/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
new file mode 100644
index 0000000..d2637d7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+  "title": "Creating an Option List Based on an LDAP Query",
+  "ordinal": 157,
+  "parent_title": "Options",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Option List Based on an LDAP Query",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md b/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
new file mode 100644
index 0000000..5cea83d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
@@ -0,0 +1,51 @@
+# Creating an Option List Based on an LDAP Query
+
+## About this task
+
+In Morpheus version 4.2.1 and higher, Option Lists can be populated from LDAP queries. This gives users the ability to search Active Directory, capture objects, and present them as custom options where needed.
+
+It’s recommended that you connect LDAP-type Option Lists to Typeahead-type Inputs as the list of returned selections can be very large. This also allows you to select multiple options from the list, presuming you’ve allowed for that when creating the Input.
+
+Populating LDAP-type Option Lists requires knowledge of LDAP query syntax. This guide provides one example and there are many publicly-available resources for help writing additional queries.
+
+## Procedure
+
+1. Create a new Option List (Library > Options > Option Lists > ADD)
+2. Enter a name for the new LDAP Option List
+3. Change the Type value to LDAP and the relevant fields will appear as shown in the screenshot:
+4. Enter the LDAP URL in the following format (an example is also shown as a placeholder in the UI form field): 
+
+   ```
+   ```
+   ldap[s]://<hostname>:<port>/<base_dn>
+   ```
+   ```
+5. Enter the fully qualified username with @ suffix syntax, such as: user@ad.mycompany.com
+6. Enter the account password
+7. Enter your LDAP query. You can even inject variables into your query structure to query based on the value the user has entered into the typeahead field as shown in the example below: 
+
+   ```
+   ```
+   (&(objectClass=user)(cn=<%=phrase%>*))
+   ```
+   ```
+8. Finally, enter a translation script which will convert the returned LDAP object into a list of name:value pairs you can work with in Morpheus. The example script below shows the user DisplayName and sets the value to the SAMAccountName: 
+
+   ```
+   ```
+   for(var x=0;x < data.length ; x++) {  
+     var row = data[x];  
+     var a = {};  
+     if(row.displayName != null) {  
+       a['name'] = row.displayName;  
+     } else {  
+       a['name'] = row.sAMAccountName;  
+     }  
+     a['value'] = row.sAMAccountName;  
+     results.push(a);  
+   }
+   ```
+   ```
+9. Click SAVE CHANGES 
+
+   ![../../_images/ldap_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F3A370B1-BB00-4177-8AF4-D6E5A2975918-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json b/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
new file mode 100644
index 0000000..0d46bcc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+  "title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 363,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md b/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
new file mode 100644
index 0000000..d3e5fd1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
@@ -0,0 +1,358 @@
+# Automated Single-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. In this guide, we will create a custom Instance Type for SuiteCRM which can then be selected during provisioning. Once configured, the provisioning process is completely automated and results in SuiteCRM and a database installed on a single node. There is also an accompanying guide which automates the process for deployed SuiteCRM as a multi-tiered application consisting of a MySQL database on one node and the SuiteCRM application on a second node.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a single-node application:
+
+- Instance Types
+- Layouts
+- Node Types
+- Cypher
+- Archive
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. This could be used to create a provisionable Instance Type on any HPE Morpheus Enterprise-supported Cloud type and it’s intentionally left open-ended to be useful for any environment. As I’m building the example, I’ll show screenshots targeting a build for VMware vCenter Clouds. Despite the screenshots, this guide is useful for any environment.
+
+## Create a HPE Morpheus Enterprise Archive for Install Files
+
+HPE Morpheus Enterprise Archives allow you to store files which can then be made available for download in scripts or by users. Archives are backed by buckets or file shares which must exist prior to creating the Archive. Buckets could be backed by Amazon S3, for example. File Shares could be backed by an NFS file share or even point directly to a local folder on the appliance itself. In this example, we’ll use an S3-backed bucket. With an Amazon AWS Cloud already integrated with HPE Morpheus Enterprise, we can even create the S3 bucket itself without leaving HPE Morpheus Enterprise UI.
+
+To create a new bucket, navigate to Infrastructure > Storage. From the Buckets tab, click + ADD and then select “AWS S3 Bucket”. The example bucket configuration is shown below. Bear in mind if you make any changes you may need to carefully confirm Task configurations and calls to Cypher or Archive to ensure they match any changes you’ve made.
+
+- **NAME:** Automation Training S3 Bucket (this is simply a friendly name for the bucket within HPE Morpheus Enterprise)
+- **Storage Service:** Select your pre-existing AWS Cloud
+- **BUCKET NAME:** Enter a unique name for the bucket (this much conform to AWS bucket naming rules, consult AWS documentation if needed)
+- **CREATE BUCKET:** Checked
+- **REGION:** The AWS region to create the bucket in
+- **ACTIVE:** Checked (this makes it available for use in HPE Morpheus Enterprise)
+
+![../../_images/newBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F1FDC927-C674-4E43-A0EC-C9347212EEC5-high.png)
+
+With the bucket created, we can now create the Archive. Start by going to Tools > Archives and clicking + ADD. In the new Archive, we need to configure the following:
+
+- **NAME:** Software Archive
+- **BUCKET:** Select the bucket we just created
+- **PUBLIC URL:** Checked (this automatically creates a public download URL when files are added to the Archive)
+
+NOTE
+
+If you don’t name your Archive “Software Archive” as indicated here, you will have to make manual changes to Task config later in this guide.
+
+At this point, you should go ahead and download the installation ZIP file for SuiteCRM. You can access version 7.14.3 [here](https://github.com/salesagility/SuiteCRM/releases). This guide is designed for version 7.14.3. If you opt to download a different version please note that changes might be needed to the automation scripts to account for any changes to the installation or configuration processes for that version.
+
+Click on the newly created Archive and note there are no files contained in it. Under the Files tab, click + ADD. Slide the installation ZIP file onto the modal and wait for the file to be successfully uploaded. Click DONE. We’ve now added the installation ZIP file and it is visible in the list of files on the Files tab.
+
+Click on the name of the newly added file to access the File detail page. While here, click on the Scripts tab and you’ll see syntax examples for how this and other files might be accessed in your automation scripts. You’ll see this syntax used later in this example as we access the ZIP file directly from this Archive and automate the installation process. Generated links can be viewed from the Links tab and a record of it will be visible on the History tab.
+
+![../../_images/fileDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the MariaDB root user password as a Cypher entry. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here’s we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dba/mariadb\_root
+- **VALUE:** Password123?
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/cypherMaria.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-9196BD2B-DED5-4018-891A-19D5BCE27DA4-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** SuiteCRM DB Name (The name for the Input object in HPE Morpheus Enterprise)
+- **LABEL:** SUITECRM (Labels are a categorizing feature in HPE Morpheus Enterprise)
+- **FIELD NAME:** databaseNameSCRM (The internal property which the input value is assigned to)
+- **SHOW ON EDIT:** Checked (By checking this box, we can view this Input value when editing the Instance after provisioning)
+- **DISPLAY VALUE ON DETAILS:** Checked (By checking this box, we will see the value of this Input on the detail page for the provsioned Instance)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** SuiteCRM DB Name (The label the user will see next to the field at provsion time)
+- **REQUIRED:** Checked (By checking this box, the Input will be required at provision time)
+
+### Database Name Input
+
+![../../_images/dbNameInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C19EB913-4A34-4D5D-A85A-C0620C2BDFCF-high.png)
+
+Click SAVE CHANGES. Then, create two additional Inputs:
+
+- **NAME:** SuiteCRM DB User
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databaseUserSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Text
+- **LABEL:** SuiteCRM DB User
+- **REQUIRED:** Checked
+
+### Database Username Input
+
+![../../_images/dbUserInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CFB7E6DB-864A-4995-B1EB-A77E2D08ABA9-high.png)
+
+- **NAME:** SuiteCRM DB Password
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databasePassSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Password (Password type Inputs are masked on screen when entered by the user)
+- **LABEL:** SuiteCRM DB Password
+- **REQUIRED:** Checked
+
+### Database Password Input
+
+![../../_images/dbPassInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-35947404-36DD-48AC-A3FF-2E57EE6B68FF-high.png)
+
+## Create File Templates
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. Navigate to Library > Templates > File Templates and click + ADD. Enter the following:
+
+- **NAME:** suitecrm - conf
+- **LABELS:** SUITECRM
+- **FILE NAME:** suitecrm.conf
+- **FILE PATH:** /etc/apache2/sites-available
+- **PHASE:** Provision
+- **TEMPLATE:** See below for the complete template, note how we’re able to dynamically resolve HPE Morpheus Enterprise variables within the template
+- **FILE OWNER:** root
+- **SETTING NAME:** suitecrm
+- **SETTING CATEGORY:** App
+
+```
+```
+<VirtualHost *:80>  
+   ServerAdmin admin@localhost  
+   ServerAlias "<%=server.externalIp%>"  
+   DocumentRoot /var/www/html/suitecrm  
+   <Directory /var/www/html/suitecrm/>  
+        Options FollowSymlinks  
+        AllowOverride All  
+        Require all granted  
+   </Directory>  
+   ErrorLog ${APACHE_LOG_DIR}/error.log  
+   CustomLog ${APACHE_LOG_DIR}/access.log combined  
+   <Directory /var/www/html/suitecrm/>  
+          RewriteEngine on  
+          RewriteBase /  
+          RewriteCond %{REQUEST_FILENAME} !-f  
+          RewriteRule ^(.*) index.php [PT,L]  
+  </Directory>  
+</VirtualHost>
+```
+```
+
+![../../_images/filetemplate.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-58E7A9A8-1822-4B60-9860-CA3DFDD3870B-high.png)
+
+## Create Tasks
+
+At this point, we need to create three automation Tasks. One will set the Apache config file we just created, another will be a Bash script Task to actually install and configure SuiteCRM on the box, and the third will be another Bash script Task which will restart the Apache service.
+
+To create a Library Template Task, navigate to Library > Automation > Tasks. Click + ADD. Enter the following:
+
+- **NAME:** suitecrm file template
+- **CODE:** suitecrmfiletemplate
+- **LABELS:** SUITECRM
+- **TYPE:** Library Template (The proper fields will appear once the Type is set)
+- **TEMPLATE:** suitecrm - conf (Select the File Template we already created from this dropdown menu)
+- **EXECUTE TARGET:** Resource
+
+![../../_images/libtemtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3ADB5F3A-1E18-46BD-9DF2-4D467460BEB6-high.png)
+
+Now create the first Bash Task which will install and configure SuiteCRM on a newly-provisioned box:
+
+- **NAME:** suitecrm - single node
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **CONTENT:** Expand the section below to see the script content. Note how Cypher secrets and custom option (Input) values are invoked in this script
+- **EXECUTE TARGET:** Resource
+
+### Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/dba/mariadb_root')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+PHP_VERSION="8.1"  
+MARIADB_VERSION="mariadb-10.11"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+    sleep 120  
+fi  
+#Install apache, start service and enable on boot  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Install MariaDB, start service and enable on boot  
+curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | \  
+sudo bash -s ----mariadb-server-version="$MARIADB_VERSION"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enablemariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -e "ALTER USER 'root'@'localhost' IDENTIFIED BY '$RPass';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='root' \  
+AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass-e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.db WHERE Db='test' \  
+OR Db='test\_%';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+#Create the SuiteCRM User  
+mysql -u root -p$RPass-e "CREATE User '$SCRMUser'@'localhost' \  
+IDENTIFIED BY '$SCRMPass';"  
+#Create the SuiteCRM database  
+mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO \  
+$SCRMUser@localhost IDENTIFIED BY '$SCRMPass';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php$PHP_VERSIONlibapache2-mod-php$PHP_VERSION \  
+php$PHP_VERSION-common php$PHP_VERSION-mysql php$PHP_VERSION-gmp \  
+php$PHP_VERSION-curl php$PHP_VERSION-intl php$PHP_VERSION-mbstring \  
+php$PHP_VERSION-xmlrpc php$PHP_VERSION-gd php$PHP_VERSION-bcmath \  
+php$PHP_VERSION-imap php$PHP_VERSION-xml php$PHP_VERSION-cli \  
+php$PHP_VERSION-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+  sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" \  
+/etc/php/$PHP_VERSION/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+file_url="<%= archives.link('Software Archive', 'SuiteCRM-7.14.3.zip',1200) %>"  
+wget $file_url-O "./SuiteCRM-7.14.3.zip"--no-check-certificate  
+apt-get install unzip -y  
+unzip SuiteCRM-7.14.3.zip -d /var/www/html  
+mv /var/www/html/SuiteCRM-7.14.3/ /var/www/html/suitecrm  
+cd/var/www/html/suitecrm  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/installtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E9CE3244-8398-46FB-B6BD-70FBB18B51D8-high.png)
+
+Finally, we’ll add the Apache restart Task. Configure a new Task as shown below:
+
+- **NAME:** suitecrm apache restart
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local
+- **CONTENT:** Expand the section below to see the script content
+- **EXECUTE TARGET:** Resource
+
+### Restart Task Content
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/restarttask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B205F51E-1A3C-4DEB-8FA7-7E59213395B6-high.png)
+
+## Create the Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provisioning phase so that SuiteCRM will be installed, the Apache config file will be set, and the Apache service will be restarted automatically when the Instance is provisioned.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRM - single node
+- **LABELS:** SUITECRM
+- **PLATFORM:** Linux
+- **TASKS:** Expand the Provision section and begin typing the names of our Tasks in the Search field. After adding them, they can be reordered but they should be set such that the install script is run first, the file template is set second, and the Apache restart is run last
+
+Click SAVE CHANGES
+
+![../../_images/provworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4CD1EFEA-943C-40B9-AC3E-7431042CBD21-high.png)
+
+## Create a Custom Library Item
+
+Having created Cypher entries, Inputs, and Tasks, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. We’ll create a new SuiteCRM Library entry that will be available to some or all users (depending on Role permissions) in the provisioning wizard. This will allow them to stand up single node SuiteCRM appliances with just a few clicks. In HPE Morpheus Enterprise there are three layers to such Library items: Instance Types, Layouts, and Node Types. We’ll create the Instance Type first:
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** Custom SuiteCRM
+- **CODE:** custSuiteCRM
+- **CATEGORY:** Apps
+- **LABELS:** SUITECRM
+- **ICON:** If desired, search the file system on your local computer for a SuiteCRM logo icon for easier identification of this Instance Type at provision time
+
+![../../_images/instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0E99A5BF-3532-4F17-94B0-F80D1F98A54F-high.png)
+
+Click SAVE CHANGES. After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** SuiteCRM - Single Node
+- **VERSION:** 7.14.3
+- **LABELS:** SUITECRM
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **MINIMUM MEMORY:** 2048 (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **WORKFLOW:** Select the Workflow we’ve already created, “SuiteCRM - single node”
+- **INPUTS:** Search and find the three custom Inputs we created earlier
+
+![../../_images/layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-87B329F6-4D66-4D7C-8D9B-65796365436F-high.png)
+
+Once the configurations are entered, click SAVE CHANGES. After creating the Layout, we need to associate a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. Node Types are compute images and will be relevant types for the destination Cloud technology (AMIs for provisioning on AWS or VMware virtual images for vCenter Clouds, etc.) In this case, we’re simply going to point to a default Ubuntu image in an appropriate format which is supplied by HPE Morpheus Enterprise. You can associate Node Types with your own custom virtual images as well when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** Custom Ubuntu 22.04 Node
+- **SHORT NAME:** ubuntu2204
+- **VERSION:** 22.04
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **VM IMAGE:** Select the included Ubuntu 18.04 image
+
+Click SAVE CHANGES
+
+![../../_images/nodetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-851F39FE-55AA-4EE3-85A8-94FD5E6ADA2C-high.png)
+
+## Provision the SuiteCRM Instance Type
+
+At this point, the setup is finished and SuiteCRM will be available as an Instance Type option for your users. We’ll go ahead and walk through the provisioning process at this point just to take a look.
+
+To begin provisioning, navigate to Provisioning > Instances and click + ADD. From the list of Instance Types, select the “SUITE\_CRM” Instance Type we just created, click NEXT. From the Group tab, select a Group which contains a destination Cloud relevant to the Instance configuration and then select the Cloud you’d like to provision the app onto. Click NEXT. From the Configuration Tab, select the Layout we created and configure a plan, Resource Pool, and network which makes sense for your environment and the compute needs of the workload. You’ll then notice the Input fields we created where you’ll need to enter a SuiteCRM database name, Username, and Password. Click NEXT. On the Automation tab, we do not need to select a Workflow as our Workflow is already set on the Layout. Click NEXT and click COMPLETE.
+
+![../../_images/provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-43E0CE55-E46C-408F-AA4F-F0320E933520-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_INSTANCE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json b/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
new file mode 100644
index 0000000..5238a91
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+  "title": "Capacity and Planning",
+  "ordinal": 13,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity and Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md b/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
new file mode 100644
index 0000000..78c9ce3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
@@ -0,0 +1,33 @@
+# Capacity and Planning
+
+There are many different architectures HPE Morpheus Enterprise can be deployed as. However, the most common architectures are an All-In-One (AIO) single node and a 3-Node Highly Available (HA) cluster. These architectures can have many variables to determine the capacity of each node, as each users’ environment will be different. Example factors that determine the capacity are:
+
+- Number of virtual machines (VMs)/systems/instances that HPE Morpheus Enterprise will manage, also know as Workload Elements (WLEs)
+- If the WLEs will have agents installed
+- The number of clouds added to HPE Morpheus Enterprise
+- The technologies used, such as: Kubernetes, Terraform, ARM, etc.
+- The number of concurrent worflows
+- Number of active users
+
+Although there are many factors that can contribute to the capacity planning, even outside the list above, below are recommended initial specifications.
+
+Table 1. Recommendations
+
+        | Architecture | # of CPUs per node | Memory (GB) per node | Local Storage (GB) per node | Shared Storage (NFS) | Supported WLEs |
+| --- | --- | --- | --- | --- | --- |
+| AIO | 4 | 16 | 200 | N/A | 5,000 |
+| AIO | 4 | 32 | 400 | N/A | 10,000 |
+| 3‐Node HA | 4 | 16 | 400 | 50 | 10,000 |
+| 3‐Node HA | 8 | 32 | 400 | 50 | 20,000 |
+
+In the above recommendations, an AIO can support ~5,000 WLEs with agents installed at the base requirements. Due to ease of installation and maintenance, an AIO architecture should be strongly considered for environments that will manage less than a few thousand WLEs. Consider the significantly increased complexity of multi-node architectures and opt for an AIO appliance unless there is a specific compelling reason (such as high capacity needs or a zero downtime requirement) to select anything else. However, the AIO architecture cannot tolerate failure and will be unavailable during upgrades, unlike the 3-Node HA, which is the likely choice for ensuring zero downtime upgrades and high availability. A 3-Node HA architecture could support ~15,000 WLEs with agents installed (3 x 5,000) at the base requirements but it is best to consider the possible loss of a node, which would be an effective support of ~10,000 WLEs with agents installed (2 x 5,000).
+
+In the case of both the AIO and 3-Node HA architectures, HPE Morpheus Enterprise nodes can be **scaled up** to a maximum of 32GB of memory, which can support more WLEs per node. Adding more CPU or memory is possible, without adding additional nodes. Also, in the case of the 3-Node HA architecture, HPE Morpheus Enterprise can be **scaled out**, which can support additional WLEs per node added and provides additional redundancy, whereas the AIO configuration cannot add additional nodes. The 3-Node HA architecture should always have an odd number of nodes for quorum.
+
+IMPORTANT
+
+Customer architectures and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment, which can help right-size the environment
+
+Additional information around the various architectures can be found here:
+
+[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html) [HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json b/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
new file mode 100644
index 0000000..f908dd9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+  "title": "Azure Active Directory SSO (SAML)",
+  "ordinal": 282,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Active Directory SSO (SAML)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md b/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
new file mode 100644
index 0000000..57829e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
@@ -0,0 +1,204 @@
+# Azure Active Directory SSO (SAML)
+
+Azure Active Directory Single Sign-on can be added as a Identity Source in HPE Morpheus Enterprise using the SAML Identity Source Type. The Azure AD SSO configuration is slightly different than other SAML providers, and this guide will assist in adding a Azure AD SSO Identity Source.
+
+## Create Azure Enterprise Application
+
+### Procedure
+
+1. Login to the [Azure Portal](https://portal.azure.com)
+2. Navigate to: Azure Active Directory  >  Enterprise Applications
+3. Click the `+ New application` button at the top
+4. Click the `+ Create your own application` button at the top
+5. Ensure `Integrate any other application you don't find in the gallery (Non-gallery)` is selected and enter a name for the app. Common examples are: `MorpheusSSO`
+6. Click the `Create` button at the bottom and wait for it to complete
+7. Once created, you’ll be in the `Overview` of the application created. Navigate to the `Single sign-on` section from the left pane
+8. Choose `SAML` as the Single sign-on method
+9. Copy both the `Login URL` and `Logout URL` in Step 4, we’ll need these in some of the next steps
+10. Before we can continue configuring the application, the configuration needs to be generated in HPE Morpheus Enterprise for more data
+
+## Create an Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### About this task
+
+Azure requires inputting the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` in the Azure SSO configuration before it provides the Endpoints and Certificate necessary to add the Integration into HPE Morpheus Enterprise. In order to get the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` to input into Azure SSO configuration, we need to create a `Azure AD SAML SSO` integration in HPE Morpheus Enterprise first.
+
+To add the integration:
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Click the IDENTITY SOURCES button in the Tenant detail page
+5. Click the + ADD IDENTITY SOURCE button
+6. Select `Azure AD SAML SSO` from the `TYPE` dropdown
+7. Add 
+
+   - Name
+   - (Optional) Description
+   - Paste the `Login URL` copied from Azure into the `LOGIN REDIRECT URL` field
+   - Paste the `Logout URL` copied from Azure into the `SAML LOGOUT REDIRECT URL` field
+8. This is the minimum information needed for now, which will let us generate the details needed from HPE Morpheus Enterprise. We’ll return to this configuration page later to enter more information.
+9. Click the SAVE CHANGES button 
+
+   IMPORTANT
+
+   Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+   Upon saving, the Entity ID (`Identifier (Entity ID)`) and SP ACS URL (`Reply URL (Assertion Consumer Service URL)`) will be provide in the Identity Source list view. Copy these for use in Azure SSO configuration.
+
+   ![../../_images/saml_setup.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C3ECE586-166D-49EB-85B2-42D73E125E79-high.png)
+
+## Configure Azure Enterprise Application
+
+### About this task
+
+This guide assumes an Azure AD Enterprise Application has already been created. Please refer to documentation above, if this has not already been configured.
+
+### Procedure
+
+1. Navigate to: Azure Active Directory  >  Enterprise Applications  >  Single sign-on
+2. Choose `SAML` as the Single sign-on method
+3. On Step 1 (`Basic SAML Configuration`), click the `Edit` button and enter the following: 
+
+   - Identifier (Entity ID)
+     :   Enter the `Entity ID` URL from the HPE Morpheus Enterprise Identity Source Integration above
+   - Reply URL (Assertion Consumer Service URL)
+     :   Enter the `SP ACS URL` from the HPE Morpheus Enterprise Identity Source Integration above
+   - Logout URL
+     :   Enter the following format: `https://yourUrl/login/` If this is a sub tenant, the format may instead be the following: `https://yourUrl/login/account/1` The login URL can be found under IDENTITY SOURCES in the tenant
+4. On Step 2 (`Attributes and Claims`), click the `Edit` button
+5. Click the `Add a group claim` button at the top
+6. Choose `All groups` and ensure `Group ID` is selected for the `Source attribute` dropdown 
+
+   NOTE
+
+   You can also choose `Security groups`, which ever makes more sense for the organization
+7. Close the pane and return to the Enterprise Application in the `Single sign-on` section
+8. On Step 3 (`SAML Certificates`), click the `Download` link next to `Certificate (Base64)` and `Federation Metadata XML` 
+
+   NOTE
+
+   The files will download, keep them available for later configuation in HPE Morpheus Enterprise
+9. Navigate to `Users and Groups` in the left pane
+10. Click the `Add user/group` button
+11. Add Azure groups to this application that will be able to login to HPE Morpheus Enterprise 
+
+    NOTE
+
+    the object ID for each of these groups, as they will be used later when configuring HPE Morpheus Enterprise to map the group to roles
+12. Once groups have been added, click the `Assign` button at the bottom
+
+## Configure the Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise using `Username and Password`, as usual
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Select IDENTITY SOURCES in the Tenant detail page
+5. Click the pencil (edit) next to the integration created previously
+6. Ensure the `SAML REQUEST` field is set to `Self Signed` 
+
+   NOTE
+
+   A custom RSA signature can be used here if needed, if required by the orgnaization
+7. Ensure the `SAML RESPONSE` field is set to `Validate Assertion Signature` 
+
+   NOTE
+
+   With this setting, if the assertion signature ever changes in the Azure Enterprise Application, this would need to be updated to match
+8. Edit/view the downloaded `Federation Metadata XML` (`.xml` extension) file from the previous section 
+
+   NOTE
+
+   It is recommended to use `Microsoft Edge`, or another browser, to view the contents
+9. In the `Federation Metadata XML` file, locate the `<X509Certificate> </X509Certificate>` under the `<Signature>` section. Copy the entire contents between the `<X509Certificate>` and `</X509Certificate>`, it is very long
+10. Paste the value copied from the `Federation Metadata XML` file into the `Public Key (Optional)` box, below the `SAML RESPONSE` dropdown
+
+## Configure Role Mappings
+
+### About this task
+
+Role mappings will map Azure AD Groups to Morpheus Roles. Azure AD users will be assigned Roles in HPE Morpheus Enterprise upon signing in based on their Group Membership in Azure AD.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+DEFAULT ROLE
+:   Role a Azure AD user will be assigned by default upon signing in to HPE Morpheus Enterprise using this Identity Source.
+
+REQUIRED AZURE AD GROUP OBJECT ID
+:   Object ID of Azure AD Group a user must be a member of to be authorized to sign in to HPE Morpheus Enterprise. Users not belonging to this Group will not be authorized to login to HPE Morpheus Enterprise. This field is optional, and if left blank, any user from the Azure AD App will be able to sign in to HPE Morpheus Enterprise and will be assigned the Default Role if no Role Mappings match AD Group membership.
+
+GROUP ASSERTION ATTRIBUTE NAME
+:   Enter `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` for Azure AD SSO
+
+Additional Role Mappings
+:   The existing Roles in HPE Morpheus Enterprise will be listed. To map a HPE Morpheus Enterprise Role to an Azure AD Group, enter the Object ID of the desired Azure AD Group in the Role Attribute Value field for the corresponding HPE Morpheus Enterprise Role.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added. The Identity Source can be edited anytime to deactivate or change Role Mappings or other values.
+
+NOTE
+
+If Role mappings are edited after Azure AD SSO users have signed into HPE Morpheus Enterprise, currently logged in users will need to log out of HPE Morpheus Enterprise for the new Role mappings to take effect, when applicable.
+
+### Procedure
+
+1. Under the `Role Azure Group Mappings` secton, verify the `DEFAULT ROLE` dropdown has the role in HPE Morpheus Enterprise selected that all users will be assigned by default 
+
+   - It is recommended that this role contains no permissions, which ensures that anyone who authenticates gets no access
+2. Under the `Role Azure Group Mappings` secton, you will see role names listed. Next to these are text boxes with `Assertion Attribute Mappings` inside. Enter group object IDs from Azure into these text boxes. This will map the Azure AD groups to specific roles in Morpheus
+3. Finally, click `Save Changes` at the bottom of the page 
+
+   Here is an example of the configuration above:
+
+   ![../../_images/saml_setup_complete.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5666456C-8FE1-4305-816E-FD051CC4636F-high.png)
+
+## Azure Group Lookups
+
+When a user in azure ad has more that 150 group attributes, Azure does not include the group claims in the SAML response, and HPE Morpheus Enterprise is required to query Microsoft Graph to obtain the users group attribute values. When there are users that are members of more that 150 groups, populate the `Azure Group Lookups` section in order for those users to be able to use the Azure AD SAML SSO integration, otherwise no groups will be obtained and proper role mappings cannot occur.
+
+AZURE TENANT ID
+:   Add Azure AD Tenant ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Tenant ID
+
+AZURE APP ID
+:   Add Azure AD Application (Client) ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Application (Client) ID
+
+AZURE APP SECRET
+:   Add Azure Application (Client) Secret if user group membership will exceed 150. See [Generate a Client Secret](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-0A7984C3-E094-45D6-B2D9-ED3179A79988) for information on creating an Azure Application (Client) Secret
+
+ROLE LINK ATTRIBUTE NAME
+:   default: <http://schemas.microsoft.com/claims/groups.link>. This is not normally changed.
+
+## Logging Into HPE Morpheus Enterprise with Azure AD SAML
+
+### Procedure
+
+1. Navigate to the HPE Morpheus Enterprise URL
+2. A new button will appear to allow sign-in using Azure AD SAML, with the same name as the integration. Click the button 
+
+   ![../../_images/sign_in_page.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1FEC124E-FF68-4E72-9872-1D336777E8E5-high.png)
+3. Sign-in with your Microsoft/Azure account 
+
+   ![../../_images/ms_signin.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF8B57F9-055B-4A8C-AEB5-95ABA09BD3DF-high.png)
+
+   NOTE
+
+   If no local users other than the System Admin have been created, “USERNAME AND PASSWORD” option will not be displayed, only the SAML option.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json b/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
new file mode 100644
index 0000000..75005e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+  "title": "Adding Functionality Through Operational Workflows",
+  "ordinal": 365,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Functionality Through Operational Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md b/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
new file mode 100644
index 0000000..36c6242
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
@@ -0,0 +1,113 @@
+# Adding Functionality Through Operational Workflows
+
+Operational Workflows, in HPE Morpheus Enterprise, are logically arranged sets of individual automation Tasks designed to accomplish some function. They can be executed on a one-off basis as needed or set on a timed execution schedule, similar to a cron job. While they’re often used to orchestrate some facet of cloud resource management, they can also be used to speed and standardize creation of HPE Morpheus Enterprise constructs.
+
+As an example case for this guide, we’ll create an Operational Workflow which will allow Primary Tenant administrators to create Groups within Subtenants. This is not natively-available functionality as Groups are not a tenanted construct in HPE Morpheus Enterprise. They exist solely within the Tenant that created them and cannot be shared or viewed by others.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Groups
+- Cypher
+- Tasks
+- Workflows
+- Inputs
+- HPE Morpheus Enterprise API
+
+## Initial Considerations
+
+Since we’re creating Groups in a second Tenant, you’ll need to have at least one other Tenant in your appliance (Administration > Tenants). You’ll also need access to a user account within the Subtenant which has rights to create Groups. You could use a pre-existing user account or create a service user for automated processes like this one.
+
+Impersonate or log in with your service account and create an API Key. API Keys are created by clicking on the user’s name in the upper-right corner of the application window, then clicking User Settings. On the User Settings page, click API ACCESS. Next to one of the entries (it doesn’t matter which one but be careful about overwriting a key that is already in use), click ACTIONS and then Generate. Copy the Access Token into a secure place you can retrieve it from in the next step. You will not be able to see this key again after closing the modal containing the API Keys. Return to your primary HPE Morpheus Enterprise account in the original Tenant to continue with the guide.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the API Key for our service account user so we can call it into automation scripts in a later step. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/subusertoken
+- **VALUE:** Enter HPE Morpheus Enterprise API Key for the Subtenant user
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/createcypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EF5395A9-F584-4E5D-B77C-11ED02BF2822-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, Workflows, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. In this case, the Inputs will be associated with our Operational Workflow. We will create three so the user can define a name for the new Group and optionally provide a code and/or location value if desired.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** Subtenant Group Name (The friendly name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** subgroupname (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** Subtenant Group Name (The label the user sees next to the input field)
+- **REQUIRED:** Checked (A name value is required for our Group so this Input should be marked required. The other two Inputs we’ll create will not be required as they are optional fields when creating a Group)
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createinput.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1081A234-C0CA-4B22-82F1-EE91843663DD-high.png)
+
+Create two more Inputs in a similar fashion with the following configuration:
+
+### Code Input
+
+- **NAME:** Subtenant Group Code
+- **FIELD NAME:** subgroupcode
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Code
+- **HELP BLOCK:** Optional Code Value (I opted to enter help block text to make it clearer to the user that this is an optional input)
+- **REQUIRED:** Unchecked
+
+### Location Input
+
+- **NAME:** Subtenant Group Location
+- **FIELD NAME:** subgrouplocation
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Location
+- **HELP BLOCK:** Optional Location Value
+- **REQUIRED:** Unchecked
+
+## Create Task
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ve written a Python script outside HPE Morpheus Enterprise and tracked it in a Github repository. Since my Github account is integrated with HPE Morpheus Enterprise, I can simply refer to the script in a new Task. This prevents me from having to cut and paste code and also ensures the latest version of my code in executed every time the Task is invoked. Integrating with version control is optional, for simplicity you can also draft a quick script directly in HPE Morpheus Enterprise if you’d prefer. If you want to view, copy, or fork the code, you can see it [here](https://github.com/ahark86/morpheus-group-create/blob/master/main.py). New Github integrations can be added in Administration > Integrations.
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Subtenant Group Create - Task
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Repository (Select Local to draft or paste code directly into HPE Morpheus Enterprise)
+- **FILE PATH:** main.py (In my case, the script is in the root of the repository so I can simply refer to it by filename)
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the HPE Morpheus Enterprise API Key from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US).
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5C031817-0262-4BF2-919F-0B9677FB0559-high.png)
+
+## Create Operational Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. Provisioning Workflows (which aren’t used in this guide) are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need an Operational Workflow which are run on-demand when needed or on timed intervals.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** Subtenant Group Create
+- **PLATFORM:** All
+- **TASKS:** Subtenant Group Create - Task
+- **INPUTS:** Find Subtenant Group Name, Subtenant Group Code, and Subtenant Group Location using the typeahead field. I think it makes most sense to order them with Name first but it’s not required
+
+Once done, click SAVE CHANGES
+
+![../../_images/createworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-680497EC-0916-4C46-9821-E3DC1A379126-high.png)
+
+## Execute Workflow
+
+After saving the new Operational Workflow, you’ll be left on the Workflows list page. From here we can try the new Workflow. Click on the gear icon at the far-right part of the row, then click Execute. Our three Inputs should be visible. We can see the Name field is marked as required (as we configured) and our help block text underneath the optional Inputs. Complete each field (Context Type can be left at None) and click EXECUTE.
+
+![../../_images/executeworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E459787E-142E-4A07-819A-E280C1C9021C-high.png)
+
+Once again login in as or impersonate your service account user within the Subtenant. Navigate to Infrastructure > Groups and inspect the list. You should now see that our Group has been created here.
+
+![../../_images/grouplist.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1D03AA1C-1895-4C61-86EB-10C99456022D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json b/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
new file mode 100644
index 0000000..bb3371a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+  "title": "CLI Troubleshooting",
+  "ordinal": 347,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html",
+  "topic_cluster": {
+    "clustering_title": "CLI Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md b/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
new file mode 100644
index 0000000..9749045
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
@@ -0,0 +1,11 @@
+# CLI Troubleshooting
+
+If you have installed the HPE Morpheus Enterprise CLI successfully and get a successful login but see this error `Error Communicating with the Appliance. SSL_connect returned=1 errno=0 state=error: certificate verify failed`
+
+run the command
+
+```
+```
+morpheus remote update {appliancename} --insecure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..e6d441b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 104,
+  "parent_title": "Automation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..8801104
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,10 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html)**
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html)**
+- **[Task Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json b/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
new file mode 100644
index 0000000..d776ca6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+  "title": "Users & User Groups",
+  "ordinal": 307,
+  "parent_title": "Administration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html",
+  "topic_cluster": {
+    "clustering_title": "Users & User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md b/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
new file mode 100644
index 0000000..f407dcc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
@@ -0,0 +1,6 @@
+# Users & User Groups
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json b/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
new file mode 100644
index 0000000..f71a701
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+  "title": "Creating Instances",
+  "ordinal": 84,
+  "parent_title": "Instances",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md b/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
new file mode 100644
index 0000000..1b51298
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
@@ -0,0 +1,41 @@
+# Creating Instances
+
+The Instance catalog is the one-stop shop for selecting items to be provisioned and pieced together. It contains not only basic container and VM options but also tailored services for SQL databases, NoSQL databases, cache stores, message busses, web servers, and even full-fledged apps. The list contains a lot of items to choose from and they are represented to the user based on what provisioning engines are enabled and integrated in the HPE Morpheus Enterprise environment.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances section. A modal will display allowing the catalog to be searched. Once an item is selected it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) thereby restricting access to non-sanctioned catalog items, as well as added to via the Library section. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple cloud integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. If the environment is new and these do not yet exist, it may be advisable to refer to one of our starter guides, such as the guide on getting started with HPE Morpheus Enterprise and [VMware](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html). The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is mostly useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. Datastore for VMware or Network). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such.
+
+Configuration options provided in this screen are very powerful. An example is MySQL where a Master/Slave or Master/Master layout can be selected. These configurations will automatically deploy two MySQL VMs or containers and link them together to provide replication. These types of configurations exist for a wide range of Instance types and are optimized for high performance and scale. It is even possible to provision entire sharded MongoDB clusters.
+
+One last step before the Instance can be provisioned is the Automation step. This wizard step may or may not appear depending on the capabilities of the Instance type or previous configurations in the account. It is here one can easily select a post-provisioning workflow to run (see more on Tasks and Workflows elsewhere in HPE Morpheus Enterprise documentation), assign a load balancer, or even configure the backup job that gets created.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes (typically a container configuration will be rather quick if the Instance type has previously been provisioned before).
+
+## Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for HPE Morpheus Enterprise to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with HPE Morpheus Enterprise, EC2 instances pre-existing on an Amazon AWS account, or virtual machines that are running on a KVM host. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for HPE Morpheus Enterprise to automatically onboard these resources. Not only will HPE Morpheus Enterprise inventory these instances at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, HPE Morpheus Enterprise allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Assign to the primary Tenant or one of the Subtenants
+- Select a Group (this dropdown contains a filtered list of Groups which the associated Cloud is in)
+- Username and password for a seeded account
+- Opt to install HPE Morpheus Enterprise Agent or not (for more on HPE Morpheus Enterprise Agent, click [here](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/morpheus_agent.html))
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Select a version number for the Instance (such as 20.04 for a basic Ubuntu Instance)
+- Select a Layout, Instance Types often have multiple Layout configurations
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by adding it to an App or expanding the Instance horizontally with added nodes.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json b/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
new file mode 100644
index 0000000..57e5d5e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+  "title": "Installing iSUT on Deployed Instances (Optional)",
+  "ordinal": 424,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html",
+  "topic_cluster": {
+    "clustering_title": "Installing iSUT on Deployed Instances (Optional)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md b/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
new file mode 100644
index 0000000..d84cff8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
@@ -0,0 +1,25 @@
+# Installing iSUT on Deployed Instances (Optional)
+
+## About this task
+
+To enable driver inventory and updates within the operating system, iSUT and AMS must be installed on each deployed instance.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the target instance.
+
+   NOTE
+
+   Since the workflow requires iLO credentials, only one instance can be selected at a time. Multiple instances cannot be targeted for a single iSUT/AMS install.
+3. Click Actions > Run Workflow.
+4. Select the appropriate workflow:
+   1. Download and Install iSUT and AMS (Linux), or
+   2. Download and Install iSUT and AMS (Windows)
+5. Enter the **iLO credentials** for the targeted bare metal server.
+
+   NOTE
+
+   These are iLO credentials, not OS credentials.
+6. Click Execute.
+7. Monitor progress from the History tab until the workflow completes.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json b/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
new file mode 100644
index 0000000..ec47b02
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+  "title": "Alert Rules",
+  "ordinal": 261,
+  "parent_title": "Overview",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html",
+  "topic_cluster": {
+    "clustering_title": "Alert Rules",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md b/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
new file mode 100644
index 0000000..9ed07e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
@@ -0,0 +1,12 @@
+# Alert Rules
+
+Alert Rules provide a powerful means to configure who gets notified in various scenarios. These scenarios include targeting specific checks, groups, or apps, and adding the appropriate recipients to be notified during a situation in which those filters are impacted.
+
+- **Min Duration:** This setting delays notification to the recipients by the entered number of minutes required for the incident to be opened.
+- **Min Severity:** Some executives might want to be notified of an outage but only if the severity impact goes above a certain level. This is very useful for scoping escalations.
+
+To add recipients to a rule just start typing their name in the Recipients section towards the button of the edit form. An auto-complete list will start populating with contact names. Once one is selected a delivery method can be selected as well as whether or not they should be notified of any escalation changes and/or closed incidents. The delivery methods available depend on the type of contact information configured for your contact. If needed, contacts can be created or edited in Monitoring  >  Contacts.
+
+TIP
+
+A recipient can be in multiple alert rules and can even be configured to be notified via different methods depending on the rule. A useful example might be to alert someone via email for lower severity incidents but SMS for critical severity levels.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json b/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
new file mode 100644
index 0000000..3d7a25b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+  "title": "Add SSL Certificate",
+  "ordinal": 242,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html",
+  "topic_cluster": {
+    "clustering_title": "Add SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md b/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
new file mode 100644
index 0000000..ae1cf17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
@@ -0,0 +1,13 @@
+# Add SSL Certificate
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, click + ADD
+3. From the Add SSL Certificate wizard input the following as needed: 
+
+   - Name
+   - Domain Name
+   - Key File
+   - Cert File
+   - Root Cert
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json b/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
new file mode 100644
index 0000000..eeb95ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+  "title": "Data Stores",
+  "ordinal": 233,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md b/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
new file mode 100644
index 0000000..d70694d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
@@ -0,0 +1,30 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, HPE Morpheus Enterprise will onboard all existing data stores and administrators can then make them available to Groups or Tenants as needed. At provision time, when applicable based on Cloud and Layout, users can select the data store they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
+
+## Create Data Stores
+
+To a limited extent, data stores can be created from this view. Currently, data store creation is restricted to VMware data store creation on 3Par volumes. In order to create such a data store you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and HPE Morpheus Enterprise will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
+
+## Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store, and which Tenants have access. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Tenants:** Primary Tenant users can opt to make the data store available to all Tenants (public visibility) or to selected Tenants (private visibility with specific Tenants selected). Subtenant users will only be able to make data stores visible to their own Tenant
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..0510a11
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 270,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..eecee10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json b/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
new file mode 100644
index 0000000..2ce975b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+  "title": "ServiceNow Monitoring Integration",
+  "ordinal": 504,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.html",
+  "topic_cluster": {
+    "clustering_title": "ServiceNow Monitoring Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md b/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
new file mode 100644
index 0000000..8498001
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
@@ -0,0 +1,28 @@
+# ServiceNow Monitoring Integration
+
+NOTE
+
+A ServiceNow Integration must be already configured in Administration > Integrations to enable the ServiceNow Monitoring Integration. Refer to the [ServiceNow](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html) configuration guide for more information.
+
+Enabled
+:   Enables the ServiceNow Monitoring Integration
+
+Integration
+:   Select from a ServiceNow Integration added in Administration > Integrations
+
+New Incident Action
+:   The Service Now action to take when a Morpheus incident is created.
+
+Close Incident Action
+:   The Service Now action to take when a Morpheus incident is closed.
+
+Incident Severity Mapping
+
+Table 1.
+
+    |  |  |
+| --- | --- |
+| HPE Morpheus Enterprise Severity | ServiceNow Impact |
+| Info | Low/Medium/High |
+| Warning | Low/Medium/High |
+| Critical | Low/Medium/High |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json b/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
new file mode 100644
index 0000000..d78295e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+  "title": "Provisioning",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md b/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
new file mode 100644
index 0000000..278b76b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
@@ -0,0 +1,14 @@
+# Provisioning
+
+There are several capabilities in the HPE Morpheus Enterprise provisioning engine. Things ranging from application / service deployments via containers, virtual machines, and even bare metal. Deployment management and app template construction are also core aspects of the provisioning engine. Take advantage of custom tasks and workflows within any environment by building tasks and workflows from those tasks. There is a lot of information to cover with regards to provisioning but HPE Morpheus Enterprise makes it intuitive and smooth.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html)**
+- **[Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html)**
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html)**
+- **[Executions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html)**
+- **[Code](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json b/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
new file mode 100644
index 0000000..d910a2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+  "title": "Viewing the Self Service Catalog",
+  "ordinal": 139,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md b/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
new file mode 100644
index 0000000..d523963
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
@@ -0,0 +1,5 @@
+# Viewing the Self Service Catalog
+
+The complete Self Service catalog can be viewed by clicking on Catalog from the Provisioning menu. The complete list of items available for the Self Service catalog are shown here but users working in the Service Catalog Persona will see only those allowed based on their user role. In addition to the name and type of each catalog item, we can also see a description and whether not the catalog item is featured or active. Featured items are given special visibility in the Service Catalog Persona and inactive items will not appear as provisioning options.
+
+![../../_images/catalogList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E3A8EE0B-A475-4D68-B6C5-626CB50D9772-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json b/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
new file mode 100644
index 0000000..317ab72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+  "title": "Creating Resource Pools",
+  "ordinal": 403,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Resource Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md b/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
new file mode 100644
index 0000000..46c8267
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
@@ -0,0 +1,13 @@
+# Creating Resource Pools
+
+## About this task
+
+This section describes how to create a resource pool within your HPE ProLiant Bare Metal Cloud in Morpheus. Resource pools help you organize and allocate servers for provisioning and management.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds. Select the cloud and click the Resources tab.
+2. Click the + Add Resource Pool.
+3. Enter a name and complete any additional required details for the resource pool and then click Next.   
+   ![New Resource Pool](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0192576F-1954-421D-8C37-5CF3A41C0C7D-high.png)
+4. Click Save Changes to finalize resource pool creation.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json b/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
new file mode 100644
index 0000000..1fcc6a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+  "title": "Price Phase Task Utilization",
+  "ordinal": 118,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html",
+  "topic_cluster": {
+    "clustering_title": "Price Phase Task Utilization",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md b/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
new file mode 100644
index 0000000..9e3c367
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
@@ -0,0 +1,52 @@
+# Price Phase Task Utilization
+
+Price Phase Tasks Video Demo
+
+Price Phase Tasks allow computed pricing for any workload in any Cloud (even public Clouds) to be overridden based on custom logic designed by the user. The variable “spec” is fed into the Task which represents the Instance configuration. The Task can be designed to use the Instance config data and compute an appropriate price for the Instance. HPE Morpheus Enterprise expects a return payload in the format below for the price override to work correctly. If used, pricing computed via Task replaces any other costing data which would have been applied to the workload (such as pricing based on the Service Plan). The user will see price estimates based on the Price Phase Task in the Instance provisioning wizard where the Service Plan pricing would otherwise be shown. Additionally, since Workflows which invoke Price Phase Tasks are tied to the Layout, the user can see different pricing depending on which Instance Type Layout is selected.
+
+NOTE
+
+Price Phase Tasks are only invoked if the Workflow is tied to a Layout.
+
+The return payload should be a JSON array of “priceData” objects. priceData objects should contain values for each of the keys in the table below:
+
+| Key | Description | Data Type | Possible Values |
+| --- | --- | --- | --- |
+| incurCharges | Indicates the Instance state when this charge should be applied | String | **Running:** Charge is incurred while the workload is in a running state, **Stopped:** Charge is incurred while the workload is in a stopped or shutdown state, **Always:** This charge is always applied. Some charges may apply simultaneously, for example, “Always” and “Running” states will apply while the workload is running. |
+| currency | Indicates the currency in which the charge will be applied | String | Enter any three‐letter currency code which HPE Morpheus Enterprise supports for its pricing, such as “USD”, “CAD”, or “GBP” |
+| unit | Indicates the time interval at which the charge is applied | String | Enter “minute”, “hour”, “day”, “month”, or “year” |
+| cost | Indicates the amount applied as cost for each configured time unit interval that passes. This is the cost to you, not the price with markup which the customer would see. | Number | A numerical amount such as “3.00” or “34.23” |
+| price | Indicates the amount applied as price for each configured time unit interval that passes. This is the price to the customer with any built‐in markup you need to apply. | Number | A numerical amount such as “3.00” or “34.23” |
+
+A number of different Task types could be used in this phase. As long as the Task is returning the required JSON array, the Task will work correctly. Below is an example using a Groovy Task. This is simply outputting a static payload though in a real world scenario you’d likely use Task logic to output a dynamic array based on the Instance configuration.
+
+```
+```
+def rtn = [  
+  priceData: [  
+    [  
+      incurCharges: 'always',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 2.0,  
+      price: 2.0  
+    ],  
+    [  
+      incurCharges: 'running',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 3.0,  
+      price: 3.0  
+    ],  
+    [  
+      incurCharges: 'stopped',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 1.0,  
+      price: 1.0  
+    ]  
+  ]  
+]  
+return rtn
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..220fd79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 517,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..a6fa0b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,9 @@
+# Storage
+
+**Subtopics**  
+
+- **[3Par](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html)**
+- **[AzureStorage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html)**
+- **[Dell ECS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html)**
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
+- **[Isilon](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json b/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
new file mode 100644
index 0000000..5804ac5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+  "title": "Creating and Running Security Scan Jobs",
+  "ordinal": 93,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running Security Scan Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md b/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
new file mode 100644
index 0000000..007c250
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
@@ -0,0 +1,86 @@
+# Creating and Running Security Scan Jobs
+
+Security Scan Jobs allow users to create and schedule SCAP program (Security Content Automation Program) scans for groups of managed systems. These Jobs can call in existing SCAP packages and checklists, which are used to scan the targeted systems on-demand or on a scheduled basis. Historical data for these scans is saved in the Job Execution list and in the software section of server detail pages. Detailed scan reports can also be viewed for each system as needed once the scan is complete. See the [SCAP documentation](https://csrc.nist.gov/CSRC/media/Projects/Security-Content-Automation-Protocol/documents/docs/scap-nistir-7343.pdf) on the NIST website for information on developing your own scanning procedures.
+
+NOTE
+
+Creating and editing Security Scan Jobs requires the “Security: Scanning” Role permission set to Full. Viewing Security Scan Jobs and seeing the results for scanned servers requires at least a Read-level permission.
+
+## Add a new Security Scan Job
+
+### About this task
+
+NOTE
+
+New security scan packages are added in HPE Morpheus Enterprise Library rather than here in the Jobs section. Ensure you have uploaded the desired security package in Library > Templates > Security Packages before proceeding with new security Job creation.
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click +ADD
+3. Set the Job type to “Security Scan Job” and provide a friendly name for the Job
+4. Click NEXT 
+
+   ![../../_images/2new_job.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E8A3A8C8-27F1-48F1-8B98-2AF3AAE6E121-high.png)
+5. Select a security package, see the previous section to add a new one
+6. Enter your Scan Checklist (XML document) and Security Profile (XCCDF document), more information on these can be found in the SCAP documentation linked above
+7. Set a schedule or leave as Manual to only run this scan on-demand (new execution schedules can be created in Library > Automationif needed)
+8. Set a specific power state target if desired. This indicates whether the Job should run against workloads having any power state, just an “on” power state, or just an “off” power state
+9. Set the context, can be Instance or Server. Select as many Instances or Servers as needed for this scanning run
+10. Click NEXT
+11. After final review, click COMPLETE 
+
+    ![../../_images/3job_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-77399E18-27B9-465D-885C-F34C86B2EA19-high.png)
+
+## Running Security Scan Jobs
+
+### About this task
+
+Once created, Security Scan Jobs will run based on the configured schedule. They can also be run on-demand when needed:
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click MORE
+3. Click “Execute” 
+
+   ![../../_images/4execute_scan.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-ECB853BF-5ACC-4D03-BCC3-AF5A1D2706A3-high.png)
+
+## Viewing Completed Security Scan Jobs
+
+### About this task
+
+To view a list of completed Security Scan Jobs (and Jobs of other types):
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Job Executions Tab
+2. Additional details can be viewed by clicking (i) 
+
+   ![../../_images/5execution_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-486B12EC-23D0-4977-9075-9BAE63439855-high.png)
+
+### Results
+
+To view scan results for specific servers:
+
+1. Navigate to the server detail page (Infrastructure > Hosts > Virtual Machines tab > Selectedserver)
+2. Click on the Software tab part way down the page, then click on the Security subtab
+3. High level details on previous scans is viewable here
+
+   ![../../_images/6server_results.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FEF15F44-AFFC-4639-B948-E5077F44A1AA-high.png)
+4. To view the full report, click (i)
+
+   ![../../_images/7scan_report.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-87EF931F-9CF2-4909-BD82-654F0658AE7D-high.png)
+
+## Security Drift
+
+In addition to tracking the scan results over time as described in the previous section, HPE Morpheus Enterprise also provides detail into the change from the most recent scan to the one prior. This information is displayed in the Software tab (and Security subtab) of the detail page for the virtual machine (accessed from the associated Instance detail page or at Infrastructure > Hosts > Virtual Machines). The information surfaced by this view is listed below. If there is no change, you’ll simply see a “No Drift” message.
+
+- **Title:** The criteria for the test that has newly passed or failed
+- **Severity:** The severity level for the indicated security requirement
+- **Result:** The indicator for whether this test has newly passed or failed
+- **New Pass:** The number of tests that have newly passed compared to the prior scan
+- **New Fail:** The number of tests that have newly failed compared to the prior scan
+- **Status:** An indicator of the change in security posture since the prior scan. A net gain in test failures will yield a negative status indicator while net gains in passed tests (or no change) will yield a positive status indicator
+
+![../../_images/8securityDrift.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A56F50AC-F22B-4AB1-84B2-AE09A887951C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json b/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
new file mode 100644
index 0000000..1ca60fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+  "title": "Oracle Cloud",
+  "ordinal": 466,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md b/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
new file mode 100644
index 0000000..cd61259
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
@@ -0,0 +1,230 @@
+# Oracle Cloud
+
+## Required Permissions
+
+Integrating Oracle Public Cloud with HPE Morpheus Enterprise requires access to a service account with at least the permission set listed below. When creating an Oracle Cloud integration scoped to a specific compartment, the service account needs access only to the listed resource families within the chosen compartment. If the Cloud will be scoped to all compartments, the service account will need access to the listed resource families at the root compartment.
+
+### Oracle Cloud Policy Requirements
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage cluster-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage compute-management-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage data-catalog-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage dns in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage file-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage instance-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage object-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage virtual-network-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage volume-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+## Add Oracle Public Cloud
+
+IMPORTANT
+
+A Keypair (both public and private key) must be added to HPE Morpheus Enterprise with the Public Key in ssh-rsa format. The Public Key in PEM format needs to be added to Oracle Cloud users keys in Oracle Cloud console for authentication.
+
+NOTE
+
+Information on uploading the Public Key and generating Tenancy’s OCID and User’s OCID can be found at <https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm>
+
+To get started, navigate to Infrastructure > Clouds. Click + ADD and select Oracle Public Cloud to begin a new one. Configure the following options for the new Cloud:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+TENANCY OCID
+:   The OCID string from Tenancy Information section in Oracle Cloud
+
+USER OCID
+:   OCID String for the OPC API user
+
+SELECT KEY PAIR
+:   Select a keypair added to HPE Morpheus Enterprise matching the public key added to specified OPC API user
+
+REGION
+:   Select the OPC region (populates after successful account authentication)
+
+COMPARTMENT
+:   Choose to scope the Cloud to all compartments or to one specific compartment (populates after successful account authentication)
+
+INVENTORY
+:   Turn on for HPE Morpheus Enterprise to discover and sync existing VMs
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Enable Live Costing for Oracle Public Cloud
+
+Morpheus version 4.2.1 and higher support live costing data from the Oracle Cloud metering API. In order to authenticate with this API, edit your existing Oracle Cloud account integration or begin the process of newly integrating an account that wasn’t previously consumable in HPE Morpheus Enterprise (Infrastructure > Clouds > +ADD).
+
+In the advanced options section of the add/edit cloud modal for Oracle Public Cloud, the COSTING KEY and COSTING SECRET fields must be completed to work with metering API data in HPE Morpheus Enterprise. Unlike the OCI API authentication used to initially integrate Oracle Cloud, the metering API uses token-based authentication. We must access a Client ID and Client Secret value from the Oracle Public Cloud console to complete these fields.
+
+![../../../_images/1editcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CA223A6F-8A57-42C6-B371-5D9F07D3DDBA-high.png)
+
+Navigate to Oracle cloud sign in page, the URL for which is similar to the following example:
+
+`https://idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/signin`
+
+If you’re not redirected to the admin console similar to the one pictured below, log out and replace ‘signin’ at the end of the URL with ‘adminconsole’ as in the following example:
+
+`https:// idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/adminconsole`
+
+You’ll immediately be redirected back to the same signin page but in doing that you should be taken to the admin console after authenticating your session once again.
+
+![../../../_images/2adminconsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E1A971F2-CCF2-4FCF-BCAB-4E9EC09A92EE-high.png)
+
+Create a new application and select the type “Confidential Application”.
+
+![../../../_images/3confapp.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B6335CF7-81F9-4564-9377-E3B26BCA269F-high.png)
+
+On the Details tab, enter a “Name” value and click “Next”.
+
+![../../../_images/4appdetails.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B1C6E805-6451-4525-8A6F-F96C9D28BA31-high.png)
+
+On the Client tab, choose to “Configure this application as a client now” to reveal additional fields. Then, in the Authorization section, mark the boxes for “Client Credentials” and “JWT Assertion”.
+
+![../../../_images/5appauth.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5B10DEAF-82FB-461E-A804-8D2586512948-high.png)
+
+In the Token Issuance Policy section, click the “+Add Scope” button. Click the right-facing arrow button in the row for “CloudPortalResourceApp”. Mark the box to give read access for metering and click “Add”.
+
+![../../../_images/6meteringread.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F724B49C-D954-4EB3-BDAF-20A717A770AA-high.png)
+
+Click “Next” until the “Finish” button is shown, then click “Finish”
+
+The Client ID and Client Secret value will be shown at this point. If these values need to be referenced in the future, simply edit the application and go to the Configuration tab. The Client ID and Client Secret are shown in the General Information section.
+
+![../../../_images/7secretvalues.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-AACE06F0-9EBF-414D-9414-AFC686F70DE7-high.png)
+
+Back in HPE Morpheus Enterprise, enter these values in the COSTING KEY and COSTING SECRET fields of the add/edit cloud modal for your Oracle Public Cloud integration. You also need to fill in the IDENTITY SERVICE value. This value can be found in the URL for your Oracle admin console as shown in the image below. It will be in a format `idcs-xxxxxx`.
+
+![../../../_images/8identityservice.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E608C9F2-141F-4075-9B0D-B3A5EC53F46A-high.png)
+
+Save changes to the Cloud.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json b/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
new file mode 100644
index 0000000..cba66d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+  "title": "Digital Ocean",
+  "ordinal": 392,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.html",
+  "topic_cluster": {
+    "clustering_title": "Digital Ocean",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md b/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
new file mode 100644
index 0000000..01449da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
@@ -0,0 +1,143 @@
+# Digital Ocean
+
+## Add a Digital Ocean Cloud
+
+DigitalOcean Cloud Integration Detail fields:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   DigitalOcean Username
+
+API Key
+:   Personal access tokens/Key from the DigitalOcean API  >  Tokens/Keys section.
+
+Data Center
+:   Select DigitalOcean DataCenter Region
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json b/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
new file mode 100644
index 0000000..f126c10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+  "title": "SAML Integration",
+  "ordinal": 285,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html",
+  "topic_cluster": {
+    "clustering_title": "SAML Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md b/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
new file mode 100644
index 0000000..40e0879
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
@@ -0,0 +1,150 @@
+# SAML Integration
+
+## Overview
+
+The HPE Morpheus Enterprise SAML identity source integration allows customers to add user SSO to HPE Morpheus Enterprise, authenticated by external login SAML providers.
+
+![../../_images/samlLoginGeneric.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0A6CC774-6C13-4B74-B7A5-C8D414D5D46A-high.png)
+
+## Adding a SAML Integration
+
+### About this task
+
+To add a SAML integration:
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a tenant.
+3. Select IDENTITY SOURCES in the Tenant detail page
+4. Select + ADD IDENTITY SOURCE.
+5. Select SAML SSO from the TYPE field
+6. Add a Name and optional Description for the SAML integration
+
+### Results
+
+![../../_images/saml.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FEB50132-F13C-491F-83D8-FEABA6E7BB0C-high.png)
+
+There are 4 sections with fields that need to be populated depending on the desired configuration:
+
+- SAML Configuration
+- Role Mappings
+- Role Options
+- Assertion Attribute Mappings
+
+## SAML Configuration
+
+LOGIN REDIRECT URL
+:   This is the SAML endpoint HPE Morpheus Enterprise will redirect to when a user signs into HPE Morpheus Enterprise via SAML
+
+SAML LOGOUT REDIRECT URL
+:   The URL HPE Morpheus Enterprise will POST to when a SAML user logs out of HPE Morpheus Enterprise
+
+INCLUDES SAML REQUEST PARAMETER
+:   **Yes** (recommended) - the AuthN request will be sent via the ?SAMLRequest= parameter in the URL (GET)
+
+    **No** - the AuthN request will be submitted in the body of the request (POST)
+
+    NOTE
+
+    The SAML SP documentation should mention which binding to use but GET is most common
+
+SAML REQUEST
+:   **No Signature** - No signature is used on the SAML request
+
+    **Self Signed** - A self-signed X.509 Certificate is generated after clicking SAVE CHANGES. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+    **Custom RSA Signature** - Import a custom RSA Private Key and respective X.509 Certificate. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+SAML RESPONSE
+:   **Do Not Validate Assertion Signature** - The SAML response signature from the SAML SP will not be validated
+
+    **Validate Assertion Signature** - The SAML response signature from the SAML SP will be validated. Enter the SAML SP X.509 certificate in the **Public Key** field. This must be in PEM format
+
+IMPORTANT
+
+Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+## Role Mappings
+
+DEFAULT ROLE
+:   Role any SAML user will be assigned by default
+
+ROLE ATTRIBUTE NAME
+:   The name of the attribute/assertion field that will map to HPE Morpheus Enterprise roles, such a MemberOf
+
+REQUIRED ROLE ATTRIBUTE VALUE
+:   Attribute/assertion value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+<HPE Morpheus Enterprise ROLE NAME>
+:   Additional roles that can be mapped to a user, which will add to the DEFAULT ROLE. Attribute value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+## Role Options
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+## Assertion Attribute Mappings
+
+GIVEN NAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user First Name
+
+SURNAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user Last Name
+
+EMAIL ATTRIBUTE
+:   SAML SP field value to map to HPE Morpheus Enterprise user email address
+
+![../../_images/saml_assertion_attribute_mappings.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A5E51597-2545-4462-AD43-F82AB88434E7-high.png)
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added.
+
+In the Identity Sources section, important information for configuration of the SAML integration is provided. Use the SP ENTITY ID and SP ACS URL for configuration on the external login SAML provider side.
+
+NOTE
+
+In some cases, the SAML provider may need these values before providing the LOGIN REDIRECT URL and other values. When creating the integration, the NAME and LOGIN REDIRECT URL can contain any values, then selecting SAVE CHANGES will generate the above values. The NAME and LOGIN REDIRECT URL can be edited later, once the SAML configuration is created in the SAML provider.
+
+- ENTITY ID
+- SP ACS URL
+- LOGIN REDIRECT URL
+- SP METADATA
+
+![../../_images/identity_sources_info.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-112ECB06-8A2B-4025-B4CB-B57B7F12A12B-high.png)
+
+Sample Metadata code output:
+
+```
+```
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?><EntityDescriptor entityID="https://someip.com/saml/eDKL60P25" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"><SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"><NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat><AssertionConsumerService index="0" isDefault="true" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://someip.com/externalLogin/callback/eDKL60P25"/></SPSSODescriptor></EntityDescriptor>
+```
+```
+
+NOTE
+
+Different SAML providers will have different field names and requirements. An Okta SAML Dev environment was used for the example integration in this article.
+
+## Okta SAML SSO
+
+For Okta SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : Identity Provider Single Sign-On URL
+- ENTITY ID: Audience URI (SP Entity ID)
+- SP ACS URL: Single sign on URL
+
+## Onelogin SAML SSO
+
+For Onelogin SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : SAML 2.0 Endpoint (HTTP)
+- SAML LOGOUT REDIRECT URL : SLO Endpoint (HTTP)
+- SIGNING PUBLIC KEY : X.509 Certificate
+- ENTITY ID: ACS (Consumer) URL Validator
+- SP ACS URL: ACS (Consumer) URL
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json b/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
new file mode 100644
index 0000000..bab98c1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+  "title": "OS Imaging",
+  "ordinal": 450,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html",
+  "topic_cluster": {
+    "clustering_title": "OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md b/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
new file mode 100644
index 0000000..ba7861a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
@@ -0,0 +1,7 @@
+# OS Imaging
+
+| S. No. | Symptom | Additional Details | Common Checks | Log Files | **Remarks** |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Windows Setup fails before completion | - Do **not** dismiss error dialogs immediately, as this may remove diagnostic information. - Use **iLO Remote Console** to access the system. - Press **Shift + F10** to open a command prompt in the Windows PE environment. | **Disk layout** – Confirm the primary disk is attached to the local RAID controller.  **AutoUnattend.xml** – Verify the file exists and defines required partitions:   - EFI System Partition (500 MB) - Microsoft Reserved Partition (128 MB) - Primary OS partition | Relevant setup logs may be found in:   - `X:\Windows\Panther` - `C:\$WINDOWS.~BT\Sources\Panther`   Key files:   - `setupact.log` - `setuperr.log` | Use logs to identify the specific failure stage and error code. |
+| 2 | RHEL / Oracle Linux  (Autoinstall via Kickstart) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F1: Installer UI - Alt + F2: Interactive shell - Alt + F3: Installation logs | **Key Logs:**   - `/var/log/anaconda/anaconda.log` - `/var/log/anaconda/syslog` - `/root/anaconda-ks.cfg` - `/root/original-ks.cfg` - `/root/post-ks.log` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to validate disk and network configuration before retrying installation. |
+| 3 | Ubuntu Linux  (Autoinstall via Curtin and Subiquity) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F2 or Ctrl + Alt + F2: Interactive shell - Installer runs on TTY1 | **Key Logs**   - `/var/log/installer/curtin-install.log` - `/var/log/installer/early-commands.log` - `/var/log/installer/subiquity-client*` - `/var/log/installer/subiquity-server*` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to check network and storage configuration, then review logs for errors. |
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..fbaa05d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 149,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..ea00ba5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,83 @@
+# Configuring Virtual Images
+
+## System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
+
+## User Images
+
+Typically HPE Morpheus Enterprise does not have sufficient metatdata to successfully provision synced User Images. After integrating clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+### To edit and configure an existing Virtual Image:
+
+#### Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   HPE Morpheus Enterprise does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json b/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
new file mode 100644
index 0000000..e188236
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+  "title": "Morpheus Discovery",
+  "ordinal": 41,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Discovery",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md b/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
new file mode 100644
index 0000000..2b1859f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
@@ -0,0 +1,28 @@
+# Morpheus Discovery
+
+Morpheus has the ability to ingest existing environments. Existing running workloads will be inventoried into Morpheus and displayed in the UI. In 5-7 days Morpheus will start making recommendations based off of usage and pricing.
+
+NOTE
+
+Workloads that are inventoried do not have to be converted to managed.
+
+Once inventoried, Morpheus can provide valuable data for that instance:
+
+- Morpheus will know about networks
+- Start aggregating cost on public clouds
+- Start tracking usage
+- Some Clouds offer statistical details ( Amazon / VMware)
+- Power Status
+
+Right away inventorying existing environments will provide you with immediate insight to that environment. Once an existing workload has been discovered it can be converted to managed. Once converted to managed, Morpheus can deliver more capabilities and features.
+
+NOTE
+
+Workloads do not need the agent installed to be managed
+
+Once a workload is managed:
+
+- Enforce expiration/shutdown policies. This helps reign in environments (sprawl) and reduce cost.
+- Can tell what instance type it is
+- Can install agent (agent is optional)
+- Installing agent provides credentials and allows you to run workflows against it (day 2 operations)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json b/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
new file mode 100644
index 0000000..38979e5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+  "title": "User Roles",
+  "ordinal": 301,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html",
+  "topic_cluster": {
+    "clustering_title": "User Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md b/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
new file mode 100644
index 0000000..45396e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
@@ -0,0 +1,16 @@
+# User Roles
+
+User Roles can be single or multitenant. A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
+
+**Subtopics**  
+
+- **[Create a Single Tenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html)**
+- **[Create a MultiTenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json b/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
new file mode 100644
index 0000000..45eda38
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+  "title": "Cherwell",
+  "ordinal": 488,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html",
+  "topic_cluster": {
+    "clustering_title": "Cherwell",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md b/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
new file mode 100644
index 0000000..8c67d88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
@@ -0,0 +1,53 @@
+# Cherwell
+
+## Add Cherwell Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Cherwell` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   HOST
+   :   Url of the Cherwell Instance
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Cherwell user’s password
+
+   CLIENT KEY
+   :   Provide your Cherwell client key
+
+   CREATED BY USER
+   :   This is the full name of a user in the Cherwell system. When a new change management record is created in the Cherwell system, this user will be added to the record as the user that created it.
+
+   START DAYS FROM NOW
+   :   Number of days from now to set proposed start date
+
+   END DAYS FROM NOW
+   :   Number of days from now to set proposed end date
+
+   CUSTOM MAPPING
+   :   This is an optional json object that allows the custom setting of the Cherwell fields on the Change Request object.
+
+       NOTE
+
+       The keys in the map correspond to the name of the field on the Change Request in Cherwell that you would like to set (see <https://bertram.d.pr/1Ziuhy> for a reference). In addition, the value in the map corresponds to the value you wish to use. Within the value, Morpheus variables may be used. Here is an example for setting the Description is:
+
+       ```
+       ```
+       {  
+       "Description":"Created from Morpheus by ${instance.createdByUsername} in ${zone.name}"  
+       }
+       ```
+       ```
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.json b/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
new file mode 100644
index 0000000..33dcf8b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+  "title": "Job Executions",
+  "ordinal": 94,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html",
+  "topic_cluster": {
+    "clustering_title": "Job Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.md b/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
new file mode 100644
index 0000000..df5c568
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
@@ -0,0 +1,24 @@
+# Job Executions
+
+## Required Role Permissions
+
+Access and capabilities for the **Job Executions** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Job Executions`
+:   - None: Cannot access Provisioning: Job Executions section
+    - Read: Can access Provisioning: Job Executions section
+
+The Job Executions tab contains execution history of completed Jobs, including any process outputs and error messages. Information included in the Job Executions list includes:
+
+- Execution Status Icon
+- **Job Name - Task Name - Result Error Message:** The title of each execution includes the Job Name, Task or Workflow name (for Task and Workflow job types), and execution result error messages (when applicable) separated by hyphens (-). The title also links to the Job Execution detail page
+- **Start Date:** The date and time the Job Execution kicked off. When expanded, the start date and time of each individual Task are also shown
+- **Duration:** The time taken for the Job to complete. When expanded, the time to complete each individual Task is also shown
+- **User:** The user who executed or scheduled the Job
+
+Additional details and actions are available per execution:
+
+- Select an execution name to go to the Job Execution Detail page
+- Select the ⌃ icon at the end of the row to expand the execution and view additional details, including task process output
+- Select the 📋 icon to copy process output to local clipboard
+- Select the ⌄ icon at the end of an expanded to to collapse additional execution details
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..0a12b2b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 193,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..7c84cfa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json b/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
new file mode 100644
index 0000000..eac8eea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+  "title": "Creating ArubaCX Network Integration",
+  "ordinal": 431,
+  "parent_title": "Managed Networks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html",
+  "topic_cluster": {
+    "clustering_title": "Creating ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md b/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
new file mode 100644
index 0000000..8070e8c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
@@ -0,0 +1,21 @@
+# Creating ArubaCX Network Integration
+
+## About this task
+
+The network integration allows the user to specify the switch information. It is expected that there are 2 switches per rack acting as the top-of-rack (ToR) switches. You need to specify information for a switch pair for a rack. If there are more than 1 rack, then information for the switch pair for each rack is required.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network > Integrations.
+3. Click the Add to add a new integration.
+4. Select **HPE**Aruba CX Switches under the Networking section.   
+   ![Aruba CX Switches](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-EFC5C2DB-4496-480A-8039-50B8F31AAC5E-high.png)
+5. Enter the following details for the network integration: 
+
+   - **Name** for network integration
+   - **Username/Password** for the switches
+   - **Switch pair IP Addresses** for each pair of switches
+
+   ![Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6902768F-0D2B-472A-8F9F-6F8A7B286581-high.png)
+6. Click the Add Network Integration to create the Network Integration.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json b/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
new file mode 100644
index 0000000..9f38ecb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+  "title": "Prerequisites",
+  "ordinal": 203,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md b/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
new file mode 100644
index 0000000..c9d8415
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
@@ -0,0 +1,7 @@
+# Prerequisites
+
+- HPE Morpheus Enterprise appliance running version 8.0.13 or higher
+- At least one pre-existing OpenShift 4.x cluster, which can communicate back to the HPE Morpheus Enterprise appliance on the HTTPS port
+- Access to a full administrator account for each cluster which will be integrated
+- Ability for the HPE Morpheus Enterprise appliance to communicate with the OpenShift API on port 6443
+- Ability for the HPE Morpheus Enterprise appliance to communicate with each provisioned VM on port 22 for SSH and on port 3389 for Windows RDP
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json b/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
new file mode 100644
index 0000000..da7a5cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+  "title": "Isilon",
+  "ordinal": 522,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html",
+  "topic_cluster": {
+    "clustering_title": "Isilon",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md b/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
new file mode 100644
index 0000000..cda08b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
@@ -0,0 +1,132 @@
+# Isilon
+
+## Add Dell EMC Isilon Storage Server
+
+### About this task
+
+IMPORTANT
+
+Enable insecure mode on the NFS settings. This allows non-root ports to be used. Setting the insecure/privileged mode will require a restart of the Isilon nodes.
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Add Dell EMC Isilon File Share
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..9fd84cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 183,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..89fbd2e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,13 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json b/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
new file mode 100644
index 0000000..055438d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+  "title": "Adding Volume",
+  "ordinal": 442,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md b/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
new file mode 100644
index 0000000..06194f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
@@ -0,0 +1,17 @@
+# Adding Volume
+
+## About this task
+
+Perform the following procedure to create a new volume:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Add button.
+3. Select the storage server to create the volume in and click Next.   
+   ![Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-88533534-DD97-4462-88F4-443E815641B6-high.png)
+4. Select the required volume type, unreplicated, CPP replicated, or APP replicated, and click Next.   
+   ![Select Type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3E92F9CE-3785-4A3B-B5EF-BAADC8E40E1C-high.png)
+5. On the Configure screen, specify the volume name, size, datastore in which the volume needs to be created, shared/unshared. You can optionally specify the server/instance to export the volume, depending on whether it is unshared/shared.
+6. Click Complete to finish adding the volume.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8DC7D478-39B9-47ED-9F9A-4B6D87200464-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json b/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
new file mode 100644
index 0000000..7ad81c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+  "title": "Network Usage",
+  "ordinal": 434,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html",
+  "topic_cluster": {
+    "clustering_title": "Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md b/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
new file mode 100644
index 0000000..111e1a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
@@ -0,0 +1,15 @@
+# Network Usage
+
+Networks are attached to interfaces on a compute server. The interfaces can be the physical ports themselves or bond interfaces that combine two physical ports into an aggregated pipe. Bond interfaces provide the benefits of aggregated bandwidth on a single interface and also high availability by providing port-level redundancy.
+
+Once the decision is made on what kind of interfaces to use, networks can be chosen from the preconfigured list to attach to the network interfaces. This determines which VLANs are configured on which switch ports (or LAGs). As mentioned earlier, the primary VLAN is provisioned as an untagged VLAN, and the trunk VLANs are provisioned as tagged VLANs on the server ports.
+
+The supported bond types are:
+
+- Static Bond: This uses an L2+L3-based hash on the server OS and a static LAG on the switches.
+- LACP Bond: This uses the LACP mode on the server OS and LACP LAG on the switches.
+- Switch Independent Bond: This uses the balance-tlb mode on Linux servers and the switch-independent mode on Windows. The switch is configured as independent physical ports.
+
+**Subtopics**  
+
+- **[Specifying Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json b/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
new file mode 100644
index 0000000..ee8f827
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+  "title": "Trust Integrations",
+  "ordinal": 244,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html",
+  "topic_cluster": {
+    "clustering_title": "Trust Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md b/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
new file mode 100644
index 0000000..265019e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
@@ -0,0 +1,3 @@
+# Trust Integrations
+
+This area lists integrations with external services to manage secrets, keys, and certificates. New Cypher integrations can be created here. See [our guide](https://docs.morpheusdata.com/en/latest/infrastructure/keypairs_certificates/keypairs_certs.html#installing-and-integrating-an-external-cypher-appliance) on installing and integrating an external Cypher store for full details. Additionally, some other external trust services may be populated here, such as NSX certificate services.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json b/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
new file mode 100644
index 0000000..0453e63
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+  "title": "Overview",
+  "ordinal": 229,
+  "parent_title": "Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md b/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
new file mode 100644
index 0000000..0cb36a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
@@ -0,0 +1,11 @@
+# Overview
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in HPE Morpheus Enterprise.
+
+## Role Requirements
+
+There are two Role permissions for the Infrastructure  >  Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage give Full, Read or No access to the Infrastructure  >  Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
+
+## Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is var/opt/morpheus/morpheus-ui/. Its is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure  >  Storage section to avoid running out of disk space on the HPE Morpheus Enterprise Appliance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json b/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
new file mode 100644
index 0000000..28b95aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+  "title": "UCS Manager",
+  "ordinal": 471,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.html",
+  "topic_cluster": {
+    "clustering_title": "UCS Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md b/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
new file mode 100644
index 0000000..c87b46d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
@@ -0,0 +1,75 @@
+# UCS Manager
+
+## Overview
+
+The HPE Morpheus Enterprise UCS Manager Integration enables UCS M B and C Chassis Inventory, VM and Container Host Bare Metal Provisioning, PXE boot with IPMI, Storage Profile, SAN Connection Profile, Server Pool, BIOS Profile, Boot Profile, Maintenance Profile, UUID Pool and Disk Group Profile sync.
+
+## Adding UCS Manager Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select UCS MANAGER from the Clouds list
+4. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   UCS MANAGER
+   :   IP or hostname of UCS Manager
+
+   USERNAME
+   :   UCS Manager User
+
+   PASSWORD
+   :   UCS Manager Password
+
+   ORGANIZATION
+   :   - EXISTING (select)
+       - NEW (create)
+         :   - ORG NAME
+               :   Enter name for the new Organization
+
+   SERVER PREFIX
+   :   String provisioned servers will be prefixed with
+
+   DATA DISK MODE
+   :   - LVM data disk
+       - Single Disk
+
+   DATA VOLUME
+   :   Defaults to `/dev/sdb` \* Check to enable SOFTWARE RAID
+
+   NET INTERFACE
+   :   Defaults to eth0
+5. Select NEXT
+6. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+7. Select NEXT
+8. Review and then Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json b/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
new file mode 100644
index 0000000..da21f99
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+  "title": "Oracle VM",
+  "ordinal": 465,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle VM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md b/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
new file mode 100644
index 0000000..bfa1aa3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
@@ -0,0 +1,150 @@
+# Oracle VM
+
+## Add an Oracle VM Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+API URL
+:   Oracle VM API URL. ex: <https://10.20.30.40:7002/ovm/core/wsapi/rest>
+
+USERNAME
+:   Oracle VM User
+
+PASSWORD
+:   Oracle VM User Password
+
+REPOSITORY
+:   Available repositories will auto-populate upon successful authentication with the above credentials. Select appropriate repository for this Cloud.
+
+SERVER POOL
+:   Available server pools will auto-populate upon successful authentication with the above credentials. Select appropriate server pool for this Cloud.
+
+Inventory Existing Instances
+:   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..5065379
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 324,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..46c6dd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,68 @@
+# Provisioning
+
+## Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Show Pricing
+:   Displays or hides Pricing in Provisioning wizard and Instance and Host detail pages.
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and HPE Morpheus Enterprise will track issued sequence numbers and use the next available number each time.
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
+
+## Cloud-Init Settings
+
+HPE Morpheus Enterprise can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
+
+## Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
+
+## PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
+
+## App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
+
+## Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, HPE Morpheus Enterprise will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint (only up to v1.5.5). When selecting “manual”, HPE Morpheus Enterprise will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json b/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
new file mode 100644
index 0000000..10d5edd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+  "title": "Instance Details",
+  "ordinal": 85,
+  "parent_title": "Instances",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md b/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
new file mode 100644
index 0000000..1cb0e10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
@@ -0,0 +1,53 @@
+# Instance Details
+
+The instance detail page is where you can view and fully manage an instance. To get to an instance detail page, navigate to Provisioning > Instances, and click on an Instance. Please note Instance details and actions will differ between Instance types and user permissions.
+
+There are several sections within an Instance page that provide useful capabilities to the user.
+
+![../../_images/instanceDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1E7A4007-3C1F-4E44-A046-41A0C62111AA-high.png)
+
+Summary
+:   Basic information, stats and status information
+
+    - **Availability:** The Instance availability is the percentage of time the Instance is up. When stopping Instances, the option is given to mute monitoring if you wish for intentional down time not to count against the availability
+    - **Response Time:** If listed as “N/A” (Not Applicable), the Instance does not have any Checks set against it or does not have any Checks set against it that report a response time. Agent Checks, for example, do not report a response time. Some Checks, such as Docker Checks for Docker containers, require HPE Morpheus Enterprise to ping the container which reports a response time.
+
+Deploy
+:   Track deployment history for instance types that support deployments or manually kick off a deployment (only visible for Instance Types that support deployments)
+
+Settings
+:   Some Instance Types support custom configuration settings (for example, MySQL presents the my.ini)
+
+Resources
+:   VMs, containers, or other resources associated with the Instance are listed here. Some Instance Types, such as XaaS Instances, will not have resources and the tab is not displayed
+
+Runtime
+:   View the environment variables presented to the Instances or exported to the Instances via Apps (more on this in the Apps section). Users may also see Imported environment variables that may be referenced by the running Instance.
+
+    For Instances that support load balancing and auto scaling, configure auto scaling thresholds and load balancer settings in the Scale subsection that pertain to a particular Instance.
+
+    The software subsection will show any tracked software which is Installed as part of the provisioning process and is being tracked.
+
+Storage
+:   See storage information associated with the Instance including the list of volumes and controllers which are associated with each machine that makes up the Instance.
+
+Network
+:   Useful for configuring network interfaces for your VMs or security groups which allow access to the Instance.
+
+Monitoring
+:   Quick summary of the monitoring system and all checks that were configured to test the state of the Instance. Stats views (memory, cpu, etc.) can be zoomed out to a 90-day view if desired (in global settings, ensure your stats retention setting will support this). Logs and guidance for the individual Instance are also shown in their respective subtabs.
+
+Backups
+:   Quick backup dashboard. Useful for viewing historical backups and snapshots as well as adding new backup jobs.
+
+History
+:   See historical information related to automation which has been run against the Instance. This is useful for examining automation which was run as part of a phase of a Provisioning Workflow. Users can also drill into the Workflows to examine individual Tasks, including viewing the output from these Tasks to confirm success or troubleshoot issues.
+
+Costing
+:   Invoices pertaining to the Instance are displayed here. See the Instance level or host level invoices along with individual line items. In the History subtab view historical pricing data to monitor trends. In the Prices subtab view any prices which have been created and used to build a metered costing profile for the workload.
+
+Console
+:   Access the Instance or container via a client-less Console supporting SSH, RDP, VNC, or even hypervisor-level remote consoles.
+
+Wiki
+:   View the Wiki page for this Instance or edit the existing Wiki page (which may currently be blank). The content field supports markdown formatting, see the main Wiki section of HPE Morpheus Enterprise documentation for additional details.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..0b2f386
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 510,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..53d6937
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,142 @@
+# HPE Aruba CX DSS
+
+## Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus Enterprise Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a HPE Morpheus Enterprise `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for HPE Morpheus Enterprise environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM Cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. HPE Morpheus Enterprise integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM Hosts in the HVM Cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM Cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
+
+## Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM Hosts are added or removed from the HVM Cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
+
+## Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in HPE Morpheus Enterprise
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM Cluster
+
+  - Ensure all hosts within the HVM Cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- HPE Morpheus Enterprise appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the HPE Morpheus Enterprise Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
+
+## Adding HPE Aruba CX DSS Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+### Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
+
+## Create HPE ANW DSS Port Group Network
+
+### About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-02143765-1935-4568-A755-9A6B134CA122-high.png)![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BF4B2385-7813-4CB8-912B-DCF724834F47-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
+
+## Delete HPE ANW DSS Port Group Network
+
+### About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
+
+## View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json b/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
new file mode 100644
index 0000000..175eae4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+  "title": "ESXi",
+  "ordinal": 393,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.html",
+  "topic_cluster": {
+    "clustering_title": "ESXi",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md b/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
new file mode 100644
index 0000000..d0029da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
@@ -0,0 +1,159 @@
+# ESXi
+
+## About this task
+
+The ESXi Cloud type enables managing and provisioning to ESXi hosts, even without the ESXi API enabled.
+
+IMPORTANT
+
+The VMware ESXi integration is for adding a single ESXi / vSphere Hypervisor host. If you have vCenter please use the VMWare vCenter cloud type for full vSphere integraiton features.
+
+To get started with VMware ESXi, simply add a VMware ESXi Cloud in either the Infrastructure  >  Clouds or Infrastructure  >  Groups section.
+
+## Procedure
+
+1. Select `+ Create Cloud` Button
+2. Select ESXi from the Add Cloud modal
+3. Select NEXT
+4. Provide the following information. 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   - ESXi Host name or IP address
+   - Username ( This is normally root )
+   - Password
+
+## Results
+
+NOTE
+
+If you receive the message “Error! Invalid cloud config” Please ensure you have ssh enabled on the ESXi host.
+
+## Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+## CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+## INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+## Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+IMPORTANT
+
+ESXi provisioning require a vmx file, which is not included in an OVF/OVA export from vCenter. A proper vmx file must be included when adding a vmdk/ovf/ova image to Virtual Images in Morpheus for successful provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..35c4194
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 188,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json b/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
new file mode 100644
index 0000000..a2e4651
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+  "title": "morpheus-ctl tips",
+  "ordinal": 25,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html",
+  "topic_cluster": {
+    "clustering_title": "morpheus-ctl tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md b/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
new file mode 100644
index 0000000..a393646
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
@@ -0,0 +1,63 @@
+# morpheus-ctl tips
+
+`morpheus-ctl` is useful beyond reconfigures and starting the ui, and many commands can be run across all services, or scoped to a singe service.
+
+Some common commands include:
+
+morpheus-ctl status
+:   Lists all the installed services and their current status
+
+morpheus-ctl start (service)
+:   This starts all services if no service is specified, or starts the specified service. For example,
+
+    - `morpheus-ctl start/stop/restart/kill` on an all-in-one appliance will start, stop, restart or kill mysql, opensearch, rabbitmq, check-server, guacd and the morpheus-ui, one by one.
+    - `morpheus-ctl start/stop/restart/kill morpheus-ui` will only start, stop, restart or kill the morpheus-ui service, leaving the other service in their current state. Same goes for `morpheus-ctl start/stop/restart/kill mysql`, `morpheus-ctl start/stop/restart/kill opensearch` etc.
+
+`morpheus-ctl` commands:
+
+```
+```
+General Commands:  
+  cleanse  
+    Delete *all* morpheus data, and start from scratch.  
+  help  
+    Print this help message.  
+  reconfigure  
+    Reconfigure the application.  
+  show-config  
+    Show the configuration that would be generated by reconfigure.  
+  uninstall  
+    Kill all processes and uninstall the process supervisor (data will be preserved).  
+ Service Management Commands:  
+   graceful-kill  
+     Attempt a graceful stop, then SIGKILL the entire process group.  
+   hup  
+     Send the services a HUP.  
+   int  
+     Send the services an INT.  
+   kill  
+     Send the services a KILL.  
+   once  
+     Start the services if they are down. Do not restart them if they stop.  
+   restart  
+     Stop the services if they are running, then start them again.  
+   service-list  
+     List all the services (enabled services appear with a *.)  
+   start  
+     Start services if they are down, and restart them if they stop.  
+   status  
+     Show the status of all the services.  
+   stop  
+     Stop the services, and do not restart them.  
+   tail  
+     Watch the service logs of all enabled services.  
+   term  
+     Send the services a TERM.  
+ Opensearch Commands:  
+   open-util  
+     Backup/Restore OpenSearch data  
+ Firewall Commands:  
+   firewall-enable-blocking  
+     Enables firewall blocking mode.
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json b/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
new file mode 100644
index 0000000..e4d67cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+  "title": "Getting Started with Terraform Instance Types",
+  "ordinal": 368,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started with Terraform Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md b/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
new file mode 100644
index 0000000..264a677
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
@@ -0,0 +1,203 @@
+# Getting Started with Terraform Instance Types
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+## Terraform Instance Types in Action
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+## Spec Templates
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+### AWS Subnet by Count
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+### AWS Terraform Default Vars
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+### AWS Provider Role Assume
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+### AWS Terrform Locals
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+### AWS VPC
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+## Inputs and Option Lists
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+## Instance Type
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+## Layout
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+## Provisioning
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+## Review the New Instance
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json b/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
new file mode 100644
index 0000000..83e3857
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+  "title": "Helm Blueprints",
+  "ordinal": 134,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html",
+  "topic_cluster": {
+    "clustering_title": "Helm Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md b/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
new file mode 100644
index 0000000..7edf706
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
@@ -0,0 +1,27 @@
+# Helm Blueprints
+
+If you’re using Helm Charts to manage Kubernetes applications, HPE Morpheus Enterprise allows you to bring them in from a Git repository as a Blueprint. The selected repository must be integrated with HPE Morpheus Enterprise before creating the Blueprint.
+
+To create a new Helm Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Helm. Click guilabel:NEXT.
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+In the Helm Configuration section, complete the following fields as needed to sync in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **CHART PATH:** The path to the folder within the repository containing your configuration files, enter “./” if this is the top level folder within the repository
+- **CONFIG:** Config files within your selected folder are displayed here for confirmation
+
+Once finished, click COMPLETE.
+
+Your new Helm Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..6daf1f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 240,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..ffc566b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,65 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+## Add Existing Key Pair
+
+### About this task
+
+To generate a existing Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
+
+## Generate Key Pair
+
+### About this task
+
+To generate a Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+### Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
+
+## Delete Key Pair
+
+### About this task
+
+To Delete Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json b/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
new file mode 100644
index 0000000..299cd2c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+  "title": "OpenShift Clusters",
+  "ordinal": 201,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html",
+  "topic_cluster": {
+    "clustering_title": "OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md b/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
new file mode 100644
index 0000000..1f8c400
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
@@ -0,0 +1,11 @@
+# OpenShift Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html)**
+- **[Adding the OpenShift Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html)**
+- **[Adding OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html)**
+- **[Provisioning into OpenShift](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json b/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
new file mode 100644
index 0000000..7df19d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+  "title": "SELinux",
+  "ordinal": 10,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md b/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
new file mode 100644
index 0000000..633687f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
@@ -0,0 +1,7 @@
+# SELinux
+
+If not required by organizational policy, we recommend setting SELinux to “Permissive” or “Disabled” modes to prevent any unnecessary security-related issues. HPE Morpheus Enterprise versions 3.6.0 and higher do support “Enforcing” mode if it is required by your organization due to IT policies. Set the mode appropriately prior to running the HPE Morpheus Enterprise installer and it will make the required changes based on your chosen SELinux context.
+
+IMPORTANT
+
+Setting SELinux to “Enforcing” mode requires policies to be configured correctly in order for the HPE Morpheus Enterprise appliance to function correctly.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json b/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
new file mode 100644
index 0000000..779a503
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+  "title": "Code",
+  "ordinal": 96,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html",
+  "topic_cluster": {
+    "clustering_title": "Code",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md b/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
new file mode 100644
index 0000000..cf48038
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
@@ -0,0 +1,37 @@
+# Code
+
+NOTE
+
+In v5.3.2+, `provisioning/deployments` is moved to `provisioning/code`.
+
+Provisioning > Code contains the Repositories, Deployments and Code Integrations sections.
+
+## Required Role Permissions
+
+Access and capabilities for the **Code** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents.
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents.
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
+
+**Subtopics**  
+
+- **[Repositories](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html)**
+- **[Import and Export](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html)**
+- **[Deployments](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html)**
+- **[Code Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json b/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
new file mode 100644
index 0000000..f031c37
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+  "title": "Github",
+  "ordinal": 481,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html",
+  "topic_cluster": {
+    "clustering_title": "Github",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md b/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
new file mode 100644
index 0000000..76194c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
@@ -0,0 +1,92 @@
+# Github
+
+Integrate your Github account with HPE Morpheus Enterprise and have access to all your public and private repositories within the platform. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Integrated Github repositories also populate the Code list page (Provisioning > Code) where repositories can be browsed and individual files can be viewed. Repositories can be configured as [import and export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html?highlight=import#import-and-export) targets from Code detail pages as well. Each time code from your repositories is invoked in Tasks, Workflows, Spec Templates, and more, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Generating a Personal Access Token (Classic)
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens (described in the next section). To create a new access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Tokens (classic)”
+7. Click Generate new token
+8. Click “Generate new token (classic)”
+9. Give the new token at least access to everything in the “repo” scope
+10. Click Generate token
+11. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+We recommend using a long-lived token, Github even includes the option to have no expiration on your tokens (for classic personal access tokens only, not fine-grained tokens). Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Generating a Fine-Grained Token
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens. To create a new fine-grained access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Fine-grained tokens”
+7. Click Generate new token
+8. Give the token access to all repositories unless you will only need to work with specific repositories within HPE Morpheus Enterprise
+9. Click Generate token
+10. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+Fine-grained tokens can be created with an expiration date of up to one year. Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Creating an Integration
+
+### About this task
+
+New Github integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need a Github access token to complete this step, see the prior section for instructions on obtaining a Github access code.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Github
+4. Configure the following: 
+
+   - NAME: A friendly name for the Github integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, this Github integration is active and any code repositories are available for building HPE Morpheus Enterprise automation and other constructs within the platform
+   - USERNAME: The username for your Github account
+   - PASSWORD: Copy your access token here rather than in the “ACCESS TOKEN” field. See the “Important” box below for additional details
+   - ACCESS TOKEN: Do not use this field. See the “Important” box below for additional details
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
+
+### Results
+
+IMPORTANT
+
+Your access token should be pasted into the PASSWORD field and not the ACCESS TOKEN field. If the ACCESS TOKEN field is used, the repository will create successfully and many features will work. However, in Code detail pages (Provisioning > Code > Selected code detail page), you will not be able to browse files in private Github repositories unless the access token is pasted into the PASSWORD field. New Github integrations should be created by pasting the access token in the PASSWORD field and the ACCESS TOKEN field should be ignored.
+
+NOTE
+
+In certain cases, it can take several seconds for the integration process to complete and the ADD INTEGRATION modal to be dismissed.
+
+## Viewing an Integrated Github Account
+
+When authentication is successful, click into the new Github integration from the list of available integrations. The Organizations tab will list each organization the Github account is associated with. The Repositories tab lists all public and private repositories which are associated with the account. We can also click in to each repository to view its files and folders, as well as create specific types of automation or Spec Templates from the files directly in this view.
+
+![../../_images/github.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-19D7B591-B18D-4BB5-A378-425A0110A7C7-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json b/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
new file mode 100644
index 0000000..8ed04b1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+  "title": "Overview",
+  "ordinal": 105,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md b/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
new file mode 100644
index 0000000..e037d06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
@@ -0,0 +1,7 @@
+# Overview
+
+There are many Task Types available, including scripts added directly, scripts and templates from the Library section, recipes, playbooks, puppet agent installs, and http (api) calls. Tasks are primarily created for use in Workflows, but a single Task can be executed on an existing instance via Actions  >  Run Task.
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json b/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
new file mode 100644
index 0000000..18af53e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+  "title": "Compute",
+  "ordinal": 209,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md b/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
new file mode 100644
index 0000000..7663e47
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
@@ -0,0 +1,23 @@
+# Compute
+
+![../../_images/infra_compute_header_5.4.3.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-04AE9DB4-27C9-40E0-8E37-1BCFA3CD8C32-high.png)
+
+NOTE
+
+The Infrastructure `Hosts` page from previous versions has been renamed to `Compute` and updated with `Container` and `Resource` sections.
+
+The Infrastructure  >  Compute section provides a universal stage for viewing and managing Hosts, Virtual Machines, Containers, Resources, and Bare Metal across Clouds.
+
+In this section you can:
+
+- View & Manage and Hosts, Virtual Machines, Containers, Resources, Bare Metal and Hypervisors
+- Add manual Virtual Machines and Bare Metal Hosts
+- Convert Hosts, Virtual Machines and Bare Metal to Managed
+
+**Subtopics**  
+
+- **[Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html)**
+- **[Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html)**
+- **[Resources](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html)**
+- **[Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json b/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
new file mode 100644
index 0000000..b4fc528
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+  "title": "Features",
+  "ordinal": 204,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md b/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
new file mode 100644
index 0000000..624c03c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
@@ -0,0 +1,14 @@
+# Features
+
+- Adds a new Cluster type, which is used to onboard pre-existing OpenShift clusters into HPE Morpheus Enterprise
+- Enables inventory synchronization for workloads provisioned outside of HPE Morpheus Enterprise in the OpenShift console
+- Monitor high-level cluster health details such as host numbers, alarms, and high CPU, memory or disk use situations
+- Monitor individual host and VM health details such as high CPU, memory, disk use, or network I/O situations
+- Onboard network objects, device-agnostic storage objects, and virtual images to enable OpenShift provisioning from the HPE Morpheus Enterprise provisioning wizard UI
+- Supports IPv4 and IPv6 networking
+- Adds new Instance Type to the HPE Morpheus Enterprise provisioning wizard for easy provisioning of new OpenShift virtualized workloads
+- VM provisioning supports the use of existing templates and service plans
+- Interface with Morpheus-type IP Pools or IP Pools sourced from IPAM integrations throughout the lifecycle of OpenShift workloads
+- Utilize the HPE Morpheus Enterprise automation engine for provisioning and for day two operations across the Instance lifecycle
+- Supports HPE Morpheus Enterprise labels and tagging features for resource organization
+- Provides guest console access into OpenShift-hosted virtual machines
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..b99690c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 223,
+  "parent_title": "Network",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..8d59ca1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,49 @@
+# Integrations
+
+## Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations. These services can also be added in the Administration > Integrations section.
+
+The following integrations are currently supported:
+
+Networking
+
+- Cisco ACI
+- VMWare NSX
+
+IPAM
+
+- Infoblox
+- Bluecat
+- phpIPAM
+
+Security
+
+- Cisco ACI
+
+DNS
+
+- Microsoft DNS
+- PowerDNS
+- Route 53
+
+## Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json b/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
new file mode 100644
index 0000000..a8f1853
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+  "title": "Policy Types",
+  "ordinal": 316,
+  "parent_title": "Policies",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md b/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
new file mode 100644
index 0000000..b205c81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
@@ -0,0 +1,117 @@
+# Policy Types
+
+Approve Delete
+:   Sets an approval requirement for deleting Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow. On delete request, Instances will be shut down and only deleted if approved.
+
+Approve Provision
+:   Sets an approval requirement for provisioning Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Reconfigure
+:   Sets an approval requirement for reconfiguring Instances and servers within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Workflow Execute
+:   If enabled, when Workflows are executed on workloads within the Policy scope, an Approval is generated. This could apply when a Workflow is executed from the Workflows list page or from the detail page for an Instance or server. Approvals can be targeted to HPE Morpheus Enterprise internal Approvals or targeted to a third-party integration (such as ServiceNow). The Workflow will not begin to execute until after the approval is granted.
+
+Backup Creation
+:   Disable or enable the ability to create a backup when provisioning an instance.
+
+Backup Targets
+:   A master account can determine storage provider options for backups with Backup Targets policies.
+
+Budget
+:   Sets a maximum total combined price for all instances in the Group, Cloud, Tenant or owned by the User this policy is applied to.
+
+Cluster Resource Name
+:   The name of Cluster hosts (master and workers) when creating Kubernetes, Docker and KVM Clusters. Pre-populates a fixed or editable Resource Name value for the cluster using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Cypher Access
+:   Granularly set LIST, READ, WRITE, and DELETE access to arbitrary Cypher secret paths scoped globally or to specific Roles and Users. See the section below for a guide to establishing a Cypher access policy.
+
+Delayed Delete
+:   Delayed Delete Policies allow for soft deletion of Instances and Apps. Instead of deleting immediately, Instances and Apps with a Delayed Delete policy applied will be shutdown upon deletion request and hidden by default from the UI. The Instance/App will then be in `Pending Removal` status. In order to see Instances pending deletion on the Instances list page (Provisioning > Instances), you must filter for “Pending Removal” status. These Instances will not show when filtered for “All Statuses”
+
+Expiration
+:   Sets an expiration timeframe in days after which the Instance will be deleted. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration. See HPE Morpheus Enterprise [Knowledge Base](https://support.morpheusdata.com/s/article/How-to-create-an-extensions) for more information about Expiration policies
+
+File Share Storage Quota
+:   Sets a Storage Quota for File Share usage (in GB) to scoped User, Role, Tenant or Global.
+
+Hostname
+:   The `hostname` or `computer name` which is set in the OS and DNS. On some platforms, hostnames are restricted by length, spaces, and/or special characters. Pre-populates a fixed or editable name for hostnames/machine names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Instance Name
+:   Pre-populates a fixed or editable name for Instance Names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings. Note that it’s not recommended administrators include “>”, “<”, “%”, “$”, or “=” in naming policies
+
+Instance Networks
+:   When an Instance is provisioned within the scope of the Policy (Group or Cloud scoping is supported), the network selected on the Policy is automatically set and locked in the provisioning wizard to force provisioning onto the selected network.
+
+Max Containers
+:   Sets the max number of Containers for the Group or Cloud the Policy is added to.
+
+Max Cores
+:   Sets the max number of total of Cores combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Hosts
+:   Sets the max number of total Hosts in the Group or Cloud the Policy is added to.
+
+Max Load Balancer Pools
+:   Sets the max number of load balancer pools within the policy scope
+
+Max Memory
+:   Sets the max number of total of RAM combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Pool Members
+:   Sets the maximum number of members in a load balancer pool
+
+Max Snapshots
+:   Set the maximum number of Snapshots that may be stored for each Instance or VM within the scope. Once the limit is met, HPE Morpheus Enterprise will warn the user when attempting to create more snapshots until the number is reduced
+
+Max Storage
+:   Sets the max number of total of Storage combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Virtual Servers
+:   Sets the maximum number of virtual servers within the policy scope
+
+Max VMs
+:   Sets the max number of Virtual Machines for the Group or Cloud the Policy is added to.
+
+Message of the Day (MOTD)
+:   Message of the Day”” Policy for displaying Alerts in HPE Morpheus Enterprise. Configurable as a pop-up or full-page notification with Info, Warning and Critical message types.
+
+    NOTE
+
+    Requires role permission: `Admin: Message Of the Day` set to “Full” to create and manage MOTD Policies.
+
+Network Quota
+:   Limits the number of networks that can be created within the policy’s scope
+
+Object Storage Quota
+:   Sets a Storage Quota for Object Storage usage (in GB) to scoped User, Role, Tenant or Global.
+
+Power Scheduling
+:   Adds a Power Schedule for the Instances in a Group or Cloud. Power Schedules can be created in Library > Automation > Power Scheduling
+
+Router Quota
+:   Limits the number of routers that can be created within the policy’s scope
+
+Shutdown
+:   Sets a shutdown timeframe in days upon provision after which the Instance will be stopped. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration.
+
+Storage Server Storage Quota
+:   Sets a Storage Quota for selected Storage Server (in GB), applied Globally or per specified Tenants.
+
+Tags
+:   Requires the user to add compliant Tags at provision time, this can be enforced on a strict or passive basis
+
+    NOTE
+
+    Tag scanning and enforcement is currently only available for Azure, Amazon, Google, and VMware clouds. For a more comprehensive guide on implementing Tag Policies, see the associated article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-work-with-cloud-tagging-policies?language=en_US).
+
+User Creation
+:   Controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+User Group Creation
+:   Forces User Creation of members in the selected User Group during Provisioning.
+
+Workflow
+:   Workloads provisioned within the scope of the Policy will have the indicated Workflow applied and the Tasks executed within the proper phase of the Instance lifecycle
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json b/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
new file mode 100644
index 0000000..a52751d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+  "title": "NSX Cloud",
+  "ordinal": 511,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html",
+  "topic_cluster": {
+    "clustering_title": "NSX Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md b/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
new file mode 100644
index 0000000..a4f1b53
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
@@ -0,0 +1,31 @@
+# NSX Cloud
+
+NSX Cloud is a networking solution that allows administrators to define networking and security policies for applications running in private and public clouds. When integrated with HPE Morpheus Enterprise, users can apply an NSX Cloud integration with VMware vCenter-type Clouds. This offers robust syncing and manipulation of NSX Cloud constructs as well as the ability to consume those networks when provisioning to VMware Cloud targets.
+
+## Features
+
+- Sync and manage DHCP servers
+- Sync and manage DHCP relays
+- Sync and manage network segments
+- Sync and manage distributed firewall rules
+- Sync and manage tier-1 routers
+- Sync and manage groups, including management groups and compute groups
+- Integration with VMware-type Clouds
+
+## Integrating with VMware Clouds
+
+Integration with a VMware Cloud requires the Cloud integration to be pre-existing. If you need to integrate a VMware Cloud first, refer to the [VMware Cloud integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html) in HPE Morpheus Enterprise UI documentation for full details. If you are creating the VMware Cloud now, bear in mind that you will need to update firewall inbound rules to allow the HPE Morpheus Enterprise appliance to connect with VMware. If this step is not done, any attempts to create that Cloud integration will fail. Log into the NSX Cloud web console and click on the Security tab. Within the security tab, go to the Gateway Firewall section and the Management Gateway tab within it. Edit the list of sources for your vCenter inbound rules. The IP address for the HPE Morpheus Enterprise appliance should be among the allowed inbound addresses.
+
+To begin a new NSX Cloud integration, navigate to Infrastructure > Network > Integrations. Click + ADD and then click “NSX Cloud”. Make the following configurations to create the integration with NSX Cloud:
+
+- **NAME:** A friendly name for the NSX Cloud integration in HPE Morpheus Enterprise
+- **VISIBILITY:** This option is only available from the Master Tenant. Select “Public” to make the NSX Cloud integration available to all Tenants. Select “Private” to reserve the integration for the Master Tenant
+- **API HOST:** The API access URL for NSX Cloud. Your API URL will look something like this: <https://nsx-xx-xx-xx-xx.rp.vmwarevmc.com/vmc/reverse-proxy/api/orgs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/sddcs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx>
+- **API KEY:** An API token granting sufficient access for HPE Morpheus Enterprise to work with all relevant NSX constructs
+- **CLOUD:** Select the VMware Cloud integration that NSX Cloud should integrate with
+
+Once done, click ADD NETWORK INTEGRATION. After a brief moment, the new integration will be created and will appear alongside other network integrations on the network integration list page. We can verify that NSX Cloud and the VMware Cloud are integrated by editing the VMware Cloud (Infrastructure > Clouds > Selected VMware Cloud > EDITbutton). Expand the Advanced Options panel of the EDIT CLOUD modal and the NSX Cloud integration should be set under the NETWORK MODE configuration.
+
+## Managing NSX Cloud
+
+With the integration complete, you can now examine the detail section for the new integration. From the network integration list page (Infrastructure > Network > Integrations), select the NSX Cloud integration that was just created. From this section, we can create, manage, and delete DHCP servers and relays, network segments, firewall rules, tier-1 routers, and groups.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.json b/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.json
new file mode 100644
index 0000000..59584fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+  "title": "Windows OS Imaging",
+  "ordinal": 411,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E55D4270-ED77-4161-8712-45824C891713.html",
+  "topic_cluster": {
+    "clustering_title": "Windows OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.md b/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.md
new file mode 100644
index 0000000..a9b29c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E55D4270-ED77-4161-8712-45824C891713.md
@@ -0,0 +1,38 @@
+# Windows OS Imaging
+
+This section provides guidance and requirements for deploying **Windows Server on bare metal** using Morpheus Enterprise. It covers required virtual image settings, Windows-specific boot considerations, current licensing limitations, and high-level troubleshooting guidance for failed installations.
+
+The following Windows distributions are supported for deployment:
+
+- Windows Server 2019
+- Windows Server 2022
+- Windows Server 2025
+
+## Virtual Image Configuration
+
+When adding a Windows ISO to the **Morpheus Virtual Images Library**, the following settings **must** be configured:
+
+- Is Cloud Init Enabled: Unchecked
+- Cloud Guest Customization: Checked
+- Sysprepped / Generalized Image: Checked
+- Install Agent: Checked
+- Advanced
+  - VM Tools Installed: Checked
+
+## Windows Install Image Index
+
+By default, Morpheus installs Image Index 2, which typically corresponds to Windows Server Standard (Desktop Experience).
+
+To deploy a different Windows edition:
+
+1. Navigate to Library > Operating Systems.
+2. Add a new Operating System entry with **Platform = Windows**.
+3. Specify the desired Windows Install Index.
+4. Complete the required fields (Vendor, OS Version, Category, OS Name, Codename, OS Family).
+5. Associate the Windows Virtual Image with this Operating System.
+
+You can use the existing Windows Operating System as reference templates.
+
+**Subtopics**  
+
+- **[Boot Prompt Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json b/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
new file mode 100644
index 0000000..a9dd3cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+  "title": "Tenant Role Permission Sections",
+  "ordinal": 297,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md b/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
new file mode 100644
index 0000000..8bb3768
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
@@ -0,0 +1,34 @@
+# Tenant Role Permission Sections
+
+Features
+:   Controls Tenant access level for sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Clouds
+:   Controls Tenant access level for Clouds. This list includes Clouds integrated from the Master Tenant and shared publicly. Tenants given this Tenant Role will have either Full, Read, or None access levels to a given Cloud. See the section below for more information on Cloud Access levels.
+
+Instance Types
+:   Controls Tenant access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls Tenant access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls Tenant access for each report type in the Reports section (Operations > Reports). The Tenant must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls Tenant access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls Tenant access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters within the associated Tenant
+
+VDI Pools
+:   Controls Tenant access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls Tenant access to Workflows. Only selected Workflows will be shared down to Tenants having the associated Role
+
+Tasks
+:   Controls Tenant access to Tasks. Only selected Tasks will be shared down to Tenants having the associated Role
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json b/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
new file mode 100644
index 0000000..3d13dd8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+  "title": "Provisioning a Workload",
+  "ordinal": 182,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md b/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
new file mode 100644
index 0000000..1006844
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. The system default Ubuntu Instance Type contains a compatible Layout for HVM deployment. Add an Instance from the Instances list page (Provisioning > Instances). After selecting the Instance Type, choose a Group that allows for selection of the HPE Morpheus Enterprise-type Cloud containing the HVM cluster.
+
+![../../_images/groupCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-87BE27BB-2F87-4323-B45A-8A8D0C89DE4B-high.png)
+
+After moving to the next tab, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the Ceph volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+![../../_images/configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-36A8D9F5-3920-45A7-A6A6-1803A8897B35-high.png)
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json b/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
new file mode 100644
index 0000000..6a13ff5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+  "title": "Roles and Identity Sources",
+  "ordinal": 294,
+  "parent_title": "Roles",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md b/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
new file mode 100644
index 0000000..9ab871a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to HPE Morpheus Enterprise for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the HPE Morpheus Enterprise role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within HPE Morpheus Enterprise. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Tenant management or user management in Administration > Tenants or Administration > Users, and has to be configured on a per-tenant basis. Additionally, administrators may opt to lock users to their mapped role in HPE Morpheus Enterprise or keep the roles unlocked to manually administer roles in one-off scenarios.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json b/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
new file mode 100644
index 0000000..8338549
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+  "title": "Importing Pre-Provisioned Server",
+  "ordinal": 418,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html",
+  "topic_cluster": {
+    "clustering_title": "Importing Pre-Provisioned Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md b/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
new file mode 100644
index 0000000..710c5a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
@@ -0,0 +1,13 @@
+# Importing Pre-Provisioned Server
+
+Importing a Pre-Provisioned server enables administrators to bring existing physical servers and associated resources (networks and storage) into HPE Morpheus. This is the initial step in migrating an existing workload cluster into Morpheus management. It is completed in two phases:
+
+- **Import**: Import existing servers as Pre-Provisioned resources.
+- **Convert to Managed**: Convert imported servers into managed instances, creating Morpheus instances with associated network and storage attachments.
+
+This process is performed one workload cluster at a time, and each cluster can contain one or more servers. Once the initial server is converted, additional imported servers can be added to the same instance using the Add Node operation.
+
+**Subtopics**  
+
+- **[Import Pre-Provisioned Servers](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html)**
+- **[Add Additional Nodes to the Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json b/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
new file mode 100644
index 0000000..897ca24
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+  "title": "Deleting Volume",
+  "ordinal": 443,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md b/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
new file mode 100644
index 0000000..ccc51ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
@@ -0,0 +1,12 @@
+# Deleting Volume
+
+## About this task
+
+This procedure allows the users to delete a volume. A volume can be deleted only after it is detached from all the servers.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Delete for the volume to be deleted.
+3. Click the Delete on the confirmation screen.   
+   ![Delete Volume](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4385EF29-CF09-4386-B7D5-20D68EC1B8F9-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json b/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
new file mode 100644
index 0000000..236329c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+  "title": "Bare Metal",
+  "ordinal": 214,
+  "parent_title": "Compute",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html",
+  "topic_cluster": {
+    "clustering_title": "Bare Metal",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md b/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
new file mode 100644
index 0000000..35d7c9a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
@@ -0,0 +1,10 @@
+# Bare Metal
+
+![../../_images/infra_compute_header_bm_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-26D91B4A-96E5-45CF-AC5E-4234F1F3AA28-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Bare Metal hosts are from discovered, PXE Boot or manually added Bare Metal hosts. Bare Metal hosts that are also Hypervisors will be listed in the Hosts section.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json b/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
new file mode 100644
index 0000000..e813587
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+  "title": "Networks Configuration",
+  "ordinal": 432,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html",
+  "topic_cluster": {
+    "clustering_title": "Networks Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md b/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
new file mode 100644
index 0000000..24d2953
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
@@ -0,0 +1,16 @@
+# Networks Configuration
+
+Once the network integration is created, networks can be created using the specific network integration that was created. Networks essentially define the VLAN that they represent along with other attributes such as the subnet’s IPv4 prefix, IP address allocation method, gateway address, DNS, etc. The screenshot below shows those details.
+
+The VLAN Trunks specifies the trunk VLANs to be added when this network is consumed by an instance. The VLAN ID field represents the primary VLAN for this network. This VLAN is configured as the untagged VLAN when this network is consumed by an instance.
+
+The Network Service corresponds to the network integration that was created. This specifies that the network is to be created in the infrastructure (switches) specified in the network integration selected.
+
+The Private checkbox specifies that the network is a private network. By default, all networks are public. If private is selected, the primary VLAN in this network is not configured on the uplink connection. This would render them unreachable from outside of the cloud infrastructure. This is typically used for workload networks that are used to communicate between only the workload servers and other infrastructure within the private cloud.
+
+The configuration of a network will result in the primary VLAN in that network being provisioned on the network switches. The server ports are configured when those networks are consumed during the provisioning of a compute instance.
+
+**Subtopics**  
+
+- **[Creating Network Using the ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html)**
+- **[Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json b/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
new file mode 100644
index 0000000..a64b927
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+  "title": "Add FortiADC load balancer",
+  "ordinal": 499,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html",
+  "topic_cluster": {
+    "clustering_title": "Add FortiADC load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md b/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
new file mode 100644
index 0000000..4be98ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
@@ -0,0 +1,48 @@
+# Add FortiADC load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **FortiADC**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![FortiADC lb](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-70A960BC-376C-493B-A101-3E02EB65C9C2-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the FortiADC API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the FortiADC API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter FortiADC service account username.
+   :   **PASSWORD \***: Enter FortiADC service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new FortiADC Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new FortiADC Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new FortiADC Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json b/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
new file mode 100644
index 0000000..c6845e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+  "title": "Add Additional Nodes to the Instance",
+  "ordinal": 421,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Add Additional Nodes to the Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md b/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
new file mode 100644
index 0000000..089e000
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
@@ -0,0 +1,20 @@
+# Add Additional Nodes to the Instance
+
+## About this task
+
+To convert a Pre-Provisioned server into a fully provisioned node, and to make it part of an existing instance, the Add Node action is used, from the context of the Instance to which it is desired to be added.
+
+Once an instance is created with the first converted node, you can add other imported servers to the same instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the newly created instance.
+3. Click Add Node. ![Add node action](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-E34393DB-6064-4C8B-B3CA-6AC91E7546D5-high.png)
+4. Select Pre-Provisioned.
+5. Choose the imported server and provide the required details.
+6. Click Execute. ![Execute Action](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CCCDD2C8-A5AF-4EBD-9902-85ACA1A99155-high.png)
+
+## Results
+
+This converts the selected imported server into a managed node and adds it to the existing instance.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json b/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
new file mode 100644
index 0000000..63da739
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+  "title": "User Guides",
+  "ordinal": 359,
+  "parent_title": "Guides",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html",
+  "topic_cluster": {
+    "clustering_title": "User Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md b/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
new file mode 100644
index 0000000..145e799
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
@@ -0,0 +1,18 @@
+# User Guides
+
+**Subtopics**  
+
+- **[Getting started with Morpheus and AWS](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html)**
+- **[Getting started with HPE Morpheus Enterprise and VMware](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html)**
+- **[Getting started with HPE Morpheus Enterprise and Azure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html)**
+- **[Automated Single-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html)**
+- **[Automated Multi-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html)**
+- **[Adding Functionality Through Operational Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html)**
+- **[Creating XaaS Instance Types with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html)**
+- **[Morpheus Virtual Desktops](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html)**
+- **[Getting Started with Terraform Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html)**
+- **[Backing Up and Restoring HPE Morpheus Enterprise Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html)**
+- **[Cloud Resource Tagging with Morpheus](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html)**
+- **[Cypher Policies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-0060B753-B50F-4F2A-A500-BABB38426A84_2.html)**
+- **[Configuring Access with Clouds, Groups, and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html)**
+- **[Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json b/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
new file mode 100644
index 0000000..8ccb719
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+  "title": "Add Azure load balancer",
+  "ordinal": 493,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html",
+  "topic_cluster": {
+    "clustering_title": "Add Azure load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md b/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
new file mode 100644
index 0000000..ffd6d26
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
@@ -0,0 +1,27 @@
+# Add Azure load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Azure Load Balancer**. 
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Azure LB](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C6A8AF5C-33DF-49FE-9EEA-C205AE35F54B-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions.
+
+   RESOURCE GROUP
+   :   Select the Resource Group for the load balancer.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json b/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
new file mode 100644
index 0000000..4d12d92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+  "title": "Delete SSL Certificate",
+  "ordinal": 243,
+  "parent_title": "Trust",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html",
+  "topic_cluster": {
+    "clustering_title": "Delete SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md b/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
new file mode 100644
index 0000000..be44533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
@@ -0,0 +1,11 @@
+# Delete SSL Certificate
+
+## About this task
+
+To Delete SSL Certificate:
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected SSL Certificate
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..8c37892
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 169,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..4f1f018
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,191 @@
+# Clouds
+
+## Overview
+
+Clouds are integrations or connections to public, private, hybrid clouds, or bare metal servers. Clouds can belong to many groups and contain many hosts. The clouds view includes clouds status, statistics, tenant assignment, and provides the option to add, edit, delete new clouds. HPE Morpheus Enterprise supports most Public Clouds and Private Clouds.
+
+### Supported Cloud Types
+
+- Alibaba Cloud
+- Amazon
+- Azure (Public)
+- Azure Stack (Private)
+- Canonical MaaS
+- Cloud Foundry
+- Dell (Cloud type for PXE and manually added Dell EMC Hosts)
+- DigitalOcean
+- Google Cloud
+- HPE (Cloud type for PXE and manually added HPE Hosts)
+- Huawei
+- Hyper-V
+- IBM Cloud
+- IBM Cloud Platform
+- Kubernetes
+- MacStadium
+- Morpheus (Generic Cloud type for PXE/Bare Metal and manually added Hosts)
+- Nutanix
+- Open Telekom Cloud
+- OpenStack
+- Oracle Public Cloud
+- Oracle VM
+- Platform 9
+- SCVMM
+- Supermicro (Cloud type for PXE and manually added Supermicro Hosts)
+- UCS
+- UpCloud
+- vCloud Air (OVH)
+- VMWare ESXi
+- VMware Fusion
+- VMWare on AWS
+- VMware vCenter
+- VMware vCloud Director
+- XenServer
+
+Information on each cloud type can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Creating Clouds
+
+Clouds can be added from Infrastructure  >  Clouds or in Infrastructure  >  Groups  >  (select Group)  >  Clouds. Individual Guides for adding specific Cloud Types can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, current month costs, average monthly costs, resource utilization statistics, and resource counts for Container Hosts, Hypervisors, Bare Metal, Virtual Machines, and Unmanaged resources.
+
+![../../_images/clouddetailview1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-79A36EB1-C3D0-4D23-9067-DD12ABD6EDB7-high.png)
+
+To view the Cloud List View, select the name of a Cloud to display the clouds Detail View.
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud. Depending on the Cloud, choose to force a standard Cloud sync (occurs every five minutes by default) or a nightly sync. When syncing Costing data, HPE Morpheus Enterprise will force a pull of costing data for your specified period. If opting to “rebuild” the costing data, HPE Morpheus Enterprise will delete all costing data from the Cloud for that period and attempt to rebuild the data by calling the Cloud API.
+
+DELETE
+:   Delete the Cloud from HPE Morpheus Enterprise
+
+IMPORTANT
+
+All Instances and managed Hosts and VM’s associated with the Cloud must be removed prior to deleting a cloud.
+
+### Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Load Balancers
+:   The load balancers tab panel displays available load balancers in the cloud including the name, description, type, cloud and host. You can add a load balancer from this tab by clicking ADD LOAD BALANCER.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
+
+Policies
+:   Manages Policies enforced on the Cloud. Setting a policy on this tab is equal to creating a policy in Administration > Policies and scoping it to the selected Cloud.
+
+Profiles
+:   Manages Terraform, Key/Value Profiles that create custom object associated secrets and metadata that will automatically be mapped per Cloud selection during provisioning and automation.
+
+## Deleting Clouds
+
+### About this task
+
+To delete a cloud:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+### Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud. To remove Instances, hosts and VMs from HPE Morpheus Enterprise without deleting the Cloud resources they represent, select Delete on the host or VM, unselect “Remove Infrastructure”, and select “Remove Associated Instances” if Instance are associated with the selected Hosts or VMs.
+
+## Cloud Profiles
+
+### Role Permissions
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+### Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+#### Create a Terraform Profile
+
+##### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+##### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+### Key/Value Store Profiles
+
+- Key/Value Profiles (Key/Value Store) expand provisioning, automation, billing and reporting capabilities by allowing dynamic custom object specific metadata in provisioning and automation mappings
+- Key/Value Profile entries are available using `<%=cloud.profile.key%>`
+- Terraform Profiles are limited to one Profile per Cloud, however multiple key/value pairs can be added to a single profile
+
+#### Create a Key/Value Profile
+
+##### Procedure
+
+1. Navigate to `/infrastructure/clouds/` and select a Cloud
+2. Select the `Profiles` tab
+3. Select + ADD PROFILE
+4. Select Key/Value Profile Type
+5. Enter key/value entries, selecting + to add additional entries
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..0108003
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 335,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..402a4ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json b/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
new file mode 100644
index 0000000..ae0a0ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+  "title": "OpenSearch Configuration",
+  "ordinal": 11,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html",
+  "topic_cluster": {
+    "clustering_title": "OpenSearch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md b/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
new file mode 100644
index 0000000..ab74f81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
@@ -0,0 +1,496 @@
+# OpenSearch Configuration
+
+Starting with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. All HPE Morpheus VM Essentials Software versions already use OpenSearch — this change only affects HPE Morpheus Enterprise appliance upgrades. Hewlett Packard Enterprise continues to support both Elasticsearch and OpenSearch for external clusters.
+
+During upgrade, the reconfigure process will:
+
+- Automatically disable the old Elasticsearch service
+- Start OpenSearch in its place
+- Migrate the Elasticsearch PKCS12 CA to PEM format if `secure_mode` is enabled
+
+No changes to /etc/morpheus/morpheus.rb are required. Existing `elasticsearch[...]` settings are bridged to the `opensearch` namespace automatically (see Notes for details on key precedence).
+
+Data (indices) must be migrated separately using `morpheus-ctl migrate-elasticsearch` (see upgrade sections below, or run `morpheus-ctl migrate-elasticsearch help` on an appliance after upgrade for more info).
+
+## What the settings control
+
+| Setting | opensearch.yml | Purpose |
+| --- | --- | --- |
+| `enable` | — | Enable/disable the embedded OpenSearch service. Set to `false` when using an external cluster. Default `true`. |
+| `es_hosts` | `cluster.initial_master_nodes`, `discovery.seed_hosts` | Cluster membership and discovery. For external clusters, lists the external hosts. |
+| `node_name` | `node.name` | Unique name for this node within the cluster. |
+| `host` | `network.host` or `network.bind_host` | Interface to bind to. Default `127.0.0.1`. Set to `0.0.0.0` for cluster use. |
+| `publish_ip` | `network.publish_host` | The IP other nodes use to reach this node. Falls back to Ohai's `node['ipaddress']` if not set. |
+| `secure_mode` | `plugins.security.disabled: false`, TLS config | Enables TLS on HTTP and transport layers, generates certs, runs securityadmin.sh. |
+| `cluster` | `cluster.name` | Cluster name. Defaults to `morpheus`. Must be the same on all nodes. |
+| `use_tls` | — | Connect to OpenSearch over HTTPS. Automatically set to `true` when `secure_mode` is enabled on the embedded service. Set manually for external TLS clusters. |
+| `auth_user` | — | Username for Morpheus to authenticate with OpenSearch. Used for external clusters. When nil and `secure_mode` is enabled, the auto-created `morpheus` internal user is used. |
+| `auth_password` | — | Password for `auth_user`. Used for external clusters. |
+| `replica_count` | `numberOfReplicas` | Number of index replicas. Default `1`. Set to `0` for single-node deployments. |
+| `admin_dn` | `plugins.security.authcz.admin_dn` | Distinguished name for the admin certificate. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+| `nodes_dn` | `plugins.security.nodes_dn` | Distinguished name for trusted node certificates. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+
+## Ports
+
+For embedded clusters, ensure the following ports are open between all cluster nodes:
+
+- **9200** — HTTP (client queries)
+- **9300** — Transport (inter-node communication and cluster formation)
+
+## Notes
+
+- You can use either `elasticsearch[...]` or `opensearch[...]` keys in morpheus.rb. The `elasticsearch` keys are bridged to `opensearch` automatically. If the same key is set under both namespaces, the `opensearch[...]` value takes precedence.
+- The reconfigure strips `127.0.0.1` from `es_hosts` when more than one host is present, so you don't need to exclude it.
+- In secure mode, `admin_dn` and `nodes_dn` default to `O=Morpheus,OU=Ops,CN=<node_name>` and are set automatically per node. These only need to be overridden when using custom certificates (see below).
+
+## Custom certificates (admin\_dn and nodes\_dn)
+
+When using your own certificates instead of the auto-generated ones, set `admin_dn` and `nodes_dn` to match the subject DN of your certificates. These values map to `plugins.security.authcz.admin_dn` and `plugins.security.nodes_dn` in opensearch.yml.
+
+- `admin_dn` — Identifies the certificate authorized to run administrative operations (e.g., `securityadmin.sh`). Only requests signed by a certificate matching this DN can modify the security index.
+- `nodes_dn` — Identifies certificates trusted for inter-node transport communication. Nodes will reject transport connections from certificates that don't match.
+
+To extract the subject DN from an existing certificate:
+
+```
+```
+openssl x509 -in /path/to/cert.pem -noout -subject -nameopt RFC2253
+```
+```
+
+Set the values in /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['admin_dn'] = 'CN=admin,OU=MyTeam,O=MyOrg'  
+opensearch['nodes_dn'] = 'CN=node,OU=MyTeam,O=MyOrg'
+```
+```
+
+If the admin and node certificates share the same DN (common when a single wildcard or shared cert is used), both values can be set to the same string. With the default auto-generated certificates, these are set to `O=Morpheus,OU=Ops,CN=<node_name>` per node and do not need to be configured manually.
+
+## Setting the HPE Morpheus Enterprise user password
+
+When `secure_mode` is enabled, reconfigure creates an internal OpenSearch user named `morpheus` that HPE Morpheus Enterprise uses to authenticate with OpenSearch. The password for this user is auto-generated and stored in /etc/morpheus/morpheus-secrets.json under the `elasticsearch.morpheus_password` key. No manual configuration is needed in the default case.
+
+To set a custom password, add it to /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['morpheus_password'] = 'my-custom-password'
+```
+```
+
+## Encrypting the password
+
+Passwords in morpheus.rb can be stored in encrypted form using the `ENC{...}` wrapper. During reconfigure, the recipe detects the `ENC` prefix and decrypts the value automatically. Plaintext values are used as-is.
+
+To generate an encrypted string:
+
+```
+```
+morpheus-ctl get-crypto-string string 'my-custom-password'
+```
+```
+
+This outputs an encrypted value that can be used in morpheus.rb:
+
+```
+```
+opensearch['morpheus_password'] = 'ENC{aBcDeFgHiJkLmNoPqRsTuVwXyZ...}'
+```
+```
+
+The encryption uses the appliance's `encryption_key_suffix` (from /etc/morpheus/morpheus-secrets.json), so the encrypted value is specific to that appliance. All nodes in the cluster share the same secrets file contents, so the same encrypted string works on all nodes.
+
+Any password setting in morpheus.rb supports this format (under either the `opensearch[...]` or `elasticsearch[...]` namespace), including `morpheus_password` and `auth_password`. As with other settings, `opensearch[...]` takes precedence over `elasticsearch[...]` if both are set.
+
+## Single Node
+
+A single-node setup uses the embedded OpenSearch service with default settings. No morpheus.rb changes are required unless enabling secure mode.
+
+## Single Node — Fresh Install
+
+The embedded OpenSearch service starts automatically after the initial reconfigure. No configuration is needed:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+To enable secure mode, add to /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['secure_mode'] = true
+```
+```
+
+## Single Node — Upgrading from Elasticsearch
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new HPE Morpheus Enterprise package. Do **NOT** run reconfigure yet.
+
+**Step 2 — Export data**
+
+After upgrading the package (but before reconfigure), export Elasticsearch data. The old Elasticsearch binary is preserved in the new package to allow this:
+
+```
+```
+morpheus-ctl migrate-elasticsearch export --dir /var/opt/morpheus/es-migration
+```
+```
+
+**Step 3 — Reconfigure**
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The old Elasticsearch service is disabled automatically and OpenSearch starts in its place. If `secure_mode` was enabled, the Elasticsearch PKCS12 CA is automatically migrated to PEM format.
+
+**Step 4 — Import data**
+
+```
+```
+morpheus-ctl migrate-elasticsearch import --dir /var/opt/morpheus/es-migration
+```
+```
+
+This strips Elasticsearch-specific `_type` metadata from the exported data and bulk-imports it into OpenSearch.
+
+**Step 5 — Cleanup (optional)**
+
+After verifying the data is intact, migrate-elasticsearch will present the option to remove the old Elasticsearch files. This can also be done manually:
+
+```
+```
+rm -rf /opt/morpheus/embedded/elasticsearch-*  
+rm -rf /var/opt/morpheus/elasticsearch-*  
+rm -rf /var/opt/morpheus/es-migration
+```
+```
+
+## 3-Node Embedded Cluster
+
+## 3-Node Embedded Cluster — Prerequisites
+
+**Networking**
+
+- All 3 nodes must be able to reach each other on:
+
+  - **Port 9200 (TCP)** — HTTP API (client queries, health checks)
+  - **Port 9300 (TCP)** — Transport (inter-node communication, cluster formation, shard replication)
+- Each node needs a stable, routable IP address or resolvable hostname that the other nodes can reach (no NAT between nodes)
+- Both IP addresses and hostnames are supported in `es_hosts` and `publish_ip`
+
+**Configuration**
+
+- Each node must have:
+
+  - The same `es_hosts` hash listing all 3 nodes
+  - A unique `node_name`
+  - A unique `publish_ip` matching that node's routable IP
+  - `host` set to `0.0.0.0` (default `127.0.0.1` only listens locally and will not allow cluster formation)
+- All nodes must share the same `cluster` name (defaults to `morpheus` — only set this if you need to change it)
+
+**Secure Mode**
+
+- When `secure_mode` is enabled, TLS is used on both HTTP and transport layers
+- All nodes must share the **same root CA** — Node 1 must be reconfigured first to generate the CA, then the CA files are copied to the remaining nodes before their first reconfigure
+- Each node auto-generates its own node certificate signed by the shared CA
+
+**Example nodes:**
+
+- Node 1: `10.0.0.1` (morpheus-1)
+- Node 2: `10.0.0.2` (morpheus-2)
+- Node 3: `10.0.0.3` (morpheus-3)
+
+## Fresh Install — Without Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+**Node 1** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'
+```
+```
+
+**Node 2** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'
+```
+```
+
+**Node 3** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'
+```
+```
+
+**Apply**
+
+Run on all three nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Nodes can be reconfigured in any order. The cluster will form once all nodes are up and can reach each other on ports 9200 and 9300.
+
+## Fresh Install — With Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Secure mode enables TLS on both the HTTP and transport layers. Each node generates its own node certificate, but all nodes must share the **same root CA** so they trust each other.
+
+**Step 1 — Configure and reconfigure Node 1 first**
+
+Node 1 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Node 1:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+This generates the root CA and node certificate at:
+
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem
+
+**Step 2 — Copy the root CA to Nodes 2 and 3**
+
+Copy both CA files from Node 1 to the same path on Nodes 2 and 3 **before** running reconfigure on them:
+
+```
+```
+# From Node 1:  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node3:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node3:/opt/morpheus/embedded/opensearch-2.18.0/config/
+```
+```
+
+Set ownership on Nodes 2 and 3:
+
+```
+```
+chown morpheus-es:morpheus-es /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca*.pem
+```
+```
+
+**Step 3 — Configure and reconfigure Nodes 2 and 3**
+
+Node 2 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'  
+opensearch['secure_mode'] = true
+```
+```
+
+Node 3 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Nodes 2 and 3:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Each node will skip CA generation (the files already exist) and generate its own node certificate signed by the shared CA.
+
+## Upgrading from a 3-Node Elasticsearch Cluster
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on all 3 nodes. Do **not** run reconfigure yet.
+
+**Step 2 — Export data**
+
+After upgrading the package (but before reconfigure), export Elasticsearch data on **one node** (the data is cluster-wide). The old Elasticsearch binary is preserved in the new package to allow this:
+
+```
+```
+morpheus-ctl migrate-elasticsearch export --dir /var/opt/morpheus/es-migration
+```
+```
+
+This will:
+
+- Query all available indices and their sizes
+- Prompt you to select which indices to export (or export all)
+- Verify sufficient disk space (requires ~2x index size for JSON format)
+- Write each index as a JSON file to the export directory
+
+**Step 3 — Reconfigure**
+
+**Without secure mode** — No special ordering is required. Run on all 3 nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The old Elasticsearch service is disabled automatically and OpenSearch starts in its place. The existing morpheus.rb cluster settings (`es_hosts`, `node_name`, `host`, `publish_ip`) carry over unchanged.
+
+**With secure mode** — No special ordering is required. The existing Elasticsearch cluster already shares a single CA via the PKCS12 truststore on each node. During reconfigure, each node independently extracts the same CA from its local truststore and uses it to generate its OpenSearch node certificate.
+
+Run on all 3 nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+On each node, the recipe will:
+
+- Detect the old PKCS12 truststore at /var/opt/morpheus/elasticsearch\*/local/elastic-stack-ca.p12
+- Extract the shared CA certificate and key to PEM format (root-ca.pem and root-ca-key.pem)
+- Generate a new OpenSearch node certificate signed by the migrated CA
+- Disable the old Elasticsearch service
+
+It is assumed existing Elasticsearch clusters use the same CA. When all nodes extract the same CA, they will trust each other's certificates and form a cluster without any manual certificate copying.
+
+**Step 4 — Import data**
+
+Once all 3 nodes are reconfigured and the OpenSearch cluster is formed, import the data on **one node**:
+
+```
+```
+morpheus-ctl migrate-elasticsearch import --dir /var/opt/morpheus/es-migration
+```
+```
+
+This strips Elasticsearch-specific `_type` metadata from the exported data and bulk-imports it into OpenSearch.
+
+**Step 5 — Cleanup (optional)**
+
+After verifying the data is intact in OpenSearch, migrate-elasticsearch will present the option to remove the old Elasticsearch files. This can also manually be done on the other nodes with:
+
+```
+```
+rm -rf /opt/morpheus/embedded/elasticsearch-*  
+rm -rf /var/opt/morpheus/elasticsearch-*  
+rm -rf /var/opt/morpheus/es-migration
+```
+```
+
+## External Cluster
+
+When using an externally managed OpenSearch (or Elasticsearch) cluster, disable the embedded service and point Morpheus at the external hosts.
+
+## External Cluster — Fresh Install
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Add the following to /etc/morpheus/morpheus.rb on each Morpheus appliance node:
+
+```
+```
+opensearch['enable'] = false  
+opensearch['es_hosts'] = {'os-node1.example.com' => 9200, 'os-node2.example.com' => 9200, 'os-node3.example.com' => 9200}  
+opensearch['auth_user'] = 'morpheus'  
+opensearch['auth_password'] = 'the-external-cluster-password'
+```
+```
+
+If the external cluster uses TLS:
+
+```
+```
+opensearch['use_tls'] = true
+```
+```
+
+Then reconfigure:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The embedded OpenSearch service will not be started. Morpheus will connect directly to the external cluster using the provided hosts and credentials.
+
+- `auth_user` and `auth_password` are sent to the external cluster for authentication. These must match a user configured on the external cluster.
+- `auth_password` supports the `ENC{...}` encrypted format (see Encrypting the password).
+- Do not set `secure_mode` — that setting controls the embedded service's certificate generation and security plugin. For external TLS clusters, use `use_tls` instead.
+- `replica_count` can be adjusted to match the external cluster's topology (default `1`).
+
+## Upgrading with an External Cluster
+
+If the existing Morpheus installation was already configured to use an external Elasticsearch or OpenSearch cluster, the upgrade is straightforward — no data migration is needed on the appliance side since the data lives on the external cluster. The external cluster does not need to be migrated to OpenSearch; Morpheus supports both.
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on each appliance node.
+
+**Step 2 — Reconfigure**
+
+No morpheus.rb changes are needed. The existing `elasticsearch[...]` settings are bridged automatically.
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.json b/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.json
new file mode 100644
index 0000000..a3c3261
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+  "title": "Security Packages",
+  "ordinal": 162,
+  "parent_title": "Templates",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-ED404402-F168-4635-ADEB-02609465196E.html",
+  "topic_cluster": {
+    "clustering_title": "Security Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.md b/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.md
new file mode 100644
index 0000000..143b1b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-ED404402-F168-4635-ADEB-02609465196E.md
@@ -0,0 +1,20 @@
+# Security Packages
+
+The Security Packages Section is for uploading SCAP packages which can then be consumed in Security Scan Jobs (Provisioning > Jobs).
+
+## Add a new Security Package
+
+### Procedure
+
+1. Navigate to Library > Templates > Security Packages
+2. Click +ADD > SCAP Package
+3. Provide a name in addition to a URL to source the package
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Currently URL is the only source option for security packages
+
+![../../_images/1add_package.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-8BD09052-92FA-4310-AE20-7EF52079B937-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json b/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
new file mode 100644
index 0000000..d2254af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+  "title": "Creating a Datastore",
+  "ordinal": 440,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md b/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
new file mode 100644
index 0000000..5a01c15
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
@@ -0,0 +1,19 @@
+# Creating a Datastore
+
+## About this task
+
+This procedure guides you through creating a Datastore. The datastore acts as a container for volumes and must be created before volumes can be created.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > DataStores.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage Baremetal for type, select your cloud, the storage server previously created, FC as the protocol type, and the Resource Pool that applies to this storage server.
+5. Click the Save to create the DataStore.   
+   ![Add Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4455C3A5-99BD-49B4-86A3-C2CB67FDD579-high.png)
+
+## Results
+
+The added data store appears under Data Store.   
+![Data Store](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-A1A160B8-E303-4B49-85E6-20044732C34B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json b/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
new file mode 100644
index 0000000..979c9a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+  "title": "CloudFormation Blueprints",
+  "ordinal": 133,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html",
+  "topic_cluster": {
+    "clustering_title": "CloudFormation Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md b/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
new file mode 100644
index 0000000..680a6bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
@@ -0,0 +1,46 @@
+# CloudFormation Blueprints
+
+CloudFormation Blueprints consume new or existing CloudFormation templates to create easily-deployable application stacks. CloudFormation templates in HPE Morpheus Enterprise are JSON or YAML-formatted text documents that declare all relevant AWS resources needed for the provisioned application. They can be created directly in the New Blueprint modal or pulled in from existing Git repositories.
+
+If needed, Amazon has educational resources available for getting started with CloudFormation. They can be found in the [AWS CloudFormation documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html).
+
+To create a new CloudFormation Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select CloudFormation. Click NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+In some cases, you must explicitly acknowledge that your template contains certain capabilities in order for the application to successfully be deployed. There is more information on this in Amazon’s documentation [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html). If any of the following capabilities are contained in your application, acknowledge them by marking any of the following boxes that apply:
+
+- **CAPABILITY\_IAM**
+- **CAPABILITY\_NAMED\_IAM**
+- **CAPABILITY\_AUTO\_EXPAND**
+
+Continuing on with the CloudFormation Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “CloudFormation Template JSON (.json)”
+- **CONFIG TYPE:** “CloudFormation Template YAML (.yaml)”
+- **CONFIG:** Enter your configuration here
+
+In the CloudFormation Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new CloudFormation Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..ab4737c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 337,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..c48371c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json b/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
new file mode 100644
index 0000000..b8c9a2d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+  "title": "IBM Cloud",
+  "ordinal": 459,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F003BCEE-0E64-412A-9045-295910E15A5A.html",
+  "topic_cluster": {
+    "clustering_title": "IBM Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md b/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
new file mode 100644
index 0000000..ab7cb7a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
@@ -0,0 +1,133 @@
+# IBM Cloud
+
+IBM Cloud offers a wide set of cloud computing services including compute, storage, database, networking, and more. It is deployed in data centers across the world and its services can scale to meet the needs of small development teams as well as large-scale enterprises. HPE Morpheus Enterprise integrates with IBM Cloud to offer virtual machine provisioning, brownfield discovery, and lifecycle management.
+
+## Integrating IBM Cloud with HPE Morpheus Enterprise
+
+### About this task
+
+Connecting an IBM Cloud account with HPE Morpheus Enterprise is a simple process requiring only an API key. You can create an API key from the IBM Cloud web console if you don’t currently have access to one. Integrating with HPE Morpheus Enterprise requires a user API key. If needed, create one by clicking “Manage” in the upper menu bar of the IBM Cloud web console and clicking “Access (IAM)”. Select “Users” from the left navigation menu and click on the desired user. Create a new API Key from within the API Keys section and store the API Key in a secure place to retrieve in the next step. It’s recommended that you integrate HPE Morpheus Enterprise using an IBM Cloud admin account to ensure you won’t run into any blockers while working in HPE Morpheus Enterprise. Using HPE Morpheus Enterprise role-based access you can limit which IBM Cloud constructs and capabilities are accessible to your users.
+
+With the API key created, head back to HPE Morpheus Enterprise and continue with the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Click + ADD
+3. Complete the following required fields:
+
+### Results
+
+- **NAME:** A friendly name for the cloud inegration in HPE Morpheus Enterprise
+- **USERNAME:** Enter “apikey” (Do not enter your IBM Cloud username or anything other than “apikey”)
+- **API Key:** The API key value
+- **DATACENTER:** Select the IBM Cloud data center
+- **OBJECT STORE:** If desired and if any are found, select an object store
+
+1. Click NEXT
+2. Select a Group for this Cloud or create a new one if desired
+3. Complete the wizard to save the new integration
+
+![../../../_images/1createCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-55120133-3640-459B-B4C4-796C4CC5C741-high.png)
+
+Once the wizard has completed, the new IBM Cloud integration will appear alongside other Clouds currently available in HPE Morpheus Enterprise. If you’ve selected to automatically onboard existing resources, those will appear shortly.
+
+IBM Cloud integrations also support a number of advanced options which were not discussed as part of the initial integration set up discussed above. For more information on the advanced options, consult the section below.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json b/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
new file mode 100644
index 0000000..69e6125
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+  "title": "Overview",
+  "ordinal": 280,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md b/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
new file mode 100644
index 0000000..0234f78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on any Tenant detail page (Administration > Tenants > Selected Tenant) or on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in HPE Morpheus Enterprise so at first log in users are assigned the appropriate role.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json b/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
new file mode 100644
index 0000000..9b58be5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+  "title": "Service Catalog Persona",
+  "ordinal": 340,
+  "parent_title": "Personas",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html",
+  "topic_cluster": {
+    "clustering_title": "Service Catalog Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md b/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
new file mode 100644
index 0000000..d70c858
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
@@ -0,0 +1,53 @@
+# Service Catalog Persona
+
+The Service Catalog Persona presents a simplified catalog where users can select and deploy Instances or Blueprints with pre-defined configuration with just a few clicks and without presenting an overwhelming list of options.
+
+## Configuring Catalog Item Access
+
+Within the Service Catalog Persona, users are presented with Catalog Items based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items (and no access to the Service Catalog Persona). When enabling Service Catalog Persona access for User Roles, you will also need to give access to some or all Catalog Items.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Dashboard
+
+The default page for the Service Catalog Persona is the Dashboard. The Dashboard shows a selection of featured catalog items, a listing of the last few items the user has ordered, and a selection from the user’s inventory.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-98CB46CB-C852-48BE-8F39-09E5E676BCCE-high.png)
+
+## Catalog
+
+The catalog shows the complete list of pre-defined catalog items available to the user for provisioning. Catalog items are not created in the Service Catalog Persona. For more on creating catalog items, see the [Self Service section](https://docs.morpheusdata.com/en/latest/tools/self-service.html) (Tools > SelfService) of HPE Morpheus Enterprise docs.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-782B5419-8EEF-4E93-A621-974E15760B4A-high.png)
+
+## Inventory
+
+The Inventory Page reveals the complete list of items which have been ordered by the user and provisioned. Users will only see their own items in this section.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-BA083368-6AF1-4E7D-A035-B175C86AED03-high.png)
+
+## Inventory Detail
+
+Access the detail page for an item in your inventory by clicking the View Details link. The page displayed will look very similar to an Instance or App detail page in the Standard Persona. Highly detailed information on the health of the Instance or App are shown here. We can also take actions against Instances such as running Tasks or Workflows, reconfiguring the Instance, controlling the power state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-193E867C-87CF-49A6-B994-AC2CEE9B6D08-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-B4E37C64-41C3-4CF9-8D36-47260212AEC6-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Click “Review Order”. When reviewing your order, each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-6A53CB8B-6B6D-40A5-AEB3-AF96A7D8917B-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can be viewed in Inventory and additional details can be accessed through the Inventory item detail page.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json b/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
new file mode 100644
index 0000000..e881044
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+  "title": "Overview",
+  "ordinal": 287,
+  "parent_title": "Plans",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md b/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
new file mode 100644
index 0000000..47efcc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
@@ -0,0 +1,9 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from HPE Morpheus Enterprise, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to HPE Morpheus Enterprise-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance.
+
+Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time. Price sets are associated with plans, which is how HPE Morpheus Enterprise can compute cost values even for Instances running in private, on-prem Clouds.
+
+The Plans & Pricing section is where Plans, Prices Sets and Prices are managed. These concepts are associated with each other in the following way: Prices are added to Prices Sets, and Price Sets are added to Plans. Plans include Service Plans, Load Balancer Price Plans, Virtual Image Prices Plans and Snapshot Price Plans. Price sets can be agnostic and available for any Plan, or specific to a Region Code, Cloud or even a specific Resource Pool. Prices are configured per Price Type and can be added to Price Set configurations that support the Price Type. Master Tenant Prices can apply to all Tenants or be assigned to a single Tenant.
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json b/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
new file mode 100644
index 0000000..1625375
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+  "title": "Microsoft DNS",
+  "ordinal": 484,
+  "parent_title": "DNS",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html",
+  "topic_cluster": {
+    "clustering_title": "Microsoft DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md b/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
new file mode 100644
index 0000000..9c25dee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
@@ -0,0 +1,328 @@
+# Microsoft DNS
+
+The HPE Morpheus Enterprise Microsoft DNS integration is developed as an official plugin separate from the core product. It is easily added and uploaded to any HPE Morpheus Enterprise appliance. Download the plugin from the official plugin repository <share.morpheusdata.com > \_ and add it to the appliance from the plugin management UI section (Administration > Integrations > Plugins).
+
+The MSDSN integration automates DNS record creation and DNS record cleanup both manually or automatically during workload provisioning to a configured Cloud or Group. It should be noted that this integration is typically not needed when joining a Windows VM to an Active Directory Domain as typically this automatically creates a DNS record.
+
+## Prepare DNS Server(s)
+
+NOTE
+
+This section will assume a the DNS server is in an Active Directory environment and joined to the domain. The process may be different for other configurations.
+
+The easiest method to prepare DNS server(s) is to use a service account that is added to the `DnsAdmins` and `Remote Management Users` groups, either in Active Directory (if DNS is on domain controllers) or the local groups of a member server. The `DnsAdmins` group will provide permissions for the service account to make DNS changes, such as creating/deleting A and PTR records. The `Remote Management Users` group will allow HPE Morpheus Enterprise to connect to the server(s) via WinRM.
+
+Additionally, ensure firewall rules have been updated if needed to allow WinRM through. In some cases, the default WinRM rules allow `Private` and `Domain` networks but not `Public`. Enable `Public` if the network HPE Morpheus Enterprise is connected is considered `Public`, or disable the firewall if permitted. If a jump box is required (discussed below), then ensure the firewall is configured to allow the jump box to connect to the DNS server instead.
+
+Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+### Minimum Permissions
+
+Some organizations may require that users cannot be added to the `DNSAdmin` group, mentioned previously. If this is a requirement, the following process/permissions would be required to ensure HPE Morpheus Enterprise can connect successfully. This process may be required on each DNS server, depending on the environment. Note that if HPE Morpheus Enterprise adds additional functionality at a later time, these permissions may need to be updated to support those features.
+
+- Run `dnsmgmt.msc`
+- Right-click the DNS server object and choose `Properties`
+- Add the service account to the user list and ensure the following permissions are applied:
+
+  - Read
+  - Create all child objects
+  - Delete all child objects
+- Run `wmimgmt.msc`
+- Right-click `WMI Control (Local)` and choose `Properties`
+- Click the `Security` tab
+- Set the following permissions for each of the below nodes:
+
+  - `CIMV2`
+  - `MicrosoftDNS`
+  - `Microsoft => Windows => DNS` (only the DNS node)
+- Hightlight the node and click the `Security` button
+- Click the `Advanced` button
+- Click the `Add` button to add the service account to the list
+- Ensure the `Applies to` field is set to `This namespace and subnamespaces`
+- Set the following permissions:
+
+  - Enable Account
+  - Remote Enable
+  - Execute Methods
+- Finally, restart Windows Management Instrumentation Service or the server. This is required for the change in permissions to take place.
+
+Additional support reference: <https://support.morpheusdata.com/s/article/How-to-give-C?language=en_US>
+
+## (Optional) Prepare Jump Box
+
+In some environments, HPE Morpheus Enterprise may not be allowed to access the DNS servers directly, as they may be on segregated networks. In this case, HPE Morpheus Enterprise can utilize a member server as a “jump box” that can access the DNS servers directly, the jump box will be used to interact with the DNS server instead. If this is a requirement, follow the below process to prepare the jump box.
+
+- Add the service account to the `Remote Management Users` group of the jump box, which will allow WinRM to access
+- Verify the firewall allows WinRM from HPE Morpheus Enterprise
+- Create or edit the following registry key by running `regedit`:
+
+  - Navigate to: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb`
+  - Create or edit `ProtectionPolicy` DWORD (32-bit) Value
+  - Set `ProtectionPolicy` value to `1`
+- Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+## Adding a Microsoft DNS integration
+
+For appliances with the MSDNS plugin installed, the option to create an integration is available. Navigate to Administration > Integrations and click + NEW INTEGRATION to create a new one.
+
+- **NAME:** A friendly name for the integration in HPE Morpheus Enterprise
+- **RPC SERVER** Enter the name of the server brokering access to the Microsoft DNS Services. This is the Windows server HPE Morpheus Enterprise will connect to directly. In most cases, the RPC SERVER will be a Windows domain-joined server with the DNS Server tools installed. HPE Morpheus Enterprise will use this server to connect and manage DNS
+- **RPC PORT:** This configuration is visible if “USE AGENT FOR RPC” is unmarked. The WinRM port number 5985/5986, default is 5985
+- **USE AGENT FOR RPC:** Select this option to have the plugin use a configured agent to handle the HPE Morpheus Enterprise to Windows RPC connection. The RPC SERVER should be an Instance (in other words, a managed VM) which is part of the same HPE Morpheus Enterprise environment where the integration is added. The HPE Morpheus Enterprise Agent must also be configured to logon as the DNS Service user account. In most cases, customers would only use this option when using an intermediate server to access DNS services
+- **CREDENTIALS:** Provide account credentials for a service account. You may use credentials already stored in HPE Morpheus Enterprise or create new Username/Password credentials
+- **DNS SERVER:** If the RPC SERVER is not the server hosting DNS Services, then add the FQDN name of the DNS server here. Leave blank if the RPC SERVER is also the DNS Server
+- **ZONE FILTER:** The ZONE FILTER is a comma separated list of glob-style filters which can be used to specify the zones that HPE Morpheus Enterprise will import and sync. Glob style filters apply to the zone name only and at a domain level. The `\*` character matches any legal DNS character [-] 0 or more times. Wildcarding stops at the . (period), leave blank to import all forward and reverse zones
+- **SERVICE TYPE:** This configuration is visible if the DNS SERVER is not blank. This option informs the plugin how the RPC SERVER should contact the DNS SERVER. There are 3 supported options: **local** when the RPC SERVER is the DNS Server (ie when DNS SERVER is blank in which case local is the default and only option), **wmi** which is used when the RPC SERVER contacts the DNS Server over WMI (Windows RPC, this is the recommended and default option when using an intermediate RPC SERVER), and **winrm** which is used when the RPC SERVER connects to DNS SERVER over a WinRM session (this is not often used due to WinRM restrictions on domain controllers)
+- **INVENTORY EXISTING:** Have the integration import and sync all DNS records for the matching Zones. Using this option is not recommended for installations with large namespaces
+- **CREATE POINTERS:** Have DNS create a PTR record when the forward record is created
+
+NOTE
+
+If you’re not using an intermediate server, the RPC SERVER will also be the DNS Server. The HPE Morpheus Enterprise Windows Agent should be set to log in using these credentials.
+
+## Domains
+
+Once the integration is added, Microsoft DNS Domains will sync and listed under Infrastructure > Network > Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Infrastructure > Network > Domains
+
+## Configuring Microsoft DNS with Clouds and Groups
+
+DNS Integrations are available in the `DNS Integration` dropdown in Cloud and Group settings. HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the `Advanced Options` section.
+3. In the `DNS Integration` dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the `Edit` button for the Group
+3. Expand the `Advanced Options` section.
+4. In the `DNS Integration` dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
+
+## Using Zone Filters
+
+In this example a ZONE FILTER string of
+
+`*.morpheus.com, *.10.in-addr.arpa, d*.us.morpheus.com`
+
+would
+
+**IMPORT**`test.morpheus.com, prod.morpheus.com` but **NOT** `mydomain.test.morpheus.com` which has a 4th level
+
+**IMPORT**`32.10.in-addr.arpa, 33.10.in-addr.arpa` but **NOT** `12.11.in-addr.arpa` or `10.in-addr.arpa` (which has 3 levels)
+
+**IMPORT**`denver.us.morpheus.com` and `delaware.us.morpheus.com` but **NOT** `ohio.us.morpheus.com` (wildcard at 4th level)
+
+## Improved Integration Validation
+
+Recent versions of this integration have improved the error handling and validation. RPC connectivity and access to DNS Services is tested at the time the integration dialog is saved. The dialog will not save unless validation is passed successfully. The integration dialog will hint where problems occur but you should check the HPE Morpheus Enterprise Health logs (Administration > Health > Morpheus Logs) to see detailed messages.
+
+TIP
+
+To force the integration to save you can uncheck the ENABLED checkbox. Doing this disables the validation testing allowing you to save the integration dialog contents and perform troubleshooting without having to reenter configurations. When the issue is resolved, edit the integration and set the integration to ENABLED. Validation will then be performed on the save.
+
+## Custom Powershell Module Script
+
+Recent versions of this integration include a custom Powershell Module script (.ps1 file) which is maintained by the plugin and transferred to the RPC SERVER when the integration is added. The Powershell script file contains functions designed to handle the interface between Morpheus and DNS. The script uses the standard Windows DNS-Server module (Windows feature RSAT-DNS-Server). The script file is MD5 checked each time the integration syncs and the module is refreshed from the plugin if the checksum fails. The custom script is stored in the **%LOCALAPPDATA%** folder for the integration service account user.
+
+The module contains custom functions designed to interface with the MSDNS plugin via JSON.
+
+- Having the Powershell module installed on the RPC SERVER offers some performance benefits as HPE Morpheus Enterprise now can call on the modules functions to perform tasks
+- The Powershell functions test RPC connectivity and DNS service connectivity on each sync refresh ensuring the integration is healthy
+- The module uses a standard JSON interface between Windows RPC SERVER and HPE Morpheus Enterprise
+- The module overcomes restrictions imposed on HPE Morpheus Enterprise WinRM connections authenticating with NTLM
+
+IMPORTANT
+
+For version 2.1.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v32.ps1` and for version 2.3.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v34.ps1`. The HPE Morpheus Enterprise health logs will log the status of the HPE Morpheus Enterprise Powershell file on each refresh. For example: `INFO c.m.m.MicrosoftDnsPluginHelper - testHelperFileScript - Checking for valid Helper script fileName: morpheusDnsPluginHelper_v32.ps1 - MD5: 698d8e6ad0bf7f64d9e9ccac962e4ab1`
+
+## Secure credential cache file
+
+The HPE Morpheus Enterprise Powershell functions use a technique where script blocks are executed with Invoke-Command passing a credential object. This effectively creates a new session from RPC SERVER using kerberos overcoming the restrictions imposed by Windows on the original Morpheus NTLM connection. Credentials are cached using the Windows Data Protection API meaning only the user account who created the credential can decrypt it and only on the original Windows server. The credential cache is stored in `%LOCALAPPDATA%\S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` where `S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` is the Service Account SID.
+
+NOTE
+
+If “USE AGENT FOR RPC” is checked, there is no need to create a new session since the original session is already Kerberos, however the credentials are still cached.
+
+## Troubleshooting Connections
+
+### Service Account Requirements
+
+The service account used to access DNS via the plugin must meet the following requirements:
+
+- If using an intermediate server as the RPC SERVER, the service account should be a member of local `administrators` group on the RPC SERVER
+- If “USE AGENT FOR RPC” is checked, the HPE Morpheus Enterprise Windows Agent service must be configured to login as the service account. The service account will require `Log on as a Service` rights in the RPC SERVER local policy
+- If not using an intermediate server, the service account must be a member of `Remote Management Users` on the RPC SERVER as a minimum in order to access the RPC SERVER from HPE Morpheus Enterprise via WinRM. Membership of `administrators` however, is recommended
+- The service account must be a member of the domain global group `DNS Admins`
+- To Access Microsoft DNS WMI namespaces, the service account must be granted access to the DNS WMI classes
+
+### RPC SERVER requirements
+
+When using an intermediate server as the RPC SERVER, the following requirements must be met:
+
+- The RPC SERVER must be a Windows Server which is a member of a domain or forest which is trusted to access the DNS namespace
+- The RPC SERVER must have the Microsoft Windows feature RSAT-DNS-Server installed
+- If planning to “USE AGENT FOR RPC” then the Windows server must have a HPE Morpheus Enterprise Windows Agent installed and this agent must report into the HPE Morpheus Enterprise environment where the DNS Integration is being added or configured. Ideally, HPE Morpheus Enterprise will have deployed the RPC SERVER as an Instance
+- If not planning to “USE AGENT FOR RPC” then the RPC server must have WinRM configured and must be reachable over WinRM from the HPE Morpheus Enterprise appliance
+- When using an intermediate server to access DNS Services, the computer account of the RPC SERVER must be configured for delegation `Trusted for Delegation to any service (Kerberos only)`. Use Active Directory Users and Computers, locate the computer account for RPC SERVER. Click properties and select the Delegation tab and choose the option `Trust this computer for delegation to any service (Kerberos only)`
+
+## Using the plugin test Service page
+
+Recent versions of this integration have the ability to run a connection test via the HPE Morpheus Enterprise appliance. Users must have full access to the Integrations permission to test a Microsoft DNS plugin connection. For example, to test connectivity to an integration with id value of 5, browse to the following URL in HPE Morpheus Enterprise: `https://my.morpheus.appliance/plugin/msdns/service?integrationId=5`
+
+The plugin will run a series of tests using details from the integration dialog.
+
+NOTE
+
+Tests can be run even if the integration ENABLED checkbox is unmarked allowing troubleshooting with the integration offline.
+
+The results are output in the browser in JSON.
+
+In the example below, inspect the `serviceProfile`. Here, the `rpcType` is “agent” so “USE AGENT FOR RPC” is checked and the `serviceType` is “wmi”. The `rpcSession` and `serviceSession` show the connection details, logon types and group membership for the RPC and service sessions. The `dnsServer` section shows the FQDN and version of the DNS server and if populated indicates a successful test (status = 0).
+
+If the test is unsuccessful, a status code other than 0 is returned and any error will be listed in the “Errors” section
+
+```
+```
+Morpheus Microsoft DNS Integration Service Profile  
+Discovered service profile for Microsoft DNS integration : 5  
+Rpc Connection Status true  
+Successful rpc response from spie-mo-w-3011 via agent: Command completed successfully  
+Errors  
+{  
+}  
+Rpc Output  
+{  
+    "status": 0,  
+    "cmdOut": {  
+        "serviceProfile": {  
+            "rpcHost": "SPIE-MO-W-3011",  
+            "rpcType": "agent",  
+            "serviceHost": "ip-c61302.myad.net",  
+            "serviceType": "wmi",  
+            "useCachedCredential": false  
+        },  
+        "dnsServer": {  
+            "computerName": "IP-C61302.myad.net",  
+            "version": "10.0.17763"  
+        },  
+        "rpcSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "serviceSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "domainSOAServers": {  
+            "nameToQuery": "ip-c61302.myad.net",  
+            "fqdn": "ip-c61302.myad.net",  
+            "dcList": [  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61301.myad.net"  
+                },  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61302.myad.net"  
+                }  
+            ]  
+        }  
+    },  
+    "errOut": null  
+}
+```
+```
+
+## DNS Record validation and Error Handling
+
+- DNS records are now fully validated before they are created. Only record types A, AAAA, CNAME and PTR are currently supported
+- Adding a DNS Record which already exists (ie FQDN and IP address match an existing record in DNS) would normally return an error (code 9711), this is masked to a success to prevent HPE Morpheus Enterprise aborting the provision
+- Removing a HPE Morpheus Enterprise DNS Record that does not exist in DNS (error 9714) is also masked to success to have HPE Morpheus Enterprise delete its copy
+- If a fwd record is created but the PTR record fails (due to missing PTR zone error 9715), this is also masked to success to prevent HPE Morpheus Enterprise aborting the Provision
+- All errors are logged to the HPE Morpheus Enterprise health logs (Administration > Health > Morpheus Logs).
+
+## AWS Directory Services Support
+
+Support is included for AWS Active Directory service.
+
+- Access is only possible via a correctly configured intermediate server (RPC SERVER) hosted in AWS and having the DNS Management Tools installed
+- The DNS SERVER must be the fully qualified name of one of the AWS Domain controllers
+- The Service Account should be a member of AWS Delegated Domain Name System Administrators, AWS Delegated Kerberos Delegation Administrators and AWS Delegated Server Administrators (for access to RPC SERVER)
+- The RPC SERVER computer object should be trusted for delegation for all Kerberos Services on the AWS Directory Service domain controllers. This can be performed using AD Users and Computers to modify the properties of the RPC SERVER Computer object. Right click the computer object, select properties and open the Delegation tab. Select the Radio button `Trust this computer for delegation to any service (Kerberos Only)`. Click OK to Save
+
+NOTE
+
+It is possible to finely tune the delegation so that the RPC SERVER computer object can only delegate to specific services if this is required.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json b/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
new file mode 100644
index 0000000..3ee93c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+  "title": "Reconfiguring Volume",
+  "ordinal": 445,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html",
+  "topic_cluster": {
+    "clustering_title": "Reconfiguring Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md b/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
new file mode 100644
index 0000000..4cdeb59
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
@@ -0,0 +1,19 @@
+# Reconfiguring Volume
+
+## About this task
+
+Reconfiguration allows the user to make changes to volumes consumed by a compute instance post-provisioning. This is achieved through the Reconfigure action on the instance.
+
+New volumes can be created and attached to the compute instance. These can be shared or unshared volumes. Any volume attached to the compute instance can be resized to increase the size of the volume. Any attached volume can be detached. However, volumes cannot be deleted from the Reconfigure action. Volumes can be deleted only from the infrastructure management section.
+
+All these operations work in the context of a compute instance and are not specific to a compute server within the instance.
+
+## Procedure
+
+1. Navigate to Provision > Instance.
+2. Click on the compute instance you want to reconfigure and access the details of the instance.
+3. Click on Actions and select Reconfigure.   
+   ![Action Reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-DE3C1BD1-CF86-4745-BF9D-F88C65D2E407-high.png)
+4. In the Reconfigure wizard, make the changes desired to add a new volume, resize an existing volume or click the trash icon to detach a volume from the instance.   
+   ![Reconfigure Instance](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-12FE7650-4E11-449B-907A-4AB15A132992-high.png)
+5. Click on Reconfigure.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json b/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
new file mode 100644
index 0000000..6bc8233
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+  "title": "Morpheus API & CLI",
+  "ordinal": 526,
+  "parent_title": null,
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus API & CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md b/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
new file mode 100644
index 0000000..6de0d35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
@@ -0,0 +1,4 @@
+# Morpheus API & CLI
+
+- [API Documentation](https://apidocs.morpheusdata.com)
+- [CLI Documentation](https://clidocs.morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json b/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
new file mode 100644
index 0000000..a4bc3af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+  "title": "VMware Support Statement",
+  "ordinal": 52,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Support Statement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md b/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
new file mode 100644
index 0000000..95b085a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
@@ -0,0 +1,18 @@
+# VMware Support Statement
+
+## About this task
+
+Morpheus Data will support customers who run HPE Morpheus Enterprise products on supported operating systems, irrespective of whether they are running in VMware environments or not. Morpheus Data supports operating systems, not specific hardware configurations. Accordingly, VMware operates as a hardware abstraction layer.
+
+VMware supports a set of certified operating systems and hardware. The customer and VMware will be responsible for any interactions or issues that arise at the hardware or operating system layer as a result of their use of VMware.
+
+Morpheus Data will not require clients to recreate and troubleshoot every issue in a non-VMware environment; however, Morpheus Data does reserve the right to request our customers to diagnose certain issues in a native certified operating system environment, operating without the virtual environment. Morpheus Data will only make this request when there is reason to believe that the virtual environment is a contributing factor to the issue.
+
+Any time spent on investigation of problems that may, in the sole opinion of Morpheus Data be related to VMware, will be handled in the following fashion:
+
+## Procedure
+
+1. Morpheus Data will provide standard support to all HPE Morpheus Enterprise products.
+2. If a problem is encountered while HPE Morpheus Enterprise is/are running in a VMware environment, the client may be required to recreate the problem on a non-VMware server unit, at which time Morpheus Data will provide regular support.
+3. The client can authorize Morpheus Data to investigate the VMware-related items at normal time and materials rates. If such investigation shows that the problem is VMware related, the client may contract Morpheus Data to provide a software change to resolve the issue if such a resolution is possible.
+4. Regardless of the problem type or source, if the problem is determined to be a non VMware-related issue, time spent on investigation and resolution will be covered as part of regular maintenance and support will be provided as usual.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json b/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
new file mode 100644
index 0000000..1d116ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+  "title": "Provisioning an Instance",
+  "ordinal": 416,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md b/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
new file mode 100644
index 0000000..66dbbf6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
@@ -0,0 +1,31 @@
+# Provisioning an Instance
+
+## About this task
+
+Perform the following steps to provision an instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.   
+   ![Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-C7BB967B-5DC0-4932-8F24-0AD471BB5430-high.png)
+2. Click the + ADD.
+3. In the TYPE tab, select the Instance Type as HPE Bare Metal (ILO) SERVER.  
+   ![Type](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D8ED39AD-773F-408D-9AC6-075C86E99337-high.png)
+4. In the GROUP tab, complete the Instance Summary fields.  
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-7F89FF6E-7D74-47A0-8C79-7564B839ED39-high.png)
+5. In the CONFIGURE tab, complete the Configuration Options:
+
+   1. Layout: Select the appropriate layout from the drop-down list (for example, Single iLO Server).
+   2. Service Plan: Choose one of the following:
+
+      - Generic Plan: Any iLO
+      - Specific Plan: For example, DL360.Gen10Plus.1-32C.129-256GiB
+   3. Resource Pool: Select the required resource pool from the drop-down list.
+   4. Volumes: Configure storage volumes as required. Refer to the Storage section for details.
+   5. Networks: Configure network settings as required. Refer to the Networking section for details.
+   6. Image: Select the Bare Metal OS image from the drop-down list.
+   7. Baremetal Host(s): Select the target Bare Metal host(s) from the drop-down list if specific server(s) are desired.  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-CC32AE45-9726-469E-B453-4ADF3113B80B-high.png)
+6. In the AUTOMATION tab, select the appropriate options, then click Next.
+7. In the REVIEW tab, verify the configuration summary and click Complete.   
+   ![Review](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-86C9130B-3808-4D68-AD5F-75D408B4B4C8-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json b/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
new file mode 100644
index 0000000..82ce67a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+  "title": "Requirements",
+  "ordinal": 80,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md b/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
new file mode 100644
index 0000000..9c7c833
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
@@ -0,0 +1,231 @@
+# Requirements
+
+Provisioning Instances and Apps typically involves many steps beyond starting a workload. HPE Morpheus Enterprise is centered around automating everything desired for your application to be fully operational, including networking, storage, hostnames, domains, dns, licenses, scripts/automation, scaling, load balancers, security, accessibility, governance, auditing, monitoring, backups, costs, sizing and on and on. Point being there is a lot that goes on when spinning up an instance or app, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Images or SKIP AGENT INSTALL is selected when provisioning.
+
+## VM Provision Steps
+
+While an infinite number of steps can happen when provisioning an Instance or App using VM(s) in HPE Morpheus Enterprise, the basic order is:
+
+- Look for Virtual Image
+
+  HPE Morpheus Enterprise will check if the Virtual Image set on the Node Type or selected during provisioning is already available in the source Cloud. If not and it is an Uploaded/Local Image, HPE Morpheus Enterprise will attempt to upload the Image to the target Cloud.
+
+  **Upload Image**
+
+  For Uploaded/Local Images that do not exist in the target cloud, HPE Morpheus Enterprise will need to upload the Image. Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, HPE Morpheus Enterprise will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, HPE Morpheus Enterprise will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, HPE Morpheus Enterprise will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   HPE Morpheus Enterprise will run Guest Customizations via VMware VM Tools, including network config when assigning static IP’s.
+- Wait for Power On status and Network info
+
+  HPE Morpheus Enterprise will wait to hear back from the target cloud/hypervisor that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, HPE Morpheus Enterprise will skip waiting for network.
+- Finalize
+
+  By default this will include Agent Installation and any post-provision scripts or workflows or integration automation steps.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for longs periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
+
+## Virtual Images
+
+While containers are the future, the most common provisioning method involves Virtual Machines, and the most important part of Provisioning a VM is the Virtual Image. When provisioning a VM, HPE Morpheus Enterprise will need to do a few things depending on the location of the Virtual Image and if agent install, console access, and script execution is desired.
+
+Synced Images need to be properly configured
+:   HPE Morpheus Enterprise gathers as much metadata for synced images as possible, but depending on the cloud, os, image configuration, agent install settings, by default the synced Virtual Images may not be ready to provision until configured. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, and networks and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to HPE Morpheus Enterprise are configured during the Add Virtual Image process, however HPE Morpheus Enterprise in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required and network and image configurations can cause upload failures, resulting in provisioning issues.
+
+Marketplace Images
+:   AWS and Azure marketplace Images can be provisioned using the generic Amazon or Azure Instance Types, or added as Virtual Images as scoped to Node Types for custom Instance Types. Marketplace items provisioned/added to HPE Morpheus Enterprise still fall upon the requirements of the target Cloud, such as matching the region with the Image and licensing.
+
+### Synced Images
+
+When a Cloud is added to HPE Morpheus Enterprise, all available Images/Templates records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These Image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type, ie VMware, Amazon, Azure, Openstack etc Instance Types, or by creating custom Instance Types and selecting the Image on a Node Type.
+
+NOTE
+
+Synced Virtual Images are just meta-data records in HPE Morpheus Enterprise pointing to the Image in the target Cloud. The actual Image files are not copied/imported to HPE Morpheus Enterprise.
+
+Before provisioning a synced Virtual Images, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the Image, but editing will not change the name of the actual Image.
+
+Operating System
+:   Specifies the Platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the Platform for all Images without Operating System specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Service Plans options during provisioning. Service Plans that do not meet the Minimum Memory value set on the Virtual Image will not be provided as Service Plan choices.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are collected for agent-less hosts and vm’s from VMware and AWS clouds).
+
+Username
+:   Existing Username on the Image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the Existing User on the image if Username is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is /var/opt/morpheus/morpheus-ui/VMs. Additional Storage Providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in runcmd and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Permissions
+:   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. No impact on single-tenant environments.
+    :   Visibility
+        :   Private
+            :   Image is only available in the specified Tenants below.
+
+            Public
+            :   Image is available to all Tenants.
+
+        Tenant
+        :   If Visibility is set to Private, specify Tenants the Image will be available for.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM based Hypervisors.
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+Enabled Sysprep?
+:   Applicable to Nutanix Only. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject Unattend.xml through the Nutanix API (v3+ only)
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-Init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
+
+### Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to HPE Morpheus Enterprise. To provision, HPE Morpheus Enterprise will need to upload the Image to the target Cloud upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a Local Virtual Image has been uploaded to a Cloud, subsequent provisions will use the Image local to the cloud instead of uploading again as long as the copied image is still available in the source Cloud.
+
+## Agent Install
+
+When provisioning an instance, there are some network and configuration requirements to successfully install the morpheus agent. Typically when a vm instance is still in the provisioning phase long after the vm is up, the instance is unable to reach HPE Morpheus Enterprise, or depending on agent install mode, HPE Morpheus Enterprise is unable to reach the instance.
+
+The most common reason an agent install fails is the provisioned instance cannot reach the HPE Morpheus Enterprise Appliance via the appliance\_url set in Administration > Settings over both 443 and 80. When an instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the appliance\_url or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main appliance\_url in Administration > Settings, additional appliance\_urls can be set per cloud in the Advanced options of the cloud configuration pane when creating or editing a cloud. When this field is populated, it will override the main appliance url for anything provisioned into that cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting agent installations.
+
+### Agent Install Modes
+
+There are 3 Agent install modes:
+
+- ssh/winrm
+- VMware Tools
+- cloud-init
+
+#### For All Agent Install modes
+
+When an instance is provisioned and the agent does not install, verify the following for any agent install mode:
+
+- The HPE Morpheus Enterprise appliance\_url (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The appliance\_url begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise Appliance from provisioned VM’s and container hosts on port 443 (needed for agent communication)
+- Private (non-morpheus provided) vm images/templates must have their credentials entered. These can be entered/edited in the Library > Virtual Images section but clicking the Actions dropdown of an image and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to clouds network sections for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or cloud appliance.
+
+### SSH/Winrm
+
+#### Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+![../_images/agent_ssh.gif](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D2F4F5EE-5377-4E4A-A6E8-DAD6ED4FBD80-high.gif)
+
+#### Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+### VMware tools (vmtools) rpc mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
+
+### Cloud-Init agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image/blueprint has Cloud-Init (linux) or Cloudbase-Init (windows) installed
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json b/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
new file mode 100644
index 0000000..7208b3b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+  "title": "Integrations",
+  "ordinal": 310,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md b/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
new file mode 100644
index 0000000..0ebf004
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
@@ -0,0 +1,26 @@
+# Integrations
+
+NOTE
+
+To add and edit certain integrations such as Ansible Tower, vRO, Chef and Puppet, the user must have FULL permission for “Library: Integrations” in addition to “Admin: Integrations”.
+
+To add an integration select + ADD and choose your integration. Many HPE Morpheus Enterprise-supported integrations can be configured in this section, though not all. Some integrations, such as networking integrations, must be configured within their own areas of the application. The following integrations can be configured in this section:
+
+- Chef
+- Puppet
+- Ansible
+- Ansible Tower
+- vRealize Orchestrator
+- Microsoft DNS
+- PowerDNS
+- Route 53
+- Bind DNS
+- Git
+- Github
+- Docker Repositories
+- Jenkins
+- ServiceNow
+- Cherwell
+- Remedy
+
+Refer the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) for each specific integration type for more detailed information on setup steps and features supported by the integration.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json b/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
new file mode 100644
index 0000000..c3714da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+  "title": "Initial Appliance Setup",
+  "ordinal": 39,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Appliance Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md b/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
new file mode 100644
index 0000000..8ed308f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
@@ -0,0 +1,80 @@
+# Initial Appliance Setup
+
+## Appliance Setup
+
+### About this task
+
+After installation, log into the appliance at the URL presented upon completion. An initial setup wizard walks through the first account and user creations.
+
+### Procedure
+
+1. Enter Master Account name 
+
+   - Typically, the Master Account name is your Company name.
+2. Create Master User 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email Address
+   - Password \* Must be at least 8 characters long and contain one each of the following: Uppercase letter, lowercase letter, Number, Special Character
+3. Enter Appliance Name & Appliance URL 
+
+   - The Appliance Name is used for white labeling and as a reference for multi-appliance installations.
+   - The Appliance URL is the URL all provisioned instances will report back to. Example: <https://example.morpheusdata.com>. The Appliance URL can be changed later, and also set to a different URL per cloud integration.
+4. Optionally Enable or Disable Backups, Monitoring, or Logs from this screen. 
+
+   NOTE
+
+   You may adjust these settings from the Administration section.
+
+   NOTE
+
+   The Master Account name is the top-level admin account.
+
+   NOTE
+
+   The Master User is the system super user and will have full access privileges.
+
+### Results
+
+Upon completing of the initial appliance setup, you will be taken to the Administration > Settings page, where you will add your License Key.
+
+## Login Methods
+
+Master Tenant
+
+- Enter username (or email address) and password
+
+Subtenant
+
+To login, subtenants can either use the master tenant URL with `subtenant\username` formatting:
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
+
+Or use the tenant specific URL which can be found and configured under Administration > Tenants > Select Tenant > IdentitySources.
+
+![../../_images/tenant_url.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-24D6CCD6-E864-4CA6-8D91-5EFDFB50CB33-high.png)
+
+IMPORTANT
+
+In 3.4.0+ Subtenant users will no longer be able to login from the main login url without specifying their subdomain.
+
+## Configure Cloud-init Global Settings
+
+When using cloud-init, cloudbase-init, VMware Tools customizations, or Nutanix Sysprep, Global Linux User and Windows Administrator credentials can be set using the settings in Administration > Settings > Provisioning. It is recommended to define these settings after installation unless credentials are defined per Virtual Image for Provisioning.
+
+## Add a License Key
+
+In order to provision anything in HPE Morpheus Enterprise, a HPE Morpheus Enterprise License Key must be applied.
+
+If you do not already have a license key, one may be requested from <https://app.morpheushub.com> or from your HPE Morpheus Enterprise representative.
+
+In the Administration > Settings section, select the LICENSE tab, paste your License Key and click UPDATE
+
+![../../_images/license_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-1DE90FFC-D78A-4AEC-B168-D1AF1DF3E611-high.png)
+
+When the license is accepted, your license details will populate in the Current License section.
+
+If you receive an error message and your license is not accepted, please check it was copied in full and then contact your HPE Morpheus Enterprise representative. You can also verify the License Key and expiration at <https://app.morpheushub.com>.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json b/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
new file mode 100644
index 0000000..301406e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+  "title": "Power Scheduling",
+  "ordinal": 123,
+  "parent_title": "Automation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html",
+  "topic_cluster": {
+    "clustering_title": "Power Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md b/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
new file mode 100644
index 0000000..c582a4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
@@ -0,0 +1,114 @@
+# Power Scheduling
+
+Set weekly schedules for shutdown and startup times for Instances and VM’s, apply Power Schedules to Instances pre or post-provisioning, apply Power Schedule policies on Group or Clouds, or use Guidance to automatically recommend and apply optimized Power Schedules.
+
+## Create Power schedules
+
+### Procedure
+
+1. Navigate to Library > Automation > Power Scheduling
+2. Select + ADD
+3. Configure the following options: 
+
+   NAME
+   :   Name of the Power Schedule
+
+   DESCRIPTION
+   :   Description for the Power Schedule
+
+   TIME ZONE
+   :   Time Zone the Power Schedule times correlate to.
+
+   TYPE
+   :   Power On
+       :   Power Up and then Down at scheduled times
+
+       Power off
+       :   Power Down then Up at scheduled times
+
+       Enabled
+       :   Check for Power Schedule to be Active. Uncheck to disable Power Schedule.
+
+       DAYS
+       :   Slide the start and end time controls for each day to configure each days Schedule. Green sections indicate Power on, red sections indicate Power Off. Time indicated applies to selected Time Zone. The sliders can be used to set time in 15-minute steps, for single-minute granularity click the pencil icon and enter a specific time down to the minute.
+
+   ![../../_images/powerSchedule.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3FAFD413-3475-44A9-811A-575B689D836D-high.png)
+4. Select SAVE CHANGES
+
+### Results
+
+TIP
+
+To view the Instances a power schedule is currently set on, select the name of a Power Schedule to go to the Power Schedule Detail Page.
+
+## Add Power Schedule to Instance
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Select an Instance
+3. Select EDIT
+4. In the POWER SCHEDULE dropdown, select a Power Schedule.
+5. Select SAVE CHANGES
+
+## Add Power Schedule to Virtual Machine
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Compute  >  Virtual Machines
+2. Select a Virtual Machine
+3. Select EDIT
+4. Expand the Advanced Options section
+5. In the POWER SCHEDULE dropdown, select a Power Schedule.
+6. Select SAVE CHANGES
+
+## Add Power Schedule Policy
+
+### About this task
+
+NOTE
+
+Power Schedule Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD
+3. Select TYPE Power Schedule
+4. Configure the Power Schedule Policy: 
+
+   NAME
+   :   Name of the Policy
+
+   DESCRIPTION
+   :   Add details about your Policy for reference in the Policies tab.
+
+   Enabled
+   :   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Clouds Instances until re-enabled.
+
+   ENFORCEMENT TYPE
+   :   - User Configurable: Power Schedule choice is editable by User during provisioning.
+       - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+   POWER SCHEDULE
+   :   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+   SCOPE
+   :   Global
+       :   Applies to all Instances created while the Policy is enabled
+
+       Group
+       :   Applies to all Instances created in or moved into specified Group while the Policy is enabled
+
+       Cloud
+       :   Applies to all Instances created in specified Cloud while the Policy is enabled
+
+       User
+       :   Applies to all Instances created by specified User while the Policy is enabled
+
+       Role
+       :   Applies to all Instances created by Users with specified Role while the Policy is enabled
+
+   Permissions- TENANTS
+   :   Leave blank to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+5. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..c635b48
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 321,
+  "parent_title": "Settings",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..54e61d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,189 @@
+# Appliance
+
+## Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the HPE Morpheus Enterprise API. For example, if you were designing a web application which needed to make AJAX calls to HPE Morpheus Enterprise API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Incident Retainment
+:   Enter the number of days HPE Morpheus Enterprise should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the HPE Morpheus Enterprise appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured HPE Morpheus Enterprise Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of HPE Morpheus Enterprise documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
+
+Dashboards to Display
+:   A typeahead field which will show all Dashboards available to the appliance from Dashboard-type plugins. Select all desired Dashboards and they will be displayed in the order set. Dashboards can be dragged up and down the list to set the order correctly.
+
+## Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+## User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
+
+## Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide HPE Morpheus Enterprise the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the HPE Morpheus Enterprise server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into HPE Morpheus Enterprise, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the HPE Morpheus Enterprise appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your HPE Morpheus Enterprise server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
+
+## Twilio SMS Settings
+
+Configure SMS text message delivery for HPE Morpheus Enterprise alerts. Previously, customers could use HPE Morpheus Enterprise’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all HPE Morpheus Enterprise nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
+
+## Proxy Settings
+
+The HPE Morpheus Enterprise Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+
+  : Specifies the hostname or IP address of the proxy server.
+- Proxy Port
+
+  : Specifies the port number used by the proxy server to communicate.
+- Proxy User
+
+  : Specifies the username used to authenticate with the proxy server.
+- Proxy Password
+
+  : Specifies the password associated with the proxy user account.
+- Proxy Domain
+
+  : Specifies the authentication domain for the proxy user.
+- Proxy Workstation
+
+  : Specifies the workstation name used for proxy authentication.
+- No Proxy
+
+  : Specifies a list of hosts that should bypass the proxy.
+
+## Currency Settings
+
+In HPE Morpheus Enterprise, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, HPE Morpheus Enterprise allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
+
+## Integrating With a Currency Exchange Provider
+
+### Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+### Results
+
+The service is now integrated and can be used as described in the next section.
+
+## Consuming Currency Exchange in HPE Morpheus Enterprise
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
+
+## Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json b/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
new file mode 100644
index 0000000..c6e62af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+  "title": "Adding the OpenShift Plugin",
+  "ordinal": 205,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html",
+  "topic_cluster": {
+    "clustering_title": "Adding the OpenShift Plugin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md b/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
new file mode 100644
index 0000000..f782676
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
@@ -0,0 +1,13 @@
+# Adding the OpenShift Plugin
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise, which is not included in the product by default.
+
+1. To download the plugin, navigate to the plugin share site (share.morpheusdata.com) and browse or search for the OpenShift plugin
+2. With the plugin downloaded to your workstation, navigate to the plugins list page (Administration > Integrations > Plugins) in HPE Morpheus Enterprise UI
+3. Click Add
+4. Browse for the plugin JAR or drag and drop it onto the target
+5. Click Upload
+
+After a few brief moments, the new plugin will be added. This plugin adds a new Cluster type, which can be added from the Clusters list page (Infrastructure > Clusters) and also adds a new Instance Type which can be provisioned from the Instance provisioning wizard once a compatible cluster is integrated.
+
+Further configuration and usage details are covered in later sections of this guide.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json b/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
new file mode 100644
index 0000000..13dc221
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+  "title": "See Also",
+  "ordinal": 528,
+  "parent_title": null,
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.html",
+  "topic_cluster": {
+    "clustering_title": "See Also",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md b/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
new file mode 100644
index 0000000..80a1f57
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
@@ -0,0 +1,14 @@
+# See Also
+
+**Subtopics**  
+
+- **[Navigation Updates](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html)**
+- **[Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798_2.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA_2.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2_2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42_2.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD_2.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F_2.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8_2.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json b/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
new file mode 100644
index 0000000..1914ded
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+  "title": "Failover",
+  "ordinal": 189,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md b/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
new file mode 100644
index 0000000..9e363c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
@@ -0,0 +1,17 @@
+# Failover
+
+HVM supports automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+This three-node cluster has three VMs running on the first host:
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json b/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
new file mode 100644
index 0000000..76df3cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+  "title": "Provisioning Images",
+  "ordinal": 150,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md b/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
new file mode 100644
index 0000000..f77c843
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, HPE Morpheus Enterprise will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced, marketplace, or previously copied images, no image stream from S3 through the HPE Morpheus Enterprise Appliance to the destination cloud will take place.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json b/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
new file mode 100644
index 0000000..21241c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+  "title": "Creating Apps",
+  "ordinal": 88,
+  "parent_title": "Apps",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md b/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
new file mode 100644
index 0000000..060fd95
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
@@ -0,0 +1,56 @@
+# Creating Apps
+
+New Apps can be created from Blueprints or using existing Instances.
+
+## Creating Apps from Blueprints
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select an existing App Blueprint and click NEXT. 
+
+   NOTE
+
+   App Blueprints must be created in Library > Blueprints > App Blueprints to appear as options when provisioning an App.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected.
+4. Click NEXT. Blueprint configurations matching the Group, Cloud and Environment selections will auto-populate the configurations of the Instances in the App. If no Blueprint Configuration matched the Group, Cloud or Env selections, the Instances will have default configurations.
+5. Configure your Instances. Depending on the Blueprint Configurations settings, instances may already be fully configured. Fields that are locked in a Blueprint cannot be edited when creating an App. 
+
+   NOTE
+
+   Once an Instance is fully configured, a green checkmark will appear next to the Instance. Instances that have required fields that need populated will have a red X and must be completed. If your Blueprint is already fully configured, you can simply select COMPLETE!
+6. Select COMPLETE and the App will be created, and the Instances will begin provisioning.
+
+### Results
+
+![../../_images/apps_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-F0EDC63A-480C-4013-AC6D-A1C51BA13CC7-high.png)
+
+## Creating Apps from Existing Instances
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select `APP FROM EXISTING INSTANCES` from the Blueprints list and click NEXT.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected. 
+
+   NOTE
+
+   Only instances within the selected Group and Cloud will be available to be added to the App.
+4. In the STRUCTURE section, select + to add a Tier
+5. Select or enter a Tier Name.
+6. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+7. In the STRUCTURE section, select + in a Tier to add an Instance
+8. Select the Instance Type of the Existing Instance to be added to the App.
+9. In the STRUCTURE section, select the Instance.
+10. In the CONFIGURATION section, select the Cloud the Existing Instance is in. Existing INSTANCES that match the Group, Cloud and Instance Types set will populate.
+11. Select the desired Instance from the INSTANCES list. Selected instance will show in the SELECTED INSTANCE section. 
+
+    NOTE
+
+    Only one existing Instance can be added per Instance. To add multiple Existing Instances, repeat the step above including adding an Instance for each Existing Instance to be added to the App.
+12. Once all Existing Instances have been selected, click COMPLETE.
+13. A new App will be created out of the Existing Instances.
+
+### Results
+
+![../../_images/apps_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-2EECD2F1-36D5-4E56-B12D-99872F54B075-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json b/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
new file mode 100644
index 0000000..0f4c03c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+  "title": "Boot Prompt Configuration",
+  "ordinal": 412,
+  "parent_title": "Windows OS Imaging",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Prompt Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md b/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
new file mode 100644
index 0000000..8675424
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
@@ -0,0 +1,30 @@
+# Boot Prompt Configuration
+
+Unmodified Microsoft Windows Server ISOs display a Press any key to boot CD/DVD… prompt, which will interrupt unattended bare metal deployments.
+
+Two approaches are supported:
+
+- Option 1: Use a Modified ISO (Recommended)
+- Option 2: Manual Console Interaction
+
+## Option 1: Use a Modified ISO (Recommended)
+
+Use a Windows ISO with the boot prompt removed. A script to generate such an ISO is available at `https://github.com/HewlettPackard/hpegl-metal-os-windows-iso`
+
+Only the resulting ISO is required. A prebuilt Windows Server 2022 Evaluation ISO with this modification is also available and suitable for testing environments.
+
+## Option 2: Manual Console Interaction
+
+If using an unmodified ISO:
+
+1. Create the instance as usual.
+2. When the instance enters provisioning, open the Remote Console.
+3. Press Enter when prompted to boot from the installation media.
+
+## Windows Licensing Considerations
+
+At present, Windows licensing is not supported during bare metal provisioning.
+
+Only Evaluation editions or versions that do not require a Product Key in AutoUnattend.xml can be deployed.
+
+The modified Windows Server 2022 ISO referenced above is an Evaluation edition and is suitable for testing.
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json b/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
new file mode 100644
index 0000000..7e175c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+  "title": "Installation Overview",
+  "ordinal": 15,
+  "parent_title": "Installation",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html",
+  "topic_cluster": {
+    "clustering_title": "Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md b/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
new file mode 100644
index 0000000..d86e675
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
@@ -0,0 +1,111 @@
+# Installation Overview
+
+IMPORTANT
+
+HPE Morpheus Enterprise v4.2.0 enhanced security configuration restricts incoming appliance connections to TLS v1.2, potentially impacting front-end load balancer monitoring/health checks that support only TLS v1.1 or lower, as well as HPE Morpheus Enterprise Agent installations for Windows nodes using .net versions that do not support TLS v1.2. Refer to TLS
+
+HPE Morpheus Enterprise comes packaged as a `debian` or `yum` based package. The default configuration installs all required services on a single vm or bare metal Host. Morpheus can be configured in a distributed architecture to use one or multiple external services, and multiple application Hosts can be configured for High Availability configurations.
+
+All components required for Morpheus are installed and configured by default during the Morpheus `reconfigure` command. The Morpheus config file, `morpheus.rb`, can optionally be configured to point the Morpheus App to external services (distributed configuration).
+
+Morpheus can optionally be configured to use external Database, Messaging, and/or Search Tiers. This means instead of installing, for example, MySQL on the same host as the Morpheus App, the Morpheus configuration file (morpheus.rb) is setup to point to an external MySQL host, cluster or service, and MySQL will not be installed or configured on the Appliance Host.
+
+## Install Packages
+
+HPE Morpheus Enterprise Release Package URLs can be obtained from My HPE Software Center.
+
+## Configuration Options
+
+- Single Host (All-In-One/default)
+  :   All tiers running on a single host. The reconfigure process installs all required services. This is the default configuration.
+- Single Hosts with Distributed Service(s)
+  :   Transactional Database, Non-Transactional Database, and/or Message tiers are externalized, with the remaining services on a single host. The reconfigure process installs all services not set to false in `/etc/morpheus/morpheus.rb`
+- Clustered Hosts with Distributed Transactional Database (3-Node HA)
+  :   Application, Message and Non-Transactional tiers are installed and clustered on three or more hosts, with all three hosts pointing to externalized database tier. The reconfigure process installs all services except mySQL.
+- App Host(s) with Distributed Services (Full HA)
+  :   Application tier is installed on one or more hosts. All UI hosts point to externalized Transactional Database, Non-Transactional Database, and Message Tiers. The reconfigure process installs only Application services.
+
+## Distributed Configurations
+
+Morpheus provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the Morpheus HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the Morpheus appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Message Tier. Each of these tiers have their own recommendations for High availability deployments that we need to cover.
+
+### Application Tier
+
+The application tier is easily installed with the same Debian or yum repository package that Morpheus is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. These machines should also have at least 8gb of Memory. They can be configured across all regions and placed behind a central load-balancer or Geo based load-balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is a shared storage means is necessary when it comes to maintaining things like deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. If not using those options a simple NFS cluster can also be used to handle the shared storage structure.
+
+### Transactional Database Tier
+
+The Transactional database tier usually consists of a MySQL-compatible database. It is recommended that a lockable clustered configuration be used. There are several documents online related to configuring and setting up such a cluster but it most simply can be laid out in a many-master configuration. There can be some nodes setup with replication delay as well as some with no replication delay. It is common practice to have no replication delay within the same region and allow some replication delay cross region. This does increase the risk of job run overlap between the 2 regions however, the concurrent operations typically self-correct and this is a non-issue.
+
+### Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an OpenSearch (version 7.6.0) cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a Java-based system and does require a sizable chunk of memory for larger data sets. 8 GB is recommended and more nodes can be added to scale either horizontally or vertically.
+
+### Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster, it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. The ports necessary to forward in a Rabbit MQ cluster are (5672, and 61613). A RabbitMQ cluster can run on smaller memory machines depending on how frequent large requests bursts occur. 4 - 8 GB of Memory is recommended to start.
+
+## Pros/Cons
+
+### Single Host
+
+Advantages
+:   - Simple Installation - Morpheus Installs all required services
+    - Simple Configuration - Morpheus configures all required services
+    - Simple Maintenance - All service connections and credentials are local - All logs are local - All Data is local (by default)
+    - Not dependent on network connections for vital services - Facilitates speed and reliability
+
+Disadvantages
+:   - Single point of failure
+    - Individual services cannot be scaled
+    - Upgrades require (minimal) downtime
+    - Single region
+
+### Single Hosts with Distributed Service(s)
+
+Advantages
+:   - Individual services can be scaled
+    - Managed Services such as RDS can be utilized
+
+Disadvantages
+:   - Single region
+    - External services require additional configuration and maintenance
+    - Morpheus is subject to network performance, configuration and availability
+    - Increased Installation time possible
+
+### Clustered Hosts with Distributed Transactional Database
+
+Advantages
+:   - Database can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - RabbitMQ and Opensearch Clusters
+
+Disadvantages
+:   - External Database services requires additional configuration and maintenance
+    - App Host Clustering requires additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+
+### App Host(s) with Distributed Services
+
+Advantages
+:   - Individual services can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - Multi region support
+
+Disadvantages
+:   - External services require additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure Requirements
+    - Increased Networking requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+    - Rabbit Load balancer required
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json b/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
new file mode 100644
index 0000000..7a65a0a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_0",
+  "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+  "title": "Costing: Budget Analysis",
+  "ordinal": 63,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007510en_us",
+  "version": "8.1.0",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007510en_us&page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Budget Analysis",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md b/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
new file mode 100644
index 0000000..c5babe1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_0/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
@@ -0,0 +1,25 @@
+# Costing: Budget Analysis
+
+![../_images/6budgetanalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007510en_us/GUID-D7C44885-681F-4B92-8D83-E5EB52F25660-high.png)
+
+The Budget Analysis dashboard allows administrators to filter and view budgets in one place in order to keep track of progress against budget over time. Budgets in HPE Morpheus Enterprise (Operations > Budgets) are tied to a specific scope (Account, Tenant, Cloud, Group, or User) and budgets of the same scope are viewed together in this dashboard. A scope filter must be set in order for data to be populated into the dashboard. Once a scope is selected, the search bar can be utilized to return only budgets within the selected scope whose “Name” meets the search terms.
+
+## Filters
+
+Filter the budgets pulled into the dashboard by one or more of the following fields:
+
+- Budget name (all matched by search)
+- Scope (This is a required field, data is not populated into the dashboard until a scope is specified)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all budgets that meet set filters:
+
+- **BUDGETS:** The total number of budgets that meet set filters
+- **MONTH TO DATE:** The total spend in the current month against the selected budgets
+- **BUDGETS TO DATE:** The total amount budgeted to date among budgets selected by the dashboard filters (from the start of the year to the end of the current interval)
+- **TO BUDGET:** The difference between the COST TO DATE and BUDGETS TO DATE value, should be close to $0 if the costs are appropriately tracking against the budgeted amounts
+
+## Budget List
+
+Each budget with its own graph and breakdown is displayed going down the page. The format of the information presented depends on the interval that the specific budget is configured for.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json b/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
new file mode 100644
index 0000000..1f56257
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+  "title": "SSL Self-signed Certificate Regeneration",
+  "ordinal": 356,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Self-signed Certificate Regeneration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md b/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
new file mode 100644
index 0000000..0099ff5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
@@ -0,0 +1,19 @@
+# SSL Self-signed Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year self-signed non-trusted SSL certificate. Below details the process to regenerate this certificate and key.
+
+## Replacing both the certificate and private key
+
+### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/` that end in `.crt` and `.key`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
+
+## Replacing only the certificate
+
+### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/` it ends in `.crt`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json b/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
new file mode 100644
index 0000000..fb64bb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+  "title": "Settings",
+  "ordinal": 321,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md b/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
new file mode 100644
index 0000000..c2fedb1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
@@ -0,0 +1,18 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the HPE Morpheus Enterprise appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for HPE Morpheus Enterprise itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Whitelabel](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html)**
+- **[Email Templates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5_2.html)**
+- **[Clients](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[Software Licenses](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json b/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
new file mode 100644
index 0000000..44637a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+  "title": "Load Balancers",
+  "ordinal": 227,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md b/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
new file mode 100644
index 0000000..43a09c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
@@ -0,0 +1,88 @@
+# Load Balancers
+
+The Load Balancers tab list currently available Load Balancers, which you can select, edit or delete, and is where you can create new or integrate with external Load Balancers.
+
+## Configuration parameters to add a new load balancer
+
+Following parameters are required configure the respective load balancers:
+
+Amazon ALB
+:   - Scheme
+    - Internal
+    - Internet-Facing
+    - Amazon Subnets (Select + to add additional) \* Specify the subnets to enable for your load balancer. You can specify only one subnet per Availability Zone. You must specify subnets from at least two Availability Zones to increase the availability of your load balancer.
+    - Amazon Security Groups (Select + to add additional)
+
+      For details, see [Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html).
+
+Azure load balancer
+:   - Cloud
+    - Resource Group \* Populated from cloud selection
+
+      For details, see [Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html).
+
+Citrix NetScaler
+:   - API Host
+    - API Port
+    - Username
+    - Password
+
+      For details, see [Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html).
+
+F5 BigIP (v11.4+)
+:   - API Host
+    - API Port
+    - Username
+    - Password
+    - Management URL
+
+      For details, see [Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html).
+
+FortiADC
+:   - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - INTERFACE (synced on auth)
+
+      For details, see [Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html).
+
+HaProxy Container (Internal, will create a HaProxy container, must have available docker host to provision to)
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - Plan \* Select the size of HaProxy container to be provisioned
+
+      For details, see [Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html).
+
+NSX load balancer
+:   - NSX
+    - Name
+    - Description
+    - Enabled
+    - Admin State
+    - Size
+    - Tier-1 Gateways
+    - Log Level
+
+      For details, see [Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html).
+
+NSX Advanced load balancer
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - AVI CLOUD
+
+      For details, see [Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html).
+
+Upon saving, your new load balancer will be added to the load balancers list and available in the load balancer drop-down list under the Provisioning Wizard Automation Section for Instance Types that have scaling enabled.
+
+### Load Balancer Detail Pages
+
+In the main Load Balancer page, select an existing Load Balancer to go to that Load Balancers Details Page, which lists Stats, Settings, Actions and Virtual Servers for that load balancer.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json b/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
new file mode 100644
index 0000000..525e4e8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+  "title": "Ansible Troubleshooting",
+  "ordinal": 346,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md b/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
new file mode 100644
index 0000000..c004156
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
@@ -0,0 +1,52 @@
+# Ansible Troubleshooting
+
+When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in UI logs at `/var/log/morpheus/morpheus-ui/current​`. These can be tailed by running `morpheus-ctl tail morpheus-ui`.
+
+## Verify Ansible is installed on the HPE Morpheus Enterprise Appliance
+
+Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+### If Ansible is not installed
+
+Follow these instructions to install, or use your preferred installation method
+
+Ubuntu:
+
+```
+```
+sudo apt-get install software-properties-common  
+sudo apt-add-repository ppa:ansible/ansible  
+sudo apt-get update  
+sudo apt-get install ansible python-requests
+```
+```
+
+CentOS:
+
+```
+```
+sudo yum install epel-release  
+sudo yum install ansible python-requests
+```
+```
+
+Then create the working Ansible directory for Morpheus:
+
+```
+```
+sudo mkdir /opt/morpheus/.ansible  
+sudo chown morpheus-app.morpheus-app /opt/morpheus/.ansible
+```
+```
+
+## Validate Git repo authorization and the configured paths
+
+The public and private SSH keys need to be added to the HPE Morpheus Enterprise appliance via Infrastructure  >  Keys & Certs and the public key needs to be added to the Git repo via user settings. If both are set up correctly, you will see the playbooks and roles populate in the Ansible Integration details page.
+
+The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+
+When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+
+NOTE
+
+If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json b/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
new file mode 100644
index 0000000..ded6b1d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+  "title": "Provisioning a New Server",
+  "ordinal": 415,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a New Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md b/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
new file mode 100644
index 0000000..0d7d0b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
@@ -0,0 +1,9 @@
+# Provisioning a New Server
+
+Provisioning a new server allows onboarding new, unmanaged HPE ProLiant servers into a Bare Metal Cloud environment, enabling HPE Morpheus to manage their lifecycle, including automated OS deployment and hardware monitoring.
+
+**Subtopics**  
+
+- **[Importing HPE ProLiant Bare Metal Servers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html)**
+- **[Provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html)**
+- **[Post-Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json b/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
new file mode 100644
index 0000000..f9ba8d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+  "title": "CyberArk Conjur",
+  "ordinal": 526,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html",
+  "topic_cluster": {
+    "clustering_title": "CyberArk Conjur",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md b/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
new file mode 100644
index 0000000..2c9f4bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
@@ -0,0 +1,63 @@
+# CyberArk Conjur
+
+HPE Morpheus Enterprise supports integration with CyberArk Conjur for stored credential sets as well utilization of Conjur-stored secret values via HPE Morpheus Enterprise Cypher service. This works identically to built-in credential storage and built-in Cypher functionality with the exception that your Conjur server is the storage backend rather than the HPE Morpheus Enterprise appliance itself. In some cases, this may help to consolidate secret management into one central place or it even may be a requirement to satisfy internal security policies at some organizations.
+
+CyberArk Conjur integration is not included with HPE Morpheus Enterprise out of the box. It is developed as an official plugin and may be applied to any HPE Morpheus Enterprise appliance that needs it. See the HPE Morpheus Enterprise plugin repository website for access to the latest version of the plugin.
+
+## Applying the Plugin
+
+The latest version of the CyberArk Conjur plugin is available at the HPE Morpheus Enterprise [plugin share site](https://share.morpheusdata.com/). Select the pane for the correct plugin and click the DOWNLOAD button. The plugin JAR file will be downloaded to the local computer you’re working on.
+
+![../../_images/share.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C8A10069-9604-4478-904C-F916186AB33E-high.png)
+
+With the plugin downloaded, head back to HPE Morpheus Enterprise to apply the plugin to your appliance. Plugins are added by navigating to Administration > Integrations > Plugins and clicking ADD. Drop the plugin JAR file onto the target and click UPLOAD. It may take a few moments for the plugin to be applied successfully and for the modal to be dismissed after clicking the upload button.
+
+![../../_images/addPlugin.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ED50E88D-DE3D-419D-9071-B86CFBFD5BDD-high.png)
+
+Once the plugin is added, we configure the connection details here. Edit the new Conjur plugin by clicking the pencil (✎) icon from its row in the list. Configure the following fields:
+
+- **NAME:** A friendly name for the new integration to identify it within HPE Morpheus Enterprise
+- **ENABLED:** Mark the box to make this integration active and available
+- **CONJUR API URL:** The full URL for the Conjur server, usually listening on port 8443
+- **CONJUR USERNAME:** The Conjur user account you wish to authenticate with. This user should have read, write, and execute access to the variables configured within the Conjur policy
+- **CONJUR USERNAME API KEY:** The API key for user entered in the prior field
+- **CONJUR ORGANIZATION:** The Conjur account in which the user and variables reside
+- **CLEAR SECRET ON DELETION:** When marked, secret values will be cleared when deleted from HPE Morpheus Enterprise
+
+IMPORTANT
+
+Variables are predefined by Conjur policies. This integration does not allow users to create variables but does allow you to read and update their values. If the plugin is configured to clear secrets that are deleted from HPE Morpheus Enterprise, the variable value is updated with an empty value as there is no concept of fully deleting secrets in the Conjur API. If the plugin is configured not to clear secrets on deletion, the secret object is deleted from HPE Morpheus Enterprise without altering it on the Conjur backend.
+
+By applying and configuring the plugin, the appliance now has the Conjur/Cypher integration available. If you don’t intend to use the credential store integration, you can stop here and look ahead to the feature demonstration further ahead in this guide. If you do intend to use the credential store integration as well, there’s one additional configuration step to take in the next section.
+
+## Adding A Conjur Trust Integration
+
+In order to use Conjur with HPE Morpheus Enterprise credentials, we must also add a Conjur-type integration in Infrastructure > Trust > Integrations. By applying the plugin in the previous step, we now have the ability to add this type of integration. From the Trust integrations list page, click + ADD and select “Conjur.” It’s important to note that you **do not** need to again configure the API URL and Conjur login credentials as we just did in the previous step. You may configure them here if you wish, such as if you were making multiple integrations with multiple Conjur appliances, but if you’re simply integrating with the same appliance and user account, this is unnecessary. Simply give the new Trust integration a friendly name for reference in HPE Morpheus Enterprise and indicate the desired mount point for secrets you wish to consume as done in the screenshot below.
+
+NOTE
+
+In many cases, you don’t have to configure the connection details when adding a Conjur Trust integration. See the paragraph above.
+
+![../../_images/addTrustInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AE830924-B765-498F-98B6-154E38F1A4A5-high.png)
+
+## Conjur and Credential Stores
+
+With configurations completed, we can take a look at how HPE Morpheus Enterprise is able to interface with Conjur as a credential store. As mentioned at the beginning of this guide, variables are created by Conjur policies and not by HPE Morpheus Enterprise. We can reference existing variables and update the secret values stored within.
+
+As an example, there is a variable named `BotApp/secretVar` in the target Conjur appliance. When configuring the Trust integration (in the prior section), the `BotApp/` mount point was referenced (see the screenshot in the last section). When creating stored credential sets in HPE Morpheus Enterprise against this Conjur credential store, reference the rest of the variable path as the NAME value on the credential set. In this case, the credential set will be named `secretVar` to complete the `BotApp/secretVar` path as shown in the screenshot below. Be sure to also select Conjur as the CREDENTIAL STORE value rather than the default “Internal.”
+
+![../../_images/credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4DCB5DDF-130A-4847-912C-CAE31A96EDBE-high.png)
+
+After saving and going back to the Conjur appliance, the value stored at the referenced variable has been updated. This credential set is also available for use anywhere HPE Morpheus Enterprise allows users to utilize them, such as when integrating new Clouds, authenticating REST calls to populate Option Lists, and many other places.
+
+## Conjur and Cypher
+
+In addition to stored credential sets, the CyberArk Conjur plugin also enables integration with HPE Morpheus Enterprise Cypher. Just as calls can be made to internally-stored secret values with Cypher, Conjur variable endpoints may be referenced to onboard secret strings into automation Tasks.
+
+In the screenshot below, see a simple shell script Task which echoes out a secret value stored in Conjur. As you can see, the `conjur/` mount point is referenced along with the rest of the path to the variable which should be accessed. After executing the Task, we can check the execution history and see that the Conjur-stored value is indeed echoed back out.
+
+![../../_images/cypherTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DE2D6E0C-3988-42C1-8C27-2F31438CDED9-high.png)
+
+If desired, the value stored in Conjur could also be updated through the HPE Morpheus Enterprise Cypher UI. Navigate to Tools > Cypher and click + ADD. Note the `conjur` mount point is included in the example list of available mount points shown in the modal. By creating a new Cypher entry at the `conjur` mount point which references an existing Conjur variable path, the value in Conjur can be overwritten. If you’ve configured the plugin to clear secrets on deletion, you can also update the stored value with an empty string when you delete the Cypher object in HPE Morpheus Enterprise. For our example case, we could update the value in Conjur by creating a Cypher entry at the mount point `conjur/BotApp/secretVar`.
+
+![../../_images/cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F2FAE481-318A-42D8-A12B-D1904246CF52-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json b/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
new file mode 100644
index 0000000..58de15b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+  "title": "Utilities",
+  "ordinal": 331,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md b/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
new file mode 100644
index 0000000..cbda40a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places HPE Morpheus Enterprise into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting HPE Morpheus Enterprise UI disables maintenance mode.
+
+NOTE
+
+When using HPE Morpheus Enterprise in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A HPE Morpheus Enterprise node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json b/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
new file mode 100644
index 0000000..c1197a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+  "title": "Storage",
+  "ordinal": 229,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md b/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
new file mode 100644
index 0000000..e64fc78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
@@ -0,0 +1,14 @@
+# Storage
+
+NOTE
+
+In v3.5.2 STORAGE PROVIDERS has been split out into BUCKETS and FILE SHARES sections.
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html)**
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html)**
+- **[Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html)**
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html)**
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
new file mode 100644
index 0000000..c16d163
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+  "title": "ARM Blueprints",
+  "ordinal": 132,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html",
+  "topic_cluster": {
+    "clustering_title": "ARM Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
new file mode 100644
index 0000000..53baef2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
@@ -0,0 +1,41 @@
+# ARM Blueprints
+
+ARM Blueprints provide a simple and repeatable way of deploying infrastructure-as-code to Azure Clouds. Objects and properties are defined in a JSON file and are provisionable on-demand in |ProApp|
+
+To create a new ARM Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select ARM. NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The ARM template itself is defined in the ARM Configuration section. Using the Config Type dropdown menu, we can opt to write or paste JSON configuration directly into this modal, or we can choose to bring in a JSON which we’re keeping under version control in a Git repository.
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+If writing or pasting your configuration JSON directly into the modal, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** ARM Template JSON (.json)
+- **CONFIG:** Your JSON configuration template
+
+If bringing in a template from a Git repository, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new ARM Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json b/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
new file mode 100644
index 0000000..40465f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+  "title": "File Templates",
+  "ordinal": 160,
+  "parent_title": "Templates",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html",
+  "topic_cluster": {
+    "clustering_title": "File Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md b/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
new file mode 100644
index 0000000..d10d769
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
@@ -0,0 +1,60 @@
+# File Templates
+
+File Templates are for generating config files, such as my.cnf, opensearch.yml, morpheus.rb, or any text file. With full config map variable support, Template Files are dynamically generated during a Workflow phase or ad hoc via Instance actions.
+
+File Templates can also be exposed on Instances in the Settings Tab. Ensure the Instance Type supports settings, and Category is defined in Advance Options on the Library Template config.
+
+NOTE
+
+HPE Morpheus Enterprise variables are supported in Library Templates using `<%= variable.var %>` format
+
+Examples:
+
+HA Proxy Config (haproxy.cfg)
+
+- FILE NAME: haproxy.cfg
+- FILE PATH: /config/haproxy.cfg
+- PHASE: Pre Provision
+- TEMPLATE:
+- SETTING NAME: haproxyConfig
+- SETTING CATEGORY: haproxy
+
+```
+```
+#!/bin/bash  
+global  
+ maxconn 256  
+ log /dev/log local0 warning  
+ log-tag <%=logTag%>  
+defaults  
+ mode http  
+ timeout connect 5000ms  
+ timeout client 50000ms  
+ timeout server 50000ms  
+ log global  
+frontend http-in  
+ bind *:<%=container.externalPort%>  
+ default_backend servers  
+backend servers  
+ # server server1 127.0.0.1:80 maxconn 32
+```
+```
+
+mysql config (mysqld.cnf)
+
+- FILE NAME: mysqld.cnf
+- FILE PATH: /config/mysqld.cnf
+- PHASE: Pre Provision
+
+```
+```
+#!/bin/bash  
+[mysqld]  
+pid-file= /var/run/mysqld/mysqld.pid  
+socket= /var/run/mysqld/mysqld.sock  
+datadir= /var/lib/mysql  
+# Disabling symbolic-links is recommended to prevent assorted security risks  
+symbolic-links=0  
+explicit_defaults_for_timestamp = 1
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json b/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
new file mode 100644
index 0000000..ec88287
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+  "title": "DNS",
+  "ordinal": 483,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html",
+  "topic_cluster": {
+    "clustering_title": "DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md b/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
new file mode 100644
index 0000000..5e166e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
@@ -0,0 +1,7 @@
+# DNS
+
+**Subtopics**  
+
+- **[AWS Route53](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html)**
+- **[Microsoft DNS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html)**
+- **[PowerDNS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json b/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
new file mode 100644
index 0000000..65fbfa9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+  "title": "Policy Types",
+  "ordinal": 319,
+  "parent_title": "Policies",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md b/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
new file mode 100644
index 0000000..9707b3b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
@@ -0,0 +1,262 @@
+# Policy Types
+
+## Cypher Policies
+
+HPE Morpheus Enterprise allows administrators to set robust Cypher policies, which determine global, role, and/or specific user access to configured Cypher secret mount points. A number of considerations should be made when deploying Cypher Access policies, including how user role permissions will interact with the policy and how conflicts between overlapping policies are resolved.
+
+### Role Permissions
+
+User Role permissions (Administration > Roles) greatly affect Cypher access. Cypher access Role permissions are set from the Features tab of the selected Role under “Tools: Cypher”. The Role permission should be set based on the highest level of access to any one individual Cypher entry needed for the specific Role. For example, if the Role needs no access to any Cypher entries, set the feature permission to “None” and hide the Cypher UI from the Role completely. Alternatively, if the Role needs to use and decrypt even one Cypher entry, set the feature permission to “Full Decrypt”. The complete set of available permissions are below:
+
+- **NONE:** Cypher UI hidden
+- **READ:** Cypher UI present, entries can be listed
+- **USER:** Cypher UI present, user sees and can use their own entries, user can create new entries
+- **FULL:** Cypher UI present, user sees and can use all entries, user can create new entries, user cannot decrypt any entries
+- **FULL DECRYPT:** Full access to Cypher features including the ability to decrypt secrets
+
+### Cypher Access Policies
+
+Like other Policy types, Cypher Access Policies are created in Administration > Policies. Click + ADD POLICY to create new. Set the type to “Cypher Access” and the relevant configuration options will be displayed. In addition to the type, enter a name for the Policy in the top section.
+
+![../../_images/polname.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F8F43DED-7C86-4242-8B6E-37376AC02AEE-high.png)
+
+In the next section, enter the key path to which the Policy will apply. In addition to static entries that point to one specific Cypher entry, this field supports pattern matching with regex. For example, enter “.\*” to refer to all Cypher entries or “secret/.\*” to refer to all entries under the secret mount point.
+
+In addition to the path, set the privileges users in the Policy scope should have on the indicated path.
+
+- **LIST:** See the entries on the indicated path listed in the Cypher UI
+- **READ:** Decrypt the entries on the indicated path
+- **WRITE:** Add new entries on the indicated path
+- **UPDATE:** Edit Cypher entries on the indicated path
+- **DELETE:** Delete entries on the indicated path
+
+![../../_images/polconfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3073851F-5D93-4F03-94A1-C77B7D140E46-high.png)
+
+Finally, set the scope for the Policy. Cypher Access Policies support Global, Role, and User scope. For example, you may want to block off sets of Cypher entries for various departments within your organization. If you have existing Roles in HPE Morpheus Enterprise for each department, you can set up Role-scoped Policies to ensure they can only list, use, and add Cypher entries which are relevant to their own department.
+
+![../../_images/polfilter.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-63A43C98-F636-420D-828D-19BF24B01237-high.png)
+
+IMPORTANT
+
+When Cypher Access Policies conflict, the Policy with the longest path string length (typically the most specific) takes precedence. For example, a Policy giving LIST and READ access to “secret/aws/.\*” would be superseded by a Policy giving NO access to “secret/aws/my-secret-key”. In such a case, the user would see everything at the “secret/aws/.\*” path except the one indicated in the more specific Policy. When Policies targeting the same path differ only in their scope, the following scope precedence is applied: Role > User > Global. For example, if a Role-scoped Policy targeting “.\*” grants LIST and READ while a User-scoped Policy targeting the same path grants LIST, the user would be granted the rights in the Role-scoped Policy.
+
+### Cloud Profiles
+
+Terraform Cloud Profiles are created on each Cloud detail page (Infrastructure > Clouds > Selected Cloud > ProfilesTab), encrypted in Cypher, and create a Cypher entry that is visible both on the Profile tab of the Cloud detail page and in Cypher. When added to a Cloud they create a Cypher entry at path tfvars/profile/cloud/$cloudCode/variables. If a Cloud profile Cypher entry is restricted by a Cypher Access policy, it will be (or will not be) listable/readable/deletable as dictated by the Policy but still will be viewable from the Cloud detail page if the user has sufficient permissions. Restricting or granting access to Cloud profiles via Policy does not affect access on the Cloud. Other Role permissions, such as “Admin: Profiles”, “Infrastructure: Clouds”, and Cloud/Group access must be used to restrict access via Cloud detail pages.
+
+### Example Policy
+
+In my example organization, I have one department that needs access to AWS-related secrets and another department that needs access to Azure-related secrets. There are many other secrets stored in my appliance but I don’t want either of these departments to access any of those.
+
+![../../_images/cypherlist.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E85ADD10-D850-4AC0-B155-027367EC2C47-high.png)
+
+For the first department, I’ve set up a Policy that allows them to list and read (including use and decryption rights) AWS secrets. A second Policy specifically excludes them from seeing one specific entry. The Policy with the more specific path will supersede the more generic Policy that includes a wildcard.
+
+![../../_images/pollist.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1FF1D390-EB0B-4C24-9289-4AF2717D8895-high.png)
+
+By impersonating the user, we see they indeed have access to just the two desired Cypher entries.
+
+![../../_images/user1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3BD14A79-055F-4C2E-AF21-EDE494DAB877-high.png)
+
+For the second department, I have set up a Policy that allows them to list and read (including use and decryption rights) Azure secrets.
+
+![../../_images/cypherlist2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6FD23103-1276-4EBB-AC2A-15440A479D4D-high.png)
+
+By impersonating the user once again, we see they indeed have access only to Azure entries.
+
+![../../_images/user2cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E2E311FD-BE92-4152-A79B-AB71DBA890B9-high.png)
+
+## Expiration Policies
+
+Expiration policies set an expiration timeframe for any instance provisioned into the cloud, role, group or by the user the policy is added to. When an instance expires, it is terminated and deleted.
+
+Configuration options for expiration policies:
+
+Expiration Type
+:   - User Configurable- expiration timeframe is editable during provisioning
+    - Fixed Expiration- user cannot change expiration timeframe
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being removed.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the expiration date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to expire.
+
+Notification Message
+:   Customizable message for notification emails. The default message is `Instance ${instance?.name} is set to expire on ${instance?.expireDate}`
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+Instances with expirations show the time until expiration in the instance detail pane. Instances with active expiration policies can be extended by selecting the EXTEND NOW button in the instance detail pane. The extension length is set in the policy by the RENEWAL DAYS field.
+
+Expirations can also be added to any instance during provisioning by entering the number of days in the EXPIRATION DAYS field in the Lifecycle section of the automation section of the provisioning wizard. Expiration can be added to any instance even if no policies have been created.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Instance and Host Names
+
+Naming Policies will populate a fixed or editable name for instances, hosts and hostnames. The Name Pattern field uses ${variable} string interpolation.
+
+NAMING TYPE
+:   User Configurable
+    :   Naming pattern will pre-populate during provisioning but can be edited by the user.
+
+    Fixed Name
+    :   Naming pattern will pre-populate during provisioning and cannot be changed.
+
+NAME PATTERN
+:   The Name Pattern field uses Static text and/or `${variable}` string interpolation, such as `morpheus${cloudCode}${type}${sequence+3000}`
+
+    An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+    Commonly used variables for naming patterns include:
+
+    ```
+    ```
+    ${groupName}  
+    ${groupCode}  
+    ${cloudName}  
+    ${cloudCode}  
+    ${type}  
+    ${accountId}  
+    ${account}  
+    ${accountType}  
+    ${platform}  
+    ${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+    ${userId}  
+    ${username}  
+    ${userInitials}  
+    ${provisionType}  
+    ${instance.instanceContext} # Environment Code  
+    ${sequence} # results in 1  
+    ${sequence+100} # results in 101  
+    ${sequence.toString().padLeft(5,'0')} #results in 00001
+    ```
+    ```
+
+    Cloud codes and Group codes are fields found in their respective configuration panes.
+
+AUTO RESOLVE CONFLICTS
+:   HPE Morpheus Enterprise will automatically resolve naming conflicts by appending a sequential -number to the name when enabled.
+
+## Shutdown Policies
+
+Shutdown policies dictate the number of days an instance is allowed to run before it is shut down. Shutdown is consistent across cloud types i.e.: in VMware, a VM is powered off. In AWS, an instance is stopped. Etc.
+
+Configuration options for shutdown policies:
+
+Shutdown Type
+:   User Configurable
+    :   Shutdown timeframe is editable during provisioning.
+
+    Fixed Expiration
+    :   User cannot change shutdown timeframe during provisioning.
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being shut down.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the shutdown date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to shut down.
+
+Notification Message
+:   Customizable message for notification email.
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Provision Approval
+
+HPE Morpheus Enterprise Provision Approvals enable an approval workflow via internal HPE Morpheus Enterprise approval or via ServiceNow workflow. If a ServiceNow integration is present, the ServiceNow option is enabled. The Approval workflow to be selected is dynamically created by querying the ServiceNow Workflow table in the integrated ServiceNow instance.
+
+This ServiceNow approval integration enables users to use the HPE Morpheus Enterprise Self-Service provisioning portal to provision new instances and still respect the required ServiceNow business approval workflow.
+
+## Power Schedules
+
+Power Schedules set daily times to shutdown and startup instances. Power schedule can be created and managed in Library > Automation > Power Scheduling
+
+NOTE
+
+Power Schedule Policies will apply to Instances created in a Group or Cloud after the Policy is enabled, and will not apply to pre-existing Instances.
+
+Configuration options for Power Schedule Policies:
+
+DESCRIPTION
+:   Add details about your Policy for reference in the Policies tab.
+
+Enabled
+:   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Groups Instances until re-enabled.
+
+ENFORCEMENT TYPE
+:   - User Configurable: Power Schedule choice is editable by User during provisioning.
+    - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+POWER SCHEDULE
+:   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## Max Resources
+
+Max Resource policies allow setting quotas for Clouds, Groups, Roles or Users for maximum amount of Memory, Storage, Cores, Hosts, VM’s, or Containers that can be created in the Cloud, Group, Role or by the User the Policy is assigned to.
+
+Configuration options for Max Resources Policies:
+
+Max Containers
+:   Sets the maximum combined total of Containers in Instances per Policy Scope.
+
+Max Cores
+:   Sets the maximum combined total of Cores in Instances per Policy Scope.
+
+Max Hosts
+:   Sets the maximum total of Hosts per Policy Scope.
+
+Max Memory
+:   Sets the maximum combined total of RAM (capacity) for Instances per Policy Scope.
+
+Max Storage
+:   Sets the maximum combined total of Storage (capacity) for Instances per Policy Scope.
+
+Max VMs
+:   Sets the maximum total of managed Virtual Machines per Policy Scope.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## User Creation
+
+The User Creation policy controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+Configuration options for User Creation Policies:
+
+TYPE
+:   User Creation
+
+DESCRIPTION
+:   Description to identify the policy config
+
+Enabled
+:   Policies enforcement can be disabled or enabled at any time.
+
+ENFORCEMENT TYPE
+:   - User Configurable: User Creation choice is editable by User during provisioning.
+    - Fixed: User cannot change User Creation setting during provisioning.
+
+CREATE USER
+:   Check to allow or force user creation. Uncheck to disable by default or force no user creation.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json b/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
new file mode 100644
index 0000000..a6f876b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+  "title": "NSX",
+  "ordinal": 509,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html",
+  "topic_cluster": {
+    "clustering_title": "NSX",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md b/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
new file mode 100644
index 0000000..4d32151
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
@@ -0,0 +1,115 @@
+# NSX
+
+## Overview
+
+VMware NSX offers network virtualization allowing for creation and management of software-based virtual networks in an efficient and programmatic way. HPE Morpheus Enterprise offers a full-featured integration with NSX, including Project scoping for NSX 4+ integrations. HPE Morpheus Enterprise will ingest and expose its networking abstractions in the following sections of the HPE Morpheus Enterprise NSX integration:
+
+- SUMMARY
+- TRANSPORT ZONES
+- DHCP
+- SEGMENTS
+- FIREWALL
+- TIER-1 GATEWAYS
+- TIER-0 GATEWAYS
+- EDGE CLUSTERS
+- GROUPS
+
+This guide goes through the process of integrating an existing NSX installation with HPE Morpheus Enterprise and working with the associated objects synced in with the integration. For more on installing NSX and an overview of its concepts, please review the [NSX overview documentation](https://docs.vmware.com/en/VMware-NSX-Data-Center/2.0/com.vmware.nsxt.install.doc/GUID-10B1A61D-4DF2-481E-A93E-C694726393F9.html) provided by VMware.
+
+## NSX Tagging
+
+An NSX integration can apply Instance and VM tags to VMs in NSX, if desired. To apply this, mark the box for “APPLY VM TAGS” when adding or editing an NSX integration.
+
+![../../_images/applyTags.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0DEECD00-D8E9-4B5D-98C9-A07FB86C1CDE-high.png)
+
+Once this configuration is set on the integration, any tags that are applied to applicable Instances through the provisioning wizard at provision time will be applied to those VMs in NSX. In the example below, I’ve set one tag on the new Instance in the provisioning wizard:
+
+![../../_images/setTag.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-806F0064-33EE-43D9-83EB-B8A9BBF0BE93-high.png)
+
+Once provisioning is complete, the tags are confirmed to be visible in the NSX console as well:
+
+![../../_images/showNsx.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-64F1C009-4585-4F84-BBFD-FFD85FEF51D7-high.png)
+
+## NSX Projects
+
+Projects in NSX are analogous to tenants in other products and are a part of NSX version 4+. Projects allow for the isolation of networking abstractions into individual tenants within a single NSX appliance. If your organization is already utilizing NSX Projects, you are probably very familiar with their concept and execution but others can find high-level details about them [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+HPE Morpheus Enterprise supports a full-featured integration with NSX, including the ability to scope the HPE Morpheus Enterprise integration to a specific Project the service user can access. Using Project-scoped integrations allows multiple NSX integrations to be made to the same NSX appliance and ensures HPE Morpheus Enterprise users are siloed to only the NSX Projects they can access.
+
+## Add NSX Integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select Select + ADD > VMWare NSX
+3. Enter the following: 
+
+   - NAME: Name for the NSX Integration in HPE Morpheus Enterprise
+   - VISIBILITY: Public (available to all HPE Morpheus Enterprise Tenants) or Private (available only to the current Tenant). This option is shown only in the HPE Morpheus Enterprise Master Tenant
+   - API HOST: URL of the NSX Manager (ex. <https://x.x.x.x/api>)
+   - CREDENTIALS: A pre-stored credential set can be used to create this integration. If “Local Credentials” is selected, USERNAME and PASSWORD fields are presented and must be filled
+   - USERNAME: NSX service account username. Prior to NSX version 4, this is likely an admin account with access to all networking constructs. In NSX version 4 and higher, this could be an admin for access to default space constructs or it could be a Project-specific user depending on the access needs of the integration being created
+   - PASSWORD: The password for the NSX service account entered above
+   - PROJECT: As soon as an API HOST and credentials are provided, HPE Morpheus Enterprise will attempt to authenticate with the NSX appliance. When authentication is successful and a NSX 4+ appliance is detected, a PROJECT field will appear and the dropdown will be pre-populated with Projects accessible to the service user account
+   - VMWARE CLOUD: Select the existing VMware cloud associated with this NSX integration
+4. Select ADD NETWORK INTEGRATION
+
+### Results
+
+Once the NSX Integration is added HPE Morpheus Enterprise will sync in existing Transport Zones, DHCP servers and relays, Segments, firewall groups and rules, Gateways, Edge Clusters, and Groups. We can manage these synced items from within HPE Morpheus Enterprise UI, including the ability to create, edit, and delete them.
+
+NOTE
+
+The available tabs on the integration detail page will be dependent on the Project selected when the integration was created. Just like in NSX, the default view (and thus integrations scoped to the default Project) will have access to all constructs whereas individual Projects will not. Integrations scoped to individual Projects can view the DHCP, Segments, Firewall, Tier-1 Gateways, and Groups tabs but not the other tabs described here. These limitations are identical to those in the NSX console UI. More information on NSX Projects is available [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+## Summary View
+
+The SUMMARY tab contains the default view when accessing an NSX integration. From the summary view we can see the status of the NSX server, and details about interfaces and group status.
+
+## Transport Zones
+
+Access Transport Zones by selecting the Transport Zones tab. The default view of the Transport Zones tab lists Transport zones and presents some detail about them such as name, traffic type, status, and more. The integration allows for creation of new Transport Zones, editing and deleting.
+
+![../../_images/1tz.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E5021E3F-6EC5-433B-9471-40D7563D0107-high.png)
+
+## DHCP
+
+DHCP servers and relays are displayed on the DHCP tab. View information such as names and server addresses. The integration allows for creation of new servers and relays, editing and deleting.
+
+![../../_images/1dhcp.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B3C32D7F-69D9-462D-9766-55EE13CAD643-high.png)
+
+## Segments
+
+Access Segments by from the Segments tab. The summary view includes high-level information such as status, name, network name and CIDR. The integration allows for creating, editing and deleting NSX Segments
+
+![../../_images/1segments.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D72DEE9B-2CF2-40E3-9256-5C4FE66E2794-high.png)
+
+## Firewall
+
+Firewall Groups and Rules are accessible from the Firewall tab. From the summary view, Groups can be expanded to view Rules within. From the ACTIONS menu, create new Groups by selecting “Create Group”. When a Group has been expanded, the “Create Rule” selection within the ACTIONS menu will also be accessible and a new rule can be created within the selcted Group. The integration allows for viewing, creating, editing and deleting Firewall Groups and Rules.
+
+![../../_images/1firewall.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-04A798AB-AD05-4547-97F6-515C09BE616A-high.png)
+
+## Tier-0 Gateways
+
+Access Tier-0 Gateways from the Tier-0 Gateways tab. The integration allows creating, editing and deleting Tier-0 Gateways.
+
+![../../_images/1t0.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E58BC69D-9E6A-44E7-8181-4B7597235E5F-high.png)
+
+## Tier-1 Gateways
+
+Access Tier-1 Gateways from the Tier-1 Gateways tab. The integration allows creating, editing and deleting Tier-1 Gateways.
+
+![../../_images/1t1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ECFD21E1-3744-46E8-9A14-3A07AE2EA2EB-high.png)
+
+## Edge Clusters
+
+View Edge Clusters from the Edge Clusters tab. The default view lists each Edge Cluster with name, member type, cluster profile, and more. The integration allows viewing and limited editing of Edge Clusters.
+
+![../../_images/1edgeclusters.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-42A4E243-3B5E-45C6-AC05-01E63382D520-high.png)
+
+## Groups
+
+NSX Groups are viewed from the Groups tab. The default view lists each Group alone with member details. The HPE Morpheus Enterprise NSX integration allows for creating, editing and deleting Groups.
+
+![../../_images/1groups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C6C0EDD3-C289-4A0A-B449-038EF1E08D17-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json b/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
new file mode 100644
index 0000000..de79f58
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+  "title": "Mac Stadium",
+  "ordinal": 462,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-06D232B4-F473-44C5-AD24-AECD128273E5.html",
+  "topic_cluster": {
+    "clustering_title": "Mac Stadium",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md b/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
new file mode 100644
index 0000000..3e1dd2c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
@@ -0,0 +1,136 @@
+# Mac Stadium
+
+## Overview
+
+MacStadium is a provider of enterprise-class hosting solutions for Apple Mac infrastructure. It can be used to deploy a hosted private cloud for large-scale CI/CD or even a single Mac mini to test an iOS app. It allows virtualized Mac build machines
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json b/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
new file mode 100644
index 0000000..f677c25
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+  "title": "To create a Tenant Role:",
+  "ordinal": 306,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html",
+  "topic_cluster": {
+    "clustering_title": "To create a Tenant Role:",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md b/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
new file mode 100644
index 0000000..93c7423
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
@@ -0,0 +1,14 @@
+# To create a Tenant Role:
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “Tenant Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select SAVE CHANGES
+
+## Results
+
+After saving, the Role will be created and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json b/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
new file mode 100644
index 0000000..29d56f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+  "title": "Workloads: Blueprint Usage",
+  "ordinal": 69,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Blueprint Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md b/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
new file mode 100644
index 0000000..7ff060f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
@@ -0,0 +1,32 @@
+# Workloads: Blueprint Usage
+
+![../_images/11blueprintusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C67DA833-C730-4887-9672-7E63FABC0841-high.png)
+
+The Blueprint Usage dashboard lists all provisioned Apps that meet filters set on the dashboard. Once the desired group of Apps is filtered into the dashboard, administrators will see the total provisioned from each Blueprint, total number of Instances created from the Apps, and costing details.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **TYPES:** The total number of App types represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **MONTH TO DATE:** The total month-to-date spend for all Apps shown in the dashboard
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Blueprint Usage List
+
+All Blueprints which have a currently-existing App provisioned from them and selected in the dashboard filters are listed here. The name and type of the Blueprint is listed along with the total number of Instances across all provisionings, total Groups, total Clouds, and the total count of all Apps from that Blueprint.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json b/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
new file mode 100644
index 0000000..ffba1aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+  "title": "Docker Clusters",
+  "ordinal": 199,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md b/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
new file mode 100644
index 0000000..e2782a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
@@ -0,0 +1,71 @@
+# Docker Clusters
+
+## About this task
+
+Provisions a new Docker Cluster managed by Morpheus.
+
+To create a new Docker Cluster:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Docker Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Docker Cluster
+
+   RESOURCE NAME
+   :   Name for Docker Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+5. Select NEXT
+6. Populate the following (options depend on Cloud Selection and will vary): 
+
+   LAYOUT
+   :   Select from available layouts.
+
+   PLAN
+   :   Select plan for Docker Host
+
+   VOLUMES
+   :   Configure volumes for Docker Host
+
+   NETWORKS
+   :   Select the network for Docker Master & Worker VM’s
+
+   NUMBER OF HOSTS
+   :   Specify the number of hosts to be created
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+7. Select NEXT
+8. Select optional Workflow to execute
+9. Select NEXT
+10. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json b/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
new file mode 100644
index 0000000..bd18b0a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+  "title": "Volume Management",
+  "ordinal": 442,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md b/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
new file mode 100644
index 0000000..4110d2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
@@ -0,0 +1,10 @@
+# Volume Management
+
+Volume life cycle management can be performed under the Infrastructure > Storage > Volumes tab. It allows the user to perform create/resize/delete operations.
+
+**Subtopics**  
+
+- **[Adding Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html)**
+- **[Deleting Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html)**
+- **[Resizing Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html)**
+- **[Reconfiguring Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json b/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
new file mode 100644
index 0000000..15c2314
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+  "title": "Adding OpenShift Clusters",
+  "ordinal": 207,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html",
+  "topic_cluster": {
+    "clustering_title": "Adding OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md b/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
new file mode 100644
index 0000000..05dd0ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
@@ -0,0 +1,24 @@
+# Adding OpenShift Clusters
+
+NOTE
+
+Adding an OpenShift cluster requires a pre-existing Group and Private Cloud-type Cloud. See Groups and Clouds documentation elsewhere in this user manual for more details on those constructs.
+
+To onboard an OpenShift cluster, begin by collecting an API token and API URL from OpenShift. Bear in mind the integration user with HPE Morpheus Enterprise must be a full administrator user.
+
+1. Log into the OpenShift console
+2. In the far top-right of the application window, click on the name of the logged in user to expand a small dropdown menu
+3. Click "Copy login command"
+4. Click "Display Token"
+5. On the resulting screen, both the API URL and the API token can be copied. You will need to enter these values directly into the "Add Cluster" modal within HPE Morpheus Enterprise in the next step
+
+With the authentication details available, head back to HPE Morpheus Enterprise to add a new OpenShift cluster:
+
+1. Navigate to Infrastructure > Clusters
+2. Click + Add Cluster
+3. Select "RED HAT OPENSHIFT CLUSTER" and click Next
+4. On the Group tab, select the HPE Morpheus Enterprise Group to associate with the cluster and click Next
+5. On the Name tab, you must at least configure a "Cluster Name" attribute and select a Cloud. The "Cluster Name" is a friendly name to identify the OpenShift cluster in HPE Morpheus Enterprise. The Cloud configuration requires you to select a pre-existing Private Cloud-type Cloud. There are optional configurations here as well, such as applying Labels or adding a description
+6. On the Configure tab, select the Layout that corresponds closest to the version of OpenShift running on the cluster. Integration with HPE Morpheus Enterprise requires OpenShift version 4.x at minimum. On this tab, you'll also enter the API URL and service token collected earlier. If "Inventory Existing Instances" is checked, HPE Morpheus Enterprise with automatically onboard any virtualized workloads which are currently running on the cluster and any that are provisioned directly from the OpenShift console in the future. Click Next
+7. On the Review tab, click Complete
+8. Within a short time, the new OpenShift cluster will appear on the clusters list page alongside any other cluster that may currently be running
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json b/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
new file mode 100644
index 0000000..5617332
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+  "title": "Common Ports & Requirements",
+  "ordinal": 350,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md b/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
new file mode 100644
index 0000000..512d7ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | DNS Resolution from node to appliance url Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node | user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node | user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..3e01cee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 287,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..1022a17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,8 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html)**
+- **[Price Sets](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html)**
+- **[Prices](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..a82b630
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 328,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..72b30f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,34 @@
+# Environments
+
+## Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+### Creating Environments
+
+#### Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in HPE Morpheus Enterprise
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+   Visibility
+   :   - Private: Available only in the Tenant the environment is created in
+       - Public: Available for all Tenants. Public is only applicable for environments created in the the Master Tenant.
+
+#### Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. HPE Morpheus Enterprise-default environments can only be hidden from users during provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json b/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
new file mode 100644
index 0000000..d115de4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+  "title": "Wiki",
+  "ordinal": 72,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md b/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
new file mode 100644
index 0000000..d655f94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
@@ -0,0 +1,50 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, Clusters, and Self-Service Persona Catalog Items. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations  >  Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+## Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, Bare Metal, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations  >  Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations  >  Wiki
+- One Wiki is created per Tenant. There is no multi-tenant access to Wikis
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in User and Tenant Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with HPE Morpheus Enterprise
+
+NOTE
+
+The Wiki replaces Notes. Notes are automatically migrated to corresponding Wiki pages when upgrading HPE Morpheus Enterprise to 4.0.0+.
+
+## Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many HPE Morpheus Enterprise constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
+
+## Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the HPE Morpheus Enterprise appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The HPE Morpheus Enterprise [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the HPE Morpheus Enterprise appliance local storage. HPE Morpheus Enterprise generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in HPE Morpheus Enterprise Archives within your Wiki pages.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json b/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
new file mode 100644
index 0000000..a0c71e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+  "title": "Uploading OS Images Using NFS",
+  "ordinal": 411,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using NFS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md b/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
new file mode 100644
index 0000000..240c9c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using NFS
+
+## About this task
+
+NFS allows OS images to be stored on a shared Linux file server.
+
+## Procedure
+
+1. Configure an NFSv3 file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the NFS share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json b/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
new file mode 100644
index 0000000..ff87037
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+  "title": "Import Trusted Certificates",
+  "ordinal": 35,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html",
+  "topic_cluster": {
+    "clustering_title": "Import Trusted Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md b/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
new file mode 100644
index 0000000..87790cb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
@@ -0,0 +1,61 @@
+# Import Trusted Certificates
+
+## About this task
+
+IMPORTANT
+
+The following applies to upgrades after modifying the java keystore.
+
+Steps to import trusted certificates to HPE Morpheus Enterprise after an upgrade.
+
+## Procedure
+
+1. Obtain the full SSL certificate chain in PEM format.
+2. Copy them to each appliance and place them in the `/etc/morpheus/ssl/trusted_certs` directory.
+3. Run morpheus-ctl reconfigure on each appliance, note you don’t need to stop Morpheus before you run this.
+4. Run the following command as root: 
+
+   ```
+   ```
+   export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
+   ```
+   ```
+5. Run the following command for each certificate in the chain, adjusting the file and alias name as needed. Answer yes for the root certificate when asked it you want to trust it. 
+
+   ```
+   ```
+   /opt/morpheus/embedded/java/jre/bin/keytool -import -keystore /opt/morpheus/embedded/java/jre/lib/security/cacerts -trustcacerts -file /etc/morpheus/ssl/trusted_certs/root_ca.pem -alias some_alias -storepass changeit
+   ```
+   ```
+6. Verify by running: 
+
+   ```
+   ```
+   openssl s_client -connect host:port -showcerts -tls1_2
+   ```
+   ```
+7. You should get an output similar to: 
+
+   ```
+   ```
+   New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384  
+   Server public key is 2048 bit  
+   Secure Renegotiation IS supported  
+   No ALPN negotiated  
+   SSL-Session:  
+   Protocol : TLSv1.2  
+   Cipher  : ECDHE-RSA-AES256-GCM-SHA384  
+   Session-ID: 5D9E820E4FF2A73A9977BA663E6029AA5415FEE85F49D8B1E541F5997C8E1FB2  
+   Session-ID-ctx:  
+   Master-Key: 29EEC2E7750C659AECB9942902D9A87B824E571522812B718420FC08F8D2ACE68CB16EC812A7D90B12A86D1970FFD81C  
+   Key-Arg  : None  
+   PSK identity: None  
+   PSK identity hint: None  
+   SRP username: None  
+   Start Time: 1547219217  
+   Timeout  : 7200 (sec)  
+   Verify return code: 0 (ok) #<----------------
+   ```
+   ```
+8. If the certificates are installed correctly you should see `Verify return code: 0 (ok)`. If they were not installed correctly then you will see a return similar to: `Verify return code: 21 (unable to verify the first certificate)`
+9. Repeat for all App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json b/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
new file mode 100644
index 0000000..d4e2b9e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+  "title": "EfficientIP SOLIDserver",
+  "ordinal": 517,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html",
+  "topic_cluster": {
+    "clustering_title": "EfficientIP SOLIDserver",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md b/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
new file mode 100644
index 0000000..32704d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
@@ -0,0 +1,113 @@
+# EfficientIP SOLIDserver
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+
+## Required Role Permissions
+
+### Add, edit and remove EfficientIP SOLIDserver integrations
+
+- Infrastructure: Network Integration: Full
+
+### View and edit synced IP pools
+
+- Infrastructure: Network IP Pools: Full
+
+### View networks and add synced IP pools to networks
+
+- Infrastructure: Networks: Full or Group
+
+### View and edit synced DNS zones, including creation of zone records
+
+- Infrastructure: Network Domains: Full
+
+## Adding EfficientIP SOLIDserver Integration
+
+### About this task
+
+The EfficientIP SOLIDserver integration type is a plugin that must be added to HPE Morpheus Enterprise before the option to create one will be available. In the future, users will be able to download this and other plugin types from a centralized marketplace. For now, the plugin jar file can be compiled from a public Github repository or can be requested from your account team. See the [Plugins Section](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) of HPE Morpheus Enterprise documentation for more on the process of uploading the plugin JAR to your appliance.
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations and click + ADD
+2. Under the IPAM section, select EfficientIP SOLIDserver
+3. Configure the following: 
+
+   - NAME: Friendly name for this EfficientIP SOLIDserver integration
+   - ENABLED: When checked, this integration will be accessible in HPE Morpheus Enterprise
+   - API URL: The FQDN for the EfficientIP server, not a specific path
+   - USERNAME: The username for an EfficientIP service account. Bear in mind this account will need API access as well as the rights to work with pools, zones, and records you wish to consume from HPE Morpheus Enterprise
+   - PASSWORD: The password for the above named account
+   - THROTTLE RATE: In larger environments, it may be necessary to introduce a rate limit on calls to the EfficientIP API from HPE Morpheus Enterprise. If the EfficientIP console UI becomes less responsive than it was prior to integration with HPE Morpheus Enterprise, it may be due to a high number of API calls in the background from HPE Morpheus Enterprise. In such a case, start with a 50ms throttle rate and adjust accordingly depending on performance
+   - DISABLE SSL SNI VERIFICATION: If necessary, disable the check for a valid SSL certificate on the EfficientIP server
+   - INVENTORY EXISTING: When checked, used IP space will be continually synced between HPE Morpheus Enterprise and EfficientIP. If left unchecked, only IP space claimed (and freed) from HPE Morpheus Enterprise is shown on the detail page for the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+Once saved, HPE Morpheus Enterprise will begin to onboard data from EfficientIP. EfficientIP networks are viewable in Infrastructure > Network > IP Pools under the IP Pools tab. Depending on EfficientIP configuration, you may see up to two “types” of Network Pools sync from EfficientIP, SOLIDserver Subnet and SOLIDserver Pool. In EfficientIP, “pools” are an optional construct that subdivides subnets. In HPE Morpheus Enterprise, both constructs are synced which gives an additional layer of organization when linking Network Pools with Networks (described in the next section) for organizations that use the pools construct. Within a selected IP Pool, host records will also sync and can be viewed in a grid or list layout. DNS Zones are synced under Infrastructure > Network > Domains. By clicking into the domain, DNS Zone records can be viewed.
+
+![../../_images/pool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8125D46A-139B-415D-A7F1-C47CE46A6FD8-high.png)
+
+## Adding IP Pools to Networks
+
+### About this task
+
+At provision time, HPE Morpheus Enterprise can automatically assign the next available IP address in an EfficientIP pool and create the corresponding DNS records. HPE Morpheus Enterprise can also clean up DNS records and free up IP address space on teardown. In order to enable this functionality, add an EfficientIP IP Pool as the Network Pool for an existing network (or networks).
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select a network to view the network detail page and click EDIT
+3. In the typeahead field for NETWORK POOL, search for and select the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Gateway, DNS and CIDR must be populated for static/pool IP assignment. If desired, select “Allow IP Override” to allow selecting between DHCP, Static entry, and pool selection at provision time. Finally, deselect “DHCP server” if a DHCP server will not be used on the network (only static and/or IP Pool assignment).
+
+## Creating Host Records
+
+### Procedure
+
+1. Select an EfficientIP Network Pool from Infrastructure > Network > IP Pools
+2. Select + ADD
+3. Configure the following:
+
+### Results
+
+- **HOSTNAME:** The hostname for the record
+- **IP ADDRESS:** The IP address for the host record
+- **DOMAIN:** Select an EfficientIP zone
+- **CREATE DNS RECORDS:** If selected, DNS A and PTR records will be created in EfficientIP
+
+1. Click SAVE CHANGES
+
+![../../_images/createhost.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-327856E4-74AE-4477-87F4-DF8DB6390B2F-high.png)
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select an EfficientIP zone from the domains list at Infrastructure > Network > Domains
+2. Click + ADD on the Zone Records tab
+3. Configure the following:
+
+### Results
+
+- **NAME:** The name for the records (hostname)
+- **TYPE:** The record type: A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+- **CONTENT:** The content of the record, such as IP address or A record
+- **TTL:** The time to live value
+
+1. Click SAVE CHANGES
+
+![../../_images/createzone.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C64B7661-39C6-4ED3-A6C7-0C57521C7794-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json b/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
new file mode 100644
index 0000000..7feabeb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+  "title": "Common Ports & Requirements",
+  "ordinal": 8,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md b/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
new file mode 100644
index 0000000..af2ddc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | Not required for agent installation in VMware vCenter and vCloud Director type clouds. Otherwise, access from HPE Morpheus Enterprise App Nodes to Instance Node on 5985 Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json b/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
new file mode 100644
index 0000000..fe6cd73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+  "title": "Adding HPE BMaaS Integration",
+  "ordinal": 401,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE BMaaS Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md b/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
new file mode 100644
index 0000000..5fdf61d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
@@ -0,0 +1,21 @@
+# Adding HPE BMaaS Integration
+
+## Prerequisites
+
+This procedure describes how to integrate the HPE BMaaS with your Morpheus Enterprise environment.
+
+## About this task
+
+To install the **HPE BMaaS** plugin, perform the following steps:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Administration > Integrations.
+3. Select the Plugins tab and click Add button.
+4. Drag the HPE BMaaS `JAR` file into the Drop Files Here area, or click Add File to select it manually. ![Add Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4551F618-EBCF-470F-80C1-64A815379B94-high.png)
+5. Click the Upload.
+
+## Results
+
+After a successful upload, the HPE BMaaS is available for use.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json b/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
new file mode 100644
index 0000000..637d7bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+  "title": "Creating and Running an SPP Update Job",
+  "ordinal": 426,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running an SPP Update Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md b/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
new file mode 100644
index 0000000..e822246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
@@ -0,0 +1,54 @@
+# Creating and Running an SPP Update Job
+
+## About this task
+
+This procedure describes how to create and execute a HPE Morpheus Job to perform firmware and driver updates using an HPE SPP image.
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs.
+2. Click Add.
+3. Enter a name for the job.
+
+   NOTE
+
+   - Separate jobs are required for different server generations (for example, Gen10 vs Gen11).
+   - Create separate jobs for **Dry Run** and **Deploy** executions.
+4. Select Workflow Job as the Job Type and click Next.
+5. Select Deploy SPP as the workflow.
+6. Enter the SPPVIRTUALIMAGE value using the ID of the Virtual Image created earlier.
+7. Select a DEPLOYMODE:
+
+   - `DryRun`: Performs inventory only
+   - `Deploy`: Applies firmware and/or driver updates
+8. For SPP Deploy Content, choose one of the following:
+
+   - Firmware only
+   - Drivers only
+   - Firmware and Drivers
+
+   NOTE
+
+   Driver inventory and updates require iSUT and AMS to be running on the target servers.
+9. In the Nodes field, enter the iLO details for each target server in JSON format (minimum 1 server, maximum 30 servers). For example:
+
+   ```
+   ```
+   [  
+     {  
+       "ilo_ip":"1.2.3.4",  
+       "ilo_user":"user1",  
+       "ilo_password":"password1"  
+     },  
+     {  
+       "ilo_ip":"1.2.3.5",  
+       "ilo_user":"user2",  
+       "ilo_password":"password2"  
+     }  
+   ]
+   ```
+   ```
+10. **Optional:**  Create a schedule, or leave the job as Manual.
+11. Select Run Now if you want to execute the job immediately.
+12. Click Next, review the settings, and click Complete.
+13. If the job was not run immediately, click the **gear icon** next to the job and select Execute.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json b/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
new file mode 100644
index 0000000..4e6518d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+  "title": "Jobs",
+  "ordinal": 91,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md b/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
new file mode 100644
index 0000000..98750ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
@@ -0,0 +1,19 @@
+# Jobs
+
+## Required Role Permissions
+
+Provisioning: Jobs
+
+- **None:** Cannot access Provisioning > Jobs > Jobs tab
+- **Read:** Can access Provisioning > Jobs > Jobs tab but cannot create, edit, or delete Jobs
+- **Full:** Full permissions to create, view, edit, and delete Jobs
+
+Provisioning: Job Executions
+
+- **None:** Cannot access Provisioning > Jobs > Job Executions tab
+- **Read:** Can access and view Provisioning > Jobs > Job Executions tab including job execution history, status, and Job output
+
+**Subtopics**  
+
+- **[Creating Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html)**
+- **[Creating and Running Security Scan Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json b/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
new file mode 100644
index 0000000..8d3df97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+  "title": "Clients",
+  "ordinal": 327,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html",
+  "topic_cluster": {
+    "clustering_title": "Clients",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md b/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
new file mode 100644
index 0000000..b50046f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
@@ -0,0 +1,24 @@
+# Clients
+
+## Overview
+
+HPE Morpheus Enterprise includes pre-configured OAuth clients and allows the user to create as many additional clients as they’d like. The pre-configured clients are editable but cannot be deleted. Once configured, access tokens may be generated or re-generated from the [API Access section](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html). Their expiration times may be viewed as well. Client settings are available only in the Primary Tenant and affect all Tenants.
+
+## Creating an OAuth Client
+
+To create a new OAuth Client, click + ADD and configure the following:
+
+- **CLIENT ID:** A reference name for the client in HPE Morpheus Enterprise
+- **SECRET:** An optional OAuth client secret
+- **ACCESS TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the token should be enabled
+- **REFRESH TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the refresh token should be enabled
+
+Once the client is configured, click SAVE CHANGES.
+
+## Editing and Deleting OAuth Clients
+
+From the OAuth client list view (Administration > Settings > Clients), click the pencil (✎) or trash can (🗑) icons to edit or delete the OAuth Client.
+
+NOTE
+
+Pre-configured HPE Morpheus Enterprise-default clients may be edited but not deleted. User-created clients may be edited or deleted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..083bbfd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 195,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..10cdcb6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json b/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
new file mode 100644
index 0000000..a28cfc7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+  "title": "Blueprints",
+  "ordinal": 125,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md b/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
new file mode 100644
index 0000000..9d53c03
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
@@ -0,0 +1,12 @@
+# Blueprints
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html)**
+- **[Blueprint Development Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html)**
+- **[Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html)**
+- **[Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html)**
+- **[Node Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html)**
+- **[App Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html)**
+- **[Catalog Items](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html)**
+- **[Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..7d30efa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 337,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..16d9185
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json b/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
new file mode 100644
index 0000000..4ce4359
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+  "title": "Spec Templates",
+  "ordinal": 159,
+  "parent_title": "Templates",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html",
+  "topic_cluster": {
+    "clustering_title": "Spec Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md b/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
new file mode 100644
index 0000000..e3ba103
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
@@ -0,0 +1,35 @@
+# Spec Templates
+
+Spec Templates allow HPE Morpheus Enterprise users to leverage several major Infrastructure-as-Code solutions. These are typically JSON or YAML-based configuration files which make creating and managing multiple resource types easier. HPE Morpheus Enterprise allows users to create and/or manage a collection of these templates for different solutions and from different sources.
+
+HPE Morpheus Enterprise currently supports Spec Templates of the following types:
+
+- Kubernetes Spec
+- Helm Chart
+- Terraform
+- ARM Template
+- CloudFormation Template
+- OneView Server Profile Template
+- UCS Service Profile Template
+
+HPE Morpheus Enterprise also allows users to leverage templates pulled from URL sources, online repositories (such as GitHub), or you can write a template locally inside the “NEW SPEC TEMPLATE” modal.
+
+TIP
+
+To see HPE Morpheus Enterprise Spec Templates in action, take a look at our guide on [creating custom Instance Types using Terraform](https://docs.morpheusdata.com/en/latest/getting_started/guides/terraform_instances.html) or see our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-use-Spec-Templates-to-create-a-custom-instance-type?language=en_US) for another example where a CloudFormation Spec Template is used to create a provisionable custom Instance Type.
+
+## Creating a Spec Template
+
+### Procedure
+
+1. Navigate to Library > Templates > Spec Templates
+2. Click + ADD
+3. Complete the following fields, then click SAVE CHANGES:
+
+### Results
+
+- **NAME**
+- **TYPE:** See the previous section for a complete list of Spec Template types
+- **SOURCE:** Local, Repository, or URL
+- **CONTENT:** If this is a local Spec Template, supply the template in this field. If the template is supplied through a URL or online repository, the CONTENT field will change to allow the user to point HPE Morpheus Enterprise to that resource
+- **VERSION:** (Only displayed on Terraform Spec Templates) Enter a Terraform version number to force a specific version when provisioning your Terraform Instance Type or App, assuming your Terraform Runtime setting (Administration > Settings > Provisioning Tab) is “auto”. If Terraform Runtime is set to “manual”, HPE Morpheus Enterprise will use the version of Terraform installed on the appliance box
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json b/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
new file mode 100644
index 0000000..14f0f68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+  "title": "App Blueprints",
+  "ordinal": 131,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md b/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
new file mode 100644
index 0000000..07190e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
@@ -0,0 +1,20 @@
+# App Blueprints
+
+App Blueprints support a vast array of providers and configurations with programmatic markup or Infrastructure as Code capabilities. Blueprints configs can be manually added or scoped to a git repo. HPE Morpheus Enterprise blueprints allows for full automation configuration, locked fields, tiered boots, and linked tiers with exported evars. All blueprints have permission settings for controlling group and tenant access.
+
+App Blueprint Types
+:   - HPE Morpheus Enterprise
+    - Terraform
+    - ARM (Azure)
+    - CloudFormation (AWS)
+    - Kubernetes
+    - Helm
+
+**Subtopics**  
+
+- **[ARM Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html)**
+- **[CloudFormation Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html)**
+- **[Helm Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html)**
+- **[Kubernetes Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html)**
+- **[HPE Morpheus Enterprise Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html)**
+- **[Terraform Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json b/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
new file mode 100644
index 0000000..ef05312
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+  "title": "Huawei Cloud",
+  "ordinal": 458,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.html",
+  "topic_cluster": {
+    "clustering_title": "Huawei Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md b/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
new file mode 100644
index 0000000..426a840
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
@@ -0,0 +1,306 @@
+# Huawei Cloud
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- Huawei OBS buckets (create, manage, delete, and discovery)
+- Huawei SFS (create, manage, and delete)
+
+## Integrate Huawei Cloud with HPE Morpheus Enterprise
+
+To integrate Huawei Cloud with HPE Morpheus Enterprise, we’ll gather the following pieces of information:
+
+- Account Name
+- Identity (IAM) API URL
+- Project
+- Username
+- Password
+
+Begin by logging into your [Huawei Cloud console](https://console-intl.huaweicloud.com/console). If you’re not currently logged in, you will be prompted to do so. Once on the console page, hover over your username in the upper-right corner of the application window and select “My Credentials”.
+
+![../../../_images/1credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-073462C5-393F-4B31-B939-5DB39532766C-high.png)
+
+From the credentials page, we can gather the Account Name and the Project Name, record them for later when we provide the integration information to HPE Morpheus Enterprise.
+
+![../../../_images/2account_project.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0EA453C5-849B-4F01-AA40-AEDFFCC3A737-high.png)
+
+To gather the API endpoint URL, take a look at the complete list of [endpoints](https://developer.huaweicloud.com/en-us/endpoint). If a specific endpoint exists for your region, use it. In any other case use the endpoint for all regions. It will be formatted like this: <https://iam.myhuaweicloud.com/v3>.
+
+![../../../_images/3identity_api_endpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8DEF10C6-F6CD-4E55-9D76-D67AA280E6CF-high.png)
+
+With this information gathered, and presuming you know the credentials for the service account you wish to use, we can move back into HPE Morpheus Enterprise-UI.
+
+IMPORTANT
+
+Integrating HPE Morpheus Enterprise with Huawei Cloud requires a service account that has programmatic access.
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Huawei Cloud and click NEXT. The information we’ve gathered will be plugged into the CREATE CLOUD modal. The DOMAIN ID field will accept the Account Name field we gathered. Your completed CREATE CLOUD modal will look similar to the one pictured below:
+
+![../../../_images/4add_cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-029DC867-5A63-4F28-9423-F5C3C5C2141F-high.png)
+
+After clicking NEXT, add this new Cloud to a Group or create a new Group. On finalizing the wizard, Huawei Cloud will be integrated into HPE Morpheus Enterprise and ready for provisioning. If you opted to inventory existing workloads, those will be onboarded shortly.
+
+## Add/Edit Huawei Cloud Modal Fields
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity endpoint. See the integration steps above for more detail
+
+DOMAIN ID
+:   The DOMAIN ID field takes the “Account Name” as shown on the [Basic Informati](https://account-intl.huaweicloud.com/usercenter/?locale=en-us#/userindex/accountInfo) of the account. See the integration steps above for more detail
+
+PROJECT
+:   The target project name. See the integration steps above for more detail
+
+USERNAME
+:   The service account username. See the integration steps above for more detail
+
+PASSWORD
+:   The integration service account password. See the integration steps above for more detail
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK image type
+
+Image Store
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VMs
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment.
+
+TIP
+
+When using the RAW image format, you can bypass the image conversion service within the cloud leading to quicker performance. Other image formats are converted to RAW format and back when performing various actions. Using the RAW format from the start will bypass these conversion steps.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Huawei Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud includes the capability to work with Huawei Scalable File Service (SFS). SFS is shared file storage hosted on Huawei Cloud. By integrating HPE Morpheus Enterprise with Huawei Cloud you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Huawei Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Huawei Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+![../../../_images/1editServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DD161EBC-E99E-449A-8B3E-BA8C021C3670-high.png)
+
+Additionally, Huawei SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click + ADD to begin and set the storage server type value to “Huawei SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/2addServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E7F8C4A2-D408-4C34-9C04-C9C7C27A20F0-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to file shares displayed to those whose names match the search terms.
+
+![../../../_images/3shareList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9FD9B522-BF4F-42A5-A282-16726D330F86-high.png)
+
+We can drill into individual file shares by clicking on their hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking + ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+A “Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Huawei SFS file shares can be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking + ADD. Select the type “Huawei SFS Share”. Set the storage service field to a pre-existing Huawei SFS server. A friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones are required fields.
+
+![../../../_images/4addShare.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E135CE4B-C1C8-44C1-9F18-328901E4C10F-high.png)
+
+## Huawei Object Storage Service (OBS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud also supports Object Storage Service (OBS). HPE Morpheus Enterprise will automatically onboard existing OBS servers and buckets shortly after completing the cloud integration. Before you can add a new OBS server from HPE Morpheus Enterprise, you must know or generate a key and secret value from the Huawei console and must provide a Huawei OBS API endpoint.
+
+### Generate a Key and Secret
+
+From the Huawei web console, log into the account used to integrate Huawei Cloud with HPE Morpheus Enterprise. Hover over your account name in the upper-right corner of the application window and click “My Credentials”. Select “Access Keys” from the left-hand sidebar. To create a new key, click + Create Access Key. Complete the two-factor authentication steps in the box that appears.
+
+![../../../_images/1createKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4FC170FA-49EF-4072-A6F4-42311AB880D9-high.png)
+
+Once the key is generated, download or record the key and store it in a safe location. The key will not be viewable or available for download again after this point.
+
+### Create OBS Server in HPE Morpheus Enterprise
+
+With the key and secret value in hand from the previous section, navigate to Infrastructure > Storage > Servers. Click + ADD. On changing the server type to Huawei OBS, you will see the fields for the access key and the secret key. OBS API endpoints can be found in [Huawei endpoint documentation](https://developer.huaweicloud.com/en-us/endpoint). Include those three values in the Create Server modal along with a friendly name for use in HPE Morpheus Enterprise UI. Just like with SFS objects, we can choose to scope the server to all or specific Tenants at this time.
+
+![../../../_images/2addObsServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BFC92FBB-94A2-46A8-ABFC-E7397C7C6E9E-high.png)
+
+### Create Huawei OBS Bucket
+
+With an OBS server onboarded or created in HPE Morpheus Enterprise, you’re able to create and manage Huawei OBS buckets as needed. To create a new bucket, navigate to Infrastructure > Storage > Buckets. Click + ADD and select “Huawei OBS Bucket”. The following fields are required when creating a Huawei OBS bucket:
+
+- **NAME**: A friendly name for use in HPE Morpheus Enterprise UI
+- **STORAGE SERVICE**: Choose the OBS server to associate the new bucket with
+- **BUCKET NAME**: The name of the bucket in Huawei Cloud, this must be unique
+- **STORAGE CLASS**: If needed, view the [discussion of storage classes](https://support.huaweicloud.com/en-us/eu-west-0-usermanual-obs/en-us_topic_0050937852.html) in Huawei support documentation
+- **BUCKET ACL**: Public Read, Public Read/Write, or Private
+- **BUCKET POLICY**: Public Read, Public Read/Write, or Private
+- **STORAGE QUOTA**: Set to 0 for no quota
+
+Once finished, click SAVE CHANGES
+
+![../../../_images/3createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6A0E3B1B-0B05-4CA3-BBF6-E319A6DD6390-high.png)
+
+## Network and Router Creation
+
+Once a Huawei Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Huawei Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Huawei Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Huawei Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the Huawei project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json b/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
new file mode 100644
index 0000000..16c9346
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 238,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md b/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
new file mode 100644
index 0000000..03f2f8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
@@ -0,0 +1,22 @@
+# OAuth 2.0 Credentials
+
+HPE Morpheus Enterprise supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how HPE Morpheus Enterprise should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+With the OAuth 2.0 credential set stored, they can be set on REST-type Option Lists to source data from behind a compatible authentication wall. With a REST-type Option List open (Library > Options > Option Lists), click the CREDENTIALS dropdown and select the credential set you’ve created. Alternatively, you can add a credential set directly in the add/edit Option List modal if needed. Option Lists can be associated with Select List or Typeahead-type Inputs and applied to Layouts, Instance Types, Workflows, and more to allow for customization at provision or Workflow execution time. Additional details on creating Option Lists can be found in the Library section of HPE Morpheus Enterprise docs.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json b/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
new file mode 100644
index 0000000..0e073be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+  "title": "Advanced morpheus.rb Settings",
+  "ordinal": 30,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced morpheus.rb Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md b/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
new file mode 100644
index 0000000..c15d7e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
@@ -0,0 +1,124 @@
+# Advanced morpheus.rb Settings
+
+Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work.
+
+```
+```
+app['encryption_key_suffix'] = '$suffix'  
+  # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+appliance_url 'https://morpheus.appliance-url.com'  
+  # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+  # The appliance_url cannot exceed 64 characters  
+  # The appliance_url must not contain a trailing `/`.  
+bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+opensearch['auth_user'] = 'morpheus-es-user'  
+opensearch['enable'] = true  
+opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+opensearch['host'] = "127.0.0.1"  
+opensearch['port'] = "9200"  
+opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+opensearch['use_tls'] = false  
+↓ The following Opensearch settings are only valid for Internal/Embedded Opensearch services  
+opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+opensearch['memory_alloc_arena_max'] = 2  
+opensearch['memory_map_max'] = 65536  
+opensearch['memory_map_threshold'] = 131072  
+opensearch['memory_top_pad'] = 131072  
+opensearch['memory_trim_threshold'] = 131072  
+opensearch['open_files'] = 204800  
+opensearch['secure_mode'] = false  
+opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+opensearch['xmx'] = 0.25  
+guacd['guacamole_enabled'] = false  
+guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+mysql['enable'] = true  
+mysql['host'] = {'127.0.0.1' => 3306}  
+mysql['use_tls'] = false  
+mysql['morpheus_db_user'] = 'morpheus-db-user'  
+mysql['morpheus_password'] = 'morpheus-db-password'  
+mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+mysql['tmp_dir'] = '/tmp/mysql'  
+mysql['log_dir'] = '/var/log/morpheus/mysql'  
+mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+mysql['max_connections'] = 151  
+mysql['max_allowed_packet'] = 67108864  
+mysql['mysql_connect_timeout'] = 60000  
+mysql['mysql_max_reconnects'] = 2  
+mysql['mysql_queries_before_retry_source'] = 0  
+mysql['mysql_seconds_before_retry_source'] = 300  
+nginx['cache_max_size'] = '5000m'  
+nginx['enable'] = true  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['max_loops'] = 60 # seconds  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['log_format_name'] = 'custom'  
+nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+nginx['ssl_company_name'] = "Morpheus, LLC"  
+nginx['ssl_country_name'] = "US"  
+nginx['ssl_email_address'] = "personal@email.com"  
+nginx['ssl_locality_name'] = "San Mateo"  
+nginx['ssl_organizational_unit_name'] = "DevOps"  
+nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+nginx['ssl_session_timeout'] = "5m"  
+nginx['ssl_state_name'] = "CA"  
+nginx['worker_connections'] = 10240  
+nginx['workers'] = integer calculated from number of cpus  
+nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+rabbitmq['enable'] = true  
+rabbitmq['host'] = '127.0.0.1'  
+rabbitmq['port'] = '5672'  
+rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+rabbitmq['vhost'] = 'morpheus'  
+↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+rabbitmq['heartbeat'] = nil  
+rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+rabbitmq['nodename'] = 'rabbit@localhost'  
+rabbitmq['port'] = '5672'  
+rabbitmq['use_tls'] = false  
+repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+ui['kerberos_config'] = nil  
+ui['kerberos_login_config'] = nil  
+ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+ui['max_memory_mb'] = nil  
+ui['memory_alloc_arena_max'] = 2  
+ui['memory_map_max'] = 65536  
+ui['memory_map_threshold'] = 131072  
+ui['memory_top_pad'] = 131072  
+ui['memory_trim_threshold'] = 131072  
+ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+ui['support_links'] = {  
+  'name' => ['url', 'i18n'],  
+  'name1' => ['url1', i18n1'],  
+  'name2' => ['url2', i18n2']  
+} #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+ui['xmx'] = 0.25
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json b/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
new file mode 100644
index 0000000..0bdd862
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+  "title": "Overview",
+  "ordinal": 226,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md b/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
new file mode 100644
index 0000000..ce51737
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
@@ -0,0 +1,31 @@
+# Overview
+
+HPE Morpheus Enterprise provisions the following load balancers:
+
+- Amazon ALB (Application Load Balancer)
+- Azure Load Balancer
+- HaProxy Container
+
+and integrates with the following external load balancers:
+
+- Citrix NetScaler
+- F5 BigIP (v11.4+)
+- FortiADC
+- NSX
+- NSX Advanced
+
+Once created or integrated, load balancers are available as an option to be added during provision time or post-provisioning.
+
+Once a load balancer is added to an instance, you can manually scale or configure auto-scaling based on thresholds or schedules, and burst across clouds with cloud priority.
+
+In the load balancers page there are two sections:
+
+Load Balancers
+:   View or edit existing load balancers, add new load balancers.
+
+Virtual Servers
+:   View and link to Instances that are attached to load balancers.
+
+## Group and Tenant Access
+
+Load balancers can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the load balancer resource. Only workloads being provisioned to the selected Groups would have visibility to the load balancer. Workloads provisioned to other Groups would not see the load balancer as an available selection. **Tenant Permissions** control which Tenants may see the load balancer. Public visibility allows access to the load balancer for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json b/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
new file mode 100644
index 0000000..ea0d2e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+  "title": "Adding HPE SPP to the Virtual Image Library",
+  "ordinal": 424,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE SPP to the Virtual Image Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md b/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
new file mode 100644
index 0000000..433ba42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
@@ -0,0 +1,28 @@
+# Adding HPE SPP to the Virtual Image Library
+
+## About this task
+
+This procedure describes how to add an HPE Service Pack for ProLiant (SPP) ISO to the Morpheus Virtual Images library for use in firmware and driver update workflows.
+
+1. Obtain the appropriate HPE SPP ISO for the target ProLiant server generation.
+
+   NOTE
+
+   A separate ISO is required for each server generation (for example, Gen10 and Gen11).
+2. In the Morpheus appliance, navigate to Library > Virtual Images.
+3. Click Add > SPP.
+4. Enter a name for the image (for example, `HPE Gen10 SPP 2025.09.00`).
+5. From the Operating System drop-down list, select the appropriate **HPE SPP for Gen…** entry.
+6. Add the SPP ISO using one of the following methods:
+   - Upload the locally downloaded ISO file, or
+   - Select **URL / PATH** and paste the full URL for the ISO.
+7. Leave all other properties at their default values.
+8. Click Save Changes.
+
+   NOTE
+
+   When uploading a local file, wait for the upload to complete.
+9. In the Virtual Images list, wait until:
+   - Source shows `Uploaded`
+   - Status shows `Active`
+10. Record the **ID** of the Virtual Image entry. This ID is required when creating the update job.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json b/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
new file mode 100644
index 0000000..be11aa1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+  "title": "Orchestrating Load Balancers",
+  "ordinal": 228,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html",
+  "topic_cluster": {
+    "clustering_title": "Orchestrating Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md b/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
new file mode 100644
index 0000000..590d37f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
@@ -0,0 +1,40 @@
+# Orchestrating Load Balancers
+
+A large part of application orchestration and automation involves tying various web services and backend services into different load balancer configurations. If the automation tool is unable to communicate or integrate with this aspect of your infrastructure, a lot of gaps will be created in the full orchestrated flow of application deployment. This is why Morpheus provides deep integration with load balancers and explicit definitions with catalog items as to how they are connected to provisioned instances. Some of the functionality includes:
+
+- Public Cloud Load Balancer Support
+- Private Cloud Load Balancer Support
+- Port Type definitions (Profiles like HTTP/HTTPS or UDP)
+- SSL Certificate Management and SSL Certificate Upload
+- SSL Passthrough or Forced Redirect
+
+Not only does Morpheus have an ability to provision HAProxy based load balancer containers for easy consumption in development environments, but also has direct tie ins with several Load Balancer Types:
+
+- F5 BigIP
+- Netscaler
+- NSX Advanced Load Balancer
+- Amazon ELB
+- Amazon ALB
+- Azure Load Balancer
+- Fortinet
+- Openstack Octavia
+- HA Proxy
+- NSX
+
+Morpheus exposes configuration options during provisioning of an Instance relevant and common to each supported LB Integration. In some cases, Morpheus also provides direct management and sync support for VIP configurations on the various Load Balancers (such as F5, and NSX Advanced Load Balancer), However in a day to day orchestrated workflow this would not be the ideal means by which a user should consume load balancer services.
+
+By tying the Load Balancer associations into the provisioning of instances and the definition of the instance catalog item, the lifecycle of the VIP can more easily be maintained throughout the lifecycle of whatever application may be deployed.
+
+## Setting up an Instance for Load Balancer Consumption
+
+Several of the provided Morpheus instance types are ready to go with load balancer orchestration out of the box (Apache, Nginx, Tomcat, Node.js, etc). It is also fairly easy to extend existing generic instance types during provisioning to be tied to load balancers or to set up said catalog items in advanced for such functionality.
+
+When creating a custom Instance Type (in Library), one can define a list of exposed ports that the node type within the instance exposes. When defining these exposed ports it prompts for a Name, Port Number, and LB Type. The LB Type is what enables load-balancer functionality. This can either be HTTP,HTTPS, or TCP. This specification helps build the correct profile for the VIP as well as setup the appropriate types of Health Monitors within the target load balancer integration.
+
+Now, when a user consumes this custom instance type (either through single instance provisioning or full application blueprint provisioning), a section appears in the Automation phase of provisioning. Each port that is defined that exposes a load-balancer gets a dropdown to choose which load balancer integration attach to the exposed port and various prompts become available.
+
+These prompts control features ranging from target VIP Address to selecting an SSL Certificate to be applied to the VIP. These SSL Certificates will even go so far as to create SSL Profiles in integrations for things like an F5 automatically for the application.
+
+Once the instance is provisioned, as part of the final phase, the load balancer configuration will be applied and maintained on the instance. This association can be manipulated after the fact via the “Scale” tab found on the Instance Detail page.
+
+Another benefit to associating load-balancers this way is that the pool members are automatically maintained during scaling events, either via auto-scaling thresholds or manual node additions / removals.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json b/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
new file mode 100644
index 0000000..d609b38
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+  "title": "Overview",
+  "ordinal": 171,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md b/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
new file mode 100644
index 0000000..d7d78dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
@@ -0,0 +1,22 @@
+# Overview
+
+Infrastructure  >  Clusters is for creating and managing Kubernetes Clusters, HPE Morpheus Enterprise manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS, AKS and GKE.
+
+## Cluster Types
+
+Table 1.
+
+     |  |  |  |
+| --- | --- | --- |
+| **Name** | **Description** | **Provider Type** |
+| Kubernetes Cluster | Provisions by default a Kubernetes cluster consisting of 1 Kubernetes Master and 3 Kubernetes Worker nodes. Additional system layouts available including Master clusters. Custom layouts can be created. | Kubernetes |
+| Docker Cluster | Provisions by default a Morpheus controlled Docker Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus Docker Hosts are automatically converted to Clusters upon 4.0.0 upgrade. | Docker |
+| EKS Cluster | Amazon EKS (Elastic Kubernetes Service) Clusters | Kubernetes |
+| AKS Cluster | Azure AKS (Azure Kubernets Service) Clusters | Kubernetes |
+| Ext Kubernetes | Brings an existing (brownfield) Kubernetes cluster into HPE Morpheus Enterprise | Kubernetes |
+| GKE Cluster | Google Cloud GKE (Google Kubernetes Engine) Clusters | Kubernetes |
+| HVM Cluster | A KVM‐based virtualization solution. See the detailed section below on HVM Clusters for complete use documentation. | KVM |
+
+NOTE
+
+Refer to clusterLayouts for supported Clouds per Cluster Type.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json b/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
new file mode 100644
index 0000000..ac70e58
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+  "title": "Diagrams",
+  "ordinal": 344,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html",
+  "topic_cluster": {
+    "clustering_title": "Diagrams",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md b/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
new file mode 100644
index 0000000..b5776f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
@@ -0,0 +1,45 @@
+# Diagrams
+
+The HPE Morpheus Enterprise diagram repository contains many diagrams related to HPE Morpheus Enterprise appliance architectures, HPE Morpheus Enterprise concepts, and reference diagrams for integrating HPE Morpheus Enterprise with third-party technologies.
+
+## Appliance Architectures
+
+### All-in-one (single node) Installation
+
+![../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+### 3-node High Availability (HA) Installation
+
+![../_images/morpheus-3node-ha.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EF3C066B-2133-4DBC-8E53-1C23C38740D4-high.png)
+
+### Fully Distributed High Availability (HA) Installation
+
+![../_images/FullDistributedSingleSite.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6791DB71-7757-41D2-985E-8E45863D89CD-high.png)
+
+## HPE Morpheus Enterprise Concepts
+
+### Cloud-Group-Role Relationship
+
+![../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+### Library Items
+
+![../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
+
+### Mapping Morpheus Constructs to Public and Private Cloud Constructs
+
+![../_images/awsAndMorpheusConstructs.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-921BCD31-0FFD-4AB6-98C5-9FA5BCC5E31C-high.png)
+
+## Third-Party Technology Integration
+
+### Zerto
+
+![../_images/morpehus_zerto_chart.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+### Veeam
+
+![../_images/MorpheusVeeamIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-42CD5807-1040-4713-9939-451BA81D9190-high.png)
+
+### Mapping Identity Source Groups to Morpheus Roles
+
+![../_images/mapIdentityToMorpheus.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-58D1993D-5964-4804-877B-ECF3112E147E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json b/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
new file mode 100644
index 0000000..730964f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+  "title": "Unmanaged Networks",
+  "ordinal": 430,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html",
+  "topic_cluster": {
+    "clustering_title": "Unmanaged Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md b/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
new file mode 100644
index 0000000..6df932e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
@@ -0,0 +1,23 @@
+# Unmanaged Networks
+
+The unmanaged Network mode is used when the network infrastructure is not managed by HPE Morpheus.
+
+In this case, there is a minimal configuration that is created as default when the cloud gets created with the network mode set to `Unmanaged network`. This minimal configuration includes a default Resource Pool that can be used to associate compute servers with, and a default unmanaged network that is available during instance provisioning to attach with compute servers.
+
+The default unmanaged network is configured as an untagged network with DHCP as the IP allocation method. This allows a compute instance provisioned to come up with network connectivity without any specific network configuration required from the user.
+
+The unmanaged network assumes:
+
+- The network infrastructure to be configured correctly for the untagged network to work correctly.
+- A DHCP server stood up in the infrastructure for that network.
+
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DD9E1A8A-D473-4DDE-9761-DD613DCF1F4B-high.png)
+
+Users can create other networks (VLANs) if required, in addition to the default unmanaged network, and use them in their BM instance.
+
+NOTE
+
+- If the ALLOW IP OVERRIDE checkbox is selected (allows selection of DHCP or static IP or IP Pool), ensure that the CIDR and GATEWAY fields are configured correctly.
+- At present, only one physical interface is supported for the unmanaged network mode.
+
+The network consumption by an instance is the same as for managed networks.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..ffa5c09
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 101,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..41e3cdb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,13 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html)**
+- **[Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
+- **[Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html)**
+- **[Templates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html)**
+- **[Library Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html)**
+- **[Operating Systems](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html)**
+- **[Variables](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json b/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
new file mode 100644
index 0000000..f8e3bac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+  "title": "Morpheus Virtual Desktops",
+  "ordinal": 368,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Virtual Desktops",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md b/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
new file mode 100644
index 0000000..260d87f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
@@ -0,0 +1,450 @@
+# Morpheus Virtual Desktops
+
+## VDI Pools Overview
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
+
+## Virtual Desktop Persona Overview
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json b/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
new file mode 100644
index 0000000..a8018cb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+  "title": "Costing: Cloud Costing",
+  "ordinal": 58,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Cloud Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md b/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
new file mode 100644
index 0000000..b854a35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
@@ -0,0 +1,39 @@
+# Costing: Cloud Costing
+
+![../_images/1cloudcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-429BA931-09F3-4CC2-AC8E-45B3D0167664-high.png)
+
+The Cloud Costing dashboard breaks down total costs by cloud type, cloud region, and individual cloud. This includes reporting the total number of clouds that meet your filters, the month-to-date running total, the projected monthly spend, among other useful metrics.
+
+## Filters
+
+Filter the Clouds pulled into the dashboard by one or more of the following fields:
+
+- Cloud (all matched by search)
+- Group
+- Cloud (selected from dropdown)
+- Tenant
+- Tag (Key)
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Clouds that meet set filters:
+
+- **CLOUDS:** The total number of Clouds that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Clouds meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Clouds meeting dashboard filters
+- **CLOUD TYPES:** The number of distinct cloud types that meet the dashboard filters, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud types
+- **REGIONS:** The total number of regions represented by Clouds meeting the dashboard filters
+
+In addition to the totals described above, graphs visualize the percentage of these totals accounted for by specific Clouds, Cloud types, and Cloud regions.
+
+## Cloud List
+
+Each Cloud that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Cloud:
+
+- **TYPE:** The Cloud type, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud type
+- **NAME:** The name given to the Cloud in HPE Morpheus Enterprise at the time of integration
+- **LOCATION:** The Cloud location (if available)
+- **REGION:** The Cloud region (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Cloud listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Cloud listed
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json b/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
new file mode 100644
index 0000000..4d88cf5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+  "title": "Security Groups",
+  "ordinal": 223,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html",
+  "topic_cluster": {
+    "clustering_title": "Security Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md b/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
new file mode 100644
index 0000000..269452d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
@@ -0,0 +1,81 @@
+# Security Groups
+
+Infrastructure  >  Network - Security Groups
+
+## Overview
+
+A Security Group acts as a virtual firewall that controls the traffic for one or more Instances. When you launch an instance, you associate one or more Security Groups with the instance. You add rules to each Security Group that allow traffic to or from its associated Instances. You can modify the rules for a Security Group at any time; the new rules are automatically applied to all Instances that are associated with the Security Group.
+
+IMPORTANT
+
+The local firewall setting must be enabled for Security Groups to be applied in the guest firewall (iptables). The local firewall setting can be enabled in Infrastructure > Clouds > Click the Cloud > Edit > Advanced Options > LocalFirewall (On/Off)
+
+IMPORTANT
+
+When then local firewall setting is enabled, Morpheus will automatically set an iptable rule to allow incoming connections on tcp port 22 from the Morpheus Appliance.
+
+IMPORTANT
+
+If the local firewall setting is configured on a cloud that supports Security Groups natively (AWS for example), the local firewall setting is ignored and the guest firewall will not be modified. Security Groups will be attached to the instance as normal
+
+## Add Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the + Add Security Group button.
+3. From the Security Group Wizard input a name, and description.
+4. Save Changes
+
+## Add Security Group Rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to add a rule to.
+3. From the Security Group page click the + Add Rule button.
+4. From the Rule Wizard select the rule type and input source and depending on the type selected protocol and input a port range.
+5. Save Changes
+
+## Edit Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to edit a rule in.
+3. Click the edit icon on the row of the Security Group rule you wish to edit.
+4. Modify information as needed.
+5. Save Changes
+
+## Delete Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to delete a rule from.
+3. Click the delete icon on the row of the Security Group rule you wish to delete.
+
+## Add Cloud Security Group
+
+### About this task
+
+To add Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the desired cloud to add a Security Group
+3. Click the Networks tab
+4. Within the “Security Groups” section, click on a Security Group to edit its rules
+5. Alternatively, click + ADD SECURITY GROUP to create a new one
+
+## Remove Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the cloud to remove the Security Group from.
+3. Click the Security Groups tab.
+4. Click the Edit Security Groups button.
+5. Click the - (Minus) button of the Security Group from the Added Security Groups list to remove.
+6. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json b/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
new file mode 100644
index 0000000..240689b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+  "title": "Building Catalog Blueprints",
+  "ordinal": 141,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md b/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
new file mode 100644
index 0000000..626f291
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
@@ -0,0 +1,62 @@
+# Building Catalog Blueprints
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+HPE Morpheus Enterprise Blueprints allow for full multi-tier application deployment. In the Self Service catalog, user can create catalog items based on pre-existing App Blueprints. If new Blueprints need to be created for the Service Catalog, see other sections of HPE Morpheus Enterprise docs on building App Blueprints of various supported types. Just like with catalog Instances, we can pre-configure Blueprints and present them to users viewing the Service Catalog Persona view for easy, one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Blueprint. The modal window will appear to configure and add a new catalog Blueprint.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIGURE:** Click CONFIGURE to use the familiar App provisioning wizard to tie Blueprint and App deployment configuration to the Catalog Item
+- **APP SPEC:** Inject App spec here for any fields required to provision an App from your Blueprint. You may also inject any overrides to the existing Blueprint spec that are desired. App Spec configuration must be YAML, a simple example that names the App and sets the Group and Cloud is included below:
+
+  ```
+  ```
+  #Example App Spec  
+  name: '<%= customOption.appName %>'  
+  group:  
+    name: Dev Group  
+  environment: Dev  
+  tiers:  
+    Web:  
+      instances:  
+        - instance:  
+            type: nginx  
+            cloud: Dev AWS  
+    App:  
+      instances:  
+        - instance:  
+            type: apache  
+            cloud: Dev AWS
+  ```
+  ```
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+
+  NOTE
+
+  App spec custom option variables should be single quoted in YAML: `cloud: '<%= customOption.cloud %>'`. Additionally, not all variables are available here as many are unknown until provisioning. Users may use any custom Input values (customOption) as well as name or hostname values which are resolved as part of naming policy evaluation.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json b/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
new file mode 100644
index 0000000..c8e6682
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+  "title": "Creating Roles",
+  "ordinal": 301,
+  "parent_title": "Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md b/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
new file mode 100644
index 0000000..a103931
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
@@ -0,0 +1,6 @@
+# Creating Roles
+
+**Subtopics**  
+
+- **[User Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html)**
+- **[Tenant Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json b/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
new file mode 100644
index 0000000..e4f3be6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+  "title": "Create a MultiTenant User Role",
+  "ordinal": 304,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html",
+  "topic_cluster": {
+    "clustering_title": "Create a MultiTenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md b/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
new file mode 100644
index 0000000..222c262
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
@@ -0,0 +1,28 @@
+# Create a MultiTenant User Role
+
+## About this task
+
+A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select the MULTITENANT ROLE checkbox
+7. Optionally select the MULTITENANT LOCKED checkbox \* When enabled, the FEATURE ACCESS settings in the Role will not be editable by subtenants. Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+8. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
new file mode 100644
index 0000000..0d9d8cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+  "title": "Volumes",
+  "ordinal": 233,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
new file mode 100644
index 0000000..7409f80
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
@@ -0,0 +1,176 @@
+# Volumes
+
+Volumes sync or created in HPE Morpheus Enterprise can be viewed in Infrastructure- Storage - Volumes. Volumes can be added for Storage Servers integrated with HPE Morpheus Enterprise in the Infrastructure- Storage - Servers section.
+
+## Volumes Types
+
+The available Volume Types list and filterable by are:
+
+- 3Par Volume
+- Alibaba Cloud SSD
+- Alibaba Efficiency Disk
+- Alibaba Cloud Disk
+- AWS gp2
+- AWS io1
+- AWS sc1
+- AWS st1
+- Azure Volume
+- Azure Disk
+- Bluemix Disk
+- Bluemix SAN
+- Bluemix SAN
+- CD ROM
+- DO Disk
+- ECS Block Storage
+- ECS Object Storage
+- ECS Shared File System
+- Floppy Disk
+- Google Standard
+- HP Enclosure Disk
+- Oracle iSCSI
+- Isilon NFS Volume
+- Nutanix IDE
+- Nutanix SATA
+- Nutanix SCSI
+- Open Telekom Volume
+- Openstack Disk
+- Openstack Volume
+- Oracle Block Volume
+- Oracle Disk
+- Oracle Virtual Volume
+- SCVMM Datastore
+- Softlayer Disk
+- Softlayer SAN
+- Softlayer SAN
+- Disk
+- UpCloud Disk
+- UpCloud MaxIOPS
+- NULL
+- NULL
+- VMWare Datastore
+- VMWare Disk
+
+## CREATE VOLUME
+
+At least one Storage Server Integration from Infrastructure- Storage - Servers is required to create volumes from Infrastructure- Storage - Volumes.
+
+### 3par
+
+#### About this task
+
+To Add a 3Par Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select 3Par from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the 3par Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   3Par Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+       PROVISION TYPE
+       :   - FULL
+           - TPVV
+           - SNP
+           - PEER
+           - UNKNOWN
+           - TDVV
+
+       Click COMPLETE
+       :   Select COMPLETE
+
+### Dell EMC ECS
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC ECS from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the DELL EMC ECS Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   ECS Block Storage ECS Object Storage ECS Shared File System
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+   Click COMPLETE
+   :   Select COMPLETE
+
+### Dell EMC Isilon
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC Isilon from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the Dell EMC Isilon Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   Isilon NFS Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       ALLOWED IP’s
+       :   Specify IP Addresses to limit accessibility to the File Share
+           :   Leave blank for open access
+               :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+   Click COMPLETE
+   :   Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json b/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
new file mode 100644
index 0000000..ddb1301
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+  "title": "Add Citrix NetScaler Integration",
+  "ordinal": 495,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html",
+  "topic_cluster": {
+    "clustering_title": "Add Citrix NetScaler Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md b/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
new file mode 100644
index 0000000..f253d5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
@@ -0,0 +1,48 @@
+# Add Citrix NetScaler Integration
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Citrix NetScaler**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Citrix LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E18D9A6C-6C61-4C00-9B2C-45F95C2FEEF7-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the NetScaler API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the NetScaler API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NetScaler service account username.
+   :   **PASSWORD \***: Enter NetScaler service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new NetScaler Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new NetScaler Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new NetScaler Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json b/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
new file mode 100644
index 0000000..e116514
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+  "title": "Add Virtual Image",
+  "ordinal": 151,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md b/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
new file mode 100644
index 0000000..5b416f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
@@ -0,0 +1,124 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be upload to HPE Morpheus Enterprise from local files or URL’s. Amazon and Azure Marketplace metadata can also be added to the Virtual Images library, enabling the creation of custom catalog Instance Type from Marketplace images (no image is transferred to HPE Morpheus Enterprise when adding Marketplace images).
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the HPE Morpheus Enterprise Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the HPE Morpheus Enterprise Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - Alibaba
+   - Amazon AMI
+   - Azure Marketplace
+   - Digital Ocean
+   - ISO
+   - PXE Boot
+   - QCOW2
+   - RAW
+   - VHD
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+## VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to HPE Morpheus Enterprise, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be sync’d into HPE Morpheus Enterprise.
+
+If all the vCenters are added as Clouds into HPE Morpheus Enterprise and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in HPE Morpheus Enterprise. This means that as you deploy to the various vCenter Clouds in HPE Morpheus Enterprise using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+This eliminates the need for creating multiple Node Types for each virtual image if the templates were named differently in each vCenter. This can reduce the overhead of maintaining multiple Node Types and reduces user selections. As well, this can reduce the cloning time of VMs by avoiding network transfers of images between geographic locations, ensuring the closest VM template is selected.
+
+HPE Morpheus Enterprise supports VMware Content Libraries storing VM templates and syncing into HPE Morpheus Enterprise, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Data Center** level object. The same process above applies to a single VMware cloud with multiple logical data centers. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..4e0642e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 292,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..986354b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,9 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html)**
+- **[Role Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
+- **[Creating Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json b/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
new file mode 100644
index 0000000..0257f06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+  "title": "Overview",
+  "ordinal": 255,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md b/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
new file mode 100644
index 0000000..574859e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
@@ -0,0 +1,15 @@
+# Overview
+
+HPE Morpheus Enterprise provides great monitoring features out of the box. Anything provisioned within HPE Morpheus Enterprise automatically gets a check created in the monitoring service. These checks are organized hierarchically in “Groups” and “Apps”. This makes it easy to gain a perspective as to what a customer or full stack facing impact is in the event of a particularly instance failure. This also takes into account redundancy layers when it comes to calculating the applications overall uptime percentage.
+
+HPE Morpheus Enterprise also includes a monitoring integration with ServiceNow.
+
+**Subtopics**  
+
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html)**
+- **[Checks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html)**
+- **[Monitoring Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html)**
+- **[Incidents](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html)**
+- **[Contacts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html)**
+- **[Alert Rules](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json b/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
new file mode 100644
index 0000000..3f393a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+  "title": "Editing and Deleting from the Self Service Catalog",
+  "ordinal": 143,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Deleting from the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md b/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
new file mode 100644
index 0000000..b04dae8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
@@ -0,0 +1,3 @@
+# Editing and Deleting from the Self Service Catalog
+
+Once created, Service Catalog items can be edited or deleted from the Catalog Items list view (Library > Blueprints > Catalog Items). Click the pencil icon in the relevant row to edit the Service Catalog item or the trash can icon to delete it. Alternatively, Service Catalog items can be made inactive to remove them as provisioning options rather than deleting them.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json b/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
new file mode 100644
index 0000000..9ee1596
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+  "title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+  "ordinal": 370,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md b/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
new file mode 100644
index 0000000..a101779
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
@@ -0,0 +1,115 @@
+# Backing Up and Restoring HPE Morpheus Enterprise Appliance
+
+HPE Morpheus Enterprise includes built-in tools for backing up managed Instances as well as the appliance itself. Use this guide to configure a location and schedule for backing up your HPE Morpheus Enterprise appliance. This guide also includes steps for restoring or migrating your appliance from the created backup. The steps are the same whether your appliance is deployed in a single node or distributed architecture.
+
+The built-in HPE Morpheus Enterprise appliance backup functionality backs up the MySql data. In addition to the database, it’s advisable to back up your shared storage (at `/var/opt/morpheus/morpheus-ui`) and the morpheus.rb configuration file.
+
+NOTE
+
+The destination HPE Morpheus Enterprise appliance must be running the same version as that which the backup was taken from.
+
+## Create A Backup Job
+
+### About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the execute scheduling section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+### Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
+
+## Integrate a Bucket or File Share
+
+### About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in storage documentation.
+
+## Configuring HPE Morpheus Enterprise Appliance Backup
+
+### About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+### Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+### Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
+
+## Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json b/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
new file mode 100644
index 0000000..e097e46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+  "title": "Approvals",
+  "ordinal": 77,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html",
+  "topic_cluster": {
+    "clustering_title": "Approvals",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md b/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
new file mode 100644
index 0000000..d16dd46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
@@ -0,0 +1,161 @@
+# Approvals
+
+HPE Morpheus Enterprise and Service Now Approvals
+
+## Overview
+
+Policies can be created for Groups and Clouds to require approvals for actions with the built-in HPE Morpheus Enterprise approvals engine, or via a ServiceNow integration. Approvals can be configured for Provisioning and Lifecycle extensions.
+
+## Configuring Approvals
+
+### About this task
+
+Configuring HPE Morpheus Enterprise for Approvals
+
+To configure HPE Morpheus Enterprise for approvals:
+
+### Procedure
+
+1. Configure Roles for Approval access
+2. Optionally configure a ServiceNow Integration for ServiceNow approvals. 
+
+   - Please note ServiceNow integration is not required for Internal Approvals.
+3. Create approvals policies for: 
+
+   - Internal Approvals
+   - SNOW Approvals
+
+### Configure Roles
+
+Configure User Role access settings in Administration > Roles > (Role) > Operations: Approvals.
+
+- All Users with a Role applied containing Operations: Approvals set to Full will have approval authority, and be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to Read will be able to view Approval requests and history, but will not be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to None will not have access to the Operations: Approvals section, and such will not be able to see or act on approval requests.
+- Regardless of Role settings, any instance or app provisioned by any user to a group or cloud with an active Approval policy applied will require approval before the instance or app will provision.
+
+### ServiceNow Approvals
+
+#### About this task
+
+Configure ServiceNow integration for SNOW Approvals
+
+#### Procedure
+
+1. Navigate to Admin > Integrations
+2. Select + NEW INTEGRATION
+3. Select ServiceNow from the Type dropdown in the Integration modal and enter: 
+
+   - Name
+     :   Name of the integration in HPE Morpheus Enterprise
+   - Enabled
+     :   Leave checked to enable the integration.
+   - Host
+     :   URL of the ServiceNow host (ex: <https://ven0000.service-now.com>)
+   - User
+     :   A User in ServiceNow that is able to access the REST interface and create/update/delete incidents, requests, requested items, item options, catalog items, workflows, etc.
+   - Password
+     :   Password for User above
+4. Save Changes
+
+#### Results
+
+HPE Morpheus Enterprise then configures the integration with ServiceNow, syncs ServiceNow workflows which are available when creating approvals policies. (This process can take up to 5 minutes depending on the size of the workflow table in ServiceNow.)
+
+### Create Approval Policies
+
+- Policies applied to a Group are created in Infrastructure > Groups > (group) > Policies tab.
+- Policies applied to a Cloud are created in Infrastructure > Clouds > (cloud) > Policies tab.
+
+#### To create an Approval policy:
+
+##### Procedure
+
+1. Navigate to the Policies tab in the Group or Cloud to which the policy will apply.
+2. Select + ADD POLICY to open the New Policy wizard
+3. Select Provision Approval from the Type dropdown
+4. Add an optional description
+5. Leave Enabled selected for this Policy to be active once saved.
+   :   - Enabled can be deselected to disable to policy.
+6. In the config section, select either Internal Approvals or ServiceNow Approvals: 
+
+   - Internal Approvals
+     :   Approval requests will be managed within HPE Morpheus Enterprise via the Operations: Approvals section.
+   - ServiceNow Approvals
+     :   Approval requests will be managed with ServiceNow (SNOW). Please note a ServiceNow integration (Admin: Integrations) must be configured prior to SNOW Approval policy generation.
+
+         - For ServiceNow Approvals, select the appropriate ServiceNow workflow for this policy. Please note the workflows presented are created in ServiceNow and synced with HPE Morpheus Enterprise .
+7. Add the HPE Morpheus Enterprise Accounts to which this policy will apply, or leave the Accounts field blank to apply to all accounts.
+8. Save
+
+##### Results
+
+Upon saving, a new policy is created in the Group or Cloud Policies tab.
+
+NOTE
+
+SNOW Approvals will take a few moments to save as the policy is generated.
+
+## Managing Approval Requests
+
+Once Instance approval policies are added to a Group or Cloud, any Instance or App provisioned into that Group or Cloud will create an approval request entry in the Operations  >  Approvals section.
+
+NOTE
+
+User Role permission Operations: Approvals  >  FULL is required to manage Approvals.
+
+- To Approve, Deny, or Cancel an internal approval request, select the request and use the Actions dropdown.
+- To Cancel a ServiceNow Approval request, select the request and use the Actions dropdown. ServiceNow approvals are managed in ServiceNow.
+
+NOTE
+
+Instances requiring provisioning approval will have a PENDING status until approved.
+
+Each Approval Request will have:
+
+- Name: A name for the approval in HPE Morpheus Enterprise
+- Monthly Price (Est.): The estimated monthly price of the Instance to be provisioned
+- Request Type: What is being requested, such as Instance approval
+- External Name: For ServiceNow integrations, the name of the approval in the ServiceNow console
+- Type: Internal or ServiceNow
+- Status
+- Date Created
+- Requested By: The HPE Morpheus Enterprise user making the request
+- Actions dropdown (for internal approval requests)
+  :   - Approve
+      - Deny
+      - Cancel
+- Actions dropdown (for ServiceNow requests)
+  :   - Cancel
+
+NOTE
+
+The Approvals list view can be sorted by NAME, REQUEST TYPE, EXTERNAL NAME, DATE CREATED, and REQUESTED BY
+
+### Internal approval requests
+
+#### About this task
+
+To Approve, Deny or Cancel an Internal approval request:
+
+#### Procedure
+
+1. Navigate to Operations  >  Approvals
+2. Select the Name of the Approval request
+3. Select Actions on the far right of the request
+4. Select Approve, Deny, or Cancel from the Actions dropdown
+5. Select OK on the confirmation modal
+
+#### Results
+
+- When an Internal request is approved, the related instance will begin to provision immediately and the request will show approved.
+- When an Internal request is denied, the related instances status will change to Denied and the request will show Rejected in the Approvals section.
+- When an Internal request is canceled, the related related instances status will change to Cancelled and the request will be canceled.
+
+### ServiceNow Approval requests
+
+ServiceNow approval request are managed in ServiceNow. The process of approving or rejecting requests is determined by the ServiceNow Workflow selected when configuring the SNOW Approval policy. These Workflows are configured in ServiceNow.
+
+IMPORTANT
+
+HPE Morpheus Enterprise syncs with ServiceNow every 5 minutes. Once an Approval Request is Approved or Rejected in Service Now, it will take up to 5 minutes for the instance to respond accordingly, and the status for the approval request in the Approvals section in HPE Morpheus Enterprise to update.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json b/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
new file mode 100644
index 0000000..cd62ea6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+  "title": "Nutanix Prism Central",
+  "ordinal": 469,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Central",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md b/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
new file mode 100644
index 0000000..2cea905
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
@@ -0,0 +1,140 @@
+# Nutanix Prism Central
+
+HPE Morpheus Enterprise offers Nutanix Prism Central Cloud integration support through and official plugin. Adding the plugin to a HPE Morpheus Enterprise appliance adds a new Cloud integration type for Nutanix Prism Central. Download the plugin from the HPE Morpheus Enterprise [Plugin Exchange](https://share.morpheusdata.com/morpheus-nutanix-prism/about) and upload it to the appliance. Plugins are uploaded at Administration > Integrations > Plugins. See HPE Morpheus Enterprise [plugin documentation](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) for more details on adding plugins.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Project scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Creating a Minimal Service Account
+
+Integrating Nutanix Prism Central with HPE Morpheus Enterprise requires the use of a service account which has sufficient privileges to work with all Nutanix contructs that HPE Morpheus Enterprise touches. If possible, it’s recommended to use a service account with full administrator rights. This is because there is currently a bug on the Nutanix side that prevents limited roles from working with backups and snapshots. If you choose to use the minimal role permissions outlined in this section, those features will not work until the bug is resolved.
+
+### Recommended Minimal Service Account
+
+- The user belongs to the built-in “Prism Viewer” role
+- The user must be added to any Projects that need to be surfaced to the integration
+- The user must belong to a custom role with the permissions listed in the expandable section below
+
+#### Required Custom Role Permissions
+
+- Access Console VM
+- Allow Cross Cluster VM Migration
+- Allow VM Power Off
+- Allow VM Power On
+- Allow VM Reboot
+- Allow VM Reset
+- Allow VM Volume Group Connection
+- Clone VM
+- Copy Image Remote
+- Create External Subnet
+- Create Image
+- Create Layer2 Stretch
+- Create Overlay Subnet
+- Create Subnet
+- Create VM
+- Delete External Subnet
+- Delete Image
+- Delete Layer2 Stretch
+- Delete Subnet
+- Delete VM
+- Delete VM Recovery Point
+- Deploy VM Templates
+- Expand VM Disk Size
+- Export VM
+- Mount VM CDROM
+- Restore VM Recovery Point
+- Revert VM
+- Snapshot VM
+- Unmount VM CDROM
+- Update Cluster
+- Update Container Disks
+- Update External Subnet
+- Update Image
+- Update Layer2 Stretch
+- Update Overlay Subnet
+- Update Subnet
+- Update VM
+- Update VM Boot Config
+- Update VM Categories
+- Update VM CPU
+- Update VM Description
+- Update VM Disk List
+- Update VM GPU List
+- Update VM Memory
+- Update VM Memory Overcommit
+- Update VM Name
+- Update VM NGT Config
+- Update VM NIC List
+- Update VM Owner
+- Update VM Power State
+- Update VM Power State Mechanism
+- Update VM Project
+- Update VM Recovery Point
+- View Availability Zone
+- View Category
+- View Cluster
+- View Cluster Networking Capabilities
+- View Container
+- View Container Datastore
+- View Container Stats
+- View Dashboard
+- View External Subnet
+- View Host
+- View Image
+- View Layer2 Stretch
+- View Layer2 Stretch Related Entities
+- View Marketplace Item
+- View Name Category
+- View Network Gateway
+- View Overlay Subnet
+- View Project
+- View Storage Pool
+- View Subnet
+- View Value Category
+- View vCenter Cluster
+- View vCenter Container
+- View vCenter Node
+- View vCenter VM
+- View Virtual Switch
+- View VM
+- View VM Host Affinity Policy
+- View VM Recovery Point
+- View VM Templates
+- View VPC
+- View Vpn Connection
+
+IMPORTANT
+
+Due to a current Nutanix bug, non-administrator service accounts will not be able to utilize backup or snapshot features via HPE Morpheus Enterprise. Users who need these features should integrate using an administrator service account rather than the minimal user described here.
+
+## Adding a Nutanix Prism Central Cloud
+
+Adding Nutanix Prism Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the NPC appliance at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the Nutanix Prism Central plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), NUTANIX PRISM CENTRAL should be selectable as a Cloud type to add. Select it and click NEXT.
+
+![../../../_images/pickType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-75A6B1BB-774A-4E63-B8E7-70CF427BE53C-high.png)
+
+At minimum, it’s required to configure the following to add the new cloud:
+
+- **NAME:** A friendly name for the new NPC Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx:9440>)
+- **USERNAME:** Username for a Nutanix Prism Central service account (see the previous section for recommendations on service account user role configuration)
+- **PASSWORD:** The password for the service account
+- **VMM API VERSION:** Allows the user to select which VMM API versions their environment will support as HPE Morpheus Enterprise cannot auto-detect this and endpoint support differs between versions
+
+You’ll know the API URL and credentials have been entered correctly when the PROJECTS dropdown becomes populated. You may choose to scope Nutanix Prism Central Clouds to a specific project or scope the Cloud to all Projects. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+![../../../_images/configureCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B94510F8-00EB-4108-943D-8029EDB50DCD-high.png)
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json b/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
new file mode 100644
index 0000000..4a71d4e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+  "title": "Creating Jobs",
+  "ordinal": 92,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md b/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
new file mode 100644
index 0000000..2f4ae05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
@@ -0,0 +1,63 @@
+# Creating Jobs
+
+## About this task
+
+NOTE
+
+Jobs require existing Tasks or Workflows. See the appropriate section of HPE Morpheus Enterprise docs for more on creating [Tasks](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#tasks) and [Workflows](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#workflows).
+
+To create a new Job:
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs
+2. Select + ADD
+3. Enter the following 
+
+   - NAME: Name of the Job in HPE Morpheus Enterprise
+   - JOB TYPE: A Task Job will execute a selected Task, a Workflow Job will execute a selected Workflow
+   - ENABLED: When checked, the Job will run as scheduled
+4. Select NEXT
+5. Configure the Job 
+
+   Task Jobs
+   :   TASK: Select target Task. If relevant to the Task, Input fields will be presented
+
+       SCHEDULE:
+       :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions > ExecuteDate And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually) Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+           NOTE
+
+           HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+
+       Workflow Jobs
+       :   WORKFLOW: Select target Workflow. If relevant to the Workflow, Input fields will be presented
+
+           SCHEDULE:
+           :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions  >  Execute
+
+               Date And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually)
+
+               Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+               NOTE
+
+               HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+6. Select NEXT
+7. Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json b/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
new file mode 100644
index 0000000..635edad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+  "title": "Building Catalog Instances",
+  "ordinal": 140,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md b/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
new file mode 100644
index 0000000..b6b689b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
@@ -0,0 +1,227 @@
+# Building Catalog Instances
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+An Instance in HPE Morpheus Enterprise is a set of one or more containers or virtual machines that correlate to a single, horizontally-scalable entity or service suite. From the Self Service section, we can pre-configure HPE Morpheus Enterprise Instances and present them to users viewing the Service Catalog Persona for one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Instance. The modal window will appear to configure and add a new catalog Instance.
+
+![../../_images/createInstance1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0D1DD7D2-5438-441D-9D5D-515401798FE8-high.png)
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When marked, this Catalog Item will be available from the provisioning Catalog view
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIG:** Enter, view, or edit Instance config here. Click CONFIGURE to build a base configuration through the HPE Morpheus Enterprise Instance wizard. After configuration through the Instance wizard, you may need to overwrite some static values in the Instance JSON body with calls to custom Input values. This allows your users to easily set the Instance Plan, Group, name, tags, or anything else they may need to control. Dynamic inputs are passed with the following syntax: “<%= customOptions.fieldName %>” where fieldName is the Field Name value set on the Input
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+## Using Forms with Catalog Items
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+Using Forms provides a number of advantages over using Inputs. Once the Form is selected, HPE Morpheus Enterprise helpfully provides a sidebar which contains all variables that can be consumed in the Instance config from the Form:
+
+![../../_images/catalogSidebar.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4820885E-F91A-4F9E-881B-4C5ECEC0F160-high.png)
+
+Many Form Inputs are designed to auto-inject themselves into the Instance config, you can see in the screenshot above that “AUTO INJECT” is checked. For variables that auto-inject, you do not need to override any static configuration with a variable call in order to consume that form value. In most cases, you should leave auto-inject turned on but the option is available to disable it for more advanced situations such as if you wanted to code custom logic into the variable call.
+
+Other types of Form Inputs do not auto-inject and, for these, you must override any static configuration in the Instance config with a variable call. For these situations, HPE Morpheus Enterprise helpfully provides the results of all variables so you can be sure you’re injecting the proper call. Click on the question mark (?) button immediately to the right of the “FORM VARIABLES” header to see a list of available variables and an example resolved variable. Variable tiles may be dragged from the sidebar into the CONFIG text area and a properly-formatted variable call will be inserted.
+
+![../../_images/optionTypeHelp.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF683E2D-8807-45D4-8E2B-B807A250D92B-high.png)
+
+As an example, see the configuration for an Ubuntu server in the expandable section below. You’ll notice in the configuration that a VMware Cloud, a specific Group, a specific Plan, and other static configurations are set. Since the Group, Cloud, Plan and other variables are able to be automatically injected, the user may select a different Group, Cloud, Plan, etc. from the form at provision time. The creator of the Catalog Item does not need to override those static configurations with variable calls.
+
+### Example Catalog Item Config
+
+```
+```
+{  
+  "hostName": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "metadata": "<%=customOptions.targetTags%>",  
+  "backup": {  
+    "backupRepository": 40,  
+    "veeamManagedServer": "",  
+    "jobSchedule": 2,  
+    "createBackup": true,  
+    "jobAction": "new",  
+    "jobRetentionCount": "3",  
+    "providerBackupType": 12,  
+    "target": 37006  
+  },  
+  "instance": {  
+    "userGroup": {  
+      "id": ""  
+    },  
+    "tags": "Forms,Test"  
+  },  
+  "defaultExpandAdvanced": false,  
+  "volumes": [  
+    {  
+      "maxIOPS": null,  
+      "displayOrder": 0,  
+      "unitNumber": "0",  
+      "minStorage": 5368709120,  
+      "configurableIOPS": false,  
+      "uuid": "a6781cc1-31ca-406b-aea0-e33ea1a18b7f",  
+      "controllerMountPoint": "2200223:0:4:0",  
+      "internalId": "[ESXi-DC2-QA-LUN01] Morpheus Ubuntu 22.04 20230307/Morpheus Ubuntu 22.04 20230307.vmdk",  
+      "id": 5255832,  
+      "datastoreId": "autoCluster",  
+      "maxStorage": 26843545600,  
+      "volumeCustomizable": true,  
+      "readonlyName": false,  
+      "controllerId": 2200223,  
+      "externalId": "2000",  
+      "virtualImageId": 1418543,  
+      "vId": 1418543,  
+      "size": 25,  
+      "name": "root",  
+      "planResizable": true,  
+      "rootVolume": true,  
+      "storageType": 1,  
+      "typeId": 1,  
+      "resizeable": true,  
+      "uniqueId": null  
+    }  
+  ],  
+  "type": "ubuntu",  
+  "ports": [  
+    {  
+      "code": "ubuntu.22",  
+      "visible": true,  
+      "internalPort": 22,  
+      "loadBalancePort": null,  
+      "loadBalanceProtocol": null,  
+      "sortOrder": 1,  
+      "name": "SSH",  
+      "id": 7,  
+      "shortName": "ssh",  
+      "externalPort": 22,  
+      "loadBalance": false  
+    }  
+  ],  
+  "version": "22.04",  
+  "hideLock": true,  
+  "cloud": {  
+    "name": "QA VMware",  
+    "id": 26324  
+  },  
+  "layout": {  
+    "code": "vmware-ubuntu-22.04-single",  
+    "id": 2608414  
+  },  
+  "showScale": false,  
+  "environment": "2",  
+  "networkInterfaces": [  
+    {  
+      "ipMode": "",  
+      "primaryInterface": true,  
+      "showNetworkPoolLabel": true,  
+      "showNetworkDhcpLabel": false,  
+      "network": {  
+        "idName": "VLAN0002 - Internal Server",  
+        "pool": {  
+          "name": "10.32.20.0 /22",  
+          "id": 18823  
+        },  
+        "id": "network-173431",  
+        "hasPool": false  
+      },  
+      "networkInterfaceTypeId": 4,  
+      "networkInterfaceTypeIdName": "VMXNET 3"  
+    }  
+  ],  
+  "copies": 1,  
+  "loadBalancer": [],  
+  "name": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "storageControllers": [  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 0,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "IDE 0",  
+      "typeId": 2,  
+      "id": 1729031,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 1,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "1",  
+      "removable": false,  
+      "name": "IDE 1",  
+      "typeId": 2,  
+      "id": 1729032,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "SCSI LSI Logic Parallel",  
+      "maxDevices": 15,  
+      "displayOrder": 2,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": 7,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "SCSI 0",  
+      "typeId": 4,  
+      "id": 1729030,  
+      "category": "scsi"  
+    }  
+  ],  
+  "config": {  
+    "poolProviderType": null,  
+    "isVpcSelectable": true,  
+    "smbiosAssetTag": null,  
+    "isEC2": false,  
+    "resourcePoolId": "pool-139625",  
+    "hostId": null,  
+    "createUser": true,  
+    "nestedVirtualization": null,  
+    "vmwareFolderId": "group-v80",  
+    "noAgent": false  
+  },  
+  "plan": {  
+    "code": "vm-8192",  
+    "id": 149  
+  },  
+  "group": {  
+    "name": "All Clouds",  
+    "id": "2"  
+  }  
+}
+```
+```
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json b/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
new file mode 100644
index 0000000..5675b1f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+  "title": "Nesting Workflows",
+  "ordinal": 119,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html",
+  "topic_cluster": {
+    "clustering_title": "Nesting Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md b/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
new file mode 100644
index 0000000..6c21ec8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
@@ -0,0 +1,9 @@
+# Nesting Workflows
+
+HPE Morpheus Enterprise allows Workflows to be nested for easier Workflow creation when many Workflows are used in an environment which have only slight differences or which are made up of common pieces. Nestable Workflows are created like any other Operational Workflow. Once the Workflow is saved, it can be embedded into a special Task type called “Nested Workflow.” A Nested Workflow-type Task simply references an Operational Workflow which may need to be used within other Workflows. Once Nested Workflow Tasks are created they can be used as part of any new Operational or Provisioning Workflows that are created thereafter (or may be added to existing Workflows too). For more on creating Tasks, see HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#tasks).
+
+NOTE
+
+Results from prior Tasks are still accessed using the same syntax even when a prior Task is embedded in a Nested Workflow. Additional syntax to reference the Nested Workflow Task or the Workflow itself are not needed. See HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#task-results) for more on chaining Task results.
+
+Nested Workflows Video Demo
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json b/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
new file mode 100644
index 0000000..8a9a286
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+  "title": "Contacts",
+  "ordinal": 261,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html",
+  "topic_cluster": {
+    "clustering_title": "Contacts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md b/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
new file mode 100644
index 0000000..f313cc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
@@ -0,0 +1,10 @@
+# Contacts
+
+To configure user notifications, a contact must first be created in Monitoring  >  Contacts. These contacts can be one of a few types:
+
+- **Contact:** Used for either Email or SMS
+- **Web Hook:** Used for posting a notification to a web endpoint or Alert Ops
+- **Slack Hook:** Used for posting notifications to a Slack channel (ex. [https://slack.com/[Slack](https://slack.com/%5BSlack)])
+- **VictorOps:** Provides a web post format consistent with the required notification format for Victor Ops.
+
+Most of these options provide convenient examples and information when configuring the contact. Once they are configured, contacts can freely be used to build Alert Rules.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json b/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
new file mode 100644
index 0000000..38ebf30
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+  "title": "Uploading OS Images Using S3-Compatible Object Storage",
+  "ordinal": 409,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md b/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
new file mode 100644
index 0000000..57f63ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using S3-Compatible Object Storage
+
+## About this task
+
+S3-compatible object storage (such as MinIO) provides scalable and durable storage for OS images.
+
+## Procedure
+
+1. Configure an S3 storage bucket under Infrastructure > Storage > Buckets.
+2. Provide access credentials with read/write permissions.
+3. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+4. Confirm successful upload and activation.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json b/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
new file mode 100644
index 0000000..1f0eb63
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+  "title": "Cloud Resource Tagging with Morpheus",
+  "ordinal": 371,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Resource Tagging with Morpheus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md b/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
new file mode 100644
index 0000000..acc088f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
@@ -0,0 +1,91 @@
+# Cloud Resource Tagging with Morpheus
+
+## Introduction
+
+As organizations scale their cloud environments, they often need to devise methodologies for organizing those resources. Tags consist of key and optional value pairs which make it easier to search for or filter your cloud resources based on categories relevant to the organization. While each public or private cloud handles tagging slightly differently, Morpheus removes that complexity and differentiation by handling tags in a consistent way across clouds. In addition, the Morpheus policy engine gives administrators tools to set up guard rails and ensure cloud resource tagging is handled consistently with each provisioning.
+
+This guide will go through Morpheus tagging features and best practices, as well as include provisioning examples from some of the most commonly integrated clouds.
+
+NOTE
+
+Tag syncing is bi-directional in Morpheus for supported clouds. Tag syncing is currently supported in Amazon, Azure, Google, VMware, and Alibaba Clouds.
+
+## Tagging on Provisioning
+
+In the simplest use case, tags can be entered manually in most provisioning scenarios. For example, on the Configure tab of the Create Instance wizard, the user can expand the Tags section and enter as many Tags as he or she needs to comply with organization practices.
+
+![../../_images/1_manual_tag.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A9D53B5E-99C6-49D9-9F6E-8E1A18C1CFA7-high.png)
+
+Once the resource is deployed, Tags are synced and applied to the provisioned machine in the relevant cloud. Tags are shown on the Instance detail page in Morpheus and can also be confirmed in the cloud console if desired. Tag syncing is also a two-way street in that any tag updates applied within Morpheus or within the cloud console will be reflected everywhere.
+
+NOTE
+
+Tag updates made in the cloud console may take up to five minutes to be reflected in Morpheus UI following the next sync of cloud data.
+
+## Custom Instance Types and Tagging
+
+Manually tagging resources as described in the previous section will work in some cases but many administrators will likely need to pre-seed the provisioning wizards with tagging prompts or build dropdown lists for tag values. This is accomplished in Morpheus through the use of custom Instance Types, Inputs, and Option Lists.
+
+To get started, first create an Option List to hold dropdown or typeahead sets of available key values if needed based on organizational tagging policy. If the tag value field should be manually entered at provision time or if the value field is to be left blank, this step can be skipped. Option Lists are created and stored in the Morpheus Library (Library). They can be populated manually by entering CSV or JSON datasets as shown in the example below. They can also be dynamically populated through Morpheus API or REST calls.
+
+![../../_images/2_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5216C432-43A8-4C56-9D07-4C3D728D757A-high.png)
+
+With the set of possible values defined (if needed), we next create an Input to prompt the user for tag input when provisioning relevant Instance types. Inputs are also housed in the Morpheus Library (Library).
+
+It’s important to note the value entered for the FIELD NAME on the new Input will be set as the tag key. The EXPORT AS TAG box should also be marked. By default, the TYPE value is Text. This is appropriate when the user should be prompted with a free text field at provision time to enter a tag value. To tie this Input to the Option List that was just created (if needed), change the TYPE value to Select List or Typeahead. Typeahead works best for very long lists while Select List is often a better user experience for lists of a more manageable size. Set the Option List we created in the previous step in the OPTION LIST value (if needed).
+
+![../../_images/3_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FC1E55AE-02D8-40CB-9BE5-E0ED9106E1E7-high.png)
+
+At this point, we are ready to add this Input to any custom Instance Types or Layouts. When those Instance Types or Layouts are provisioned, the values input by the user become tags associated with the created cloud resources. By setting the Input on an Instance Type, the tag selection appears when provisioning all associated Layouts. Alternatively, if the Input is set on individual Layouts, it will only appear when those Layouts are provisioned.
+
+Instance Types and Layouts are also stored in the Morpheus Library (Library). By opening up any custom Instance Type, we can add the Input we just created when editing the Instance Type. Additionally, we can drill into associated Layouts and apply the Input to selected Layouts if that’s more appropriate.
+
+![../../_images/4_instance_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3F4F0DA9-5384-489B-AC6F-C33024D7F939-high.png)
+
+Going forward, each time the chosen Instance Type or Layout is provisioned, the user will be prompted to enter relevant tag selections. We can even require the user input these values or govern their inputs through tagging policies which will be discussed in the next section.
+
+## Instituting Tagging Policies
+
+If needed, Morpheus allows cloud resource tagging to be governed through its native policy engine. Like other policies, tag policies are added from Administration > Policies. By creating a new policy and setting the TYPE to Tags, the relevant fields are revealed.
+
+NOTE
+
+Tag policy scanning and enforcement is only currently supported for Azure, Amazon AWS, VMware, and Google Cloud Platform clouds. Additional Clouds may be supported in the future.
+
+With a tag policy, we can choose to enforce the policy on a strict or passive basis by marking or unmarking the STRICT ENFORCEMENT box. Strictly enforced tagging policies will not allow provisioning to proceed in supported clouds if the policy requirements are not met. If we opt to enforce the policy passively, a warning banner will appear on the detail page of any server that does not meet policy requirements. Additionally, existing servers in supported clouds will be scanned and those which do not meet policy requirements will also receive the warning banner.
+
+A tag policy must be given a KEY value. If we define only a KEY value, the policy will look for a tag with that key and any (or no) value. Alternatively, we can select any pre-existing Option List as the VALUE LIST to require the tag contain a value that exists in that list or even enter a specific VALUE.
+
+Finally, like other HPE Morpheus Enterprise policies, we can choose to scope it globally, by group, by cloud, or by user. Primary Tenant administrators can also choose to scope the policy to one or more Subtenants.
+
+![../../_images/5_tag_policy_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B7104343-4BFF-4072-808C-403A0182CD17-high.png)
+
+## Tagging in Action
+
+With the prep work complete, we can take a look at our Inputs in action at provision time. In this example case, several Inputs have been created and applied to one custom Instance Type. The example Instance Type has three associated CentOS Layouts, one for AWS, one for VMware, and one for Azure. Regardless of the selected Layout, users are prompted to fill the same tag fields and our tagging remains consistent regardless of the user who is provisioning a new resource at the time.
+
+## Tagging and AWS
+
+When provisioning my CentOS Instance Type with an Amazon Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/6_aws_provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-45A12345-D313-46FB-9806-C09FB33C0A9B-high.png)
+
+In the AWS web console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to the AWS web console. The opposite is also true.
+
+![../../_images/7_aws_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9164DCFD-602C-4B6B-ADA7-B389FB81215E-high.png)
+
+## Tagging and VMware
+
+When provisioning my CentOS Instance Type with a VMware Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/8_vmware_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-264EA4E8-7CD7-45D2-9CE1-CF46AC2E0598-high.png)
+
+In the VMware console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to VMware. The opposite is also true.
+
+## Tagging and Azure
+
+When provisioning my CentOS Instance Type with an Azure Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/9_azure_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-62F1E8EF-C109-4E41-BAF8-C76B9E31E27F-high.png)
+
+In the Azure console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to Azure. The opposite is also true.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json b/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
new file mode 100644
index 0000000..cca74e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+  "title": "Resizing Volume",
+  "ordinal": 445,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html",
+  "topic_cluster": {
+    "clustering_title": "Resizing Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md b/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
new file mode 100644
index 0000000..0a80866
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
@@ -0,0 +1,12 @@
+# Resizing Volume
+
+## About this task
+
+This procedure allows the user to resize a volume. Volume size can only be increased. A rescan is required on the server OS to see the increased size.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Resize for the volume to be deleted.
+3. Specify the new size and click Resize.   
+   ![Resize volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9E3B3BDC-4EE0-491F-B1FC-BDFF31E19553-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json b/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
new file mode 100644
index 0000000..e0185dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+  "title": "Specifying Network Usage",
+  "ordinal": 436,
+  "parent_title": "Network Usage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html",
+  "topic_cluster": {
+    "clustering_title": "Specifying Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md b/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
new file mode 100644
index 0000000..e3f837b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
@@ -0,0 +1,21 @@
+# Specifying Network Usage
+
+## About this task
+
+Perform the following to specify networks used during instance provisioning:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Provisioning > Instances.
+3. Select **HPE**Bare Metal (ILO) Server as the type.
+4. Click Next.
+5. Specify a Group, Cloud, and a Name for the Instance.
+6. Click Next.
+7. Select a Network.
+8. Select an interface type (Bond/Physical).
+9. Specify any required virtual interface.
+10. Click Next and complete. ![Instance Bond Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5359D1DC-7863-49EC-9F61-4C14BFC8F0F1-high.png)
+
+    For physical interfaces, the interfaces represent the physical ports in their display order. Virtual networks specify that tagged networks under the primary network specified are to be configured on the server OS with an IP interface. If any of those tagged networks are not required to be configured on the server OS as an IP interface, do not specify a virtual interface for those.   
+    ![InstancePhysicalNetwork](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CA592D7B-4562-4AA1-8A46-BF66F13DC305-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.json b/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.json
new file mode 100644
index 0000000..af43957
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+  "title": "Dashboard",
+  "ordinal": 54,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2277183A-E315-4439-A885-C111A77C7154.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.md b/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.md
new file mode 100644
index 0000000..c0eaad7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2277183A-E315-4439-A885-C111A77C7154.md
@@ -0,0 +1,80 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within HPE Morpheus Enterprise UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+NOTE
+
+Opensearch 7.16+ is required for the Log Trends Dashboard panel to work. When using versions below 7.16 you will see error messages in logs due to this panel missing needed dependencies to work correctly but these errors may be safely ignored.
+
+## Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of HPE Morpheus Enterprise user accounts
+
+## System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [HPE Morpheus Enterprise Health](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html#GUID-E6FCD7DB-6973-459F-9EBC-3088B211CF1C).
+
+## Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
+
+## Alarms
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
+
+## Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
+
+## Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+## Daily Cloud Instances
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
+
+## Group Workloads
+
+The instantaneous count of host or container records broken down by Group association
+
+## Cloud Workloads
+
+The instantaneous count of host or container records broken down by Cloud association
+
+## Cluster Workloads
+
+The instantaneous count of managed containers broken down by Cluster association
+
+![../_images/dashboard2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1B7CFE86-1657-4EF7-B515-E3D104CDB5D2-high.png)
+
+## Log History
+
+Log History shows a snapshot of various time segments throughout the current day and the number of logs generated during each segment. Hover over any bar on the graph to see a breakdown in severity of the logs within each segment
+
+## Log Trends
+
+Log Trends identifies and lists repeated messages found in recent longs. If desired, this view can be filtered to show only Error or Warning-level log messages
+
+## Job Executions
+
+Displays the number of successful and unsuccessful Job executions over the last day, week or month
+
+## Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
+
+## Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
+
+## Activity
+
+The activity list displays the last few events that have taken place in HPE Morpheus Enterprise by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json b/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
new file mode 100644
index 0000000..fd165e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+  "title": "SCVMM",
+  "ordinal": 470,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.html",
+  "topic_cluster": {
+    "clustering_title": "SCVMM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md b/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
new file mode 100644
index 0000000..dd30a9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
@@ -0,0 +1,240 @@
+# SCVMM
+
+NOTE
+
+HPE Morpheus Enterprise supports SCVMM cloud deployment as HA SCVMM failover cluster. You must follow the process to have a singular agent API key and only one agent online at a time.
+
+## Requirements
+
+- Access to SCVMM host on port 5985 for Agent installation
+- Access to Hyper-V host on port 2179 for hypervisor console access
+- HPE Morpheus Enterprise Agent installation (installed on the target SCVMM host via port 5985 and WinRM)
+- User with administrator privileges
+
+## Agent Requirement
+
+SCVMM and Hyper-V integrations utilize the HPE Morpheus Enterprise Agent for communication with the HPE Morpheus Enterprise appliance, making the HPE Morpheus Enterprise Agent required. This also means SCVMM and Hyper-V Clouds can only point to one HPE Morpheus Enterprise Appliance at any given time. If another HPE Morpheus Enterprise Appliance adds an SCVMM or Hyper-V Cloud thats is already managed by another HPE Morpheus Enterprise Appliance, the HPE Morpheus Enterprise Agent appliance\_url will be updated to point to the new HPE Morpheus Enterprise appliance\_url, and the previous HPE Morpheus Enterprise Appliance will no longer be able to communicate with the SCVMM Cloud or Hyper-V Cloud until the Agent configuration is updated to point to the previous appliance again. In HPE Morpheus Enterprise version 4.2.1 and higher, multiple HPE Morpheus Enterprise clouds can be created by integrating with the same SCVMM host. This allows users to create separate Clouds with are scoped to different SCVMM Cloud, Host and/or Cluster combinations.
+
+## Add a SCVMM Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select SCVMM, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   NOTE
+
+   You will need to open port 5985 in order for HPE Morpheus Enterprise to communicate to SCVMM. You will also want to make sure the SCVMM Controller has WinRM enabled.
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   SCVMM HOST
+   :   IP address or URL of SCVMM host server
+
+   USERNAME
+   :   SCVMM Username, for example: svc.scvmm
+
+   PASSWORD
+   :   SCVMM user Password
+
+   CLOUD
+   :   To scope the SCVMM Integration to a single Cloud, select it from the Cloud dropdown, which populates after establishing communication and authorization over port 5985 using the supplied username and password. To scope to all Clouds, leave the dropdown selection as `Select Cloud`
+
+   HOST GROUP
+   :   To scope the SCVMM Integration to a single host group, select a host group from the dropdown list. To scope to all host groups, select `All Hosts`
+
+   CLUSTER
+   :   To scope the SCVMM Integration to a single cluster, select a cluster from the dropdown list. To scope to all host groups, select `All`
+
+   LIBRARY SHARE
+   :   Select a Library Share to be used with the cloud integration
+
+   SHARED CONTROLLER
+   :   When creating additional HPE Morpheus Enterprise clouds that point to an SCVMM host already integrated with this appliance, select the appropriate shared controller value from the dropdown.
+
+       IMPORTANT
+
+       Only set `SHARED CONTROLLER` on additional HPE Morpheus Enterprise clouds and not on the Primary HPE Morpheus Enterprise SCVMM cloud. Failure to set the `SHARED CONTROLLER` on secondary HPE Morpheus Enterprise clouds pointed to the same SCVMM cluster will cause agent comm issues resulting in provisioning failures.
+
+       WORKING PATH
+       :   Path for HPE Morpheus Enterprise to write to, for example `c:\cloud`
+
+       DISK PATH
+       :   Path for Virtual Disks, for example `c:\virtualdisks`
+
+       HIDE HOST SELECTION FROM USERS
+       :   Prevents host selection from appearing in provisioning wizards
+
+       INVENTORY EXISTING INSTANCES
+       :   Enable for HPE Morpheus Enterprise to automatically discover existing VMs in the scoped resources
+
+       ENABLE HYPERVISOR CONSOLE
+       :   Enable to use VNC Hypervisor Console for HPE Morpheus Enterprise console connection as opposed to the default SSH and RDP console connection methods. Requires resolution of all Hyper-V host names and access over port 2179 from the HPE Morpheus Enterprise appliance to Hyper-V hosts.
+
+       SCVMM Specific Advanced Options
+
+       INSTALL AGENT
+       :   Enabled by default, INSTALL AGENT installs the HPE Morpheus Enterprise agent on the scvmm Controller when adding the cloud, which is required for full functionally unless using a shared controller in which scenario the agent would already be installed on the scvmm controller node. Disabling INSTALL AGENT on the cloud config when not using a shared controller will remove the ability to provision to the cloud.
+
+       Advanced Options
+
+       DOMAIN
+       :   Specify a default domain for instances provisioned to this Cloud.
+
+       SCALE PRIORITY
+       :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+       APPLIANCE URL
+       :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+       TIME ZONE
+       :   Configures the time zone on provisioned VM’s if necessary.
+
+       DATACENTER ID
+       :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+       NETWORK MODE
+       :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+       LOCAL FIREWALL
+       :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+       SECURITY SERVER
+       :   Security Server setting is for Security Service Integrations such as ACI
+
+       TRUST PROVIDER
+       :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+       STORAGE MODE
+       :   Single Disk, LVM or Clustered
+
+       BACKUP PROVIDER
+       :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+       REPLICATION PROVIDER
+       :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+       GUIDANCE
+       :   Enable Guidance recommendations on cloud resources.
+
+       COSTING
+       :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+       DNS INTEGRATION
+       :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+       SERVICE REGISTRY
+       :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+       CONFIG MANAGEMENT
+       :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+       CMDB
+       :   Select CMDB Integration to automatically update selected CMDB.
+
+       CMDB DISCOVERY
+       :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+       CHANGE MANAGEMENT
+       :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+       AGENT INSTALL MODE
+       :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+           - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+       VDI GATEWAY
+       :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+       CUSTOM LOGOS
+
+       When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+       INVENTORY OPTIONS
+
+       Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+       - Service Plans
+       - Resource Pools
+       - Networks
+       - Security Groups
+       - Datastores
+       - Folders
+
+       Provisioning Command
+
+       PROXY
+       :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+       Bypass Proxy for Appliance URL
+       :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+       NO PROXY
+       :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+       USER DATA (LINUX)
+       :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After clicking NEXT, the new Cloud can be added to a Group or configured with additional advanced options.
+
+### Create Ubuntu 22.04 image template
+
+Use the template creation steps detailed in the below article:
+
+https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006774en\_us&page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD\_2.html#ariaid-title1
+
+with the exceptions as below:
+
+1. Enable required VM integration services before deploying the VM
+
+- Naviagate to "Hardware Configuration" -> "Advanced" -> "Integration Services". Check the checkbox "Guest services" under "Services".
+
+2. After the the step titled "Complete the installation process and reboot the machine. Update the package list and apply any upgrades", execute the below (to install a collection of utilities for hypervisor integration) :
+
+```
+```
+sudo apt install -y linux-cloud-tools-$(uname -r) linux-tools-$(uname -r)
+```
+```
+
+Follow the subsequent steps as in the article.
+
+**Create windows template**
+
+Create a new machine in SCVMM and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+**Procedure**
+
+- Apply any service packs / updates to the operating system.
+- Install .Net at least 4.5.2
+- Install SCVMM Agent
+- Ensure Windows Firewall will allow WinRM connections.
+- Shutdown the virtual machine and convert to a template.
+
+  Note : Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json b/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
new file mode 100644
index 0000000..9227fca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+  "title": "Repositories",
+  "ordinal": 97,
+  "parent_title": "Code",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html",
+  "topic_cluster": {
+    "clustering_title": "Repositories",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md b/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
new file mode 100644
index 0000000..5816d96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
@@ -0,0 +1,128 @@
+# Repositories
+
+The Provisioning ‣ Code ‣ Repositories section contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repository folders and files, view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. This section also handles Import/Export functionality which allows users to backup HPE Morpheus Enterprise items (Tasks, Library Items, etc.) as code in a repository which can also be imported into another appliance, if desired.
+
+- Browse integrated repositories
+- View repo files
+- Switch branches
+- Trigger repo refreshes
+- Filter by Integration, Organization or Text search
+- Create Custom Views
+- Create Tasks from repo files
+- Create Spec Templates from repo files
+
+## Role Permissions
+
+Access and capabilities for the **Repositories** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Administration: Users`
+:   - None: Can view repo list but cannot browse repo folder and file names, select branch, refresh repositories or access/view file contents
+    - Read or Full: Can view repo list, browse repo folder and file names, select branch, refresh repositories. Cannot access/view file contents without Read or Full level permission on `Provisioning: Code Repositories`
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents
+
+Role: Feature Access: `Provisioning: Tasks`
+:   - None: Cannot create Tasks from repo files in repository browser
+    - Read or Full: Can create Tasks from repo files in repository browser
+
+Role: Feature Access: `Provisioning: Library`
+:   - None: Cannot create Spec Templates from files in repository browser
+    - Read or Full: Can create Spec Templates from files in repository browser
+
+## List Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Users with sufficient permissions will see a list view of all integrated code repositories
+4. Use the Search, Integrations or Organizations filter to filter listed repositories
+
+### Results
+
+TIP
+
+Select the gear icon ⚙ in the top right of the repos list view to create and save custom list views.
+
+## Refresh Repository
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ACTIONS ▿ > `Refresh`
+
+## Browse Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Users with sufficient permissions can browse repo folder and file names, select branches, and refresh repositories. Users can access/view file contents with Read or Full level permission on `Provisioning: Code Repositories`
+5. Select target folder icon to drill into the folder
+
+## View Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ℹ icon to right of target file name
+
+### Results
+
+NOTE
+
+Users can access/view file contents only with Read or Full level permission on `Provisioning: Code Repositories`. File contents displayed is from last repo sync. Refresh repo to ensure current version for recent commits.
+
+## Create Task from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of compatible target file name
+5. Select target task type from available actions
+6. Complete the NEW TASK wizard to create a new Task. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Shell and Powershell Tasks types can be created from the code repo browser in v8.0.7. Ensure file compatibility with target Task type.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Tasks`.
+
+## Create Spec Template from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of target file name
+5. Select target spec template type from available actions
+6. Complete the NEW SPEC TEMPLATE wizard to create a new Spec Template. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Terraform spec template types can be created from the code repo browser in v8.0.7. Other spec template types can be created from repo files by changing the TYPE field in the NEW SPEC TEMPLATE wizard.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Templates`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..41b87ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 264,
+  "parent_title": "Tools",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..7fbcf01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,199 @@
+# Cypher
+
+## Overview
+
+Cypher at its core is a secure Key/Value store. But what makes cypher useful is the ability to securely store or generate credentials to connect to your instances. Not only are these credentials encrypted but by using a cypher you don’t have to burn in connection credentials between instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
+
+## Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between HPE Morpheus Enterprise and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
+
+## Creating Cypher Keys
+
+### Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
+
+## Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
+
+## tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
+
+## Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your HPE Morpheus Enterprise user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
+
+## UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than HPE Morpheus Enterprise. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the HPE Morpheus Enterprise Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
+
+## Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
+
+## Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another HPE Morpheus Enterprise user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks and Workflows that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
+
+NOTE
+
+You can reference the original owner of a workflow so that keys can be used in a subtenant. Example `PASSWORD=<%=cypher.read('secret/myuserpassword')%>` could be changed to `PASSWORD=<%=cypher.read('secret/myuserpassword',true)%>` within a library or a workflow and the true means OWNER true. This will keep that key in the master tenants cypher store.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json b/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
new file mode 100644
index 0000000..8775500
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+  "title": "Add NSX advanced load balancer",
+  "ordinal": 503,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX advanced load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md b/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
new file mode 100644
index 0000000..edfda56
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
@@ -0,0 +1,34 @@
+# Add NSX advanced load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX Advanced Load Balancer**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX adv LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0257709D-4A5C-441C-9E7B-C5793572100E-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   API HOST \*
+   :   Enter the API host name.
+
+   API PORT \*
+   :   Enter the PORT number.
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NSX service account username.
+   :   **PASSWORD \***: Enter NSX service account password.
+
+   AVI CLOUD
+   :   From the drop-down list, select the AVI cloud (VMware Avi Load Balancer).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json b/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
new file mode 100644
index 0000000..d0ac9f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+  "title": "Delete Workflow",
+  "ordinal": 121,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md b/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
new file mode 100644
index 0000000..2b5e366
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
@@ -0,0 +1,8 @@
+# Delete Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Delete icon on the row of the workflow you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json b/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
new file mode 100644
index 0000000..c9f58a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+  "title": "Canonical MAAS",
+  "ordinal": 461,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.html",
+  "topic_cluster": {
+    "clustering_title": "Canonical MAAS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md b/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
new file mode 100644
index 0000000..3c4dc06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
@@ -0,0 +1,42 @@
+# Canonical MAAS
+
+MAAS from Canonical is an open-source server orchestration tool. It’s designed to allow administrators to build a datacenter from on-premises, bare-metal servers where large networks of individual units can be discovered, deployed, and reconfigured.
+
+## Integrating MAAS and HPE Morpheus Enterprise
+
+### About this task
+
+Integrating MAAS with HPE Morpheus Enterprise is a simple process requiring the MAAS API URL and API Key. We’ll start by gathering what we need from the MAAS UI, then move back into HPE Morpheus Enterprise to store the required details.
+
+We can gather the API key by clicking on the username in the upper-right corner of the MAAS UI window. From this preferences page, click on “API keys” as shown in the screenshot:
+
+![../../../_images/1prefPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2CE6F9DA-2A53-497D-B397-89CE446156D7-high.png)
+
+From the API keys page, select the displayed key and copy it. Alternatively, you can click the copy button in the UI to add the full key to your clipboard. Store this key in an accessible location for a later step.
+
+![../../../_images/2maasApi.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C7F62A15-E82D-479B-9D76-2A83365CD918-high.png)
+
+In addition to the API key, we need the MAAS API URL. As entered in HPE Morpheus Enterprise, the value will be like the following example: `http://<maas-hostname-or-ip>:5240`. We’ll enter the API URL into HPE Morpheus Enterprise duriong the next step.
+
+In HPE Morpheus Enterprise, navigate to the list of integrated Clouds and start a new MAAS Cloud integration:
+
+### Procedure
+
+1. Infrastructure > Clouds
+2. Click + ADD
+3. Select “MAAS”
+4. Click NEXT
+
+### Results
+
+On the “CREATE CLOUD” modal, you must at least give a friendly name for the Cloud in HPE Morpheus Enterprise, MAAS API URL and API KEY. An example is shown below:
+
+![../../../_images/3createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AA9E6041-8181-4D62-8EC4-516C7234E0FF-high.png)
+
+TIP
+
+You’ll know the credentials are entered correctly when your list of MAAS resource pools is synced in as you can see in the example screenshot.
+
+Click NEXT and add this new Cloud to an existing Group or create a new Group for it. Once you advanced past the end of the wizard, the Cloud is added and HPE Morpheus Enterprise begins to inventory (if you’ve opted to inventory when adding the Cloud).
+
+![../../../_images/4cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-598C2A66-38D0-4401-B1C5-14CF91A97474-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json b/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
new file mode 100644
index 0000000..f1145b5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+  "title": "Active Directory",
+  "ordinal": 282,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html",
+  "topic_cluster": {
+    "clustering_title": "Active Directory",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md b/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
new file mode 100644
index 0000000..bc6bcbd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
@@ -0,0 +1,130 @@
+# Active Directory
+
+## Overview
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+## How It Works
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+## Example Integration
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in-built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+## Adding an Active Directory Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following: 
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES. 
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Troubleshooting
+
+### About this task
+
+If you’re unable to get the Active Directory integration to work, the following troubleshooting steps may be useful to ensure your appliance can talk to the Active Directory server.
+
+### Procedure
+
+1. Open firewall ports 
+
+   Source: HPE Morpheus Enterprise appliance Destination: AD server’s FQDN or IP address Non-SSL AD integration: TCP-389 SSL AD integration: TCP-636
+2. Checking open LDAP connections from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following:
+
+   ```
+   ```
+   $ sudo lsof i- | grep :ldap
+   ```
+   ```
+3. Check LDAP connectivity from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following. Be sure to replace the placeholder values in the command with the correct values for your environment:
+
+   ```
+   ```
+   $ ldapsearch   -x -h xx.xx.xx.xx -D "binding-user@acme.com" -W -b "cn=users,dc=acme,dc=com"
+   ```
+   ```
+4. Run tcpflow from the HPE Morpheus Enterprise appliance for non-SSL enabled AD identity Integrations 
+
+   Use tcpflow from the HPE Morpheus Enterprise appliance and then start the identity source configuration once again. Keep in mind this will only work for AD servers which are not SSL enabled:
+
+   ```
+   ```
+   $ sudo tcpflow -i any -c -v port 389
+   ```
+   ```
+5. Check the AD and domain controllers event logs 
+
+   Check the event logs for LDAP queries from the HPE Morpheus Enterprise appliance to ensure network connectivity.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..a618065
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 263,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..b4d39bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,9 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Image Builder](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
+- **[VDI Pools](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json b/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
new file mode 100644
index 0000000..ff9a026
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+  "title": "Email Templates",
+  "ordinal": 324,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html",
+  "topic_cluster": {
+    "clustering_title": "Email Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md b/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
new file mode 100644
index 0000000..485799d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
@@ -0,0 +1,50 @@
+# Email Templates
+
+## Email Templates
+
+HPE Morpheus Enterprise sends out email to its users periodically to alert for various conditions such as an Instance provisioning success, warnings about upcoming Instance expiration, requests for password reset links, and more. HPE Morpheus Enterprise includes system-default email templates for all of these emailed conditions but allows users to create their own email templates to override the default template.
+
+On accessing the Email Templates tab, users will see a list of all email templates that currently exist. We can also see the owner which created the template as well as the associated Account (Tenant). System-default templates are shown as being owned by “System” and show no associated Account (Tenant). When a Master Tenant user creates a template, the option is given to tie the template to an Account or to make a global template. The Accounts column will show “Global” for global templates. Templates will apply in order of specificity: Tenant-specific templates apply first, then custom global templates, and finally system templates if no others exist for that email type.
+
+IMPORTANT
+
+Email templates apply in order of specificity. Tenant-specific templates apply over custom global templates which apply over system-default templates.
+
+![../../_images/emailTemplateList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-278D8A99-12B8-47EE-8FC8-F360DDA69C70-high.png)
+
+### Creating Templates
+
+Before creating the first template, it’s important to realize email from custom templates will still come wrapped in the standard HPE Morpheus Enterprise email headers and footers. It will also have included styling. This styling comes directly from your Tenant whitelabel configuration and will include HPE Morpheus Enterprise standard styling or your custom whitelabel styling depending on appliance configuration. The template itself should only include email body content which will be inserted within the styling wrapper.
+
+IMPORTANT
+
+It is possible to break the functionality of certain types of generated email by creating a custom template. For example, in a password reset email, you must ensure the password reset button is still included with the template. Other functionality-breaking scenarios may also be possible. Review the system-default template of any email type to copy syntax examples for such vital components.
+
+Some template types will have variables accessible, such as the logged in user’s name (to address the email) or an Instance name. To see the available variables, click on the info button for the system-default template of the type you wish to create. You’ll see the variables mentioned in a comment at the bottom of the template such as in this example Confirm Password Update Template:
+
+```
+```
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.greeting"}}}</p>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.message"}}}</p>  
+<a href={{{url}}}>{{{i18n "com.bertramlabs.plugins.accounts.password.email.linkLabel"}}}</a>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.signature"}}} </p>  
+<!-- available hbs variables are user.displayName and user.username -->
+```
+```
+
+To begin creating a new template, from the Email Templates tab of the global settings page (Administration > Settings), click + CREATE. The following configurations must be set:
+
+- **TYPE:** Select the email type for the new template
+- **TEMPLATE:** The HTML markdown for the new custom email template
+- **TENANTS:** This option is only available in the Master Tenant. Select a specific Tenant to tie the template to that Tenant or leave it empty to create a global template
+
+The following is an example of a Forgot Password Template. Note that it calls in the variable for the associated user display name and username.
+
+```
+```
+<p>Hello {{{user.displayName}}},</p>  
+<p>You have requested to reset the password for the account with username: {{{user.username}}}.</p>  
+<p>To reset the password, please click the button below. If you did not make this request, you can ignore this email but you should change your password.</p>  
+<a href='{{{forgotPasswordUrl}}}' class="btn-primary">Magical Password Reset Button</a>
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json b/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
new file mode 100644
index 0000000..adf05a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+  "title": "Hardware Requirements",
+  "ordinal": 179,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md b/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
new file mode 100644
index 0000000..6d8ae13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System:** Ubuntu 22.04
+- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory:** 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space:** For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while HPE Morpheus Enterprise will configure Ceph for multi-node clusters
+- **Network Connectivity:** HVM hosts must be assigned static IP addresses. They also need DNS resolution of the HPE Morpheus Enterprise appliance and Internet access in order to download and install system packages for HVM dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus Enterprise Agent communication with the HPE Morpheus Enterprise appliance | HVM Host | HPE Morpheus Enterprise appliance server | 443 | TCP |
+| HPE Morpheus Enterprise Agent communication with the HVM Host for hypervisor console | HPE Morpheus Enterprise appliance server | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus Enterprise appliance server | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus Enterprise server SSH access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTP) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json b/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
new file mode 100644
index 0000000..05e3ad3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+  "title": "Morpheus UI war files",
+  "ordinal": 28,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus UI war files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md b/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
new file mode 100644
index 0000000..b42926c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
@@ -0,0 +1,51 @@
+# Morpheus UI war files
+
+## About this task
+
+Pre-release or patched versions of the HPE Morpheus Enterprise UI are sometimes provided. To deploy the ui war on a HPE Morpheus Enterprise Appliance:
+
+## Procedure
+
+1. Download the war file to the target appliance 
+
+   ```
+   ```
+   wget https://url/war_file
+   ```
+   ```
+
+   NOTE
+
+   If the war file is provided via a droplr link, ensure a `+` is added to end of droplr url or the file will not download
+2. Backup current war file 
+
+   ```
+   ```
+   sudo mv /opt/morpheus/lib/morpheus/morpheus-ui.war /opt/morpheus/lib/morpheus/morpheus-ui.bak.`date +"%m-%d-%Y"`
+   ```
+   ```
+3. Move and rename new war file 
+
+   ```
+   ```
+   sudo mv <file> /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+4. Ensure war is owned by `morpheus-app` 
+
+   ```
+   ```
+   sudo chown morpheus-app:morpheus-app /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+5. Restart the HPE Morpheus Enterprise UI 
+
+   ```
+   ```
+   sudo morpheus-ctl restart morpheus-ui
+   ```
+   ```
+
+## Results
+
+The new ui war will load on startup!
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json b/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
new file mode 100644
index 0000000..e53626c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 423,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md b/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
new file mode 100644
index 0000000..dd84c8c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
@@ -0,0 +1,28 @@
+# Firmware and Driver Lifecycle Management
+
+Starting with HPE BMaaS version 1.0.0, HPE Morpheus Enterprise supports firmware and driver updates for HPE ProLiant bare-metal servers using preloaded tasks and workflows. This capability enables administrators to centrally manage server firmware and driver compliance using HPE Service Pack for ProLiant (SPP) images, executed directly from the HPE Morpheus appliance.
+
+Firmware and driver updates are performed through **Jobs and Workflows** in HPE Morpheus and can be run in **Dry Run (inventory)** or **Deploy** modes. Updates can target firmware only, drivers only, or both, depending on operational requirements. The update process supports multiple servers per job and provides detailed execution logs for auditing and troubleshooting.
+
+## Prerequisites
+
+Before performing firmware and driver updates, ensure the following:
+
+- HPE BM Plugin version 1.0.0 or later is installed.
+- An appropriate HPESPP ISO is available for each server generation (for example, Gen10 and Gen11 require different SPP ISOs).
+- The HPE Morpheus appliance has access to the SPP ISO, either through:
+
+  - A locally downloaded ISO file, or
+  - A URL accessible without authentication.
+- For driver inventory and updates within a deployed operating system:
+
+  - iSUT (Integrated Smart Update Tools) and AMS (Agentless Management Service) must be installed and running on the target servers.
+  - ESXi hosts are expected to already have iSUT installed.
+
+**Subtopics**  
+
+- **[Adding HPE SPP to the Virtual Image Library](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html)**
+- **[Installing iSUT on Deployed Instances (Optional)](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html)**
+- **[Creating and Running an SPP Update Job](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html)**
+- **[Monitoring and Completion](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html)**
+- **[Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json b/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
new file mode 100644
index 0000000..66f5106
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+  "title": "API Access",
+  "ordinal": 339,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md b/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
new file mode 100644
index 0000000..1fc2227
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
@@ -0,0 +1,20 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+If needed, Primary Tenant administrators may configure the expiration periods for existing clients or create new clients from HPE Morpheus Enterprise global settings (Administration > Settings > Clients). See [client configuration documentation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html) for more details.
+
+- **morph-api:** Used for HPE Morpheus Enterprise API access and should be the default token-type used
+- **morph-cli:** Used for HPE Morpheus Enterprise CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json b/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
new file mode 100644
index 0000000..3f85ecd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+  "title": "Upgrading",
+  "ordinal": 20,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md b/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
new file mode 100644
index 0000000..08c98c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
@@ -0,0 +1,8 @@
+# Upgrading
+
+**Subtopics**  
+
+- **[Upgrading Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html)**
+- **[Single Node/AIO Appliance Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html)**
+- **[3-Node HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html)**
+- **[Full HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json b/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
new file mode 100644
index 0000000..b572844
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+  "title": "Okta",
+  "ordinal": 284,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html",
+  "topic_cluster": {
+    "clustering_title": "Okta",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md b/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
new file mode 100644
index 0000000..44ba4a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
@@ -0,0 +1,52 @@
+# Okta
+
+## Overview
+
+HPE Morpheus Enterprise allows users to integrate an Okta deployment for user management and authentication. In HPE Morpheus Enterprise, identity sources are added on a per-Tenant basis and Morpheus allows you to map Okta user groups to HPE Morpheus Enterprise user groups. User accounts are automatically created with matching metadata and role permissions when users are authenticated.
+
+## Adding an Okta Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + IDENTITY SOURCE
+5. Choose TYPE: “Okta”
+6. Populate the following, then select SAVE CHANGES:
+
+### Results
+
+Name
+:   Unique name for authentication type
+
+Description
+:   A description for your new Okta Identity Source
+
+Okta URL
+:   Your Okta URL
+
+Administrator API Token
+:   Your Okta Administrator API Token
+
+Required Group
+:   The Okta group that users must be in to have access (optional)
+
+Default Role
+:   The default role a user is assigned if no group is listed under an Okta user that maps within the Morpheus Role Mappings section
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Now, allowed Okta users can log into HPE Morpheus Enterprise via their Okta credentials and a user will be automatically generated within HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+NOTE
+
+If you’ve created multi-tenant roles, these will also appear here and can be mapped to Okta user groups allowing you to map users to equivalent user groups in HPE Morpheus Enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json b/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
new file mode 100644
index 0000000..2e069f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+  "title": "Edit Workflow",
+  "ordinal": 120,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md b/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
new file mode 100644
index 0000000..1318da7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
@@ -0,0 +1,10 @@
+# Edit Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Edit icon on the row of the workflow you wish to edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json b/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
new file mode 100644
index 0000000..cc2646f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+  "title": "Inputs",
+  "ordinal": 154,
+  "parent_title": "Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html",
+  "topic_cluster": {
+    "clustering_title": "Inputs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md b/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
new file mode 100644
index 0000000..ff3f658
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
@@ -0,0 +1,220 @@
+# Inputs
+
+Inputs are custom input fields that can be added to Instance Types and Layouts, then presented in Instance, App, and Cloning wizards. The resulting value is available in the Instance config map as <%=customOptions.fieldName%> or <%=customOptions[‘fieldName’], the latter syntax being required in certain situations such as when the field name contains a hyphen “-” (ex. <%=customOption[‘my-field-name’]). The fieldName and value can also be exported as Tags.
+
+![../../_images/new_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ADEB1679-C4C4-4345-B276-57B434C94563-high.png)
+
+## Create Input
+
+NOTE
+
+All possible fields listed. Displayed fields depend on `TYPE` selection
+
+NAME
+:   Name of the Input
+
+DESCRIPTION
+:   Description for reference in Input list view
+
+FIELD NAME
+:   This is the input fieldName property that the value gets assigned to
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+HIDDEN
+:   When marked, this Input will be hidden from the user but the value will still be accessible. This allows for alternate Input types to be used as hidden Inputs than what is possible with “Hidden” type Inputs (described further below). This is also different from Input “Visibility” settings as the values of non-visible Inputs is not accessible for consumption in automation routines
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value. It should also be noted that when an Input is not visible, its value is not available for consumption in automation routines. Use the “Hidden” flag (see above) to configure hidden yet accessible values
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+TYPE
+:   - **Text:** Text Input Field
+    - **Text Area:** A text area input, when selected an additional option appears to allow the user to configure the default number of visible rows in the text area
+    - **Select List:** Populated by Option Lists, presents a manual or REST-populated dropdown list
+    - **Checkbox:** Checkbox for `on` or `off` values
+    - **Number:** Input field allowing only numbers
+    - **Typeahead:** Populated by Option Lists: Rather than presenting a potentially-large dropdown menu, the user can begin typing a selection into a text field and choose the desired option. Multiple selections can be allowed with this type by marking the ‘ALLOW MULTIPLE SELECTIONS’ box
+    - **Hidden:** No field will be displayed, but the field name and default value will be added to the Instance config map for reference
+    - **Password:** An input field with suitable encryption for accepting passwords
+    - **Radio List:** Populated by Option Lists, presents a selection of radio buttons for the provisioning user
+
+LABEL
+:   This is the input label that typically shows to the left of a custom option
+
+ROWS
+:   For `Textarea` type Option Lists, determines how many text rows will be given when the Input is presented
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+REMOVE NO SELECTION
+:   For Select List-type Inputs. When marked, the Input will default to the first item in the list rather than to an empty selection. This is especially useful when only one choice is anticipated to be in the list as it saves the user from manually making a default selection
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+    **Verify Pattern Demo**
+
+DEFAULT CHECKED
+:   For `Checkbox` types, when marked the Checkbox will be checked by default
+
+OPTION LIST
+:   For `Select List` types, select a pre-existing Option List to set dropdown values
+
+    NOTE
+
+    `Select List` and `Typeahead` Inputs require creation and association of an Option List
+
+## Cascading Inputs
+
+One powerful facet of HPE Morpheus Enterprise Inputs is the ability to present users with different lists of input options based on their selections in other Inputs within the same wizard or modal. One common example, which is fully illustrated in this section, is to have a user select:
+
+- The Group they wish to provision into…
+- Then select the target Cloud from a list limited to Clouds which are in the selected Group…
+- Then select the target network from a list limited to networks which are available to the selected Cloud and Group
+
+To set this up, we will first configure our Inputs (custom option fields that can be applied to Instance Types and other HPE Morpheus Enterprise constructs) and Option Lists (dynamic lists of possible choices which can be associated with Inputs and presented in a dropdown or typeahead format). Once the custom options are configured, we will associate them with a new service catalog item and take a look at how the user would interact with them.
+
+### Group Custom Options
+
+To begin, we will create a new [Option List](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#option-lists) In this case, we will select type of “Morpheus Api” which will populate the list based on a call to the internal HPE Morpheus Enterprise API. Option Lists can also be populated by calls to external REST APIs or even from static lists that you enter manually. When dynamically populating Option Lists, whether via HPE Morpheus Enterprise API or an external API, translation and/or request scripts may be needed to prepare the request or translate the results. More on that as we build out the example.
+
+I have called my Option List “Groups” and selected “Groups” from the OPTION LIST menu. This simply indicates that Groups are the construct we want to call into our list from HPE Morpheus Enterprise API. In this case, we want to present a list of all Groups to the user by their name and pass the Group database ID in the background. Since it is common to create Option Lists from HPE Morpheus Enterprise API where the construct name is displayed to the user and the ID is passed, we actually do not need to input any translation scripts in this case. However, I will include a translation script here which does the same thing simply to provide more clarity to the example. HPE Morpheus Enterprise [Option List documentation](https://docs.morpheusdata.com/en/latest/library/options/option_lists.html) includes additional details on available translation script inputs and which are available without translation as a convenience feature.
+
+```
+```
+for (var x = 0; x < data.length; x++) {  
+  results.push({name: data[x].name, value:data[x].id});  
+}
+```
+```
+
+After saving the Option List, create the Input that presents the list we just created. I gave my Input the name of “Selected Group”, field name of “selectedGroup”, and label of “Group”. For type, choose “Select List” and a new field will appear at the bottom of the modal where we can select the Option List we just created. With this configuration, the Input will present as a dropdown list containing the options called from our Option List.
+
+### Cloud Custom Options
+
+Adding the Option List and Input for Clouds will be similar to the prior step with the exception that we will be including a request script which effectively filters the list of available Clouds to only those associated with the selected group. Follow the same process to start a new Option List, I have configured mine as follows:
+
+- **NAME:** Parsed Clouds
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Clouds
+
+We also need a request script that loads the `siteId` attribute of the `results` variable with the Group ID if the user has made a group selection. Essentially it appends this input as a query parameter to the API call, calling (for example) `./api/clouds?siteId=1` rather than `.../api/clouds`. It should be similar to the script below. Note that we are referencing the `selectedGroup` field name we created previously and that a “site” is the term for Groups in the HPE Morpheus Enterprise database.
+
+```
+```
+if (input.selectedGroup) {  
+  results.siteId = input.selectedGroup  
+}
+```
+```
+
+We also need a translation script which will be identical to the one used previously with the exception that if there is no input on the `selectedGroups` field, nothing will be displayed for the Clouds option.
+
+```
+```
+if (input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+We also need to create an Input to house this Option List. This process will be very similar to creating the previous Input except that we need to set selectedGroup as the Dependent Field. Setting a dependent field on an Input will trigger it to reload each time a selection is made in the indicated option. My configuration is as follows:
+
+- **NAME:** Parsed Cloud
+- **FIELD NAME:** parsedCloud
+- **DEPENDENT FIELD:** selectedGroup
+- **TYPE:** Select List
+- **LABEL:** Cloud
+- **OPTION LIST:** Parsed Clouds
+
+Save your changes once done.
+
+### Network Custom Option
+
+Finally, we will create an Option List/Input pair for network selection. In this case, it will be dependent on both the Group and Cloud selection. My Option List configuration is below:
+
+- **NAME:** Parsed Networks
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Networks
+
+### Request Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+  results.cloudId = input.parsedCloud  
+  results.groupId = input.selectedGroup  
+}
+```
+```
+
+### Translation Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+The Input is configured as follows:
+
+- **NAME:** Parsed Networks
+- **FIELD NAME:** parsedNetwork
+- **DEPENDENT FIELD:** parsedCloud
+- **TYPE:** Select List
+- **LABEL:** Network
+- **OPTION LIST:** Parsed Networks
+
+### Setting Custom Options at Provision Time
+
+At this point, our dependent options are ready to be applied to custom Instance Types, Workflows or Service Catalog items as needed. When creating them, we can select an unlimited number of Inputs from a typeahead field on the create modal and they will be presented when a user goes to provision that element or run that Workflow. As an example, I have created a Service Catalog item that incorporates the three Inputs we have created. You can see how the dependent fields reload and present different options based on my selections.
+
+![../../_images/cascadingOptionList.gif](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-41F98D9A-033E-4560-8F99-824818F25590-high.gif)
+
+## Visibility Field
+
+The Input Visibility field allows users to set conditions under which the Input field is displayed. Visibility field accepts `fieldName:value` or `fieldName:(regex)`, where “fieldName” equals the fieldName of another Input which will determine the visibility of this Input, and “value” equals the target value of the other Input (or a regex pattern that matches to the values that meet your desired conditions). You can simply enter “fieldName” when visibility should be triggered when any value is entered. When the value of the target Input matches the “value” or “(regex)” set in the Visibility field, this Input will be displayed. When the value of the target Input does not match “value” or satisfy the “(regex)” set in the Visibility field, this Input will not be displayed.
+
+Expanding on the simplified example above, we could trigger visibility based on any one of multiple selections from the same Input by using a different regular expression, such as `color:(red|blue|yellow)`. Additionally, we are not restricted to the conditions of just one Input to determine visibility as the following would also be valid: `color:(red|blue|yellow),shape:(square)`. In the previous example, the Input “Color” would have to be set to red, blue, or yellow OR the Input “Shape” would have to be set to square in order to trigger visibility of the Input currently being configured. Prepend the previous example with `matchAll::` in order to require both conditions to be met rather than one or the other (ex. `matchAll::color:(red|blue|yellow),shape:(square)`).
+
+## Required Field
+
+The Required field allows for Inputs to be conditionally required. In this field, enter the Field Name value for another Input and, if that Input is filled by the user, the current Input will become required. This feature could also be used in conjunction with the Visibility field described above in that you may want a field to be required when visible but not required when hidden. Below is a simple abstract example showing how the second displayed Input becomes required when the first displayed Input is filled.
+
+![../../_images/required.gif](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E44477FD-45A4-44BD-A7CA-0587E51A09ED-high.gif)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json b/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
new file mode 100644
index 0000000..1de8ad7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+  "title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+  "ordinal": 367,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md b/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
new file mode 100644
index 0000000..c3cc829
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
@@ -0,0 +1,207 @@
+# Creating XaaS Instance Types with HPE Morpheus Enterprise
+
+HPE Morpheus Enterprise version 5.4.2 and higher includes the ability to build and provision XaaS Instance Types. These are non-VM backed Layouts which allow users to represent anything as an Instance. This includes the ability to utilize Provisioning Workflows to manage all phases of the Instance lifecycles consistently and automatically. XaaS Instance Types can also be tied into service plans to track costs or bill customers.
+
+In this specific example, we will create an XaaS Instance Type to manage the lifecycle of folders within a Dropbox account. Users will be able to visit the HPE Morpheus Enterprise Catalog and have the folder created by entering a name for the folder and clicking a single button. We’ll see how each folder is then represented as an Instance. With the Instance standing, users will be able to update the folder name by simply editing a custom value on the Instance. Finally, when the Instance is deleted, the folder is deleted from Dropbox as well.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Clouds
+- Inputs
+- Tasks
+- Workflows
+- Instance Types
+- Layouts
+- Catalog Items
+- Instances
+
+NOTE
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. In this guide we will go through the process of creating a HPE Morpheus Enterprise-type Cloud which can be used to hold your XaaS resources.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the Dropbox API token as a Cypher entry. Creating Dropbox developer accounts and obtaining API keys goes beyond the scope of this guide but Dropbox developer tools are well-documented if you want to try this out for yourself. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dropboxtoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-865BCB56-4457-4DA6-A9A1-34CFCD22EEAE-high.png)
+
+One of my Tasks will also send a request to the HPE Morpheus Enterprise API so I’ll create a second Cypher entry to store a HPE Morpheus Enterprise API key:
+
+- **KEY:** secret/morphapitoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+## Create Cloud
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. For this example, I’m creating a Cloud just to organize Dropbox folders. Navigate to Infrastructure > Clouds and click + ADD. The only required steps to create the Cloud are to give it a name and associate it with a Group. I’ve given mine a generic name but you could opt to be more targeted with your naming if you will use many HPE Morpheus Enterprise-type Clouds to manage other types of resources.
+
+- **NAME:** MorphCloud
+
+![../../_images/1cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B1A71913-825C-4533-BBBD-AEF60F33F4F1-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create two Inputs in this case, one to allow the user to enter a name for their folder on provisioning and another which will be visible when editing the Instance to allow the user to rename their folder.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** DropBox Folder Name (The name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** dbfoldername (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **SHOW ON EDIT:** Checked (When checked, this Option is visible when editing an Instance)
+- **EDITABLE:** Checked (When checked, this Option is editable in addition to being visible while editing the Instance)
+- **LABEL:** DropBox Folder Name (The label the user sees next to the input field)
+
+Once done, click SAVE CHANGES
+
+![../../_images/2input.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-13B6ACC4-D949-465D-B229-1A7E9D065999-high.png)
+
+Next, configure a second Input with the following attributes:
+
+- **NAME:** DropBox Folder New Name
+- **FIELD NAME:** dbfoldernewname
+- **TYPE:** Text
+- **SHOW ON EDIT:** Checked
+- **EDITABLE:** Checked
+- **LABEL:**
+
+Click SAVE CHANGES
+
+## Create Tasks
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ll write the Task configuration directly into the HPE Morpheus Enterprise Tasks. However, Tasks can also be sourced directly from integrated version control repositories (like Github) so you never have to copy and paste code or make manual updates when your code changes.
+
+For this example, we need to create four Tasks. One to create the folder, one to rename the folder, one to rename the HPE Morpheus Enterprise Instance, and one to delete the folder. I’ve used Python Tasks to interact with the Dropbox Python SDK. I won’t go into how to write the individual Tasks here but the Python SDK is well-documented if you want to try things out for yourself. The same functions could be carried out using other Task types as well.
+
+![../../_images/3tasks.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BBDD2BA6-FF48-4A8B-903C-7F8C08E972A2-high.png)
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Dropbox - Create Folder
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Local (Select Repository to source your code from an integrated version control repository)
+- **CONTENT:** Enter Task content here
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the Dropbox API token from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US)
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES
+
+![../../_images/5createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-82B72BAF-618B-4F5A-B82F-8D4BE96BD27A-high.png)
+
+The process for creating the remaining three Tasks is very similar, expand the sections below to see screenshots of the Task config, if desired:
+
+### Dropbox - Delete Folder
+
+![../../_images/6deletetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-020E198F-49C6-4228-ABE8-C5580D223F15-high.png)
+
+### Dropbox - Rename Folder
+
+![../../_images/7renametask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-05551E97-6453-4079-A6D5-B0CF880BC840-high.png)
+
+### Dropbox - Reset Instance Name
+
+![../../_images/8resetinstancetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BFB5EBC7-4C8A-4F58-AB33-90475BCB8B6E-high.png)
+
+## Create Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need the following to occurring during the Instance lifecycle:
+
+- At the provisioning phase, we want a folder to be created
+- At the reconfigure phase (when the Instance is edited), we want the folder to be renamed and the Instance name to be updated
+- At the teardown phase (when the Instance is deleted), we want the folder to be deleted
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **PLATFORM:** All
+- **TASKS - Provision:** Dropbox - Create Folder
+- **TASKS - Reconfigure:** Dropbox - Rename Folder; Dropbox - Reset Instance Name
+- **TASKS - Teardown:** Dropbox - Delete Folder
+
+Once done, click SAVE CHANGES
+
+![../../_images/9workflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4710C85B-97B8-4EFB-B607-8D8289BEE58C-high.png)
+
+## Create Instance Type
+
+With the Workflow and Inputs complete, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. From this, we’ll create a catalog item that our users can order in a later step.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **CODE:** xaas
+- **CATEGORY:** Utility
+- **ICON:** If desired, search the file system on your local computer for a Dropbox logo icon for easier identification of this Instance Type at provision time
+- **ENVIRONMENT PREFIX:** XAAS
+
+![../../_images/10instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-08F8C46C-E7EE-4E11-B0D2-D204B32405B6-high.png)
+
+Click SAVE CHANGES.
+
+## Create Layout
+
+After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case Workflow. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on (when dealing with VM-based Instance Types). Configure the Layout as follows:
+
+- **NAME:** XaaS - Dropbox
+- **VERSION:** Latest
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Workflow
+- **WORKFLOW:** Select the Workflow we’ve just created, “XaaS - Dropbox”. By selecting this, all Instances provisioned with this Layout will automatically have our chosen Tasks run during specific Instance lifecycle phases
+- **INPUTS:** Search and find the two custom Inputs we created earlier, “DropBox Folder Name” and “DropBox Folder New Name”
+
+![../../_images/11layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3C57ACEF-141F-4DED-929C-1724C2B1F81C-high.png)
+
+## Create Catalog Item
+
+Catalog Items offer a simplified provisioning process. Administrators can create Catalog Items using existing Instance Types, App Blueprints, or Workflows. Most or all of the provisioning options can be pre-selected leaving fewer decisions up to the user and allowing them to easily create what they need. In this case, we’ll create one based on the Instance Type that was made in the previous sections. Navigate to Library > Blueprints > Catalog Items and click + ADD, then Instance. Configure the following:
+
+- **NAME:** XaaS - Dropbox Folder
+- **ENABLED:** Checked (If unchecked, this Catalog Item will not be displayed in the provisioning catalog for users)
+- **LOGO:** If desired, browse your local disk for a Dropbox logo to make this Catalog Item easily recognizable
+
+Then, click CONFIGURATION WIZARD. On the “TYPE” tab, search for the Instance Type we created and click NEXT. On the “Group” tab, select the HPE Morpheus Enterprise-type Cloud and enter any name (we’ll override this name value later so it’s dynamic based on user input). Click NEXT. On the “CONFIGURE” tab, the Layout and Plan fields should default to acceptable values. Enter anything for the “Dropbox Folder Name”, we will also update this to be dynamic in the next step. Click through the final two tabs, there’s no need to attach our Workflow on the “AUTOMATION TAB” since we already have it on our Layout. Finally, click COMPLETE.
+
+Once finished, you’ll see the JSON configuration map for the Instance loaded into the “CONFIG” field. Update the “dbfoldername” Input value and the Instance name value to dynamically take on the user-entered value on the “Dropbox Folder Name” field as I’ve done in my screenshot below:
+
+![../../_images/12catitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F93420D1-2F2A-479B-9ACD-56A52256AD43-high.png)
+
+Near the bottom of the modal window, search for and attach the “DropBox Folder Name” Input. This will be the only input our users need to make to order their folder. Then, click SAVE CHANGES
+
+## Ordering Catalog Item
+
+At this point, the configuration steps are completed. As a test, we can order a folder from the provisioning Catalog. Navigate to Provisioning > Catalog and click “Order” on our “XaaS - Dropbox Folder” item. We need only provide a name for our folder and click “Order Now”.
+
+![../../_images/13orderitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-27E8619F-240F-43AE-A00F-70489E83CE32-high.png)
+
+If we now head to Provisioning > Instances, we can see a new Instance entry has been created for our Dropbox folder. Note that the Instance is named for our folder name exactly as we configured earlier.
+
+![../../_images/14inslist.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2FA0BA43-267B-4BFD-8C3A-46A8879844F4-high.png)
+
+Taking a look in the Dropbox web console, we can also see a folder has been created just as we’d expect.
+
+![../../_images/15dbcreate.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-38887B6A-8B2B-44AA-BDA0-91C557D414F8-high.png)
+
+## Managing and Deleting Instances
+
+Back in HPE Morpheus Enterprise, we can take a look at the Instance detail page (Provisioning > Instances > Specific Instance) and perform some Day 2 actions. By clicking EDIT, we can update Instance details. When Input values are updated, HPE Morpheus Enterprise will automatically trigger reconfigure actions on our Instance. In our case, we’ve configured it to update the folder name in Dropbox and update the Instance name in HPE Morpheus Enterprise for easier identification. As you can see in the screen shot, I’m providing a new folder name value:
+
+![../../_images/16editins.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4A83E6DE-B560-4FBC-A948-892DA9AFBBE2-high.png)
+
+As expected, our Instance name is updated and the folder is renamed on the Dropbox side:
+
+![../../_images/17insdetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9E516B64-6C3D-4577-B7C6-E67FC23ADBB2-high.png) ![../../_images/18dbupdate.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FB2B154B-85F7-4AA0-B77E-FB596CE9F7FE-high.png)
+
+Finally, I’ll delete the Instance. This has the effect of deleting the Instance object out of HPE Morpheus Enterprise and triggering our Teardown-phase action which deletes the folder from Dropbox:
+
+![../../_images/19dbdelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5D5388E9-5251-499E-ABE9-36A1342F356C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json b/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
new file mode 100644
index 0000000..cd9d912
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+  "title": "3 Node HA Install Example",
+  "ordinal": 18,
+  "parent_title": "Installation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html",
+  "topic_cluster": {
+    "clustering_title": "3 Node HA Install Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md b/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
new file mode 100644
index 0000000..22baef3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
@@ -0,0 +1,489 @@
+# 3 Node HA Install Example
+
+Distributed App Nodes with Externalized MySQL Database
+
+A common and recommended HA Morpheus deployment consists of three app nodes using embedded services and an external MySQL DB cluster (minimum of 3 nodes).
+
+IMPORTANT
+
+HA environments installed without engagement from Morpheus are not eligible for support. The provided configuration serves as a sample only and requirements may vary. Please reach out to your account manager to discuss deploying a HA environment to meet the requirements for support.
+
+## Assumptions
+
+This guide assumes the following:
+
+- App nodes can resolve each others short names
+- All app nodes have access to shared storage mounted at `/var/opt/morpheus/morpheus-ui`.
+- This configuration is designed to tolerate the complete failure of a single node but not more. Specifically, the Elasticsearch tier requires MORE than 50% of the nodes to be up and clustered at all times. However, you can always add more nodes to increase resilience.
+- You have a load balancer available and configured to distribute traffic between the app nodes. [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
+
+![Morpheus 3-Node HA Architecture](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-627980F3-725B-4765-8CF0-89FD087667C8-high.png)
+
+## Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## MySQL requirements for Morpheus HA
+
+The requirements are as follows:
+
+- MySQL version v8.0.x (minimum of v8.0.72)
+- MySQL cluster with at least 3 nodes for redundancy.
+- Morpheus application nodes have connectivity to MySQL cluster.
+
+NOTE
+
+Morpheus does not create primary keys on all tables. If you use a clustering technology that requires primary keys, you will need to leverage the invisible primary key option in MySQL 8
+
+## Configure Morpheus Database and User
+
+### Procedure
+
+1. Create the Database you will be using with HPE Morpheus Enterprise. Login to mysql node: 
+
+   ```
+   ```
+   [root@node: ~]  mysql -u root -p  
+     # password: `enter root password`  
+   mysql> CREATE DATABASE morpheus CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;  
+   mysql> show databases;
+   ```
+   ```
+2. Next create your HPE Morpheus Enterprise database user. This is the user the HPE Morpheus Enterprise app nodes will auth with mysql. 
+
+   ```
+   ```
+   mysql> CREATE USER 'morpheus'@'%' IDENTIFIED BY 'morpheusDbUserPassword';
+   ```
+   ```
+3. Next Grant your new HPE Morpheus Enterprise user permissions. 
+
+   ```
+   ```
+   mysql> GRANT ALL PRIVILEGES ON morpheus.* TO 'morpheus'@'%' with grant option;  
+   mysql> GRANT SELECT, PROCESS, SHOW DATABASES, RELOAD ON *.* TO 'morpheus'@'%';  
+   mysql> FLUSH PRIVILEGES;  
+   mysql> exit
+   ```
+   ```
+
+## App Node Installation
+
+### Requirements
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `outbound` access to the various backend services:
+
+- mySQL Port to External DB
+
+  - 3306/tcp
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `inbound` from agents and users:
+
+- HTTPS Port
+
+  - 443/tcp
+- RabbitMQ Ports
+
+  - 4369 (epmd - inter node cluster discovery)
+  - 5671 (TLS from nodes to RabbitMQ)
+  - 5672 (non-TLS from nodes to RabbitMQ)
+  - 15671 (HTTPS API)
+  - 15672 (HTTP API)
+  - 25672 (inter node cluster communication)
+  - 61613 (STOMP - non-TLS)
+  - 61614 (STOMP - TLS)
+- OpenSearch Ports
+
+  - 9200 (API access)
+  - 9300 (inter node cluster communication)
+
+### Installation
+
+#### Procedure
+
+1. First begin by downloading and installing the requisite HPE Morpheus Enterprise packages to ALL HPE Morpheus Enterprise app nodes. 
+
+   HPE Morpheus Enterprise packages can be found in the Downloads section of the [Morpheus Hub](https://morpheushub.com/download)
+
+   RHELL/CentOS
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance-ver-1.el8.x86_64.rpm  
+   [root@node: ~] rpm -ihv morpheus-appliance-appliance-ver-1.el8.x86_64.rpm
+   ```
+   ```
+
+   Ubuntu
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance_ver-1.amd64.deb  
+   [root@node: ~] dpkg -i morpheus-appliance-appliance_ver-1.amd64.deb
+   ```
+   ```
+2. Do NOT run reconfigure yet. The HPE Morpheus Enterprise configuration file must be edited prior to the initial reconfigure.
+3. Next you will need to edit the HPE Morpheus Enterprise configuration file `/etc/morpheus/morpheus.rb` on each node. 
+
+   NOTE
+
+   In the configuration below, the UID and GID for the users and groups are defined for services that will be embedded. This ensures they are consistent on all nodes. If they are not consistent, the shared storage permissions can become out of sync and errors will appear for plugins, images, etc. If not specified, Morpheus will automatically find available UIDs/GIDs starting at 999 and work down. Availability of UIDs and GIDs can be seen by inspecting `/etc/passwd` and `/etc/group` respectively. Change the UIDs and GIDs below based on what is available.
+
+   You can find additional configuration settings [here](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#advanced-morpheus-rb-settings)
+
+   Node 1
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.01'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node01'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.02'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node02'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.03'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node03'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   NOTE
+
+   The configurations above for `` `mysql['host'] `` shows a list of hosts, if the database has multiple endpoints. Like other options in the configuration, `mysql['host']` can be a single entry, if the database has a single endpoint: `mysql['host'] = 'myDbEndpoint.example.com` or `mysql['host'] = '10.100.10.111'`
+
+   IMPORTANT
+
+   The OpenSearch node names set in `opensearch['node_name']` must match the host entries in opensearch[‘es\_hosts’]. `node_name` is used for `node.name` and `es_hosts` is used for `cluster.initial_master_nodes` in the generated opensearch.yml config. Node names that do not match entries in cluster.initial\_master\_nodes will cause clustering issues.
+
+   IMPORTANT
+
+   The rabbitmq[‘node\_name’] in the Node 1 example above is rabbit@node01. The shortname for the server of node01 must be resolvable by DNS or /etc/hosts of all other hosts, same for node02 and node03. FQDNs cannot be used here
+4. Mount shared storage at `/var/opt/morpheus/morpheus-ui` on each App node if you have not already done so. Create the directory if it does not already exist.
+5. Reconfigure on all nodes 
+
+   All Nodes
+
+   ```
+   ```
+   [root@node: ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   HPE Morpheus Enterprise will come up on all nodes and OpenSearch will auto-cluster. RabbitMQ will need to be clustered manually after reconfigure completes on all nodes.
+
+## Clustering Embedded RabbitMQ
+
+### Procedure
+
+1. Select one of the nodes to be your Source Of Truth (SOT) for RabbitMQ clustering (Node 1 for this example). On the nodes that are NOT the SOT (Nodes 2 & 3 in this example), begin by stopping the UI and RabbitMQ. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop morpheus-ui  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   [root@node2 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop morpheus-ui  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   [root@node3 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+2. Then on the SOT node, we need to copy the secrets for RabbitMQ. 
+
+   Begin by copying secrets from the SOT node to the other nodes.
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /etc/morpheus/morpheus-secrets.json  
+    "rabbitmq": {  
+      "morpheus_password": "***REDACTED***",  
+      "queue_user_password": "***REDACTED***",  
+      "cookie": "***REDACTED***"  
+    },
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /etc/morpheus/morpheus-secrets.json  
+     "rabbitmq": {  
+       "morpheus_password": "***node01_morpheus_password***",  
+       "queue_user_password": "***node01_queue_user_password***",  
+       "cookie": "***node01_cookie***"  
+     },
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] vi /etc/morpheus/morpheus-secrets.json  
+   "rabbitmq": {  
+     "morpheus_password": "***node01_morpheus_password***",  
+     "queue_user_password": "***node01_queue_user_password***",  
+     "cookie": "***node01_cookie***"  
+   },
+   ```
+   ```
+3. Then copy the erlang.cookie from the SOT node to the other nodes 
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # 754363AD864649RD63D28
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+
+   Nodes 3
+
+   ```
+   ```
+   [root@node3 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+4. Once the secrets and cookie are copied from node01 to nodes 2 & 3, run a reconfigure on nodes 2 & 3. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+5. Next we will join nodes 2 & 3 to the cluster. 
+
+   IMPORTANT
+
+   The commands below must be run at root
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop rabbitmq  
+   [root@node2 ~] morpheus-ctl start rabbitmq  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node02' ...  
+   [root@node2 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node02' with 'rabbit@node01' ...  
+   [root@node2 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node02' ...
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop rabbitmq  
+   [root@node3 ~] morpheus-ctl start rabbitmq  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node03' ...  
+   [root@node3 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node03' with 'rabbit@node01' ...  
+   [root@node3 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node03' ...
+   ```
+   ```
+
+   NOTE
+
+   If you receive an error `unable to connect to epmd (port 4369) on node01: nxdomain (non-existing domain)` make sure to add all IPs and short (non-fqdn) hostnames to the `/etc/hosts` file to ensure each node can resolve the other hostnames.
+6. Next reconfigure Nodes 2 & 3 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+7. The last thing to do is start the HPE Morpheus Enterprise UI on the two nodes that are NOT the SOT node. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+8. You will be able to verify that the UI services have restarted properly by inspecting the logfiles. A standard practice after running a restart is to tail the UI log file. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   The UI should be available once the Morpheus logo is displayed in the logs. Look for the ascii logo accompanied by the install version and start time:
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2024  
+   timestamp: ****************************************
+   ```
+   ```
+
+## Embedded Elasticsearch
+
+Morpheus clusters OpenSearch automatically.
+
+## Load Balancer
+
+Configure your load balancer to distribute traffic between the app nodes.
+
+You can see some examples here: [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json b/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
new file mode 100644
index 0000000..c135de5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+  "title": "Workloads: Apps Usage",
+  "ordinal": 70,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Apps Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md b/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
new file mode 100644
index 0000000..8613861
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
@@ -0,0 +1,32 @@
+# Workloads: Apps Usage
+
+![../_images/12appusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9916D4B0-7144-4088-98AC-2B2F2E780378-high.png)
+
+The Apps Usage dashboard lists all provisioned Apps that meet a set of filters and organizes them by Cloud. Totals for cost and resource usage of all relevant Apps can be viewed with a per-Cloud breakdown.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **TOTAL COST:** The total cost of all selected Apps
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Instance Usage List
+
+All Clouds with a currently-provisioned App which is selected in the dashboard filters are listed here. The name of the Cloud is listed along with its App count, the total memory, total storage, total CPU cores and price of the Apps provisioned in that Cloud are also listed.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..e2742ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 326,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..7c4d145
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,39 @@
+# Backups
+
+## Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+IMPORTANT
+
+Appliances with an HA architecture containing multiple app nodes must ensure all nodes can access stored backups. By default, if no “Default Backup Bucket” configuration is made, backups are stored in `/var/opt/morpheus/bitcan`. If this path is local to the app nodes, all other app nodes would not be able to reach the backups. In such a case, one solution would be to create an NFS share for the `bitcan` directory for all app nodes. Another solution would be to make a “Default Backup Bucket” configuration selection, which all nodes would then use for backup storage and retrieval.
+
+### HPE Morpheus Enterprise Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to HPE Morpheus Enterprise if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json b/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
new file mode 100644
index 0000000..2e31987
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+  "title": "Oracle Linux Virtualization Manager",
+  "ordinal": 464,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Linux Virtualization Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md b/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
new file mode 100644
index 0000000..d7d4238
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
@@ -0,0 +1,56 @@
+# Oracle Linux Virtualization Manager
+
+Oracle Linux Virtualization Manager (OLVM) allows administrators to manage and support a multi-host Oracle Linux KVM environment. HPE Morpheus Enterprise has developed and supports a plugin which allows an OLVM environment to be integrated and consumed as any other Cloud type within the HPE Morpheus Enterprise ecosystem. OLVM Clouds can be scoped to individual OLVM datacenters or scoped across all datacenters depending on configuration at the time of integration. Once integrated, HPE Morpheus Enterprise can automatically bring onboard OLVM resources including existing hosts, VMs (if desired), virtual images, networks and datastores.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Datacenter scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Adding an OLVM Cloud
+
+Adding OLVM Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the OLVM at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the OLVM plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), OLVM should be selectable as a Cloud type to add. Select it and click NEXT.
+
+At minimum, it’s required to configure the following to add the new Cloud:
+
+- **NAME:** A friendly name for the new OLVM Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx/ovirt-engine/api>)
+- **USERNAME:** Username for a OLVM service account, using an admin account will avoid any downstream permissions issues that could prevent features of the integration from working properly
+- **PASSWORD:** The password for the service account
+- **DATACENTER:** The Cloud may be scoped to a specific datacenter or to all datacenters
+
+You’ll know the API URL and credentials have been entered correctly when the DATACENTER dropdown becomes populated. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
+
+## Monitoring the OLVM Cloud
+
+After integrating the Cloud, click into the Cloud detail page to see high level details about the OLVM environment including computed costs, number and health of hosts, resource utilization, and the number of running workloads.
+
+![../../../_images/cloudDetail1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-096B3009-F0C1-4217-9152-D59226017104-high.png)
+
+Additional tabs on the detail page allow administrators to view a list of hosts (and click into a host detail page, if desired), view a list of running VMs (and click into a VM detail page, if desired), view and manage networks and datastores, view or add Docker clusters, and view any containers running on Docker hosts.
+
+## Provisioning to the OLVM Cloud
+
+There are multiple ways to consume the new OLVM Cloud as a provisioning target. Adding an OLVM Cloud to HPE Morpheus Enterprise adds the OLVM Instance Type to the provisioning wizard. From the Instance list page (Provisioning > Instances), click + ADD and select “OLVM.”
+
+![../../../_images/olvmInsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6CDB3D9E-AFDF-45DC-830C-0356DCF91ABA-high.png)
+
+HPE Morpheus Enterprise syncs in all available Virtual Images from OLVM and presents them along with Datacenter and Cluster selections. Select the proper resource sizing and image template to provision a new VM into OLVM.
+
+![../../../_images/configIns.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E0A6E761-BCFB-4307-8E0F-76A9548B7230-high.png)
+
+In addition to using the built-in OLVM Instance Type, adding the OLVM Cloud allows administrators to add OLVM-type Layouts to new or existing Instance Types. Add new Layouts in the HPE Morpheus Enterprise Library (Library > Blueprints > Layouts). When adding a new Layout, select “OLVM” from the Technology dropdown to make this Layout available when an OLVM Cloud has been selected as the provisioning target. See the Library section of HPE Morpheus Enterprise UI documentation for more details on building out Library items.
+
+![../../../_images/layoutTech.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A46EF9A1-9EC9-416E-BB80-3B516BF4BB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json b/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
new file mode 100644
index 0000000..4fcbc82
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+  "title": "Costing: Workload Costing",
+  "ordinal": 62,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Workload Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md b/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
new file mode 100644
index 0000000..76a9e06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
@@ -0,0 +1,26 @@
+# Costing: Workload Costing
+
+![../_images/5workloadcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-102FBE32-895E-4617-80D4-AA313E7BB572-high.png)
+
+The Workload Costing dashboard allows administrators to look at all or a subset of HPE Morpheus Enterprise-managed workloads to analyze their cost impact. Filters can be set to isolate a specific group of workloads and cost breakdowns are shown. Graphs are generated to reveal cost breakdowns of individual workloads or certain groups of workloads.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matched by search)
+- Group
+- Cloud
+- Tenant
+- Tag (Key). This is a required field and the top key in the list will be pre-selected by default
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all workloads that meet set filters:
+
+- **WORKLOADS:** The total number of workloads that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all workloads meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all workloads meeting dashboard filters
+- **TYPES:** The total number of workload types represented among workloads meeting set filters
+- **SIZES:** The total number of unique workload sizes represented among workloads meeting set filters
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json b/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
new file mode 100644
index 0000000..e3b0a69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+  "title": "Communication Data",
+  "ordinal": 51,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md b/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
new file mode 100644
index 0000000..3aa1028
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
@@ -0,0 +1,156 @@
+# Communication Data
+
+The following page contains communication information between the HPE Morpheus Enterprise appliance, integrated technologies, managed machines, and services.
+
+## Communication Frequency and Configurability
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency and Configurability
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Elastic Search Check | Server Pull | Elastic Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | 5 minutes | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Push | ServiceNow | Sync HPE Morpheus Enterprise library items to ServiceNow catalog | Nightly | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
+
+## Ports and Protocols
+
+The following table contains communication port and protocol data between HPE Morpheus Enterprise appliance tiers, managed machines, and services. All communication to and from HPE Morpheus Enterprise goes thru the application tier with exception of inter-cluster communications for each of the HPE Morpheus Enterprise tiers when using a distributed architecture.
+
+Ports used to communicate with integrated technologies are those defined for the integration’s API. They are not represented in this table as many of these are configurable and may be different in each customer environment. Additionally, ports used to complete Morpheus checks are customizable and may vary for each check configured. They are also not represented in this table.
+
+Table 2. Ports and Protocols
+
+       | Source | Destination | Port | Protocol | Description |
+| --- | --- | --- | --- | --- |
+| User | Application Tier | 443 | TCP | User Access |
+| Morpheus Servers | DNS Servers | 53 | TCP | Domain Name Resolution |
+| Morpheus Servers | Time Source | 123 | TCP | Time Resolution |
+| Morpheus Servers | Web or Offline Installer | 80, 443 | TCP | Download repos and Morpheus packages (yum/apt repos) |
+| Managed Machine | Application Tier | 443 | TCP | Morpheus Agent Communications |
+| Managed Machine | Application Tier | 80, 443 | TCP | Agent Installation. (Requires port 80 only for Ubuntu 14.04) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Clout‐init (Linux) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Cloudbase‐init (Windows) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation VMtools |
+| Managed Machine | Application Tier | N/A | N/A | Static IP Assignment & IP Pools (Cloud‐init or VMware Tools) |
+| Managed Machine | Docker Image Repo | 443 | TCP | Applicable if using docker |
+| Managed Machine | Application Tier | 69 | TCP/UDP | PXE Boot (Forwarded to internal PXE port 6969) |
+| Application Tier | Managed Machine | 5985 | TCP | Agent Installation WinRM (Windows) |
+| Application Tier | Managed Machine | 22 | TCP | Agent Installation SSH (Linux) |
+| Application Tier | Managed Machine | 22, 3389, 443 | TCP | Remote Console (SSH, RDP, Hypervisor Console |
+| Application Tier | AWS S3 | 443 | TCP | Morpheus Catalog Image Download |
+| Application Tier | Hypervisor | 443 | TCP | Hypervisor hostname resolvable by Morpheus Application Tier |
+| Application Tier | Non‐ Transactional Database Tier | 443 | TCP | Applicable if using Amazon Elasticsearch Service |
+| Application Tier | Docker CE Repo | 443 | TCP | Applicable only when integrated with Docker |
+| Application Tier | Rubygems | 443 | TCP |  |
+| Application Tier | Morpheus Hub | 443 | TCP | (Optional) Telemetry data (Disabled only via license feature) |
+| Application Tier | Mail Server | 25 or 465 | SMTP | Send email from Morpheus |
+| Application Tier | postmarkapp | 2525 | TCP | Send email from Morpheus (such as alerts and password reset requests) when custom SMTP settings aren’t present |
+| Application Tier | Messaging Tier | 5672 | TCP | AMQP non‐TLS connections |
+| Application Tier | Messaging Tier | 5671 | TCP | AMQPS TLS enabled connections |
+| Application Tier | Messaging Tier | 61613 | TCP | STOMP Plugin connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Application Tier | Messaging Tier | 61614 | TCP | STOMP Plugin TLS enabled connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Messaging Tier | Messaging Tier | 25672 | TCP | Inter‐node and CLI tool communication |
+| Administrator Web Browser | RabbitMQ Server Management | 15672 | TCP | Management plugin |
+| Administrator Web Browser | RabbitMQ Server Management | 15671 | TCP | Management plugin SSL |
+| Messaging Tier Cluster Node | Messaging Tier Cluster Node | 4369 | TCP | erlang (epmd) peer discovery service used by RabbitMQ nodes and CLI tools |
+| Application Tier | Non‐Transactional Database Tier | 9200 | TCP | Elasticsearch requests (Used in all cases except when utilizing AWS ES service) |
+| Application Tier | Non‐Transactional Database Tier | 443 | TCP | Elasticsearch requests (Used in all cases where ES is consumed as a PaaS service) |
+| Non‐Transactional Database Tier | Non‐Transactional Database Tier | 9300 | TCP | Elasticsearch Cluster |
+| Transactional Database Tier | Transactional Database Tier | 4567 | TCP/UDP | Write‐set replication traffic (over TCP) and multicast replication (over TCP and UDP). |
+| Transactional Database Tier | Transactional Database Tier | 4568 | TCP | Incremental State Transfer (IST) |
+| Application Tier | Transactional Database Tier | 3306 | TCP | MySQL client connections |
+| Backup Solution | Transactional Database Tier | 4444 | TCP | State Snapshot Transfer (SST) |
+| Application Tier | Integrated Technology | Varies | TCP | Integrations (Uses the port of the 3rd party systems API) |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json b/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
new file mode 100644
index 0000000..5d23be8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+  "title": "Offline Installations and Upgrades",
+  "ordinal": 32,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html",
+  "topic_cluster": {
+    "clustering_title": "Offline Installations and Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md b/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
new file mode 100644
index 0000000..2af4ba1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
@@ -0,0 +1,104 @@
+# Offline Installations and Upgrades
+
+For customers that have an appliance behind a firewall/proxy that does not allow downloads from our Amazon download site, you can add the supplemental package to add the needed packages the standard Morpheus installer would have downloaded.
+
+## Offline Installation Requirements
+
+- NTP should be correctly configured and the server is able to connect to the NTP server in the ntp.conf file
+- The OS package repositories should be configured to use local LAN repository servers or the server should be able to receive packages from the configured repositories
+- The standard Morpheus and supplemental packages must be downloaded from another system and transferred to the Morpheus Appliance server
+- The supplemental package is additive, the full installer is also required
+
+NOTE
+
+The supplemental package is linked 1-to-1 to the appliance release. For example the supplemental package for 4.2.1-1 should be used with the appliance package 4.2.1-1
+
+## Offline Install
+
+## Ubuntu/Debian
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the Supplemental packages on to the appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_version_amd64.deb  
+   wget http://example_url/morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_version_amd64.deb  
+   sudo dpkg -i morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   # edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus log file located at /var/log/morpheus/morpheus-ui/current with the command `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
+
+## CentOS/RHEL
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the matching Supplemental package on to the Appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_package_url.noarch.rpm  
+   wget http://example_url/morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo rpm -i morpheus-appliance_package_url.noarch.rpm  
+   sudo rpm -i morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   #Edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus-ui log file with `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json b/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
new file mode 100644
index 0000000..1ba0a5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+  "title": "Default Unmanaged Network Support",
+  "ordinal": 403,
+  "parent_title": "Creating an HPE BMaaS Cloud",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html",
+  "topic_cluster": {
+    "clustering_title": "Default Unmanaged Network Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md b/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
new file mode 100644
index 0000000..a6cd968
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
@@ -0,0 +1,15 @@
+# Default Unmanaged Network Support
+
+HPE Morpheus Enterprise 8.0.13 and later automatically create a default unmanaged network during the **Bare Metal Cloud** creation process.
+
+When you select Unmanaged Network as the network mode, HPE Morpheus performs the following actions:
+
+- Creates a default unmanaged network automatically.
+- Configures the network to use DHCP for IP allocation.
+- Enables immediate selection of the network during instance provisioning.
+
+The below image shows the default unmanaged network automatically created during Bare-Metal cloud creation.   
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9CB5E90B-9DED-4601-84AD-CA4E4538E297-high.png)
+
+The below image shows an untagged VLAN configuration with DHCP selected as the IP allocation method.   
+![Edit Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C186BB86-0721-493C-B4ED-10864ABF69F3-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..578c269
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 231,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..b4dc4e1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,462 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
+
+## Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+
+## Alibaba Buckets
+
+### About this task
+
+To Add an Alibaba Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Amazon S3 Buckets
+
+### About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Google Cloud Storage Buckets
+
+### About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in HPE Morpheus Enterprise
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in HPE Morpheus Enterprise
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of HPE Morpheus Enterprise
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by HPE Morpheus Enterprise. When selecting ‘Backup Old Files’, HPE Morpheus Enterprise will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, HPE Morpheus Enterprise will delete any files that reach a certain number of days old
+
+## Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Openstack Swift Buckets
+
+### About this task
+
+To Add an Azure Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Rackspace CDN Buckets
+
+### About this task
+
+To Add a Rackspace CDN Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json b/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
new file mode 100644
index 0000000..8916a91
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+  "title": "IPv6",
+  "ordinal": 38,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html",
+  "topic_cluster": {
+    "clustering_title": "IPv6",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md b/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
new file mode 100644
index 0000000..0f69d4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
@@ -0,0 +1,43 @@
+# IPv6
+
+## Overview
+
+There may be situations where instances only have IPv6 routing available. HPE Morpheus Enterprise fully supports IPv6 for the appliance and agent comms.
+
+To enable IPv6 listener on the HPE Morpheus Enterprise appliance, you must modify the NGINX listeners.
+
+## Configuring NGINX Listeners
+
+### Procedure
+
+1. Confirm IPv6 is enabled and IP address is applied within the Morpheus underlying OS.
+2. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:80;
+   ```
+   ```
+3. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus-ssl.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:443 ssl;
+   ```
+   ```
+4. Restart the NGINX service: 
+
+   ```
+   ```
+   morpheus-ctl restart nginx  
+   ok: run: nginx: (pid 47868) 0s
+   ```
+   ```
+5. The site should now be resolvable via IPv6. To test you should be able to do the following: 
+
+   ```
+   ```
+   curl -k -6 https://[<IPv6 Address>]/ping  
+   MORPHEUS PING
+   ```
+   ```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json b/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
new file mode 100644
index 0000000..134d216
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+  "title": "Kubernetes Clusters",
+  "ordinal": 198,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md b/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
new file mode 100644
index 0000000..d4211c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
@@ -0,0 +1,363 @@
+# Kubernetes Clusters
+
+## Requirements
+
+- Agent installation is required for Master and Worker Nodes. Refer to [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html) section for additional information.
+- Access to Cloud Front, Image copy access and permissions for System and Uploaded Images used in Cluster Layouts
+  :   Image(s) used in Cluster Layouts must either exist in destination cloud/resource or be able to be copied to destination by Morpheus, typically applicable for non-public clouds. For the initial provision, Morpheus System Images are streamed from Cloud Front through Morpheus to target destination. Subsequent provisions clone the local Image.
+- System Kubernetes Layouts require Master and Worker nodes to access to the following over 443 during K8s install and configuration:
+
+  - Morpheus Appliance url (443)
+  - <https://packages.cloud.google.com>
+  - <https://storage.googleapis.com>
+  - <https://docs.projectcalico.org>
+  - <https://openebs.github.io>
+  - <https://cloud.weave.works>
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
+
+## Creating Kubernetes Clusters
+
+### About this task
+
+Provisions a new Kubernetes Cluster in selected target Cloud using selected Layout.
+
+NOTE
+
+When deploying a highly-available Kubernetes cluster, it’s important to note that HPE Morpheus Enterprise does not currently auto-deploy a load balancer. Additionally, when HPE Morpheus Enterprise runs the `kubeadm init` command in the background during cluster provisioning, it also sets the `--control-plane-endpoint` flag to the first control plane node. This is a hard-coded behavior. To accomplish a highly-available cluster, users may wish to update the configured control plane endpoint, such as to a DNS name pointing to a load balancer. We are currently investigating updates to the product that would allow the user to specify such a DNS name prior to kicking off cluster provisioning. Additionally, users can circumvent this issue by configuring and deploying their own custom Cluster Layouts.
+
+HPE Morpheus Enterprise maintains a number of default Kubernetes Cluster Layouts which are updated frequently to offer support for current versions. AKS & GKE Kubernetes versions will dynamically update to the providers supported versions. HPE Morpheus Enterprise also supports creation of custom Kubernetes Cluster Layouts, a process which is described in detail in a later section.
+
+To create a new Kubernetes Cluster:
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Kubernetes Cluster`
+4. Select a Group for the Cluster
+5. Select NEXT
+6. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Kubernetes Cluster
+
+   RESOURCE NAME
+   :   Name for Kubernetes Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+7. Select NEXT
+8. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   LAYOUT
+   :   Select from available layouts. System provided layouts include Single Master and Cluster Layouts.
+
+   PLAN
+   :   Select plan for Kubernetes Master
+
+   VOLUMES
+   :   Configure volumes for Kubernetes Master
+
+   NETWORKS
+   :   Select the network for Kubernetes Master & Worker VM’s
+
+   CUSTOM CONFIG
+   :   Add custom Kubernetes annotations and config hash
+
+   CLUSTER HOSTNAME
+   :   Cluster address Hostname (cluster layouts only)
+
+   POD CIDR
+   :   POD network range in CIDR format ie 192.168.0.0/24 (cluster layouts only)
+
+   WORKER PLAN
+   :   Plan for Worker Nodes (cluster layouts only)
+
+   NUMBER OF WORKERS
+   :   Specify the number of workers to provision
+
+   LOAD BALANCER
+   :   Select an available Load Balancer (cluster layouts only) }
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain override for DNS records
+
+       HOSTNAME
+       :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+
+   Autoscaler
+   :   The Cluster Autoscaler is a Kubernetes component that automatically adjusts the number of worker nodes in your cluster based on the resource requirements of your workloads. When application demand increases and existing nodes are unable to schedule new pods, the autoscaler adds additional nodes to the cluster. Conversely, when demand drops and nodes become underutilized, the autoscaler removes unnecessary nodes, helping to optimize resource usage and control costs.
+   :   NOTE
+
+       During scale down, the Cluster Autoscaler will skip nodes that have workloads which cannot be safely evicted, such as pods with persistent or local storage (e.g., Rook Ceph), or pods that are constrained by affinity or anti-affinity rules.
+   :   |  |  |
+       | --- | --- |
+       | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+       | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+       | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+9. Select NEXT
+10. Select optional Workflow to execute
+11. Select NEXT
+12. Review and select COMPLETE 
+
+    - The Master Node(s) will provision first.
+    - Upon successful completion of VM provision, Kubernetes scripts will be executed to install and configure Kubernetes on the Masters.
+      :   NOTE
+
+          Access to the sites listed in the [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892) section is required from Master and Worker nodes over 443
+    - After Master or Masters are successfully provisioned and Kubernetes is successfully installed and configured, the Worker Nodes will provision in parallel.
+    - Provision status can be viewed:
+      :   - From the Status next to the Cluster in Infrastructure  >  Clusters
+          - Status bar with eta and current step available on Cluster detail page, accessible by selecting the Cluster name from Infrastructure  >  Clusters
+    - All process status and history is available - From the Cluster detail page History tab, accessible by selecting the Cluster name from Infrastructure  >  Clusters and the History tab - From Operations - Activity - History - Individual process output available by clicking i on target process
+13. Once all Master and Worker Nodes are successfully provisioned and Kubernetes is installed and configured, the Cluster status will turn green. 
+
+    IMPORTANT
+
+    Cluster provisioning requires successful creation of VMs, Agent Installation, and execution of Kubernetes workflows. Consult process output from ``Infrastructure  >  Clusters - Details and morpheus-ui current logs at `Administration - Health - Morpheus Logs` for information on failed Clusters.
+
+### Intra-Kubernetes Cluster Port Requirements
+
+The table below includes port requirements for the machines within the cluster (not for the HPE Morpheus Enterprise appliance itself). Check that the following ports are open on Control-plane and Worker nodes:
+
+Table 1. Control‐plane node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 6443 | Kubernetes API Server | All |
+| TCP | Inbound | 6783 | Weaveworks |  |
+| TCP | Inbound | 2379‐2380 | etcd server client API | kube‐apiserver, etcd |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 10251 | kube‐scheduler | Self |
+| TCP | Inbound | 10252 | kube‐controller‐manager | Self |
+
+Table 2. Worker node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 30000‐32767 | NodePort Services | All |
+
+## Adding Worker Nodes
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `ADD (type) Kubernetes Worker` 
+
+   NAME
+   :   Name of the Worker Node. Auto=populated with `${cluster.resourceName}-worker-${seq}`
+
+   DESCRIPTION
+   :   Description of the Worker Node, displayed in Worker tab on Cluster Detail pages, and on Worker Host Detail page
+
+   CLOUD
+   :   Target Cloud for the Worker Node.
+4. Select NEXT
+5. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   SERVICE PLAN
+   :   Service Plan for the new Worker Node
+
+   NETWORK
+   :   Configure network options for the Worker node.
+
+   HOST
+   :   If Host selection is enabled, optionally specify target host for new Worker node
+
+   FOLDER
+   :   Optionally specify target folder for new Worker node
+       :   Advanced Options
+           :   DOMAIN
+               :   Specify Domain override for DNS records
+
+               HOSTNAME
+               :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+6. Select NEXT
+7. Select optional Workflow to execute
+8. Select NEXT
+9. Review and select COMPLETE
+
+### Results
+
+NOTE
+
+Ensure there is a default StorageClass available when using a Morpheus Kubernetes cluster with OpenEBS so that Kubernetes specs or HELM templates that use a default StorageClass for Persistent Volume Claims can be utilised.
+
+## Configure Autoscaler
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `Configure Autoscaler`
+4. |  |  |
+   | --- | --- |
+   | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+   | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+   | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+5. Select `Apply`
+
+## Kubernetes Cluster Detail Pages
+
+The Kubernetes Cluster Detail page provides a high degree of monitoring and control over Kubernetes Clusters. This includes monitoring of all nodes in the Cluster, `kubectl` command line, account and role control, workload management, and more. The upper section of the page (which is persistent regardless of the currently-selected tab) provides high level costing and monitoring information, including a current aggregate metric for the CPU, memory and storage use.
+
+![../../_images/clusterDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-824D0DA3-5400-4EF0-BE66-A96F64902C89-high.png)
+
+The upper section also includes the ACTIONS menu which includes the following functions:
+
+- **REFRESH:** Forces a routine sync of the cluster status
+- **PERMISSIONS:** View and edit the Group, Service Plan, and Tenant access permissions for the cluster
+- **VIEW API TOKEN:** Displays the API token for the cluster
+- **VIEW KUBE CONFIG:** Displays the cluster configuration
+- **RUN WORKLOAD:** Run deployments, stateful sets, daemon sets, or jobs and target them to a specific namespace
+- **UPGRADE CLUSTER:** Upgrade the cluster to a higher version of Kubernetes
+
+  IMPORTANT
+
+  Kubelet configuration cleanup is required to upgrade clusters. The `--pod-infra-container-image` flag is deprecated from Kubernetes version 1.35.3. Upgrading clusters to v1.35.3 or later will fail if this deprecated flag is present in the Kubelet configuration. This flag must be manually removed from all nodes prior to initiating the upgrade process. See upgrade process below:
+  1. Edit the kubelet environment configuration file with `sudo vim /var/lib/kubelet/kubeadm-flags.env`
+  2. Locate the `KUBELET_KUBEADM_ARG`S entry and remove the following entry: `--pod-infra-container-image=registry.k8s.io/pause:3.10`
+  3. Save the file and exit the editor
+  4. Reload the configuration and restart the service with `sudo systemctl daemon-reload` and `sudo systemctl restart kubelet`
+  5. This process is repeated for all cluster nodes
+- **ADD KUBERNETES WORKER:** Launches a wizard which allows users to configure a new worker for the cluster
+
+Additional monitoring and control panes are located within tabs, some of which contain subtabs.
+
+- [Summary](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22330E1_D22331E1_D22332E1_D22333E1_D22334E1_D22335E1)
+- [Control](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22340E1_D22341E1_D22342E1_D22343E1_D22344E1_D22345E1)
+- [Access](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22350E1_D22351E1_D22352E1_D22353E1_D22354E1_D22355E1)
+- [Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22360E1_D22361E1_D22362E1_D22363E1_D22364E1_D22365E1)
+- [Workloads](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22370E1_D22371E1_D22372E1_D22373E1_D22374E1_D22375E1)
+- [Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22380E1_D22381E1_D22382E1_D22383E1_D22384E1_D22385E1)
+- [Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22390E1_D22391E1_D22392E1_D22393E1_D22394E1_D22395E1)
+- [Containers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22400E1_D22401E1_D22402E1_D22403E1_D22404E1_D22405E1)
+- [Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22410E1_D22411E1_D22412E1_D22413E1_D22414E1_D22415E1)
+- [History](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22420E1_D22421E1_D22422E1_D22423E1_D22424E1_D22425E1)
+- [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22430E1_D22431E1_D22432E1_D22433E1_D22434E1_D22435E1)
+
+### Summary
+
+The summary tab contains high-level details on health and makeup of the cluster. ![../../_images/clusterSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-42D2FAC8-D054-4AEC-8D10-59C6B15EE02A-high.png)
+
+### Control
+
+Contains the `kubectl` command line with ability to target commands to specific namespaces. The Control tab also contains the Packages subtab which displays the list of packages and their versions. ![../../_images/clusterControl.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-88388DAC-D1A7-4218-B17A-D605AB1D9095-high.png)
+
+### Access
+
+The Access Tab contains view and edit tools for Namespaces, accounts, roles, and role bindings. ![../../_images/clusterAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BC2EC859-76DA-4EC4-883C-DBA8BAD9DD52-high.png)
+
+### Nodes
+
+The nodes tab includes a list of master and worker nodes in the cluster, their statuses, and the current compute, memory, and storage pressure on each node. ![../../_images/clusterNodes.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-88E093F0-4EAB-4E6D-A023-F1C70F06812A-high.png)
+
+### Workloads
+
+View and edit existing Pods, Deployments, Replica Sets, Daemon Sets, Stateful Sets, and Jobs. Add new Deployments, Stateful Sets, Daemon Sets, and Jobs through the ACTIONS menu near the top of the Cluster Detail Page. ![../../_images/clusterWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5AA1E4AA-4AD5-4A7F-A274-2D7C01357494-high.png)
+
+### Network
+
+View, add, and edit Services, Endpoints, Ingress and Network Policies ![../../_images/clusterNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A94FC46E-8856-411E-8E6A-F2B6DBEAB45F-high.png)
+
+### Storage
+
+View, add, and edit Storage classes, Volume claims, Volumes, Config maps, and Secrets ![../../_images/clusterStorage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2A352500-C7FF-43CD-B91B-AD299208090B-high.png)
+
+### Containers
+
+View a list of containers running on the cluster and restart or delete them if needed. This list can be filtered by Namespace or a specific Worker if desired. ![../../_images/clusterContainers.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8D0ABC87-4D4D-4A4B-91A3-214698B516DD-high.png)
+
+### Monitoring
+
+View logs and events with filtering tools and search functionality available. ![../../_images/clusterMonitoring.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-02EEA1D6-F4BE-4060-AEBB-B6A2BD715EF6-high.png)
+
+### History
+
+View the Cluster lifecycle history. This includes lists of automation packages (Tasks and Workflows) run against the cluster or its nodes, the success of these scripts and the output. ![../../_images/clusterHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-394CC8A6-5257-4B4C-BF41-E10643BEEE8A-high.png)
+
+### Wiki
+
+View the HPE Morpheus Enterprise Wiki entry for this Cluster. This Wiki page may also be viewed in the Wiki section (Operations > Wiki). Edit the Wiki as desired, most standard Markdown syntax will be honored allowing the use of headings, links, embedded images, and more. ![../../_images/clusterWiki.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BAD395AC-5FAD-495D-B797-EEDA93C17B73-high.png)
+
+## Adding External Kubernetes Clusters
+
+HPE Morpheus Enterprise supports the management and consumption of Kubernetes clusters provisioned outside of HPE Morpheus Enterprise. These are referred to as External Kubernetes Clusters in HPE Morpheus Enterprise UI. This could be used, for example, to onboard and manage OpenShift clusters. In order to fully integrate the Kubernetes cluster with the HPE Morpheus Enterprise feature set, you may need to create a service account for HPE Morpheus Enterprise. Without first taking that step, some features may not work fully, such as listing all namespaces. The process for creating a service account and integrating the Cluster with HPE Morpheus Enterprise is described here.
+
+First, create the Service Account within the Kubernetes cluster:
+
+```
+```
+kubectl create serviceaccount morpheus
+```
+```
+
+Next, create the Role Binding:
+
+```
+```
+kubectl create clusterrolebinding morpheus-admin \  
+--clusterrole=cluster-admin --serviceaccount=default:morpheus \  
+--namespace=default
+```
+```
+
+With those items created, we can gather the API URL and the API token which will be used to add the existing cluster to HPE Morpheus Enterprise in the next step:
+
+```
+```
+kubectl config view --minify | grep server | cut -f 2- -d ":" | tr -d " "
+```
+```
+
+```
+```
+SECRET_NAME=$(kubectl get secrets | grep ^morpheus | cut -f1 -d ' ')  
+kubectl describe secret $SECRET_NAME | grep -E '^token' | cut -f2 -d':' | tr -d " "
+```
+```
+
+After finishing those steps, we can now create the external cluster in HPE Morpheus Enterprise. Navigate to Infrastructure > Clusters. Click + ADD CLUSTER and then select “External Kubernetes Cluster”. Set the following fields, you will have to advance through the pages of the wizard to see all fields indicated:
+
+- **GROUP:** A previously created HPE Morpheus Enterprise Group
+- **CLOUD:** A previously-integrated Cloud
+- **CLUSTER NAME:** A friendly name for the onboarded cluster in HPE Morpheus Enterprise UI
+- **RESOURCE NAME:** The resource name will be pre-pended to Kubernetes hosts associated with this cluster when shown in HPE Morpheus Enterprise UI
+- **LAYOUT:** Set an associated Layout
+- **API URL:** Enter the API URL gathered in the previous step
+- **API TOKEN:** Enter the API Token gathered in the previous step
+- **KUBE CONFIG:** Enter Kubeconfig YAML to authenticate the cluster
+
+The above are the required fields, others may be optionally configured depending on the situation. Complete the wizard and HPE Morpheus Enterprise will begin the process of onboarding the existing cluster into management within HPE Morpheus Enterprise UI. Once things are finalized and statuses are green, the cluster can be monitored and consumed as any other cluster provisioned from HPE Morpheus Enterprise.
+
+![../../_images/extKube.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E72E1043-FF51-4388-9D80-79CC7660C86A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json b/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
new file mode 100644
index 0000000..41a50b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+  "title": "Tenant Roles",
+  "ordinal": 305,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md b/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
new file mode 100644
index 0000000..b2d57b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
@@ -0,0 +1,8 @@
+# Tenant Roles
+
+A Tenant Role sets the highest possible permissions for a Tenant. User Roles within that Tenant cannot exceed those of the Tenants assigned Tenant Role. Tenant Roles can be assigned to single or multiple Tenants, and do not apply to the Master Account.
+
+**Subtopics**  
+
+- **[To create a Tenant Role:](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html)**
+- **[Setting an Optional Landing URL](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json b/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
new file mode 100644
index 0000000..dc80254
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+  "title": "Nutanix Prism Element",
+  "ordinal": 463,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Element",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md b/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
new file mode 100644
index 0000000..2598995
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
@@ -0,0 +1,188 @@
+# Nutanix Prism Element
+
+## Overview
+
+Nutanix Prism Element simplifies datacenter infrastructure by integrating server and storage resources allowing applications to run at scale. HPE Morpheus Enterprise enhances Nutanix resources by allowing efficient and seamless deployment of virtualized or containerized applications, management of existing brownfield resources in Nutanix Clouds, pricing and cost tracking, and monitoring of running workloads.
+
+## Features
+
+- Virtual machine provisioning
+- Brownfield discovery
+- Containers
+- Backups / Snapshots
+- Datastores
+- Kubernetes
+- Resources Groups
+- Migrations
+- HPE Morpheus Enterprise costing and pricing
+- Auto Scaling
+- Load Balancing
+- Remote Console for hypervisor hosts and running workloads
+- Two-way Cloud sync
+- Lifecycle Management and Resize
+
+NOTE
+
+Prism Central is currently supported and is maintained as a separate, plugin-based Cloud integration. See the [Prism Central plugin page](https://share.morpheusdata.com/plugin/morpheus-nutanix-prism/about) on the HPE Morpheus Enterprise plugin share site for additional details and access to the plugin. There is also an [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/prismCentral/prismCentral.html) for that plugin here in HPE Morpheus Enterprise UI documentation.
+
+## Getting Started
+
+To get started, first confirm that a few prerequisite steps have been completed. The Nutanix cluster should be provisioned and available on the network. In a typical configuration, Nutanix will be available at the `https://fqdn:9440` URL. Have the credentials for an administrator service account available to integrate HPE Morpheus Enterprise with the Nutanix cluster. With those prerequisites already completed, you’re ready to add a Nutanix Cloud to HPE Morpheus Enterprise using the instructions in the next section.
+
+## Adding a Nutanix Cloud
+
+To start, navigate to the Cloud list page (Infrastructure > Clouds) and click + ADD. On the ADD CLOUD modal, you will at least need to provide a NAME for the Cloud in HPE Morpheus Enterprise along with the API URL and credentials. Other fields listed here are optional but may be needed for the Cloud to perform as desired in your environment.
+
+- **NAME:** A name for the Nutanix Cloud within HPE Morpheus Enterprise
+- **CODE:** A unique code for the cloud which is used in HPE Morpheus Enterprise API, CLI, and in automation scripts
+- **LABELS:** Select or create a new Label to apply to the Cloud. See [Labels documentation](https://docs.morpheusdata.com/en/latest/library/labels.html) for a complete description of the usefulness of Labels
+- **LOCATION:** An optional description field for the Cloud to hold location information
+- **VISIBILITY:** For multitenant environments, sets the visibility level for Tenants outside of the one the Cloud resources are assigned to
+- **TENANT:** If the visibility is set to private, this sets the Tenant the Cloud resources are assigned to
+- **ENABLED:** When checked, HPE Morpheus Enterprise will perform regular syncs with this Cloud and the Cloud will also be selectable as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** Indicates whether HPE Morpheus Enterprise should control the power state for provisioned VMs (not brownfield discovered VMs). If VMs are powered off for an unknown reason (that is, outside of HPE Morpheus Enterprise) they will be powered back on. Leave unchecked if you wish to manage workload power state outside of HPE Morpheus Enterprise
+- **API URL:** The URL for the Nutanix Prism API, typically in a format like `https://xx.xx.xx.xx:9440`
+- **CREDENTIALS:** Choose a pre-stored username/password credential set or enter a username/password set. If entering the credentials locally, you may also choose to securely store the credentials for later use. Depending on selection, additional fields will be added to facilitate that choice
+- **API VERSION:** Select the API version supported by your Nutanix environment to ensure HPE Morpheus Enterprise is not targeting endpoints which are incompatible with your environment
+- **INVENTORY EXISTING INSTANCES:** When checked, HPE Morpheus Enterprise will automatically onboard workloads which are already running in the Nutanix environment but which were provisioned outside of HPE Morpheus Enterprise. These may be brought under HPE Morpheus Enterprise management at a later time, if desired
+- **ENABLE HYPERVISOR CONSOLE:** When checked, enables remote console support directly to the hypervisor
+
+In addition to these basic settings, there are also some advanced options. These are similar but not identical for every Cloud type and some of them may not appear for Nutanix Clouds.
+
+### Advanced Cloud Options
+
+**Advanced Options**
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+**CUSTOM LOGOS**
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+**INVENTORY OPTIONS**
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+**Provisioning Command**
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+With the above configurations made, click NEXT. Choose to add the Cloud to an existing Group or to create a new Group and click NEXT once again. Finally, review the details of the new Cloud on the REVIEW tab and click COMPLETE if all looks good. At this point the new Cloud will be added to HPE Morpheus Enterprise and the initial Cloud sync will begin. On the Cloud list page (Infrastructure > Clouds), we will see the Cloud in an “OK” status once it is ready to be consumed in HPE Morpheus Enterprise as a provisioning target. Click into the Cloud detail page by clicking on the NAME of the Cloud from the list. Continue on to the next section for an overview of the details available on the Cloud detail.
+
+## Monitoring Nutanix Clouds
+
+On clicking into the Nutanix Cloud, you’ll land on the Summary tab. Here we can see high-level details including cost metrics for the month, general resource utilization information, and information on the number of hosts, workloads, and more that are currently running within the Cloud scope.
+
+![../../../_images/cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1E122ED6-DF89-43B3-AB53-F645F37F8371-high.png)
+
+You’ll also notice the Clusters tab. Here you can see and click into any Docker or Kubernetes Clusters which are running on the Nutanix Cloud. HPE Morpheus Enterprise will see these clusters as provisioning targets themselves for containerized applications (as opposed to the Cloud itself for virtualized applications). You can also add new Kubernetes or Dockers clusters from this tab. HPE Morpheus Enterprise includes built-in Cluster Layouts but custom Cluster Layouts can also be created. There is a guide on creating your own custom Kubernetes Cluster Layouts in the Clusters section of HPE Morpheus Enterprise UI documentation.
+
+On the Hosts tab, you’ll see all Nutanix hypervisior hosts which are associated with the cluster. Host health metrics are viewable and we can click into individual hosts to see even greater detail on the individual host detail pages.
+
+The VM and Containers tabs show all current VM and container workloads across the cluster. When integrating the Cloud, if you opted to inventory existing workloads, discovered resources will appear here. If not (or if there simply are none), only HPE Morpheus Enterprise-provisioned workloads will appear here.
+
+## Provisioning New Workloads
+
+With the Cloud integrated, you’re already to provision new workloads. HPE Morpheus Enterprise comes pre-installed with a number of default library items designed to work with each supported Cloud integration type, including Nutanix. While this guide will not go through the process of using the provisioning wizard (see Provisioning > Instances page to start), you could provision a default workload to test functionality now if desired. Additionally, HPE Morpheus Enterprise will sync Virtual Images from Nutanix Clouds (Library > Virtual Images) and custom Library items may be built from these images. See the Library section of HPE Morpheus Enterprise documentation for more information on piecing together Instance Types, images, and automation scripts into cohesive and easily-consumed Library items.
+
+## Service Plans
+
+HPE Morpheus Enterprise includes a default set of Service Plans. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, and CPU cores. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Nutanix or create a new one. These all can be easily managed from the Administration > Plans & Pricing section.
+
+## Docker
+
+So far, this document has covered how to add the Nutanix cloud integration and has enabled users the ability to provision virtual machine-based Instances. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this, a Docker Host must first be provisioned into Nutanix (multiple are needed when dealing with horizontal scaling scenarios). As mentioned previously, these can be viewed or created from the Clusters tab of the Cloud detail page.
+
+To provision a Docker Host, simply navigate to the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a Nutanix Docker Host. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top. Just like with VMs, HPE Morpheus Enterprise includes default containerized items out of the box so provisioning to Docker hosts can be tested even before you’ve created your own container-based Library items.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, then the Agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a Nutanix Instance. From the Instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the Instance detail page. Snapshots taken outside HPE Morpheus Enterprise will be synced every five minutes (by default). To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json b/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
new file mode 100644
index 0000000..b3cbac3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+  "title": "Load Balancer Configuration",
+  "ordinal": 31,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancer Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md b/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
new file mode 100644
index 0000000..4374b2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
@@ -0,0 +1,561 @@
+# Load Balancer Configuration
+
+For configurations with 2 or more Applications Nodes, a load balancer is recommended to ensure high availability (HA) from disruptions and upgrades. Below are the guidelines to configuring a load balancer for HPE Morpheus Enterprise but each configuration may differ based on the organization’s requirements.
+
+## Requirements
+
+- WebSockets enabled
+- Load Balance 443 (optionally redirect 80 to 443)
+
+  - SSL Termination (Offload), Bridging, and Passthrough are supported
+- Round-Robin or least connection distribution
+- HTTPS monitor `https://ip_address/ping` body for `MORPHEUS PING` or status of 200, for node operational health
+
+## Example configurations
+
+Below are a few examples of configuring load balancers to meet the needs of a HA configuration. The examples assume SSL bridging will be used, which means an SSL (TLS) certificate is presented by the load balancer to clients and the load balancer will communicate with the backend nodes via a different (possibly same) certificate. This configuration is recommended because the HPE Morpheus Enterprise application nodes will create self-signed certificates and the load balancer will present a valid certificate to end users. Additionally, all communication will be encrypted. This reduces the overhead of maintaining the certificates on the HPE Morpheus Enterprise application nodes, as the load balancer can ignore invaild certs on the application nodes. However, the certificates on the HPE Morpheus Enterprise application nodes are not required to be self-signed, they can be replaced with other trusted certificates following the [SSL Certificates](https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html) documentation.
+
+TIP
+
+The list below is not meant to be a complete list for all load balancers. The provided examples are common deployments that can be used for reference. The settings mentioned in the examples list the primary settings that may need to be configured, other settings are based on the organization’s needs requirements and own configuration.
+
+### F5 BIG-IP
+
+**Monitor**
+
+- **Type:** HTTPS
+- **Send String:** GET /ping
+- **Receive String:** MORPHEUS PING
+
+**Pool**
+
+- **Health Monitor:** Select monitor created in the **Monitor** section
+- **Load Balancing Method:** Least Connections (member) is recommended (alternatively Round Robin)
+- **Node Service Port:** 443/HTTPS
+
+**Virtual Server**
+
+- **Type:** Standard
+- **Service Port:** 443/HTTPS
+- **Protocol:** TCP
+- **Protocol Profile (Client):** tcp
+- **Protocol Profile (Server):** tcp
+- **HTTP Profile (Client):** http
+- **HTTP Profile (Server):** http
+- **SSL Profile (Client):** clientssl (or preferred profile with a trusted certificate)
+- **SSL Profile (Server):** serverssl
+- **Source Address Translation:** Auto Map
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### AWS Application Load Balancer (ALB)
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### HAProxy
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### Azure Application Gateway
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json b/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
new file mode 100644
index 0000000..acb19d3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+  "title": "Veeam",
+  "ordinal": 384,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.html",
+  "topic_cluster": {
+    "clustering_title": "Veeam",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md b/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
new file mode 100644
index 0000000..d80968e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
@@ -0,0 +1,102 @@
+# Veeam
+
+Veeam is a backup and replication platform designed to work with popular on-prem cloud providers, including VMware, Microsoft Hyper-V, and vCloud Director. HPE Morpheus Enterprise integrates with your existing Veeam appliance which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Veeam with HPE Morpheus Enterprise, sharing a Veeam integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from Veeam backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Veeam integration as the default backup target for compatible clouds
+- Select Veeam integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Veeam Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Integrations
+2. Select + ADD
+3. Select Veeam
+4. Fill in the following: 
+
+   Name
+   :   Friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, this integration will be active and available for use
+
+   API URL
+   :   IP or Hostname of the Veeam Enterprise Manager, must be HTTPS for VEEAM 10
+
+   Port
+   :   Port number configured to access the Veeam server, must be 9398 for VEEAM 10
+
+   Username
+   :   Username for an admin service account in Veeam
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise)
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that added the integration
+
+           Public
+           :   Available to Subtenants (primary tenant option only)
+5. Click SAVE
+
+### Results
+
+NOTE
+
+Veeam Backup Enterprise Manager must be installed in order to successfully integrate HPE Morpheus Enterprise with Veeam.
+
+IMPORTANT
+
+Once Veeam service has been integrated with HPE Morpheus Enterprise, Veeam server(s) will be available to select as the backup provider for VMware, Hyper-V, and vCloud Director cloud integrations (Infrastructure > Clouds > Edit a compatible Cloud). To enable Veeam backups, select the appropriate Veeam server as the “backup provider” for your cloud integrations as needed. Failure to do so will result in blank `Backup Repositories` and `Backup Job Templates` options when configuring Veeam Backups during provisioning.
+
+## Set Veeam as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Veeam integrations are supported as backup target for VMware, Hyper-V, and vCloud Director Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware, Hyper-V, or vCD Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Veeam integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-96E45BAD-D2AD-43F9-AE73-7AF6E41035F2-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Veeam is set as the backup provider, Veeam will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Veeam backup type
+- **Repository:** Select a repository synced from the Veeam backup provider associated with the Cloud
+- **Managed Server:** Select a managed server associated with the backup server selected in the previous step
+- **Backup Name:** A name for the backup in Morpheus, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A8EBDB01-089D-4518-B943-4DACE51F7528-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Veeam
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..0263a76
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 359,
+  "parent_title": null,
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..668ed42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Guides](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
new file mode 100644
index 0000000..0542b2e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+  "title": "Boot Menus",
+  "ordinal": 251,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Menus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
new file mode 100644
index 0000000..d66dff7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
@@ -0,0 +1,21 @@
+# Boot Menus
+
+System-seeded Boot Menus are displayed and user-created Boot Menus can be edited and deleted. User-created Boot Menus are edited or deleted by clicking on the pencil or trash can icon in the appropriate row.
+
+## Adding a Boot Menu
+
+To begin, click + ADD. Available fields include:
+
+- NAME: Name of the Boot Menu
+- DESCRIPTION: Description of the Boot Menu
+- TYPE: Select between **bios, uefi, ipxe and grub**
+- ENABLED: Determines if the Boot Menu is active
+- DEFAULT MENU
+- ROOT MENU
+- MENU NAME
+- BOOT IMAGE
+- ANSWER FILE
+- MENU CONTENT
+- SUB MENUS
+
+Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json b/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
new file mode 100644
index 0000000..7b02150
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+  "title": "Budgets",
+  "ordinal": 74,
+  "parent_title": "Costing",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html",
+  "topic_cluster": {
+    "clustering_title": "Budgets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md b/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
new file mode 100644
index 0000000..f04c6ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
@@ -0,0 +1,51 @@
+# Budgets
+
+Budgets provide insight into spending across their designated scope, allowing users to create and plan a budget targeted to their account, clouds, tenants, users, or groups.
+
+## Creating A Budget
+
+1. Navigate to Operations  >  Costing  >  Budgets
+2. Start a new budget by clicking + ADD
+
+   1. **Name**
+   2. **Description**
+   3. **Scope:** Here you can choose which construct this budget is tied to (Account, Tenant, Cloud, Group, or User)
+   4. **Period:** Currently “Year” is the only option
+   5. **Year:** Select a year to set budgets for future years. Alternatively, select “custom” to create a multi-year budget or input a custom fiscal year if required by your organization
+   6. **Forecast Model:** Optionally apply a forecast model to the Budget. When applied, forecasted amounts for each budget interval will be computed and graphical trend lines will be shown based on the model computation
+   7. **Interval:** Choose Month, Quarter, Year then fill in the budgeted amount for that interval (for quarter and year interval Budgets the entered amount is evenly split across the months in the given interval)
+3. Click SAVE CHANGES
+
+![../_images/createBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-18A42C5E-8C61-4ADA-AF78-23E743A230ED-high.png)
+
+## Multi-year Budgets
+
+Some organizations may need to create multi-year budgets or may need to set a fiscal year period. By default, annual budgets are tied to a calendar year (January - December) but HPE Morpheus Enterprise offers the flexibility of setting a fiscal year period when needed. When selecting a value from the YEAR dropdown in the add/edit budget modal, select “Custom” rather than one of the discreet years from the list. After selecting Custom, START DATE and END DATE fields allow the user to input any desired fiscal year period. Users can enter a period of up to three years using the start and end date bookends. The entered period must be one, two or three full years, partial years are not permitted.
+
+In the example below, I’ve created a three-year budget:
+
+![../_images/multiBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5E19B144-131B-4F0D-892B-9D10DB431658-high.png)
+
+## Budget Monitoring
+
+As the year (or years) goes on, existing Budgets can be reviewed to compare actual spend against the budgeted amount. To access the Budget detail, navigate to Operations > Costing > Budgets and select the desired Budget. The reported actual amount for a given month will be the same as the total cost reported for the month on the Invoice with the same scoping (for the current month, projected cost is used). Depending on the Cloud type, this figure can be pulled from a public clouds live costing API (such as with AWS, Azure, or GCP Clouds) or from the HPE Morpheus Enterprise in-built cost metering for private clouds (like VMware).
+
+Example Budget, Cloud-scoped:
+
+![../_images/budget.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4A12A8C3-AB86-4D4A-AF4E-432D5D9515BA-high.png)
+
+Example Cloud Invoice for the same month:
+
+![../_images/invoice.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-36CA0790-41CA-421C-9971-50062F8B82F4-high.png)
+
+## Cloud Budgets
+
+If you scope a budget to a Cloud, visit the Cloud summary tab in Infrastructure  >  Clouds  >  Select Cloud to see a cost-to-budget breakdown for that Cloud.
+
+![../_images/cloudBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C731E3A8-F507-477B-93AB-71BC98DA37A0-high.png)
+
+## Budget Analytics
+
+In Operations  >  Analytics  >  Budget Analysis select scope (Account, Tenant, Cloud, Group, User) to view the budget analysis. If a budget exists for the selected scope, a cost breakdown against budgeted amounts will be shown.
+
+![../_images/budgetAnalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EA3645F4-5E49-4CFC-90CF-4A04880BF602-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json b/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
new file mode 100644
index 0000000..9eec247
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+  "title": "Retrying Workflows",
+  "ordinal": 116,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html",
+  "topic_cluster": {
+    "clustering_title": "Retrying Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md b/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
new file mode 100644
index 0000000..a14ff61
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
@@ -0,0 +1,7 @@
+# Retrying Workflows
+
+When a Workflow fails, HPE Morpheus Enterprise allows users to retry from the failed Task. Access the Workflow execution from the executions list page (Provisioning > Executions), from the Executions tab of the Workflow detail page (Library > Automation > Workflows > Selected Workflow), or from the History tab on the Instance detail page (Provisioning > Instances > Selected Instance). From the execution, select the Retry button which looks like a clockwise circular arrow and is highlighted in the screenshot below. This can be very useful as it allows you to resume what could potentially be a very long running Workflow from a point of failure without needing to start from the beginning. Similarly, if a provisioned Instance is in a failed state due to a failure in an attached Workflow (such as a failed Task in the Provision phase of an attached Provisioning Workflow), the user can opt to resume the Tasks from the failure point after making a correction and restore the Instance to a successfully-provisioned state.
+
+Retry Workflow Tasks Video Demo
+
+![../../_images/retryTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-433AD4AB-C735-49B2-913B-302BF3209248-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json b/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
new file mode 100644
index 0000000..63ad577
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+  "title": "Prerequisites",
+  "ordinal": 399,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md b/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
new file mode 100644
index 0000000..c5bb6a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
@@ -0,0 +1,55 @@
+# Prerequisites
+
+Before integrating the HPE BMaaS with Morpheus Enterprise, verify that the following prerequisites are met to ensure successful deployment and operation.
+
+## Supported Hardware
+
+HPE BMaaS supports the following HPE ProLiant server platforms:
+
+- HPE ProLiant Gen10 Plus servers
+- HPE ProLiant Gen11 servers
+- HPE ProLiant Gen12 servers
+
+Ensure that servers are equiped with a supported HPE iLO version and are reachable over the network.
+
+## Network Connectivity
+
+The Morpheus Enterprise appliance must have:
+
+- Network connectivity to the iLO management interface of each ProLiant server
+- Network connectivity to the physical data network interfaces used for operating system provisioning
+- Proper routing and firewall rules allowing bidirectional communication between Morpheus and target servers
+- For environments using managed networking, additional connectivity to supported network switches (for example, HPE Aruba CX) is required.
+
+## Access Credentials
+
+Ensure the following credentials are available for each ProLiant server:
+
+- iLO IP address
+- iLO administrator username
+- iLO administrator password
+
+Credentials must have sufficient privileges to perform power operations, hardware inventory, and virtual media mounting.
+
+## Morpheus Platform Requirements
+
+- A supported version of Morpheus Enterprise is installed and operational
+- Administrative access to Morpheus for HPE BMaaS installation and configuration
+- Sufficient storage configured in Morpheus for OS images
+
+## Operating System Images
+
+OS ISO images available in the Morpheus Virtual Image Library
+
+## SSH Keys for Remote Login tothe Instance
+
+- Configure the SSH key access from an authorized host, for details see HPE Morpheus Enterprise documentation.
+- You can configure the SSH in HPE Morpheus under Infrastructure > Trust > Key Pairs
+
+## User Settings for OS (Linux and Windows)
+
+When provisioning a Linux- or Windows-based resource and opting to create users during the provisioning, the credentials entered in this section are used to create user during. For configuration, navigate to User Settings > Linux or User Settings > Windows Settings.
+
+## Proxy Configuration
+
+To configure proxy, navigate to Infrastructure > Network > Proxies.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json b/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
new file mode 100644
index 0000000..2b9172f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+  "title": "Trust",
+  "ordinal": 525,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md b/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
new file mode 100644
index 0000000..c9440e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
@@ -0,0 +1,5 @@
+# Trust
+
+**Subtopics**  
+
+- **[CyberArk Conjur](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json b/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
new file mode 100644
index 0000000..8551d09
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+  "title": "Managing Instances",
+  "ordinal": 86,
+  "parent_title": "Instances",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md b/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
new file mode 100644
index 0000000..c25e35f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
@@ -0,0 +1,92 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Metadata, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual VM’s or Containers and cannot be undone, unless a Delayed Removal policy has been applied prior to the Deletion. To delete Instances without deleting associated VM’s, delete the Instances VM record(s) from the Infrastructure section with “Remove Infrastructure” deselected and select “Remove Associated Instances” in the VM delete modal options. This will delete the records in HPE Morpheus Enterprise but leave the infrastructure in place.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+## Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Service
+:   Stops, Starts or Restarts the service associated with the Instance Type.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Lock/Unlock Instance
+:   A locked instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, cpu, ram, networks and storage controller changes. Available options depend on the instance type and service plan configuration. Some resize actions require an instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. Only available for Instances with backups enabled.
+
+Run Workflow
+:   Presents workflow options and then immediately runs selected Workflow on the Instance. Workflows can be created in the Library > Automationsection.
+
+Run Script
+:   Presents Script options and immediately executes selected Script on the Instance. Scripts can be created in the Library section.
+
+Apply Template
+:   Presents Template options and immediately applies selected Template to the Instance. Templates can be created in the Library section.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on instance configuration and type.
+
+Eject Disk
+:   Ejects attached disk/iso.
+
+Add Slave
+:   Adds a database slave in the Instance.
+
+Change Master
+:   Changes the database Master node in an Instance.
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding HPE Morpheus Enterprise Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
+
+## Performing Instance Actions
+
+### Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. Click the Instance from the list of instances you wish to perform an action on.
+3. Click the Actions drop down button and select an Action.
+
+## Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab button on the bottom of Instance Detail pages. Instances with associated VMware VM’s will bi-directionally sync HPE Morpheus Enterprise Instance Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json b/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
new file mode 100644
index 0000000..09d476c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+  "title": "PowerDNS",
+  "ordinal": 486,
+  "parent_title": "DNS",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html",
+  "topic_cluster": {
+    "clustering_title": "PowerDNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md b/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
new file mode 100644
index 0000000..44673f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
@@ -0,0 +1,78 @@
+# PowerDNS
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with PowerDNS to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in PowerDNS Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add PowerDNS Integration
+
+### About this task
+
+PowerDNS can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   PowerDNS
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   API HOST
+   :   URL of PowerDNS API. Example: `http://10.30.20.10:8081`
+
+   Token
+   :   PowerDNS API Token
+
+   Version
+   :   PowerDNS API Version
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, PowerDNS Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring PowerDNS with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json b/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
new file mode 100644
index 0000000..4ac619c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+  "title": "Google Cloud Platform (GCP)",
+  "ordinal": 395,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-36BA3E37-26D3-488F-85C2-942C45119F02.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Platform (GCP)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md b/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
new file mode 100644
index 0000000..33f6f19
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
@@ -0,0 +1,297 @@
+# Google Cloud Platform (GCP)
+
+## Integration Features
+
+- Provisioning Virtual Machines
+- Network tagging
+- Private and Local Images
+- Google VM Snapshots
+- Brownfield Inventory
+- Costing
+- Right-sizing
+- Shared Network Support
+
+## Requirements for Integration with HPE Morpheus Enterprise
+
+To integrate HPE Morpheus Enterprise with Google Cloud Platform, you will need the following. APIs are enabled in “APIs & Services” and must be enabled for all projects or the selected project (depending on your GCP Cloud integration settings). The next section contains more detailed steps for enabling API in the GCP web console.
+
+- The Compute Engine API enabled
+- The Cloud Resource Manager API enabled
+- The Cloud Billing API
+- The Identity and Access Management (IAM) API enabled
+- The BigQuery API enabled
+- The BigQuery Data Transfer API enabled
+- The Kubernetes Engine API enabled (required to provision GKE clusters)
+- Credentials for an IAM service account with Owner or Compute Admin role permissions
+- The private key and client email for the service account
+
+This integration guide goes through the process of configuring your account and obtaining the information necessary to integrate with HPE Morpheus Enterprise. Continue to the next section for a detailed look at enabling the APIs mentioned above.
+
+## Enabling the Required APIs
+
+In order to take full advantage of the HPE Morpheus Enterprise integration with Google Cloud, a number of APIs must be enabled within the GCP web console. It’s recommended that you enable all of the APIs listed in the preceding section regardless of the HPE Morpheus Enterprise feature set you intend to use. This will ensure you do not run into problems down the road stemming from a lack of access which may take time to diagnose.
+
+Log into the Google Cloud web console and navigate to the APIs and Services page. You may find this in the Quick access area of the welcome page or you can search for it as shown in the screenshot below.
+
+![../../../_images/apis.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C41DCEFF-896A-485D-B7F1-1097EF7E1E18-high.png)
+
+From the APIs and Services page, a list of enabled APIs and some details about your usage are shown. To enable new APIs, click + ENABLE APIS & SERVICES near the top of the window. Now on the API library page, search for the API you wish to enable. Here I’ve searched for the Kubernetes Engine API.
+
+![../../../_images/apisearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-11AC3447-F2D7-4C1D-B2FD-AF477146AB37-high.png)
+
+From the search results, click on the API you wish to enable to view its detail page. Click ENABLE. Once successfully enabled, the button will change to a MANAGE button. It may take a few moments for the API to be fully enabled. You may also be prompted to enable the Cloud Billing API or create an association with a Billing Account when enabling APIs. Go ahead and do so if prompted.
+
+![../../../_images/apienable.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-88E68260-6F46-43BB-8525-EF1D814408B5-high.png)
+
+Repeat this process until all required APIs (listed in the previous section) are enabled.
+
+## Creating a Service Account
+
+### Procedure
+
+1. From anywhere in the GCP web console, search for “service accounts” in the global search bar at the top of the window
+2. Click on the Service Accounts page (within the IAM & Admin stack)
+3. A list of existing service accounts within the selected Project is shown (if any)
+4. To create a new one, click + CREATE SERVICE ACCOUNT 
+
+   ![../../../_images/3create_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A3CD48CE-C19C-41EF-A6C2-286B2320673B-high.png)
+5. Enter at least a name for your new service and click CREATE AND CONTINUE 
+
+   ![../../../_images/4config_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5E5FB1A4-AE19-4582-BF8A-CBDF18100628-high.png)
+6. After creating the service account, you’ll be prompted to set a role for the account. In order to fully integrate with HPE Morpheus Enterprise, you must use an account in the Owner role or the Compute Admin role
+7. Click CONTINUE 
+
+   ![../../../_images/5service_acct_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-172734F2-7D01-4F27-83CA-40CB948F05D2-high.png)
+8. Following creation of the service account, you’ll be taken back to the list of existing service accounts
+
+## Generating Keys and Integrating with HPE Morpheus Enterprise
+
+### Procedure
+
+1. From the list of service accounts, click the ellipsis button (…) to the right of a selected account
+2. Click “Manage Keys” 
+
+   ![../../../_images/6create_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-94F3D47B-1CE6-4C7C-A572-745199DE161D-high.png)
+3. On the Keys page, click “Add Key” and then “Create New Key”
+4. Select JSON format and click CREATE
+5. A JSON-formatted document will be downloaded, this document contains the Project ID, private key, and client email values needed to complete the integration process in the next step
+
+## Add a GCP Cloud
+
+### About this task
+
+NOTE
+
+The JSON-formatted document downloaded when creating a key for your service account contains all of the required values for completing the integration. Consult the above section on generating keys if needed.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select + CREATE CLOUD, select Google Cloud, and then click NEXT.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   PRIVATE KEY
+   :   The service account private key. Paste in the entire value between (but not including) the quotation marks in your downloaded JSON document, formatted like the following example: `-----BEGIN PRIVATE KEY-----(your_key)-----END PRIVATE KEY-----`
+
+   CLIENT EMAIL
+   :   The service account client email, ex: morpheus@morpheus.iam.gserviceaccount.com
+
+   PROJECT ID
+   :   Projects will auto-populate upon successful entry of the private key and client email. You can opt to scope the GCP integration to a single Project or select “All” to instead select the Project from the Resource Pool dropdown at provision time
+
+   REGION
+   :   Regions will auto-populate upon successful entry of the private key and client email. Select the appropriate region for this Cloud, if applicable. You can also opt to scope the GCP integration to all regions to allow users to select from any region at provision time
+
+   INVENTORY EXISTING INSTANCES
+   :   If checked, existing GCP resources will be inventoried and appear as unmanaged virtual machines in HPE Morpheus Enterprise.
+
+   If advanced options are not needed, click NEXT to advance to the Group selection page. Otherwise, continue on with this guide and review advanced or provisioning options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After reviewing all options, click NEXT to advance to the Group selection page. Following Group selection, click COMPLETE to finish the integration process. If you’ve opted to inventory existing Instances, they will be viewable in HPE Morpheus Enterprise shortly. At this point, you are ready to provision new resources in Google Cloud Platform as needed!
+
+### Results
+
+IMPORTANT
+
+If you experience difficulties adding a GCP Cloud, review the above guide and ensure you’ve met all requirements for completing the integration. For example, if the Compute Engine API is not enabled, HPE Morpheus Enterprise will not accept credentials entered on the Create Cloud modal. If you repeatedly run into problems completing the integration process, review the above guide in its entirely and double check that each step is completed and your account meets all configuration requirements.
+
+## Create a GCP Project
+
+### About this task
+
+On initial integration, HPE Morpheus Enterprise will sync Projects and allow you to scope the integration to a specific Project or to scope the integration to all Projects. As time goes on, additional Projects are continually synced and can be managed from within the Resources tab on the Cloud detail page (Infrastructure > Clouds > Selected GCP Cloud). Within the Resources tab, users can edit some Project settings as well as delete Projects if needed.
+
+To create a new GCP Project:
+
+### Procedure
+
+1. Click + ADD RESOURCE POOL
+2. Enter a name value for the new Project
+3. Mark the “DEFAULT” box if you’d prefer newly provisioned Instances default to the new Project
+4. Enter a Project ID and ensure it meets the listed validation requirements
+5. Set a Parent value if the new Project should exist underneath a parent organization
+6. Finally, select a billing account
+7. Click SAVE CHANGES
+
+### Results
+
+After a few minutes, the new Project will be ready on the GCP side and HPE Morpheus Enterprise will be ready to provision new resources into it.
+
+## Enabling Live Costing for GCP
+
+GCP costing is done at the Billing Account level. Each Billing Account can be linked to one or more GCP Projects. All projects which are linked to the Billing Account will have their costing data available to HPE Morpheus Enterprise but if the GCP Cloud has been scoped to only one Project, HPE Morpheus Enterprise will ingest costing data only for that Project. Users can view the Billing Account linked to a particular project by clicking on the hamburger menu (main menu button in the far upper-left of the console window) and selecting billing. A pop-up window will give users the option to navigate to the Billing Account which is linked to the currently-selected Project.
+
+![../../../_images/costing1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9F511176-D2F9-4455-A1EB-7E9EA11219B3-high.png)
+
+Within the Billing Account, Standard Usage Cost must be enabled for HPE Morpheus Enterprise to access costing data. From the page for the appropriate Billing Account, click on Billing Export and then click “Edit Settings” under the “Standard usage cost heading”. Specify a project and create a dataset or specify an existing one. In doing this, you’re specifying a location for the dataset which will be for the entire billing account and not just for the Project the dataset resides in.
+
+![../../../_images/costing2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A3C3C708-1787-4F98-AA95-99BBBDDCEFAC-high.png)
+
+With configuration in the GCP console completed, we can now enable cost onboarding from the HPE Morpheus Enterprise side. Add or edit an existing GCP Cloud (Infrastructure > Clouds). Within the Advanced Options section, note the COSTING PROJECT and COSTING DATASET fields. When selecting a Project, associated datasets (if any) will automatically be loaded into the dropdown in the next field for selection. Additionally, the COSTING field should be set to “Sync Costing” rather than “Off”. Recall from the previous paragraph that this is merely pointing to the Project that houses the appropriate dataset. If your GCP Cloud in HPE Morpheus Enterprise is configured for all Projects, all costing data will be consumed for the Projects linked to the associated Billing Account (assuming those Projects have billing enabled). If the GCP Cloud in HPE Morpheus Enterprise is scoped to just one Project, only billing data for that Project will be onboarded. For this reason, the selected Costing Project can be (but is not necessarily) the Project to which the HPE Morpheus Enterprise Cloud is scoped.
+
+![../../../_images/costing3.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-15DC0856-A5ED-4CE5-8AFF-7C30A062DA86-high.png)
+
+## Windows Images
+
+HPE Morpheus Enterprise can add custom metatdata that will be injected into the unattend conf by GCP during provisioning. This is required for customizations including setting the Windows Administrator password during provisioning. GCP Windows Images must be syspreped using the `GCESysprep` command prior to image creation, and must have platform/os set on the Virtul Image record in HPE Morpheus Enterprise after image sync for successful customization and Agent Installation.
+
+### GCP Windows Requirements
+
+- GCP Windows Images must be syspreped using the `GCESysprep` command prior to Image creation in GCP. Refer to [Googles “creating-windows-os-image” doc](https://cloud.google.com/compute/docs/instances/windows/creating-windows-os-image).
+- Once the Image is synced into Morpheus, the Platform (Windows, Windows 2016 etc) must be set on the HPE Morpheus Enterprise Virtual Image record, otherwise linux is assumed and the metadata will not be generated correctly.
+- The Global Windows “Administrator” password must be set in HPE Morpheus Enterprise under `/admin/provisioning/settings` > Windows Settings > AdministratorPassword, or Administrator and password defined on the HPE Morpheus Enterprise Virtual Image record.
+- Be aware the unattend configuration during startup after sysprep delays causes a reboot and a prolonged finalization process during provisioning, and console/rdp may not be available during this time as windows is configuring.
+
+NOTE
+
+Some Google provided Windows Images have slow startups that cause the Morpheus Agent service to not start within the default 30 second service startup timeframe, including after initial reboot after sysprep/unattend configuration. This can be adjusted by running `New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\" -Name "ServicesPipeTimeout" -PropertyType DWORD -Value 180000` in powershell on the Windows Image.
+
+IMPORTANT
+
+Failure to use a GCP Windows Image that has not been sysprepped using `GCESysprep` will cause Agent Installation, Automation, and Console issues as HPE Morpheus Enterprise will not be able to set user credentials and authenticate.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json b/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
new file mode 100644
index 0000000..a3baa7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+  "title": "Adding hosts",
+  "ordinal": 185,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md b/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
new file mode 100644
index 0000000..ae8aad0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
@@ -0,0 +1,13 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the HVM Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once HPE Morpheus Enterprise has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
+
+![../../_images/addHost.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-23D2DBDA-8840-4B60-A4B2-04DAD55E279E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json b/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
new file mode 100644
index 0000000..b06aa0d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+  "title": "Attaching Logs to Case",
+  "ordinal": 347,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html",
+  "topic_cluster": {
+    "clustering_title": "Attaching Logs to Case",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md b/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
new file mode 100644
index 0000000..6e24f28
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
@@ -0,0 +1,11 @@
+# Attaching Logs to Case
+
+When submitting a case it is critical to attach the relevant logs. The logs can be found at `/var/log/morpheus/morpheus-ui/current`. Logs can be attached to the case at anytime.
+
+When submitting logs please reproduce the error right before capturing and sending the log file. This will ensure the activity that took place and resulted in an error is contained in the logs.
+
+Log rotation takes the current file each night or after it’s a certain size and compresses them. The `*.s` files in the current directory are rotated and zipped logs that can be sent as is.
+
+The logs can also be captured from the Morpheus UI. Under Administration > Health > Morpheus Logs. Please copy relevant logs and add to case as an attachment.
+
+![../_images/Morpheus-Health-Logs.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json b/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
new file mode 100644
index 0000000..0f7131f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+  "title": "Role Permissions",
+  "ordinal": 106,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md b/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
new file mode 100644
index 0000000..846b505
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
@@ -0,0 +1,5 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete tasks.
+
+Tasks Types that can execute locally against the HPE Morpheus Enterprise Appliance have an additional Role Permission: `Tasks - Script Engines`. Script Engine Task Types will be hidden for users without `Tasks - Script Engines` role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..5d934a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 235,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..11bccce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1,112 @@
+# Servers
+
+## Add Storage Server
+
+### Adding 3Par Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+#### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC Isilon Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json b/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
new file mode 100644
index 0000000..3f20529
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+  "title": "Creating Custom Cluster Layouts",
+  "ordinal": 145,
+  "parent_title": "Cluster Layouts",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Custom Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md b/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
new file mode 100644
index 0000000..f7e8cd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
@@ -0,0 +1,207 @@
+# Creating Custom Cluster Layouts
+
+Custer Layouts can be built for an infinite number of use cases and targeting a wide range of configurations or provisioning technologies. However, it still may help to see an example Cluster Layout created. In this section, we’ll create an example Cluster Layout which provisions a Kubernetes Cluster to a VMware vCenter Cloud containing a master node and three worker nodes. We’ll build out two Node Types to embed in the Cluster, one master and one worker. Within the Node Types, we will embed Script Templates needed to configure the nodes as they are provisioned and allow the workers to join the cluster. Script Templates can be configured to execute at various phases of the lifecycle of the node, similar to a Provisioning Workflow, so HPE Morpheus Enterprise can orchestrate the whole process.
+
+## Creating Script Templates
+
+We’ll first start by creating the necessary Script Templates. In this example, I’ll use a generic prep script that both the master and worker nodes will utilize and then I’ll create three additional scripts (two for the master node and one for the worker nodes) to accomplish various Kubernetes cluster setup tasks (`kubeadm init`, creating Role Bindings, joining workers to the cluster, etc.). I’ll briefly describe each here and step through the process of creating the Script Template objects in HPE Morpheus Enterprise.
+
+To begin a new Script Template, navigate to Library > Templates > Script Templates and click + ADD. All of the scripts used in this example will be “Bash” type, run as user “root” and with SUDO marked.
+
+The first script to add will be a prep script that both the master and worker nodes will use. This script turns swap off, installs `containerd`, runs updates, sets network config, and installs `kubelet`, `kubeadm`, and `kubectl`. Set this script to run in the PreProvision phase. The complete script, named “k8sprep” in my example can be viewed below:
+
+### k8sprep Script Template
+
+```
+```
+function wait_for_dpkg() {  
+  FRONT_END_LOCK_FILE=/var/lib/dpkg/lock-frontend  
+  DPKG_LOCK_FILE=/var/lib/apt/lists/lock  
+  echo "checking for dpkq lock existence..."  
+  if [ -e "$DPKG_LOCK_FILE" ]; then  
+    while fuser $DPKG_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $DPKG_LOCK_FILE..."  
+      sleep 1  
+    done  
+  fi  
+  echo "checking for dpkq lock-frontend existence..."  
+  if [ -e "$FRONT_END_LOCK_FILE" ]; then  
+    while fuser $FRONT_END_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $FRONT_END_LOCK_FILE..."  
+      sleep 1  
+    done  
+    echo "force removing lock $FRONT_END_LOCK_FILE"  
+    sudo rm $FRONT_END_LOCK_FILE  
+    sleep 5  
+  fi  
+}  
+  # Swap must be turned off see https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo swapoff -a ; sudo sed -i '/ swap / s/^/#/' /etc/fstab  
+  # Install containerd packages from Debian sse: https://docs.docker.com/engine/install/ubuntu/  
+wait_for_dpkg  
+sudo apt-get update  
+sudo apt-get install ca-certificates curl gnupg lsb-release -y  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpgsudo  
+echo   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \  
+$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null  
+sudo apt-get update  
+  # the Docker documentation advises to install the whole Docker runtime environment but containerd.io is sufficient  
+sudo apt-get install containerd.io -y  
+  # Prepare the necessary network config see: https://kubernetes.io/docs/setup/production-environment/container-runtimes/  
+sudo cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf  
+overlay  
+br_netfilter  
+EOF  
+sudo modprobe overlay  
+sudo modprobe br_netfilter  
+sudo cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf  
+net.bridge.bridge-nf-call-iptables  = 1  
+net.bridge.bridge-nf-call-ip6tables = 1  
+net.ipv4.ip_forward                 = 1  
+EOF  
+  # Apply sysctl params without reboot  
+sudo sysctl --system  
+  # Install kubeadm follwing the K8s documentation: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo apt-get install -y apt-transport-https ca-certificates curl  
+sudo curl -fsSL  https://packages.cloud.google.com/apt/doc/apt-key.gpg|sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/k8s.gpg  
+sudo echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list  
+sudo apt-get update  
+sudo apt-get -y install -y kubelet=1.26.1-00 kubeadm=1.26.1-00 kubectl=1.26.1-00  
+sudo apt-mark hold kubelet kubeadm kubectl  
+  # see https://github.com/etcd-io/etcd/issues/13670  
+cat << EOF | sudo tee /etc/containerd/config.toml  
+version = 2  
+  [plugins]  
+  [plugins."io.containerd.grpc.v1.cri"]  
+   [plugins."io.containerd.grpc.v1.cri".containerd]  
+      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]  
+        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]  
+          runtime_type = "io.containerd.runc.v2"  
+          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]  
+            SystemdCgroup = true  
+EOF  
+sudo systemctl restart containerd
+```
+```
+
+Next we’ll add a script called “kubeadm-init” in this example which will create and configure some working directories, set the `kubeadm` config yaml, and run `kubeadm init`. Set this script to run in the PreProvision phase as well. The complete script can be viewed below:
+
+### kubeadm-init Script Template
+
+```
+```
+mkdir -p <%=morpheus.morpheusHome%>/kube  
+mkdir -p <%=morpheus.morpheusHome%>/kube/working  
+mkdir -p <%=morpheus.morpheusHome%>/.kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube/working  
+cat <<EOF | sudo tee <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+# kubeadm-config.yaml  
+kind: ClusterConfiguration  
+apiVersion: kubeadm.k8s.io/v1beta3  
+kubernetesVersion: v1.26.1  
+networking:  
+  serviceSubnet: "10.96.0.0/16"  
+  podSubnet: "10.244.0.0/24"  
+  dnsDomain: "cluster.local"  
+apiServer:  
+  extraArgs:  
+    authorization-mode: "Node,RBAC"  
+clusterName: "example-cluster"  
+---  
+kind: KubeletConfiguration  
+apiVersion: kubelet.config.k8s.io/v1beta1  
+cgroupDriver: systemd  
+EOF  
+sudo kubeadm init --config <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+sudo cp -i /etc/kubernetes/admin.conf <%=morpheus.morpheusHome%>/.kube/config &&  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/.kube/config
+```
+```
+
+Lastly, we’ll add a setup script for the Kubernetes master node called “k8s-master-setup” for this example. This script creates the service account and role bindings. Set this script to run in the PostProvision phase and view the complete script below:
+
+### k8s-master-setup Script Template
+
+```
+```
+#create a service account  
+cd <%=morpheus.morpheusHome%>  
+#kubectl -n kube-system create sa morpheus  
+kubectl create sa morpheus  
+cat <<EOF | tee <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+apiVersion: v1  
+kind: Secret  
+metadata:  
+  name: morpheus-token  
+  annotations:  
+    kubernetes.io/service-account.name: morpheus  
+type: kubernetes.io/service-account-token  
+EOF  
+kubectl create clusterrolebinding serviceaccounts-cluster-admin --clusterrole=cluster-admin --group=system:serviceaccounts  
+kubectl create -f <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
+```
+```
+
+The three scripts we’ve just created will prepare the master node for our cluster. We now need an additional script that will prepare the worker nodes and join them to the cluster. The worker nodes will also use the “k8s-prep” script we added in the very first step which you’ll see in the next step when we create the node types.
+
+Add a fourth script which I’ve called “k8s-join” for this example. This script takes advantage of a special `joinCommand` variable as you’ll see when you view the full script. If you want to see exactly what this does later, you can create a new Bash script Task that echoes out that variable and run it against an existing Kubernetes worker node VM (`echo "<%=morpheus.kubernetes.joinCommand%>"`). Set this script to run in the PostProvision phase and view the full script below:
+
+### k8s-join Script Template
+
+```
+```
+sudo <%=morpheus.kubernetes.joinCommand%>
+```
+```
+
+This completes the needed Script Templates which we will set on two new Node Types in the next step. Continue on to the next section.
+
+## Creating Node Types
+
+With the Script Templates created we now need to make two new Node Types, one for the master node and one for the worker nodes. In this example case, we don’t need to add a new Virtual Image because we can use one of the preinstalled system images for Ubuntu on VMware vCenter which will work fine. Node Types are created in Library > Blueprints > Node Types. Once there, click + ADD. Within the modal for the new Node Type, configure the following:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the master node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep”, “kubeadm-init” and “k8s-master-setup” Script Templates (you may have called them something different)
+
+Finally, click SAVE CHANGES.
+
+Repeat the process to create a second Node Type. The second time around, use the following configurations:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the worker node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep” and “k8s-join” Script Templates (you may have called them something different)
+
+Once done, click SAVE CHANGES to save the second Node Type. With the pieces in place, we are now ready to create the Cluster Layout object itself. Continue on to the next section.
+
+## Creating a Cluster Layout
+
+At this point we can create the Cluster Layout object in HPE Morpheus Enterprise and attach the Node Types we’ve just created (which themselves have our Script Templates applied). Cluster Layouts are created in Library > Blueprints > Cluster Layouts. Click + ADD and configure the following:
+
+- **NAME:** Provide a name for the Cluster Layout, can be anything to denote this is a Kubernetes cluster
+- **VERSION:** The version number you wish to apply to this Cluster Layout which is useful if you later iterate on this Cluster Layout
+- **CLUSTER TYPE:** Kubernetes Cluster
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4096 MB
+- **INPUTS:** Use the typeahead field to add configured Inputs to the Cluster Layout
+- **MASTER NODES:** Use the typeahead field to find the Kubernetes master Node Type we just created
+- **WORKER NODES:** Use the typeahead field to find the Kubernetes worker Node Type we just created. Set the “Count” value to three (3) since we wish to have three worker nodes in this cluster
+- **CLUSTER PACKAGES:** Use the typeahead field to add configued Cluster Packages to the Cluster Layout. Cluster Packages are created in the [Templates section](https://docs.morpheusdata.com/en/latest/library/templates/templates.html)
+- **SPEC TEMPLATES:** Use the typeahead field to add Spec Templates to the Cluster Layout
+
+Click SAVE CHANGES to save the Cluster Layout.
+
+## Testing and Wrap-Up
+
+At this point we are finished and we have a viable Kubernetes cluster that we can deploy with just one click. To add a new managed cluster to this HPE Morpheus Enterprise environment, navigate to Infrastructure > Clusters. To provision a cluster from the layout we just created, click + ADD CLUSTER and select “Kubernetes Cluster” from the dropdown menu. Make the appropriate selections to target the new cluster to an existing VMware vCenter Cloud and complete the wizard. Once complete, the new cluster will be visible on your clusters list page and from there you can drill into the detail page to view relevant details about the cluster including monitoring metrics, current workloads, and more.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json b/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
new file mode 100644
index 0000000..e0be326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+  "title": "Dell ECS",
+  "ordinal": 521,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html",
+  "topic_cluster": {
+    "clustering_title": "Dell ECS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md b/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
new file mode 100644
index 0000000..8378aa5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
@@ -0,0 +1,246 @@
+# Dell ECS
+
+## Overview
+
+HPE Morpheus Enterprise integrates with DELL EMC ECS via the ECS api. This allows Morpheus to talk directly to the ECS services.
+
+When you add a ECS Server, HPE Morpheus Enterprise will sync in the following.
+
+- Storage Groups
+- Buckets
+- File shares
+
+Users will be able to create the following items within ECS without direct access to the ECS console.
+
+- Buckets
+- File shares
+
+## Storage Servers
+
+The first step in the Dell EMC ECS integration is to add a Dell EMC ECS Storage Server. Once added, Buckets, Files Shares and Storage Groups will be synced in and can be access and managed in HPE Morpheus Enterprise.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Buckets
+
+- **Buckets** will be listed in Infrastructure - Storage - Buckets
+
+  - Buckets can be created and deleted with Infrastructure - Storage Role Permissions
+  - Buckets can be browsed with Infrastructure: Storage Browser Role permissions
+  - File and folders can be uploaded, downloaded and deleted with Full Infrastructure: Storage Browser Role permissions.
+
+## Adding Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell ECS Bucket.
+
+To Add a Dell ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell ECS bucket.
+
+   USER
+   :   Your Dell EMC ECS S3 user account
+
+   SECRET KEY
+   :   Your Dell EMC ECS S3 Secret
+       :   Example: jW+pFyAPtSS5FuEqKwt44xlpM/2
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Add Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json b/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
new file mode 100644
index 0000000..49e0bcc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+  "title": "Hosts",
+  "ordinal": 211,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md b/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
new file mode 100644
index 0000000..b047e7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
@@ -0,0 +1,12 @@
+# Hosts
+
+![../../_images/infra_compute_header_hosts_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BC2FD43F-BD46-40FD-BA88-FA7789B6DE81-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Hosts in HPE Morpheus Enterprise are Hypervisors and Container hosts that VMs and Containers are hosted on, such as ESXi Hosts and Kubernetes Master and Workers. These hosts are populated from integrated clouds, hosts and clusters provisioned from Morpheus, or manually added hosts.
+
+Provisioning new hosts takes place in the Infrastructure > Clusters section of HPE Morpheus Enterprise. For example, provisioning a new Docker cluster in that section will begin the process of creating a HPE Morpheus Enterprise-managed Docker cluster with one host (by default). Additional hosts and custom layouts can also be created. See the [Clusters section](https://docs.morpheusdata.com/en/latest/infrastructure/clusters/clusters.html) of HPE Morpheus Enterprise docs for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..21bbd33
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 296,
+  "parent_title": "Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..48158c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,12 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[User Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html)**
+- **[Tenant Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html)**
+- **[Cloud Access Levels](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json b/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
new file mode 100644
index 0000000..6d81d4e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+  "title": "Import and Export",
+  "ordinal": 98,
+  "parent_title": "Code",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html",
+  "topic_cluster": {
+    "clustering_title": "Import and Export",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md b/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
new file mode 100644
index 0000000..d6aed21
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
@@ -0,0 +1,128 @@
+# Import and Export
+
+Onboarded Git repositories can be configured as either import or export targets for a HPE Morpheus Enterprise appliance. This means that many created HPE Morpheus Enterprise constructs, such as Tasks, Library Items, and others, can be backed up to an integrated Git repository as code. This backup can take place on an automatic schedule (syncs every four hours) or can be triggered manually after changes are made. Users can back up all supported constructs within the appliance to a single repository or use Labels to back up only selected items. Exported constructs can also be imported into target appliances. This is useful for sharing items between two HPE Morpheus Enterprise environments, such as from a development appliance to a production appliance.
+
+NOTE
+
+The use of this feature requires an integrated Git repository. Please see our [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for Github or other Git integrations if you’ve not yet integrated your code repositories. While Morpheus can onboard and work with both public and private code repositories, it is strongly recommended that you use private repositories for exporting your Morpheus constructs as code.
+
+Supported Constructs:
+
+- Tasks
+- Workflows
+- Spec Templates
+- Library Items
+- Forms
+
+NOTE
+
+When exporting all supported constructs HPE Morpheus Enterprise will export more than just the above types, however, only the above types are exportable as individual resources. This list may expand in the future as additional constructs become supported by future updates.
+
+## Role Permissions
+
+Access and capabilities for the Import/Export feature set is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Export/Import`
+:   - **None:** Cannot access the edit button on the Code List Page (Provisioning > Code) to set Import/Export settings or see Import/Export actions on the Code Repository Detail Page
+    - **Full:** Code repositories can be edited to set Import/Export configurations and Import/Export actions can be viewed and used on Code Repository Detail Pages
+
+## Import/Export Settings
+
+Code repositories are set to allow import, export or both from the Code Repositories List Page (Provisioning > Code). Click the edit button (✎) to the right of the selected repository to edit its import/export settings. When editing a code repository for import and export, set the following configurations:
+
+- **ENABLED:** When marked, routine syncs will take place between HPE Morpheus Enterprise and this repository. This includes all file syncs and not just actions related to import and export
+- **IMPORT/EXPORT:** Set “Auto export all” to automatically export once every four hours, “Manual export” to enable this repository for manual exports on demand, “Manual import” to enable this repository for manual imports on demand, “Import/Export” to enable both manual imports and exports on demand
+- **PATH:** The path within the repository where HPE Morpheus Enterprise should import from or export to
+- **EXPORT LABEL FILTER:** Enter a Label and HPE Morpheus Enterprise will export or import only constructs which include the Label into the repository. This must be a single Label, it cannot be a list of multiple Labels
+
+Once you’ve configured the code repository, click SAVE CHANGES
+
+NOTE
+
+Code repositories must have at least one file in them in order to export HPE Morpheus Enterprise constructs as code. This can be as simple as a README file, they just cannot be empty.
+
+![../../_images/editRepo.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1897DAD3-23E6-4D44-8331-93C40D4FD9FA-high.png)
+
+## Exporting
+
+After a repository is configured to allow export (see previous section), it may perform periodic automatic refreshes or the user may need to refresh the repository on demand (depending on settings). To manually initiate an export, drill into the Repository Detail page, click ACTIONS, and click “Export All Resources”.
+
+![../../_images/exportAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-01557155-5F51-4E18-9423-80740E675D88-high.png)
+
+Any new or updated constructs will be refreshed within the repository at the path your repository is configured to export into. Bear in mind that, even if you’ve configured HPE Morpheus Enterprise to export only constructs categorized with a specific Label, any required dependencies would also be exported. For example, if you’ve labeled a Workflow to be exported, HPE Morpheus Enterprise will also export the dependency Tasks so the Workflow will be functional. A similar behavior applies for exported Library Items which may have a number of dependencies. In the screenshot below, files can be seen populating the targeted Github repository.
+
+![../../_images/githubView.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-200CE557-64D2-4090-9C52-EE941972E411-high.png)
+
+HPE Morpheus Enterprise items are exported as scribe files. These are HCL-formatted representations of the construct as code. They include static attributes representative of the attributes set on the construct itself or they may use UUIDs to refer to other constructs or integrations. It shouldn’t be necessary to view or edit them unless you’re curious.
+
+![../../_images/viewScribe.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5C55D002-8AF1-4F8D-9EAE-D6839820B80F-high.png)
+
+## Importing
+
+After HPE Morpheus Enterprise constructs have been exported as code, they can be pulled down into other appliances which have the same repositories integrated. Items can be imported ad-hoc from the file browser within a Code Repository Detail page. Click on the gear (⚙) dropdown to the right of any scribe file that may exist in your repository. For example, in the screenshot below, an individual Task is being imported into the destination appliance.
+
+![../../_images/importFile.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E526F230-60CB-4FB1-ACCE-EA127DA5E7D2-high.png)
+
+In addition to importing one-off items, code repositories may also be configured for import so that many items can be imported at once. The same configurations can be made for import as export, including a specific path within the repository to import from and whether only specific Label groups should be targeted. Triggering a larger scale import for a whole repository is done from the Code Repository Detail Page. Click the ACTIONS button and then click “Import All Resources”.
+
+![../../_images/importAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-66220000-CC18-46E6-9B31-28E732091886-high.png)
+
+Once the import has been initiated, HPE Morpheus Enterprise will check to see if a new item will be created, if an existing item would be updated, if no action could be taken due to a conflict, or if no changes would result. This information is presented to the user who may then decide if the import action should go ahead.
+
+![../../_images/checkImport.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7E6E76A0-2B8D-49C7-ADBE-3D515134ED07-high.png)
+
+IMPORTANT
+
+Care has been taken with HPE Morpheus Enterprise Import/Export to ensure that existing work cannot be wiped out by an import action. For example, if a Task with a name identical to a pre-existing Task would try to be imported, HPE Morpheus Enterprise will require the naming conflict be resolved before the import can take place. In fact, HPE Morpheus Enterprise Import can only create new items or overwrite items created by import. It cannot overwrite anything user-created or anything pre-seeded with the system at install. Additionally, import cannot be scheduled automatically. Users must initiate all imports.
+
+IMPORTANT
+
+Importing resources which rely on existing integrations or sensitive values will require some additional configuration on the destination appliance. For example, importing a Task which references code in a separate repository which is not integrated on the target appliance will be imported with reference to the missing integration. This integration would need to be added before the Task could be used. Another example scenario would be a Task which references a secret value held in HPE Morpheus Enterprise Cypher. Once again, the Task would be imported and the required Cypher references would need to be made within the destination appliance before the Task could be used.
+
+## Checking Imported Items Prior to Use
+
+As mentioned in the previous section, not every imported item will immediately be available for use. This is primarily due to the target appliance lacking an integration (for example, an Ansible Tower integration required for an imported Task) or a securely stored secret string (for example, a Task that calls a secret string stored in HPE Morpheus Enterprise Cypher). HPE Morpheus Enterprise will still import these resources but this section discusses some manual changes that may have to be made to imported items in order for them to be usable. HPE Morpheus Enterprise will attempt to export all dependent resources (for example, the needed Tasks if a Workflow is exported) but imported items should still be checked and manually supplemented under certain conditions outlined below.
+
+When exporting, remember that HPE Morpheus Enterprise cannot export to a completely empty repository. Any file (such as a README) needs to exist first. Items deleted from HPE Morpheus Enterprise but previously exported to your repository will continue to exist in the repository. If you wish to delete them from any future imports, you must manually delete them from the repo. Finally, bear in mind that export functionality will only export items which are owned by the Tenant in which the export is created. HPE Morpheus Enterprise does not currently support exporting items which are shared to the tenant from the Master Tenant.
+
+### Protected Fields and User Credentials
+
+Protected information and secret values are not exported. When importing any resources which rely on protected information, the user will need to manually update the resource on the target appliance. Examples include anything authenticated using a stored credential set (from the Infrastructure > Trust > Credentials section), anything with a password field (such as HTTP Tasks or REST-based Option Lists accessing password-protected information), Chef Task Data Bag Keys, and more. Anything configured with a password or other protected field will need to be edited on the importing appliance and updated to have the protected information needed to function.
+
+### Integrations
+
+When an imported Task requires an integration that does not exist on the appliance, an integration will be created with the same name. The integration credentials will not be established, nor will any other configuration fields outside of the name. Users will need to update the integration configuration to make it functional in order for the imported Task to function.
+
+### SSH Keys
+
+SSH Keys are not set on imported resources, such as Tasks configured to be executed on a remote host. Users will need to add a valid key to the importing appliance and update the Task to use that SSH Key.
+
+### Ansible Tower Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on Ansible Tower Tasks.
+
+### vRealize Orchestrator Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on vRO Tasks.
+
+### Option Lists
+
+Option lists need to be edited and saved prior to use in order to load any initial data sets that have been configured on the Option List.
+
+### Forms
+
+Input defaults that are ID-based will require manual correction after import. For example, if you have a Group Input which defaults to `GroupName:A(ID:2)`, when imported it will still be based off an ID value of 2. It’s highly likely that in the importing environment, a different Group will have an ID value of 2. A manual change to the correct ID value is required in the destination environment. Bear in mind that if you re-import a Form, you will also undo any manual changes you’ve made in the importing environment. Thus, if you update all defaults after importing, and then import once again, these manual default changes will be wiped out.
+
+Additionally, when Forms are using existing Inputs, those Inputs will be exported and imported for use in the destination environment. On import, HPE Morpheus Enterprise will add the needed Inputs unless the destination environment already has an Input with the same CODE value. This could give the appearance of creating duplicate Inputs if the destination environment happens to have an Input with the same name but a different code value. Users may wish to rename Inputs in the event they end up with more than one having the same name.
+
+### Tasks
+
+The user must ensure the presence of any dependency required by a Task. One example would be any Cypher keys being called by the Task. Add any required Cypher entries with identical keys or add compatible Cypher keys and update the Task configuration to utilize the updated Cypher mountpoints. Cypher is just one example, any other dependency required by the Task must be present. HPE Morpheus Enterprise does not parse the Task configuration to determine which dependencies are or are not present or required.
+
+### Icons and Images
+
+Icons which are set up on imported Instance Types will need to be manually uploaded to the appliance after import. They are not brought over as part of the import/export process.
+
+### Virtual Images
+
+When importing Node Types, the associated Virtual Image is mapped by its “Code” value. It is expected that a Virtual Image with the correct “Code” value already exists on the target appliance. If not, the Node Type will be imported without any Virtual Image attached. The user will then need to edit the Node Type and associate it with a compatible Virtual Image in order to become usable.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json b/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
new file mode 100644
index 0000000..303bdfc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+  "title": "HPE Bare Metal (BMaaS)",
+  "ordinal": 396,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Bare Metal (BMaaS)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md b/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
new file mode 100644
index 0000000..1d4ac23
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
@@ -0,0 +1,29 @@
+# HPE Bare Metal (BMaaS)
+
+HPE Bare-Metal-as-a-Service (BMaaS) for Morpheus Enterprise extends Morpheus hybrid cloud management capabilities to HPE ProLiant physical servers. This integration allows the Morpheus platform to discover, provision, and manage these servers as first-class resources. Additionally, HPE BMaaS Cloud integrates HPE ProLiant bare-metal infrastructure into cloud environments to enable cloud-based provisioning and lifecycle management.
+
+HPE BMaaS manages the end-to-end server lifecycle, including hardware discovery, bare-metal provisioning, operating system deployment, monitoring, and metering. The Morpheus interface centrally orchestrates these tasks. This unified approach enables organizations to manage physical infrastructure, virtual machines, and cloud resources using consistent workflows, policies, and governance controls.
+
+HPE BMaaS Cloud provides the following key capabilities:
+
+- **Automated Server Discovery**: Automatically imports and discovers HPE ProLiant servers.
+- **Bare-Metal Provisioning**: Provisions hardware using custom or pre-configured OS images.
+- **Comprehensive OS Deployment**: Deploys Windows and Linux with unattended installations and customizable boot parameters.
+- **Lifecycle Management**: Manages firmware and drivers using the HPE Service Pack for ProLiant (SPP).
+- **Flexible Networking**: Supports both unmanaged and managed network integrations.
+- **Metering and Billing**: Maps discovered hardware to service plans to align metering with billing.
+- **Logical Organization**: Organizes resources into Bare Metal Clouds and Resource Pools to support multi-site environments and scalable infrastructure segmentation.
+
+HPE BMaaS improves operational visibility and server lifecycle control. It offers a scalable, automated approach to manage physical infrastructure across both greenfield (new) and brownfield (existing) environments.
+
+**Subtopics**  
+
+- **[Supported Software Versions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html)**
+- **[Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html)**
+- **[Compute Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html)**
+- **[Network Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html)**
+- **[Storage Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html)**
+- **[Troubleshooting and Diagnostics](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html)**
+- **[Known Limitations and Operational Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..fd8ad2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 270,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..6f15530
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json b/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
new file mode 100644
index 0000000..479bb9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+  "title": "Reports",
+  "ordinal": 55,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html",
+  "topic_cluster": {
+    "clustering_title": "Reports",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md b/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
new file mode 100644
index 0000000..6e8d772
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
@@ -0,0 +1,87 @@
+# Reports
+
+## Overview
+
+HPE Morpheus Enterprise offers 28 different report types which are designed to slice up costing and usage across Clouds, Tenants, and more. Reports can be run on-demand as needed or can be scheduled to run on certain intervals to be viewed at a later time. The list of available report types can be viewed at Operations > Reports.
+
+![../_images/1reportList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF328552-F0CB-4A16-89DE-DD5E534DDA21-high.png)
+
+## Report Types
+
+### ACCOUNT INVENTORY
+
+- Tenant Inventory Summary
+
+### CLOUD USAGE
+
+- Cloud Usage
+- Cloud Usage App Summary
+- Cloud Usage Instance Type Summary
+- [Tenant Usage](https://docs.morpheusdata.com/en/latest/operations/report_types/tenant_usage.html)
+
+### CLOUD COST
+
+- Amazon Reservation Coverage
+- Amazon Reservation Utilization
+- Amazon Savings Inventory Summary
+- Amazon Savings Plan Coverage
+- Amazon Savings Plan Utilization
+- Application Cost
+- Cloud Cost
+- Group Cost
+- Instance Cost
+- Tenant Cost
+- Time Series Cost
+
+### INFRASTRUCTURE INVENTORY
+
+- Cloud Inventory Summary
+- Container Host Inventory Summary
+- Group Inventory Summary
+- Guidance
+- Hypervisor Inventory Summary
+- Migration Planning
+- Tenant Resource Allocation
+
+### PROVISIONING INVENTORY
+
+- Instance Inventory Summary
+- Software Inventory
+- Software Inventory By Server
+- Tag Compliance
+- Virtual Machine Inventory Summary
+- Workload Summary
+
+By clicking into a report type, users can see any previous runs and active report schedules. New on-demand runs and new schedules of the selected report type can be created, edited, or deleted from here. The next few sections go into creating, editing, scheduling, viewing, and deleting reports in greater detail.
+
+## Create Reports
+
+To create a new report, navigate to the report type list page (Operations > Reports). Click RUN NOW to the right of the specific report type to bring up the wizard to run that particular report. The required and optional fields to run the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/2reportExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-39F2C925-F3CB-4E65-B5A6-B5B515D2A1F6-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Once the report is run, it will be visible in the list of Instance Cost reports and all reports until deleted.
+
+## Schedule Reports
+
+In addition to running on-demand reports, HPE Morpheus Enterprise also allows reports to be scheduled. This allows you to save report configuration and have access to refreshed information on the schedule you need.
+
+The process of scheduling a report is nearly identical to running on on-demand. From the report type list page (Operations > Reports) click SCHEDULE to the right of the report type you wish to schedule. The required and optional fields to schedule the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/3scheduleExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF0ECE3F-331E-4BDF-9CF3-8DA3BAF19EFA-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Additionally, we select the time schedule on which this report should automatically run. Finally, we can opt to add a comma-separated list of email addresses which should receive an emailed link to the report each time the report is run.
+
+NOTE
+
+HPE Morpheus Enterprise includes three schedules by default: Date and Time (run once at the specified time), Daily at Midnight, and Weekly on Sunday at Midnight. Any other listed scheduling periods are user-configured execution schedules (Library > Automation > Execute Scheduling). Create a new execution schedule if none of the existing schedules work for your reporting needs.
+
+## Viewing Results
+
+A list of all report runs is viewable on the Results tab of the report types list page (Operations > Reports). To view the report itself, click on the hyperlinked report filters. Only reports that are ready for viewing will have an active hyperlink on their filters. In addition to report filters, the run date, report type, creating user, and run status are shown. Click on any of these headers to filter the report list by that column in either ascending or descending order. Any report can be deleted by clicking on the trash can icon at the end of its row.
+
+![../_images/4resultsList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CDD94D4F-361B-4237-B8FD-B88CCFCB6118-high.png)
+
+## Viewing Schedules
+
+A list of all scheduled report runs can be viewed in the Scheduled tab of the report types list page (Operations > Reports). The friendly name of the report schedule is displayed along with the report type, last run time, next run time, and success status of the previous run. Schedules can be edited or deleted by clicking on the pencil or trash can icon, respectively. We can also view the most recent run of a given schedule (if it was successful) by clicking on the hyperlinked “last run” value.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json b/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
new file mode 100644
index 0000000..ca22fc7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+  "title": "Remote Storage",
+  "ordinal": 439,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md b/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
new file mode 100644
index 0000000..2a2e324
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
@@ -0,0 +1,16 @@
+# Remote Storage
+
+Remote storage enables lifecycle management of volumes on supported **HPE Alletra storage arrays** (including **Alletra MP** and **Alletra 9000**, where supported) and allows compute instances to attach to or detach from those volumes. These operations can be performed during instance provisioning or post-provisioning through the reconfigure workflow. The currently supported transport protocol is **Fibre Channel**.
+
+To get started with using remote storage, first, the storage plugin for Alletra needs to be loaded, and a storage server added. This allows the user to specify the URL where the management interface of the storage array is available, along with the user credentials to manage the storage array.
+
+There is also a concept of a datastore, which is used to represent a container for a set of volumes. A datastore is associated with a storage server and also a resource pool. The resource pool is used to represent a site or a location, which is useful when storage HA is being used with datastores associated with different sites.
+
+## Adding HPE AlletraStorage Integration
+
+You can add the Allertra Storage plugin JAR using the Upload plugin method.
+
+**Subtopics**  
+
+- **[Creating a Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html)**
+- **[Creating a Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json b/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
new file mode 100644
index 0000000..e929f7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+  "title": "Price Sets",
+  "ordinal": 290,
+  "parent_title": "Plans",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html",
+  "topic_cluster": {
+    "clustering_title": "Price Sets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md b/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
new file mode 100644
index 0000000..ea3c08b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
@@ -0,0 +1,41 @@
+# Price Sets
+
+Price Sets combine Prices and then attach to Plans. Prices must be created prior to creating Price Sets, but it is recommended to review the Price Set Type options prior to creating Prices.
+
+Price Unit
+:   Select the Price Unit to use for the Price Set.
+
+    - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+    NOTE
+
+    Only Prices configured with matching Price Units can be used in a Price Set. “Month” is equivalent to 30 days by default. For AWS, month is 30.5 days. For Azure, month is 30.4 days.
+
+Type
+:   Price Set types determine which Prices are available to make up the set. This selection will filter the values returned in the Prices field at the bottom of the modal.
+
+    NOTE
+
+    It’s helpful to make note of the Prices options below before creating Price Sets.
+
+    - **Everything:** ‘Everything’ price sets require one or more ‘Everything’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Compute + Storage:** ‘Compute + Storage’ price sets require at least one of each ‘Memory’, CPU’, and ‘Disk Only’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Component:** ‘Component’ price sets require at least one of each ‘Memory’, ‘Cores’, ‘CPU’, and ‘Storage’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Load Balancer:** ‘Load Balancer’ price sets require at least one ‘Load Balancer’ price type and may include ‘Load Balancer Virtual Server’ price types. Load Balancer price sets are the only type which can be associated with Load Balancer Price Plans
+    - **Virtual Image:** ‘Virtual Image’ price sets require at least one ‘Storage’ price type. Virtual Image price sets are the only type which can be associated with Virtual Image Price plans
+    - **Snapshot:** ‘Snapshot’ price sets require at least one ‘Storage’ price type and may also include ‘Datastore’ price types. Snapshot price sets are the only type which can be associated with Snapshot Price plans
+    - **Software/Service:** ‘Software/Service’ Price Sets require at least one ‘Software/Service’ Price type
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
+
+Prices
+:   Search for and select Prices to be added to the Price Set. One of each Price Type required for the Price Set Type selected must be added for the Price Set to save.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json b/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
new file mode 100644
index 0000000..aac1a9a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+  "title": "Openstack",
+  "ordinal": 465,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md b/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
new file mode 100644
index 0000000..1fc31d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
@@ -0,0 +1,325 @@
+# Openstack
+
+## Overview
+
+Openstack is becoming a widely used on-premise infrastructure orchestration platform. It has a wide array of contributors and enterprise sponsorships. There are several variations on Openstack as well. HPE Morpheus Enterprise supports integration with all the various platform offerings and ranges in support all the way back to Openstack Juno. The complete list of compatible versions is listed in our [Integration Compatibility table](https://docs.morpheusdata.com/en/latest/release_notes/compatibility.html#integrations). It leverages the APIs and provides full functionality as a self service portal in front of Openstack.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups and Snapshots
+- Security Group Management
+- Disk Mode support Local/Image
+- Floating IP Assignment support
+- Brownfield VM management and Migration
+- Lifecycle Management and Resize
+- Docker Host management and configuration
+- Manila File Services (SFS)
+- Object Storage (OBS)
+- Network Lifecycle
+- LBaaS/Octavia Load Balancing Services
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to Openstack that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Image to QCOW2 Image Conversion
+- QCOW2 to RAW Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+- Instance Cloning
+- HPE Morpheus Enterprise Kubernetes Cluster Deployment
+
+TIP
+
+To allow Morpheus to list Hypervisor Hosts, ensure the Openstack user used for the Cloud Integration has sufficient privileges for `os_compute_api:os-hypervisors` in `/etc/nova/policy.json` in Openstack.
+
+NOTE
+
+CEPH is not supported in Morpheus 8.0.10 or higher.
+
+## Getting Started
+
+OpenStack Clouds are very easy to integrate with HPE Morpheus Enterprise. First, go to the Infrastructure  >  Clouds section and click + ADD. Select OpenStack to begin the integration process, most branded flavors of OpenStack will work with this Cloud selection as well.
+
+WARNING
+
+Support for OpenStack v2 Identity API has been removed in v5.3.3
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   v3 Identity endpoint.
+
+DOMAIN ID
+:   For Default domains, Default can be used. For other domain the Domain ID must be entered, not the Domain Name.
+
+PROJECT
+:   Enter the target project or leave this field blank to integrate all projects
+
+USERNAME
+:   Service Username
+
+PASSWORD
+:   Service user password
+
+OS VERSION
+:   Select Openstack Version. HPE Morpheus Enterprise supports the latest versions of OpenStack, select the latest version available if your current version is not shown.
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK Image Type
+
+LB TYPE
+:   Select LB Type for Openstack LB syncing and creation
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VM’s
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment. When disabled HPE Morpheus Enterprise will use ssh and rdp for console conneciton (vm/host credentials required)
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+NOTE
+
+v5.3.3 adds openstack project management which requires additional permissions in openstack:
+
+```
+```
+identity:list_domain_roles  
+identity:list_role_assignments  
+identity:list_roles  
+identity:list_projects  
+identity:create_project  
+identity:update_project  
+identity:delete_project  
+identity:create_grant  
+identity:revoke_grant
+```
+```
+
+Most of the information in the dialog can be acquired from the Openstack dashboard. under Project  >  Access & Security  >  API Access. The API URL that is needed is the one tied to Identity. The Domain and Project inputs typically correlate to the multitenant domain setup within Openstack (sometimes just left at default) as well as the project name given to instances. HPE Morpheus Enterprise allows multiple integrations to the same Openstack cluster to be scoped to various domains and projects as needed.
+
+The remaining options help HPE Morpheus Enterprise determine which API capabilities exist in the selected Openstack environment. Hence the need for the Openstack version and image format. If a newer Openstack cluster is being used then exists in the dropdown, simply select the most recent version in the dropdown and this should function sufficiently until the new version is added.
+
+TIP
+
+Some Openstack environments do not support QCOW2 and force RAW image formats (like Metapod). This is due to some network overhead in Ceph created by using QCOW2. HPE Morpheus Enterprise keeps two copies of Openstack image templates for this exact purpose.
+
+Saving this cloud integration should perform a verification step and close upon successful completion.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure > Compute > Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+## Service Ports
+
+HPE Morpheus Enterprise consumes the following OpenStack service ports by default as part of its cloud integration. If your OpenStack implementation has been configured to use alternate service ports, these can be overwritten in the Cloud configuration under the Service Endpoints section when adding or editing the Cloud integration.
+
+![../../../_images/serviceEndpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-533A8DF6-01D2-4189-A822-6565F7C5395D-high.png)
+
+### Default Service Ports
+
+- Identity: 5000
+- Compute: 8774
+- Image: 9292
+- Key Manager: 9311
+- Network: 9696
+- Volume API v3: 8776 v3
+- Manila: 8786
+
+## OpenStack Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Openstack Cloud includes the capability to work with Openstack Scalable File Service (SFS). SFS is shared file storage hosted on Openstack Cloud. By integrating HPE Morpheus Enterprise with Openstack you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Openstack Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Openstack Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+Additionally, Openstack SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click +ADD to begin and set the storage server type value to “Openstack SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/addSfs.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-948FDB48-9D25-4116-8FAF-DF9669B6F3E1-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to only file shares whose names match the search terms.
+
+We can drill into individual file shares by clicking on the hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking +ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+“Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Openstack SFS file shares can also be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking +ADD. Select the type “Openstack SFS Share”. Set the storage service field to a pre-existing Openstack SFS server. Setting a friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones is required.
+
+## Network and Router Creation
+
+Once an OpenStack Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “OpenStack Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select OpenStack Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select OpenStack Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OpenStack project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
+
+## Advanced
+
+There are a few advanced features when it comes to provisioning on top of Openstack. Most of these present themselves in the provisioning wizard. This includes OS Volume Type (Local or Volume) which dictates whether the main OS disk is copied and run off the hypervisor or remotely mounted as a volume via Glacier. Some Openstack setups only configure hypervisors with minimal local disks so volume type is needed.
+
+Another option during provisioning is “Assign Floating IP”. This option does exactly what it says and is similar to the feature on the Openstack instance dashboard itself. It should be noted that this will attempt to acquire a floating IP from the project and, if out of capacity, will attempt to increase capacity to the project if the cloud credentials provided have sufficient administrative privileges to do so.
+
+## Docker
+
+So far this document has covered how to add the Openstack cloud integration and has described how to provision virtual machine-based Instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to work with Docker containers and even support multiple containers per Docker host. To do this, a Docker host must first be provisioned into Openstack (multiple hosts are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host, navigate to Infrastructure > Clusters and click + ADD CLUSTER. Complete the provisioning wizard including selecting the appropriate Group and Cloud. Alternatively, you can navigate to the Clusters tab for a specific Cloud (Infrastructure > Clouds > Specific Cloud detail page > Clusterstab) and begin the process of provisioning a Docker host to that Cloud from there. Once completed, this host will show up in the Hosts sections (Infrastructure > HostsOR Infrastructure > Clouds > Specific Cloud detail page > Hoststab). HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones.
+
+Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, the HPE Morpheus Enterprise Agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json b/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
new file mode 100644
index 0000000..69c768c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md b/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
new file mode 100644
index 0000000..88a95a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
@@ -0,0 +1,11 @@
+# Getting Started
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html)**
+- **[Capacity and Planning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html)**
+- **[Installation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html)**
+- **[Upgrades & Maintenance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html)**
+- **[Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html)**
+- **[Initial Appliance Setup](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html)**
+- **[Core Functionality](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json b/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
new file mode 100644
index 0000000..2603567
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+  "title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 365,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md b/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
new file mode 100644
index 0000000..398af88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
@@ -0,0 +1,281 @@
+# Automated Multi-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. This is a companion guide to our [single-node application deployment guide](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.xml) and, in some cases, will refer directly to sections of that guide rather than duplicating information here.
+
+In this guide, we will create a custom App Blueprint for SuiteCRM consisting of a database node and an application node. Once configured, the provisioning process is completely automated (Provisioning > Apps) and results in the two-tiered app mentioned previously. We’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a multi-tiered application:
+
+- App Blueprints
+- Cypher
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. Additionally, while this could be done on many different Cloud types, I’m setting up this Instance Type for provisioning on a VMware vCenter Cloud. You would need to have a VMware Cloud already integrated with HPE Morpheus Enterprise in order to follow the guide exactly but I will not go through the process of creating new Clouds here. If you do not have a vCenter Cloud available to you, the concepts in the guide will translate to other Cloud types, including public clouds like Amazon AWS. You may have to make slight modifications in spots in order to make a fully working Instance Type for other Clouds.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. In this case, we need to store two Cypher secrets: The first is for the MySQL root password and the second is for the user which we will use to run SSH commands from the app server to the database server. Refer to the [single-node deployment guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-cypher) for details on setting up the first Cypher entry.
+
+Next we need to set up a Cypher for the SSH user so our application node can access the database. A handy trick here is to use the user specified in the HPE Morpheus Enterprise global Cloud-Init Setting as this will be automatically created on the Instances when they are provisioned by HPE Morpheus Enterprise. To check that the user is set up correctly, in the HPE Morpheus Enterprise UI go to Administration > Settings > Provisioning. Under the Cloud-Init Settings section, ensure that a username and password is set. After that, simply create a secret/cloudinit Cypher entry which stores the password for this user using the same process by which you set up the MySQL root password Cypher entry.
+
+## Create Inputs
+
+Inputs are custom input fields in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password. The steps to create these inputs have been detailed in the companion guide, if needed, you can reference them [here](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-inputs).
+
+## Create File Template and Library Template Task
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. We’ll also create a Task which we can use to automatically set our file template at the appropriate time during provisioning. The steps to create the [File Template](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-file-templates) and [Library Template Task](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks) are detailed in the companion guide so follow the links for walkthrough steps and return to this guide.
+
+## Create Database Install Task
+
+Since the database is installed on its own node, we need a Task which installs just database. In the prior section, we created a Library Template Task but this time we will create Bash Script Tasks to handle database node installation and application node installation. We’ll also need a simple third Task to restart the Apache service after setting the config file. We’ll go through the steps for creating all three of these Tasks in this section.
+
+Navigate to Library > Automation > Tasks and click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install db multi node
+- **Code:** suitecrminstalldbMN
+- **Type:** Shell Script (The proper fields will appear once the Type is set)
+- **Sudo:** Checked
+- **Source:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **Execute Target:** Resource
+
+### Database Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` != 0 ]  
+then  
+      sleep 120  
+fi  
+#Install MariaDB, start service and enable on boot  
+wget https://downloads.mariadb.com/MariaDB/mariadb_repo_setup  
+echo "fd3f41eefff54ce144c932100f9e0f9b1d181e0edd86a6f6b8f2a0212100c32c mariadb_repo_setup" | sha256sum -c -  
+chmod +x mariadb_repo_setup  
+./mariadb_repo_setup  --mariadb-server-version="mariadb-10.6"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enable mariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -u root -e "UPDATE mysql.user SET Password=PASSWORD('$RPass') WHERE User='root';"  
+mysql -u root -e "flush privileges"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass -e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.db WHERE Db='test' OR Db='test\_%';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Set bind-address parameter in my.cnf  
+sed -e '/^bind/s/^/#/g' -i /etc/mysql/mariadb.conf.d/50-server.cnf  
+systemctl restart mariadb.service
+```
+```
+
+## Create Application Install and Apache Restart Tasks
+
+We now need to create a Bash script task to install the application. However, before we do this, we need to consider how these Tasks will run. We need to have the database installed before the application. We can achieve this in our App Blueprint by configuring the boot order so that the database is provisioned before the application. However, as part of the database configuration, we also need to create a database user and set up remote access to the database for the application server IP. The challenge here is that we cannot create the database user as part of the database install Task as we will not know the application server IP address. To get around this, we will run the database configuration Tasks within the application install task using sshpass to remotely execute the MySQL commands on the database. This is where the cloud-init user and Cypher we created earlier come in.
+
+NOTE
+
+In the code section below, remember to set the correct username for your cloud-init user. In the code below it is set to pjonesci. You will also see in the Task below we are using environment variables to pull in the IP address of the database host (MYSQL\_HOST variable). We are able to do this because in the App Blueprint we will connect the tiers which means Instances in a tier can import the evars from Instances in connected tiers.
+
+Once again, click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install app multi node
+- **Code:** suitecrminstallappMN
+- **Type:** Shell Script
+- **Sudo:** Checked
+- **Source:** Local
+- **Execute Target:** Resource
+
+### Application Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+CIPass="<%=cypher.read('secret/cloudinit')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+MYSQL_HOST="<%=evars.SUITECRMDBMN_IP%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+        sleep 120  
+fi  
+#Install sshpass and apache, start service and enable on boot  
+apt-get install sshpass -y  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Use sshpass to remotely execute mysql commands on DB server to create database and database user  
+sshpass -p $CIPass ssh -o StrictHostKeyChecking=no -t pjonesci@$MYSQL_HOST <<REMOTE  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE USER '$SCRMUser'@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO $SCRMUser@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+REMOTE  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php7.3 libapache2-mod-php7.3 php7.3-common php7.3-mysql php7.3-gmp php7.3-curl php7.3-intl php7.3-mbstring php7.3-xmlrpc php7.3-gd php7.3-bcmath php7.3-imap php7.3-xml php7.3-cli php7.3-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+ sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" /etc/php/7.3/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+curl -sS https://getcomposer.org/installer | sudo php -- --version=1.10.9 --install-dir=/usr/local/bin --filename=composer  
+git clone https://github.com/salesagility/SuiteCRM.git /var/www/html/suitecrm  
+cd /var/www/html/suitecrm  
+composer install --no-dev  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+Finally, create the Apache restart Task mentioned earlier. The exact steps to create this Task are shown in the [companion single-node application guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks).
+
+## Create Workflows
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provision phase. One Workflow will primarily handle database node installation and the other will primarily handle application node installation.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRMDB - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install db multi node” Task
+
+![../../_images/dbwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AE350F66-EE19-401B-A0C9-EB946194C3F2-high.png)
+
+Click SAVE CHANGES and then create the second Workflow:
+
+- **NAME:** SuiteCRMApp - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install app multi node”, “suitecrm file template”, and “suitecrm apache restart” Tasks
+
+Click SAVE CHANGES
+
+![../../_images/appwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B02FA612-F552-422C-B489-354AB4074DE4-high.png)
+
+## Create Instance Types for the Database and Application
+
+At this point we’re ready to put our pieces together into custom Instance Types for the database and application. Instance Types can be provisioned individually (Provisioning > Instances) but in this case we want to structure multiple Instance Types into logical tiers in an App Blueprint so they can be provisioned as a HPE Morpheus Enterprise App. Each Instance Type will contain a Layout and a Node Type, I’ll discuss each construct more fully as it’s time to create them.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Set the following configurations:
+
+- **NAME:** SUITE\_CRM\_DB\_MN
+- **CODE:** suitecrmdbmn
+- **CATEGORY:** SQL
+- **ICON:** If desired, browse your local computer for a MariaDB icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMDBMN
+
+![../../_images/dbinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-992A3460-9FE9-4F5F-ABB2-FB8F13F0B3A9-high.png)
+
+Click SAVE CHANGES. With the Instance Type created, we’re ready to add a Layout. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** LO\_SUITE\_CRM\_DB\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **WORKFLOW:** Select the “SuiteCRM - Multi Node” Workflow that was previously created
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/dblo.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6BAE38A4-A27D-447A-86D1-01C6CF434D0E-high.png)
+
+Click SAVE CHANGES. With the Layout created, we’re ready to associated a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. In this case, we’re simply going to point to a default Ubuntu image which is supplied by HPE Morpheus Enterprise though you can associate Node Types with your own custom virtual images when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** NODE\_SUITE\_CRM\_DB\_MN
+- **SHORT NAME:** nodesuitecrmdbmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+Click SAVE CHANGES. This completes the database Library item needed to build out our App Blueprint in the next section. We now need to add a Library item representing the application node. Below I will list out the configurations for the Instance Type, Layout, and Node Type, you can refer back to the steps above if you need to see the click-by-click instructions once again for creating these objects.
+
+- **NAME:** SUITE\_CRM\_APP\_MN
+- **CODE:** suitecrmappmn
+- **CATEGORY:** Apps
+- **ICON:** If desired, browse your local computer for a SuiteCRM icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMAPPMN
+
+![../../_images/appinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D63BD45E-E0A9-4D0D-BAA2-2EFF77CC111B-high.png)
+
+- **NAME:** LO\_SUITE\_CRM\_APP\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4 GB (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/applo.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-29EF47D8-7883-4F20-8C82-6995D7CA784C-high.png)
+
+- **NAME:** NODE\_SUITE\_CRM\_APP\_MN
+- **SHORT NAME:** nodesuitecrmappmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+![../../_images/appnode.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0BBD1C18-2B48-489F-959F-214CD44CED21-high.png)
+
+## Create the App Blueprint
+
+We are now ready create a HPE Morpheus Enterprise App Blueprint. HPE Morpheus Enterprise Blueprints allow pre-configured multi-tier application deployments for multiple environments. In this example we will use the custom Instance Types previously created to build out an App Blueprint for a two-tier SuiteCRM application with the database running on one VM and the application running on another VM.
+
+Go to Library > Blueprints > App Blueprints and click + ADD. Enter a name for the Blueprint (SuiteCRM Multi Node) and set type to HPE Morpheus Enterprise. Click NEXT.
+
+You will now be in the App Blueprint configuration screen where you can build out the structure of the App Blueprint. In the structure section on the left of the screen, click the + to add App Tier and then click it again to add a Database tier.
+
+![../../_images/namebp.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4B83AA01-4C21-4B94-B440-4E5E0BE1A81A-high.png)
+
+Now that we have the tiers created, we can create the configuration for each tier. Click the “+”” next to the App tier and in the window that pops up select the application Instance Type created previously (SUITE\_CRM\_APP\_MN).
+
+![../../_images/setappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-53BFEE5F-524C-498F-8000-E746C992C738-high.png) ![../../_images/nameappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D440051E-3817-4EFA-BEEF-AE37834507C5-high.png)
+
+Now click the “+” next to the Suite CRM Instance Type (under App). Select the Group and Cloud required (I’m selecting my VMware Cloud, in this case) and then click ADD CONFIG.
+
+![../../_images/setappcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-78CEFAB6-9636-4B0D-AC7A-913583BD97C9-high.png)
+
+You will now have a configuration under the Suite CRM icon. Click on the configuration and it will appear in the right-hand pane of the window. Fill in the configuration required to provision the Instance. The locks to the right of the fields allow you to lock down entries so that they cannot be changed when provisioning the App later. Do not click COMPLETE yet, we still need to configure the database tier.
+
+![../../_images/configappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-81561E16-36A7-44E7-AB89-4D944C4C34A4-high.png)
+
+Back in the left-hand pane, click the “+” next to Database and perform the same steps as before to add in the SUITE\_CRM\_DB\_MN Instance Type to the database tier. Add in the required configuration.
+
+![../../_images/configdbins.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0D8D8FF1-9617-4369-B1DF-B49DE4993A26-high.png)
+
+Once the configuration is set up for both tiers, we need to set the boot order and connect the tiers. The boot order is used to control the order in which the tiers are built. We want the database tier to build first, so we set the boot order to 0 on the database and 1 on the application. We also need to connect the tiers by checking the box under connected tiers.
+
+![../../_images/dbbootorder.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5C12EFCD-2D25-427F-AE41-752B282FF1C1-high.png)
+
+Save the App Blueprint by clicking COMPLETE.
+
+## Deploy the App Blueprint
+
+To deploy an App Blueprint, navigate to Provisioning > Apps and click + ADD. Select the App Blueprint we just created and work through the provisioning wizard, including naming the App and selecting the target Cloud.
+
+NOTE
+
+For the database hostname, specify the internal IP address of the database node
+
+![../../_images/app1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CA2843B6-3893-49B7-97B7-3236C92974E1-high.png) ![../../_images/app2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-11B85356-456E-453E-819A-E1848F22A86E-high.png) ![../../_images/app3.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-90155AD7-21F3-4243-BE6B-DE3205678495-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_APP\_NODE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json b/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
new file mode 100644
index 0000000..8954eaf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+  "title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+  "ordinal": 428,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html",
+  "topic_cluster": {
+    "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md b/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
new file mode 100644
index 0000000..cfb5f18
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
@@ -0,0 +1,33 @@
+# Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure
+
+After applying an HPE Service Pack for ProLiant (SPP) on Gen11 and Gen12 servers, a full cold power cycle is required to ensure proper initialization of updated firmware components.
+
+An iLO reset or standard operating system reboot is not sufficient after an SPP update.
+
+Failure to perform a cold power cycle may result in:
+
+- Inconsistent Redfish storage inventory
+- Smart Array controller desynchronization
+- Missing or stale drive objects
+- Management platform initialization failures
+- Incomplete firmware activation
+
+Perform the following steps for cold power cycle:
+
+1. **Power OFF the server**:Shut down gracefully through the operating system or iLO interface. Confirm the server is completely powered off.
+2. **Disconnect AC Power**: Physically remove all power cables from the server power supplies.
+3. **Wait for 60 Seconds**: Allow sufficient time for residual power to drain. This clears controller cache and resets hardware state.
+4. **Reconnect Power**: Reattach all power cables securely.
+5. **Power ON the Server**: Boot the system normally.
+
+A full AC power removal forces:
+
+- Smart Array controller re-enumeration
+- PCI bus reinitialization
+- Storage firmware reload
+- Redfish object tree regeneration
+- Hardware state synchronization
+
+This process resolves the majority of post-SPP Redfish storage inconsistencies observed on Gen11 and Gen12 platforms.
+
+HPE strongly recommends performing a full cold power cycle after major firmware bundle updates to ensure all updated components are fully initialized.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json b/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
new file mode 100644
index 0000000..1b95bd4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+  "title": "Resource Center",
+  "ordinal": 528,
+  "parent_title": null,
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3CEB493A-1086-4AE2-8220-93B372329509.html",
+  "topic_cluster": {
+    "clustering_title": "Resource Center",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md b/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
new file mode 100644
index 0000000..df78ca3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
@@ -0,0 +1,5 @@
+# Resource Center
+
+- [Developer Zone](https://developer.morpheusdata.com/)
+- [Support KnowledgeBase](https://support.morpheusdata.com/s/knowledge-base?language=en_US)
+- [White Papers](https://www.morpheusdata.com/resource-center)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json b/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
new file mode 100644
index 0000000..bc4a554
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+  "title": "F5 Load Balancers",
+  "ordinal": 499,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html",
+  "topic_cluster": {
+    "clustering_title": "F5 Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md b/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
new file mode 100644
index 0000000..ec1af30
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
@@ -0,0 +1,139 @@
+# F5 Load Balancers
+
+## Virtual Servers
+
+Instances attached to an F5 will be listed in the Virtual servers tab. Virtual servers can also be manually added in this section.
+
+### Add Virtual Server
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers
+2. Select F5 Integration name to drill into the detail page
+3. Select + ADD in the VIRTUAL SERVERS tab
+4. Fill in the following: 
+
+   - NAME
+     :   Name of the Virtual Server in HPE Morpheus Enterprise
+   - DESCRIPTION
+     :   Description of the Virtual Server in HPE Morpheus Enterprise
+   - Enabled
+     :   Uncheck to keep the configuration but disable F5 availability in HPE Morpheus Enterprise
+   - VIP TYPE
+     :   - Standard
+         - Forwarding (Layer 2)
+         - Forwarding (IP)
+         - Performance (HTTP)
+         - Performance (Layer 4)
+         - Stateless
+         - Reject
+         - DHCP
+         - Internal
+         - Message Routing
+   - VIP HOSTNAME
+     :   Enter Hostname of the VIP (optional)
+   - VIP ADDRESS
+     :   Enter IP address for the VIP
+   - VIP PORT
+     :   Enter post used for the VIP
+   - SOURCE ADDRESS
+     :   Enter Virtual Server source address
+   - PROTOCOL
+     :   tcp, udp, or sctp
+   - PROFILES Search for and select from available PROFILES
+   - POLICIES
+     :   Search for and select from available POLICIES
+   - IRULES
+     :   Search for and select from available RUEL SCRIPTS
+   - PERSISTENCE
+     :   - cookie
+         - dest-addr
+         - global-settings
+         - hash
+         - msrdp
+         - sip
+         - source-addr
+         - ssl
+         - universal
+   - DEFAULT POOL
+     :   Select from available POOLS
+5. Select SAVE CHANGES
+
+## Policies
+
+Policies will be synced and listed in the Policies tab. These policies will be available options when creating Virtual Servers.
+
+## Pools
+
+### Create Pool
+
+NAME
+:   Name of the POOL in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the POOL in HPE Morpheus Enterprise
+
+BALANCE MODE
+:   - Round Robin
+    - Least Connections
+
+SERVICE PORT
+:   Specify SERVICE PORT for the POOL
+
+MEMBERS
+:   Search for and select from available NODES
+
+MONITORS
+:   Search for and select from available Monitors
+
+## Profiles
+
+SSL Profiles are synced and and will be created when an SSL Certificate is assigned in the Load balancer section when provisioning or editing a Load balancer on an Instance.
+
+## Monitors
+
+### Create Monitor
+
+NAME
+:   Name of the MONITOR in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the MONITOR in HPE Morpheus Enterprise
+
+PARENT MONITOR
+:   Select from available MONITORS
+
+DESTINATION
+:   Specify Destination, such a `*:443`. Default is `*:*`
+
+INTERVAL
+:   Specify Monitor Interval. Default is `5`
+
+TIMEOUT
+:   Specify Monitor Timeout. Default is `15`
+
+MONITOR CONFIG
+:   Enter monitor config.
+
+## Nodes
+
+### Create Node
+
+NAME
+:   Name of the NODE in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the NODE in HPE Morpheus Enterprise
+
+ADDRESS
+:   Enter node address
+
+MONITOR
+:   Select from available MONITORS
+
+SERVICE PORT
+:   Specify SERVICE PORT for the NODE
+
+## Rule Scripts
+
+Rule Scripts will be synced and listed in the RULE SCRIPTS tab. These rules will be available options when creating Virtual Servers.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json b/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
new file mode 100644
index 0000000..e1d55f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 184,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md b/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
new file mode 100644
index 0000000..ea41964
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
@@ -0,0 +1,11 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+![../../_images/managePlacement.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-496FBC66-FFC3-4D76-B3D1-F0E4F31A838D-high.png)
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json b/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
new file mode 100644
index 0000000..d01355a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+  "title": "Forms",
+  "ordinal": 153,
+  "parent_title": "Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html",
+  "topic_cluster": {
+    "clustering_title": "Forms",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md b/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
new file mode 100644
index 0000000..094fdb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
@@ -0,0 +1,163 @@
+# Forms
+
+Forms are designed to be used with [Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items). Using the provided tools, build forms to provide the appropriate customization fields for endusers in the Provisioning Catalog. Catalog Items can also be built using HPE Morpheus Enterprise Inputs but Forms provide unique capabilities that open up additional functionality and simplify the process. Once a Form is created it is then available to be associated with a Catalog Item. This section discusses the creation of Forms, the available options, and how they can be used effectively to create Catalog Items.
+
+## Creating a New Form
+
+To begin a new Form, navigate to Library > Options > Forms and click + ADD.
+
+![../../_images/newForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-79EB5F32-18B1-4437-9727-EA6FEC436A5C-high.png)
+
+## Adding Field Groups
+
+Field Groups are logical groupings of Input fields on your Form. Especially with larger forms, they make the Form easier to read and use. You can even collapse down sections of less commonly needed Inputs to keep your Forms clean. By default a new Form has no Field Groups but one can be added by clicking “+ ADD FIELD GROUP” in the center of the NEW FORM modal (which can be seen in the screenshot above). Field Groups can accept the following options:
+
+- **NAME:** The name and label for the Field Group
+- **DESCRIPTION:** And optional description for the Field Group
+- **COLLAPSIBLE:** When marked, the user can collapse (hide) or show the Field Group
+- **COLLAPSIBLE BY DEFAULT:** If the Field Group is marked collapsible, this option will appear to make the Field Group shown (unchecked) or hidden (checked) by default
+- **VISIBILITY FIELD:** Enter the fieldName of another Input and this Field Group will appear only when that Input has a value
+
+![../../_images/newFieldGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-07A59B83-A70F-407E-83F5-B6ABCB054D52-high.png)
+
+## Adding Inputs
+
+Inputs are the Form options themselves and can take various forms, such as text fields, checkboxes, select lists or other custom forms. Inputs can be added outside of any created Field Groups or they may be added within them. Click + ADD INPUT within the desired area (inside a Field Group or outside of them).
+
+When adding Inputs, you may add any Input (Library > Options > Inputs) that is pre-existing to your form. Set “USE EXISTING” to “Yes” and make the selection from the “EXISTING OPTION TYPE” typeahead field. Once selected, you’ll notice that all other settings cannot be edited. If needed, edit this Input within the Inputs section (Library > Options > Inputs).
+
+![../../_images/existingInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-25AEAFA2-3766-4411-9796-FCCD26396206-high.png)
+
+When adding Inputs, you may also create new Inputs within the Form builder. Some available types are no different than other Inputs you might make in the Input section (Library > Options > Inputs) but other types are unique to Forms. To create a new Input, set “USE EXISTING” to “No” and select the desired type.
+
+Input types are organized by categories. Inputs in the basic category are primarily the same types of Inputs that can be made in the Inputs section (Library > Options > Inputs). These include text fields, select lists, checkbox arrays, numerical inputs, and more. You can read more about the basic Input types in HPE Morpheus Enterprise [Input documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#inputs).
+
+Inputs in the Advanced and Provisioning categories are unique to Forms and require additional explanation. Advanced inputs are similar to basic but provide some sort of data manipulation capability or have a specific targeted function. See the list of advanced Input types below:
+
+- **Byte Size:** Allows numerical disk or storage size values to be given with selectable units (MB, GB, etc.). When a value is input and the unit is changed, the same value will be automatically computed into the new unit amount (1 GB > 1024MB, for example). Users may select which unit is initially loaded by default.
+- **Code Editor:** Gives the user a code editor field. Set a language or markdown format in the “HIGHLIGHTING” field to enable automatic syntax highlighting and spacing for the user. For example, the user could enter a provisioning shell script for their workload or provide a custom JSON payload at provision time (complete with syntax highlighting for easy entry).
+- **File Content:** Access file content either locally entered or sourced from an integrated repository or outside URL
+- **Icon Picker:** Allows the user to select an icon for their workload at provision time. The user may select from previously uploaded icons, upload their own, or use the built-in icon generator tool to create a unique icon right in the Form
+- **Key Value:** Allows the user to enter as many key/value pairs as they’d like which can be onboarded into the workload config at provision time
+- **Text Array:** Allows the user to enter multiple values separated by a delimiter of your choosing. HPE Morpheus Enterprise will parse out the entered values which can be individually deleted if desired before the form is submitted
+- **Typeahead:** Similar to Select List, especially for very long lists. Search for the desired value by typing the first few letters as a search parameter. Users may also browse the complete list by clicking the dropdown icon. This Input type can also support multiple selections, if needed. Associate this type of Input with a pre-defined Option List or create a new Option List right inside the Form builder
+
+![../../_images/forms1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E413A285-DAE5-4097-ABD7-5503BDA5B518-high.png)
+
+Inputs in the provisioning category are specifically tied to some provisioning construct in HPE Morpheus Enterprise (Groups, Clouds, etc.). They’re very useful for allowing users to select specific provisioning constructs, such as the Group, Cloud, Layout, or Network they wish to provision, and can automatically inject the user’s selection into the Catalog Item. This makes for much simpler Catalog Item development as compared to setting up the configuration using just the Input construct outside of Forms.
+
+Provisioning Inputs also include relevant reload and filtering behaviors by default. For example, your Cloud Input field will automatically reload after making a Group selection or your Layout Input field will automatically reload after setting a Group, Cloud, and Instance Type. This makes it very easy to create flexible Catalog Item forms that are useful across Clouds.
+
+The following provisioning Input types are supported, each with their own automatic filtering behavior and auto-inject capability into the Catalog Item spec:
+
+- Cloud
+- Disks
+- Exposed Ports
+- Group
+- Layout
+- Networks
+- Plan
+- Resource Pool
+- Security Groups
+- Tags
+- Vmw Folders
+
+![../../_images/forms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-186CA89B-1E7C-49B9-9C71-3CD0CE4E9A59-high.png)
+
+In order for provisioning Inputs to work properly, be sure to properly set the fields they should filter against. In the screenshot below you can see for a Resource Pool Input I’ve set the Group, Cloud, Layout, and Plan Inputs that it must be filtered against in order to work. Search for the Field Label of the target Input.
+
+![../../_images/poolFilters.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8E7A4B9B-FC72-4F3D-9EB8-6625130B3DA4-high.png)
+
+Once the type selected, the new Input will have many configuration options, most of which are the same options available when creating an Input from the Inputs section though some are new and some are presented in slightly different ways. The available options depend on the Input type selected but common options are shown in the expandable section below:
+
+### Common Input Configuration Options
+
+FIELD LABEL
+:   The name and label of the Input
+
+LOCALIZED LABEL
+:   If a localization code is selected, this field will have a translated label relative to the localization language selected for the appliance or user
+
+FIELD NAME
+:   This is the Input fieldName property used to resolve the field value into code or to refer to this field for creating dynamic relationships with other Input fields
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+LOCALIZED HELP BLOCK
+:   If a localization code is selected, this field will have a translated help block relative to the localization language selected for the appliance or user
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+LOCKED
+:   The Input field is visible but locked from being edited by the user. Any configured default values will be seen and set on the Instance but the user may not change the value
+
+HIDDEN
+:   Hides the field from view. The field is still active, however, and any configured default value would still be set
+
+EXCLUDE FROM SEARCH
+:   For Select List and Typeahead Inputs, check to exclude the form data from being stored as variables (which can be leveraged from an API call when needed)
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+ALLOW MULTIPLE SELECTIONS
+:   For certain Input types which support multiple selections (Select List and Typeahead, for example), check to allow multiple items to be selected
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+A complete example form making use of provisioning Inputs and Field Groups is shown below:
+
+![../../_images/completeForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B953106A-64A3-4A8C-9BA9-428AE4A26C8A-high.png)
+
+## Using Localized Labels on Form Fields
+
+In creating a Form Input, you may enter a custom static text label by setting the FIELD LABEL attribute on the Input. Using this will set a label for your Form field which will appear the same for all users. Alternatively, you can set a dynamic text label by selecting an entry from the LOCALIZED LABEL typeahead field. By setting a Localized Label, the label will appear differently depending on the user’s web browser language localization setting, the HPE Morpheus Enterprise appliance localization setting (set in the [global settings area](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html)), or the user’s own localization setting from within the [User Settings section](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html). More specific localization settings (such as a user’s setting over the appliance-wide setting) override less specific settings.
+
+As an example, I’ll create a simple Form which has only a Group-type Input. Both the Field Label and Localized Label fields have been filled but the Localized Label takes precedence. Based on the localization settings for the user creating this Form, we see the label presented in US English as “GROUP.”
+
+![../../_images/buildForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2A54A030-6474-4ACB-B3A2-8E428EBF215E-high.png)
+
+If we then navigate to provision a Catalog Item based on this Form, we still see the US English “GROUP” field label as this specific user has a default localization of “English (United States)” in its User Settings menu.
+
+![../../_images/english.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F11BC817-1A85-4274-A47B-D401E36D4BDB-high.png)
+
+However, if we select a different user which has a default localization of “French,” and go to provision the same Catalog Item, the field label is shown in French.
+
+![../../_images/french.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-40BAFA08-1439-49F9-B642-C7C3FAED943F-high.png)
+
+HPE Morpheus Enterprise has several complete language packs and also allows users to contribute to new or in-progress language packs. If interested in creating or contributing to UI translations, take a look at [this YouTube video](https://www.youtube.com/watch?v=oX25kutg8vU).
+
+## Turning Forms into Catalog Items
+
+Once created, Forms can be associated with Catalog Items in the same way individual Inputs could before Forms were added. Add a new Catalog Items (or edit an existing one) in Library > Blueprints > Catalog Items. For complete details, refer to documentation on [creating Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#building-catalog-instances).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json b/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
new file mode 100644
index 0000000..a99354b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+  "title": "Variables",
+  "ordinal": 166,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html",
+  "topic_cluster": {
+    "clustering_title": "Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md b/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
new file mode 100644
index 0000000..ac4d853
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
@@ -0,0 +1,1373 @@
+# Variables
+
+A vast number of variables are available for use in Tasks, Scripts, Templates, Resource Names, Cloud-Init User Data and Option List configs.
+
+IMPORTANT
+
+Variables are case sensitive
+
+## Pre-Provision Vars
+
+A subset of variables are available for Instance, Host Name and Hostnames. These can be passed inside `${ }` blocks during provisioning or in relevant policy configs. Groovy syntax can be resolved to allow for dynamic name generation as shown in some of the examples below.
+
+Instance Naming Policy example: `${userInitials}-${cloudCode}-${platform == 'windows' ? 'W' : 'L'}-${sequence}`
+
+Available variables for Naming Policy naming patterns include:
+
+```
+```
+${account}  
+${accountId}  
+${accountName}  
+${accountNumber}  
+${accountType}  
+${cloudCode}  
+${cloudName}  
+${customerNumber}  
+${customOptions.fieldName}  
+${groupCode}  
+${groupName}  
+${instance.instanceContext} # Environment Code  
+${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+${platform}  
+${provisionType}  
+${sequence} # results in 1  
+${sequence+100} # results in 101  
+${sequence.toString().padLeft(5,'0')} # results in 00001  
+${tenantId}  
+${tenant} # Tenant Name  
+${tenantSubdomain}  
+${type}  
+${userId}  
+${userInitials}  
+${username}
+```
+```
+
+An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+NOTE
+
+It’s not recommended that users include “>”, “<”, “%”, “$”, or “=” in naming policies.
+
+## Syntax Examples
+
+PowerShell Example: `$app_id = "<%= instance.metadata.app_id %>"`
+
+Bash Example: `HOSTNAME="<%= container.server.hostname %>"`
+
+Python Example: `hostname = morpheus['server']['hostname']`
+
+HTTP Body Example: `{"name": "<%= instance.createdByUsername %>"}`
+
+![../_images/Metadata-Enviornment-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-14CAAF3E-4218-42AA-9D8B-8511E2C5E913-high.png) ![../_images/Tags-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B9FCD0BE-6651-4DA3-BC61-3AB7E704065C-high.png)
+
+NOTE
+
+customOptions values are defined from custom Inputs.
+
+## Common Examples
+
+```
+```
+                  container.configGroup: <%=container.configGroup%>  
+                  container.configId: <%=container.configId%>  
+                  container.configPath: <%=container.configPath%>  
+                  container.configRole: <%=container.configRole%>  
+                  container.containerTypeCode: <%=container.containerTypeCode%>  
+                  container.containerTypeName: <%=container.containerTypeName%>  
+                  container.containerTypeShortName: <%=container.containerTypeShortName%>  
+                  container.cores: <%=container.cores%>  
+                  container.dataPath: <%=container.dataPath%>  
+                  container.dateCreated: <%=container.dateCreated%>  
+                  container.domainName: <%=container.domainName%>  
+                  container.environmentPrefix: <%=container.environmentPrefix%>  
+                  container.externalIp: <%=container.externalIp%>  
+                  container.hostMountPoint: <%=container.hostMountPoint%>  
+                  container.hostname: <%=container.hostname%>  
+                  container.image: <%=container.image%>  
+                  container.internalHostname: <%=container.internalHostname%>  
+                  container.internalIp: <%=container.internalIp%>  
+                  container.logsPath: <%=container.logsPath%>  
+                  container.memory: <%=container.memory%>  
+                  container.planCode: <%=container.planCode%>  
+                  container.provisionType: <%=container.provisionType%>  
+                  container.server: <%=container.server.serverTypeName%>  
+                  container.serverId: <%=container.serverId%>  
+                  container.sshHost: <%=container.sshHost%>  
+                  container.status: <%=container.status%>  
+                  container.storage: <%=container.storage%>  
+                  container.version: <%=container.version%>  
+                  customOptions: <%=customOptions.fieldName%>  
+                  accountNumber: <%= accountNumber %> #resource tenant account number  
+                  customerNumber: <%= customerNumber %> #resource tenant customer number  
+                  accountName: <%= accountName %> # resource tenant account name  
+                  taskOwner.accountNumber: <%= taskOwner.accountNumber %> #task owner tenant account number  
+                  taskOwner.customerNumber: <%= taskOwner.customerNumber %>  
+                  taskOwner.accountName: <%= taskOwner.accountName %>  
+                  user.accountNumber: <%= user.accountNumber %> #user executing task tenant account number  
+                  user.customerNumber: <%= user.customerNumber %>  
+                  user.accountName: <%= user.accountName %>  
+                  evar: <%=evars.name%>  
+                  evars: <%=evars%>  
+                  group.code: <%=group.code%>  
+                  group.datacenterId: <%=group.datacenterId%>  
+                  group.location: <%=group.location%>  
+                  group.name: <%=group.name%>  
+                  instance.autoScale: <%=instance.autoScale%>  
+                  instance.configGroup: <%=instance.configGroup%>  
+                  instance.configId: <%=instance.configId%>  
+                  instance.configRole: <%=instance.configRole%>  
+                  instance.containers[0]: <%=instance.containers[0].containerTypeName%>  
+                  instance.cores: <%=instance.cores%>  
+                  instance.createdByEmail: <%=instance.createdByEmail%>  
+                  instance.createdByFirstName: <%=instance.createdByFirstName%>  
+                  instance.createdById: <%=instance.createdById%>  
+                  instance.createdByLastName: <%=instance.createdByLastName%>  
+                  instance.createdBYUsername: <%=instance.createdByUsername%>  
+                  instance.deployGroup: <%=instance.deployGroup%>  
+                  instance.description: <%=instance.description%>  
+                  instance.displayName: <%=instance.displayName%>  
+                  instance.domainName: <%=instance.domainName%>  
+                  instance.environmentPrefix: <%=instance.environmentPrefix%>  
+                  instance.expireDate: <%=instance.expireDate%>  
+                  instance.firewallEnabled: <%=instance.firewallEnabled%>  
+                  instance.hostname: <%=instance.hostname%>  
+                  instance.instanceContext: <%=instance.instanceContext%> (tip: instanceContext = Environment)  
+                  instance.instanceLevel: <%=instance.instanceLevel%>  
+                  instance.instanceTypeCode: <%=instance.instanceTypeCode%>  
+                  instance.instanceTypeName: <%=instance.instanceTypeName%>  
+                  instance.instanceVersion: <%=instance.instanceVersion%>  
+                  instance.memory: <%=instance.memory%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.name: <%=instance.name%>  
+                  instance.networkLevel: <%=instance.networkLevel%>  
+                  instance.plan: <%=instance.plan%>  
+                  instance.provisionType: <%=instance.provisionType%>  
+                  instance.status: <%=instance.status%>  
+                  instance.statusMessage: <%=instance.statusMessage%>  
+                  instance.storage: <%=instance.storage%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.userStatus: <%=instance.userStatus%>  
+                  server.agentInstalled: <%=server.agentInstalled%>  
+                  server.agentVersion: <%=server.agentVersion%>  
+                  server.apiKey: <%=server.apiKey%>  
+                  server.category: <%=server.category%>  
+                  server.commType: <%=server.commType%>  
+                  server.configGroup: <%=server.configGroup%>  
+                  server.configId: <%=server.configId%>  
+                  server.configRole: <%=server.configRole%>  
+                  server.consoleHost: <%=server.consoleHost%>  
+                  server.consolePort: <%=server.consolePort%>  
+                  server.consoleType: <%=server.consoleType%>  
+                  server.consoleUsername: <%=server.consoleUsername%>  
+                  server.dataDevice: <%=server.dataDevice%>  
+                  server.dateCreated: <%=server.dateCreated%>  
+                  server.description: <%=server.description%>  
+                  server.displayName: <%=server.displayName%>  
+                  server.domainName: <%=server.domainName%>  
+                  server.externalId: <%=server.externalId%>  
+                  server.externalIp: <%=server.externalIp%>  
+                  server.fqdn: <%=server.fqdn%>  
+                  server.hostname: <%=server.hostname%>  
+                  server.internalId: <%=server.internalId%>  
+                  server.internalIp: <%=server.internalIp%>  
+                  server.internalName: <%=server.internalName%>  
+                  server.internalSshUsername: <%=server.internalSshUsername%>  
+                  server.lastAgentUpdate: <%=server.lastAgentUpdate%>  
+                  server.lvmEnabled: <%=server.lvmEnabled%>  
+                  server.macAddress: <%=server.macAddress%>  
+                  server.managed: <%=server.managed%>  
+                  server.maxCores: <%=server.maxCores%>  
+                  server.maxMemory: <%=server.maxMemory%>  
+                  server.maxStorage: <%=server.maxStorage%>  
+                  server.name: <%=server.name%>  
+                  server.nodePackageVersion: <%=server.nodePackageVersion%>  
+                  server.osDevice: <%=server.osDevice%>  
+                  server.osType: <%=server.osType%>  
+                  server.osTypeCode: <%=server.osTypeCode%>  
+                  server.parentServerId: <%=server.parentServerId%>  
+                  server.plan: <%=server.plan%>  
+                  server.platform: <%=server.platform%>  
+                  server.platformVersion: <%=server.platformVersion%>  
+                  server.powerState: <%=server.powerState%>  
+                  server.serialNumber: <%=server.serialNumber%>  
+                  server.serverModel: <%=server.serverModel%>  
+                  server.serverType: <%=server.serverType%>  
+                  server.serverTypeCode: <%=server.serverTypeCode%>  
+                  server.serverTypeName: <%=server.serverTypeName%>  
+                  server.serverVendor: <%=server.serverVendor%>  
+                  server.softwareRaid: <%=server.softwareRaid%>  
+                  server.sourceImageId: <%=server.sourceImageId%>  
+                  server.sshHost: <%=server.sshHost%>  
+                  server.sshPort: <%=server.sshPort%>  
+                  server.sshUsername: <%=server.sshUsername%>  
+                  server.status: <%=server.status%>  
+                  server.statusMessage: <%=server.statusMessage%>  
+                  server.tags: <%=server.tags%>  
+                  server.toolsInstalled: <%=server.toolsInstalled%>  
+                  server.visibility: <%=server.visibility%>  
+                  task.results (using task code): <%=results.taskCode%>  
+                  task.results (using task name): <%=results["Task Name"]%>  
+                  task.results.value: <%=results.taskCode.key%>  
+                  zone.agentMode: <%=zone.agentMode%>  
+                  zone.cloudTypeCode: <%=zone.cloudTypeCode%>  
+                  zone.cloudTypeName: <%=zone.cloudTypeName%>  
+                  zone.code: <%=zone.code%>  
+                  zone.domainName: <%=zone.domainName%>  
+                  zone.firewallEnabled: <%=zone.firewallEnabled%>  
+                  zone.location: <%=zone.location%>  
+                  zone.name: <%=zone.name%>  
+                  zone.regionCode: <%=zone.regionCode%>  
+                  zone.scalePriority: <%=zone.scalePriority%>  
+                  cypher: <%=cypher.read('secret/hello')%>  
+cypher: <%=cypher.read('secret/' + zone.code)%> # Make variables more dynamic based off other variables
+```
+```
+
+## Instance
+
+```
+```
+instance {  
+        adminPassword,  
+        adminUsername,  
+        apps.[],  
+        assignedDomainName,  
+        autoScale,  
+        backup.{},  
+        configGroup,  
+        configId,  
+        configRole,  
+        container.{},  
+        containers.[],  
+        cores,  
+        createBackup,  true/false  
+        createdByEmail,  
+        createdByFirstName,  
+        createdById,  
+        createdByLastName,  
+        createdByUser.{  
+                 username,  
+                 displayName,  
+                 firstName,  
+                 lastName,  
+                 email,  
+                 linuxUsername,  
+                 windowsUsername  
+        },  
+        createdByUsername,  
+        createUser, # true/false  
+        customOptions,  
+        deployGroup,  
+        description,  
+        displayName,  
+        domainName,  
+        environmentPrefix,  
+        evars:{},  
+        expireDate, # YYYY-MM-DD-T00:00:00Z  
+        expireDays,  
+        expose.[],  
+        firewallEnabled:true/false,  
+        hostId,  
+        hostname,  
+        id,  
+        instanceContext,  
+        instanceLevel,  
+        instanceTypeCode,  
+        instanceTypeName,  
+        instanceVersion,  
+        isEC2:true/false,  
+        isVpcSelectable, # true/false  
+        layoutCode,  
+        layoutId,  
+        layoutName,  
+        layoutSize,  
+        lbInstances.[],  
+        memory(bytes),  
+        memoryDisplay, #MB/GB  
+        metadata.{},  
+        name,  
+        nestedVirtualization,  
+        networkLevel,  
+        noAgent,  
+        plan,  
+        poolProviderType,  
+        ports,  
+        provisionType,  
+        resourcePoolId,  
+        scheduleStatus,  
+        servicePassword,  
+        serviceUsername,  
+        smbiosAssetTag,  
+        sslCertId,  
+        sslEnabled, # true/false  
+        status,  
+        statusMessage,  
+        storage, # bytes  
+        tags,  
+        userStatus,  
+        vmwareFolderId,  
+}
+```
+```
+
+## Container
+
+```
+```
+container {  
+        configGroup,  
+        configId,  
+        configPath,  
+        configRole,  
+        containerTypeCode,  
+        containerTypeShortName,  
+        cores,  
+        dataPath,  
+        dateCreated,  
+        domainName,  
+        environmentPrefix,  
+        externalIp,  
+        hostMountPoint,  
+        hostname,  
+        image,  
+        internalHostname,  
+        internalIp,  
+        logsPath,  
+        memory,  
+        planCode,  
+        provisionType,  
+        server:{},  
+        serverId,  
+        sshHost,  
+        status,  
+        storage,  
+        version,  
+        containerTypeName  
+}
+```
+```
+
+## Server
+
+```
+```
+server {  
+        agentInstalled,  
+        agentVersion,  
+        apiKey,  
+        category,  
+        commType,  
+        configGroup,  
+        configId,  
+        configRole  
+        consoleHost,  
+        consolePort,  
+        consoleType,  
+        consoleUsername,  
+        dataDevice,  
+        dateCreated,  
+        description,  
+        displayName,  
+        domainName,  
+        externalId,  
+        externalIp,  
+        fqdn,  
+        hostname,  
+        internalId,  
+        internalIp,  
+        internalName,  
+        internalSshUsername,  
+        lastAgentUpdate,  
+        lvmEnabled,  
+        macAddress,  
+        managed,  
+        maxCores,  
+        maxMemory,  
+        maxStorage,  
+        name,  
+        nodePackageVersion,  
+        osDevice,  
+        osType,  
+        osTypeCode,  
+        parentServerId,  
+        plan,  
+        platform,  
+        platformVersion,  
+        powerState,  
+        serialNumber,  
+        serverModel,  
+        serverType,  
+        serverTypeCode,  
+        serverTypeName,  
+        serverVendor,  
+        softwareRaid,  
+        sourceImageId,  
+        sshHost,  
+        sshPort,  
+        sshUsername,  
+        status,  
+        statusMessage,  
+        tags,  
+        toolsInstalled,  
+        visibility,  
+        volumes {  
+                name  
+                id  
+                deviceName  
+                maxStorage  
+                unitNumber  
+                displayOrder  
+                rootVolume  
+        }  
+}
+```
+```
+
+## Zone (Cloud)
+
+```
+```
+zone {  
+        agentMode,  
+        cloudTypeCode,  
+        cloudTypeName,  
+        code,  
+        datacenterId,  
+        domainName,  
+        firewallEnabled,  
+        location,  
+        name,  
+        regionCode,  
+        scalePriority  
+}
+```
+```
+
+## networkConfig
+
+```
+```
+'networkConfig': {  
+  'primaryInterface': {  
+    'doDhcp': false,  
+    'dnsServers': [],  
+    'dnsDomain': "",  
+    'netmask': "",  
+    'gateway': "",  
+    'ipAddress': "",  
+    'doDhcp6': false,  
+    'gateway6': "",  
+    'ipv6Address': "",  
+    'cidr6Suffix': "",  
+    'dnsServers6': ""  
+  },  
+  'extraInterfaces': [  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    },  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    }  
+  ]  
+}
+```
+```
+
+## Group (Site)
+
+```
+```
+group {  
+        code,  
+        location,  
+        datacenterId,  
+        name  
+}
+```
+```
+
+## Custom Options (Inputs)
+
+```
+```
+customOptions {  
+        customOptions.fieldName  
+}
+```
+```
+
+## Global
+
+ex: `<%= morpheus.user.id %>`
+
+```
+```
+"morpheus":{  
+   "user":{  
+      "id":value,  
+      "account":{  
+         "id":value  
+      },  
+      "username":"value",  
+      "displayName":"value",  
+      "email":"value",  
+      "firstName":"value",  
+      "lastName":"value",  
+      "dateCreated":0000-00-00T00:00:00Z,  
+      "lastUpdated":0000-00-00T00:00:00Z,  
+      "enabled":true/false,  
+      "accountExpired":true/false,  
+      "accountLocked":false,  
+      "passwordExpired":false,  
+      "defaultGroupId":value,  
+      "defaultZoneId":value,  
+      "hasLinuxUser":true/false,  
+      "hasWindowsUser":true/false,  
+      "role":{  
+         "id":value  
+      },  
+      "instanceLimits":value  
+   },  
+}
+```
+```
+
+## User
+
+```
+```
+'user': {'accountId': int,  
+        'accountName': 'string',  
+        'accountNumber': 'string',  
+        'attributes': {samlAttributes},  
+        'customerNumber': 'string',  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',
+```
+```
+
+## Script Variables Example
+
+Below is an example of the variables available to a script running against an Instance context.
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+```
+```
+'account': 'string',  
+'accountId': int,  
+'accountType': 'string',  
+'allowExisting': boolean,  
+'apps': [{'appContext': 'string',  
+          'description': 'string',  
+          'id': int,  
+          'name': 'string',  
+'cloud': 'string',  
+'cloudCode': 'string',  
+'cloudName': 'string',  
+'container': {'allowExisting': boolean,  
+              'certificatePath': string,  
+              'certificateStyle': string,  
+              'changeManagementExtId': int,  
+              'changeManagementServiceId': int,  
+              'cloud': 'string',  
+              'cloudConfig': {'agentInstall': agentInstallScript,  
+                              'finalizeServer': finalizeServerScript,  
+                              'meta': metaData,  
+                              'user': userData},  
+              'configGroup': int,  
+              'configId': int,  
+              'configPath': 'string',  
+              'configRole': int,  
+              'containerTypeCategory': 'string',  
+              'containerTypeCode': 'string',  
+              'containerTypeName': 'string',  
+              'containerTypeShortName': 'string',  
+              'cores': int,  
+              'coresPerSocket': int,  
+              'createUser': boolean,  
+              'customOptions': {'morph_ver': 'string',  
+              'dataPath': 'string',  
+              'dateCreated': 'string',  
+              'domainName': 'string',  
+              'environmentPrefix': 'string',  
+              'evars': {},  
+              'expireDays': 'string',  
+              'expose': ['string'],  
+              'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                                'name': 'string',  
+                                'port': int}],  
+              'externalIp': 'string',  
+              'externalPort': int,  
+              'hostMountPoint': 'string',  
+              'hostName': 'string',  
+              'hostname': 'string',  
+              'hosts': {'containerName': 'string',  
+                        'containerName': 'string',  
+                        'containerName': 'string',  
+              'id': int,  
+              'image': 'string',  
+              'instanceContext': 'string',  
+              'instanceType': {'code': 'string',  
+              'internalHostname': 'string',  
+              'internalIp': 'string',  
+              'internalPort': int,  
+              'layout': {'code': 'string',  
+                        'id': int},  
+              'logsPath': 'string',  
+              'maxCores': int,  
+              'maxCpu': int,  
+              'maxMemory': int,  
+              'maxStorage': int,  
+              'memory': int,  
+              'memoryDisplay': 'string',  
+              'mounts': [],  
+              'name': 'string',  
+              'networkId': int,  
+              'networkInterfaces': [{'id': 'string',  
+                                    'ipAddress': 'string',  
+                                    'ipMode': 'string',  
+                                    'network': {'dhcpServer': int,  
+                                                'group': int,  
+                                                'id': int,  
+                                                'name': 'string',  
+                                                'pool': int},  
+                                    'networkInterfaceTypeId': int}],  
+              'noAgent': boolean,  
+              'planCode': 'string',  
+              'portMap': {},  
+              'ports': [{'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean},  
+                        {'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean}],  
+              'provisionType': 'string',  
+              'publicKeyId': int,  
+              'server': {}  
+              'serverId': int,  
+              'shutdownDays': 'string',  
+              'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}],  
+              'sshHost': 'string',  
+              'status': 'string',  
+              'storage': int,  
+              'storageController': int,  
+              'type': 'string',  
+              'userGroup': {'id': '',  
+              'version': 'string',  
+              'vm': boolean,  
+              'volumes': [{'datastoreId': int,  
+                          'id': int,  
+                          'maxIOPS': int,  
+                          'maxStorage': int,  
+                          'name': 'string',  
+                          'rootVolume': boolean,  
+                          'size': int,  
+                          'storageType': int,  
+                          'vId': int}]},  
+'containerName': 'string',  
+'coresPerSocket': int,  
+'createUser': boolean,  
+'customOptions': {'morph_ver': 'string',  
+'deployOptions': {},  
+'evars': {},  
+'expireDays': 'string',  
+'expose': ['string'],  
+'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                  'name': 'string',  
+                  'port': int}],  
+'externalIp': 'string',  
+'group': {'code': 'string',  
+          'configCmdbId': 'string',  
+          'configManagementId': 'string',  
+          'datacenterId': int,  
+          'dnsIntegrationId': 'string',  
+          'location': 'string',  
+          'name': 'string',  
+          'serviceRegistryId': 'string',  
+'groupCode': 'string',  
+'groupName': 'string',  
+'host': ,  
+'hostMountPoint': 'string',  
+'hostName': 'string',  
+'hosts': {},  
+'input': {'backup': ,  
+          'cloud': {},  
+          'computedHostName': 'string',  
+          'computedName': 'string',  
+          'copies': int,  
+          'domainOptions': {}},  
+          'environmentVariables': {},  
+          'executionId': int,  
+          'expireDays': int,  
+          'group': {},  
+          'hostName': 'string',  
+          'instanceContext': 'string',  
+          'layout': {},  
+          'metadata': {}},  
+          'name': 'string',  
+          'plan': {},  
+          'powerScheduleType': int,  
+          'securityGroups': {},  
+          'shutdownDays': int,  
+          'type': 'string',  
+          'version': 'string'},  
+'instance': {'adminPassword': 'maskedString',  
+            'adminUsername': 'string',  
+            'allowExisting': boolean,  
+            'apps': [{}],  
+            'assignedDomainName': 'string',  
+            'autoScale': boolean,  
+            'backup': {'backupRepository': int,  
+                        'createBackup': boolean,  
+                        'enabled': boolean,  
+                        'jobAction': 'string',  
+                        'jobRetentionCount': 'string',  
+                        'providerBackupType': int,  
+                        'showScheduledBackupWarning': boolean},  
+            'cloud': 'string',  
+            'cloudConfig': {'agentInstall': agentInstallScript,  
+                            'finalizeServer': finalizeServerScript,  
+                            'meta': metaData,  
+                            'user': userData  
+                                    },  
+            'configGroup': int,  
+            'configId': int,  
+            'configRole': int,  
+            'container': {},  
+            'containers': [{}],  
+            'cores': int,  
+            'createBackup': boolean,  
+            'createUser': boolean,  
+            'createdByEmail': 'string',  
+            'createdByFirstName': 'string',  
+            'createdById': int,  
+            'createdByLastName': 'string',  
+            'createdByUser': {'accountId': int,  
+                              'displayName': 'string',  
+                              'email': 'string',  
+                              'firstName': 'string',  
+                              'id': int,  
+                              'lastName': 'string',  
+                              'linuxUsername': 'string',  
+                              'username': 'string',  
+                              'windowsUsername': 'string',  
+            'createdByUsername': 'string',  
+            'customOptions': {'morph_ver': 'string',  
+            'deployGroup': ,  
+            'description': 'string',  
+            'displayName': 'string',  
+            'domainName': 'string',  
+            'environmentPrefix': 'string',  
+            'evars': {  
+            'expireDate': date,  
+            'expireDays': 'string',  
+            'expose': ['string'],  
+            'firewallEnabled': boolean,  
+            'hostName': 'string',  
+            'hostname': 'string',  
+            'id': int,  
+            'instanceContext': 'string',  
+            'instanceLevel': 'string',  
+            'instanceType': {'code': 'string',  
+            'instanceTypeCode': 'string',  
+            'instanceTypeName': 'string',  
+            'instanceVersion': 'string',  
+            'layout': {'code': 'string',  
+                        'id': int},  
+            'layoutCode': 'string',  
+            'layoutId': int,  
+            'layoutName': 'string',  
+            'lbInstances': [{'balanceMode': 'string',  
+                              'enabled': boolean,  
+                              'externalAddress': 'string',  
+                              'id': int,  
+                              'instanceId': int,  
+                              'loadBalancer': {'id': int},  
+                              'loadBalancerId': int,  
+                              'name': 'string',  
+                              'port': int,  
+                              'protocol': 'string',  
+                              'sslCert': 'string',  
+                              'sslRedirectMode': 'string',  
+                              'stickyMode': 'string',  
+                              'vipAddress': 'string',  
+                              'vipDirectAddress': 'string',  
+                              'vipHostname': 'string',  
+                              'vipName': 'string',  
+                              'vipPort': int,  
+                              'vipProtocol': 'string',  
+                              'vipScheme': 'string',  
+                              'vipShared': 'string',  
+            'loadBalancerId': int,  
+            'memory': int,  
+            'memoryDisplay': 'string',  
+            'metadata': {'ver': 'string',  
+            'name': 'string',  
+            'networkLevel': 'string',  
+            'plan': 'string',  
+            'ports': {},  
+            'powerScheduleType': ,  
+            'provisionType': 'string',  
+            'scheduleStatus': 'string',  
+            'servicePassword': 'maskedString',  
+            'serviceUsername': 'string',  
+            'shutdownDays': 'string',  
+            'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}]  
+            'sslCertId': int,  
+            'sslEnabled': boolean,  
+            'status': 'string',  
+            'statusMessage': 'string',  
+            'storage': int,  
+            'tags': 'string',  
+            'type': ,  
+            'userGroup': {'id': 'string',  
+            'userStatus': 'string',  
+'instanceContext': 'string',  
+'instanceType': {'code': 'string',  
+'internalIp': 'string',  
+'isDocker': boolean,  
+'layout': {'code': 'string',  
+'localScriptGitId': int,  
+'localScriptGitRef': 'string',  
+'logTag': 'string',  
+'maxCores': int,  
+'maxCpu': int,  
+'maxMemory': int,  
+'maxStorage': int,  
+'memoryDisplay': 'string',  
+'morpheus': {'apiAccessToken': 'string',  
+            'applianceHost': 'string',  
+            'appliancePort': 'string',  
+            'applianceScheme': 'string',  
+            'applianceSsl': boolean,  
+            'applianceUrl': 'string',  
+'morpheusUser': 'string',  
+'mounts': [],  
+'name': 'string',  
+'networkId': int,  
+'networkInterfaces': [{'id': 'string',  
+                      'ipAddress': 'string',  
+                      'ipMode': 'string',  
+                      'network': {'dhcpServer': ,  
+                                  'group': int,  
+                                  'Id': int,  
+                                  'name': 'string',  
+                                  'pool': int},  
+                      'networkInterfaceTypeId': int}],  
+'noAgent': boolean,  
+'platform': 'string',  
+'port': int,  
+'ports': [{'code': 'string',  
+          'displayName': 'string',  
+          'export': boolean,  
+          'exportName': 'string',  
+          'external': int,  
+          'index': int,  
+          'internal': int,  
+          'link': boolean,  
+          'loadBalance': boolean,  
+          'primaryPort': boolean,  
+          'protocol': 'string',  
+          'visible': boolean}],  
+'provisionType': 'string',  
+'publicKeyId': int,  
+'pythonAdditionalPackages': ,  
+'pythonArgs': ,  
+'pythonBinary': 'string',  
+'pythonScript': ,  
+'results': {},  
+'sequence': int,  
+'server': {'agentInstalled': boolean,  
+          'agentVersion': 'string',  
+          'apiKey': 'string',  
+          'category': ,  
+          'cloudConfig': {'agentInstall': agentInstallScript,  
+                          'finalizeServer': finalizeServerScript,  
+                          'meta': metaData,  
+                          'user': userData  
+                                  },  
+          'commType': 'string',  
+          'computeTypeCode': 'string',  
+          'computeTypeName': 'string',  
+          'configGroup': int,  
+          'configId': int,  
+          'configRole': 'string',  
+          'consoleHost': 'string',  
+          'consolePort': int,  
+          'consoleType': 'string',  
+          'consoleUsername': 'string',  
+          'createdByUser': {'accountId': int,  
+                            'displayName': 'string',  
+                            'email': 'string',  
+                            'firstName': 'string',  
+                            'id': int,  
+                            'lastName': 'string',  
+                            'linuxUsername': 'string',  
+                            'username': 'string',  
+                            'windowsUsername': 'string',  
+          'dataDevice': 'string',  
+          'dateCreated': 'string',  
+          'description': 'string',  
+          'displayName': 'string',  
+          'domainName': 'string',  
+          'externalId': 'string',  
+          'externalIp': 'string',  
+          'fqdn': 'string',  
+          'hostname': 'string',  
+          'id': int,  
+          'interfaces': [{'dhcp': boolean,  
+                          'domain': {'fqdn': 'string',  
+                                      'name': 'string',  
+                                      'ouPath': 'string'},  
+                          'interfaceId': int,  
+                          'ipAddress': 'string',  
+                          'ipMode': 'string',  
+                          'ipSubnet': 'string',  
+                          'ipv6Address': 'string',  
+                          'ipv6Subnet': 'string',  
+                          'macAddress': 'string',  
+                          'network': {'cidr': 'string',  
+                                      'cidrMask': 'string',  
+                                      'gateway': 'string',  
+                                      'name': 'string',  
+                                      'netmask': 'string',  
+                                      'vlanId': int},  
+                          'networkPosition': 'string',  
+                          'vlanId': int}],  
+          'internalId': int,  
+          'internalIp': 'string',  
+          'internalName': 'string',  
+          'internalSshUsername': 'string',  
+          'lastAgentUpdate': 'string',  
+          'lvmEnabled': boolean,  
+          'macAddress': 'string',  
+          'managed': boolean,  
+          'maxCores': int,  
+          'maxMemory': int,  
+          'maxStorage': int,  
+          'name': 'string',  
+          'nodePackageVersion': 'string',  
+          'osDevice': 'string',  
+          'osPassword': 'maskedString',  
+          'osType': 'string',  
+          'osTypeCode': 'string',  
+          'osUsername': 'string',  
+          'parentServerId': int,  
+          'plan': 'string',  
+          'platform': 'string',  
+          'platformVersion': 'string',  
+          'powerScheduleType': ,  
+          'powerState': 'string',  
+          'publicKeyId': int,  
+          'serialNumber': 'string',  
+          'serverModel': 'string',  
+          'serverType': 'string',  
+          'serverTypeCode': 'string',  
+          'serverTypeName': 'string',  
+          'serverVendor': 'string',  
+          'softwareRaid': boolean,  
+          'sourceImageId': int,  
+          'sshHost': 'string',  
+          'sshPort': int,  
+          'sshUsername': 'string',  
+          'status': 'string',  
+          'statusMessage': 'string',  
+          'tags': {},  
+          'toolsInstalled': boolean,  
+          'uniqueId': int,  
+          'uuid': 'string',  
+          'visibility': 'string',  
+          'volumes': [{'deviceName': 'string',  
+                        'displayOrder': int,  
+                        'id': int,  
+                        'maxStorage': int,  
+                        'name': 'string',  
+                        'rootVolume': boolean,  
+                        'unitNumber': 'string',  
+'serverId': 'string',  
+'serverName': 'string',  
+'shutdownDays': 'string',  
+'site': {'accountId': int,  
+        'active': boolean,  
+        'id': int,  
+        'integrations': [],  
+        'location': 'string',  
+        'name': 'string',  
+        'visibility': 'string',  
+        'zones': [{}],  
+'sshKey': 'string',  
+'state': {},  
+'storageController': int,  
+'tenant': 'string',  
+'tenantId': int,  
+'tenantSubdomain': 'string',  
+'type': 'string',  
+'user': {'accountId': int,  
+        'attributes': {samlAttributes},  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',  
+'userGroup': {'id': 'string',  
+'userId': int,  
+'userInitials': 'string',  
+'username': 'string',  
+'vm': boolean,  
+'volumes': [{'datastoreId': int,  
+            'id': int,  
+            'maxIOPS': int,  
+            'maxStorage': int,  
+            'name': 'string',  
+            'rootVolume': boolean,  
+            'size': int,  
+            'storageType': int,  
+            'vId': int}],  
+'zone': {'agentMode': 'string',  
+        'cloudTypeCode': 'string',  
+        'cloudTypeName': 'string',  
+        'code': 'string',  
+        'datacenterId': int,  
+        'domainName': 'string',  
+        'firewallEnabled': boolean,  
+        'location': 'string',  
+        'name': 'string',  
+        'regionCode': 'string',  
+        'scalePriority': int}}
+```
+```
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+## Spec Template Variables
+
+Spec Template Variables
+
+- **morpheus**
+  - getApiAccessToken()
+  - formatMemory(size, unit)
+  - applianceUrl
+  - applianceHost
+  - appliancePort
+  - applianceScheme
+  - applianceSsl
+  - morpheusHome
+  - morpheusUser
+  - publicKey
+  - privateKey
+  - cloudConfig
+- **cypher**
+  - read(key)
+  - write(key, value)
+  - delete(key)
+  - readUuid(key)
+  - readEncyptionKey(key)
+  - readPassword(key)
+- **archives**
+  - link(bucketName, filePath)
+- account
+- accountId
+- accountType
+- **apps - []**
+  - appContext
+  - description
+  - id
+  - name
+- **cloudConfig**
+  - agentInstall
+  - finalizeServer
+- **customOptions**
+  - key
+- **deployOptions**
+  - key
+- **evars**
+
+  - key
+- **group**
+  - code
+  - datacenterId
+  - location
+  - name
+- groupCode
+- groupName
+- **input**
+  - backup
+  - cloud
+  - computedHostName
+  - computedName
+  - copies
+  - domainOptions
+  - environmentVariables
+  - executionId
+  - expireDays
+  - group
+  - hostName
+  - instanceContext
+  - layout
+  - metadata
+  - name
+  - plan
+  - powerScheduleType
+  - securityGroups
+  - shutdownDays
+  - type
+  - version
+- **instance**
+  - adminPassword
+  - adminUsername
+  - apps - []
+    - appContext
+    - description
+    - id
+    - instances
+    - name
+  - assignedDomainName
+  - autoScale
+  - cloudConfig
+    - agentInstall
+    - finalizeServer
+  - configGroup
+  - configId
+  - configRole
+  - container
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - containers - []
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - cores
+  - createdByEmail
+  - createdByFirstName
+  - createdById
+  - createdByLastName
+  - createdByUser
+    - accountId
+    - attributes
+    - displayName
+    - email
+    - firstName
+    - id
+    - lastName
+    - linuxUsername
+    - username
+    - windowsUsername
+  - createdByUsername
+  - customOptions
+    - key
+  - deployGroup
+  - description
+  - displayName
+  - domainName
+  - environmentPrefix
+  - evars
+    - key
+  - expireDate
+  - firewallEnabled
+  - hostname
+  - id
+  - instanceContext
+  - instanceLevel
+  - instanceTypeCode
+  - instanceTypeName
+  - instanceVersion
+  - layoutCode
+  - layoutId
+  - layoutName
+  - memory
+  - metadata
+  - name
+  - networkLevel
+  - plan
+  - ports
+  - provisionType
+  - scheduleStatus
+  - servicePassword
+  - serviceUsername
+  - sslCertId
+  - sslEnabled
+  - status
+  - statusMessage
+  - storage
+  - tags
+  - templateOutput
+  - userStatus
+- platform
+- provisionType
+- **results**
+- sequence
+- **state**
+  - iacDrift
+  - stateDate
+  - stateList - []
+    - category
+    - code
+    - contentPath
+    - errorMessage
+    - iacDrift
+    - id
+    - input
+    - name
+    - output
+    - planPath
+    - resourceVersion
+    - stateContext
+    - stateDate
+    - stateId
+    - statePath
+    - stateType
+    - status
+    - statusMessage
+    - tags
+    - workingPath
+  - stateType
+- tenant
+- tenantId
+- tenantSubdomain
+- type
+- userId
+- userInitials
+- username
+
+</</div>
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json b/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
new file mode 100644
index 0000000..fa11525
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+  "title": "Cohesity",
+  "ordinal": 382,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.html",
+  "topic_cluster": {
+    "clustering_title": "Cohesity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md b/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
new file mode 100644
index 0000000..419e37b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
@@ -0,0 +1,92 @@
+# Cohesity
+
+HPE Morpheus Enterprise integrates with Cohesity for selection as a Cloud backup target for compatible Cloud types and for adding Cohesity S3 storage servers and storage buckets. HPE Morpheus Enterprise integrates with your existing Cohesity appliance, which can then be set as the default backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. To utilize storage features, integrate a Cohesity S3 storage server and then create a Cohesity S3 storage bucket.
+
+This section discusses the process for integrating Cohesity with HPE Morpheus Enterprise, setting backup options during Instance provisioning, restoring Instances from Cohesity backup, and using Cohesity S3 storage.
+
+## Adding the integration
+
+Cohesity integrations are added in the backup integrations area of the UI (Backups > Integrations). If a Cohesity integration is not an option, you must download and add the Cohesity plugin to the HPE Morpheus Enterprise appliance. For additional information on adding a plugin, including how to access the Hewlett Packard Enterprise-maintained repository which includes the Cohesity plugin, see the [plugin section](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html) of this documentation.
+
+With the Cohesity plugin installed, navigate to Backups > Integrations to add a new Cohesity integration. Click + ADD and a modal appears for creating a new Cohesity backup provider.
+
+![../../_images/createBackupProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F640EDCF-693E-49D1-8ABA-8AC090325603-high.png)
+
+Provide the following information:
+
+- **NAME:** A name for the Cohesity provider in HPE Morpheus Enterprise UI
+- **ENABLED:** When marked, the Cohesity provider will be available for use
+- **HOST:** Enter the host name
+- **CREDENTIALS:** An API key is required for authentication. Select “Local Credentials” to enter the API key directly into this modal. Select “api key” under the “New Credentials” heading to enter the API key directly into this modal and save it in a chosen secure secret store for later use. If an API key has already been stored in an integrated secret store, you may also choose it here rather than directly entering the key into this modal
+- **SECRET STORE:** Optional and only visible if you’ve opted in the CREDENTIALS field to securely store your entered API key
+- **API KEY:** Only visible if authenticating through local credentials (that is, you haven’t selected a saved API key from the CREDENTIALS field). Enter the API key
+- **VISIBILITY:** Cohesity integrations with private visibility are consumable only by the Tenant in which the integration is created
+
+When finished, click SAVE. The new Cohesity backup provider should be successfully created.
+
+## Setting the Cloud Backup Provider
+
+Now that the Cohesity backup provider is created, it can be set as the default backup provider for supported Cloud types. To set this configuration on a Cloud, navigate to the Clouds list page (Infrastructure > Clouds) and edit a compatible Cloud (✎ icon). Expand the “Advanced Options” section and locate the BACKUP PROVIDER configuration. Set the Cohesity provider as the backup provider for the Cloud and click SAVE CHANGES.
+
+![../../_images/editCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AF02E7F0-F125-4FF5-BA08-A35DEE94F1CC-high.png)
+
+## Backup Options at Provision Time
+
+With Cohesity set up as the backup provider for a Cloud (or Clouds), additional backup options are made available when provisioning to the Cloud. These configurations are made from the AUTOMATION tab of the provisioning wizard (launched by clicking + ADD from the Instance list page at Provisioning > Instances). From the AUTOMATION tab, expand the “Backups” section. The BACKUP TYPE of “Cohesity Protection Group” should be preselected. Then, make the next two configurations:
+
+- **BACKUP NAME:** A name for the backup (often named for the Instance associated with the backup)
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group.
+
+![../../_images/noPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-593744EF-D461-44D1-9839-26105B9AA42E-high.png)
+
+If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+![../../_images/yesPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0811D470-3CF2-43F5-8689-CA8820605919-high.png)
+
+Once these configurations are provided, complete the provisioning wizard and the configured backup options are applied to the new Instance.
+
+## Creating Backups for Existing Instances
+
+In addition to creating Backups at provision time, as discussed in the previous section, Cohesity backups can be configured for existing Instances. Start from the Backups list page (Backups > Backups) and click + ADD. When the CREATE BACKUP modal appears, select “Instance” from the SELECT SOURCE tab and click NEXT. From the NAME/TYPE tab use the INSTANCE field, which is a typeahead field, to search for a compatible Instance. In the NAME field, enter a name for the new Backup and click NEXT. From the INFO tab, the following configurations are made:
+
+- **BACKUP TYPE:** Cohesity Protection Group
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group. If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+On clicking COMPLETE, the new Backup is successfully created.
+
+## Restoring from Cohesity Backups
+
+To restore an Instance from a Cohesity backup, begin at the Backups list page (Backups > Backups). From the list of Backups, click on the desired backup making sure to click the Backup name and not the name of a Backup Job. On the Backup detail page, note the BACKUP ARCHIVES section. Identify the correct restore point (if more than one are available) and click ACTIONS > Restore. The Instance will be successfully restored from backup.
+
+![../../_images/backupArchives.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6CF1441A-23C0-488D-B250-83D4CE2CAA76-high.png)
+
+## Using Cohesity S3
+
+To work with Cohesity S3, start by creating a Cohesity storage server object in HPE Morpheus Enterprise. To do so, navigate to Infrastructure > Storage > Servers and click + ADD. Make the following configurations:
+
+- **NAME:** A name for the storage server object in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description field
+- **ENABLED:** When marked, the storage server object is available for consumption in HPE Morpheus Enterprise
+- **TYPE:** Cohesity S3. When this type is selected, the required configuration fields appear
+- **ENDPOINT:** The endpoint of the cluster
+- **API KEY:** A valid API key for authentication
+
+Click SAVE CHANGES and the storage server object is created.
+
+![../../_images/createStorageServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F367EF34-C8AE-4D5E-83B2-6ECA4A797481-high.png)
+
+With the storage server created, Cohesity S3 buckets may be created. Buckets are created at Infrastructure > Storage > Buckers. Click + ADD and then Cohesity S3 Bucket. On the NEW BUCKET modal, first select a Cohesity S3 storage server from the STORAGE SERVICE dropdown menu. This will preload other configuration field dropdown menus, such as STORAGE DOMAIN and QOS. From this modal, the bucket can be set as a default backup target or as a default target for Virtual Images or deployment archives. Once finished, click SAVE CHANGES
+
+![../../_images/createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FB2BEBEB-06B5-4F1A-BCD3-E72DF8E016AD-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json b/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
new file mode 100644
index 0000000..1bc28af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+  "title": "Cisco ACI",
+  "ordinal": 513,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html",
+  "topic_cluster": {
+    "clustering_title": "Cisco ACI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md b/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
new file mode 100644
index 0000000..fda3dca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
@@ -0,0 +1,86 @@
+# Cisco ACI
+
+## Overview
+
+![ACI summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E24C5FDE-8C7F-44B1-B150-0FDDAB2B18CE-high.png)
+
+Add ACI as a network and security integration. Inventory your existing ACI configurations. Create networks, bridge domains, application profiles, tenants, endpoint groups, contexts, filters and contracts. Provision instances into new endpoint groups and define security groups that apply contracts on provision.
+
+From Morpheus below can be created:
+
+- Tenants
+- ANP’s
+- EPG’s
+- Contexts
+- Bridge Domains
+- Filters
+- Contracts
+
+NOTE
+
+Morpheus to ACI Sync Job Schedule: Every 5 minutes
+
+NOTE
+
+Morpheus connects to ACI APIC over port 443
+
+## Add Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Networks  >  Integrations
+2. Select +ADD > Networking > `Cisco ACI`
+3. Populate the following: 
+
+   NAME
+   :   ACI Integration Name/Label in HPE Morpheus Enterprise
+       :   This is unique to HPE Morpheus Enterprise and not part of authentication
+
+   URL
+   :   ACI fabric url, eg `https://apicdc.company.com`
+
+   USERNAME
+   :   ACI `aaaUser` name attribute
+
+   PASSWORD
+   :   ACI `aaaUser` pwd attribute
+
+   TENANT
+   :   Populates upon authentication, tenant selection not required
+4. Select ADD NETWORK INTEGRATION
+
+## Configure Cloud Network Mode
+
+### About this task
+
+For your ACI Integration to be available during provisioning, ACI needs to be defined on a Cloud or multiple Clouds `NETWORK MODE` advanced options.
+
+### Procedure
+
+1. Select an existing VMware vCenter Cloud
+2. Select EDIT
+3. Expand the Advanced Options section
+4. Select ACI Integration in `NETWORK MODE` dropdown
+5. Select SAVE
+
+## Instance Provisioning
+
+### About this task
+
+![ACI Instance provisioning options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+Once ACI is integration to a cloud, it can be used during instance provisioning:
+
+### Procedure
+
+1. From the EPG drop down, either an existing EPG can be selected or a new one can be created. It is the same for ANP, either create a new one or choose an existing.
+2. Under ACI security consumes and provides, contracts can be searched when you enter a name. When the provisioning wizard is completed, it will provision the instance and apply the ACI options and Security. This can be viewed under the instance page, or via REST API and CLI.
+
+## Blueprint Configuration
+
+![ACI Blueprint options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+- In a Blueprint, you can define the ANP and EPG of each Tier
+- Variables can be used for EPG and ANP names.
+- This could be useful to create blueprints for dev testing to isolate from prod networks.
+- This can be hybrid based on the VMM domains in APIC.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json b/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
new file mode 100644
index 0000000..afabe2c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+  "title": "Scaling Morpheus Nodes",
+  "ordinal": 27,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html",
+  "topic_cluster": {
+    "clustering_title": "Scaling Morpheus Nodes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md b/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
new file mode 100644
index 0000000..5558479
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
@@ -0,0 +1,40 @@
+# Scaling Morpheus Nodes
+
+Morpheus App nodes can be scaled to accommodate additional load. Appliance nodes can be scaled vertically in centralized architectures, and both vertically and horizontally in distributed architectures.
+
+## Vertical Scaling
+
+In all Appliance Architectures, Application nodes can be vertically scaled at any time, however a reconfigure must be performed for additional resources to be utilized by HPE Morpheus Enterprise on a node, which will result in the `morpheus-ui` restarting on the reconfiguring node.
+
+Morpheus configures memory/ram utilization for services during the `reconfigure` process. If additional memory/ram is added to a Host or VM running the Morpheus App, the additional memory/ram will not be utilized by the Morpheus Application until a `morpheus-ctl reconfigure` command is ran and the additional memory/ram is recognized.
+
+IMPORTANT
+
+When the `morpheus-ctl reconfigure` command detects changes on available memory/ram, it will restart the `morpheus-ui` service.
+
+The impact on Availability depends on the Morpheus Appliance Architecture.
+
+- Centralized Appliances
+  :   Morpheus will be unavailable while the `morpheus-ui` restarts.
+- Distributed Appliances
+  :   Zero-down time can be achieved by Reconfiguring one App Node at a time, with proper Front-End Load Balancer configuration.
+
+## Horizontal Scaling
+
+Additional Morpheus App Nodes can be added at any time to Fully Distributed Architectures.
+
+- Configure Shared Storage paths for the new App Node(s)
+- Install, but do not run the `morpheus-ctl reconfigure` command on the new App Node(s), using the same Morpheus version as the existing Appliance nodes.
+- Copy the `morpheus.rb` from an existing App Node to the new App Node(s)
+- Ensure permissions and network configuration for the new App Node(s) to access all MySQL and Elasticsearch nodes, and the RabbitMQ VIP.
+- Ensure permissions and network configuration for all required UI services and Integrations, such as network access to ESXi hosts over 443 for Hypervisor console and/or image transfers.
+- Add associated SSL files and configuration which is not on shared storage.
+- Reconfigure the new App Node(s) via `morpheus-ctl reconfigure`
+- Verify UI startup succeeded
+- Add New App Node(s) to Front End Morpheus UI Load Balancer pool.
+
+During `morpheus-ctl reconfigure`, the new App Node(s) will validate and be configured to use the existing tiers for the UI service. Upon successful reconfigure, the Morpheus service will be available on the App Node(s) with consistent data and capabilities.
+
+NOTE
+
+No services, including `morpheus-ui`, are required to be shut down on existing nodes when adding new App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json b/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
new file mode 100644
index 0000000..a0b3933
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+  "title": "Alibaba",
+  "ordinal": 388,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md b/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
new file mode 100644
index 0000000..b90a2d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
@@ -0,0 +1,157 @@
+# Alibaba
+
+## Features
+
+- Brownfield discovery
+- Instance cloning
+- Security group creation and management
+- Docker and Kubernetes provisioning and management
+- Usage tracking
+- Two-way tag sync
+
+## Supported Regions
+
+- ap-northeast-1 (亚太东北 1 (东京)
+- ap-south-1 (亚太南部 1 (孟买)
+- ap-southeast-1 (亚太东南 1 (新加坡)
+- ap-southeast-2 (亚太东南 2 (悉尼)
+- ap-southeast-3 (亚太东南 3 (吉隆坡)
+- ap-southeast-5 (亚太东南 5 (雅加达)
+- cn-beijing (华北 2)
+- cn-chengdu (西南1（成都）)
+- cn-guangzhou (华南3（广州）)
+- cn-hangzhou (华东 1)
+- cn-heyuan (华南2（河源）)
+- cn-hongkong (香港)
+- cn-huhehaote (华北 5)
+- cn-qingdao (华北 1)
+- cn-shanghai (华东 2)
+- cn-shenzhen (华南 1)
+- cn-wulanchabu (华北6（乌兰察布）)
+- cn-zhangjiakou (华北 3)
+- eu-central-1 (欧洲中部 1 (法兰克福)
+- eu-west-1 (英国（伦敦）)
+- me-east-1 (中东东部 1 (迪拜)
+- us-east-1 (美国东部 1 (弗吉尼亚)
+
+## Integrate an Alibaba Cloud with HPE Morpheus Enterprise
+
+To add a new Cloud, navigate to Infrastructure > Clouds and click + ADD. Select “Alibaba Cloud” and click NEXT. Once the “ADD CLOUD” modal appears, configure the following:
+
+- **NAME:** A friendly name for the Cloud in HPE Morpheus Enterprise
+- **CODE:** A Cloud code used to reference this Cloud in HPE Morpheus Enterprise API
+- **LOCATION:** An optional field for tracking location data related to this Cloud
+- **VISIBILITY:** Public Clouds are available to all Tenants, Private Clouds are available to one selected Tenant
+- **TENANT:** If the Cloud visibility is set to “Private”, this field determines which Tenant the Cloud is exposed to
+- **ENABLED:** When marked, the Cloud is available as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** When marked, HPE Morpheus Enterprise is the source of truth for the expected power state of Instances. HPE Morpheus Enterprise tools should be used to control power state and HPE Morpheus Enterprise will override any unexpected power states (such as if an instance were powered on or off from the Alibaba web console)
+- **CREDENTIALS:** Select Local Credentials to enter authentication credentials on this modal, Existing Credentials to choose a pre-saved credential set, or New Credentials to enter authentication credentials on this modal and save them (in Infrastructure > Trust) for other uses later
+- **ACCESS KEY:** (When Local Credentials or New Credentials are selected) A valid Access Key for an Alibaba Cloud account
+- **SECRET KEY:** (When Local Credentials or New Credentials are selected) A valid Secret Key for an Alibaba Cloud account
+- **INVENTORY:** When marked, HPE Morpheus Enterprise will automatically onboard existing instances in the Alibaba Cloud account as unmanaged servers
+- **REGION:** Select the Alibaba Cloud region to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+- **VPC:** Select the Alibaba Cloud VPC to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Following Integration
+
+After the integration has been created, HPE Morpheus Enterprise will sync existing workloads (if you’ve opted to inventory), security groups, tags, and more. Synced workloads can be viewed from Infrastructure > Compute. If Plans aren’t immediately available within a few minutes after the integration is created, navigate to the Cloud detail page (Infrastructure > Clouds > Your Integrated Alibaba Cloud), click REFRESH and click “Daily”. Shortly thereafter, the Plans should be synced and selectable at provision time. Without manually syncing the Plans, you may be unable to provision to this Cloud until it undertakes its next daily sync overnight as Plan selection is required.
+
+You’re now able to provision new Instances and Apps to the Alibaba Cloud. HPE Morpheus Enterprise includes a default catalog that includes Alibaba images which can be provisioned out of the box. Additionally, you can begin to create your own custom library of Alibaba workloads by adding Virtual Images and building out Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json b/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
new file mode 100644
index 0000000..ba3a675
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+  "title": "Creating Network Using the ArubaCX Integration",
+  "ordinal": 434,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Network Using the ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md b/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
new file mode 100644
index 0000000..9110d95
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
@@ -0,0 +1,26 @@
+# Creating Network Using the ArubaCX Integration
+
+## Prerequisites
+
+Before starting to create networks using integration, ensure that a Bare metal cloud is created with the ‘Network Mode’ set to the integration. If the Bare metal cloud already exists then ensure that ‘Network Mode’ is set to integration.
+
+## About this task
+
+Perform the following to create the network:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network.
+3. Click the Add to add a new integration.
+4. Enter the following details for the network:
+   - **Group** for the network
+   - **Network Service** specifies the Network Integration to use
+   - **Name** for the network
+   - **Gateway, DNS** information if required
+   - **CIDR** for the subnet
+   - Primary **VLAN ID** for the network
+   - Check the **Private** checkbox if a private network
+   - **VLAN trunks** for the network (optional)
+   - Choose Network Pool to be one of the IP pools configured![Create network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-68DA56E3-0840-4CA8-B10F-718312751234-high.png)
+5. Click Save Changes to create the network.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json b/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
new file mode 100644
index 0000000..51a624f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+  "title": "Code Integrations",
+  "ordinal": 100,
+  "parent_title": "Code",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html",
+  "topic_cluster": {
+    "clustering_title": "Code Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md b/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
new file mode 100644
index 0000000..595cc13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
@@ -0,0 +1,16 @@
+# Code Integrations
+
+The Provisioning ‣ Code ‣ Integrations section is where Code Integrations, such as Git and Github Repository Integrations, and Jenkins Build Service Integrations, can be created and managed.
+
+## Role Permissions
+
+Access and capabilities for the **Integrations** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json b/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
new file mode 100644
index 0000000..49ca88d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+  "title": "Backups",
+  "ordinal": 254,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md b/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
new file mode 100644
index 0000000..40277a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
@@ -0,0 +1,191 @@
+# Backups
+
+The HPE Morpheus Enterprise built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from HPE Morpheus Enterprise.
+
+HPE Morpheus Enterprise also integrates with external services to automate availability with other providers.
+
+## Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See HPE Morpheus Enterprise UI [Storage Documentation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+### Global Backups Settings
+
+HPE Morpheus Enterprise Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+### Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
+
+## Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See [`Policies`](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout. Many backup job types are supported including (but not limited to):
+
+- File Backup
+- Directory Backup
+- MySQL
+- MongoDB
+- LVM Snapshot
+- LVM Image
+- LVM Migration
+- Windows Migration
+- Postgres
+- Tar Directory Backup
+- Amazon VM Snapshot
+- VMWare VM Snapshot
+- Fusion VM Snapshot
+- Xen VM Snapshot
+- Veeam VMWare VM Backup
+- Veeam Hyper-V VM Backup
+- Google VM Snapshot
+- Commvault File/Directory Backup
+- Azure VM Snapshot
+- Morpheus Appliance
+- Openstack VM Snapshot
+- DigitalOcean VM Snapshot
+- Nutanix VM Snapshot
+- Softlayer VM Snapshot
+- Hyper-V VM Snapshot
+- VMWare VM Snapshot
+- SCVMM VM Snapshot
+- UpCloud VM Snapshot
+- Bluemix VM Snapshot
+- Alibaba VM Snapshot
+- Oracle Cloud VM Snapshot
+- KVM VM Snapshot
+- Container Backup
+- VM Backup
+- Object Storage Backup
+
+## Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
+
+![../_images/backupSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A241F036-0867-4093-88ED-6F98CE2D6BD9-high.png)
+
+## Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+### Create an Instance Backup
+
+#### About this task
+
+To create Instance backup:
+
+#### Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+#### Results
+
+NOTE
+
+On VMware Cloud types, HPE Morpheus Enterprise will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so HPE Morpheus Enterprise has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json b/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
new file mode 100644
index 0000000..d3cc523
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+  "title": "Unable to Delete Tenant",
+  "ordinal": 357,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Delete Tenant",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md b/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
new file mode 100644
index 0000000..5ba4195
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
@@ -0,0 +1,22 @@
+# Unable to Delete Tenant
+
+Problem
+:   When trying to delete a tenant, a message stating manage resources must be removed or other error occurs and the tenant is not deleted. The tenant may be stuck in a deleting status or return to OK status after delete attempt.
+
+Cause
+:   All managed resources must be removed from a tenant in order for that tenant to be deleted. This includes instances and their underlying managed vm’s
+
+Solution
+:   1. Login or impersonate that an Admin user inside the tenant
+    2. Navigate to Infrastructure > Hosts
+    3. Under Hosts and VM’s, delete any managed resources
+
+       - Uncheck `remove infrastructure` when deleting a VM to only remove it from HPE Morpheus Enterprise but not from the underlying hypervisor/cloud
+       - You must check `remove associated instances` if the VM has an associated instance
+       - If the VM no longer exists but there is still a record in HPE Morpheus Enterprise, uncheck `remove infrastructure` and check `force delete`
+    4. Once all managed resources are removed from the tenant, the tenant can then be deleted
+    5. In certain situations other components may prevent a tenant from being deleted. If you have removed all managed resources from a tenant and the tenant still cannot be deleted, please contact HPE Morpheus Enterprise support
+
+WARNING
+
+Managed resources can also be removed by deleting instances, but be aware this will delete VM’s associated with the instance from the underlying hypervisor/cloud
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.json b/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
new file mode 100644
index 0000000..f300e1f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+  "title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+  "ordinal": 354,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.md b/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
new file mode 100644
index 0000000..7b1c1ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
@@ -0,0 +1,72 @@
+# HPE Morpheus Enterprise UI not loading after upgrade or reconfigure
+
+Problem:
+:   The HPE Morpheus Enterprise ui does not load after performing an upgrade.
+
+Common Causes:
+:   1. The morpheus-ui has not finished loading
+    2. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+    3. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+Solutions:
+:   1. The morpheus-ui has not finished loading.
+
+       An easy way to see when the ui is finished loading and running is to tail the ui current file and look for the morpheus logo with version and start time
+
+       ```
+       ```
+       morpheus-ctl tail morpheus-ui
+       ```
+       ```
+
+    NOTE
+
+    After running morpheus-ctl start morpheus-ui, the HPE Morpheus Enterprise ui takes around 3 minutes to run depending on hardware.
+
+    1. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+
+       The morpheus ui must be stopped prior to running morpheus-ctl reconfigure when upgrading. Sometimes running morpheus-ctl stop morpheus-ui will timeout and the ui is not actually stopped. If stopping the ui does timeout, run morpheus-ctl kill morpheus-ui prior to reconfigure, and be sure to run morpheus-ctl start morpheus-ui after reconfigure is completed. If you ran a reconfigure before stopping the ui, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl reconfigure  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
+
+       Wait for the ui to come up.
+    2. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+       If the ui fails to start and you see the error `Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by morpheus` it likely means morpheus was forced to restart or shut down while the database schema was being migrated during an upgrade, and the lock was not released. To release the lock, you will need to run a mysql query. You will need to install mysql-client on the morpheus appliance, and grab the password for morpheus mysql. The username and db name are both morpheus. The password to login to mysql can be found in the application.yml file located at `/opt/morpheus/conf/application.yml` Then run the following:
+
+       ```
+       ```
+       mysql -u morpheus -p -h 127.0.0.1 morpheus
+       ```
+       ```
+
+       At the prompt, enter the mysql password from the application.yml Then run:
+
+       ```
+       ```
+       DELETE FROM DATABASECHANGELOGLOCK;
+       ```
+       ```
+
+       Then restart morpheus-ui:
+
+       ```
+       ```
+       sudo morpheus-ctl restart morpheus-ui
+       ```
+       ```
+
+       If the restart timesout, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json b/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
new file mode 100644
index 0000000..26e6e00
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+  "title": "Images",
+  "ordinal": 253,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html",
+  "topic_cluster": {
+    "clustering_title": "Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md b/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
new file mode 100644
index 0000000..25b9a1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
@@ -0,0 +1,69 @@
+# Images
+
+Morpheus provides Images for ESXi, CentOS, Ubuntu and XenServer, and user can add their own Images.
+
+## Add Images
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab then click the Add Image button.
+4. From the Upload Virtual Image Wizard input the following information 
+
+   Name
+   :   Name of the Image.
+
+   Operating System
+   :   List of available operating systems.
+
+   Storage Provider
+   :   List of available storage providers.
+
+   Image Path
+   :   Path of the image.
+
+   Visibility
+   :   Private or Public
+
+   Account
+   :   List of accounts to allow permission to this image.
+5. Save Changes
+
+## Edit Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab
+4. Click the actions drop down and select edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
+
+## Convert Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Convert.
+
+## Download Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Download.
+
+## Remove Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Image tab.
+4. Click the Actions drop and select Remove.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json b/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
new file mode 100644
index 0000000..e9c7df0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+  "title": "Utilization: Utilization vs Cost",
+  "ordinal": 65,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html",
+  "topic_cluster": {
+    "clustering_title": "Utilization: Utilization vs Cost",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md b/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
new file mode 100644
index 0000000..a95d3d3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
@@ -0,0 +1,30 @@
+# Utilization: Utilization vs Cost
+
+![../_images/8utilization.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-98D09465-88F7-420B-AEF8-80393CC3A8B7-high.png)
+
+The Utilization vs Cost dashboard is designed to reveal workloads which are underutilized (expensive and seldom-used) and which are very cost-efficient (inexpensive and frequently-used). Administrators can filter the workloads considered by the dashboard through the use of filters and potentially identify areas of cost savings by decommissioning seldom-used machines.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matching search terms)
+- Time period (Current, one-day average, one-week average, one-month average, three-month average, six-month average, or one-year average)
+- Type (virtual machines, hosts, or bare metal)
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **COUNT:** The total number of workloads that meet dashboard filters
+- **CLOUD COUNT:** The total number of Clouds represented by the selected workloads
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **AVERAGE UTILIZATION:** The computed average utilization figure for all workloads selected by dashboard filters
+
+## Utilization List
+
+In addition to the totals and graph displayed, two workload lists are given showing the least utilized workloads by cost (lowest utilization per cost dollar) and the least utilized workloads overall (lowest utilization overall). These workloads are listed with links to the Instance or server detail pages, along with other details related to price and resource utilization.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..066cbfa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 522,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..23d7166
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,316 @@
+# HPE Alletra MP Storage
+
+## Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
+
+Before you set up Active-Active Peer Persistence (AAPP) replication, ensure that the following requirements are met:
+
+**Supported configurations**
+
+- Remote Copy is configured using either Fibre Channel (RCFC) or IP (RCIP).
+- Replication targets are synchronous only.
+- HPE Alletra MP B10000 arrays are running OS version 10.5.0 or later.
+- AAPP replication supports only a 1:1 target mapping.
+
+**Array configuration (outside VM Essentials)**
+
+- Complete the AAPP Remote Copy configuration on both primary and secondary arrays.
+- Configure replication ports and define targets on both arrays.
+- Configure a Quorum Witness for the arrays.
+
+For more information about array configuration, see HPE GreenLake for Block Storage UI 2.5 User Guide.
+
+**VM Essentials setup**
+
+- Add both primary and secondary arrays as Storage Servers in Infrastructure > Storage > Server.
+- Create a datastore on both the primary and secondary Storage Servers.
+
+## Add HPE Alletra MP Storage
+
+### About this task
+
+The first step is to create a storage server in HPE Morpheus Enterprise. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in HPE Morpheus Enterprise
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
+
+## Create Datastore
+
+### About this task
+
+Add a Datastore to the Storage Server.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+### Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
+
+## Create Instance
+
+### About this task
+
+Create an Instance with the Datastore.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. In the Instances tab, Click the + ADD button
+3. From the ADD INSTANCE wizard input the following: 
+
+   - From the TYPE section: Select “HVM”
+   - Click NEXT
+
+     ![../../_images/create-instance-type.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - From the GROUP tab, input the following:
+
+     GROUP:
+     :   Select the Group for the Instance
+
+     CLOUD:
+     :   Select the Cloud for the Instance
+
+     NAME:
+     :   Name for the Instance in HPE Morpheus Enterprise
+   - Click NEXT
+
+     ![../../_images/create-instance-group.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - From the CONFIGURE tab, input the following:
+
+     LAYOUT:
+     :   Select the Layout for the Instance
+
+     PLAN:
+     :   Select the Plan for the Instance
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section
+
+     NETWORK:
+     :   Add Networks to the Instance
+
+     IMAGE:
+     :   Select the Image for the Instance
+
+     HOST:
+     :   Select the cluster host for the Instance
+
+     Other configurations may be added as needed.
+
+     ![../../_images/create-instance-configure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click NEXT
+   - Add Automation Tasks, if needed
+   - Click NEXT
+   - Review the Instance configuration
+   - Click COMPLETE![../../_images/create-instance-review.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+### Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
+
+## Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see Add HPE Alletra MP Storage.
+
+### Viewing the Summary page
+
+The Summary tab displays system information, capacity utilization of the system, and the number of ransomware alerts detected
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomware alerts detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
+   - **Protection**
+
+     Using the Filter by drop-down list, you can view the protection status for a `VM` or an `Instance`.
+
+     This tile displays the snapshot protection and remote replication status of both virtual machines (VMs) and instances on the storage system. You can also view the total percentage of VMs or Instances that are protected. Protection is determined based on snapshot availability with or without remote replication. The protection data is auto-refreshed periodically.
+
+     NOTE
+
+     Hover over the information (i) icon beside each field to display the description.
+
+     For VMs, the following information is displayed:
+     - **Snapshot:** Count of VMs where each volume has a point-in-time snapshot.
+     - **Remote Replication:** Count of VMs that have replicated volumes.
+     - **Snapshot + Remote Replication:** Count of VMs that have replicated volumes, where each volume also has a point in time snapshot.
+     - **Unprotected:** Count of VMs that have neither replicated volumes nor point-in-time snapshot on any volume.
+
+     For Instances, the following information is displayed:
+     - **Snapshot:** Count of instances where every volume associated with each VM has a point-in-time snapshot.
+     - **Remote Replication:** Count of instances where every volume associated with each VM is replicated.
+     - **Snapshot + Remote Replication:** Count of instances where each associated VM has replicated volumes and every volume has a point-in-time snapshot.
+     - **Unprotected:** Count of instances where each associated VM neither has replicated volumes nor point-in-time snapshot on any volume.
+     - **Partially Protected:** Count of instances where some, but not all, of the instance's VMs have snapshots and can be in remote replication.
+
+### Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
+
+### Volumes tab
+
+#### Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
+
+#### Editing volumes
+
+##### About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+##### Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see .
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json b/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
new file mode 100644
index 0000000..158bd0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+  "title": "Packages",
+  "ordinal": 312,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md b/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
new file mode 100644
index 0000000..5b58eca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
@@ -0,0 +1,130 @@
+# Packages
+
+## Overview
+
+Packages are code files used to define HPE Morpheus Enterprise resources, which can then be uploaded and used in any HPE Morpheus Enterprise appliance they may be needed in. HPE Morpheus Enterprise packages (.morpkg, .mpkg, or .mopkg) are added in the Administration > Integrations > Packages section of the UI. HPE Morpheus Enterprise packages contain Library and automation objects, such as Instance Types, Layouts, Node Types, Tasks, Spec Temples and Cluster Layouts. Following upload of a valid package, the defined HPE Morpheus Enterprise resources are immediately available for use in the appliance.
+
+The addition of `/administration/packages` is primarily targeted for uploading future HPE Morpheus Enterprise-provided packages, however users can create, distribute and/or import custom HPE Morpheus Enterprise packages too. This section goes over the process for writing and preparing packages for upload to a HPE Morpheus Enterprise appliance.
+
+## Role Permissions
+
+Access and capabilities for the **Packages** section is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Plugins`
+:   - None: Cannot access Admin: Plugins section
+    - Full: Access to Admin: Plugins and ability to upload HPE Morpheus Enterprise packages (`.morpkg`, `.mpkg`, or `.mopkg`)
+
+## Getting Started
+
+Packages consist of two primary parts, a `.json` manifest file (which sets some metadata about the package) and one or more `.scribe` files which define the resources to be added. These files are zipped and imported into HPE Morpheus Enterprise as one file (`.morpkg`, `.mpkg`, or `.mopkg`). Scribe files are written in HCL (Hashicorp Configuration Language) and follow referenced resource naming. In the next section, we will define the required attributes for both the `.json` manifest and the scribe files with examples.
+
+When uploading packages to HPE Morpheus Enterprise, keep in mind that the same packages can be reinstalled as many times as desired. When the same package is reinstalled, any local changes to those resources made in the HPE Morpheus Enterprise appliance will be overwritten. For example, if a Task has been created by package and changes are made locally to the Task config within HPE Morpheus Enterprise, subsequent uploads of the packages would overwrite those changes. A better method for making changes to package-sourced resources would be to update the package code, increase the version number, and upload the package once again. This ensures important local changes would not be overwritten by subsequent uploads. There is no warning given in the UI, changes are simply overwritten without notice.
+
+Additionally, it’s worth noting that while packages can be deleted (🗑 icon on the packages detail page), you will simply delete the package from the list. HPE Morpheus Enterprise will show a helpful list of resources added with the package if cleanup is desired but will not delete them.
+
+## Creating Packages
+
+As noted in the last section, a package consists of a `.json` manifest file and any number of `.scribe` files. We’ll first look at the manifest file, its purpose, and attributes that must be included in the JSON map.
+
+A typical package manifest looks like this:
+
+```
+```
+{  
+    "type": "scribe",  
+    "name": "morpheus-ubuntu-22.04-vmware",  
+    "code": "morpheus-ubuntu-22.04-vmware",  
+    "organization": "morpheus",  
+    "version": "20240415"  
+}
+```
+```
+
+The manifest includes each of the following attributes:
+
+- **TYPE:** Tells HPE Morpheus Enterprise to process all included files with the package as scribe files. Currently, this is the only supported type
+- **NAME:** This is the name for the package that will appear in HPE Morpheus Enterprise UI. The example manifest above came from a package that adds resources for an Ubuntu 22.04 library item to HPE Morpheus Enterprise, and is named to indicate that
+- **CODE:** Not visible in UI but exists for referencing the package via HPE Morpheus Enterprise API
+- **ORGANIZATION:** Appears only in the database but can be exposed via HPE Morpheus Enterprise API
+- **VERSION:** Listed in HPE Morpheus Enterprise UI and is useful for tracking changes over time to package-sourced resources
+
+Scribe files are quite a bit more complicated and have not yet been fully documented publicly. Nevertheless, we can show a couple examples here and give strategies for extracting additional examples from your own environment. Certain resources will require reference to other resources included with the scribe file. Here’s a simple scribe file creating a shell script-type “Hello World” Task:
+
+```
+```
+resource "task" "HelloWorld" {  
+  name = "HelloWorld"  
+  uuid = "2c2306e0-3b30-4886-b8a3-d1362c9b9490"  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  executeTarget = "resource"  
+  labels = [ "export" ]  
+  lastUpdated = "2024-04-19T19:18:40.000Z"  
+  options = [  
+    { optionType = { code = "shell.sudo" }, value = "on" },  
+    {  
+      content = { uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0" }  
+      optionType = { code = "script" }  
+    }  
+  ]  
+  taskType = { code = "script" }  
+}  
+resource "file-content" "ff5de589-75da-48ec-ba66-5fe5905397b0" {  
+  uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0"  
+  content = "echo \"Hello World\""  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  lastUpdated = "2024-04-19T19:15:47.000Z"  
+}
+```
+```
+
+In this case, the Task config was written locally in the Add/Edit Task modal within HPE Morpheus Enterprise rather than sourced from elsewhere (such as a Github repository). The Task content itself is a distinct resource and is referenced in the Task resource by UUID. Outside resources can also be referenced by HCL referenced resource naming such as in the following example where a `workload-type` resource references a `virtual-image` resource:
+
+```
+```
+resource "virtual-image" "vmware_vsphere_image_morpheus_almalinux_9_20240324" {  
+  code = "vmware_vsphere_image_morpheus_almalinux_9_20240324"  
+  category = "vmware.vsphere.image.morpheus.almalinux"  
+  name = "Morpheus AlmaLinux 9 XX-DATE-XX"  
+  imageType = "vmdk"  
+  remotePath = "https://s3-us-west-1.amazonaws.com/morpheus-images/vmware/20240324/almalinux-9/morpheus-almalinux-9-x86_64-20240324.ovf"  
+  imagePath = "vmware/20240324/almalinux-9"  
+  isCloudInit = true  
+  systemImage = true  
+  installAgent = true  
+  osType {  
+    code = "almalinux.9.64"  
+  }  
+  zoneType = "vmware"  
+}  
+resource "workload-type" "vmware_almalinux_9" {  
+  code = "vmware-almalinux-9"  
+  shortName = "almalinux"  
+  name = "AlmaLinux 9"  
+  ports = [22]  
+  containerVersion = "9"  
+  entryPoint = ""  
+  mountLogs = "/var/log"  
+  statTypeCode = "vm"  
+  logTypeCode = "vm"  
+  showServerLogs = true  
+  category = "almalinux"  
+  cloneType = "almalinux"  
+  priorityOrder = 0  
+  serverType = "vm"  
+  providerType = "vmware"  
+  containerPorts = [{code = "almalinux.22"}]  
+  actions = [{code = "generic-remove-node"}]  
+  checkTypeCode = "containerCheck"  
+  virtualImage = virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324  
+  provisionType = "vmware"  
+  backupType = "vmwareSnapshot"
+```
+```
+
+The specific virtual image is referenced as `virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324`.
+
+To go further, you can generate additional examples from your own environments. Use the [Import/Export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html#import-and-export) feature built into HPE Morpheus Enterprise and export your created resources into integrated Git repositories. When viewing the results in your repositories, you’ll see the resources are exported as scribe files.
+
+## Preparing and Uploading Packages
+
+To prepare the package, ensure the manifest and scribe files are gathered into one directory. You’ll then need to zip the contents of that directory with a valid extension (`.morpkg`, `.mpkg`, or `.mopkg`). In Linux, from outside the directory, you can use: `zip -j <package-name>.mpkg <directory-name>/*`. The package is now ready to be uploaded. Navigate to Administration > Integrations > Packages on any appliance and use the file picker tool to upload your new package file.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json b/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
new file mode 100644
index 0000000..d8e2991
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+  "title": "Storage Considerations",
+  "ordinal": 5,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md b/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
new file mode 100644
index 0000000..f5cb6e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
@@ -0,0 +1,47 @@
+# Storage Considerations
+
+Upon initial installation HPE Morpheus Enterprise takes up less than 10 GB of space, however HPE Morpheus Enterprise Services, Virtual Images, Backups, Logs, stats, and user-uploaded and imported data require adequate space on the HPE Morpheus Enterprise Appliance(s) based on appliance configuration and activity. HPE Morpheus Enterprise recommends at least 200 GB as a general figure to start from but storage needs will vary dramatically based on each specific use case. In some cases, significantly more space will be needed.
+
+IMPORTANT
+
+It is the customer’s responsibility to ensure adequate storage space per configuration and use case. The appliance should be properly monitored to ensure it does not run low on disk space.
+
+## Default Paths
+
+`/opt/morpheus`
+:   Morpheus Application and Services Files
+
+`/var/opt/morpheus`
+:   User, Application and Services Data, including default config Opensearch, RabbitMQ and Database data, default Virtual Image path, and working directory for Backups
+
+`/var/opt/morpheus/morpheus-ui` (HA Installations Only)
+:   In an HA Installation, a NFS share is required and mounted to this location. Virtual Images, Plugins, and other shared files are stored at this path to be accessible for all nodes
+
+`/home`
+:   Morpheus service account home data, such as configuration files
+
+`/var/log`
+:   Morpheus Service logs
+
+`/tmp`
+:   Storage for any temp files created by Morpheus or the operating system
+
+## Images
+
+Virtual Images can be uploaded to HPE Morpheus Enterprise Storage Providers for use across Clouds. By default when no Storage Provider has been added, images will write to `/var/opt/morpheus/morpheus-ui/vms`. Please ensure adequate space when uploading Images using local file paths.
+
+## Backups
+
+HPE Morpheus Enterprise can offload snapshots when performing backups to local or other Storage Providers. By default when no Storage Provider has been added, backups will write to `/var/opt/morpheus/bitcan/backups/`. When using none NFS Storage providers, the backup file(s) must be written to `/var/opt/morpheus/bitcan/working/` before they can be zipped, sent to the destination Storage provider such as S3, and removed from `/var/opt/morpheus/bitcan/working/`. Please ensure adequate space in `/var/opt/morpheus/bitcan/` when offloading Backups.
+
+NOTE
+
+The backup /working and /backups paths are configurable in morpheus.rb with bitcan[‘working\_directory’] = ‘$path’ and bitcan[‘backup\_directory’] = ‘/tmp’
+
+## VM Logs and Stats
+
+When using HPE Morpheus Enterprise with a locally-installed Elasticsearch configuration, VM, Container, Host and Appliance logs and stats are are stored in Elasticsearch. Please ensure adequate space in `/var`, specifically `/var/opt/morpheus/elasticsearch` in relation to the number of Instances reporting logs, log frequency, and log retention count. With partition space at 85% filled or higher (by default), Elasticsearch will enter an unhealthy state and the HPE Morpheus Enterprise appliance will not function properly.
+
+## HPE Morpheus Enterprise Services Logs
+
+Logs for services local to the HPE Morpheus Enterprise Appliance, such as the Morpheus UI, elasticsearch, rabbitmq, mysql, nginx and guacd are written to `/var/log/morpheus/`. Current logs are rotated nightly, zipped, and files older than 30 days are automatically removed. Misconfigured services, ports and permissions can cause excessive log file sizes.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json b/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
new file mode 100644
index 0000000..98b0bbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+  "title": "Terraform Blueprints",
+  "ordinal": 137,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md b/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
new file mode 100644
index 0000000..da01f14
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
@@ -0,0 +1,42 @@
+# Terraform Blueprints
+
+Terraform Blueprints are one way that Terraform can be integrated and leveraged with HPE Morpheus Enterprise, with the other being the HPE Morpheus Enterprise Terraform provider which is not discussed in this section. HPE Morpheus Enterprise and Terraform are complimentary technologies which together can increase efficiency and simplify automation across cloud environments. For more on this relationship, see our [whitepaper](https://www2.morpheusdata.com/Morpheus-and-Terraform) on how HPE Morpheus Enterprise and Terraform are better together.
+
+Currently, HPE Morpheus Enterprise supports provisioning Apps based on Terraform Blueprints to VMware, Amazon, Azure, and Oracle Clouds with additional Cloud support coming in future releases. On first attempt to provision a Terraform App, HPE Morpheus Enterprise will automatically install Terraform. It is possible in some operating system configurations for this automated installation process to fail, requiring you to install Terraform manually. If needed, manual installation instructions and guidance are provided [here](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-installation).
+
+To create a new Terraform Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Terraform. NEXT
+
+![../../../_images/new_blueprint.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-65A40826-21ED-4A71-83F9-0951FA0B62B7-high.png)
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The Terraform Configuration section is where the Terraform template file (.tf) is added or linked to the Blueprint. Using a Config Type of “Terraform (.tf)” or “Terraform JSON (.tf.json)”, you can write or paste your configuration directly into the new Blueprint. Alternatively, you can pull in config files from an integrated Git repository using the “Git Repository” Config type.
+
+In the Terraform Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “Terraform (.tf)” or “Terraform JSON (.tf.json)” to create or paste configuration directly into the new Blueprint
+- **CONFIG:** Enter your configuration here
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section or HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+In the Terraform Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section of HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+Once finished, click COMPLETE.
+
+Your new Terraform Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json b/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
new file mode 100644
index 0000000..e064ca4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+  "title": "Cancelling Workflow Tasks",
+  "ordinal": 117,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html",
+  "topic_cluster": {
+    "clustering_title": "Cancelling Workflow Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md b/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
new file mode 100644
index 0000000..58a17e8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
@@ -0,0 +1,11 @@
+# Cancelling Workflow Tasks
+
+When a Workflow is running, HPE Morpheus Enterprise offers the capability of cancelling a Task and stopping any subsequent Tasks from starting. When viewed later in History or Executions, this leaves the Task and Workflow in a cancelled state. This is useful if you have a very long-running Task that you know will fail and wish to cancel or if you want to prevent a “retryable” Task from running again.
+
+To cancel a Workflow, open the execution. Within the running Task will be a cancel button, click the button to interrupt the Workflow. Once cancelled, see that the Workflow and Task are now considered to be in a cancelled state which is shown in the UI. At this point the cancel button becomes a retry button and the Task could be resumed if desired.
+
+NOTE
+
+Cancelling a Task doesn’t actually interrupt the process already running on the workloads themselves. It simply interrupts the Workflow and stops it from continuing. Behind the scenes, HPE Morpheus Enterprise allows the running process to complete or time out rather than risk corrupting data with a non-graceful interrupt.
+
+![../../_images/cancelTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-47300BA8-9B05-428D-835A-1975B04DE84E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json b/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
new file mode 100644
index 0000000..9941a0e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+  "title": "Provisioning Workflow Execution Phases",
+  "ordinal": 113,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Workflow Execution Phases",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md b/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
new file mode 100644
index 0000000..f1ee446
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
@@ -0,0 +1,18 @@
+# Provisioning Workflow Execution Phases
+
+| Phase | Description | Usage Example | Notes |
+| --- | --- | --- | --- |
+| Configuration | Tasks are run prior to initial calls to the specified cloud API to initiate provisioning | Call to an external platform to dynamically generate a hostname prior to kicking off provisioning or dynamically altering configuration of a Catalog Item prior to provisioning |  |
+| Price | Price Phase Tasks are only invoked when the Workflow is tied to a Layout. Like the Configuration Phase, these Tasks are run prior to any calls made to the target Cloud API and allow pricing data to be overridden for the Workload being provisioned. A “spec” variable containing Instance config is passed into the Task and a specific return payload is expected in order to work properly. Any other pricing (such as on the Service Plan) is overridden. See the section below for a detailed example of this Phase being used. | An MSP customer calling out to a custom pricing API to deliver Instance pricing to their own customers. | See the section below on Price Phase implementation for a detailed setup example. |
+| Pre Provision | For VMs, Tasks are run after the VM is running and prior to any Tasks in the Provision phase. For containers, Tasks in this phase are run on the Docker host and prior to `docker run` | Prepare a Docker host to run containers | Pre Provision can be used for a Blueprint so it is added before a script which is set at the Provision phase executes. Pre Provision for scripts is mainly for Docker as you can execute on the host before the container is running. |
+| Provision | Like pre‐provision, Tasks for VMs are run after the VM is running. For containers, these Tasks are run on the containers once they are running on the host. For many users, this is the most commonly‐used phase. | Join the server to a domain | Tasks included with in the Provision phase are considered to be vital to the health of the Instance. If a Task in the Provision phase fails, the Workflow will fail and the Instance provisioning will also fail. Tasks not considered to be vital to the existence of the Instance should go in the Post Provision phase where their failure will not constitute failure of the Instance. |
+| Post Provision | Tasks are run after the entire provisioning process has completed | Disable UAC or Windows Firewall on a Windows box or join Active Directory | When adding a node to an Instance, Tasks in this phase will be run on all nodes in the Instance after the new node is provisioned. This is because Post Provision operations may need to affect all nodes, such as when joining a new node to a cluster. Tasks in Pre Provision and Provision phases would only be run on the new node in this scenario. |
+| Start Service | Tasks in this phase are intended to start the service associated with the Instance type. | Include a script to start the service associated with the Instance (such as MySQL) which will execute when the Start Service action is selected from the Instance detail page | Start services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Stop Service | Tasks in this phase intended to stop the service associated with the Instance type. | Include a script to stop the service associated with the Instance (such as MySQL) which will execute when the Stop Service action is selected from the Instance detail page | Stop services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Pre Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, prior to the deploy taking place. | Extract files from a deploy folder and move them to their final positions prior to deploy | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, after the deploy has completed | Update configuration files or inject connection details from the environment at completion of the deploy process | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Reconfigure | Tasks in this phase are run when the reconfigure action is made against an Instance or host | Rescan or restart the Instance after a disk is added |  |
+| Teardown | Tasks are run during VM or container destroy | Remove Active Directory objects prior to tearing down the Instance |  |
+| Scale Down | Tasks are run when a node is removed from an Instance. This does not apply to Clusters when a worker node is removed. |  |  |
+| Shutdown | Tasks are run immediately before the target is shutdown | Send an update on Instance power state to a CMDB |  |
+| Startup | Tasks are run immediately before the target is started | Send an update on Instance power state to a CMDB |  |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json b/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
new file mode 100644
index 0000000..0457fbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+  "title": "VDI Pools",
+  "ordinal": 272,
+  "parent_title": "Tools",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html",
+  "topic_cluster": {
+    "clustering_title": "VDI Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md b/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
new file mode 100644
index 0000000..eda78d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
@@ -0,0 +1,383 @@
+# VDI Pools
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json b/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
new file mode 100644
index 0000000..2faacc1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+  "title": "Workflows",
+  "ordinal": 112,
+  "parent_title": "Automation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html",
+  "topic_cluster": {
+    "clustering_title": "Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md b/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
new file mode 100644
index 0000000..1c877bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
@@ -0,0 +1,17 @@
+# Workflows
+
+Workflows are groups of Tasks, which are described in detail in the preceding section. Operational Workflows can be run on-demand against an existing Instance or server from the Actions menu on the Instance or server detail page. Additionally, they can be scheduled to run on a recurring basis through Morpheus Jobs (Provisioning > Jobs).
+
+Provisioning Workflows are associated with Instances at provision time (in the Automation tab of the Add Instance wizard) or after provisioning through the Actions menu on the Instance detail page. Provisioning Workflows assign Tasks to various stages of the Instance lifecycle, such as Provision, Post Provision, and Teardown. When the Instance reaches a given stage, the appropriate Tasks are run. Task results and output can be viewed from the History tab of the Instance or server detail page.
+
+**Subtopics**  
+
+- **[Provisioning Workflow Execution Phases](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html)**
+- **[Add Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html)**
+- **[Retrying Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html)**
+- **[Cancelling Workflow Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html)**
+- **[Price Phase Task Utilization](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html)**
+- **[Nesting Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html)**
+- **[Edit Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html)**
+- **[Delete Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json b/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
new file mode 100644
index 0000000..747f224
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+  "title": "Library Integrations",
+  "ordinal": 164,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Library Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md b/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
new file mode 100644
index 0000000..f5e80d1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
@@ -0,0 +1,3 @@
+# Library Integrations
+
+The integrations section within HPE Morpheus Enterprise Library lists existing integrations and allows for the creation of new integrations which are related to automation technologies. A complete list of integrated third party technologies is available in the Administration section (Administration > Integrations). More detailed information about each HPE Morpheus Enterprise integration with third party technologies is included in our [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) section.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json b/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
new file mode 100644
index 0000000..ec1ac67
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+  "title": "Roles",
+  "ordinal": 276,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md b/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
new file mode 100644
index 0000000..4d42246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
@@ -0,0 +1,28 @@
+# Roles
+
+There are two Role types in HPE Morpheus Enterprise, Tenant Roles and User Roles. Understanding these Role types is key to effectively administering Role permissions in HPE Morpheus Enterprise. These two Role types are discussed in greater detail in this section.
+
+## Tenant Roles
+
+Tenant Roles set the maximum permission levels for Users in the Tenant. User Role permissions will not exceed the permissions of the Tenant Role.
+
+- Tenant Roles set the maximum permissions for a Tenant
+- User Roles in a Tenant cannot exceed the permissions of the Tenant Role
+- A Tenant Role can be assigned to one or multiple Tenants
+- Tenant Roles determine Cloud access for the child Tenant such that all Clouds in the parent Tenant which have visibility set to Public will show as options in the Tenant Role Cloud Access tab
+- Only parent Tenant Clouds given access in the Tenant Role will be accessible in the Subtenant
+
+IMPORTANT
+
+Tenant Roles cap permissions on all Subtenant User Roles. User Roles can be created in the Subtenant with lesser permissions than the Tenant Role allows. Tenant Roles are designed for a parent Tenant Admin to set max permissions for the Subtenant, and a child Tenant Admin to configure User Roles inside the Tenant.
+
+## User Roles
+
+User Roles determine feature, Group, and Instance Type access for all Users. In a multi-Tenant environment, there are two types of User Roles: Single-Tenant User Roles and Multi-Tenant User Roles.
+
+- **Single-Tenant User Roles:** These exist solely in the Tenant they are created in
+- **Multi-Tenant User Roles:** Parent Tenants can create Multi-Tenant User Roles. These Roles are automatically seeded into child Tenants and can be assigned to Users within that Tenant. Changes to Multi-Tenant User Roles made in the parent Tenant are propagated to all children. However, once a Multi-Tenant User Role is edited inside the child Tenant, it is no longer linked to the Multi-Tenant User Role and becomes its own unique single-Tenant Role. It will no longer receive propagated changes.
+
+NOTE
+
+Multi-Tenant User Roles are intended to make Subtenant User Role creation easier, so parent Tenant administrators do not have to re-create the same base Subtenant Users Roles for every Subtenant. Multi-Tenant User Roles are not a single Role across Tenants, but more like a template that creates new Subtenant User Roles that can then be managed in the Sub Tenant.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json b/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
new file mode 100644
index 0000000..8ccbfc2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+  "title": "Software Licenses",
+  "ordinal": 329,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html",
+  "topic_cluster": {
+    "clustering_title": "Software Licenses",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md b/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
new file mode 100644
index 0000000..3bb018e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
@@ -0,0 +1,53 @@
+# Software Licenses
+
+## Overview
+
+The License section is for automating the application of Licenses to Instances while provisioning. Licenses can be added to HPE Morpheus Enterprise and then attached to images. HPE Morpheus Enterprise will then apply the license to Instances provisioned using the images with license attached. Licenses can be configured for single or multiple Tenants.
+
+### Creating Licenses
+
+#### Procedure
+
+1. Select + Create License
+2. In the New License modal, enter the following: 
+
+   - License Type
+     :   Windows
+   - Name
+     :   Name of the License in HPE Morpheus Enterprise
+   - License Key
+     :   Enter the License Key
+   - Org Name
+     :   The Organization Name (if applicable) related to the license key
+   - Full Name
+     :   The Full Name (if applicable) related to the license key
+   - Version
+     :   The License Version
+   - Copies
+     :   The Number of copies available on the License
+   - Description
+     :   License description displayed in the Licenses list in HPE Morpheus Enterprise, helpful for identifying the License after creation
+   - Virtual Images
+     :   Search for existing Virtual Images by name and select to attach the image to the license.
+         :   NOTE
+
+             Virtual Images are synced from Clouds or added in the Library > Virtual Images section.
+   - Tenant Permissions
+     :   Search for and select the Tenant(s) the License will be available for. Multiple Tenants can be added.
+3. Save Changes
+
+### Provisioning with Licenses
+
+When a Virtual Image is added to a license, HPE Morpheus Enterprise will automatically apply the License to Instances configured with the Virtual Image during provisioning, including Instance Types with a Node Type that is configured with the Virtual Image, or if the image is selected when using generic Cloud Instances types (VMware, AWS, Nutanix, Openstack etc). Virtual Images can be removed from a License by editing the License.
+
+### Managing Licenses
+
+Created Licenses details are displayed in the License page, including the number of copies applied per License, the Tenants added to the License, and the Virtual Images attached to the License.
+
+The Name, Version, Copies, Description, Virtual Images and Tenant Permissions are editable but selecting the Actions dropdown on a License.
+
+NOTE
+
+License Types, Keys, Org Names and Full Names are not editable after a license has been created.
+
+License can also be removed using the Actions dropdown on a License.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json b/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
new file mode 100644
index 0000000..ae91fb4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+  "title": "Add Amazon ALB load balancer",
+  "ordinal": 492,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ALB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md b/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
new file mode 100644
index 0000000..8865034
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
@@ -0,0 +1,33 @@
+# Add Amazon ALB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ALB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-81281149-FB28-4485-B1B1-957E0FCE24AE-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json b/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
new file mode 100644
index 0000000..fd9e273
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+  "title": "Load Balancers",
+  "ordinal": 225,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md b/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
new file mode 100644
index 0000000..58bf2bc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
@@ -0,0 +1,9 @@
+# Load Balancers
+
+Infrastructure  >  Load Balancers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html)**
+- **[Orchestrating Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json b/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
new file mode 100644
index 0000000..75cc2cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+  "title": "Infrastructure",
+  "ordinal": 167,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md b/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
new file mode 100644
index 0000000..3efab8d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
@@ -0,0 +1,15 @@
+# Infrastructure
+
+The heart of HPE Morpheus Enterprise is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html)**
+- **[Boot](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json b/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
new file mode 100644
index 0000000..06815b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+  "title": "Prerequisites",
+  "ordinal": 248,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md b/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
new file mode 100644
index 0000000..a78c45a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
@@ -0,0 +1,39 @@
+# Prerequisites
+
+In order to work with HPE Morpheus Enterprise bare metal PXE boot capabilities, some initial setup configuration is required. First, on the HPE Morpheus Enterprise server, if you have a firewall enabled, make sure port 69 is open for TFTP. HPE Morpheus Enterprise actually uses port 6969 and during installation a redirect should have been set. To check this, SSH onto the Morpheus server and run the following:
+
+```
+```
+iptables -t nat -L -n -v
+```
+```
+
+If the redirect is still properly, the response should include the following:
+
+```
+```
+Chain PREROUTING (policy ACCEPT 69 packets, 9767 bytes)  
+pkts bytes target   prot opt in out source     destination  
+0     0 REDIRECT udp  --  *  *   0.0.0.0/0  0.0.0.0/0        udp dpt:69 redir ports 6969  
+0     0 DNAT     tcp  --  *  *   0.0.0.0/0  169.254.169.254  tcp dpt:80 to:192.168.1.156
+```
+```
+
+Next, in HPE Morpheus Enterprise, set a default PXE root password. This password is set in Administration > Settings > Provisioning. With the default root password set, set up the redirect on the DHCP server. In addition to the DNS and Gateway settings, add Boot Server Host Name which will be the name of the HPE Morpheus Enterprise Server and Bootfile Name which should be set to `pxelinux.0`. If you are using a Linux-based DHCP server, for example on CentOS, the dhcpd.conf configuration will look something like the following:
+
+```
+```
+allow booting;  
+allow bootp;  
+option option-128 code 128 = string;  
+option option-129 code 129 = text;  
+next-server xx.xx.xx.xx;  
+filename "pxelinux.0";
+```
+```
+
+NOTE
+
+Replace the dummy IP address in the example dhcpd.conf file above with your HPE Morpheus Enterprise appliance IP address.
+
+Once you have done this, when you boot a PXE-enabled machine on the network, it will be told to access the HPE Morpheus Enterprise server and request the `pxelinux.0` file. It will do this on port 69, the default for TFTP and will be redirected to 6969 once it hits the HPE Morpheus Enterprise server. If successful you will see the “HPE Morpheus Enterprise PXE Server” menu when you boot a server. This is the default menu defined in HPE Morpheus Enterprise and supports the shipped PXE images supplied with the product. By selecting any of the choices from the “HPE Morpheus Enterprise PXE Server menu”, the install files should be downloaded and the server configured as per the supplied kickstart files. At this point, back on the HPE Morpheus Enterprise appliance, you should see the MAC address for the new server appear in the “Discovered MAC Addresses” tab of the Infrastructure > Boot page.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..1907f46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 268,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json b/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
new file mode 100644
index 0000000..8960011
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+  "title": "Create a Single Tenant User Role",
+  "ordinal": 303,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html",
+  "topic_cluster": {
+    "clustering_title": "Create a Single Tenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md b/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
new file mode 100644
index 0000000..0359ccd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
@@ -0,0 +1,15 @@
+# Create a Single Tenant User Role
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Leave the “Multi-tenant Role” checkbox blank.
+6. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+7. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..646a6bc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 216,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..e604edf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,13 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Floating IPs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E_2.html)**
+- **[Security Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json b/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
new file mode 100644
index 0000000..d658162
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+  "title": "ITSM",
+  "ordinal": 488,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html",
+  "topic_cluster": {
+    "clustering_title": "ITSM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md b/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
new file mode 100644
index 0000000..5ec0c68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
@@ -0,0 +1,7 @@
+# ITSM
+
+**Subtopics**  
+
+- **[Service Now](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html)**
+- **[Cherwell](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html)**
+- **[Remedy](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json b/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
new file mode 100644
index 0000000..23f2c6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+  "title": "Image Types",
+  "ordinal": 148,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html",
+  "topic_cluster": {
+    "clustering_title": "Image Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md b/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
new file mode 100644
index 0000000..b8e2b6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
@@ -0,0 +1,7 @@
+# Image Types
+
+HPE Morpheus Enterprise provides a vast System Image repo with pre-configured images for every Cloud. All other images are User Images. User images can be added directly to HPE Morpheus Enterprise, or automatically synced from integrated clouds. It is important to configure synced User Images for metadata, including specifying the Platform and User Credentials, prior to provisioning. Provisioning a User Image that has not been configured may result in failed provisioning.
+
+IMPORTANT
+
+Synced User Images need to be configured prior to provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json b/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
new file mode 100644
index 0000000..c147ae2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+  "title": "Feature Access Permissions",
+  "ordinal": 300,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md b/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
new file mode 100644
index 0000000..f6065b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
@@ -0,0 +1,257 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in HPE Morpheus Enterprise. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering HPE Morpheus Enterprise, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where HPE Morpheus Enterprise administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within HPE Morpheus Enterprise is done on this page. On the License tab information about the current HPE Morpheus Enterprise license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default HPE Morpheus Enterprise backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within HPE Morpheus Enterprise. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of HPE Morpheus Enterprise UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of HPE Morpheus Enterprise constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for HPE Morpheus Enterprise guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the HPE Morpheus Enterprise Health and HPE Morpheus Enterprise Logs tabs. | The Health pages provide an overview of HPE Morpheus Enterprise health, notifications from integrations, and the current HPE Morpheus Enterprise‐ui log. | This permission is recommended for those responsible for administering and troubleshooting HPE Morpheus Enterprise. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between HPE Morpheus Enterprise and the identity provider. | Full permission is recommended for those responsible for integrating HPE Morpheus Enterprise with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in HPE Morpheus Enterprise. HPE Morpheus Enterprise may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where HPE Morpheus Enterprise monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend HPE Morpheus Enterprise functionality. | This permission is recommended for those responsible for extending HPE Morpheus Enterprise functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within HPE Morpheus Enterprise, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via HPE Morpheus Enterprise API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of HPE Morpheus Enterprise UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | HPE Morpheus Enterprise includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within HPE Morpheus Enterprise when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with HPE Morpheus Enterprise and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for HPE Morpheus Enterprise Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where HPE Morpheus Enterprise Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize HPE Morpheus Enterprise deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. The "Group" permission level allows Users to see only the Load Balancers tied to Groups they can access. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating HPE Morpheus Enterprise with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in HPE Morpheus Enterprise. | This permission is recommended for appliance administrators. See other sections of HPE Morpheus Enterprise documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, EfficientIP SolidServer, Microsoft DNS, PowerDNS, Route 53, and more. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: Server Software | None, Read, Full | Determines access to the Software tab on server detail pages. The ‘Full’ permission level surfaces a SYNC button on the Software tab, users with ‘Read’ permission do not see the SYNC button. | The Software Tab of a server detail page is where the list of installed software packages for the server are shown. |  |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of HPE Morpheus Enterprise is available. | This permission is recommended for those responsible for defining HPE Morpheus Enterprise‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within HPE Morpheus Enterprise UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of HPE Morpheus Enterprise UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of HPE Morpheus Enterprise UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for HPE Morpheus Enterprise DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into HPE Morpheus Enterprise Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within HPE Morpheus Enterprise |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within HPE Morpheus Enterprise. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in HPE Morpheus Enterprise or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default HPE Morpheus Enterprise landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the HPE Morpheus Enterprise environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through HPE Morpheus Enterprise API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows HPE Morpheus Enterprise to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in HPE Morpheus Enterprise only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed HPE Morpheus Enterprise Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | HPE Morpheus Enterprise will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes HPE Morpheus Enterprise to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, List, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “List” permission allows only listing Cypher entries in HPE Morpheus Enterprise UI and API. The “Read” permission allows listing in addition to decrypting them via automation for used in scripts and Tasks. The “User” permission will allow access similar to “Read” though only for Cypher objects the user owns, in addition to allowing for creation of Cypher entries. The “Full” permission allows creation and “Read” access to all Cypher entries regardless of who created them. The “Full Decrypt” permission gives the same rights as “Full” with the added privilege of decrypting the secret values for plaintext viewing. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The HPE Morpheus Enterprise Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. HPE Morpheus Enterprise then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json b/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
new file mode 100644
index 0000000..1e3d0ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+  "title": "Infoblox",
+  "ordinal": 507,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html",
+  "topic_cluster": {
+    "clustering_title": "Infoblox",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md b/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
new file mode 100644
index 0000000..c3aa98b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
@@ -0,0 +1,153 @@
+# Infoblox
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+- Use script variables like <%= variableX %> for evaluation of the key data in extended attributes
+
+## Adding Infoblox Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise Infoblox integration requires credentials for an Infoblox user account with API access granted, access to list the pools and zones you wish to work with, and rights to create and destroy records. See Infoblox documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network - Integrations`
+2. Select + ADD > IPAM > Infoblox
+3. Enter the following: 
+
+   ![../../_images/infoblox_settings_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-98F9FF7B-AC47-4C2E-B21B-FAE2E4D79468-high.png)
+
+   NAME
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable the Integration
+
+   URL
+   :   Infoblox wapi url. Example: <https://yourInfobloxHost/wapi/v2.10.5>
+
+       TIP
+
+       The target Infoblox host wapi version can be referenced at <https://yourInfobloxHost/wapidoc/>
+
+   USERNAME
+   :   Infoblox user username
+
+   PASSWORD
+   :   Infoblox user password
+
+   THROTTLE RATE
+   :   In milliseconds (ms)
+
+   DISABLE SSL SNI VERIFICATION
+   :   Leave selected to disable SSL SNI Verification
+
+   INVENTORY EXISTING
+   :   Mark this option to inventory existing network pools from Infoblox
+
+   NETWORK FILTER
+   :   Filter which networks are synced into HPE Morpheus Enterprise. Example: Network Filter: `network_view=default&*Building=work`
+
+   ZONE FILTER
+   :   Filter terms for Zone Records
+
+   TENANT MATCH ATTRIBUTE
+   :   This can be set to the name of the extended attribute in Infoblox where HPE Morpheus Enterprise will check for the id of a morpheus tenant. This allows for setting the tenant’s HPE Morpheus Enterprise id to an extended attribute field on a network view or network in Infoblox, and when the network or view is discovered by morpheus, it will be auto assigned to the right tenant.
+
+   IP MODE
+   :   Static IPs or DHCP Reservations
+
+   EXTRA ATTRIBUTES
+   :   Accepts a JSON input of custom attributes that can be saved on host records in Infoblox. These Must be first defined as extra attributes in Infoblox and values can be injected for the user creating the record and the date of assignment. The available injectable attributes are: userId, username, and dateCreated.
+
+       ```
+       ```
+       {  
+         "Date Assigned":"<%=dateCreated%>",  
+         "Requestor":"<%=username%>",  
+         "Request Number":"<%=userId%>"  
+       }
+       ```
+       ```
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the Infoblox IPAM integration will be created and the following will sync:
+
+- Infoblox networks will be synced in and populate in the Infrastructure - Network - IP Pools tab and in the Infoblox detail page under the NETWORK POOLS tab
+- Host Records will sync and populate in the Network Pool detail view (select an IP Pool name to view)
+- DNS Zones will sync and populate under Infrastructure - Network - Domains and in the Infoblox detail page under the HOSTS tab
+- DNS Zone Records will sync and populate
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Infoblox IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Infoblox IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time (if desired)
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP Pools or Infrastructure  >  Network  >  Services  >  Infoblox
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addhostrecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-06C4001C-7079-484B-93C0-F78B6A6000CE-high.png)
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+
+   DOMAIN
+   :   Select an Infoblox Zone
+
+   Create DNS Records
+   :   Select to create DNS A and PTR Records in Infoblox
+4. Select SAVE CHANGES
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select a Domain from Infrastructure  >  Network  >  Domains or Infrastructure  >  Network  >  Services  >  Infoblox  >  Zones
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addzonerecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9A893000-4821-4C0D-8205-5F43B0CBF5F3-high.png)
+
+   NAME
+   :   Name for the record, such as Hostname
+
+   Type
+   :   A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+
+   CONTENT
+   :   Content of the record, such as IP or A Record
+
+   TTL
+   :   Time To Live value
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json b/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
new file mode 100644
index 0000000..aa60197
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+  "title": "3-Node HA Upgrade",
+  "ordinal": 23,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html",
+  "topic_cluster": {
+    "clustering_title": "3-Node HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md b/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
new file mode 100644
index 0000000..f1d16ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
@@ -0,0 +1,301 @@
+# 3-Node HA Upgrade
+
+3-Node HA Appliances represent 3 App nodes with local RabbitMQ and Opensearch services clustered across the app nodes, and an external MySQL cluster.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be obtained from My HPE Software Center. Reach out to your account manager with any questions regarding access.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for any 3-node variations using externalized MySQL, Opensearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+WARNING
+
+Upgrades can add additional storage load on database nodes. Please refer to database storage requirements within 3nodeinstall before upgrading.
+
+### 3-Node HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3-Node HA configurations to v8.1.1.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. With the upgrade package downloaded and transferred to each application node, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once the Node 1 upgrade has completed and the UI is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work, consult the related article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/Configure-Morpheus-to-utilize-and-alternate-port-for-SSL?language=en_US).
+
+#### 3-Node Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the ui is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once Node 2 upgrade has completed and the ui is available, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### 3-Node HA CentOS / RHEL Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3 Node HA configurations to v8.1.1.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once Node 1 upgrade has completed and the UI is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the RPM package on Node 3 and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### 3-Node Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1. 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the u is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Then upgrade the RPM package on Node 3, then run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json b/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
new file mode 100644
index 0000000..fb4f724
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+  "title": "Installing and Integrating an External Cypher Appliance",
+  "ordinal": 240,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html",
+  "topic_cluster": {
+    "clustering_title": "Installing and Integrating an External Cypher Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md b/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
new file mode 100644
index 0000000..637b70c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
@@ -0,0 +1,55 @@
+# Installing and Integrating an External Cypher Appliance
+
+The external Cypher appliance runs on a small separate VM and supports a variety of base OS distributions. Credentials are securely passed to the external appliance and can be retrieved and consumed in specific places within HPE Morpheus Enterprise UI. The download URL for the installer can be retrieved from HPE Morpheus Enterprise [Hub](https://app.morpheushub.com/), replace the placeholder URL in the instructions below with the correct URL for the latest version of the Cypher appliance.
+
+Begin by provisioning and updating the VM for the Cypher appliance. Then, download the installer. The following steps go through the installation process on Ubuntu but, as mentioned in the previous paragraph, many popular distributions are supported.
+
+```
+```
+# An example URL is shown below, find the URL for the latest version and for the correct distro at |morpheus| Hub  
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-cypher_$version_amd64.deb
+```
+```
+
+Next, install and reconfigure the package.
+
+```
+```
+sudo dpkg -i morpheus-cypher_$version_amd64.deb  
+sudo morpheus-cypher-ctl reconfigure
+```
+```
+
+After the installation and reconfigure is complete, we need to record the generated API key so we can integrate the external Cypher store with HPE Morpheus Enterprise in a later step. We can get this from the logs with the following command:
+
+```
+```
+sudo morpheus-cypher-ctl tail  
+==> /var/log/morpheus-cypher/cypher/current <==  
+2022-02-02_15:22:27.84848 |  \/  (_) ___ _ __ ___  _ __   __ _ _   _| |_  
+2022-02-02_15:22:27.84848 | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|  
+2022-02-02_15:22:27.84848 | |  | | | (__| | | (_) | | | | (_| | |_| | |_  
+2022-02-02_15:22:27.84848 |_|  |_|_|\___|_|  \___/|_| |_|\__,_|\__,_|\__|  
+2022-02-02_15:22:27.84849   Micronaut (v3.2.2)  
+2022-02-02_15:22:27.84849  
+2022-02-02_15:22:28.09130 15:22:28.087 [main] INFO  i.m.context.env.DefaultEnvironment - Established active environments: [ec2, cloud]  
+2022-02-02_15:22:30.15129 15:22:30.151 [main] INFO  c.m.cypher.service.CypherService - Root Data: null  
+2022-02-02_15:22:30.83499 15:22:30.834 [main] INFO  c.m.cypher.service.CypherService - Initialized Root Token: c90xxxx00000xxxxxx000000xxxxx000 ... Write this down as it will only display once  
+2022-02-02_15:22:32.01282 15:22:32.012 [main] INFO  io.micronaut.runtime.Micronaut - Startup completed in 4749ms. Server Running: http://localhost:8080
+```
+```
+
+IMPORTANT
+
+The API key is only shown once when the appliance is first installed. Securely store this API key for later reference or you will be unable to integrate this Cypher appliance with any other HPE Morpheus Enterprise appliances.
+
+This completes the installation process, move to HPE Morpheus Enterprise UI to integrate the remote Cypher store with HPE Morpheus Enterprise. Cypher integrations are added in Infrastructure > Trust > Integrations. Click + ADD and then click Cypher. Configure the following:
+
+- **NAME:** A name for the Cypher integration in HPE Morpheus Enterprise
+- **ENABLED:** When checked, this Cypher integration is available for storing and retriving credentials
+- **API HOST:** The URL where your Cypher appliance can be reached (ex. <https://x.x.x.x/>)
+- **API KEY:** The API Key we retrieved and saved in the previous step
+
+![../../_images/addCypherInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37B0DB77-147F-4EA0-BD49-CB4DA1253ED4-high.png)
+
+Click SAVE CHANGES to save the new integration. Refer to the “Credentials” section above for details on storing new credential sets using the external appliance and how they can be called back in various places throughout the UI.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..16b2447
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 267,
+  "parent_title": "Tools",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..edd5456
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json b/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
new file mode 100644
index 0000000..698108f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+  "title": "Add F5BigIP load balancer",
+  "ordinal": 496,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html",
+  "topic_cluster": {
+    "clustering_title": "Add F5BigIP load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md b/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
new file mode 100644
index 0000000..9f97966
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
@@ -0,0 +1,61 @@
+# Add F5BigIP load balancer
+
+## About this task
+
+NOTE
+
+- The HPE Morpheus Enterprise integration with F5 only supports basic authorization. Token-based authorization is not currently supported.
+- The F5 API handles SSL certificate installation by downloading the certificate from a URL the user provides. HPE Morpheus Enterprise provides the “Appliance URL” configured in global settings (Administration > Settings > Appliance) to satisfy that requirement. Make sure you have configured a valid URL in this field and that F5 can reach it.
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. Select **F5 BigP** from the drop-down list. 
+
+   The NEW LOAD BALANCER panel opens.   
+   ![F5 LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FBE17C69-EA72-449A-9EAC-9529F57EFA38-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   Select the load balancer group.
+
+   CLOUD
+   :   Select the load balancer cloud.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions
+
+   API HOST
+   :   Enter IP or resolvable host name url.
+
+   API PORT
+   :   Enter the API port number. Typically it will be `8443`.
+
+   USERNAME
+   :   Enter the API user name.
+
+   PASSWORD
+   :   Enter the API user password.
+
+   MANAGEMENT URL
+   :   Enter the management URL. For example, <https://10.30.20.31:8443/xui/>
+
+   Advanced Options (optional)
+   :   - ALLOW VIP ENTRY: Select this parameter to list the VIP pools.
+       - VIP POOL: Select from the drop-down list.
+       - VIRTUAL NAME: Enter a virtual name.
+       - POOL NAME: Enter a virtual name.
+       - SERVER NAME: Enter a server name.
+5. Click **Save Changes**.
+
+**Subtopics**  
+
+- **[Add Load Balancer to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html)**
+- **[F5 Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
new file mode 100644
index 0000000..e463d72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+  "title": "Catalog",
+  "ordinal": 82,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
new file mode 100644
index 0000000..70dcae2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
@@ -0,0 +1,41 @@
+# Catalog
+
+The Catalog presents a simplified self-service view where users can select and deploy Instances, Blueprints or Workflows with pre-defined configuration in just a few clicks and without presenting an overwhelming list of options. Selections are presented as tiles and users can add items to a cart as if shopping on an eCommerce website. For users who tend to provision regularly from a small selection of Instance Types and configurations, the catalog is an easier option compared with the much more detailed and option-rich Instance provisioning wizard.
+
+## Configuring Catalog Item Access
+
+Within the Catalog, users are presented with selections based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items. Thus, administrators will need to enable access to some Catalog Items in order for users to make use of this view.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Catalog
+
+The catalog shows the complete list of predefined items available to the user for provisioning. Catalog items are not created here, however. For more on creating catalog items, see the Catalog Items tab in the HPE Morpheus Enterprise [Library section](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items) (Library > Blueprints > Catalog Items).
+
+![../../_images/catalog.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ED6FCF79-BB81-4C2B-B4A6-4DCB7357CFB5-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning. The catalog shows a complete list of items but the list can be filtered by entering search terms or by selecting a category. When adding or editing catalog items, an optional category may be set which aids in filtering for environments which have a lot of catalog items to select from.
+
+![../../_images/orderPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3AE2F03E-DBC7-4FC1-BED0-DB5F6B096D9F-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![../../_images/cart.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CE0F030E-A45D-4412-92D9-38608B669FC9-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can now be viewed from their respective list pages. Depending on whether you’ve ordered an Instance, App, or Workflow execution, navigate to the appropriate list page for your item to view it.
+
+## Order Detail
+
+![../../_images/orderHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D954DA2F-C2AD-4BD7-B7C3-02CE5AEF0719-high.png)
+
+The Order Detail page includes a complete list of orders and some basic details about them. If the item still exists, you can link through to the detail page for the item (whether that be Instance detail, App detail, or Execution detail). When the item name is not hyperlinked, the item has been deleted but the record of the order remains in the history.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json b/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
new file mode 100644
index 0000000..8d14864
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+  "title": "Boot",
+  "ordinal": 246,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html",
+  "topic_cluster": {
+    "clustering_title": "Boot",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md b/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
new file mode 100644
index 0000000..3d410c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
@@ -0,0 +1,11 @@
+# Boot
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html)**
+- **[Mapping](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html)**
+- **[Boot Menus](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html)**
+- **[Answer Files](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html)**
+- **[Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..b242c7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 146,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..2519669
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,9 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html)**
+- **[Image Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json b/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
new file mode 100644
index 0000000..45ef2c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+  "title": "Load Balancers",
+  "ordinal": 491,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md b/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
new file mode 100644
index 0000000..f5bbf89
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
@@ -0,0 +1,13 @@
+# Load Balancers
+
+**Subtopics**  
+
+- **[Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html)**
+- **[Add Amazon ELB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html)**
+- **[Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html)**
+- **[Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html)**
+- **[Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html)**
+- **[Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html)**
+- **[Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html)**
+- **[Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html)**
+- **[Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..8a16ac6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 33,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..f2596c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,27 @@
+# Proxies
+
+## Overview
+
+In many situations,companies deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this HPE Morpheus Enterprise provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. HPE Morpheus Enterprise is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the HPE Morpheus Enterprise appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and `no_proxy` are set appropriately.
+
+## Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within HPE Morpheus Enterprise we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
+
+## Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
+
+## Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprints as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, HPE Morpheus Enterprise will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the `No Proxy` rules for proxy exceptions.
+
+## Docker
+
+When provisioning Docker based hosts within a Proxy environment it is up to the user to configure the docker host proxy configuration manually. There are workflows that can be configured via the Automation engine to make this automatic when creating docker based hosts. Please see documentation on Docker and proxies for specific information.
+
+Proxy setups can vary widely from company to company, and it may be advised to contact support for help configuring morpheus to work in the proxy environment.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json b/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
new file mode 100644
index 0000000..2c9867a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+  "title": "Monitoring and Completion",
+  "ordinal": 427,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring and Completion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md b/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
new file mode 100644
index 0000000..ce5774c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
@@ -0,0 +1,15 @@
+# Monitoring and Completion
+
+## Procedure
+
+1. Monitor job progress from the Job Executions tab.
+2. Execution time may range from 15 minutes to over one hour, depending on:
+   1. Number of servers
+   2. Deploy mode
+   3. Selected content
+   4. Firmware and driver versions on the target servers
+3. Upon completion, detailed logs are available in the Job Executions tab.
+
+   - Do not enter any values in Custom Config.
+   - Servers are not automatically rebooted as part of the update process.
+     - If a reboot is required to complete updates, it must be performed manually at a time appropriate for the hosted services.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json b/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
new file mode 100644
index 0000000..2169822
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+  "title": "Ansible Tower",
+  "ordinal": 377,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Tower",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md b/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
new file mode 100644
index 0000000..8879583
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
@@ -0,0 +1,184 @@
+# Ansible Tower
+
+## Overview
+
+HPE Morpheus Enterprise supports Ansible Tower for configuration management. HPE Morpheus Enterprise accomplishes this by integrating with an existing instance running Ansible Tower (AT) 3.3.0-1 and earlier. The username and password required for integration can be a user with admin access or a user with project admin access
+
+HPE Morpheus Enterprise will import the current Inventory, Templates, Hosts, Groups and Projects. In the integration view it will add a Job tab which will have information of all the jobs executed from HPE Morpheus Enterprise.
+
+NOTE
+
+This integration will not import data of the jobs which are not executed from HPE Morpheus Enterprise.
+
+## Add Ansible Tower Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Ansible Tower”
+3. Populate the following fields: 
+
+   - Name: Name of the Ansible Tower Integration in HPE Morpheus Enterprise
+   - Enabled: To disable the integration, uncheck this option
+   - Ansible Tower URL: An HTTPS or HTTP Ansible Tower URL
+   - Username: The user HPE Morpheus Enterprise would use to communicate with Ansible Tower
+   - Password: Enter the password. Password is encrypted and saved in DB
+   - API Version: This drop down has one option (`v2`) for now but may have others in future
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Scope Ansible Tower Integration to a Cloud
+
+### About this task
+
+All instances provisioned in this cloud will have the Ansible Tower config option during provisioning. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Scope Ansible Tower Integration to a Group
+
+### About this task
+
+All instances provisioned in this Group will have the Ansible Tower config option during provisioning in any cloud part of the Group. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Tower Integration added, an Ansible Tower section will appear in the Config section of the provisioning wizard. By default, Ansible Tower is enabled, but can be disabled by expanding the Ansible Tower section and unchecking Enable Ansible Tower.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible Tower
+:   Select to bootstrap
+
+Inventory
+:   A list of Inventory available in Ansible Tower will appear in the drop down. Select an existing inventory. The instance will be added to the inventory selected.
+
+Ansible Group
+:   Enter the name of a new or an existing Group in the inventory selected above.
+
+Template
+:   Select an existing template or select the option ‘Create New Template’. If ‘Create New Template’ is selected below fields will appear and are mandatory
+    :   Template Name
+        :   Enter the template name
+
+        Project
+        :   Select an existing project from the drop down options
+
+        Playbook
+        :   Select a playbook from the dropdown to be associated with the template. Note: HPE Morpheus Enterprise doesn’t store a local copy of the playbooks visible in Ansible Tower. SCM or local path for playbooks should be maintained in Ansible Tower.
+
+Execute Mode
+:   Select one of the options from the dropdown
+    :   Limit to instance
+        :   This will execute the template on the instance provisioned.
+
+        Limit to Group
+        :   This will execute the template on all hosts attached to the group entered in the ‘Ansible Group’ field.
+
+        Run for all
+        :   This will execute the template on all hosts in the inventory
+
+        Skip execution
+        :   This will skip the execution of the template on the instance provisioned.
+
+## Scoping Ansible Tower Jobs to Tenant-Default Inventories
+
+Users in the Primary Tenant have an additional Inventory execution option when creating Ansible Tower Job-type Tasks. When making a selection in the Inventory field, “Use Tenant Default” may be selected rather than a specific Inventory. This is because Ansible Tower Jobs created in the Primary Tenant may be shared publicly to other Tenants through public Workflows or when associated with public Library items.
+
+![../../_images/ansibleTowerInventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-628F3A54-3E8C-4986-8502-5ADA96A0ACC6-high.png)
+
+When this option is selected and the Task is run in a Subtenant, it will automatically be run against the default Inventory which is configured for the Subtenant. The next section includes steps for associating Tenants and default Inventories.
+
+IMPORTANT
+
+An Ansible Tower Job configured to run against a Tenant-default Inventory will fail when run by a user whose Tenant does not have a default Inventory set.
+
+### Setting Default Inventories for Tenants
+
+When creating or editing Ansible Tower integrations, navigate to the Inventory tab to view all Inventories synced from the selected integration. Click “Permissions” inside the “MORE” action menu at the end of a row for the selected Invetory. Within the PERMISSIONS modal, there is a single typeahead field where a Tenant can be selected. Once the Tenant is selected, click SAVE CHANGES. Now back on the Inventory list view, you’ll see the default Tenant which is associated with each Inventory.
+
+NOTE
+
+Tenants may only be associated with one Inventory, though an Inventory can have multiple Tenant associations. If a Tenant is selected to be associated with a new Inventory, its association with a previous Inventory will automatically be removed.
+
+![../../_images/inventoryList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8724DEA8-C761-416C-81CA-D3F82E6177B8-high.png)
+
+## Ansible Tower Configuration
+
+When using an Ansible Tower task type or associating the Ansible Tower integration with a cloud/group, there are a few options that can be configured:
+
+- Inventory
+- Group
+- Job Template
+- Execute Mode
+
+### Prompt at Launch
+
+Some options used to configure your deployments have the related option of **Prompt at Launch** in Ansible Tower, which should be enabled on the template to be chosen in the **Job Template** field. If **Prompt at Launch** is not enabled, the values configured on the template in Ansible Tower will be used instead. **Prompt at Launch** can be seen below on the **Inventory** and **Limit** fields:
+
+![../../_images/ansibleTowerPromptAtLaunch.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4731D3C6-EE0D-46A5-A78C-DD7235B7A582-high.png)
+
+### Group
+
+The **Group** field is optional but a group can be entered into the field to associate the host to, in the target inventory. If the group is existing, then the instance will be associated as a host to that group. If the group does not exist, the group will be created and the instance will be associated as a host to that group.
+
+![../../_images/ansibleTowerGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-048E8C28-2E88-4711-B75F-2E8EEB9FA747-high.png)
+
+### Inventory
+
+When provisioning on a cloud with a configured Ansible Tower integration or using an Ansible Tower task type against an instance, the instance will be added as a host to the inventory chosen in the **Inventory** field. As mentioned, if specified, these instance will be associated with groups in the inventory as well. When using an inventory that syncs from a project, the instance will still be added as a host in the inventory, in addition to the sync’d inventory. This means that Ansible Tower will aggregate the manually added hosts from HPE Morpheus Enterprise with the sync’d project inventory. However, if the **Overwrite** option is enabled on the source for the project that contains the inventory, any hosts added by HPE Morpheus Enterprise **will be overwritten**. In some cases, a separate HPE Morpheus Enterprise inventory may be desired, if **Overwrite** is required on your sources.
+
+![../../_images/ansibleTowerOverwrite.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ECAFBE4F-9B9C-42E0-86EE-30B3860FFEBF-high.png)
+
+## Passing extra\_vars to Ansible Tower Job
+
+When provisioning or when running Ansible Tower Jobs as HPE Morpheus Enterprise Tasks, you may pass the `extra_vars` stack to the Tower Job. First, ensure the Job Template has extra variables “Prompt on Launch” enabled as shown below:
+
+![../../_images/towerExtraVars.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4C836374-5A94-4045-AE04-99B90A2F4F9F-high.png)
+
+The sample Playbook below is associated with the Tower Job Template.
+
+```
+```
+---  
+- hosts: all  
+vars:  
+  Opensource_Team: "Customer"  
+tasks:  
+- name: Print Hello World  
+  debug:  
+    msg:  
+    - "Hello World {{ Opensource_Team }}. Here are Morpheus extra_vars: {{ morpheus }}"
+```
+```
+
+After executing the Tower Job, we can see the variable stack surfaced into the results as defined in the Playbook:
+
+![../../_images/towerResults.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-47CAE600-317C-468B-B98F-69522E132DE4-high.png)
+
+## Use Case
+
+You have Job template(s) in Ansible Tower to do post build config after the OS is deployed. The playbook with roles and tasks to do post build will add specific users and groups, install required packages, remove packages, disable services, change config for ntp, resolv, hosts etc. You want to add the instance to an existing Group/Inventory in Tower.
+
+You can achieve this by adding the Ansible Tower Integration and then scope it to a Cloud or Group. While provisioning an instance, in the config stage you have the Ansible Tower section with option to select the post build job template, select the Inventory and provide an existing Group Name or if the Group doesn’t exist Morpheus will create it and submit for provisioning.
+
+Morpheus will provision the instance, once it is in the finalize state where the instance has an ip and has completed domain join if required, added user(s) or User Groups if specified then HPE Morpheus Enterprise will add the instance to the inventory and Group and run the Template which will do all the post build of the server.
+
+The output of the post build template execution can be see under Instance history.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..8bfb159
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 220,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..e5c75db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,34 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+## Overview
+
+The IP Pools tab in the Networks section allows you to create HPE Morpheus Enterprise-type IP Pools (which is an IP address range HPE Morpheus Enterprise can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
+
+## To add a HPE Morpheus Enterprise Network Pool
+
+### Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in HPE Morpheus Enterprise.
+
+       Pool Type
+       :   Currently HPE Morpheus Enterprise-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from HPE Morpheus Enterprise
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+### Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json b/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
new file mode 100644
index 0000000..ba72b1c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+  "title": "Executions",
+  "ordinal": 95,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html",
+  "topic_cluster": {
+    "clustering_title": "Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md b/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
new file mode 100644
index 0000000..d2b4d49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
@@ -0,0 +1,31 @@
+# Executions
+
+Executions contains the execution status and history from Task and Operational Workflow Executions run from Library > Automation > Tasks and Library > Automation > Workflows. Executions for Tasks and Workflows are split out to their own labeled tabs.
+
+NOTE
+
+Tasks and Workflows executed from a Job or from Instance or Host `Actions` do not populate in the Executions Section, and can be referenced from the History tab on the target resource. All task and Workflow executions can be referenced in Operations  >  Activity  >  History
+
+Execution results in the ui display:
+
+NAME
+:   Name of the Task or Workflow Executed
+
+TYPE
+:   Type of execution (Task or Workflow)
+
+START DATE
+:   Date and time of execution
+
+ETA/DURATION
+:   Estimate time of completion for executions in progress, or the total execution time for completed executions.
+
+RESULTS
+:   Result status of execution (Succeeded, Failed, In-Progress or Pending)
+
+Execution Detail (i)
+:   Click on the `i` to view process output results
+
+    NOTE
+
+    Job and automation executions can be expanded to show process details by clicking on the arrow icon immediately to the right of the NAME column.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..35cbc1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 196,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..22efae8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json b/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
new file mode 100644
index 0000000..2b7eae4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+  "title": "User Groups",
+  "ordinal": 310,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html",
+  "topic_cluster": {
+    "clustering_title": "User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md b/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
new file mode 100644
index 0000000..3542af6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
@@ -0,0 +1,49 @@
+# User Groups
+
+## Overview
+
+User Groups can be selected during provisioning to add each group members credentials to the Instance. User Groups can be configured for sudo access and in Linux will assign Group members to a groupId in linux.
+
+## Creating User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select + CREATE USER GROUP.
+4. Enter the following: 
+
+   NAME
+   :   Name of the User Group
+
+   DESCRIPTION
+   :   Optional User Group Description
+
+   SERVER GROUP
+   :   Name of the groupId to assign Group members to in linux.
+
+   SUDO ACCESS
+   :   Enable to give Group members sudo access
+
+   USERS
+   :   Search for and select existing Users to add to the User Group.
+5. Select SAVE CHANGES.
+
+## Editing User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select the ACTIONS dropdown next to the target User Group.
+4. Select EDIT
+5. Make changes, add or remove users from the group.
+6. Select SAVE CHANGES.
+
+## Adding a User Group when Provisioning
+
+### Procedure
+
+1. When provisioning, in the CONFIG section expand the USER section.
+2. Select an existing Group from the USER GROUP dropdown.
+3. Users will be created for members in the selected User Group on the provisioned Instance(s).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json b/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
new file mode 100644
index 0000000..b89effb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+  "title": "Local Storage - Boot Volume Selection During Instance Creation",
+  "ordinal": 455,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md b/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
new file mode 100644
index 0000000..a41e474
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
@@ -0,0 +1,9 @@
+# Local Storage - Boot Volume Selection During Instance Creation
+
+Table 1. Boot Volume Selection During Instance Creation
+
+        | S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Boot volume not found | Device UID mismatch or not yet discovered | - Confirm device discovery is complete - Verify the UID in the storage controller | - | Wait for discovery to complete and retry. |
+| 2 | `ResourceMissingAtURI` errors | Redfish device discovery is not complete | - Verify Redfish discovery status - Confirm the device is visible in Redfish inventory | - | Retry after a short wait. |
+| 3 | Script cannot find the device | UID format mismatch or missing disk link | - Verify `/dev/disk/by-id/` entries  - Confirm correct disk UID format | - | Ensure disk links are correctly mapped and retry. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..3a9902e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 170,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..df2fa64
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,13 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html)**
+- **[HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html)**
+- **[Kubernetes Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html)**
+- **[Docker Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html)**
+- **[EKS Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html)**
+- **[GKE Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html)**
+- **[OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json b/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
new file mode 100644
index 0000000..44aa5c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+  "title": "Deployments",
+  "ordinal": 99,
+  "parent_title": "Code",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html",
+  "topic_cluster": {
+    "clustering_title": "Deployments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md b/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
new file mode 100644
index 0000000..27f1af5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
@@ -0,0 +1,110 @@
+# Deployments
+
+NOTE
+
+In v5.3.2+, Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+
+The deployments section provides very useful PaaS like capabilities when it comes to deploying applications into the newly provisioned environment. These can be uploaded directly from the UI, pulled from a build server, pulled from a public or private Git repository or even via the API and the various plugins created, such as Jenkins, and Gradle to support continuous build / integration workflows.
+
+A deployment can be considered a set of versions that relate to a particular project or application being deployed. This allows one to keep track of a history of versions and easily reuse these deployment versions across Instances that may exist in different environments. An example might be to deploy a version from a deployment to a staging Instance and (once approved) also deployed into production.
+
+## Role Permissions
+
+Access and capabilities for the **Deployments** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+## Getting Started
+
+Getting started with deployments is easy. They can vary slightly for the application stack being deployed but the simplest phase of a deployment is adding a version and adding the appropriate files to the deployment archive that are needed for the application to run. This could be a single file like a WAR file for Tomcat, or it could be hundreds of files for stacks like Ruby on Rails.
+
+There are a few ways to create a deployment. The first is to use the Provisioning ‣ Code ‣ Deployments section of the application to create them. Simply add a new deployment and give it a name representing the application that is being deployed. Once a deployment is created select the deployment to view its versions (which will be empty to start). Next, it is time to add a version.
+
+When adding a version there are several options. There are 3 types represented by the UI. These include File, Fetch, and Git respectively. A File deployment allows the user to simply drag their files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees (If files exist in subfolders then only the Chrome browser is supported due to browser limitations at the time of this writing). This is also the common type that is represented when files are uploaded via the CLI, or available build tool integration plugins. Once the files have completed their upload simply save the version for use.
+
+### Git
+
+For performing git based deploys HPE Morpheus Enterprise supports both public and private repositories. To utilize a private git repository the add version dialog will display a public keypair that can be added to the git service for authentication purposes. Currently this keypair is shared across the account and not specifically scoped to the user so it may be advisable to connect this integration to a deployment account in git. From here either a ssh or `https` git url can be entered along with a git branch or tag name. Once the version is saved, this repository will be copied down into the deployment archive for use.
+
+### Fetch
+
+Fetch based deployments are pretty straightforward. Simply enter a url to a file representing the deployment. This can be a single file (in which case it will just be added to the deployment archive singularly) or it can be a zip file (which will automatically be expanded into the archive). HTTP Authentication options can also be entered if the url requires some form of basic authentication scheme for access by the appliance.
+
+## Configuring Library Items for Deployments
+
+In order to have the UI tools available to utilize Deployments with a provisioned Instance, the Library items must have certain configurations set. Once configured correctly, any Instance provisioned from the Library item would then have access to any of your Deployments.
+
+First, within the **Instance Type** (Library > Blueprints > Instance Types), ensure the SUPPORT DEPLOYMENTS attribute is marked. This is off by default so it will need to be manually enabled on all relevant Instance Types. Next, you’ll want to ensure you have the correct DEPLOY FOLDER configured on **Node Types** (Library > Blueprints > Node Types). This is the mount point which will be replaced by the contents of your Deployments. Finally, you will want the **Provisioning Workflows** associated with the Library item to have the proper Tasks configured within its Pre-Deploy and/or Deploy phases. Tasks in the Pre-Deploy phase are run as soon as the Deployment is triggered from the UI prior to any other Deploy actions taking place. This could be used, for example, to extract files from the deploy folder and move them to their final destinations before the primary deploy actions take place. Tasks in the Deploy phase are run after the deployment is completed, such as if you wanted to update configuration files or inject connection details from the environment after the completion of the deploy process.
+
+## Deploying to an Instance
+
+Now that the Deployment object and Library items are configured, it is easy to push that deployment out to any Instance provisioned within HPE Morpheus Enterprise by navigating to the specific Instance that it needs deployed to. On the Instance detail page there is a tab called Runtime and within it another tab labeled Deploy. From here simply add a deploy. The dialog will ask firstly from which deployment the deploy is from (or allow you to create a new one on the spot), and secondly which version to deploy (also with the option to add one on the fly). The next step of the wizard will display any configuration options that might be specific to the Instance type being deployed to (i.e. CATALINA\_OPTS for Tomcat or Java Command for java) as well as the file explorer and deployment type selections for review (or use when creating a new version on the fly). Fill in the required items then simply hit complete. The deploy will now be asynchronously sent off to all of the virtual machines or containers within the Instance in a rolling restart and the deployment status will be represented.
+
+TIP
+
+When deploying to an Instance, the custom configuration options that were entered during the previous deployment are automatically carried forward allowing one to edit them or leave them as is.
+
+## Rolling Backwards and Forwards
+
+Because of the tracked history of deployments kept within HPE Morpheus Enterprise, the deploy tab of Instance detail makes it easy to choose a previously run deployment and jump back to it in the event of a failed deployment. The history will automatically be updated and the configuration, as well as data from the previous deployment state of the Instance will be restored.
+
+## Offloading Storage
+
+Since a full history of the backup builds are kept in HPE Morpheus Enterprise, as the appliance grows it becomes necessary to change where these are stored. On a fresh install these are stored on the local appliance in `/var/opt/morpheus` or wherever the master account may have changed the configuration to point to. It is also possible to adjust the deployment archive store by creating a Storage Provider tied to an S3 compatible object store, Openstack Swift object store, or any other type of mountpoint provided. This option can be adjusted in Administration > Settings > Provisioning once a storage provider is created within the account.
+
+## Add Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the + Add button.
+5. Enter a Name for the deployment and a description (optional)
+6. Click the Save Changes button to save.
+
+## Add Version
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the Name of the deployment you would like to add a version to.
+5. Click the Add Version button.
+6. From the Add Version Wizard select the deployment type.
+7. Input the Version of the deployment.
+8. Depending on the type of deployment selected perform one of the following: 
+
+   Files
+   :   Drag files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees.
+
+   Fetch
+   :   Enter a url to a file representing the deployment.
+
+   Git
+   :   The add version dialog will display a public key pair that can be added to the git service for authentication purposes. Either a ssh or https git url can be entered along with a git branch or tag name.
+9. Click the Save Changes button to save.
+
+## Edit Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the ✎ icon on the row of the deployment you wish to edit, or click the Name of the deployment and then the Edit button from the deployment detail page.
+5. Modify information as needed
+6. Click the Save Changes button to save.
+
+## Delete Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the 🗑 icon on the row of the deployment you wish to delete, or click the Name of the deployment and then the DELETE button.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json b/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
new file mode 100644
index 0000000..368b859
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+  "title": "Costing: Tag Costing",
+  "ordinal": 64,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tag Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md b/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
new file mode 100644
index 0000000..d6a2169
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
@@ -0,0 +1,28 @@
+# Costing: Tag Costing
+
+![../_images/7tagcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3B425176-5841-4C03-B67D-F6B86603E1CD-high.png)
+
+The Tag Analysis dashboard creates groups of workloads based on the presence of specific tags and meeting other filters. This workload group can be analyzed for total cost and projected costs.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Tag key (all matched by search)
+- Metric (apply to see the top tag values by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+
+## Data Displayed
+
+The following aggregate totals (by tag) are compiled for workloads that meet set filters:
+
+- **TAGS:** The total number of unique tag keys for workloads meeting dashboard filters
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+
+## Tags List
+
+A list of each tag (key) represented on selected workloads is displayed in a list below the dashboard graphs. We also see the total number of workloads associated with the tag, the total memory, total storage, total CPU cores, and total price. If we click the “MORE” link at the end of each row, we can see a list of all tag values associated with the key.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json b/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
new file mode 100644
index 0000000..623f948
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+  "title": "Storage",
+  "ordinal": 454,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md b/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
new file mode 100644
index 0000000..f39f0c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
@@ -0,0 +1,8 @@
+# Storage
+
+The topic describes troubleshooting procedures for storage.
+
+**Subtopics**  
+
+- **[Local Storage - Boot Volume Selection During Instance Creation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..11cd742
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 168,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..69bd040
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,119 @@
+# Groups
+
+## Overview
+
+### About this task
+
+Groups in HPE Morpheus Enterprise define what resources a user has access to. Group access is defined by User Roles. Clouds are added to groups, and a User can only access the Clouds that are in the Groups their Role(s) gives them access to. Resources such as Networks, Datastores, Resources Pools, and Folders have additional Group access settings.
+
+Policies applied to a Group will be enforced on all Instances provisioned or moved into that Group.
+
+NOTE
+
+Groups are not multi-tenant. A group only exists in the tenant is it is created in.
+
+The Groups view displays all current groups, includes search feature, and also enables the addition of new groups.
+
+To View Groups:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## CLI
+
+View all groups: `groups list` To use the group: `groups use <id>` or `groups use "group name"` Json output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
+
+## API
+
+View all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` View a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
+
+## Adding Groups
+
+### About this task
+
+![../../_images/add_group.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-314860C2-E6E2-4F71-9AC0-AEE0E9E53A08-high.png)
+
+To add a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
+
+## Managing Groups
+
+### About this task
+
+![../../_images/group_view.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4D1622A4-0DFF-47E7-AFF2-B9CBC2298957-high.png)
+
+To view a Group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+### Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Policies
+:   Lists and allows creation or management of Policies applied to the Group.
+
+## Edit Group
+
+### About this task
+
+To edit a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
+
+## Delete Group
+
+### About this task
+
+To delete a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
+
+## User Access
+
+IMPORTANT
+
+User access to Groups is determined by their user Role(s). Group access for Roles can be configured in the Group Access section of a Roles Settings.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json b/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
new file mode 100644
index 0000000..fd697e2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 180,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md b/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
new file mode 100644
index 0000000..d260807
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total CEPH storage, which is presented as one large volume.
+
+HVM clusters must also live in HPE Morpheus Enterprise-type Clouds (See Infrastructure > Clouds). A pre-existing HPE Morpheus Enterprise Cloud may be used or a new Cloud could be created to handle HVM management.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..42b031f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 218,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..7312abd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,26 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+## Adding Network Groups
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in HPE Morpheus Enterprise
+       - Description: Details of the Network Group in HPE Morpheus Enterprise
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+
+   Tenant Permissions
+   :   - Resources with Public visibility will be available to users in any Tenant (subject to other RBAC controls). Resources with Private visibility are given only to individually selected Tenants. Select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json b/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
new file mode 100644
index 0000000..76315af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+  "title": "Remedy",
+  "ordinal": 490,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html",
+  "topic_cluster": {
+    "clustering_title": "Remedy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md b/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
new file mode 100644
index 0000000..a86d3d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
@@ -0,0 +1,80 @@
+# Remedy
+
+## PreRequisites
+
+The user used for this integration need to be an Administrator in Remedy or have all the permissions to the form that is outlined in the table below.
+
+Table 1.
+
+      | API Endpoint | Action | BMC Form | Existing BMC Role |
+| --- | --- | --- | --- |
+| /api/arsys/v1/entry/CTM:People | GET | CTM:People | Contact People Admin |
+| /api/arsys/v1/entry/COM:Company?q=%27Status%27=%22Enabled%22&fields=values(Company) | GET | COM:Company | Atrium Foundation Admin |
+| /api/arsys/v1/entry/User | GET | User | User Administrator |
+| /api/arsys/v1/entry/Group | GET | Group | User Administrator |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | POST | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | PUT | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | GET | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | POST | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | PATCH | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | GET | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | DELETE | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | POST | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | PATCH | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | GET | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | DELETE | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | POST | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | PATCH | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | GET | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | DELETE | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | POST | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | PATCH | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | GET | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | DELETE | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/arsys/v1/entry/AST:ComputerSystem | GET | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | PUT | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | POST | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | GET | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | PUT | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | POST | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | GET | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | PUT | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | POST | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | GET | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | PUT | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | POST | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | GET | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | PUT | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | POST | AST:Memory | Asset Admin |
+| /api/jwt/login | POST |  |  |
+
+## Add Remedy Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Remedy` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   REMEDY HOST
+   :   Url of the Remedy Instance. e.g: <http://xx.xx.xx.xx:8008>
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Remedy user’s password
+
+   COMPANY
+   :   The dropdown will populate with values as soon as the auth using the above creds are successful
+
+   APPROVAL USER
+   :   Full name of the user as it appear in Remedy. E.g: userid ‘anish’ would have full name as “Anish Abraham”
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json b/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
new file mode 100644
index 0000000..7a69ef9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+  "title": "Image Catalog",
+  "ordinal": 406,
+  "parent_title": "Image Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html",
+  "topic_cluster": {
+    "clustering_title": "Image Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md b/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
new file mode 100644
index 0000000..0423c1d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
@@ -0,0 +1,22 @@
+# Image Catalog
+
+This section describes how to upload Bare Metal (BM) operating system images into Morpheus using a configurable image repository. HPE Morpheus supports multiple backend storage options, allowing administrators to centrally manage OS images and reuse them across bare metal provisioning workflows.
+
+Uploaded images are registered under Library > Virtual Images and are made available for bare metal instance provisioning.
+
+## Supported OS Image Sources
+
+HPE Morpheus supports uploading Bare Metal OS images from the following storage backends:
+
+- Local storage on the HPE Morpheus appliance
+- S3-compatible object storage
+- CIFS (Samba) file shares
+- NFS (v3) file shares
+
+Each backend option is configured as a File Share or Storage Bucket and referenced during image upload.
+
+**Subtopics**  
+
+- **[Uploading OS Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html)**
+- **[Windows OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E55D4270-ED77-4161-8712-45824C891713.html)**
+- **[Linux OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json b/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
new file mode 100644
index 0000000..1864413
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+  "title": "Getting started with HPE Morpheus Enterprise and Azure",
+  "ordinal": 363,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md b/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
new file mode 100644
index 0000000..51c2c46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
@@ -0,0 +1,363 @@
+# Getting started with HPE Morpheus Enterprise and Azure
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with Microsoft Azure public cloud. By the end, you will integrate your first cloud with HPE Morpheus Enterprise, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our [Reddit user community forum](https://www.reddit.com/r/morpheusdata/).
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/latest/getting_started/requirements/requirements.html). In order to provision any new Instances, hosts, or applications (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a community edition license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License. For more, take a look at our community edition [welcome package](https://www.morpheusdata.com/community-welcome).
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to Groups and a user can only access Clouds that are in the Groups to which their roles give them access. More information on HPE Morpheus Enterprise Groups is [here](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html#groups). A deep dive into Groups goes beyond the scope of this guide but it’s often useful to create a Group that contains all Clouds for testing purposes. We will create that group now so that we can add our first Cloud into this Group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+Click SAVE CHANGES. Your Group is now ready to accept Clouds.
+
+![../../_images/1newGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-542A0791-5B19-4A90-A597-CF88E9A0B7F9-high.png)
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be on-prem, public clouds, or even bare metal. In this guide, we will focus on integrating and working with Microsoft Azure public cloud.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the Cloud list page which lists all configured Clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated Azure cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AZURE (PUBLIC)” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, we’re asked to provide Azure-specific details to connect to the cloud. HPE Morpheus Enterprise Azure integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET
+
+![../../_images/2createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-31D2E874-AE3E-4F65-B514-72258B2A437B-high.png)
+
+### Create App Registration
+
+#### About this task
+
+HPE Morpheus Enterprise authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with HPE Morpheus Enterprise has Owner or Contributor permissions on the specified Subscription.
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one using the steps below. If you already have one you wish to use, continue to the next section.
+
+#### Procedure
+
+1. Log into the Azure portal
+2. Select “Azure Active Directory”
+3. Select “App Registrations”
+4. Select “New Registration” 
+
+   ![../../_images/Default_Directory_App_registrations_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A57114C7-68E3-4BBA-B11D-51BC35609D3C-high.png)
+5. Next, give the app a name, specify Web app / API for the type (default) and enter any URL for the Sign-on URL:
+6. Click Create and your new App Registration will be created. 
+
+   ![../../_images/Register_an_application_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-55330F72-25B5-4408-8A33-43884CBF6D26-high.png)
+
+#### Results
+
+Now that we have our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration in the next section.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+![../../_images/morpheusAppReg_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3DD99466-18E6-40A5-A2C4-63B8D766487E-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select “Certificates & secrets” in the Manage section
+2. Select `+ New client secret` 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FEF1F839-2F89-43AA-A5F8-744B625725F0-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select an expiration duration
+6. Click Add 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-201809CC-7FE8-42EF-87DE-2FDE9015C0E9-high.png)
+7. Copy the newly-generated client secret value. 
+
+   IMPORTANT
+
+   Copy the client secret value before continuing as it will not be viewable again later.
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Copy.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-276863D1-39D2-4F67-8A52-511B32010C1B-high.png)
+8. Store/Paste client secret for use later when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have three of the four credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID which we will gather in the next section.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the Subscriptions section. The search function can help to locate these sections if they aren’t immediately apparent in the UI menu 
+
+   ![../../_images/azuresubscriptionssearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AE54CAA0-CE46-424A-ADB0-5F5C2E2521AF-high.png)
+2. In the Subscriptions section, copy the Subscription ID 
+
+   ![../../_images/Subscriptions_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2DA76817-C462-4B49-BCA8-DCBF83CA8860-high.png)
+3. Store/Paste for use as the Subscription ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory existing cloud resources, create resources or remove them.
+
+#### Procedure
+
+1. In the Subscriptions section in Azure, select the Subscription
+2. In the Subscription pane, select “Access Control (IAM)”
+3. Either Click :guilabel`+ Add`, and then “Add Role Assignment” OR simply select “Add a role assignment” 
+
+   ![../../_images/Azure_subscription_1_Access_control_IAM_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-68F85CA0-5206-4738-8FA9-11A40E6B4277-high.png)
+4. In the right pane, select “Owner” or “Contributor” Role type
+5. Search for the name of the App Registration used for the HPE Morpheus Enterprise integration
+6. Select the App Registration in the search results
+7. Select “Save” 
+
+   ![../../_images/Add_role_assignment_save.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-374258C1-E537-4439-BCE9-9F8918C369E4-high.png)
+
+#### Results
+
+You now have the required credentials and permissions to add an Azure Cloud integration into HPE Morpheus Enterprise. Continue on with the next sections of this guide to complete the integration from the HPE Morpheus Enterprise side.
+
+### Complete the Add Cloud Process in HPE Morpheus Enterprise
+
+If you’ve followed this guide from the start, you will already have a Cloud integration modal open in HPE Morpheus Enterprise UI. If you still need to open that wizard, navigate to Infrastructure > Clouds > + ADD > Azure (Public) and click NEXT. Fill in the following fields with the information gathered in the steps above:
+
+- Subscription ID
+- Tenant ID
+- Client ID
+- Client Secret
+- Location
+- Resource Group
+- Inventory Existing Instances
+- Inventory Level
+- Account Type
+
+Once valid credentials are populated in the appropriate fields, the LOCATION dropdown menu will be populated. Select an available region, this is also a helpful check to ensure you’ve correctly provided working credentials. In addition, we can scope the cloud integration to all resource groups in the region (All) or can select a specific resource group to limit HPE Morpheus Enterprise resource inventorying and creation to just that resource group.
+
+By checking INVENTORY EXISTING INSTANCES, HPE Morpheus Enterprise will automatically onboard existing cloud resources which are scoped to the region and resource group indicated. If this box is checked, we will also need to select either basic inventorying, which syncs name, IP addresses, platform types, power status, and sizing data (storage, CPU, and RAM) OR full (API heavy) inventorying which syncs resource utilization metrics (storage, CPU, and RAM) when available in addition to what we get with basic inventorying.
+
+To move on, expand the “Advanced Options” section.
+
+NOTE
+
+CSP accounts will also need to enter CSP TENANT ID, CSP CLIENT ID, and CSP CLIENT SECRET in the Advanced Options section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first Cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), **COSTING**, **DNS INTEGRATION**, **CMDB**, and **AGENT INSTALL MODE**.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” Groups if you wish to use the Group we configured earlier. Alternatively, you can create a new one here.
+
+![../../_images/3cloudGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0908B711-2897-4E7C-8C95-07D3BE88990B-high.png)
+
+Once you’ve selected or created the Group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new Cloud is now listed on the Cloud list page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the Cloud.
+
+#### Viewing Cloud Inventory
+
+Now that we’ve integrated our first Azure cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the Cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+#### Configuring Resource Pools
+
+With our Azure Cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  Resources tab. In here, we are able to see and control access to the various resource pools that have been configured in Azure. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise if it is not configured as active.
+
+![../../_images/4resourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7380FEF7-F20E-43FE-B217-9597FD1569DE-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any Group we’d like. We can also choose to make some or all of our resource pools available to every Group. Specific resource pools can also be defined as the default for each Group when needed.
+
+![../../_images/5resourcePoolGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BDAD86D8-81F9-4622-BB7D-FE2E1FCEFC1E-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+#### Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “Resources” tab to the “Data Stores” tab on our Cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![../../_images/6dataStore.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-971BB5E6-79F2-4447-9227-2000EAB24BEF-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific Groups. This ensures that the members of each Group are only able to consume the data stores they should have access to.
+
+#### Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all Clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific Cloud detail page so that networks from other Clouds are not shown.
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+Since this guide is focused on working within an Azure cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain Groups or Tenants.
+
+![../../_images/7cloudNetworks.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EB96C871-9B00-4B7B-9BBD-6800427665D5-high.png)
+
+#### Provisioning Your First Instance
+
+At this point, the groundwork is laid and we are ready to attempt our first new provisioning. As a first Instance, we’ll provision an Apache web server to our Azure cloud. HPE Morpheus Enterprise includes a very robust catalog of pre-configured Instance types. We’ll use one of these included catalog items for this guide but you’ll likely also need to prep your own custom images and Instance types to make available to your users. Much more on this can be found elsewhere in HPE Morpheus Enterprise documentation.
+
+Navigate to |ProIns|. If any Instances are currently provisioned, we will see them listed here. To start a new Instance we click + ADD to open the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/8createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-82D93BA5-71D0-4A63-9DBA-C13AE6E3C395-high.png)
+
+First, we’ll specify the Group to provision into which determines the Clouds available. If you’ve followed this guide to this point, you should at least have a Group that houses all of your Clouds which you can select here. This will allow us to select the Azure cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating Instances and available options is [here](https://docs.morpheusdata.com/en/latest/provisioning/instances/instances.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+![../../_images/9configureInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E9D875CD-D6C4-4D20-AD60-767C3A47671E-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your HPE Morpheus Enterprise user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click NEXT to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the Instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the Instance in the list to move to the Instance detail page. For now we will see a progress bar indicating that the Instance is being created and is starting up. The exact amount of time this process will take depends on selections made when provisioning the Instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the Instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+#### Creating Your First Library Item
+
+In the prior section, we manually provisioned our first Instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick Instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a HPE Morpheus Enterprise-provided image, you’ll want to ensure it’s configured. You will not be able to complete this section without selecting an available image. In this example we will use a CentOS image that was previously configured in the HPE Morpheus Enterprise library. If you need to configure your own images prior to starting this section, navigate to Library > Virtual Images and click + ADD. A deeper dive into image prep and virtual image configuration goes beyond the scope of this guide.
+
+Provisionable elements in HPE Morpheus Enterprise combine a Node Type(s), Layout(s), and an Instance Type. The [Overview section](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#overview) of HPE Morpheus Enterprise docs discusses these objects and how they work together in greater detail. Our first step here will be to create a Node Type which wrap the image itself with additional configuration, templates, and scripts. While not strictly required, creating the Node Type, Instance Type, and then the Layout is often a good workflow for creating Library items. That is the order we will follow in this guide.
+
+Navigate to Library > Blueprints > Node Types and click + ADD
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**: Example Azure CentOS 7
+- **SHORT NAME**: eac7 (Identifies the Node Type in HPE Morpheus Enterprise API/CLI)
+- **VERSION**: 7 (Ensures the correct Node Types are used when tying Layouts with multiple images to the same Instance Type)
+- **TECHNOLOGY**: Azure
+- **VM IMAGE**: Azure-Centos-7
+
+Click SAVE CHANGES
+
+![../../_images/10addNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A92C3DF6-A4AF-4C9E-8DFD-0ADC4CCEDC48-high.png)
+
+With the new Node Type created, we’ll now add a new Instance type which will be accessible from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click + ADD.
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click SAVE CHANGES. You could also provide a description, icon, and category for easier identification from the provisioning wizard later.
+
+![../../_images/11addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E5B46F39-E1FE-4EDF-9C6B-348A60C37A00-high.png)
+
+Now that we’ve created a new Instance type, access it by clicking on the name in the list of custom Instances you’ve created. In my case, I’ve given the name “Example Azure CentOS 7”.
+
+Once we’ve opened the new Instance type, by default, we should be on the “LAYOUTS” tab. Click + ADD LAYOUT. I’ve set the following fields on my example layout:
+
+- **NAME**: Example Azure CentOS 7
+- **VERSION**: 7 (This is the version number of the layout itself, which is labeled 7 in the example)
+- **TECHNOLOGY**: Azure
+- **Nodes**: Select the Node Type we created earlier, if desired you can specify multiple nodes
+
+Click SAVE CHANGES.
+
+![../../_images/12addLayout.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D60CF065-8C8D-4F3F-8068-61523120D1FE-high.png)
+
+At this point we’ve completed the setup work and can now provision the Instance we’ve created to our specifications. Navigate to |ProIns| and click + ADD. From the search bar we can search for the new Instance type we’ve created.
+
+![../../_images/13createCustomInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C1C05D91-5824-4DAD-8132-CF4EF2D46BD6-high.png)
+
+As before, we can select a Group and Cloud to provision this new Instance. Click NEXT. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new Instance type. Select a network and click NEXT. Once again we will also click NEXT through the “AUTOMATION” tab. Finally, click COMPLETE.
+
+As before when we provisioned a pre-existing Instance from the default catalog, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on the configuration and environmental factors but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the provisioning process has completed, open the Instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available, assuming the image and your custom catalog item were configured to seed user accounts and connect back to the HPE Morpheus Enterprise appliance.
+
+#### Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A Task could be a script added directly, scripts or Blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of Task types can be found in the [Automation section](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a Task, add the Task to a Workflow, and run the Workflow against a new and existing Instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click +NEW INTEGRATION and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus/-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE HPE Morpheus Enterprise AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus/-ansible-example.git.
+
+Click SAVE CHANGES. You’ll now see our new Ansible integration listed among any other configured integrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click + ADD. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+Now that we have a Workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring an instance to your needs. There are a number of other automation types that can be built into your Workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+#### Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume Azure public cloud. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/latest/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json b/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
new file mode 100644
index 0000000..9344cde
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+  "title": "Requirements",
+  "ordinal": 172,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md b/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
new file mode 100644
index 0000000..3cc440c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json b/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
new file mode 100644
index 0000000..321272b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+  "title": "Overview",
+  "ordinal": 43,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md b/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
new file mode 100644
index 0000000..5bd67fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
@@ -0,0 +1,9 @@
+# Overview
+
+The HPE Morpheus Enterprise Agent is an important and powerful facet of HPE Morpheus Enterprise as an orchestration tool. Though it is not required, which is one unique capability of our platform versus some of our competitors, it is recommended for use as it brings many benefits. Not only does it provide statistics for the guest operating system and resource utilization, it also brings along with it monitoring and log aggregation capabilities. After an initial brownfield discovery, Users can decide to convert unmanaged VMs to managed.
+
+NOTE
+
+**Agent installation is not required to manage an Instance.** If you don’t have the Agent installed, we make every effort to aggregate stats. These will vary based on the Cloud and can be more limited or less accurate without utilizing HPE Morpheus Enterprise Agent.
+
+The HPE Morpheus Enterprise Agent is very lightweight and secure. It does not open any inbound network ports but rather only opens an outbound connection back to the HPE Morpheus Enterprise appliance over port 443 (HTTPS or WSS protocol). This allows for a bidirectional command bus where instructions can be sent to orchestrate a workload without needing access to things like SSH or WinRM. The tool can even be installed at provision time via technologies like Cloud-Init, such that the HPE Morpheus Enterprise appliance itself doesn’t even need direct network access to the VLAN under which the workload resides. By doing this we address many of the network security concerns that come with the use of an agent while demonstrating its security and analytics benefits. We can even use this statistical data at the guest OS level rather than the hypervisor level to provide extremely precise right-sizing recommendations.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json b/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
new file mode 100644
index 0000000..f799c99
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+  "title": "Operating Systems",
+  "ordinal": 165,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html",
+  "topic_cluster": {
+    "clustering_title": "Operating Systems",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md b/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
new file mode 100644
index 0000000..b43ed1f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
@@ -0,0 +1,45 @@
+# Operating Systems
+
+Out of the box, many Operating Systems (also referred to as OS types) are seeded into HPE Morpheus Enterprise by default. OS types can be set on Virtual Images when they are created. If you don’t use any other features of OS types described here, they are still useful to set on Virtual Images to ensure only Workflows designed for the platform can be run against workloads provisioned from the image. It can also help ensure certain types of reporting and dashboard metrics are correct.
+
+IMPORTANT
+
+It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration. Read this section in full for complete detail on the use cases for the Operating System construct.
+
+## Permissions
+
+Access to Operating Systems is controlled by the `Library: Operating Systems` feature permission. Access levels are as follows:
+
+- **FULL:** Access to view, create, and edit Operating Systems
+- **READ:** Access to view Operating Systems only
+- **NONE:** No access to the Operating Systems section of the UI
+
+## Use Cases
+
+OS types can primarily be used in one of two use cases. The first is adding your own images to existing OS types. The upshot of doing this is to use built-in Instance Types (for example, the “UBUNTU” Instance Type) while replacing the included default images with your own gold master images for some or all provisioning technologies.
+
+View the existing OS types by navigating to Library > OperatingSystems. Here, a list of all OS types is shown. If this is a brand new appliance or if you’ve never added new Operating Systems, all shown here will be system default OS types. By clicking into any of the OS types for which HPE Morpheus Enterprise currently provides default images, you will see all of the Virtual Images for that OS type and the provisioning technology each image is compatible with.
+
+![../../_images/listOsImages.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-47C7B1DB-2DE5-4A66-B1A9-EAFC3B87601B-high.png)
+
+To add an existing Virtual Image to the currently-selected OS type, click + ADD. Select the image and optionally identify a provisioning technology or even a specific Cloud. When finished, click SAVE.
+
+NOTE
+
+When adding a Virtual Image to an OS type, only Virtual Images that have been saved with the same OS type (Operating System) configuration will be shown in the typeahead list.
+
+![../../_images/addOsImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-84DB6665-2DF9-46C0-9DB1-623644B30196-high.png)
+
+Once images are associated with a built-in OS type, they will be used when the situation warrants (a compatible provisioning target is selected or the correct Cloud is chosen, depending on how the OS type image was configured). It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration.
+
+The second use case is to add your own Operating System. New Operating Systems can be added by navigating to Library > OperatingSystems and clicking + ADD. OS types can be configured with highly granular detail allowing environments with similar Os types to distinguish them.
+
+![../../_images/createOsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-436A53AF-DF69-439A-83EE-7F9AB7045072-high.png)
+
+After creating the OS type, any new or existing Virtual Images can be associated to the newly created Operating System (Library > Virtual Images). Once Virtual Images have the Operating System association, you can return to the OS type and complete the association with the Operating System by clicking into the OS type and clicking + ADD.
+
+Once you have a custom Operating System loaded with your own gold master images, the OS type can be used with new Node Types going forward. To see how this works, navigate to Library > Blueprints > Node Types and click + ADD. Change the default technology for a new Node Type from the default “Docker” value to another technology, such as “VMware”. Notice that the option is given to associate the Node Type with either a specific image or with an OS type. By selecting an OS type, the Node Type will select the appropriate image at provision time based on technology and/or Cloud filters.
+
+![../../_images/createNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D7231A7E-44FC-46F2-BF5A-99020D46CF48-high.png)
+
+It’s important to note that more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Additionally, only one user image can be added per Operating System with an identical technology and/or Cloud configuration.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json b/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
new file mode 100644
index 0000000..7502d0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+  "title": "Importing HPE ProLiant Bare Metal Servers",
+  "ordinal": 416,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html",
+  "topic_cluster": {
+    "clustering_title": "Importing HPE ProLiant Bare Metal Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md b/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
new file mode 100644
index 0000000..05a90ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
@@ -0,0 +1,31 @@
+# Importing HPE ProLiant Bare Metal Servers
+
+## About this task
+
+Perform the following procedure to import HPE ProLiant Bare Metal Servers:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute, then select the Bare Metal tab.
+2. Click the + Bare Metal button, then select HPE Server.
+3. Select the Group you created earlier from the drop-down list and click Next.   
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-64D4C0D9-B1A4-4257-A316-81069FC4EF3A-high.png)
+4. Enter a Name for the server and click Next.   
+   ![Name](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B361D956-0808-4F91-9D2F-87F840898005-high.png)
+5. Enter the following iLO (Integrated Lights Out) details for the server:
+
+   - iLO IP Address
+   - iLO Username (typically "Administrator")
+   - iLO Administrator Password  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C4D9169E-91C8-4F6D-841A-B8DE6DAB8824-high.png)
+6. Leave the Pre-Provisioned Server option unselected, then click Next.
+7. Click Next to review your host configuration details.
+8. Click Complete to finalize the host creation.   
+   ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DB572274-C1F6-4461-9594-5436E0CBE9AB-high.png)  
+
+   The below image shows list of clouds available.   
+   ![clouds](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8F3FE3ED-1AEB-4AD5-808A-D9C7C54B1308-high.png)
+
+## Results
+
+the HPE ProLiant Bare Metal plugin automatically discovers and records all hardware details from the server using its Integrated Lights Out (iLO) management interface. This discovery process may take a few minutes, depending on the server and network conditions. After completion, the server becomes available (STATUS = `available`) in Morpheus for further provisioning and lifecycle operations.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json b/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
new file mode 100644
index 0000000..28ed3a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+  "title": "Single Node/AIO Appliance Upgrades",
+  "ordinal": 22,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node/AIO Appliance Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md b/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
new file mode 100644
index 0000000..c6b6ce5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
@@ -0,0 +1,55 @@
+# Single Node/AIO Appliance Upgrades
+
+IMPORTANT
+
+Only appliances running Morpheus v6.0.0 or higher can upgrade to v8.1.1. Always backup your database before running any upgrade.
+
+The following covers upgrading Single Node or AIO (All-In-One) Appliance configurations.
+
+## Debian / Ubuntu
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on Ubuntu/Debian, download new deb package from My HPE Software Center and transfer it to your application node, stop the morpheus-ui, install the new deb package, then reconfigure.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
+
+## CentOS / RHEL / Amazon / SLES
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on CentOS, RHEL, Amazon or SLES, download the upgrade package from My HPE Software Center, transfer it to your application node, install the new rpm package, stop the morpheus-ui, reconfigure and then start the morpheus-ui:
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json b/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
new file mode 100644
index 0000000..b11c5bc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+  "title": "Script Templates",
+  "ordinal": 161,
+  "parent_title": "Templates",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html",
+  "topic_cluster": {
+    "clustering_title": "Script Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md b/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
new file mode 100644
index 0000000..46032ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
@@ -0,0 +1,75 @@
+# Script Templates
+
+Scripts are bash and Powershell scripts that can be attached to Node Types to always execute at the selected phase when that Node Type is provisioned, added to Workflows as Library Script Tasks, and/or executed ad-hoc on Instances.
+
+## Creating Scripts
+
+### Procedure
+
+1. Navigate to Library > Templates > Script Templates
+2. Select + ADD
+3. Enter the Following: 
+
+   NAME
+   :   Name of the Script in HPE Morpheus Enterprise
+
+   SCRIPT TYPE
+   :   - Bash
+       - Powershell
+
+   PHASE
+   :   Select which phase the Script will execute when attached to a Node Type. When a script is attached to a Node Type, it will execute according to the selcted phase:
+
+       Start Service
+       :   Any time the Instance action `Start Service` is executed
+
+       Stop Service
+       :   Any time the Instance action `Stop Service` is executed
+
+       Pre-Provision
+       :   - Containers: Script will execute against the container host before the container is provisioned
+           - Virtual Machines: Script will execute before any provision phase Scripts or Tasks
+
+       Provision
+       :   Script will execute once per new Instance node during the provision Phase. Provisioning will not be considered complete until all scripts and tasks in the provisioning phase are completed
+
+           NOTE
+
+           Any Script or Task set to the provision phase will be included in the total provision time and impact success/warn/failure provisioning status messages. As an example, your VM could be up and running but if your Script is in the provision phase and fails, provisioning will be marked as a failure.
+
+           Post-Provision
+           :   Script will execute once per new Instance node after the provision phase is completed. Scripts and Tasks in the Post-Provision phase will show execution status and history, but are not considered part of the provision and do not impact provisioning status.
+
+           Pre-Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The Script will run prior to the deployment file(s) being written
+
+           Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The script will run after the deployment file(s) are written
+
+           Reconfigure
+           :   Script will execute on target Instance any time a reconfigure is executed against the Instance.
+
+           Teardown
+           :   Script will execute on target Instance upon Instance deletion. Script will execute against target Instance prior to the deletion/removal of resources.
+
+   SCRIPT
+   :   Enter Bash or Powershell script.
+
+       NOTE
+
+       HPE Morpheus Enterprise variables are supported in Library Scripts using `<%= variable.var %>` format
+
+   RUN AS USER
+   :   By default Scripts are execute as `morpheus-node`. To execute as another User, populate `RUN AS USER` and ensure proper user permissions & group access
+
+   SUDO
+   :   Flag `SUDO` if sudo is required to execute the Script
+
+### Results
+
+To attach Scripts and templates that have been added to the Library to a Node Type, start typing the name and then select the script(s) and/or template(s).
+
+- Multiple scripts and templates can be added to a Node Type
+- Scripts and Templates can be added/shared among multiple Node Types
+- The execution phase can be set for Scripts in the Scripts section
+- Search will populate Scripts or Templates containing the characters entered anywhere in their name, not just the first letter(s) of the name
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json b/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
new file mode 100644
index 0000000..3db82a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+  "title": "Git",
+  "ordinal": 481,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html",
+  "topic_cluster": {
+    "clustering_title": "Git",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md b/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
new file mode 100644
index 0000000..9547d74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
@@ -0,0 +1,26 @@
+# Git
+
+Git Repository integrations allow integration of public or private Git repositories in Github, GitLab or other services. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Each time code from your repositories is invoked, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Creating an Integration
+
+### About this task
+
+New Git integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need an access code for authentication with private repositories, public repositories can be integrated simply with a URL.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Git repository
+4. Configure the following: 
+
+   - NAME: A friendly name for the Git repository integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, code in this repository will be available for creating automation or other HPE Morpheus Enterprise constructs
+   - DEFAULT BRANCH: The default repository branch from which code should be sourced
+   - USERNAME: For private repositories, enter an account name (such as a Github username)
+   - PASSWORD: For Github and GitLab, password authentication is no longer supported but access tokens should go in this field.
+   - ACCESS TOKEN: Currently an unused field, access tokens should go in the Password field
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json b/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
new file mode 100644
index 0000000..8e24dbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+  "title": "EKS Clusters",
+  "ordinal": 200,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html",
+  "topic_cluster": {
+    "clustering_title": "EKS Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md b/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
new file mode 100644
index 0000000..25c485a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
@@ -0,0 +1,64 @@
+# EKS Clusters
+
+Provisions a new Elastic Kubernetes Service (EKS) Cluster in target AWS Cloud.
+
+NOTE
+
+EKS Cluster provisioning is different than creating a Kubernetes Cluster type in AWS EC2, which creates EC2 instances and configures Kubernetes, outside of EKS.
+
+HPE Morpheus Enterprise currently supports EKS in the following regions: `us-east-2`, `us-east-1`, `us-west-1`, `us-west-2`, `af-south-1`, `ap-east-1`, `ap-south-1`, `ap-northeast-3`, `ap-northeast-2`, `ap-southeast-1`, `ap-southeast-2`, `ap-northeast-1`, `ca-central-1`, `eu-central-1`, `eu-west-1`, `eu-west-2`, `eu-south-1`, `eu-west-3`, `eu-north-1`, `me-south-1`, `sa-east-1`, `us-gov-east-1`, `us-gov-west-1`
+
+## Create an EKS Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `EKS Cluster`
+4. Populate the following: 
+
+   LAYOUT
+   :   Select server layout for EKS Cluster
+
+   PUBLIC IP
+   :   Subnet Default
+       :   Use AWS configured Subnet setting for Public IP assignment
+
+       Assigned EIP
+       :   Assigned Elastic IP to Controller and Worker Nodes. Requires available EIP’s
+
+   CONTROLLER ROLE
+   :   Select Role for EKS Controller from synced role list
+
+   CONTROLLER SUBNET
+   :   Select subnet placement for EKS Controller
+
+   CONTROLLER SECURITY GROUP
+   :   Select Security Group assignment for EKS Controller
+
+   WORKER SUBNET
+   :   Select Subnet placement for Worker Nodes
+
+   WORKER SECURITY GROUP
+   :   Select Security Group assignment for Worker Nodes
+
+   WORKER PLAN
+   :   Select Service Plan (EC2 Instance Type) for Worker Nodes
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json b/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
new file mode 100644
index 0000000..6053dad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+  "title": "User Role Permission Sections",
+  "ordinal": 297,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html",
+  "topic_cluster": {
+    "clustering_title": "User Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md b/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
new file mode 100644
index 0000000..ab36200
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
@@ -0,0 +1,34 @@
+# User Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Instance Types
+:   Controls User access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls User access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls User access for each report type in the Reports section (Operations > Reports). The user must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls User access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters)
+
+VDI Pools
+:   Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json b/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
new file mode 100644
index 0000000..9911ee0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+  "title": "Image Builder",
+  "ordinal": 266,
+  "parent_title": "Tools",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html",
+  "topic_cluster": {
+    "clustering_title": "Image Builder",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md b/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
new file mode 100644
index 0000000..8c767f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
@@ -0,0 +1,130 @@
+# Image Builder
+
+The Morpheus Image Builder tool creates vmdk, qcow2, vhd and raw Images from scratch. The Image Builder creates a blank VM in VMware, attaches an os iso, executes a boot script on the VM at startup via VNC which calls a preseed script which runs the unattended os installation and configuration. Morpheus then executes an ova export of the completed vmdk to target Storage provider, and converts the image to all other specified formats. The new Virtual Image records are automatically added to Morpheus and the Images are then available for use.
+
+## Requirements
+
+- DHCP must be enabled on the network specified for the VM in Morpheus, and network settings configured for DHCP in Morpheus
+  :   The blank VM must get network configuration via DHCP upon boot. Static IP assignment is not possible.
+- Hypervisor Console must be enabled on the Target Cloud
+  :   Morpheus utilizes VNC to pass the boot script to the VM.
+- VM must be able to reach and resolve the Morpheus appliance url over 443
+  :   The boot script calls to the Morpheus appliance to get the preseed script.
+- Valid Linux iso set for the Virtual Image. Windows is not supported.
+  :   The iso can exist in the target cloud or uploaded to Morpheus
+
+      NOTE
+
+      `cloud-init enabled` must be disabled on the iso Virtual Image settings.
+- Access to target ESXi host(s) over 443 and ESXi hostname dns resolution
+  :   - Same requirement as Hypervisor Console and Image upload/download to/from vCenter.
+- Valid Boot Script
+- Valid Pre-seed script
+- Valid Storage Provider configure for ova export of generated image.
+
+## Sample Scripts
+
+### Sample Boot Script
+
+```
+```
+<wait5><tab> text ks=<%=preseedUrl%><enter>
+```
+```
+
+NOTE
+
+`<%=preseedUrl%>` is a Morpheus variable that will populate with the Morpheus appliance url.
+
+### Sample Preseed Script
+
+```
+```
+# CentOS 7.x kickstart file - ks.cfg  
+#  
+# For more information on kickstart syntax and commands, refer to the  
+# CentOS Installation Guide:  
+# https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html  
+#  
+# For testing, you can fire up a local http server temporarily.  
+# cd to the directory where this ks.cfg file resides and run the following:  
+#    $ python -m SimpleHTTPServer  
+# You don't have to restart the server every time you make changes.  Python  
+# will reload the file from disk every time.  As long as you save your changes  
+# they will be reflected in the next HTTP download.  Then to test with  
+# a PXE boot server, enter the following on the PXE boot prompt:  
+#    > linux text ks=http://<your_ip>:8000/ks.cfg  
+# Required settings  
+lang en_US.UTF-8  
+keyboard us  
+rootpw password  
+authconfig --enableshadow --enablemd5  
+timezone UTC  
+# Optional settings  
+install  
+cdrom  
+user --name=cloud-user --plaintext --password password  
+unsupported_hardware  
+network --bootproto=dhcp  
+firewall --disabled  
+selinux --permissive  
+bootloader --location=mbr --append="biosdevname=0 net.ifnames=0"  
+text  
+skipx  
+zerombr  
+clearpart --all --initlabel  
+autopart --type=plain  
+firstboot --disabled  
+reboot  
+%packages --nobase --ignoremissing --excludedocs  
+openssh-clients  
+# Prerequisites for installing VMware Tools guest additions.  
+# Put in kickstart to ensure first version installed is from install disk,  
+# not latest from a mirror.  
+kernel-headers  
+kernel-devel  
+gcc  
+make  
+perl  
+curl  
+wget  
+bzip2  
+dkms  
+patch  
+net-tools  
+git  
+# Core selinux dependencies installed on 7.x, no need to specify  
+# Other stuff  
+sudo  
+nfs-utils  
+open-vm-tools  
+-fprintd-pam  
+-intltool  
+-biosdevname  
+# unnecessary firmware  
+-aic94xx-firmware  
+-atmel-firmware  
+-b43-openfwwf  
+-bfa-firmware  
+-ipw*-firmware  
+-irqbalance  
+-ivtv-firmware  
+-iwl*-firmware  
+-libertas-usb8388-firmware  
+-ql*-firmware  
+-rt61pci-firmware  
+-rt73usb-firmware  
+-xorg-x11-drv-ati-firmware  
+-zd1211-firmware  
+%end  
+%post  
+# configure vagrant user in sudoers  
+echo "%cloud-user ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers.d/cloud-user  
+chmod 0440 /etc/sudoers.d/cloud-user  
+cp /etc/sudoers /etc/sudoers.orig  
+sed -i "s/^\(.*requiretty\)$/#\1/" /etc/sudoers  
+# keep proxy settings through sudo  
+echo 'Defaults env_keep += "HTTP_PROXY HTTPS_PROXY FTP_PROXY RSYNC_PROXY NO_PROXY"' >> /etc/sudoers  
+%end
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json b/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
new file mode 100644
index 0000000..7291a3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+  "title": "AzureStorage",
+  "ordinal": 520,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html",
+  "topic_cluster": {
+    "clustering_title": "AzureStorage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md b/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
new file mode 100644
index 0000000..5fa5a13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
@@ -0,0 +1,30 @@
+# AzureStorage
+
+## To Add Azure Storage
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Storage
+2. Select + ADD
+3. From the New Storage Provider Wizard input the following: 
+
+   Name
+   :   Name of the storage provider.
+
+   Provider Type
+   :   Azure
+
+   Storage Account
+   :   Add Storage Account
+
+   Storage Key
+   :   Add Storage Key
+
+   Share Name
+   :   Add Share Name
+
+   Targets
+   :   - Default Backup Target
+       - Default Deployment Archive Target
+       - Default Virtual Image Store
+4. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json b/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
new file mode 100644
index 0000000..5d549a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+  "title": "Network Management",
+  "ordinal": 429,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md b/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
new file mode 100644
index 0000000..3797d2d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
@@ -0,0 +1,16 @@
+# Network Management
+
+At a high level, there are two network modes in which a cloud can be configured to operate:
+
+- Unmanaged network mode (`Unmanaged`).
+- Managed network mode (`ArubaCX-Int`).
+
+Network modes are created during cloud creation.
+
+![Network Mode](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-876273B4-9A6A-4398-B541-2C7FEE1F1A25-high.png)
+
+**Subtopics**  
+
+- **[Unmanaged Networks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html)**
+- **[Managed Networks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html)**
+- **[Networks Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json b/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
new file mode 100644
index 0000000..fa3462a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+  "title": "Uninstall HPE Morpheus Enterprise Agent",
+  "ordinal": 49,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html",
+  "topic_cluster": {
+    "clustering_title": "Uninstall HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md b/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
new file mode 100644
index 0000000..fb06012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
@@ -0,0 +1,37 @@
+# Uninstall HPE Morpheus Enterprise Agent
+
+## Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+## Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json b/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
new file mode 100644
index 0000000..9222e37
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+  "title": "Add NSX load balancer",
+  "ordinal": 502,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md b/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
new file mode 100644
index 0000000..211f3ee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
@@ -0,0 +1,34 @@
+# Add NSX load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX lb](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D2AD8017-CB76-4284-91AE-2514167985CA-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   OPTIONS
+   :   **ENABLED**: Select this option to enable the NSX for the integration.
+   :   **ADMIN STATE**: Select this option to switch to admin state.
+
+   SIZE
+   :   From the drop-down list, select the size of the NSX to be provisioned.
+
+   TIER-1 GATEWAYS
+   :   From the drop-down list, select the Tier-1 gateway.
+
+   LOG LEVEL
+   :   From the drop-down list, select the log level for the logs.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json b/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
new file mode 100644
index 0000000..4db7aff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+  "title": "Managing Apps",
+  "ordinal": 89,
+  "parent_title": "Apps",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md b/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
new file mode 100644
index 0000000..dc7be67
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
@@ -0,0 +1,85 @@
+# Managing Apps
+
+## App Status
+
+App Status is determined by the status of the Instances within the App or by the DELETE action. All Instances in an App must be in ‘Running’ status for the App status to equal ‘Running’.
+
+Table 1. App Statuses
+
+     | Status Icon | App Status | Status Reason |
+| --- | --- | --- |
+| ../../_images/running_icon.svg | Running | All Instance Statuses = Running |
+| ../../_images/failed_icon.svg | Failed | Any Instance Status = Failed |
+| ../../_images/pending_icon.svg | Pending | Any Instance Status = Pending |
+| ../../_images/pendingRemoval_icon.svg | Pending Removal | Any Instance Status = Pending Removal |
+| ../../_images/deploying_icon.svg | Provisioning | Any Instance Status = Provisioning |
+| ../../_images/removing_icon.svg | Removing | The DELETE action was trigger on the App |
+| ../../_images/unknown_icon.svg | Unknown | Any Instance Status = Unknown, or the App is empty |
+
+## Editing an App
+
+### About this task
+
+The EDIT action allows permissioned users to update an Apps metadata, Environment, Group and Owner.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select EDIT
+4. Update the following 
+
+   NAME
+   :   App Name
+
+   DESCRIPTION
+   :   App Description
+
+   ENVIRONMENT
+   :   App Environment
+
+   GROUP
+   :   App Group assignment
+
+   OWNER
+   :   User assigned as Owner of the App
+5. Select SAVE CHANGES
+
+## Deleting an App
+
+### About this task
+
+The DELETE action allows permissioned users to delete an App and, by default, all Instances within the App.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select DELETE
+4. The DELETE APP? confirmation modal will be displayed: 
+
+   Remove Instances
+   :   Deletes all Instances associated with the App - Enabled by Default
+
+   Preserve Backups
+   :   Preserves Backups of the Instances associated with the App - Disabled by Default
+
+   Preserve Volumes
+   :   Preserves Storage Volumes of the Instances associated with the App - Disabled by Default
+
+   Force Delete
+   :   Forces deletion of the App - Required when any Instances associated with the App are in “provisioning” state - WARNING Force deleting may cause orphaned infrastructure or resources. - Disabled by Default
+5. Select DELETE to proceed with deleting the App, or CANCEL to abort the delete action.
+
+## Exporting Configuration JSON
+
+### About this task
+
+To export an App Blueprint as JSON:
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select ACTIONS > Export
+4. The App export file will be downloaded to your computer as `{app_name}.json`
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json b/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
new file mode 100644
index 0000000..0ff7075
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+  "title": "Compute Management",
+  "ordinal": 400,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html",
+  "topic_cluster": {
+    "clustering_title": "Compute Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md b/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
new file mode 100644
index 0000000..67e334b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
@@ -0,0 +1,22 @@
+# Compute Management
+
+The topic section describes how HPE Morpheus Enterprise orchestrates on-premises and HPE BMaaS Cloud resources. It covers the end-to-end lifecycle for physical servers, including installation, cloud configuration, on-boarding, and workload migration.
+
+Administrators perform the following tasks:
+
+- Define a Bare Metal Cloud
+- Configure unmanaged networks and resource pools
+- Import HPE ProLiant servers for centralized visibility
+- Manage greenfield (new) and brownfield (existing) server deployment
+- Convert Pre-Provisioned servers into managed HPE Morpheus instances
+
+Administrators use these procedures to enable consistent provisioning, lifecycle management, and governance for HPE ProLiant infrastructure within HPE Morpheus.
+
+**Subtopics**  
+
+- **[Adding HPE BMaaS Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html)**
+- **[Creating an HPE BMaaS Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html)**
+- **[Creating Resource Pools](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html)**
+- **[Image Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html)**
+- **[Provisioning a New Server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html)**
+- **[Importing Pre-Provisioned Server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json b/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
new file mode 100644
index 0000000..a89744b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+  "title": "Morpheus Agent OS Support",
+  "ordinal": 45,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent OS Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md b/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
new file mode 100644
index 0000000..f922ab4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
@@ -0,0 +1,119 @@
+# Morpheus Agent OS Support
+
+Table 1.
+
+           | Name | Bit Count | Category | Code | OS Family | OS Version | Platform | Vendor | Install Agent? |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Almalinux Linux 8 64‐bit | 64 | almalinux | almalinux.8.64 | almalinux | 8 | linux | almalinux | Yes |
+| Almalinux Linux 9 64‐bit | 64 | almalinux | almalinux.9.64 | almalinux | 9 | linux | almalinux | Yes |
+| amazon linux 2 64‐bit | 64 | amazonlinux | amazonlinux.2.64 | centos | 2 | linux | amazon | Yes |
+| centOS | 32 | centos | cent | rhel | all | linux | centos | Yes |
+| centOS 6 | 32 | centos | cent.6 | rhel | 6 | linux | centos | Yes |
+| centOS 6 64‐bit | 64 | centos | cent.6.64 | rhel | 6 | linux | centos | Yes |
+| centOS 64‐bit | 64 | centos | cent.64 | rhel | all | linux | centos | Yes |
+| centOS 7 | 32 | centos | cent.7 | rhel | 7 | linux | centos | Yes |
+| centOS 7 64‐bit | 64 | centos | cent.7.64 | rhel | 7 | linux | centos | Yes |
+| centOS 8 | 32 | centos | cent.8 | rhel | 8 | linux | centos | Yes |
+| centOS 8 64‐bit | 64 | centos | cent.8.64 | rhel | 8 | linux | centos | Yes |
+| centOS 8 Stream 64‐bit | 64 | centos | cent.8.stream.64 | rhel | 8 | linux | centos | Yes |
+| centOS 9 64‐bit | 64 | centos | cent.9.64 | rhel | 9 | linux | centos | Yes |
+| debian | 32 | debian | debian | debian | all | linux | debian | Yes |
+| debian 10 64‐bit | 64 | debian | debian.10.64 | debian | 10 | linux | debian | Yes |
+| debian 10.9 64‐bit | 64 | debian | debian.10.9.64 | debian | 10 | linux | debian | Yes |
+| debian 11 64‐bit | 64 | debian | debian.11.64 | debian | 11 | linux | debian | Yes |
+| debian 6 | 32 | debian | debian.6 | debian | 6 | linux | debian | Yes |
+| debian 6 64‐bit | 64 | debian | debian.6.64 | debian | 6 | linux | debian | Yes |
+| debian 64‐bit | 64 | debian | debian.64 | debian | all | linux | debian | Yes |
+| debian 7 | 32 | debian | debian.7 | debian | 7 | linux | debian | Yes |
+| debian 7 64‐bit | 64 | debian | debian.7.64 | debian | 7 | linux | debian | Yes |
+| debian 8 | 32 | debian | debian.8 | debian | 8 | linux | debian | Yes |
+| debian 8 64‐bit | 64 | debian | debian.8.64 | debian | 8 | linux | debian | Yes |
+| debian 9.13 64‐bit | 64 | debian | debian.9.13.64 | debian | 9 | linux | debian | Yes |
+| debian 9.4 64‐bit | 64 | debian | debian.9.4.64 | debian | 9 | linux | debian | Yes |
+| ESXi | 64 | esxi | esxi | NULL |  | ESXi | vmware | No |
+| ESXi 4 | 64 | esxi | esxi.4 | NULL | 4 | ESXi | vmware | No |
+| ESXi 5 | 64 | esxi | esxi.5 | NULL | 5 | ESXi | vmware | No |
+| ESXi 6 | 64 | esxi | esxi.6 | NULL | 6 | ESXi | vmware | No |
+| ESXi 7 | 64 | esxi | esxi.7 | NULL | 7 | ESXi | vmware | No |
+| ESXi 8 | 64 | esxi | esxi.8 | NULL | 8 | ESXi | vmware | No |
+| fedora | 32 | fedora | fedora | NULL | all | linux | fedora | Yes |
+| fedora 64‐bit | 64 | fedora | fedora.64 | NULL | all | linux | fedora | Yes |
+| linux | 64 | linux | linux | NULL | all | linux | linux | Yes |
+| linux 32‐bit | 32 | linux | linux.32 | NULL | all | linux | linux | No |
+| linux 64‐bit | 64 | linux | linux.64 | NULL | all | linux | linux | No |
+| mac os | 64 | mac | mac | darwin | all | osx | apple | Yes |
+| opensuse | 32 | opensuse | opensuse.32 | suse | all | linux | opensuse | Yes |
+| opensuse 15 64‐bit | 64 | opensuse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| opensuse 64‐bit | 64 | opensuse | opensuse.64 | suse | all | linux | opensuse | Yes |
+| oracle enterprise | 32 | oracle | oracle.32 | NULL | all | linux | oracle | Yes |
+| oracle enterprise 64‐bit | 64 | oracle | oracle.64 | NULL | all | linux | oracle | Yes |
+| oracle linux 64‐bit | 64 | oracle | oracle.linux.64 | NULL | all | linux | oracle | Yes |
+| oracle vm server | 64 | oracle | ovs | NULL | all | linux | oracle | No |
+| other 32‐bit | 32 | other | other.32 | NULL | all | other | other | No |
+| other 64‐bit | 64 | other | other.64 | NULL | all | other | other | No |
+| redhat | 32 | redhat | redhat | rhel | all | linux | redhat | Yes |
+| redhat 6 | 32 | redhat | redhat.6 | rhel | 6 | linux | redhat | Yes |
+| redhat 6 64‐bit | 64 | redhat | redhat.6.64 | rhel | 6 | linux | redhat | Yes |
+| redhat 64‐bit | 64 | redhat | redhat.64 | rhel | all | linux | redhat | Yes |
+| redhat 7 | 32 | redhat | redhat.7 | rhel | 7 | linux | redhat | Yes |
+| redhat 7 64‐bit | 64 | redhat | redhat.7.64 | rhel | 7 | linux | redhat | Yes |
+| redhat 8 | 32 | redhat | redhat.8 | rhel | 8 | linux | redhat | Yes |
+| redhat 8 64‐bit | 64 | redhat | redhat.8.64 | rhel | 8 | linux | redhat | Yes |
+| redhat 9 64‐bit | 64 | redhat | redhat.9.64 | rhel | 9 | linux | redhat | Yes |
+| Rocky Linux 8 | 32 | rocky | rocky.8 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 8 64‐bit | 64 | rocky | rocky.8.64 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 9 64‐bit | 64 | rocky | rocky.9.64 | rocky | 9 | linux | rocky | Yes |
+| solaris | 32 | solaris | solaris.32 | NULL | all | solaris | solaris | No |
+| solaris 64‐bit | 64 | solaris | solaris.64 | NULL | all | solaris | solaris | No |
+| suse enterprise | 32 | suse | suse | suse | all | linux | suse | Yes |
+| suse enterprise 11 | 32 | suse | suse.11 | suse | 11 | linux | suse | Yes |
+| suse enterprise 11 64‐bit | 64 | suse | suse.11.64 | suse | 11 | linux | suse | Yes |
+| suse enterprise 12 | 32 | suse | suse.12 | suse | 12 | linux | suse | Yes |
+| suse enterprise 12 64‐bit | 64 | suse | suse.12.64 | suse | 12 | linux | suse | Yes |
+| suse enterprise 15 | 32 | suse | suse.15 | suse | 15 | linux | suse | Yes |
+| suse enterprise 15 64‐bit | 64 | suse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| suse enterprise 64‐bit | 64 | suse | suse.64 | suse | all | linux | suse | Yes |
+| ubuntu | 32 | ubuntu | ubuntu | debian | all | linux | canonical | Yes |
+| ubuntu 12 | 32 | ubuntu | ubuntu.12.04 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 12 64‐bit | 64 | ubuntu | ubuntu.12.04.64 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 13 | 32 | ubuntu | ubuntu.13.10 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 13 64‐bit | 64 | ubuntu | ubuntu.13.10.64 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 14 | 32 | ubuntu | ubuntu.14.04 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 14 64‐bit | 64 | ubuntu | ubuntu.14.04.64 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 15 | 32 | ubuntu | ubuntu.15.10 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 15 64‐bit | 64 | ubuntu | ubuntu.15.10.64 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 16 | 32 | ubuntu | ubuntu.16.04 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 16 64‐bit | 64 | ubuntu | ubuntu.16.04.64 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 18.04 | 32 | ubuntu | ubuntu.18.04 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 18.04 64‐bit | 64 | ubuntu | ubuntu.18.04.64 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 20.04 | 32 | ubuntu | ubuntu.20.04 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 20.04 64‐bit | 64 | ubuntu | ubuntu.20.04.64 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 22.04 64‐bit | 64 | ubuntu | ubuntu.22.04.64 | debian | 22.04 | linux | canonical | Yes |
+| ubuntu 24.04 64‐bit | 64 | ubuntu | ubuntu.24.04.64 | debian | 24.04 | linux | canonical | Yes |
+| ubuntu 64‐bit | 64 | ubuntu | ubuntu.64 | debian | all | linux | canonical | Yes |
+| unknown | 64 | other | unknown | NULL | all | unknown | unknown | No |
+| windows | 64 | windows | windows | windows | all | windows | microsoft | Yes |
+| windows 10 | 32 | windows | windows.10 | windows | 10 | windows | microsoft | Yes |
+| windows 10 64‐bit | 64 | windows | windows.10.64 | windows | 10 | windows | microsoft | Yes |
+| windows 11 | 32 | windows | windows.11 | windows | 11 | windows | microsoft | Yes |
+| windows 11 64‐bit | 64 | windows | windows.11.64 | windows | 11 | windows | microsoft | Yes |
+| windows 7 | 32 | windows | windows.7 | windows | 7 | windows | microsoft | Yes |
+| windows 7 64‐bit | 64 | windows | windows.7.64 | windows | 7 | windows | microsoft | Yes |
+| windows 8 | 32 | windows | windows.8 | windows | 8 | windows | microsoft | No |
+| windows 8 64‐bit | 64 | windows | windows.8.64 | windows | 8 | windows | microsoft | Yes |
+| windows server 2003 | 64 | windows | windows.server.2003 | windows | 2003 | windows | microsoft | No |
+| windows server 2008 | 64 | windows | windows.server.2008 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2008 R2 | 64 | windows | windows.server.2008.r2 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2012 | 64 | windows | windows.server.2012 | windows | 2012 | windows | microsoft | Yes |
+| windows server 2016 | 64 | windows | windows.server.2016 | windows | 2016 | windows | microsoft | Yes |
+| windows server 2019 | 64 | windows | windows.server.2019 | windows | 2019 | windows | microsoft | Yes |
+| windows server 2022 | 64 | windows | windows.server.2022 | windows | 2022 | windows | microsoft | Yes |
+| windows server 2025 | 64 | windows | windows.server.2025 | windows | 2025 | windows | microsoft | Yes |
+| xen server 6.1 | 64 | xen | xenserver.6.1 | xen | 6.1 | linux | xen | No |
+| xen server 6.2 | 64 | xen | xenserver.6.2 | xen | 6.2 | linux | xen | No |
+| xen server 6.5 | 64 | xen | xenserver.6.5 | xen | 6.5 | linux | xen | No |
+| xen server 7.0 | 64 | xen | xenserver.7.0 | xen | 7.0 | linux | xen | No |
+
+NOTE
+
+Other Operating System types may be supported but are not tested.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json b/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
new file mode 100644
index 0000000..ee8c030
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+  "title": "Known Limitations and Operational Considerations",
+  "ordinal": 457,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html",
+  "topic_cluster": {
+    "clustering_title": "Known Limitations and Operational Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md b/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
new file mode 100644
index 0000000..ae31592
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
@@ -0,0 +1,7 @@
+# Known Limitations and Operational Considerations
+
+Table 1. Known Limitations and Operational Considerations
+
+        | S.No | Topic | Description | Impact | Applicability | Operational Guidance |
+| --- | --- | --- | --- | --- | --- |
+| 1 | SATA Controller Initialization Delay During Importing HPE ProLiant Bare Metal Servers | During the bare-metal server import and hardware discovery process, if a server has one or more SATA controllers with no attached SATA disks, the system waits a minimum of **5 minutes per SATA controller** before continuing.  The wait time is cumulative and applies to each SATA controller detected without attached disks.  This behavior occurs during the initial hardware probing phase, before the server becomes available for provisioning in Morpheus. | 1. Increased time to complete bare-metal server discovery, import, and provisioning. 2. Delay proportional to the number of SATA controllers present without disks. 3. No impact once the server import process has completed. 4. No impact when SATA controllers have SATA disks attached. | This condition is typically observed in **lab** or **evaluation** environments where SATA controllers may be present but not populated with disks.  Standard **production** deployments are not expected to include unused SATA controllers. | Disabling an Embedded SATA Controller (HPE ProLiant)   1. Reboot the server. 2. Press **F9** to enter **System Utilities**. 3. Navigate to:  **System Configuration** → **BIOS/Platform Configuration (RBSU)** → **PCIe Device Configuration**. 4. For **each** embedded SATA controller that is not in use:     - Select the controller (for example, Embedded SATA Controller #1).    - Change the **SATA Device Disable** from **Auto** to **Disabled**. 5. Press F12 to save the changes and exit, followed by reboot. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json b/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
new file mode 100644
index 0000000..38a4e58
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+  "title": "Zerto",
+  "ordinal": 386,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-66740846-A143-48D1-80FF-7314D86BE61A.html",
+  "topic_cluster": {
+    "clustering_title": "Zerto",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md b/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
new file mode 100644
index 0000000..8060c94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
@@ -0,0 +1,56 @@
+# Zerto
+
+![Morpheus and Zerto Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+## Overview
+
+By integrating HPE Morpheus Enterprise and Zerto, HPE Morpheus Enterprise will automatically bring in your pre-existing Zerto replication groups as well as allow you to create and edit replication groups from within HPE Morpheus Enterprise UI. Additionally, the Zerto integration can be set as the replication provider to existing compatible Clouds (such as VMware vCenter Clouds) to allow new workloads to be added to replication groups. If needed, new replication groups can also be created at provision time with the newly provisioned VMs added to them. The Zerto integration detail page also provides summary details for the integration as well as listing out replications and replication sites which are available to use with replication groups.
+
+## Adding a Zerto Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Zerto
+4. Fill in the following: 
+
+   Name
+   :   A friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled and made available for consumption in HPE Morpheus Enterprise
+
+   API URL
+   :   API URL for the Zerto Virtual Manager (ex. `API URL: https://xx.xx.xx.xx:9669`)
+
+   Username
+   :   Username for an admin Zerto service account
+
+   Password
+   :   Password for the provided user (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Restricts integration access to users in the current Tenant (subject to additional RBAC settings)
+
+           Public
+           :   The integration is accessible to all Tenants (option available to Master Tenant users only)
+5. Once complete, click SAVE
+
+### Results
+
+NOTE
+
+In addition to manually entering username and password credentials in this modal, users also have the option to use a stored username/password credential set, or manually enter credentials and have them stored for later use in the HPE Morpheus Enterprise secure credential store. See the CREDENTIALS configuration in the add/edit integration modal for all of these options.
+
+Once the integration is created, you can click into the integration detail page to see existing replication groups, summary data, and other information about replications and replication sites.
+
+## Setting a Replication Provider
+
+With the integration created, Zerto can be added as the replication provider for compatible Clouds. Edit an existing Cloud (click the EDIT button from the Cloud detail page) and expand the Advanced Options section. In the dropdown for Replication Provider, select the Zerto integration. Finally, save the Cloud to commit the changes.
+
+With the Cloud and the Zerto integration associated, you will now see additional replication options at provision time. When provisioning to the associated Cloud in the future, expand the Replication section from within the AUTOMATION tab of the provisioning wizard. Here you have the option of adding newly provisioned VMs to an existing replication group. Additionally, you may also create a brand new replication group from within the provisioning wizard itself if a new group is needed.
+
+![../../_images/zertoProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DC7C1357-FBBB-469E-A3EC-D2EFAA786192-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json b/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
new file mode 100644
index 0000000..16098da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+  "title": "Building Catalog Workflows",
+  "ordinal": 142,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md b/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
new file mode 100644
index 0000000..7fd0896
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
@@ -0,0 +1,34 @@
+# Building Catalog Workflows
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Workflow. The modal window will appear to configure and add a new catalog Workflow.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this Workflow item will be available for selection in the Service Catalog
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **WORKFLOW:** Select an existing Workflow to be associated with this Catalog Item, new Workflows are created in Library > Automation
+- **CONTEXT:** Optionally restrict users to a specific target context, Instance, Server, or None
+- **CONFIG:** Enter an optional custom config JSON body. See [Workflows documentation](https://docs.morpheusdata.com/en/latest/library/automation/workflows.html#allow-custom-config) for a formatting example
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json b/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
new file mode 100644
index 0000000..7be75a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+  "title": "Automation",
+  "ordinal": 103,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md b/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
new file mode 100644
index 0000000..c947e97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
@@ -0,0 +1,13 @@
+# Automation
+
+Library  >  Automation
+
+The Automation section is composed of Tasks and Workflows. Tasks can be scripts added directly, scripts and blueprints from the Library section, recipes, playbooks, puppet agent installs, or http (api) calls. These Tasks are are combined into workflows, which can be selected to run at provision time or executed on existing instances via Actions  >  Run Workflow.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html)**
+- **[Scale Thresholds](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html)**
+- **[Power Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json b/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
new file mode 100644
index 0000000..4890d2a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+  "title": "User Settings",
+  "ordinal": 334,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md b/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
new file mode 100644
index 0000000..5efb33e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
@@ -0,0 +1,14 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your HPE Morpheus Enterprise username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
+
+![../../_images/user_settings500.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1A22C9CD-F310-4AEF-A818-55C0954C9C55-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json b/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
new file mode 100644
index 0000000..1480e03
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+  "title": "Cluster Permissions",
+  "ordinal": 173,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md b/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
new file mode 100644
index 0000000..160cd6b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
@@ -0,0 +1,6 @@
+# Cluster Permissions
+
+- Cluster Permissions
+  :   Each Cluster has Group, Tenant and Service Plan access permissions settings (“MORE” > Permissions on the Clusters list page).
+- Namespace Permissions
+  :   Individual Namespaces also have Group, Tenant and Service Plan access permissions settings
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json b/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
new file mode 100644
index 0000000..8e4bd44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+  "title": "Convert to Provisioned Node",
+  "ordinal": 421,
+  "parent_title": "Import Pre-Provisioned Servers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html",
+  "topic_cluster": {
+    "clustering_title": "Convert to Provisioned Node",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md b/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
new file mode 100644
index 0000000..32468c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
@@ -0,0 +1,20 @@
+# Convert to Provisioned Node
+
+## About this task
+
+Perform the following to convert to Managed or create a new instance:
+
+## Procedure
+
+1. After the server is imported, go to Infrastructure > Compute > Bare Metal.
+2. Select the imported server.
+3. Click Convert to Managed. ![Convert to Managed](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3462CBDA-30E9-451B-9EDE-E68FA70DDA5F-high.png)
+4. Confirm the server details and click Execute. ![Convert to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8CCF2394-D2E1-4815-AEC2-8E706E61732D-high.png)
+
+   NOTE
+
+   Use the same OS credentials that were provided during the import step.
+
+## Results
+
+The Convert to Managed action creates a new instance, makes the selected server a fully provisioned node, and adds it to the new instance. It creates the association of this server with networks and volumes in HPE Morpheus, as present in the network switches and the storage array, respectively. In addition, it creates the association of the VLAN interfaces with the IP addresses on the host OS on the server.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json b/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
new file mode 100644
index 0000000..0c5a770
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+  "title": "Instance Types",
+  "ordinal": 128,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md b/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
new file mode 100644
index 0000000..2f092e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
@@ -0,0 +1,60 @@
+# Instance Types
+
+Adding an Instance Type creates a new Library item category. Multiple Layouts can be added to an Instance Type and these Layouts can have different Nodes attached. The Instance provisioning wizard will present the Layout options compatible with the selected Cloud. If Cloud selection is turned off, all Layouts will be presented for all Cloud types accessible by the User.
+
+![../../_images/instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C56262F7-FB82-4802-A8D8-DEE2D9FE3DB1-high.png)
+
+Name
+:   Name of the Instance Type in the provisioning Library
+
+Code
+:   A useful shortcode for provisioning naming schemes and export reference
+
+Description
+:   The description of the Instance Type shown in the Provisioning Library. (255 characters max)
+
+Category
+:   For filtering in Instance sections and provisioning wizard
+
+    - Web
+    - SQL
+    - NoSQL
+    - Apps
+    - Network
+    - Messaging
+    - Cache
+    - OS
+    - Cloud
+    - Utility
+
+Icon
+:   An identifiable icon to display in-line with your Instance Type in the provisioning wizard (Suggested dimensions: 150 x 51)
+
+Visibility
+:   - Private: Only accessible by assigned Accounts/Tenants
+    - Public: Accessible by all Accounts/Tenants
+
+Inputs
+:   Custom options presented to the user at provision time, Inputs are also created and stored in Morpheus Library
+
+Price Sets
+:   Associate a Price Set with the Instance Type, Price sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Instance Types become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Instance Type. If this Instance Type is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Instance Type Price Sets Demo**
+
+Environment Prefix
+:   Used for exportable environment variables when tying Instance Types together in App contexts. If not specified, a name will be generated
+
+Environment Variables
+:   Name and value pairs for environment variables to be loaded on initialization
+
+Enable Settings
+:   Allows for attachment of modifiable file templates to Node Types in a settings tab of the Instance after deployment
+
+Enable Scaling (Horizontal)
+:   Enables load balancer assignment and auto-scaling features
+
+Support Deployments
+:   Enables deployment features (Requires a data volume be configured on each version. Files will be copied into this location)
+
+Upon saving, this Instance Type will be available in the provisioning catalog, per User Role access. However, we still need to add Layouts to the Instance Type, and prior to creating a Layout, we will add a Node Type.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json b/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
new file mode 100644
index 0000000..205fcd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+  "title": "Open Telekom Cloud",
+  "ordinal": 468,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6B3D18B4-5885-4318-848F-DE294F57057B.html",
+  "topic_cluster": {
+    "clustering_title": "Open Telekom Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md b/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
new file mode 100644
index 0000000..553a400
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
@@ -0,0 +1,222 @@
+# Open Telekom Cloud
+
+Open Telekom Cloud is an Openstack-based public cloud offering. HPE Morpheus Enterprise offers a robust integration into OTC and supports many of its features, including those listed in the next section.
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- OBS buckets (create, manage, delete, and discovery)
+
+## Add an Open Telekom Cloud
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Open Telekom Cloud and click NEXT. Complete the ADD CLOUD modal, the remainder of this guide includes descriptions of the fields presented on this modal with advice on formatting needed values and where certain data can be located.
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity API URL, such as `https://iam.eu-de.otc.t-systems.com/v3`
+
+DOMAIN ID
+:   Note that this is the Domain ID and not the Domain Name. The Domain ID can be found via the CLI by typing `openstack domain list`. For default domains, “Default” can be used
+
+PROJECT
+:   OTC projects are groupings of resources and can include compute resources, storage or networking. Multiple projects may be nested under your account. Select the project to which HPE Morpheus Enterprise should onboard from (if desired) and provision
+
+REGION
+:   OTC Region
+
+USERNAME
+:   The username for the OTC service account that HPE Morpheus Enterprise will use. Ensure this account has sufficient cloud privileges to avoid interruption of work in HPE Morpheus Enterprise
+
+PASSWORD
+:   The password for the above service account
+
+IMAGE FORMAT
+:   Select QCOW, RAW or VMDK
+
+IMAGE STORE
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+INVENTORY EXISTING IMAGES
+:   When selected, HPE Morpheus Enterprise will automatically onboard existing cloud resources which can be converted to managed Instance if desired. View onboarded cloud resources in the Compute Section (Infrastructure > Compute)
+
+ENABLE HYPERVISOR CONSOLE
+:   Hypervisor console support for Openstack currently only supports `novnc`. Be sure the novnc proxy is configured properly in your Openstack environment
+
+### Service Endpoints
+
+If needed, update the following service endpoints. A complete listing of OTC API endpoints is [here](https://docs.otc.t-systems.com/endpoint/index.html).
+
+- COMPUTE SERVICE
+- IMAGE SERVICE
+- STORAGE SERVICE
+- NETWORK SERVICE
+- LOAD BALANCER SERVICE
+- OBJECT STORAGE SERVICE
+- SHARED FILE SYSTEM SERVICE
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Network and Router Creation
+
+Once an Open Telekom Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Open Telekom Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Open Telekom Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Open Telekom Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OTC project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json b/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
new file mode 100644
index 0000000..f6d2d5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+  "title": "Host Features",
+  "ordinal": 176,
+  "parent_title": "Features",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md b/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
new file mode 100644
index 0000000..0384378
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
@@ -0,0 +1,21 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Intelligent vCPU placement to lock vCPU cores to the same NUMA node and L3 cache
+- Host hardware sensor data collection
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and data stores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Integration with HPE Morpheus Enterprise costing
+- Governance through HPE Morpheus Enterprise RBAC, Tenancy, and Policies
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json b/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
new file mode 100644
index 0000000..313fe85
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+  "title": "Prices",
+  "ordinal": 291,
+  "parent_title": "Plans",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html",
+  "topic_cluster": {
+    "clustering_title": "Prices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md b/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
new file mode 100644
index 0000000..dbc85b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
@@ -0,0 +1,85 @@
+# Prices
+
+Details on various price configurations are given here. When creating prices, it’s also necessary to understand how they will be applied. Specifically, this relates to the **INCUR CHARGES** configuration. Charges can be incurred “While Running”, “While Stopped”, or “Always”. It typically makes the most sense to have running and stopped prices for a given type (Cores, for example) OR to have an “Always” price (but not both). This is because the prices do not stack and the higher of a competing “Always” or running/stopped price will take precedence. This can lead to confusion over which price was applied and how a final cost total was computed. You should decide in advance for a given price type for a price set whether you wish to charge an “Always” rate or charge separately for running/stopped states.
+
+Price Types
+:   - Everything: One price for all resources Storage, CPU, Memory, and Disks
+    - Memory + CPU
+    - Memory Only (per MB)
+    - Cores Only (per core)
+    - Disk Only (per GB)
+    - Platform: Select from Windows, Linux (generic), or one of several specific Linux distributions
+    - Software/Service: Add prices for software licenses which may be included with your price sets
+    - Datastore (per GB)
+    - Load Balancer
+    - Load Balancer Virtual Server
+
+Price Units
+:   - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+Currency
+:   - AED
+    - ARS
+    - AUD
+    - BRL
+    - BWP
+    - CAD
+    - CHF
+    - CLF
+    - CLP
+    - COP
+    - DKK
+    - EUR
+    - GBP
+    - IDR
+    - ILS
+    - INR
+    - JOD
+    - JPY
+    - KRW
+    - MAD
+    - MNT
+    - MYR
+    - MXN
+    - NGN
+    - NOK
+    - NZD
+    - PLN
+    - ROL
+    - RUB
+    - SAR
+    - SEK
+    - SGD
+    - THB
+    - TRL
+    - USD
+    - USN
+    - VND
+    - XAF
+    - XCD
+    - XOF
+    - XPF
+    - ZAR (South African Rand)
+
+Cost
+:   The base cost of the resource(s). The Price will match the Cost unless a Price Adjustment is added.
+
+Price Adjustment
+:   - **None:** Default, no markup added and Price will match Cost
+    - **Fixed Markup:** A fixed amount added to the Cost. Price will equal Cost + Markup.
+    - **Percentage Markup:** Adds a percentage markup to Cost. Price equals Cost + (Cost x Markup %)
+    - **Custom Price:** Sets a Price independent from the Cost. If the Cost changes, a Custom Price will not.
+
+Price
+:   A computed value of the final price including the cost plus any applicable markup.
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json b/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
new file mode 100644
index 0000000..433d249
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+  "title": "Additional Configuration Options",
+  "ordinal": 29,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html",
+  "topic_cluster": {
+    "clustering_title": "Additional Configuration Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md b/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
new file mode 100644
index 0000000..bf6e1aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
@@ -0,0 +1,13 @@
+# Additional Configuration Options
+
+**Subtopics**  
+
+- **[Advanced morpheus.rb Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html)**
+- **[Load Balancer Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html)**
+- **[Offline Installations and Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html)**
+- **[Import Trusted Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html)**
+- **[Data Encryption](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html)**
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html)**
+- **[IPv6](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json b/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
new file mode 100644
index 0000000..498879a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+  "title": "Softlayer",
+  "ordinal": 471,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6C22C389-3D06-4DF0-B997-1CA161175182.html",
+  "topic_cluster": {
+    "clustering_title": "Softlayer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md b/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
new file mode 100644
index 0000000..63df293
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
@@ -0,0 +1,147 @@
+# Softlayer
+
+## Add a Softlayer Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   Softlayer Username
+
+API Key
+:   Softlayer User API Key, accessible in the Softlayer Portal under `Account  >  Users  >  View API Key
+
+Datacenter
+:   Datacenters will auto-populate upon successful authentication with the above credentials. Select appropriate Datacenter for this Cloud.
+
+Object Store
+:   Select the destination Object Store
+
+Inventory Existing Instances
+:   If enabled, existing Softlayer Instances will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json b/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
new file mode 100644
index 0000000..ab7d722
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+  "title": "Allow Custom Config",
+  "ordinal": 115,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md b/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
new file mode 100644
index 0000000..6c5266b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
@@ -0,0 +1,32 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on Operational Workflows, the user is shown a text area for custom configuration at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Workflow is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json b/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
new file mode 100644
index 0000000..5b83fb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+  "title": "Supported Integration Versions",
+  "ordinal": 524,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Integration Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md b/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
new file mode 100644
index 0000000..ddefe44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
@@ -0,0 +1,56 @@
+# Supported Integration Versions
+
+Morpheus supports an extensive range of software integrations and versions past and present. Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+In addition, HPE Morpheus Enterprise is verified to work with, but not limited to:
+
+## Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 1. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+If you have any specific requirements please contact [support@morpheusdata.com](mailto:support%40morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json b/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
new file mode 100644
index 0000000..acf6e89
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+  "title": "VM Features",
+  "ordinal": 177,
+  "parent_title": "Features",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md b/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
new file mode 100644
index 0000000..4533659
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Guest and hypervisor console support for running workloads with selectable hypervisor console keyboard layouts
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore HVM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- HPE Morpheus Enterprise library and automation support
+- Integration with HPE Morpheus Enterprise costing features
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json b/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
new file mode 100644
index 0000000..a1a7651
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+  "title": "Uploading OS Images Using Local Storage",
+  "ordinal": 408,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md b/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
new file mode 100644
index 0000000..24fbb35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
@@ -0,0 +1,16 @@
+# Uploading OS Images Using Local Storage
+
+## Prerequisites
+
+- Ensure that Morpheus-app user owns the storage directory.
+- Ensure that Morpheus-app user has access to the storage path.
+
+## About this task
+
+Local storage allows OS images to be uploaded directly to the Morpheus appliance filesystem and is suitable for smaller environments or evaluation use cases.
+
+## Procedure
+
+1. Configure a Local Storage file share under Infrastructure > Storage > File Shares.
+2. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+3. Verify the image status is **Active**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json b/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
new file mode 100644
index 0000000..0193b4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+  "title": "Option Lists",
+  "ordinal": 155,
+  "parent_title": "Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html",
+  "topic_cluster": {
+    "clustering_title": "Option Lists",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md b/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
new file mode 100644
index 0000000..481181c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
@@ -0,0 +1,468 @@
+# Option Lists
+
+Option Lists allow you to give the user more choices during provisioning to then be passed to scripts and/or automation. Option Lists, however, are pre-defined insofar as they are not free-form. They can be manually entered CSV or JSON, they can be dynamically compiled from REST calls via GET or POST requests, or populated by LDAP queries.
+
+![../../_images/newOptionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-90142EEF-2840-4A18-9295-9DFD5C795BC8-high.png)
+
+## Generic Option List Fields
+
+The displayed fields in the create/edit Option List modal depend on the TYPE value selected.
+
+NAME
+:   Name of the Option List
+
+DESCRIPTION
+:   Description of the Option List for reference in Option List list view
+
+TYPE
+:   - **REST:** REST API call to populate Option List
+    - **Manual:** Manually entered dataset, CSV or JSON
+    - **Morpheus API:** Call to internal HPE Morpheus Enterprise API to populate the Option List
+    - **LDAP:** Searches and returns a list of Active Directory objects
+    - **Plugin:** Sourced by custom-coded `DataSetProvider` plugins. See [developer documentation](https://developer.morpheusdata.com/docs#dataset-providers) for additional details
+
+VISIBILITY
+:   If the account currently signed in is not in the master tenant, visibility will automatically change to private
+
+## Manual Option List Fields
+
+DATASET
+:   Appears only for manual Option Lists. Add your CSV or JSON list to this field
+
+    NOTE
+
+    JSON entries must be formatted like the following example: `[{"name":"Test","value":1},{"name":"Testing","value":2}]`
+
+## Plugin Option List Fields
+
+OPTION LIST
+:   Select an Option List made available by a currently-integrated plugins
+
+## REST Option List Fields
+
+SOURCE URL
+:   A REST URL used to fetch list data which is cached in the appliance database
+
+REAL TIME
+:   When checked, a REST call will be made to update the Option List at the time its presented to the User
+
+IGNORE SSL ERRORS
+:   Do not fail API query for self-signed or invalid certs on REST call target
+
+INJECT SYSTEM AUTHORIZATION HEADER
+:   Select when calling back into the HPE Morpheus Enterprise API to automatically inject authorization headers
+
+USE OWNER AUTHORIZATION
+:   Select when calling back into the HPE Morpheus Enterprise API. When enabled, the Option List will be populated using the Option List owner's Role permissions rather than the logged in User's at execution time to ensure complete list population
+
+SOURCE METHOD
+:   GET or POST
+
+SOURCE HEADERS
+:   Custom HTTP Headers to include in the source request
+
+CREDENTIALS
+:   Use a stored credential set or manually enter credentials to access data requiring authentication. Currently, only basic auth is supported
+
+INITIAL DATASET
+:   Create an initial JSON or CSV dataset to be used as the collection for this option list. It should be a list containing objects with properties ‘name’ and ‘value’
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    for(var x=0;x < data.length; x++) {  
+      results.push({name: data[x].name,value:data[x].id});  
+    }
+    ```
+    ```
+
+REQUEST SCRIPT
+:   Create a JS script to prepare the request. Return a data object as the body for a POST request, and return an array containing properties ‘name’ and ‘value’ for a GET request. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’
+
+    **Example:**
+
+    ```
+    ```
+    results.push({name: 'userId', value : data.users})
+    ```
+    ```
+
+    In a GET request (SOURCE METHOD = GET), the value of the results variable is used to build out the request parameters. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1",value: "value1"}]
+    ```
+    ```
+
+    The request would be made to: `https://<someURL>?name1=value1`.
+
+    In a POST request (SOURCE METHOD = POST), the value of the results variable is used to build the body of the POST request. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1", value:"value1"}, {name:"name2", value:"value2"}]
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    {name:"name1", value:"value1"}, {name:"name2", value:"value2"}
+    ```
+    ```
+
+    An alternative method to building the POST request (SOURCE METHOD = POST), can be seen below. As well, we can access other **Inputs** that are available on the same form, when provisioning an Instance or Catalog Item. As seen below, the other Inputs can be accessed using the `data` variable. We can access another Input by calling its **Field Name**, which can be configured when editing the Input in Library > Options > Inputs. This allows using data from other Inputs to be used in this Input’s request.
+
+    In the example below the Input Field Name we’ll access is `myinputfieldname`, which we can get either the name (visible value for lists) or value from the item:
+
+    Name variable: `data.myinputfieldname` Value variable: `data.myinputfieldname_value`
+
+    ```
+    ```
+    var postBody = {};  
+    postBody["number"] = data.myinputfieldname_value;  
+    postBody["env"] = "all";  
+    results = postBody;
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    { "number": "123456", "env": "all" }
+    ```
+    ```
+
+## Morpheus API Option List Fields
+
+OPTION LIST
+:   A list of available object types to return
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    var i=0;  
+    results = [];  
+    for(i; i<data.length; i++) {  
+      results.push({name: data[i].name, value: data[i].value});  
+    }
+    ```
+    ```
+
+    Translation script inputs:
+
+    **Clouds**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `code: <String>`
+    - `description: <String>`
+    - `regionCode: <String>`
+    - `location: <String>`
+    - `zoneType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `cloud: <String>` // “public” or “private” value
+      - `code: <String>`
+
+    **Environments**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `code: <String>`
+    - `name: <String>`
+
+    **Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `name: <String>`
+    - `code: <String>`
+    - `uuid: <String>`
+    - `location: <String>`
+    - `datacenterId: <Number>`
+
+    **Instances**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `category: <String>`
+    - `description: <String>`
+    - `apiKey: <String>`
+    - `status: <String>`
+    - `hourlyPrice: <Number>`
+    - `hourlyCost: <Number>`
+    - `instanceType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `plan: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `site: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+
+    **Instances Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `instanceId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+    **Networks**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `category: <String>`
+    - `name: <String>`
+    - `status: <String>`
+    - `cloudId: <Number>`
+    - `groupId: <Number>`
+    - `networkType:<Object>`
+
+      - `id: <Number>`
+      - `code: <String>`
+      - `name: <String>`
+    - `externalId: <String>`
+    - `externalNetworkType: <String>`
+    - `networkDomain: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `networkPool: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `createdBy: <String>`
+
+    **Plans**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `storage: <Integer, bytes>`
+    - `memory: <Integer, bytes>`
+    - `cores: <Number>`
+
+    **Resource Pools**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `externalId: <String>`
+    - `name: <String>`
+    - `serverGroupId: <Number>`
+    - `status: <String>`
+    - `regionCode: <String>`
+    - `parentPoolId: <Number>`
+    - `type: <String>`
+
+    **Security Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `externalType: <String>`
+    - `externalId: <String>`
+    - `cloudId: <Number>`
+    - `scopeMode: <String>`
+    - `scopeId: <Number>`
+
+    **Servers**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `description: <String>`
+    - `category: <String>`
+    - `osType: <String>`
+    - `powerState: <String>`
+    - `lastStats: <String>`
+    - `zone: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `capacityInfo: <Object>`
+
+      - `maxStorage: <Integer, bytes>`
+      - `maxMemory: <Integer, bytes>`
+      - `maxCores: <Number>`
+      - `usedMemory: <Integer, bytes>`
+      - `usedStorage: <Integer, bytes>`
+    - `computeServerType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `nodeType: <String>`
+      - `vmHypervisor: <String>`
+      - `containerHypervisor: <String>`
+
+    **Servers Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `serverId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+REQUEST SCRIPT
+:   The request script is used differently for Morpheus API Option List types. A Morpheus API option list type will use an internal API to return a list of objects instead of performing HTTP(S) requests to the Morpheus API. Due to this approach, the results object will not be used to generate query parameters or a JSON body. The results object will instead be used to contain a map of accepted key:value pairs that can be used to filter, sort and order the list of objects that get returned.
+
+    Below is a list of accepted `key:value` pairs for each object type:
+
+    **Generic options available for all object types**
+
+    - `max: <integer>` // Maximum number of results to return. Default: 25
+    - `offset: <integer>` // Offset for returned results. Default: 0
+    - `sort: <string>` // Field to sort on. Default: ‘name’
+    - `order: <string>` // Order of returned values. Accepted values: ‘asc’, ‘desc’. Default: ‘asc’
+
+      **Example:**`results = {max: 5, order : 'desc'}`
+
+    **Networks**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only networks associated with this provision type
+    - `layoutId: <Number>` // Id of an Instance Layout, ignored if provisionTypeId is supplied, otherwise used to look up the provision type
+    - `poolId: <Number>` // Id of a network pool, filters to only networks within the specified network pool
+
+    **Instance Networks**
+
+    Contains same options for Networks Morpheus API but pre-filtered for Networks applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Plans**
+
+    - `zoneId` // Required. In order for plans to be returned and properly filtered, you must provide a `zoneId` and `siteId` as well as either a `layoutId` or `provisionTypeId`
+    - `siteId`
+    - `layoutId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only plans associated with this provision type
+
+    **Resource Pools**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `layoutId: <Number>` // Id of an Instance Layout, used to get the associated provision type and filter to that provision type
+
+    **Security Groups**
+
+    - `zoneId` // required
+    - `poolId`
+
+    **Clouds**
+
+    - `zoneId : <integer>` // Database ID of cloud to return
+    - `tenantId : <integer>` // Database ID of tenant where clouds are added. Filters to only clouds added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` // Database ID of cloud type. Filters to only clouds with the specified cloud type
+    - `siteId : <integer>` // Database ID of group. Filters to only clouds within the specified group
+    - `tagName : <string>` // Filters to clouds with servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to clouds with servers that have tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on cloud name and description
+
+      **Example:**`results = {tenantId: 1, siteId: 1, tagName: "morpheus"}`
+
+    **Instance Types Clouds**
+
+    Contains same options for Clouds Morpheus API type but pre-filtered for Clouds applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Instances**
+
+    - `appsId : <integer>` // Database ID of app to filter by. Returns instances linked to the app
+    - `tenantId : <integer>` // Database ID of tenant where instances are located. Filters to only instances within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the instance that contains the specified server
+    - `tagName : <string>` // Filters to instances with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to instances with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on instance name and description
+
+      **Example:**`results = {tenantId:1, phrase: "ha"}`
+
+    **Groups**
+
+    - `tenantId : <integer>` // Database ID of tenant where groups are located. Filters to only groups added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` Database ID of cloud type. Filters to only groups that contain clouds with the specified cloud type
+    - `zoneId : <integer>` // Database ID of cloud. Filters to only groups that contain the cloud with the specified ID
+    - `siteId : <integer>` // Database ID of group to return
+    - `phrase : <string>` // Fuzzy matches phrase on group name and location.
+
+    **Servers**
+
+    - `tenantId : <integer>` // Database ID of tenant where servers are located. Filters to only servers within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the server specified by the ID
+    - `siteZoneId : <integer>` // Database ID of cloud. Filters to servers contained within the specified cloud
+    - `serverType : <string>` // Type of server. Accepted values: ‘host’, ‘baremetal’, ‘vm’
+    - `siteId : <integer>` // Database ID of group. Filters to only servers contained within clouds that are added in the specified group
+    - `tagName : <string>` // Filters to servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to servers with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on server name and description.
+
+      **Example:**`results = {max: 50, siteZoneId : 3}`
+
+    **Instances Wiki**
+
+    Contains same options for Instances Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Servers Wiki**
+
+    Contains same options for Servers Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+## LDAP Option List Fields
+
+LDAP URL
+:   The URL pointing to the LDAP server
+
+USERNAME
+:   The fully qualified username (with @ suffix syntax) for the binding account
+
+PASSWORD
+:   The password for the above account
+
+LDAP Query
+:   The LDAP query to pull the appropriate objects. See the next section for an example use case
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+NOTE
+
+Option Lists are set on one or multiple `Select List` or `Typeahead` Inputs. The Input is then set on an Instance Type, Layout, Cluster Layout, and/or Operational Workflow for input during provisioning or execution.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
new file mode 100644
index 0000000..fecee1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+  "title": "Supported Locales",
+  "ordinal": 12,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Locales",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
new file mode 100644
index 0000000..2ad0ee4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
@@ -0,0 +1,28 @@
+# Supported Locales
+
+Morpheus supports a number of different UI locales, including:
+
+- English
+- French
+- German
+- Spanish
+- Chinese (Simplified)
+- Portuguese (Brazil)
+- Korean
+- Italian
+
+The full list of supported locales can be viewed within the Morpheus UI via the “Default Appliance Locale” select list within Administration Settings.
+
+## Switching Locales
+
+The language of text in the Morpheus UI can be changed by telling the Morpheus server which locale to use. A Locale is made up of a language code and a country code. For example “en\_US” is the code for US English, whilst “en\_GB” is the code for British English. When using the Morpheus UI software through a client, the Morpheus UI software server will send the UI text back to the client using the appropriate static Language Pack. All translations returned via Morpheus Internationalization have been made and approved prior to the Morpheus UI version release.
+
+**Via Locale Settings in the Morpheus UI:** An application wide default locale can be configured within the Master Tenant under Administration -> Settings -> Default Appliance Locale. An individual Morpheus user can configure a preferred locale within their user settings. Using a locale setting is the preferred method for switching the Morpheus UI language.
+
+**Via the Accept-Language HTTP header:** The Accept-Language request HTTP header advertises which languages the client is able to understand, and which locale variant is preferred. Most browsers will by default send a “Accept-Language” HTTP header when visiting websites. The value of Accept-Language will match the configured preference of the browser’s user language/locale settings. The Morpheus UI will automatically detect the Accept-Language header and return the UI text from the corresponding Language Pack where possible. If there is no matching Language Pack the English US language pack is displayed in the UI. If an application locale or user locale setting has been configured in the Morpheus UI, then this will override the user’s browser preferences.
+
+**Via the “lang” query parameter:** Morpheus has the capability to switch locales by passing a parameter called “lang” to the Morpheus UI request. For example, “operations/dashboard?lang=de” will switch the locale preference to German. Morpheus will automatically switch the user’s locale and store it in a cookie so subsequent requests will have the new header. If a user is unauthenticated then the user’s locale will be reset. To switch a locale back to English pass “?lang=en” as a query parameterin the Morpheus UI request.
+
+NOTE
+
+Many of Morpheus’ language packs are generated by our clients. For that reason, we cannot guarantee accuracy and completeness of the translation. As new UI elements are added, existing language sets may not have immediate updates to keep pace with application changes. If you would like to contribute to a new or existing language pack, contact your account team or Morpheus support. Contributed content will be included within the next application version.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json b/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
new file mode 100644
index 0000000..5ee91da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+  "title": "Checks",
+  "ordinal": 258,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html",
+  "topic_cluster": {
+    "clustering_title": "Checks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md b/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
new file mode 100644
index 0000000..20de295
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
@@ -0,0 +1,87 @@
+# Checks
+
+The Monitoring system is composed of individual checks. A check is created for every container or vm that is provisioned through HPE Morpheus Enterprise . One interesting thing about these checks is they are type aware. There are several different built in check types that are selected based on the service or instance type that is being provisioned. These range from database type checks to web checks and message checks. They are highly configurable and also feature fallback check types for those more generic use cases.
+
+Checks can be customized to run custom queries, check queue sizes, or even adjust severity levels and check intervals. All of these things can be controlled from the Checks sub tab within Monitoring.
+
+## Health
+
+A Check can have one of four primary health states, which are Error, Healthy, Warning, and Unknown. Checks can also be muted, in which case they are effectively disabled and are not actively run to gather an updated health state. While Checks are muted, the availability percentage does not change regardless of the health of the workload being checked. The default view shows Checks in all health states but this view can be filtered to show just one health state. Change the view filter to “Happy” to see only Checks in a Healthy state, “Sad” to see only Checks in an Error state, “Warning” to see Checks in both a “Warning” and “Unknown” state, and “Muted” to see only muted Checks.
+
+When a Check test fails, the system automatically reattempts the Check after 30 seconds to eliminate false negatives. This will convert the Check into an error state and raise the appropriate severity incident depending on the grouping of the Check. When a Check recovers, it automatically goes into a Warning state. The Warning state will remain until 10 successful Check runs have completed.
+
+## Options
+
+All check types have several core options and some of these default options can be configured in Admin  >  Monitoring. This includes the default check interval time. By default a check is run every 5 minutes. This can however be changed to run as frequently as once every minute.
+
+- Max Severity: The maximum severity level impact for a created incident that can occur if the check fails (defaults to Critical).
+- Check Interval: The frequency with which a check is run (default 5 minutes).
+- Affects Availability: Whether or not this check impacts overall system availability calculations.
+
+## SSH Tunneling
+
+In many cases when it comes to monitoring databases, and services they may not be fronted on the public ip’s for external monitoring. To reach these safely, and securely HPE Morpheus Enterprise provides an SSH Tunneling mechanism for its check servers. This allows the check to be confirmed via an ssh port tunnel securely using a keypair.
+
+## Check Servers
+
+On a base installation of HPE Morpheus Enterprise a single check server is installed on the appliance. This is used for running any custom user checks. This service connects to the provided rabbitmq services and can be moved off or even scaled horizontally onto sets of check servers. All other checks that are related to provisioned containers or VMs are executed by the installed agent on the guest OS or Docker host.
+
+## Check types
+
+### Web Check
+
+A web check is useful to identify if a url is reachable and the text to match check criteria confirms if the website is loading with the expected values. The text to match character should be within the first few lines of the page source.
+
+Use case:
+:   Adding a check to make sure morpheus demo environment is functioning. The below check will login to the morpheus UI and look for a text Morpheus on the dashboard page.
+    :   Values to be added in Check:
+        :   - Name: “<enter name>”
+            - Type: Web Check
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Web Url: <https://demo.morpheusdata.com/operations/dashboard> (Note: this page will load only if my login is successful. Enter the login details in Username and password fields)
+            - Request Method: GET
+            - Basic Authentication: \* User: <username> \* Password: <password>
+            - Text to Match: “Morpheus” (Login to the url and on the page of dashboard, right click and select view page source. In the forst few lines, look for a text that you want this check to verify)
+            - Save Changes
+
+### Push API Check
+
+This check can be used to send an API call to morpheus from a platform to check if the push api is working. A push Check is not polled regularly by the standard monitoring system. Instead it is expected that an external API push updates as to the status of the check timed closely with the configured check interval setting. This is used to throttle the push from performing too many status updates.
+
+NOTE
+
+If a check is not heard from within the check intervals, It’s status will be updated to error and an incident will be raised as if it failed.
+
+Use Case:
+:   Send an API call from an app to make sure the API is not cluttered and can send checks in a 2 mins interval.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “Push API Check”
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Copy the curl command are schedule to send this via your API. For testing we used postman to send the api call at an interval of 4 mins.
+            - Save Changes
+
+### MySQL Check
+
+This check is used to run a query on a host running mysql.
+
+Use Case:
+:   Query localhost running mysql to query a table to check if there is any status as requested. If the status has a count of 1 then the check would pass else mark it as critical.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “MySQL Check”
+            - Interval: 5 mins (Select an interval)
+            - Check the box for affects availability
+            - Host: 127.0.0.1
+            - Port: 3306
+            - DB Name: morpheus
+            - User: <db user name>
+            - Password: <password>
+            - Query: “select count(\*) as count from request\_reference where status = ‘requested’;”
+            - Operator: Equal
+            - Check results: 1
+            - Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json b/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
new file mode 100644
index 0000000..934f04f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+  "title": "Tenants",
+  "ordinal": 277,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md b/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
new file mode 100644
index 0000000..2c2c325
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
@@ -0,0 +1,71 @@
+# Tenants
+
+The Tenants page displays a list of all Tenants. This page enables users to Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, and the Created Date.
+
+Click the Tenant Name to drill into the Tenant View where you can again Edit or Delete the Tenant, as well as Create Users, Edit Users, and Delete Users users belonging to the Tenant.
+
+## Create Tenants
+
+### About this task
+
+To Create Tenants:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Create Tenant button.
+4. From the New Tenant wizard input: 
+
+   - Name
+   - Description (optional)
+   - Subdomain
+   - Base Role
+   - Currency
+5. Within the Advanced Options section, track customer data related to the Tenant if needed: 
+
+   - Account Number
+   - Account Name
+   - Customer Number
+6. Click the Save Changes
+
+## Edit Tenant
+
+### About this task
+
+To edit a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Edit the Edit Tenant settings.
+
+## Disabling Tenant
+
+### About this task
+
+When disabling a tenant, they are not able to login and cannot be impersonated by another tenant. However all of their information will still remain in HPE Morpheus Enterprise and they may still receive notifications and alerts.
+
+To disable a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Uncheck the `Enabled` box.
+
+## Delete Tenant
+
+### About this task
+
+To delete a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Delete trashcan icon on the row of the Tenant to delete.
+4. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.json b/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
new file mode 100644
index 0000000..34ab914
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+  "title": "SSL Certificates",
+  "ordinal": 34,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.md b/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
new file mode 100644
index 0000000..39d265b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
@@ -0,0 +1,75 @@
+# SSL Certificates
+
+By default HPE Morpheus Enterprise generates a Self-Signed SSL Certificate. The Self-Signed SSL Certificate can be replaced with a Trusted CA Signed SSL Certificate.
+
+## Trusted CA Signed SSL Certificate Implementation
+
+### Procedure
+
+1. If you don’t already have your certificate, run an OpenSSL command to generate an SSL certificate request (.csr) and private key (.key). If you need help formatting the command, [DigiCert provides a helpful tool](https://www.digicert.com/easy-csr/openssl.htm)
+2. Submit your certificate request (.csr) and await approval of the request and return of the certificate (.crt)
+3. Copy the private key and certificate to `/etc/morpheus/ssl/your_fqdn_name.key` and `/etc/morpheus/ssl/your_fqdn_name.crt` respectively 
+
+   Extracting Certificates in PFX Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl pkcs12 -in example.pfx -nocerts -nodes -out priv.key  
+   # Extract the public key  
+   openssl pkcs12 -in example.pfx -clcerts -nokeys -out pub.crt  
+   # Extract the CA cert chain  
+   openssl pkcs12 -in example.pfx -cacerts -nokeys -chain -out ca.crt
+   ```
+   ```
+
+   Extracting Certificates in PEM Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key  
+   # Extract the public key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key
+   ```
+   ```
+4. Edit the configuration file `/etc/morpheus/morpheus.rb` and add the following entries: 
+
+   ```
+   ```
+   nginx['ssl_certificate'] = 'path to the certificate file'  
+   nginx['ssl_server_key'] = 'path to the server key file'
+   ```
+   ```
+
+   NOTE
+
+   Both files should be owned by root and only readable by root, also if the server certificate is signed by an intermediate then you should include the signing chain inside the certificate file. The key file needs to be decrypted for Morpheus to install it properly.
+5. Next simply reconfigure the appliance and restart nginx: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl restart nginx
+   ```
+   ```
+
+## Self-Signed SSL Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year Self-Signed SSL Certificate. Below details the process to regenerate the Certificate and Key files.
+
+### Regenerate both the Certificate and Key
+
+#### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
+
+### Regenerate only the Certificate
+
+#### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json b/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
new file mode 100644
index 0000000..99386f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+  "title": "HPE Morpheus Enterprise",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md b/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
new file mode 100644
index 0000000..433fd6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
@@ -0,0 +1,20 @@
+# HPE Morpheus Enterprise
+
+IMPORTANT
+
+This user manual pertains to HPE Morpheus Enterprise Software. [Click here](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest) for the HPE Morpheus VM Essentials Software user manual.
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html)**
+- **[Personas](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html)**
+- **[Diagrams](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json b/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
new file mode 100644
index 0000000..6d9d5bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+  "title": "Floating IPs",
+  "ordinal": 221,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html",
+  "topic_cluster": {
+    "clustering_title": "Floating IPs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md b/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
new file mode 100644
index 0000000..56fe9e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
@@ -0,0 +1,32 @@
+# Floating IPs
+
+## Overview
+
+HPE Morpheus Enterprise supports sync and management of floating IP addresses for OpenStack, Huawei, and OTC Clouds. When these Clouds are integrated and floating IPs are present, HPE Morpheus Enterprise will automatically sync them in. Once synced, floating IPs are viewable from their own list page (Infrastructure > Network > Floating IPs) and related options are presented during provisioning, teardown, and from Instance detail pages.
+
+NOTE
+
+The Floating IPs tab is present only when supported Clouds are integrated and floating IPs are available. Additional Cloud support is planned for the future.
+
+## Floating IPs List Page
+
+All Floating IPs known to HPE Morpheus Enterprise can be viewed on the Floating IPs List Page (Infrastructure > Network > Floating IPs). From the Floating IPs list page we can see the following:
+
+- **IP ADDRESS**: The address for the floating IP synced from a supported Cloud
+- **CLOUD**: The Cloud integration the floating IP was synced from
+- **STATUS**: “Free” when the floating IP is available and “Assigned” when the floating IP is currently assigned to a workload
+- **VM**: For assigned floating IPs, the VM which currently has the floating IP attached
+
+Free floating IPs will have a gear icon (⚙) at the end of the row. Click the gear icon and select “Release Floating IP” to release from within the source cloud and remove the entry from the Floating IPs list.
+
+![../../_images/floatIpList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-65C72DC3-8755-45A9-978E-2E3F840D4F91-high.png)
+
+## Working with Floating IPs
+
+When provisioning to supported Clouds, HPE Morpheus Enterprise will give the option to attach a floating IP at provision time. From the CONFIGURE tab of the provisioning wizard for supported Clouds, select the desired floating IP.
+
+![../../_images/floatIpSet.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9514094E-8567-4571-ACFD-C334FA3A166C-high.png)
+
+During Instance teardown, HPE Morpheus Enterprise gives the option to release the floating IP.
+
+![../../_images/floatIpDelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5B05E0B0-B6AA-440E-947C-C9683D20BF9C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json b/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
new file mode 100644
index 0000000..371f89a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+  "title": "Uploading OS Images Using CIFS (Samba)",
+  "ordinal": 410,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using CIFS (Samba)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md b/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
new file mode 100644
index 0000000..e2d57ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using CIFS (Samba)
+
+## About this task
+
+CIFS (Samba) allows OS images to be stored on a shared Windows or Linux file server.
+
+## Procedure
+
+1. Configure a CIFS file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the Samba share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json b/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
new file mode 100644
index 0000000..7952cb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+  "title": "Communication Data",
+  "ordinal": 9,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md b/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
new file mode 100644
index 0000000..c547e36
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
@@ -0,0 +1,101 @@
+# Communication Data
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency, Ports, and Protocols
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Open Search Check | Server Pull | Open Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | On‐demand when using a file or repository for Morpheus functions | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json b/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
new file mode 100644
index 0000000..799fd2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+  "title": "Cloud Foundry",
+  "ordinal": 392,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Foundry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md b/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
new file mode 100644
index 0000000..a616c69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
@@ -0,0 +1,441 @@
+# Cloud Foundry
+
+## Configuration
+
+### Adding PCF Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select CLOUD FOUNDRY from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   Cloud Foundry API Url
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+### Adding PCF Cloud From Infrastructure > Groups
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group
+3. Select the CLOUDS tab
+4. Scroll down to CLOUD FOUNDRY and select + ADD
+5. Populate the following: 
+
+   Name
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   Location
+   :   Description field for adding notes on the cloud, such as location.
+
+   Visibility
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   Select a Tenant if Visibility is set to Private to assign to Cloud to that Tenant. Multiple Tenants can be added by editing the cloud after creation.
+
+   API URL
+   :   Cloud Foundry API Url. Example `https://api.cf.morpheusdata.com`
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Review and then Select COMPLETE
+
+## Adding Spaces
+
+### About this task
+
+Cloud Foundry Spaces are referred to as Resource Pools in Morpheus. You can add a new Space by:
+
+### Procedure
+
+1. Navigating to the Cloud and selecting the Resources tab.
+2. Then, click :guilabel:‘+ Add Resource’.
+3. Give the Resource a Name
+4. Expand the Managers, Developers, and Auditors section to add specific Cloud Foundry users to the roles. When adding a user to these sections, use their Cloud Foundry email addresses.
+
+## Provisioning
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, as well as a generic Cloud Foundry Instance Type that will create a shell app used in conjunction with deployments. PCF Marketplace items can also be added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+## Deployments
+
+The Cloud Foundry App Instance Type is used in conjunction with deployments. Users do not have to pick deployment when creating a Cloud Foundry App Instance Type, but then Instance will only be a shell of a Cloud Foundry Application.
+
+A deployment in Morpheus can either point to a git hub repository or contain the actual manifest.yml and associated artifacts required for a Cloud Foundry deployment. During the deployment, Morpheus will gather up the files required. Therefore, if the deployment points to a git hub repository, Morpheus will fetch the files from git hub. Once the files are obtained, Morpheus will deploy the artifacts in a similar fashion to the Cloud Foundry cli. This includes parsing the manifest to obtain the parameters to create or update the Cloud Foundry application. Morpheus will ignore certain fields such as memory and disk size because they are dictated by the selected plan. Other fields are utilized such as routes. After parsing the manifest.yml file (including overwriting certain fields), Morpheus is ready to update or create the App in Cloud Foundry.
+
+After the App is configured, the artifacts references in the Morpheus deployment are uploaded to Cloud Foundry for the App. Note that when paths are referenced in the manifest.yml file, the paths continue to be relative to the manifest. So, a jar file under build/libs would need to be found under the build/libs directory.
+
+If Cloud Foundry services are specified in the manifest, they must already exist within Cloud Foundry. Morpheus App templates can be utilized to wire up Cloud Foundry services created by Morpheus. In this case, Morpheus will add all of the included service names defined in the App template to the manifest.yml services section. Therefore, multiple services can be used and wired up by Morpheus.”
+
+## Example
+
+To better understand how Morpheus parses the manifest.yml file, lets take a closer look at the Cloud Foundry ‘spring-music’ project. The project can be found here (<https://github.com/cloudfoundry-samples/spring-music>).
+
+The project contains the required manifest.yml file as well as the source code and build.gradle file to define how the project is to be built. After downloading the project to your local machine, build the project to generate the jar.
+
+Now, let’s take a look at the manifest.yml file:
+
+```
+```
+---  
+applications:  
+- name: spring-music  
+  memory: 1G  
+  random-route: true  
+  path: build/libs/spring-music.jar
+```
+```
+
+Using the Cloud Foundry docs (<https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html>), we can gain a better understanding of how this file is utilized by Cloud Foundry.
+
+- The `-name` parameter defines the name that will be given to the application in Cloud Foundry. Morpheus will overwrite this value with the name given to the Instance being created in Morpheus.
+- The `-memory` parameter (as well as the disk\_quota parameter if specified) will be overwritten by Morpheus based on the plan specified for the Instance.
+- The `-path` parameter defines, where relative to the manifest.yml file, your Cloud Foundry application can be found.
+- The `-random-route parameter`, as well as all other parameters described in the Cloud Foundry documentation will simply be passed through to Cloud Foundry.
+
+## Adding Marketplace Items
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds and select your Cloud Foundry Cloud
+2. Select the MARKETPLACE tab
+3. Select + ADD MARKETPLACE ITEM
+4. Select the HPE Morpheus Enterprise Instance Type to add the Marketplace Item to.
+5. Enter version
+6. Search for and select Marketplace Item
+7. Select SAVE CHANGES
+
+### Results
+
+A Node Type and layout will be created in the Library section and the layout will be automatically added to the Instance Type selected when adding the Marketplace Item.
+
+## Provisioning Instances
+
+### Seeded and Marketplace Items
+
+#### About this task
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, and PCF Marketplace items can also be easily added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select an Instance Type with a Cloud Foundry layout (MySQL, Redis and RabbitMQ plus Marketplace additions)
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select Version and Instance Configuration for a Cloud Foundry layout, ex: Cloud Foundry MySQL
+8. Select a Plan and available options for the Plan, or use the custom Plan
+9. Select a Space to add the Instance to
+10. Optionally configure advanced options
+11. Select NEXT
+12. Optionally configure Automation options
+13. Select NEXT
+14. Select COMPLETE
+
+#### Results
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
+
+### Cloud Foundry App Instance Type
+
+#### About this task
+
+IMPORTANT
+
+Add Deployments in Provisioning > Code > Deployments to be used when provisioning a Cloud Foundry App Instance Type.
+
+NOTE
+
+Minimal options are outlined below.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select the Cloud Foundry App Instance Type
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select a Plan and available options for the Plan, or use the custom Plan
+8. Select a Space to add the Instance to
+9. Select NEXT
+10. In the Deployments section, select a Deployment and Version to be deployed. These can be git repos or files added in Provisioning > Code > Deployments 
+
+    IMPORTANT
+
+    If services are specified in a git repo manifest, HPE Morpheus Enterprise assumes they are already exist in the PCF cloud with matching names.
+11. Select NEXT
+12. Select COMPLETE
+
+#### Results
+
+This will quickly create the Cloud Foundry Application, and then the deployment will follow which may take longer depending on the app configuration. The location will be updated with the route once it is configured.
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json b/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
new file mode 100644
index 0000000..1147d75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+  "title": "HPE Morpheus Enterprise Agent Key Features",
+  "ordinal": 44,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md b/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
new file mode 100644
index 0000000..ee7c459
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
@@ -0,0 +1,64 @@
+# HPE Morpheus Enterprise Agent Key Features
+
+While optional, HPE Morpheus Enterprise Agent provides many benefits and features in areas of log aggregation, security, automation, monitoring, and more. This page contains the complete summary of its key features and benefits.
+
+## Logging
+
+The installed HPE Morpheus Enterprise Agent captures application logs and sends them back to the HPE Morpheus Enterprise appliance. The Agent buffers and compresses logs, sending them in chunks to minimize packet transfers. If desired, users may set up forwarding to an external syslog platform though for most users HPE Morpheus Enterprise internal logging functionality is sufficient. Agent logs can be viewed in the UI at Monitoring > Logs. Filtering and search tools are available, even supporting [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html). Logs may also be exported.
+
+## Monitoring and Guidance
+
+HPE Morpheus Enterprise provides robust monitoring into the workloads it manages. For example, from Instance detail pages, usage metrics are tracked on the Summary and Monitoring tabs. The available metrics are significantly improved when HPE Morpheus Enterprise Agent is installed on the workload. HPE Morpheus Enterprise will make a best effort to gather this information in the absence of an installed Agent but for some Cloud types this is not possible. The table below shows the usage metrics HPE Morpheus Enterprise can gather with and without the Agent (though the exact metric available without the Agent will vary by Cloud).
+
+Table 1.
+
+      |  |  |  |  |
+| --- | --- | --- | --- |
+| **Category** | **Statistic** | **With Agent** | **Without Agent** |
+| Memory | Max Memory | Yes | Yes |
+| Memory | Used Memory | Yes | No |
+| Memory | Cache Memory | Yes | No |
+| Storage | Max Storage | Yes | Yes |
+| Storage | Used Memory | Yes | No |
+| Processing | System CPU % | Yes | No |
+| Processing | User CPU % | Yes | Yes |
+| IOPS | Total IOPS | Yes | No |
+| IOPS | IOPS Read | Yes | No |
+| IOPS | IOPS Write | Yes | No |
+| Networking | Net TX Rate | Yes | No |
+| Networking | Net RX Rate | Yes | No |
+| Other | Agent Command Bus | Yes | No |
+| Other | Log Aggregation | Yes | No |
+| Other | Health & Monitoring | Yes | No |
+
+In addition to usage and monitoring, HPE Morpheus Enterprise also provides a useful guidance feature (Operations > Guidance). Guidance analyzes your managed workloads and makes cost-saving or performance recommendations. The effectiveness of this feature is greatly enhanced when HPE Morpheus Enterprise Agent is installed on your workloads.
+
+## Script Execution
+
+The HPE Morpheus Enterprise Agent initiates an outbound connection from the managed workload to the appliance over TCP port 443. This establishes a bidirectional command bus which allows HPE Morpheus Enterprise to orchestrate automation on managed machines without stored credentials. Many different [Task types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html) are supported and Tasks can be stacked into Operational or Provisioning Workflows to create logical automation routines. SSH or WinRM connectivity, as well as credentials, are required for Task execution when HPE Morpheus Enterprise Agent is not installed.
+
+## Setting File Templates
+
+File Templates are stored templated text files, primarily config files (for example, `my.cnf` or `morpheus.rb`). Users have access to the full map of HPE Morpheus Enterprise variables for injecting values custom to the specific workload at provision time. HPE Morpheus Enterprise Agent can transfer files generated from templates to managed nodes.
+
+## Firewall Management
+
+When “Local Firewall” is enabled for a Cloud (see the Advanced Options section on the Add/Edit Cloud modal), the HPE Morpheus Enterprise Agent can manage host or VM IP Table (firewall) rules for Linux workloads.
+
+## Summary and Additional benefits:
+
+- Installation is optional for provisioned and managed VMs
+- The Linux agent can be shrunk and should be less then 0.2% peak
+- Provides a command bus such that HPE Morpheus Enterprise doesn’t need credentials to access a box
+- Can still manage workflows if credentials are changed
+- SSH agent can be disabled and still get access to the box
+- Agent can be installed over Cloud-init, Windows unattend.xml, VMware Tools, SSH, WinRM, Cloudbase-Init, or manually
+- Makes a single, persistent connection over HTTPS websocket and runs as a service
+- Buffers and compresses logs, then sends them in chunks to minimize packets
+- Supports syslog forwarding
+- Accepts commands, executes commands, writes files, and manipulates firewalls
+- Significantly enhances Guidance recommendations through enhanced statistics
+
+NOTE
+
+The HPE Morpheus Enterprise Agent is required for managed Docker, Kubernetes, SCVMM, Hyper-V, KVM, and ESXi Hosts (for ESXi-only Cloud, not vCenter Clouds).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json b/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
new file mode 100644
index 0000000..47ae154
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+  "title": "Maintenance Mode",
+  "ordinal": 186,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md b/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
new file mode 100644
index 0000000..dc485ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
@@ -0,0 +1,5 @@
+# Maintenance Mode
+
+HVM cluster hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. HPE Morpheus Enterprise UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
+
+![../../_images/enterMaintenance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-18F5E0CD-4DD0-4720-8DA0-E81B1048013B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..55402fb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 332,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..75295a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.json b/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
new file mode 100644
index 0000000..fe6fc6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+  "title": "Node Types",
+  "ordinal": 130,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html",
+  "topic_cluster": {
+    "clustering_title": "Node Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.md b/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
new file mode 100644
index 0000000..702a281
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
@@ -0,0 +1,96 @@
+# Node Types
+
+Node Types are the link between Images and Layouts.
+
+## Node Type Configuration Options
+
+The following fields are for all Technology types:
+
+Name
+:   Name of the Node Type in HPE Morpheus Enterprise
+
+Short Name
+:   The short name is a lowercase name with no spaces used for display in your container list
+
+Version
+:   Version for the Node Type. Examples: 7.5, 2012 R2, latest
+
+Technology
+:   Select associated Technology. This will filter the available configuration options, images and which Layouts the Node Type can be added to
+
+Environment Variables
+:   Add pre-set environment variables to the Node Type
+
+Category
+:   Node Types of differing categories within the same Layout can have differing sizing
+
+## Technology-Specific Options
+
+The Options fields will change depending on the Technology option selected. For VM provisioning technology options, select an image from the VM Image dropdown. This list is populated from the HPE Morpheus Enterprise Virtual Images section and will include images uploaded into HPE Morpheus Enterprise as well as synced images from added clouds.
+
+NOTE
+
+Amazon and Azure Marketplace Images can be added in the Virtual Images section for use as Node Types in custom library items.
+
+### Docker Options
+
+For Docker, type in the name and version of the Docker Image, then select the integrated registry.
+
+Service Ports
+:   To open ports on the node, enter the name and port to expose. The Load Balancer HTTP, HTTPS, or TCP setting is required when attaching to Load Balancers.
+
+    Defining an Exposed port will also create a hyperlink(s) on the container location (IP) in the VM or Container section of the associated Instance detail page.
+
+Scripts
+:   Search for and select one or multiple scripts to be executed when the Node Type is provisioned
+
+File Templates
+:   Search for and select one or multiple File Templates to be written when the Node Type is provisioned
+
+Example port configuration:
+
+![../../_images/node_ports.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EAA33A7C-4570-4FBD-857C-F9C400D588C2-high.png)
+
+### VMware Options
+
+HPE Morpheus Enterprise supports VMware-specific configurations related to Node Types targeted for VMware vCenter Clouds. Setting the TECHNOLOGY field on the Node Type to “VMware” reveals these fields.
+
+### vApp Properties
+
+Some VMware images may expect the user to provide values for vApp properties related to server configuration. HPE Morpheus Enterprise allows the user to set values for vApp properties on the Node Type, which can be static values or even HPE Morpheus Enterprise variables such as if we wanted to provide the next available IP address from a HPE Morpheus Enterprise IP pool or source a password from HPE Morpheus Enterprise Cypher. Consider the following example workflow for examining an OVA image, uploading it to HPE Morpheus Enterprise as a Virtual Image, and setting vApp properties on the Node Type.
+
+If you have an OVA that doesn’t have the properties laid out in a visible format, you can unzip it and inspect the OVF file to help set the vApp properties in HPE Morpheus Enterprise. For example, take a look at the screenshot below from an OVF file associated with an F5 image. There are four vApp properties I wish to set related to network and user configuration. The `userConfigurable` property should be toggled to `true` for any that may be set to `false`. The key is identified by the `key` property and, if desired, default values can be set via the `value` property. Save any changes to the OVF file.
+
+![../../_images/vappOvf.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-97074F85-A232-4095-9625-CEAF93C468A2-high.png)
+
+With changes saved, the image can be uploaded to HPE Morpheus Enterprise as a Virtual Image from which we can create and configure a Node Type. Below you can see the Virtual Image uploaded and revealed on the Virtual Images list page.
+
+![../../_images/vappVirtualImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-583CAD5E-6A57-49DB-AEAB-704F815F73D7-high.png)
+
+Next, create a new Node Type. After setting the TECHNOLOGY value to “VMware” the fields related to vApp Property configuration will be revealed. Select the uploaded Virtual Image as the “VM IMAGE” and set the key/value pairs in VAPP PROPERTIES. In this case, I’ve dynamically loaded the values using HPE Morpheus Enterprise variables.
+
+![../../_images/vappNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-871C2818-8DD3-478D-ADC4-613602524004-high.png)
+
+The rest of the process is the same as building out any other HPE Morpheus Enterprise library item. House the Node Type within a Layout and the Layout within an Instance Type. It should then be provisionable as any other Instance Type.
+
+### Extra Options
+
+When VMware Technology Type is selected, EXTRA OPTIONS will be available in the VMware VM Options section. These allow defining Advance vmx-file parameters during provisioning.
+
+Some Example include:
+
+```
+```
+tools.setinfo.sizeLimit : 1048576  
+vmci0.unrestricted : FALSE  
+isolation.tools.diskWiper.disable : TRUE
+```
+```
+
+NOTE
+
+Not all parameters can be set using extra config parameters. A sample reference list can be found at <http://www.sanbarrow.com/vmx/vmx-advanced.html#vmx>
+
+IMPORTANT
+
+Use caution when setting Extra Options. Malformed config files can break provisioning. Troubleshooting issues related to Extra Options defined are beyond the scope of HPE Morpheus Enterprise product support.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json b/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
new file mode 100644
index 0000000..4b0746b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+  "title": "Integrations",
+  "ordinal": 531,
+  "parent_title": "See Also",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md b/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
new file mode 100644
index 0000000..c2805be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
@@ -0,0 +1,9 @@
+# Integrations
+
+The Integrations section in Library > Integrationsis for adding and managing Automation Integrations. Existing Automation Integrations from Administration > Integrations are also populated and accessible from Library > Integrationsand vice-versa.
+
+`Provisioning: Automation Integrations` and `Admin: Integrations` are separate Role permissions, so Automations Integration access can be separated from the Administration Integrations section.
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json b/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
new file mode 100644
index 0000000..b229e7e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+  "title": "Azure (Public)",
+  "ordinal": 390,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html",
+  "topic_cluster": {
+    "clustering_title": "Azure (Public)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md b/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
new file mode 100644
index 0000000..55bad04
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
@@ -0,0 +1,411 @@
+# Azure (Public)
+
+## Overview
+
+Morpheus offers a complete Integration with Microsoft Azure including the following:
+
+- Virtual Machine Sync, Create, Delete, Manage, RBAC, Tenant Permissions, Policies
+- Resource Group Sync, Create, Delete, RBAC, Tenant Permissions
+- Network Sync, Create, Delete, RBAC, Tenant Permissions
+- Subnet Sync, Create, Delete, RBAC, Tenant Permissions
+- Security Group Sync, Create, Delete, Tenant Permissions
+- Security Group Rule Sync, Create, Delete, Tenant Permissions
+- ARM Blueprints, Spec Templates, Deployment Logs Sync, Git/GitHub Integration
+- MSSQL Service Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- AKS Sync, Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Backup Create, Delete, Manage, RBAC, Policies
+- Storage Sync, Create, Delete, Manage, Browse, RBAC, Tenant Permissions, Policies
+- Marketplace Sync
+- Private Image Sync & Upload
+- Azure Marketplace Custom Library Item Support
+- Remote Console (SSH & RDP)
+- Lifecycle Management
+- Availability Set Support
+- Scale Set Sync, Create, Assign, Manage, Delete
+- Azure Load Balancer Create, Assign, Manage, Delete, RBAC, Tenant Permissions
+- Docker (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Kubernetes (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Service Plan Sync, Tenant Permissions, RBAC
+- Pricing Sync RBAC, Tenant Permissions, Markup
+- Costing Sync, Reporting, Invoicing
+- Reservations Sync, Guidance Recommendations
+- Azure Stack Support
+- Tag Bi-Directional Sync, Creation, Deletion Policy Enforcement
+- Cost Estimator
+- Azure US Gov Support
+- Azure China Support
+- Azure Germany Support
+- CSP Account Support
+
+## Requirements
+
+Morpheus Azure Integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET (Web App Key)
+
+The HPE Morpheus Enterprise appliance requires outbound HTTPS (443) access to the Azure endpoints. Depending on the type of cloud you choose when adding Azure, ensure the proper endpoints are allowed:
+
+**Global Azure Cloud**
+:   - <https://management.core.windows.net> (ServiceManagementUrl)
+    - <https://management.azure.com> (ResourceManagerUrl)
+    - <https://login.microsoftonline.com> (ActiveDirectoryAuthority)
+
+**US Gov Cloud**
+:   - <https://management.core.usgovcloudapi.net> (ServiceManagementUrl)
+    - <https://management.usgovcloudapi.net> (ResourceManagerUrl)
+    - <https://login.microsoftonline.us> (ActiveDirectoryAuthority)
+
+**Germany Cloud**
+:   - <https://management.core.cloudapi.de> (ServiceManagementUrl)
+    - <https://management.microsoftazure.de> (ResourceManagerUrl)
+    - <https://login.microsoftonline.de> (ActiveDirectoryAuthority)
+
+**China Cloud**
+:   - <https://management.core.chinacloudapi.cn> (ServiceManagementUrl)
+    - <https://management.chinacloudapi.cn> (ResourceManagerUrl)
+    - <https://login.chinacloudapi.cn> (ActiveDirectoryAuthority)
+
+## Credentials & Permissions
+
+Morpheus authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with Morpheus has Owner or Contributor permissions on the specified Subscription before contacting support.
+
+### Create an App Registration
+
+#### About this task
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one.
+
+TIP
+
+If you can’t find sections of the Azure portal discussed in this integration guide, such as App Registrations or Subscriptions, you may be able to find them under the “Favorites” section within the main hamburger menu, at the “All Resources” page from within the main hamburger menu, or by using the global search bar.
+
+#### Procedure
+
+1. Log into the Azure web console
+2. Select “App Registrations”, you may have to go to the “All Services” page to find it 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E7EF3195-082B-46D5-BE32-590BA7644633-high.png)
+3. Click “+ New registration” 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B7FEBDD8-32CB-479A-B49C-82A8F817992B-high.png)
+4. Next, give app a name, specify which accounts may access this API, specify Web for the Redirect URI type and enter any url for the Sign-on URL:
+5. Click Register and your new App Registration will be created. 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F16A233F-1112-4341-A19D-97F5B91E2A10-high.png)
+
+#### Results
+
+Now that we have (or already had) our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when Adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when Adding your Azure cloud in HPE Morpheus Enterprise 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-663FA392-839D-43E5-8C32-C50055985BCD-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select Certificates & secrets in the Manage Section
+2. Select `+ New client secret` 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B699A18D-B220-488B-989E-B67C83E2AA67-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select a duration
+6. Select Add 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-20277A74-BFD7-42BA-87B7-B249CAC4E4DD-high.png)
+7. Copy the newly generated Client Secret Value. It is important to copy the Client Secret Value now as it will not be displayed/available 
+
+   IMPORTANT
+
+   Copy the key value before continuing as it will not be displayed/available again.
+8. Store/Paste for use as the Client Secret when Adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have 3 of the 4 credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the main Subscriptions section. One way is to search for “Subscriptions” and select Subscriptions in the search results
+2. In the main “Subscriptions” section, copy the Subscription ID 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4B40A8B2-3C59-4AE4-8980-1DA3A3786918-high.png)
+3. Store/Paste for use as the Subscription ID when Adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration created/used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory/sync, create and/or remove resources.
+
+#### Procedure
+
+1. In the main Subscriptions section, click on the name of the Subscription
+2. With the Subscription detail open, select “Access Control (IAM)”
+3. Click “+ ADD” and then click “Add role assignment” from the pop-out menu 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8812BC0F-33DB-4F3D-8399-7EC297A6DC2E-high.png)
+4. Click on the tab for “Privileged administrator roles”
+5. Select Owner or Contributor and click “Next”
+6. Add Members to the Role Assignment by clicking “+ Select members”
+7. Select the App Registration from the search results and click Select 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-24AA7305-E9B5-428A-8FAE-ABC8F17CAE2E-high.png)
+8. Click “Review + Assign”
+
+## Add an Azure Cloud Integration
+
+### About this task
+
+To add a new Azure Cloud integration into HPE Morpheus Enterprise using the credentials created/collected from the previous section, perform the following:
+
+### Procedure
+
+1. In HPE Morpheus Enterprise, navigate to Infrastructure > Clouds and select + ADD 
+
+   ![../../../_images/Clouds_Morpheus_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DC3EC6CE-40F3-4AFA-9B6E-5CCAFE1DC9DE-high.png)
+2. Select “AZURE (PUBLIC)” from the Cloud Types list and click NEXT 
+
+   ![../../../_images/Clouds_Morpheus1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4F7C2657-7339-46B0-82DB-A517DB5B0D73-high.png)
+3. Populate the Following 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   CLOUD TYPE
+   :   - Global (Azure Cloud)
+       - US Gov (Azure US Government)
+       - German (Azure German Cloud)
+       - China (Azure China Cloud)
+
+   SUBSCRIPTION ID
+   :   The target Azure Subscription ID obtained from the previous section
+
+   TENANT ID
+   :   The Directory (tenant) ID obtained from the previous section
+
+   CREDENTIALS
+   :   If available, select a pre-stored Client ID and Client Secret set. Alternatively, select “Local Credentials” to enter the Client ID and Client Secret without storing them for later access. “client id and secret” under the “New Credentials” heading can also be selected so your Client ID and Client Secret will stored for later use in either the HPE Morpheus Enterprise credential store or in an integrated third party secret store
+
+   CLIENT ID
+   :   The Application (client) ID obtained from the previous section
+
+   CLIENT SECRET
+   :   The Application (client) Secret obtained from the previous section
+
+   LOCATION
+   :   Once valid credentials are populate above and HPE Morpheus Enterprise is able to successfully authenticate with Azure, the available locations/regions will populate.
+
+   REGION
+   :   Scope the Cloud to either “All” regions or a selected Azure region
+
+   RESOURCE GROUP
+   :   - Select “All” to scope the Cloud to all available Resource Groups in the specified location/region.
+       - Select a single Resource Group to limit HPE Morpheus Enterprise resource creation, selection and discovery to just this Resource Group.
+
+   INVENTORY EXISTING INSTANCES
+   :   Check to enable discovery/inventory of existing VM’s in the scoped Region and Resource Group(s)
+
+   ACCOUNT TYPE
+   :   Standard, EA or CSP
+
+       NOTE
+
+       For CSP Accounts, also enter CSP TENANT ID, CSP CLIENT ID and CSP CLIENT SECRET in the Advanced Options section. In order to enable cost sync for CSP accounts, the “CSP CUSTOMER” checkbox must be marked and “COSTING” should be set to “Costing” rather than “Costing and Reservations”.
+
+       For the CSP Client Secret, enter the Web App Key rather than the Native App Key. This should be accessed from the Microsoft Partner Center rather than the Azure web console. If this is not, Plans may sync but Price Sets and Prices would not.
+
+       ![../../../_images/addAzureCloudMorpheusS1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B917D3E3-342A-4DB9-9377-A0F20BB69D1F-high.png)
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+   AZURE COSTING MODE
+   :   Standard, CSP, or Azure Plan
+
+       Example configurations but choose what is applicable to the tenant:
+
+       Table 1. Example Azure Costing Configurations
+
+            | Account Type | Azure Costing Mode | Notes |
+       | --- | --- | --- |
+       | Standard (Pay as you go) | Standard |  |
+       | EA (Enterprise Agreement) | Standard |  |
+       | CSP (Cloud Solution Provider) | CSP | CSP Tenant, ID, Client ID, and Client Secret required |
+       | CSP (Cloud Solution Provider) | Azure Plan (Microsoft Customer Agreement) | CSP Tenant, ID, Client ID, and Client Secret required on the primary cloud |
+4. Once done configuring the Cloud, select NEXT. NOTE all specified values except the Subscription ID can be changes after the Cloud is created.
+5. Next select an existing Group to add the Azure Cloud to, or create a new Group, then select NEXT 
+
+   ![../../../_images/Clouds_MorpheusAddGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6C5E021D-A3B6-4AE2-9A7E-A7E1FD6A001C-high.png)
+6. Review the configuration and then select COMPLETE 
+
+   ![../../../_images/Clouds_MorpheusComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-57620E9D-45F0-4D5E-AEAB-F5496EDF994F-high.png)
+
+### Results
+
+Your new Azure Cloud integration will be created and begin to sync.
+
+NOTE
+
+The initial sync of an Azure Cloud can take some time due to Marketplace data sync.
+
+![../../../_images/Clouds_MorpheusNewCloudAdded.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E14BF630-7826-4A29-A728-7EE6BCEA365F-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json b/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
new file mode 100644
index 0000000..ff3446f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+  "title": "HVM Clusters",
+  "ordinal": 174,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md b/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
new file mode 100644
index 0000000..4211c8f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
@@ -0,0 +1,14 @@
+# HVM Clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, HPE Morpheus Enterprise can create a cluster of hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by HPE Morpheus Enterprise Tenant capabilities, a highly-granular RBAC and policy engine, and Instance Type library with automation workflows.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.json b/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
new file mode 100644
index 0000000..5fbd0f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+  "title": "GKE Clusters",
+  "ordinal": 201,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html",
+  "topic_cluster": {
+    "clustering_title": "GKE Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.md b/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
new file mode 100644
index 0000000..f7ba949
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
@@ -0,0 +1,69 @@
+# GKE Clusters
+
+Provisions a new Google Kubernetes Engine (GKE) Cluster in target Google Cloud.
+
+NOTE
+
+Ensure proper permissions exist for the Google Clouds service account to create, inventory and manage GKE clusters.
+
+## Create an GKE Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `GKE Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the GKE Cluster
+
+   RESOURCE NAME
+   :   Name for GKE Cluster resources/hosts
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+
+   LAYOUT
+   :   Select cluster layout for GKE Cluster
+
+   RESOURCE POOL
+   :   Specify an available Resource Pool from the selected Cloud
+
+   GOOGLE ZONE
+   :   Specify Region for the cluster
+
+   VOLUMES
+   :   Cluster hosts volume size and type
+
+   NETWORKS
+   :   Select GCP subnet(s) and config
+
+   WORKER PLAN
+   :   Service Plan for GKE worker nodes
+
+   RELEASE CHANNEL
+   :   Regular, Rapid, Stable or Static
+
+   CONTROL PLANE VERSION
+   :   Select from available synced GKE k8’s versions
+
+   NUMBER OF WORKERS
+   :   Number of worker nodes to be provisioned
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json b/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
new file mode 100644
index 0000000..58826d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+  "title": "Costing: Group Costing",
+  "ordinal": 59,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Group Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md b/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
new file mode 100644
index 0000000..dc651b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
@@ -0,0 +1,32 @@
+# Costing: Group Costing
+
+![../_images/2groupcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BC2102C2-6D1A-4EC2-8F51-173EAE0CE091-high.png)
+
+The Group Costing dashboard aggregates cost totals for all Groups that meet filters set on the dashboard. This allows administrators to sort Groups by their total costs and anticipate monthly total costs by Group.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- Group (all matched by search)
+- Group (selected from dropdown)
+- Cloud
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Groups that meet set filters:
+
+- **GROUPS:** The total number of Groups that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Groups meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Groups meeting dashboard filters
+
+## Group List
+
+Each Group that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Group:
+
+- **NAME:** The name given to the Group in HPE Morpheus Enterprise at the time of creation
+- **LOCATION:** The Group location (if available)
+- **DATACENTER:** The Group datacenter (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Group listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Group listed
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.json b/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
new file mode 100644
index 0000000..a6fa912
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+  "title": "Provisioning into OpenShift",
+  "ordinal": 209,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning into OpenShift",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.md b/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
new file mode 100644
index 0000000..d42cbf0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
@@ -0,0 +1,31 @@
+# Provisioning into OpenShift
+
+In addition to adding a new cluster type (as covered in the previous sections), the HPE Morpheus Enterprise OpenShift plugin also adds the "OpenShift" Instance Type to the provisioning wizard. Through this, new virtualized Instances can be provisioned to the OpenShift cluster. Use the following steps to provision a new virtual machine into the cluster.
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select OPENSHIFT and click NEXT
+4. On the Group tab, select a Group and Cloud. These selections will be filtered to include only Groups which can access Clouds that contain OpenShift clusters
+5. Still on the Group tab, provide a Name for the new Instance and click NEXT
+6. On the Configure tab, set the following configurations:
+
+   - Layout: The "Openshift VM" Layout is included by default. Additional Layouts can be created within the Blueprints section (Library > Blueprints > Layouts) by selecting the "Openshift" Layout technology and associating the Layout with the "Openshift" Instance Type. See the Blueprints section of this user manual for more information on building Library items
+   - Plan: Plans of various sizes and levels of customizability can be created in Administration > Plans & Pricing. By default, a single Plan specifying 2 CPU cores and 4 GB memory is seeded when adding the plugin
+   - Resource Pool: Select the desired OpenShift cluster
+   - Volumes: Select the proper number and size volumes
+   - Networks: Networks correspond to NetworkAttachedDefinitions (NADs) in OpenShift. This list includes all NADs and names them by "<namespace>/<NAD name>" to make it easier to select a network within the intended namespace (Project). Users may select multiple NADs while provisioning but they must be from the same namespace
+
+     IMPORTANT
+
+     The first network interface chosen as part of Instance deployment will be treated as the primary interface and is expected to be reachable from the HPE Morpheus Enterprise appliance.
+   - Image: Select from all synced virtual images. Note that only custom user images are synced from OpenShift, we do not sync from the large library of default images that ship with OpenShift
+   - Project: Select the proper namespace. Bear in mind it's currently up to the user to select a valid namespace based on the network selected. If you choose an invalid namespace for the chosen network, provisioning will fail. In the future, this select list may provide automatic filtering to prevent invalid configuration but, for now, the user must make a valid selection
+7. Still on the Configure tab, other configurations common to many Instance Types can also be made. When finished, click NEXT
+8. On the Automation tab, choose to run automation Tasks or associate Workflows with the new Instance. Other common automation configurations can also be made, such as scale or backup configurations. Click NEXT
+9. On the Review tab, click COMPLETE
+
+The new OpenShift VM will soon be running based on the configurations given. Its status can be monitored from the OpenShift cluster detail page discussed in the previous section or from the Instances list page.
+
+NOTE
+
+Instance/VM console access is only supported if the VM is available on the network and reachable by HPE Morpheus Enterprise over the SSH port for Linux or the RDP port for Windows.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json b/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
new file mode 100644
index 0000000..aa5b346
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+  "title": "OneLogin",
+  "ordinal": 285,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html",
+  "topic_cluster": {
+    "clustering_title": "OneLogin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md b/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
new file mode 100644
index 0000000..1abaace
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
@@ -0,0 +1,43 @@
+# OneLogin
+
+By integrating OneLogin with HPE Morpheus Enterprise, users can access HPE Morpheus Enterprise with their existing credentials set up within the OneLogin platform. Additionally, administrators can manage user access including Role assignment and enabling or disabling users from within the OneLogin platform. As employees are onboarded, change positions, or leave the company, additional user management within the HPE Morpheus Enterprise platform is not necessary.
+
+## Adding OneLogin Identity Source Integration
+
+To begin, log into OneLogin with an administrator account to gather some needed pieces of information. From the top menu bar, select Administration. From the admin panel, click Developers > APICredentials. Click the button labeled “New Credential”. Provide a name for the new API credentials and select “Manage Users” as the permissions type. Store the credentials somewhere they can be retrieved in the next step.
+
+![../../_images/oneLoginKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3244CCDD-7F2B-4DF3-B4E6-4BA4B0686C60-high.png)
+
+Back in HPE Morpheus Enterprise, navigate to the Tenant which will integrate with OneLogin. Identity providers are integrated on a per-Tenant basis in HPE Morpheus Enterprise. From the selected Tenant, click IDENTITY SOURCES. The list of currently-integrated identity providers is here. Click + ADD IDENTITY SOURCE to start a new integration for OneLogin. Fill in the fields below:
+
+- **TYPE:** OneLogin
+- **NAME:** A name for the identity source integration in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the identity source
+- **ONELOGIN SUBDOMAIN:** The subdomain from your OneLogin portal URL. For example, “morpheus-dev” if your portal is accessed at morpheus-dev.onelogin.com. Incorrect subdomains will cause login attempts to HPE Morpheus Enterprise to fail
+- **ONELOGIN REGION:** Specify US or EU region
+- **API CLIENT SECRET:** OneLogin API client secret which was gathered earlier in this walkthrough
+- **API CLIENT ID:** OneLogin API client ID which was gathered earlier in this walkthrough
+- **REQUIRED ROLE:** Enter a role which OneLogin users logging into HPE Morpheus Enterprise must have to gain access to HPE Morpheus Enterprise
+- **DEFAULT ROLE:** The default HPE Morpheus Enterprise Role applied to users created from the OneLogin integration if no other role mapping is specified in other Role Mappings fields
+- **ROLE MAPPINGS:** All existing HPE Morpheus Enterprise Roles will be listed with fields to enter OneLogin Roles to create a mapping. Users with OneLogin roles matching the role mappings will be assigned the appropriate Role(s) in HPE Morpheus Enterprise when signing in
+- **ENABLE ROLE MAPPING PERMISSION:** When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the core integration fields (such as the API keys)
+- **MANUAL ROLE ASSIGNMENT:** When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+Select SAVE CHANGES and the OneLogin Integration will be added.
+
+Users can now login to HPE Morpheus Enterprise with OneLogin credentials. The first login will create a user in HPE Morpheus Enterprise matching the username, email and password from OneLogin. If a REQUIRED ROLE is specified in the Identity Source settings, only users with that Role in OneLogin will be able to login to HPE Morpheus Enterprise.
+
+IMPORTANT
+
+OneLogin users will not authenticate in HPE Morpheus Enterprise if there is an existing HPE Morpheus Enterprise User with matching username or email address.
+
+You can now test the integration by logging in with user credentials which have been configured in OneLogin. On the first login, a new user will be created with the same username, email address, and password as contained in OneLogin. On subsequent logins, HPE Morpheus Enterprise will sync with OneLogin to make sure the user hasn’t been disabled or if its Role(s) have changed in OneLogin which would affect its corresponding Roles in HPE Morpheus Enterprise.
+
+The HPE Morpheus Enterprise identity source integration is interacting with the OneLogin APIs in the list below. This reference may be needed to ensure HPE Morpheus Enterprise is integrating using an API key with sufficient privileges. In a situation where troubleshooting is needed, first confirm these APIs can be accessed using the provided key.
+
+- `/auth/oauth2/token` - Generate Token
+- `/api/1/users/$user_id/roles` - Get Roles
+- `/api/1/login/auth` - Create Session
+- `/api/1/users/$user_id` - Get User
+- `/api/1/roles/$role_id` - Get Role
+- `/api/1/roles?name=$role_name` - Find Role
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json b/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
new file mode 100644
index 0000000..d388baa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+  "title": "Capacity: Capacity Planning",
+  "ordinal": 66,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity: Capacity Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md b/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
new file mode 100644
index 0000000..f39b69b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
@@ -0,0 +1,9 @@
+# Capacity: Capacity Planning
+
+![../_images/capacityPlanning.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-54937FF3-952A-40DE-8C06-8E193416776A-high.png)
+
+The capacity planning dashboard shows both realtime use and predicted future use in key metrics of memory, storage and CPU use over a pre-defined period. Choose to show this across the entire appliance (all Tenants and Clouds) or scoped to just a single Tenant or a single Cloud. This can help to plan for future hardware needs, plan for changing public Cloud spend, or identify over/under utilization of certain resources.
+
+## Filters
+
+Leave unfiltered to show data across all Tenants and Clouds. Optionally choose to filter down to all Clouds in one specific Tenant or a single Cloud. The trend line predicts future use of resources based on recent past utilization.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json b/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
new file mode 100644
index 0000000..89ff4f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+  "title": "Agent Install Methods",
+  "ordinal": 47,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Methods",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md b/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
new file mode 100644
index 0000000..0c4dcc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
@@ -0,0 +1,100 @@
+# Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+## For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+## SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+## WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+## VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+## Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+## Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+## Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+## Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json b/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
new file mode 100644
index 0000000..dba10b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+  "title": "Key Features",
+  "ordinal": 398,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html",
+  "topic_cluster": {
+    "clustering_title": "Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md b/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
new file mode 100644
index 0000000..6bd9df8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
@@ -0,0 +1,106 @@
+# Key Features
+
+HPE BMaaS for Morpheus Enterprise provides centralized discovery, provisioning, lifecycle management, and monitoring for HPE ProLiant bare-metal infrastructure. The key features of HPE BMaaS are as follows:
+
+- Automated Server Discovery and Inventory
+
+  - Server Import: Imports HPE ProLiant servers into Morpheus using iLO IP addresses and credentials.
+  - Hardware Inventory Discovery: Automatically collects detailed hardware data, including:
+
+    - Server model and generation
+    - CPU, memory, and storage configurations
+    - Network interfaces and adapters
+    - Firmware and driver versions
+  - Service Plan Mapping: Maps discovered hardware to Morpheus Service Plans to align metering, consumption tracking, and billing.
+  - Metadata Management: Maintains updated server metadata to ensure operational visibility and support capacity planning.
+- Resource Pool and Bare Metal Cloud Management
+
+  - Create a Bare Metal Cloud per tenant to represent dedicated HPE ProLiant infrastructure.
+  - Organize servers within the cloud into Resource Pools for multi-site deployments and infrastructure segmentation.
+  - Allocate servers to specific groups, environments, or use cases.
+  - Apply policies, access control, and governance at the cloud or resource pool level.
+- Bare Metal Instance Provisioning
+
+  - Provision bare metal instances directly from available HPE ProLiant servers.
+  - Support for:
+
+    - Local disk RAID configuration during deployment
+    - Automated OS installation
+    - Post-install configuration and customization
+  - Associate instances with user-defined groups, clouds, and resource pools.
+- Operating System Deployment
+
+  - Deploy Windows Server and Linux operating systems using ISO images stored in the Morpheus Virtual Image Library.
+  - Supported unattended installation mechanisms:
+
+    - Windows Setup (AutoUnattend)
+    - RHEL / Oracle Linux Kickstart
+    - Ubuntu Autoinstall (cloud-init)
+  - Consistent and repeatable OS deployments across environments.
+- Image Management
+
+  - Centralized catalog of bootable OS images.
+  - Support for multiple image storage backends:
+
+    - Storage > File Shares
+
+      - CIFS (Samba Windows File Sharing): Windows-compatible network file sharing
+      - Local Storage: Direct storage on the server
+      - Network File System version 3 (NFSv3): Linux network file sharing
+    - Storage > Buckets
+
+      - S3-compatible object storage (for example, using MinIO): Object storage through S3 API
+    - Images can be reused across multiple provisioning workflows.
+- Greenfield (New Server) Provisioning
+
+  - Provision brand-new, unconfigured HPE ProLiant servers into Morpheus-managed bare metal instances.
+  - Perform full end-to-end lifecycle automation, including:
+
+    - Server discovery
+    - Power control and boot orchestration
+    - RAID and storage configuration
+    - Network configuration
+    - Operating system deployment
+  - Enable zero-touch deployment from factory-fresh hardware to production-ready servers.
+  - Ensure consistent, repeatable provisioning aligned with organizational standards.
+- Brownfield (Pre-Provisioned Server) Import
+
+  - Import existing physical servers into Morpheus as Pre-Provisioned resources
+  - Convert imported servers into fully managed Morpheus instances.
+  - Add additional imported servers as nodes to an existing instance.
+- Firmware and Driver Lifecycle Management
+
+  - Execute firmware and driver inventory and updates using HPE Service Pack for ProLiant (SPP).
+  - Run updates through Morpheus Jobs and Workflows.
+  - Target firmware only, drivers only, or both.
+  - Support for:
+
+    - Dry Run (inventory only)
+    - Deploy (apply updates)
+- Monitoring and Metering
+
+  - Monitor real-time hardware health and operational status through iLO integration.
+  - Surface system alerts and hardware events inside HPE Morpheus Enterprise.
+  - Meter resource consumption for reporting and charge-back or show-back.
+- Networking Integration
+
+  - Automated VLAN and switch port configuration in managed mode.
+  - Flexible network attachment to physical or bonded interfaces.
+  - Support for:
+
+    - Unmanaged networks
+    - Managed networks using HPE Aruba CX switches
+- Storage Integration
+
+  - Use local server storage for OS installation.
+  - Integrate with HPE Alletra MP storage arrays for remote SAN volumes.
+  - Create, attach, detach, resize, and delete volumes from HPE Morpheus Enterprise.
+- Integration with Morpheus Core Platform Capabilities
+
+  Bare metal instances benefit from native Morpheus platform features, including:
+  - SSH and RDP access
+  - Morpheus agent (morphd) deployment
+  - Workflow automation and lifecycle scripts
+  - Policy-based governance
+  - Role-based access control
+  - Multi-group and multi-cloud support
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json b/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
new file mode 100644
index 0000000..dc85d02
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+  "title": "Single Node Installation",
+  "ordinal": 16,
+  "parent_title": "Installation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md b/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
new file mode 100644
index 0000000..8d94544
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
@@ -0,0 +1,439 @@
+# Single Node Installation
+
+## Single Node Install Overview
+
+In a Single Host/All-in-one configuration, all components required for Morpheus are automatically installed and configured during the Morpheus `reconfigure` command.
+
+![../../../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+Appliance Host
+:   - Application
+      :   - Morpheus App
+    - Web Server/Proxy
+      :   - NGINX
+    - Database
+      :   - MySQL
+    - Messaging
+      :   - RabbitMQ
+    - Search
+      :   - Opensearch
+    - Console
+      :   - Guacamole
+    - Monitoring
+      :   - Check Server
+
+### Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - MySQL: `/var/log/morpheus/mysql`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## Single Node Install on CentOS
+
+NOTE
+
+Appliance Package links are available at <https://app.morpheushub.com> in the downloads section.
+
+### Quick Install
+
+#### Procedure
+
+Install the Appliance package and run `sudo morpheus-ctl reconfigure`.
+
+#### Results
+
+That is it. After the reconfigure completes, HPE Morpheus Enterprise will start and be available at `https://your_machine_name` in a minute or few.
+
+### Step-by-step Install Instructions
+
+#### Procedure
+
+1. Ensure the HPE Morpheus Enterprise Appliance host meets the minimum [requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)
+2. Download the target version `.rpm` package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-appliance-$version.rpm
+   ```
+   ```
+3. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-appliance-$version.rpm
+   ```
+   ```
+4. Next install the rpm package 
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-appliance-x.x.x-1.x86_64.rpm
+   ```
+   ```
+5. By default the appliance\_url uses the machines hostname, ie `https://your_machine_name`. The default url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. Additional Appliance configuration options are available below. 
+
+   Appliance Configuration Options
+
+   Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+   NOTE
+
+   Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps if simply appending a port to your `appliance_url` value doesn’t work.
+
+   ```
+   ```
+   app['encryption_key_suffix'] = '$suffix'  
+     # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+   appliance_url 'https://morpheus.appliance-url.com'  
+     # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+     # The appliance_url cannot exceed 64 characters  
+     # The appliance_url must not contain a trailing `/`.  
+   bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+   bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+   opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+   opensearch['auth_user'] = 'morpheus-es-user'  
+   opensearch['enable'] = true  
+   opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+   opensearch['host'] = "127.0.0.1"  
+   opensearch['port'] = "9200"  
+   opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+   opensearch['use_tls'] = false  
+   ↓ The following opensearch settings are only valid for Internal/Embedded opensearch services  
+   opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+   opensearch['memory_alloc_arena_max'] = 2  
+   opensearch['memory_map_max'] = 65536  
+   opensearch['memory_map_threshold'] = 131072  
+   opensearch['memory_top_pad'] = 131072  
+   opensearch['memory_trim_threshold'] = 131072  
+   opensearch['open_files'] = 204800  
+   opensearch['secure_mode'] = false  
+   opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   opensearch['xmx'] = 0.25  
+   guacd['guacamole_enabled'] = false  
+   guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+   logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+   logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+   logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+   mysql['enable'] = true  
+   mysql['host'] = {'127.0.0.1' => 3306}  
+   mysql['use_tls'] = false  
+   mysql['morpheus_db_user'] = 'morpheus-db-user'  
+   mysql['morpheus_password'] = 'morpheus-db-password'  
+   mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+   mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+   ↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+   mysql['tmp_dir'] = '/tmp/mysql'  
+   mysql['log_dir'] = '/var/log/morpheus/mysql'  
+   mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+   mysql['max_connections'] = 151  
+   mysql['max_allowed_packet'] = 67108864  
+   mysql['mysql_connect_timeout'] = 60000  
+   mysql['mysql_max_reconnects'] = 2  
+   mysql['mysql_queries_before_retry_source'] = 0  
+   mysql['mysql_seconds_before_retry_source'] = 300  
+   nginx['cache_max_size'] = '5000m'  
+   nginx['enable'] = true  
+   nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+   nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+   nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+   nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+   nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+   nginx['loading_pages']['max_loops'] = 60 # seconds  
+   nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+   nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+   nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+   nginx['log_format_name'] = 'custom'  
+   nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+   nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+   nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+   nginx['ssl_company_name'] = "Morpheus, LLC"  
+   nginx['ssl_country_name'] = "US"  
+   nginx['ssl_email_address'] = "personal@email.com"  
+   nginx['ssl_locality_name'] = "San Mateo"  
+   nginx['ssl_organizational_unit_name'] = "DevOps"  
+   nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+   nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+   nginx['ssl_session_timeout'] = "5m"  
+   nginx['ssl_state_name'] = "CA"  
+   nginx['worker_connections'] = 10240  
+   nginx['workers'] = integer calculated from number of cpus  
+   nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   rabbitmq['enable'] = true  
+   rabbitmq['host'] = '127.0.0.1'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+   rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+   rabbitmq['vhost'] = 'morpheus'  
+   ↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+   rabbitmq['heartbeat'] = nil  
+   rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+   rabbitmq['nodename'] = 'rabbit@localhost'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['use_tls'] = false  
+   repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+   ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+   ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+   ui['kerberos_config'] = nil  
+   ui['kerberos_login_config'] = nil  
+   ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+   ui['max_memory_mb'] = nil  
+   ui['memory_alloc_arena_max'] = 2  
+   ui['memory_map_max'] = 65536  
+   ui['memory_map_threshold'] = 131072  
+   ui['memory_top_pad'] = 131072  
+   ui['memory_trim_threshold'] = 131072  
+   ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+   ui['support_links'] = {  
+     'name' => ['url', 'i18n'],  
+     'name1' => ['url1', i18n1'],  
+     'name2' => ['url2', i18n2']  
+   } #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+   ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+   ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   ui['xmx'] = 0.25
+   ```
+   ```
+6. After all configuration options have been set, run: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus.rb` and running `sudo morpheus-ctl reconfigure` again. Appliance and other services may need to be restarted depending on configuration changes.
+7. Once the installation is complete the morpheus-ui service will automatically start up and be available shortly. To monitor the UI startup process, run `morpheus-ctl tail morpheus-ui` and look for the ascii logo accompanied by the install version and start time: 
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2021  
+   timestamp: ****************************************
+   ```
+   ```
+
+#### Results
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on Debian/Ubuntu
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on Ubuntu or Debian a few preparatory items should be addressed first.
+
+### Procedure
+
+First make sure the apt repository is up to date by running `sudo apt-get update`. It is advisable to verify the assigned hostname of the machine is self-resolvable. 
+
+IMPORTANT
+
+If the machine is unable to resolve its own hostname `nslookup hostname` some installation commands will be unable to verify service health during installation and fail.
+
+### Results
+
+1. Next simply download the relevant `.deb` package for installation. This package can be acquired from <https://app.morpheushub.com> downloads section.
+
+   TIP
+
+   Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package/morpheus-appliance_x.x.x-1_amd64.deb`
+
+1. Next we must install the package onto the machine and configure the morpheus services:
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+2. Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl stop morpheus-ui  
+   sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   The morpheus-ui can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on RHEL
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on RHEL/RedHat a few prerequisite items are required.
+
+### Procedure
+
+1. Configure firewalld to allow access from users on 443 (Or remove firewall if not required).
+2. Make sure the machine is self resolvable to its own hostname.
+3. For RHEL 7.x, the Optional RPMs repo needs to be added for Reconfigure to succeed. It does not need to be added For RHEL 8.x, as the Optional RPMs repo is now part of the appstream repo that is enabled by default in RHEL 8.x. 
+
+   - RHEL 7.x Amazon:`yum-config-manager --enable rhel-7-server-rhui-optional-rpms`
+   - RHEL 7.x:`yum-config-manager --enable rhel-7-server-optional-rpms`
+
+### Results
+
+NOTE
+
+For Amazon users a Redhat subscription is not required if the appropriate yum REGION repository is added instead as demonstrated above.
+
+The RedHat Enterprise Linux server needs to be registered and activated with Redhat subscription. The server optional rpms repo needs to be enabled as well.
+
+To check if the server has been activated please run the subscription-manager version. Subscription manager will return the version plus the python dependency version.
+
+If the server has not been registered and activated then the subscription manager version will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: This system is currently not registered  
+subscription management server: 0.9.51.24.-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+When a server has been registered and activated with Redhat the subscription manager will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: Red Hat Subscription Management  
+subscription management server: 0.9.51.24-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+If the subscription manager re-turns the message `This system is currently not registered` please follow the below steps to register the server.
+
+TIP
+
+To register the server you will need to have sudo permissions [Member of the Wheel group] or root access to the server. You will also need your Redhat registered email address and password.
+
+subscription-manager register
+
+```
+```
+sudo subscription-manager register  
+Username: redhat@example.com  
+Password: . subscription-manager auto --attach
+```
+```
+
+NOTE
+
+This can take a minute to complete
+
+```
+```
+sudo subscription-manager attach --auto  
+Installed Product Current Status: Product Name: Red Hat Enterprise Linux  
+Server Status: Subscribed
+```
+```
+
+To check to see if the RHEL server has the Red Hat Enterprise Linux 7 Server - Optional (RPMs) repo enabled please run the following command to return the repo status.
+
+TIP
+
+To check the server repos you will need to have sudo permissions [Member of the Wheel group] or root access to the server.
+
+```
+```
+sudo yum repolist all | grep "rhel-7-server-optional-rpms" rhel-7-server-optional-rpms/7Server/x86_64 disabled
+```
+```
+
+If the repo status was returned as disabled then you will need to enable the repo using the subscription manager like below.
+
+```
+```
+sudo subscription-manager repos --enable rhel-7-server-optional-rpms  
+Repository 'rhel-7-server-optional-rpms' is enabled for this system.
+```
+```
+
+The message `Repo 'rhel-7-server-optional-rpms' is enabled for this system.` will appear after enabling the repo. This will confirm that the repo has been enabled.
+
+Next simply download the relevant `.rpm` package for installation. This package can be acquired from morpheushub.com.
+
+TIP
+
+Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package.rpm`
+
+Next we must install the package onto the machine and configure the morpheus services:
+
+```
+```
+sudo rpm -i morpheus-appliance_x.x.x-1_amd64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+```
+```
+sudo morpheus-ctl reconfigure  
+sudo morpheus-ctl stop morpheus-ui  
+sudo morpheus-ctl start morpheus-ui
+```
+```
+
+NOTE
+
+The `morpheus-ui` can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json b/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
new file mode 100644
index 0000000..64baa12
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+  "title": "Installation",
+  "ordinal": 14,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html",
+  "topic_cluster": {
+    "clustering_title": "Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md b/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
new file mode 100644
index 0000000..304067d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
@@ -0,0 +1,8 @@
+# Installation
+
+**Subtopics**  
+
+- **[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html)**
+- **[Single Node Installation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html)**
+- **[HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)**
+- **[3 Node HA Install Example](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json b/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
new file mode 100644
index 0000000..4d34c9d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+  "title": "Rubrik",
+  "ordinal": 385,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.html",
+  "topic_cluster": {
+    "clustering_title": "Rubrik",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md b/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
new file mode 100644
index 0000000..18dd225
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
@@ -0,0 +1,80 @@
+# Rubrik
+
+The embedded HPE Morpheus Enterprise Rubrik Backup integration allows syncing, creation, and management of Rubrik Backups for vCenter Clouds. New Rubrik integrations are created in Backups > Integrations and, once created, can be set as the backup provider for existing vCenter Clouds. The latest versions of the Rubrik plugin support Rubrik CDM as well as Rubrik RSC (Rubrik Cloud Security). From a HPE Morpheus Enterprise standpoint, the primary difference between the two is in how they are authenticated. CDM-based integrations are created with API key authentication whereas RSC-based integrations are created with a client ID and client secret. Once the integration is created, the feature set as used through HPE Morpheus Enterprise is identical.
+
+## Features
+
+- Backup sync & association
+- SLA Domain sync & selection
+- Backup creation, deletion & restore
+- Restore Backups over existing VMs
+- Restore Backups as new Instances
+
+## Adding Rubrik Integration
+
+### About this task
+
+NOTE
+
+The Rubrik backup service is currently only supported on the VMware Cloud type.
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Rubrik
+4. Fill in the following: 
+
+   Rubrik CDM Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (api key), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   API Token
+   :   If manually entering credentials, this field will be visible. Enter the API key
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+
+   Rubrik RSC Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server. Each Rubrik customer will have a unique host URL (for example: `https://morpheusdata.my.rubrik.com`)
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (client id and secret), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   Client ID
+   :   If manually entering credentials, this field will be visible. Enter the client ID for authentication. If needed, add a service account to obtain credentials (for example: `https://morpheusdata.my.rubrik.com/service_accounts`). Keep in mind the service account will need to have sufficient privileges to interface with the Rubrik API to execute all HPE Morpheus Enterprise functionality listed in the “Features” section above
+
+   Client Secret
+   :   If manually entering credentials, this field will be visible. Enter the client secret for authentication
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json b/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
new file mode 100644
index 0000000..f2dc585
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+  "title": "Incidents",
+  "ordinal": 260,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html",
+  "topic_cluster": {
+    "clustering_title": "Incidents",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md b/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
new file mode 100644
index 0000000..c665596
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
@@ -0,0 +1,9 @@
+# Incidents
+
+Incident management is very important in any IT Operations environment. The ability to notify the appropriate people of an outage that requires immediate attention is critical to reducing recovery time and even preventing potential customer facing impacts. Because of this, HPE Morpheus Enterprise provides incident management features as well as external integrations out of the box.
+
+Incidents can be found in the Monitoring- > Incidents section. When a check fails, an incident is automatically raised. These can vary in severity based on the user configured check severities as well as the group hierarchy (representative of redundancy).
+
+Incidents are also grouped. If an application is impacted and multiple checks fail for that application they automatically get grouped together in one Incident that can fluctuate or escalate in severity as time progresses. These incidents can be muted so as not to affect availability and they can also be resolved manually with an option to detail resolution information.
+
+There are also integrations and API’s for integrating with existing corporate workflows when it comes to incident management.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json b/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
new file mode 100644
index 0000000..66e9fce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+  "title": "Cluster Packages",
+  "ordinal": 163,
+  "parent_title": "Templates",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md b/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
new file mode 100644
index 0000000..086c7c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
@@ -0,0 +1,21 @@
+# Cluster Packages
+
+Cluster Packages are created and can then be associated with Cluster Layouts. Cluster Packages themselves are created from Spec Templates. The Spec Templates and Cluster Layouts sections of HPE Morpheus Enterprise docs include more information on creating those constucts and show the steps to deploy sample builds.
+
+## Creating a Cluster Package
+
+Navigate to the Cluster Packages List page (Library > Templates > Cluster Packages). System Cluster Packages are listed here. These are included as part of HPE Morpheus Enterprise pre-built Cluster Layouts and cannot be edited or viewed. User-created Cluster Layouts are also listed here and these may be edited. To begin creating a new Cluster Package, click + ADD and configure the following:
+
+- **NAME:** A friendly name for the Cluster Package in HPE Morpheus Enterprise
+- **CODE:** An identifying code for the Cluster Package for use with HPE Morpheus Enterprise API and CLI
+- **DESCRIPTION:** An optional description for the Cluster Package
+- **PACKAGE VERSION:** A version designation for the Cluster Package
+- **ICON:** An identifying icon for the Cluster Package, this will appear in a list with other packages associated with a Cluster Layout
+- **DARK MODE IMAGE:** An alternate icon for the Cluster Package used when the dark theme is enabled on the HPE Morpheus Enterprise appliance
+- **TYPE:** A type selection for the package, see dropdown for options
+- **PACKAGE TYPE:** A one-word descriptor for the package such as “calico”, “prometheus”, etc.
+- **ENABLED:** When marked, this Cluster Package is available to be set on Cluster Layouts
+- **REPEAT INSTALL:** When marked, if the package install initially fails, the installation will be attempted again
+- **SPEC TEMPLATES:** Use the Typeahead field to select relevant Spec Templates to build the Cluster Package
+
+![../../_images/cluster-packages.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D5D3548C-0254-4864-A53B-0147E5742FBC-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json b/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
new file mode 100644
index 0000000..c751c67
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+  "title": "Import Pre-Provisioned Servers",
+  "ordinal": 420,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html",
+  "topic_cluster": {
+    "clustering_title": "Import Pre-Provisioned Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md b/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
new file mode 100644
index 0000000..fc0f37b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
@@ -0,0 +1,29 @@
+# Import Pre-Provisioned Servers
+
+## About this task
+
+Perform the following to add a bare metal server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute > Bare Metal.
+2. Click Add Bare Metal Server.
+3. Select the Pre-Provisioned server.
+4. Complete the remaining server details and click Save.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-961F7EE2-166C-4B30-A63A-5C6CF0D638BC-high.png)  
+
+   NOTE
+
+   **For Windows**: When importing a Pre-Provisioned Windows server, select Windows OS. This is required because some import operations are specific to Windows.
+
+   During import, the HPE BMaaS validates the association between the provided iLO IP and OS IP by executing commands on the host OS. The supplied OS credentials must have elevated privileges:
+   - **Linux OS**: The user must have sudo privileges.
+   - **Windows OS**: The user must be in the Administrators group.
+
+## Results
+
+Once the server is imported, it should be ready to be converted into a fully provisioned node.
+
+**Subtopics**  
+
+- **[Convert to Provisioned Node](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json b/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
new file mode 100644
index 0000000..dfec146
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+  "title": "logback config",
+  "ordinal": 37,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html",
+  "topic_cluster": {
+    "clustering_title": "logback config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md b/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
new file mode 100644
index 0000000..0612f8b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
@@ -0,0 +1,888 @@
+# logback config
+
+NOTE
+
+This doc is for 5.4.4+ versions that use `logback.xml`. 5.4.3 and earlier versions use `logback.groovy` with a different syntax that is not compatible with this doc. Please refer to 5.4.3 and earlier documentation for `logback.groovy` configuration details.
+
+The log output for the morpheus-ui service is configured in the logback.xml file. Log output levels can be updated when more or less log output is desired.
+
+## Setting Log Levels
+
+To change a log level, edit the logback configuration file in /opt/morpheus/conf/logback.xml and save. The changes will be reflected within the configured `scanPeriod`, 30 seconds by default.
+
+Levels:
+:   - **OFF** (no log output)
+    - **ERROR** (includes error logs)
+    - **WARN** (includes warn and error logs)
+    - **INFO** (includes info, warn and error logs)
+    - **DEBUG** (includes info, warn, error and debug logs)
+    - **TRACE** (includes info, warn, error, debug and trace logs)
+
+WARNING
+
+Use DEBUG and/or TRACE levels with caution. DEBUG & TRACE levels can produce many logs that can consume disk space quickly. Only use DEBUG and/or TRACE levels when needed and target them for specific services.
+
+## Example Logback Settings
+
+Below are sample log configuration settings. This is not a complete list. Additional log names/paths can typically be determined from the standard INFO, WARN and ERROR logs.
+
+ACI
+:   ```
+    ```
+    <logger name="com.morpheus.integration.NetworkServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciNetworkService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>
+    ```
+    ```
+
+Amazon
+:   ```
+    ```
+    <logger name="com.morpheus.compute.amazon.AmazonComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AmazonComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.costing.AmazonCostingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AmazonProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Azure
+:   ```
+    ```
+    <logger name="com.morpheus.Azure.ServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.AzureSqlServerProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.azure.AzureComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureCostingService" level="DEBUG"/>
+    ```
+    ```
+
+Chef
+:   ```
+    ```
+    <logger name="com.morpheus.automation.ChefClientService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefTaskService" level="DEBUG"/>
+    ```
+    ```
+
+DNS
+:   ```
+    ```
+    <logger name="com.morpheus.dns.MicrosoftDnsService" level="DEBUG"/>
+    ```
+    ```
+
+General
+:   ```
+    ```
+    <logger name="com.morpheus.InstanceService" level="DEBUG"/>  
+    <logger name="com.morpheus.util.ApiUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.AppService" level="DEBUG"/>  
+    <logger name="com.morpheus.MorpheusComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.RpcService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractBoxProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ProgressUpdater" level="DEBUG"/>
+    ```
+    ```
+
+Google
+:   ```
+    ```
+    <logger name="com.morpheus.compute.google.GoogleComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.GoogleComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.GoogleProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Hyper-V
+:   ```
+    ```
+    <logger name="com.morpheus.compute.hyperv.HypervComputeService" level="DEBUG" />  
+    <logger name="com.morpheus.compute.HypervComputeUtility" level="DEBUG" />
+    ```
+    ```
+
+IBM Cloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.softlayer.SoftlayerComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.SoftlayerComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Kubernetes
+:   ```
+    ```
+    <logger name="com.morpheus.app.KubernetesAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.KubernetesResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.KubernetesComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.host.KubernetesHostService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.KubernetesProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.KubernetesStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Monitoring
+:   ```
+    ```
+    <logger name="com.morpheus.monitoring.MonitorCheckService" level="DEBUG"/>
+    ```
+    ```
+
+Network
+:   ```
+    ```
+    <logger name="com.morpheusdata.infoblox.InfobloxProvider" level="DEBUG"/>  
+    <logger name="com.morpheus.network.InfobloxNetworkPoolService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.network.PluginNetworkPoolService" level="DEBUG"/>
+    ```
+    ```
+
+Nutanix
+:   ```
+    ```
+    <logger name="com.morpheus.compute.nutanix.NutanixComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.NutanixComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.NutanixProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Openstack
+:   ```
+    ```
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.OpenStackProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.OpenStackSFSStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Option Types
+:   ```
+    ```
+    <logger name="com.morpheus.OptionSourceService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeListService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeService" level="DEBUG"/>
+    ```
+    ```
+
+Remote Console
+:   ```
+    ```
+    <logger name="com.morpheus.remote.MorpheusGuacamoleWebsocketHandler" level="DEBUG"/>
+    ```
+    ```
+
+SCVMM
+:   ```
+    ```
+    <logger name="com.morpheus.compute.scvmm.ScvmmComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ScvmmComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.ScvmmProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+ServiceNow
+:   ```
+    ```
+    <logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="DEBUG"/>  
+    <logger name="com.morpheus.integrations.ServiceNowUtility" level="DEBUG"/>
+    ```
+    ```
+
+Tasks
+:   ```
+    ```
+    <logger name="com.morpheus.task.AnsibleTowerTaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.TaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.WinrmTaskService" level="DEBUG"/>
+    ```
+    ```
+
+Terraform
+:   ```
+    ```
+    <logger name="com.morpheus.app.AbstractResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.TerraformProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Usage
+:   ```
+    ```
+    <logger name="com.morpheus.AccountPriceService" level="DEBUG"/>
+    ```
+    ```
+
+vCloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VcloudDirectorProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.VcdComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Veeam
+:   ```
+    ```
+    <logger name="com.morpheus.backup.VeeamBackupService" level="DEBUG"/>
+    ```
+    ```
+
+Vmware
+:   ```
+    ```
+    <logger name="com.morpheus.compute.VmwareComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.vmware.VmwareComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VmwareProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+vRO
+:   ```
+    ```
+    <logger name="com.morpheus.automation.VroService" level="DEBUG"/>
+    ```
+    ```
+
+## All core logger paths
+
+Expand below to see all core HPE Morpheus Enterprise logger paths set to INFO level.
+
+### All core logger paths
+
+```
+```
+<logger name="com.bertramlabs.plugins.AccountsAuthService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AccountsService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.ActiveDirectoryUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AzureSamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomApiUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomExternalUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.DefaultUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.JumpCloudUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.LdapUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OktaUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OneLoginUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.PingUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.SamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.UserSourceAuthenticationProvider" level="INFO"/>  
+<logger name="com.morpheus.AbstractComputeService" level="INFO"/>  
+<logger name="com.morpheus.AbstractPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.AccountBudgetService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationObjectService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.AccountInvoiceService" level="INFO"/>  
+<logger name="com.morpheus.AccountPriceService" level="INFO"/>  
+<logger name="com.morpheus.AccountResourceService" level="INFO"/>  
+<logger name="com.morpheus.AccountUsageService" level="INFO"/>  
+<logger name="com.morpheus.ActivityService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AbstractAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AmazonConvertibleRiAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.CostAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.UtilizationAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.WorkloadAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.AnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.api.AbstractApiService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.CommandService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.DownloadService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.UploadService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.AppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.HelmAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.MorpheusAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.ScribeResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAzurermResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformGoogleResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformVsphereResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceClientService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceDelayedJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceHealthService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceLicenseService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceStorageService" level="INFO"/>  
+<logger name="com.morpheus.approval.ApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.RemedyApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.ServiceNowApprovalService" level="INFO"/>  
+<logger name="com.morpheus.AppService" level="INFO"/>  
+<logger name="com.morpheus.ArchiveService" level="INFO"/>  
+<logger name="com.morpheus.AsyncService" level="INFO"/>  
+<logger name="com.morpheus.AuditLogService" level="INFO"/>  
+<logger name="com.morpheus.automation.AbstractConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleTowerService" level="INFO"/>  
+<logger name="com.morpheus.automation.ChefService" level="INFO"/>  
+<logger name="com.morpheus.automation.ConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.HelmService" level="INFO"/>  
+<logger name="com.morpheus.automation.PuppetService" level="INFO"/>  
+<logger name="com.morpheus.automation.SaltStackService" level="INFO"/>  
+<logger name="com.morpheus.automation.VroService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupExecutionInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStatus" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStorageService" level="INFO"/>  
+<logger name="com.morpheus.backup.DirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.FileBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.KarmanStorageProviderBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmImageBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmSnapshotBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusApplianceBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusContainerBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MysqlBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.SqlserverBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.TarDirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.BootMacService" level="INFO"/>  
+<logger name="com.morpheus.builds.AbstractBuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.BuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.JenkinsBuildsService" level="INFO"/>  
+<logger name="com.morpheus.CapacityService" level="INFO"/>  
+<logger name="com.morpheus.CatalogCartService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemTypeService" level="INFO"/>  
+<logger name="com.morpheus.certificate.AbstractCertificateService" level="INFO"/>  
+<logger name="com.morpheus.certificate.MorpheusCertificateService" level="INFO"/>  
+<logger name="com.morpheus.CertificateService" level="INFO"/>  
+<logger name="com.morpheus.ChefClientService" level="INFO"/>  
+<logger name="com.morpheus.cm.ChangeManagementService" level="INFO"/>  
+<logger name="com.morpheus.cm.CherwellCmService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.AbstractCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.CmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.RemedyCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="INFO"/>  
+<logger name="com.morpheus.code.AbstractCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.CodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GitCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GithubCodeService" level="INFO"/>  
+<logger name="com.morpheus.compliance.NVDSyncService" level="INFO"/>  
+<logger name="com.morpheus.compliance.PackageManagementService" level="INFO"/>  
+<logger name="com.morpheus.compute.cisco.UcsComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.CloudPluginComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeApiService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.compute.IpmiService" level="INFO"/>  
+<logger name="com.morpheus.compute.KubernetesComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.MaasComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ManualComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.OneviewComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.SelfManagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.standard.StandardComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.unmanaged.UnmanagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VmwareComputeService" level="INFO"/>  
+<logger name="com.morpheus.ComputeService" level="INFO"/>  
+<logger name="com.morpheus.container.ActivemqContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.container.ElasticsearchContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.JavaContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.MysqlContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.NodeContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.PostgresContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.RedisContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.SqlserverContainerService" level="INFO"/>  
+<logger name="com.morpheus.ContainerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ContainerService" level="INFO"/>  
+<logger name="com.morpheus.costing.AbstractCostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingInterface" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.StandardCostingService" level="INFO"/>  
+<logger name="com.morpheus.CurrencyConversionService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherGORMDatastoreService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherService" level="INFO"/>  
+<logger name="com.morpheus.DashboardService" level="INFO"/>  
+<logger name="com.morpheus.DatastoreService" level="INFO"/>  
+<logger name="com.morpheus.DataViewService" level="INFO"/>  
+<logger name="com.morpheus.DbSchedulerService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.CloudFoundryAppDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DefaultDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DockerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.GrailsDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.IisDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.JbossDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.KubernetesDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.NodeDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.ServerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.VmDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.DeploymentService" level="INFO"/>  
+<logger name="com.morpheus.discovery.AbstractDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DatastoreCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostBalancingDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ReservationRecommendationDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ShutdownDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.SizeDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.dns.AbstractDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.BindDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.ConsulDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.DNSProvider" level="INFO"/>  
+<logger name="com.morpheus.dns.DnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.MicrosoftDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PluginDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PowerDnsService" level="INFO"/>  
+<logger name="com.morpheus.ElasticCleanupService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentVariableService" level="INFO"/>  
+<logger name="com.morpheus.ExecuteScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.ExecutionRequestService" level="INFO"/>  
+<logger name="com.morpheus.export.AccountInvoiceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.CodeRepositoryExportService" level="INFO"/>  
+<logger name="com.morpheus.export.DeploymentExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExecuteScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExportService" level="INFO"/>  
+<logger name="com.morpheus.export.InstanceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AdminIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AutomationIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.BackupIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.CertificateIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.DeployIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.NetworkIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerExpertService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerInstancesExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkDomainExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkPoolExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkRouterExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkSecurityGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.PowerScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServicePlanExportService" level="INFO"/>  
+<logger name="com.morpheus.export.TaskExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ThresholdExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.WorkflowExportService" level="INFO"/>  
+<logger name="com.morpheus.FileCopyRequestService" level="INFO"/>  
+<logger name="com.morpheus.GlobalSearchService" level="INFO"/>  
+<logger name="com.morpheus.host.AbstractHostService" level="INFO"/>  
+<logger name="com.morpheus.host.DockerHostService" level="INFO"/>  
+<logger name="com.morpheus.host.ExternalKubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.KubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.SwarmHostService" level="INFO"/>  
+<logger name="com.morpheus.HttpClientService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubQueueService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubSyncService" level="INFO"/>  
+<logger name="com.morpheus.imagebuild.ImageBuildService" level="INFO"/>  
+<logger name="com.morpheus.ImageCacheService" level="INFO"/>  
+<logger name="com.morpheus.instance.InstanceUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.InstanceService" level="INFO"/>  
+<logger name="com.morpheus.InstanceTypeService" level="INFO"/>  
+<logger name="com.morpheus.integration.AbstractIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.CherwellIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.GitRepoService" level="INFO"/>  
+<logger name="com.morpheus.integration.RemedyIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.RunDeckIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.SalesForceIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.ScribeService" level="INFO"/>  
+<logger name="com.morpheus.integration.ServiceNowIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.TerraformService" level="INFO"/>  
+<logger name="com.morpheus.jobs.AbstractJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.JobExecutor" level="INFO"/>  
+<logger name="com.morpheus.jobs.KubernetesJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.SecurityScanExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.TaskJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.WorkflowJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.JobService" level="INFO"/>  
+<logger name="com.morpheus.KeyPairService" level="INFO"/>  
+<logger name="com.morpheus.library.LayoutService" level="INFO"/>  
+<logger name="com.morpheus.LicenseService" level="INFO"/>  
+<logger name="com.morpheus.LoadBalancerPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.LocalizationService" level="INFO"/>  
+<logger name="com.morpheus.LocalRepoService" level="INFO"/>  
+<logger name="com.morpheus.log.AbstractLogService" level="INFO"/>  
+<logger name="com.morpheus.log.LogRhythmLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SplunkLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SyslogLogService" level="INFO"/>  
+<logger name="com.morpheus.LogService" level="INFO"/>  
+<logger name="com.morpheus.maint.UpdateService" level="INFO"/>  
+<logger name="com.morpheus.MarketplaceClientService" level="INFO"/>  
+<logger name="com.morpheus.MarshallService" level="INFO"/>  
+<logger name="com.morpheus.MetadataTagService" level="INFO"/>  
+<logger name="com.morpheus.migration.AbstractMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.HypervisorMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.LvmMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.MigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.WindowsMigrationService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlerterService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlertRuleService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AvailabilityService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.CheckAgentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.IncidentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorAppService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorChartingService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckManagementService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitoringService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MorpheusMonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.NewRelicService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.ServiceNowService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusComputeService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusPackageService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusSecurityService" level="INFO"/>  
+<logger name="com.morpheus.MotdService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AviLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.BluecatNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.BootService" level="INFO"/>  
+<logger name="com.morpheus.network.CitrixNetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.CloudPluginNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulService" level="INFO"/>  
+<logger name="com.morpheus.network.F5BigIpLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.F5LineRateLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.FirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.FortiADCLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.HaproxyLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InfobloxNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.IPAMProvider" level="INFO"/>  
+<logger name="com.morpheus.network.KubernetesRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.LoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.LocalFirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkConfigService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkServicesService" level="INFO"/>  
+<logger name="com.morpheus.network.NutanixNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PaloAltoNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.PhpipamNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PluginNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PxeService" level="INFO"/>  
+<logger name="com.morpheus.network.SolarWindsNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.StealthNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.NetworkDomainService" level="INFO"/>  
+<logger name="com.morpheus.OauthProviderService" level="INFO"/>  
+<logger name="com.morpheus.OperationEventService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourcePluginService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourceService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeListService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeService" level="INFO"/>  
+<logger name="com.morpheus.os.LinuxOsService" level="INFO"/>  
+<logger name="com.morpheus.os.WindowsOsService" level="INFO"/>  
+<logger name="com.morpheus.PermissionService" level="INFO"/>  
+<logger name="com.morpheus.plugin.AbstractPluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.BackupProviderPluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupJobImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupRestoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupResultImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationGroupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationSiteImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeServerInterfaceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeZoneFolderImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusDatastoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusAccountInvoiceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusCostingImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.cypher.MorpheusCypherImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusAccountInventoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusIntegrationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusCloudImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputePortImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeServerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeLayoutFactoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeSetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeZonePoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContainerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContextImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusInstanceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOperationNotificationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOsTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusPermissionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusProcessImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusReportImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusServicePlanImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusSnapshotImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStatsImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusTaskImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusUsageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageLocationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusWikiPageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainRecordImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolIpImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolRangeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkSubnetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.provisioning.MorpheusProvisionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.web.MorpheusWebRequestImplService" level="INFO"/>  
+<logger name="com.morpheus.policy.AbstractPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.BackupStoragePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.MotdPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.NetworkPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.PolicyServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageBucketQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageServerQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageShareQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.TagCompliancePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.WorkflowPolicyService" level="INFO"/>  
+<logger name="com.morpheus.PolicyService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.PriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.PricePlanService" level="INFO"/>  
+<logger name="com.morpheus.ProcessService" level="INFO"/>  
+<logger name="com.morpheus.ProfileService" level="INFO"/>  
+<logger name="com.morpheus.project.ProjectService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractBoxProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.CloudPluginProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerEngineProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ExternalProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.HelmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.IProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.KubernetesProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.MaasProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ManualProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.OneviewProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ScribeProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SelfManagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.StandardProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SwarmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.TerraformProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UcsProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UnmanagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.WorkflowProvisionService" level="INFO"/>  
+<logger name="com.morpheus.ProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.ProxyService" level="INFO"/>  
+<logger name="com.morpheus.ReferenceService" level="INFO"/>  
+<logger name="com.morpheus.report.AbstractReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonCoverageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonSavingsReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonUtilizationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CostReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InvoiceReportService" level="INFO"/>  
+<logger name="com.morpheus.report.MigrationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.PluginReportService" level="INFO"/>  
+<logger name="com.morpheus.report.ReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TenantUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TimeSeriesCostReportService" level="INFO"/>  
+<logger name="com.morpheus.RoleService" level="INFO"/>  
+<logger name="com.morpheus.RpcService" level="INFO"/>  
+<logger name="com.morpheus.scale.AbstractScaleService" level="INFO"/>  
+<logger name="com.morpheus.scale.MorpheusScaleService" level="INFO"/>  
+<logger name="com.morpheus.ScaleService" level="INFO"/>  
+<logger name="com.morpheus.scribe.ScribeLibraryService" level="INFO"/>  
+<logger name="com.morpheus.ScriptConfigService" level="INFO"/>  
+<logger name="com.morpheus.sdn.AbstractSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.MorpheusSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.OvsService" level="INFO"/>  
+<logger name="com.morpheus.sdn.VethSdnService" level="INFO"/>  
+<logger name="com.morpheus.security.AbstractSecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.security.ScapScanService" level="INFO"/>  
+<logger name="com.morpheus.security.SecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.SecurityGroupService" level="INFO"/>  
+<logger name="com.morpheus.SequenceService" level="INFO"/>  
+<logger name="com.morpheus.ServerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ServerService" level="INFO"/>  
+<logger name="com.morpheus.ServicePlanService" level="INFO"/>  
+<logger name="com.morpheus.SettingsService" level="INFO"/>  
+<logger name="com.morpheus.SetupService" level="INFO"/>  
+<logger name="com.morpheus.SiteService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotService" level="INFO"/>  
+<logger name="com.morpheus.StatsService" level="INFO"/>  
+<logger name="com.morpheus.StatusService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.BasicStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.CephStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.EcsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.IsilonStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.KubernetesStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.NfsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.QnapFileStationService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageVolumeService" level="INFO"/>  
+<logger name="com.morpheus.storage.ThreeParStorageService" level="INFO"/>  
+<logger name="com.morpheus.StorageProviderService" level="INFO"/>  
+<logger name="com.morpheus.SubAccountService" level="INFO"/>  
+<logger name="com.morpheus.task.AbstractTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTowerTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ChefTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerTemplateTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.EmailTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ExecutableTaskInterface" level="INFO"/>  
+<logger name="com.morpheus.task.GroovyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.HttpTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JavascriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JRubyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.LocalScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PuppetTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PythonTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.RestartTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ShellTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskConfigService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskService" level="INFO"/>  
+<logger name="com.morpheus.task.VroTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WinrmTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WriteAttributesTaskService" level="INFO"/>  
+<logger name="com.morpheus.trust.AbstractCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialProvider" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CypherCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.InternalCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.PluginCredentialService" level="INFO"/>  
+<logger name="com.morpheus.UsageLimitService" level="INFO"/>  
+<logger name="com.morpheus.UserGroupService" level="INFO"/>  
+<logger name="com.morpheus.UserManagementService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiAppService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiGatewayService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiPoolService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImagePriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImageService" level="INFO"/>  
+<logger name="com.morpheus.WikiPageService" level="INFO"/>  
+<logger name="com.morpheus.worker.DistributedWorkerService" level="INFO"/>  
+<logger name="com.morpheus.ZoneFolderService" level="INFO"/>  
+<logger name="com.morpheus.ZoneMarketplaceService" level="INFO"/>  
+<logger name="com.morpheus.ZonePoolService" level="INFO"/>  
+<logger name="com.morpheus.ZoneRegionService" level="INFO"/>  
+<logger name="com.morpheus.ZoneService" level="INFO"/>
+```
+```
+
+## Audit logs
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+2. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+3. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+4. Once the service has stopped enter the following at the xml prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+5. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..682cc1d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 280,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..83f6a4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,12 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html)**
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json b/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
new file mode 100644
index 0000000..f0c105b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+  "title": "Virtual Machines",
+  "ordinal": 212,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md b/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
new file mode 100644
index 0000000..2f129a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
@@ -0,0 +1,22 @@
+# Virtual Machines
+
+![../../_images/infra_compute_header_vms_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-354FC170-C67F-4589-B0CA-75A62F884A32-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+The Virtual Machines tab lists all managed and unmanaged VMs across HPE Morpheus Enterprise. Managed VMs are either provisioned by HPE Morpheus Enterprise, or are inventoried/discovered VMs that have been converted to managed. Unmanaged VMs are typically inventoried/discovered VMs from Cloud integrations.
+
+## Virtual Machine Change Cloud
+
+Change Cloud functionality allows a server to be reassociated to a new Cloud, which may be necessary at times for easier record keeping in HPE Morpheus Enterprise. In order to use this feature, the user must have “Infrastructure: Move Servers” permission set to “Full.”
+
+Changing Clouds might be necessary, for example, when moving a VM from one vCenter datacenter to another. We can use this tool to update the Cloud association in HPE Morpheus Enterprise as well. Other scenarios may include migrating workloads from private Cloud to public Cloud or even creating a brand new VM in a new Cloud which represents an identical workload to something pre-existing but which will be retired.
+
+NOTE
+
+For VMware Clouds, Cloud reassignment occurs automatically when a server is migrated from one cluster to another or from one resource pool to another within the same cluster. Following the next Cloud sync, HPE Morpheus Enterprise will reflect the migration made in vCenter. In this scenario, you should not try to use the manual change Cloud tools. In fact, you will receive a warning in HPE Morpheus Enterprise logs if you attempt to do so.
+
+To change Clouds, navigate to the VM detail page (Infrastructure > Compute > Virtual Machines > selected VM), click on the ACTIONS menu, and click Change Cloud. You can select the new target Cloud here and optionally select a new VM which the current one should be merged into. The important thing to keep in mind is that this tool is for HPE Morpheus Enterprise record keeping only. **It is not a tool which does migration work for you.** See the embedded video below for a demonstration of this feature.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json b/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
new file mode 100644
index 0000000..86ce3a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+  "title": "SSL Certificates",
+  "ordinal": 242,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md b/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
new file mode 100644
index 0000000..70d0220
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
@@ -0,0 +1,3 @@
+# SSL Certificates
+
+SSL certificates authenticate the identity of web servers and encrypt the data being transmitted. HPE Morpheus Enterprise stores SSL certificates to simplify administration and application of SSL certificates to HPE Morpheus Enterprise-managed resources.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json b/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
new file mode 100644
index 0000000..479dbdc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+  "title": "Unable to Provision a Custom Image",
+  "ordinal": 358,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Provision a Custom Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md b/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
new file mode 100644
index 0000000..69d4a98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
@@ -0,0 +1,22 @@
+# Unable to Provision a Custom Image
+
+## About this task
+
+Prior to provisioning an custom image, the image must be configured in the Library > Virtual Images section by selecting Edit on the Actions dropdown of the Virtual Image.
+
+In the Edit Virtual Image pane:
+
+## Procedure
+
+1. Select “Cloud Init Enabled?” only if the Virtual Image is a linux image with cloud init installed.
+2. Enter the username and password that are set on the Virtual Image.
+
+## Results
+
+NOTE
+
+When using Static IP’s or IP Pools in VMware, VMware tools must also be installed on the template in order for HPE Morpheus Enterprise to set the static IP address when provisioning.
+
+NOTE
+
+HPE Morpheus Enterprise agents only support 64-bit vm’s prior to versions 2.12.3 and 3.0.2
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..3ab4012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 510,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..eb59360
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,177 @@
+# ArubaCX Network Integration
+
+## Overview
+
+The ArubaCX network plugin is implemented as a HPE Morpheus Enterprise `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by HPE Morpheus Enterprise and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. HPE Morpheus Enterprise integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
+
+## Features
+
+- Network - Create or Delete OVS Port Group.
+
+## Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+### Server Network Configuration (Netplan)
+
+#### Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
+
+### Switch Configuration
+
+#### Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
+
+## Adding ArubaCX Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
+
+## Add ArubaCX Integration to a Cluster
+
+### Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json b/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
new file mode 100644
index 0000000..d91395c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+  "title": "Task Types",
+  "ordinal": 108,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md b/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
new file mode 100644
index 0000000..fe77622
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
@@ -0,0 +1,25 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| ansible | Ansible | Runs an Ansible playbook. Ansible Integration required | Ansible Repo (Git) | Local, Resource | Existing Ansible Integration | Library: Tasks |
+| ansibletower | Ansible Tower | Relays Ansible calls to Ansible Tower | Tower Integration | Local, Remote, Resource | Existing Ansible Tower Integration | Library: Tasks |
+| chef | Chef bootstrap | Executes Chef bootstrap and run list. Chef Integration required | Chef Server | Resource | Existing Chef Integration | Library: Tasks |
+| conditional | Conditional Workflow | Allows the user to set JavaScript logic. If it resolves to `true`, HPE Morpheus Enterprise will run the Operational Workflow set as the “IF OPERATIONAL WORKFLOW” and if it resolves to `false`, HPE Morpheus Enterprise will run the “ELSE OPERATIONAL WORKFLOW” | N/A (JavaScript logic must be locally sourced, Tasks housed within the associated Workflows may have different sourcing options depending on their types.) | Local | Existing Operational Workflows | Library: Tasks |
+| email | Email | Send an email from a Workflow | Task Content | Local | SMTP Configured | Library: Tasks |
+| groovy | Groovy script | Executes Groovy Script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| http | HTTP | Executes REST call for targeting external API’s. | Local | Local | None | Library: Tasks |
+| javascript | Javascript | Executes Javascript locally (on HPE Morpheus Enterprise app node) | Local | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| jruby | jRuby Scirpt | Executes Ruby script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| libraryscript | Library Script | Creates a Task from an existing Library Script (Library > Templates > Script Templates) | Library Script | Resource | Existing Library Script | Library: Tasks |
+| template | Library Template | Creates a Task from an existing Library Template (Library > Templates > Spec Templates) | Library Template | Resource | Existing Library Templates | Library: Tasks |
+| nestedworkflow | Nested Workflow | Embeds a Workflow into a Task which allows the Workflow to be nested within other Workflows for situations when common Task sets are frequently used in Workflows | N/A | Local | N/A | Library: Tasks |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| puppet | Puppet Agent Install | Executes Puppet Agent bootstrap, writes `puppet.conf` and triggers agent checkin. Puppet Integration required | Puppet Master | Resource | Existing Puppet Integration | Library: Tasks |
+| python | Python Script | Executes Python Script locally | Local, Repository, Url | Local | `virtualenv` installed on Appliance Nodes | Library: Tasks, Tasks ‐ Script Engines |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
+| vro | vRealize Orchestrator Workflow | Executes vRO Workflow on the Target Resource | vRO Integration | Local, Resource | Existing vRO Integration | Library: Tasks |
+| wa | Write Attributes | Add arbitrary values to the Attributes map of the target resource | N/A | Local | Provide map of values as valid JSON | Library: Tasks |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json b/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
new file mode 100644
index 0000000..7703696
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+  "title": "Uploading OS Images",
+  "ordinal": 407,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md b/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
new file mode 100644
index 0000000..14f9412
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
@@ -0,0 +1,15 @@
+# Uploading OS Images
+
+## Prerequisites
+
+- Image upload and deployment performance depend on network bandwidth and storage backend performance.
+- File permissions on shared storage must allow Morpheus read access.
+- OS images must be bootable and compatible with the target bare metal hardware.
+- Server reboots and virtual media behavior depend on hardware management interfaces (for example, iLO).
+
+**Subtopics**  
+
+- **[Uploading OS Images Using Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html)**
+- **[Uploading OS Images Using S3-Compatible Object Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html)**
+- **[Uploading OS Images Using CIFS (Samba)](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html)**
+- **[Uploading OS Images Using NFS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json b/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
new file mode 100644
index 0000000..7dca33c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+  "title": "How to un-manage an Instance/VM/Host",
+  "ordinal": 351,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html",
+  "topic_cluster": {
+    "clustering_title": "How to un-manage an Instance/VM/Host",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md b/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
new file mode 100644
index 0000000..0132990
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
@@ -0,0 +1,63 @@
+# How to un-manage an Instance/VM/Host
+
+## Description
+
+A managed VM (and associated Instance) needs to be unmanaged and returned to Discovered type.
+
+## Solution
+
+### About this task
+
+Delete the record from the Infrastructure  >  Compute (! not from Provisioning - Instances) selection with the following configuration in the Delete modal:
+
+- `Remove Infrastructure` UNCHECKED
+- `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+- `Force Delete` UNCHECKED
+
+The most important items to be aware of when “un-managing” an Instance/VM/Host are:
+
+### Procedure
+
+1. The “Remove from Infrastructure” flag when deleting a VM or Host in HPE Morpheus Enterprise determines if the actual VM is deleted from the target Infrastructure. 
+
+   - Checking “Remove Infrastructure” means you WANT TO DELETE THE ACTUAL VM. Typing “DELETE” in the confirmation field is required when “Remove From Infrastructure” is enabled.
+   - Unchecking “Remove Infrastructure” means you only want to delete the record in HPE Morpheus Enterprise but leave the actual VM untouched.
+2. Deleting an Instance will always remove Infrastructure. 
+
+   IMPORTANT
+
+   REPEAT: Deleting an Instance from the `Provisioning` section will always remove the VM aka Infrastructure.
+3. After removing the record from HPE Morpheus Enterprise, the VM must be in a Cloud with Inventory enabled to automatically be re-discovered.
+
+## Process
+
+### About this task
+
+Steps to delete a managed VM from HPE Morpheus Enterprise and, when necessary, remove the associated Instance:
+
+### Procedure
+
+1. Navigate to the VM (not Instance) detail page at Infrastructure  >  Compute - VMs 
+
+   NOTE
+
+   VM’s inside an Instance can be navigated to inside the Instance Details page by selecting the VM in the `VM's` seciton on the Instance Details page.
+2. Select DELETE
+3. Configure the DELETE HOST modal with the following settings: 
+
+   ![../_images/delete_host_modal.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7627FF0E-DEA9-4A41-8E6B-E1E752BA731F-high.png)
+   - `Remove Infrastructure` UNCHECKED
+   - `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+   - `Force Delete` UNCHECKED
+
+   IMPORTANT
+
+   If you have to type DELETE that means the `Remove Infrastructure` flag is selected and you are confirming deletion of the actual VM. Ensure `Remove Infrastructure` is UNCHECKED when you want to leave the VM intact!
+4. Select DELETE
+5. The VM and associated Insatnce will be removed from HPE Morpheus Enterprise but the actual VM will remain.
+6. Wait up to 5 min or click REFRESH on the associated Clouds details page to force a cloud sync. 
+
+   NOTE
+
+   `Inventory` must be enabled on the associated cloud for the VM to automatically be re-discovered by HPE Morpheus Enterprise.
+7. The VM is now back in HPE Morpheus Enterprise as discovered/unmanaged. To managed and create a new Instance from the VM, select ACTIONS : Convert To Managed.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json b/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
new file mode 100644
index 0000000..c001076
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+  "title": "Overview",
+  "ordinal": 147,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md b/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
new file mode 100644
index 0000000..872bf07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
@@ -0,0 +1,17 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. HPE Morpheus Enterprise includes a rich catalog of pre-configured System Images available for every cloud type. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into HPE Morpheus Enterprise via local file or url. Amazon and Azure Marketplace images can also be added to the Virtual Images Section.
+
+Understanding the process of prepping images for consumption in HPE Morpheus Enterprise is a very important step toward building an effective HPE Morpheus Enterprise environment. In addition to the information contained in this section on Virtual Images, it may be helpful to see a complete image prep example walkthrough. Our getting started guide for HPE Morpheus Enterprise and VMware includes [a section on preparing images](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html#prepping-an-image) that may provide a helpful example.
+
+TIP
+
+HPE Morpheus Enterprise includes a wide catalog of system image types as examples to show how the product can be used and to give users a starting point for implementing their own library. The included images are not intended to be production-ready images. HPE Morpheus Enterprise always recommends its users create their own gold images which meet their required specifications.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. HPE Morpheus Enterprise syncs in as much meta-data as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json b/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
new file mode 100644
index 0000000..d5f6e5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+  "title": "Configuring Tenants and Resources for Multi-Tenancy",
+  "ordinal": 279,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md b/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
new file mode 100644
index 0000000..84d0113
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
@@ -0,0 +1,264 @@
+# Configuring Tenants and Resources for Multi-Tenancy
+
+A very common scenario for Managed Service Providers (MSPs) is the need to provide access to resources on a customer-by-customer basis. Several administrative features are available in HPE Morpheus Enterprise to ensure customer resources are properly scoped and isolated. With its built-in multi-tenancy capabilities and white label support, managed service providers have a wide range of capabilities when it comes to managing customer Tenants and users.
+
+## Tenants
+
+There are essentially two types of Tenants in HPE Morpheus Enterprise
+
+- Master Tenant
+- Sub Tenants
+
+During the initial setup of a HPE Morpheus Enterprise Appliance, the Master Tenant is created. All Tenants created in addition to this Master Tenant are Subtenants. There is only one Master Tenant, though its child Tenants can create child Tenants of their own. The Master Tenant may scope resources to all other Tenants while any Subtenants which have children of their own may only scope resources to their immediate children Tenants.
+
+### Creating Tenants
+
+#### About this task
+
+The Master Tenant is created during the initial appliance setup. Additional sub-Tenants can be created in the Administration > Tenants section.
+
+The Tenants page displays a list of all Tenants. This page enables users to: Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, Status (active or inactive) and the Created Date. Click the Tenant Name to drill into the Tenant View where you can edit or delete the Tenant, as well as create, edit and delete users belonging to the Tenant.
+
+NOTE
+
+At least one Tenant in addition to the Master Tenant is required to scope resources across Tenants.
+
+To create a new sub-Tenant
+
+#### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the +Create Tenant button.
+4. From the New Tenant wizard input \* Name (Required) \* Description \* Base Role \* Currency (for pricing)
+
+#### Results
+
+The Base Role defines a role set from which all roles created within the Tenant will inherit.
+
+NOTE
+
+In prior versions, we could set Limits when creating a Subtenant. These could restrict the amount of storage, memory, and CPUs that can be collectively provisioned by all users in the Tenant. In more recent versions, this functionality has been rolled into Policies (Administration > Policies). When creating a Policy, we are able to specify a Tenant to which the Policy should apply.
+
+Click the Save Changes button.
+
+![The Create Tenant dialog box is shown](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-16DD7A70-0CA9-44E3-8361-DBA158D96416-high.png)
+
+### Viewing Tenants
+
+To View an individual Tenant page, select the Tenant name from the main Tenants section.
+
+![../../_images/viewtenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-39DE1887-6BEA-45F1-B234-9F2921BD663A-high.png)
+
+From inside the Tenant view, we can edit or delete the Tenant, as well as click into any of the Tenant’s users.
+
+### Tenant Users
+
+To create a new user within the Tenant:
+
+Click the CREATE USER button, then from the New User wizard input the fields below:
+
+- First Name
+- Last Name
+- Username
+- Email
+- Role
+- Password
+- Confirm Password
+
+Click Save Changes.
+
+NOTE
+
+Users are specific to each Tenant. Users created in the Master Tenant or other sub-Tenants will only have access to the Tenant they are created in.
+
+### Impersonate Tenant User
+
+HPE Morpheus Enterprise allows admin users in parent Tenants to impersonate any user in their child Tenants to see HPE Morpheus Enterprise as if they are that user. To impersonate a user, you must be logged in as a user with the “Impersonate User” feature enabled in the assigned role.
+
+From inside a Tenant detail page (containing the list of that Tenant’s users), and in the specific user’s ACTIONS drop down, select “Impersonate”.
+
+![../../_images/configuring_multi_tenancy-9583a.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-071C08CB-F499-4A7F-BFCA-87B4C6B6D08F-high.png)
+
+This will log you in as that user in their respective Tenant. To log out of the impersonate users Tenant, select the username in the header, and then select “Quit Impersonating”
+
+![../../_images/configuring_multi_tenancy-d229b.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C13E674E-CE80-485D-B60E-0F33BD0BE2F7-high.png)
+
+## Resources
+
+In the Master Tenant, resources can be configured with private or public visibility:
+
+- Private Visibility: Only available to the assigned Tenant.
+- Public Visibility (option available in Master Tenant only): Available across all Tenants
+
+Resources in the Master Tenant can also be assigned directly to Subtenants. When a resource is assigned to a Subtenant, it is only available for that Subtenant, and its visibility is automatically set to private. Public visibility is not an option for any resource assigned to or created in a Subtenant.
+
+From the Master Tenant, the following resources can be configured for public visibility across all Tenants, or assigned to individual sub-Tenants
+
+- Clouds
+- Hosts
+- Virtual Machines
+- Networks
+- Datastores
+- Resource Pools
+- Folders
+- Virtual Images
+- Library Instance Types
+- Pricing
+- Policies
+- Workflows
+- Roles
+
+NOTE
+
+Virtual Image Blueprints can be made available to multiple select Tenants when set to private.
+
+### Cloud Visibility & Assignment
+
+#### About this task
+
+To set the visibility of a Cloud to Public (shared across all Tenants) or Private (only available to the assigned Tenant):
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-349e2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF8023AD-C31F-4FF1-A51C-AE47C55EA399-high.png)
+
+When a cloud is set to Public visibility, it is available to be added to Subtenants. All Subtenants created after a Master Tenant cloud is set to public will automatically have clouds with public visibility added, and a group will be created for each available cloud matching the cloud name in the new Subtenant(s).
+
+For Tenants created prior to a Master Tenant cloud being set to public visibility, the Subtenant will have the option to add that cloud but it will not automatically be added.
+
+While the cloud will be available for Subtenants, the resources available in that cloud to the Subtenant(s) depends on the visibility or assignment of the individual resources.
+
+NOTE
+
+A Subtenant user must have sufficient role permissions and cloud access to add publicly available clouds. Master Tenant clouds settings cannot be edited from Subtenants.
+
+### Assign a Cloud to an Tenant
+
+IMPORTANT
+
+When assigning a Cloud to a Tenant, all resources for that Cloud will only be available to the assigned Tenant. If a cloud is created in the Master Tenant and assigned to a sub-Tenant, it will no longer be available for use by the Master Tenant or any other sub-Tenants, although it can be assigned back to the Master Tenant, or to another sub-Tenant.
+
+It may be preferable for service providers to share or assign their cloud resources, such as specific hosts, networks, resources pools and datastores, across sub-Tenants, rather than an entire cloud.
+
+### To assign a cloud from the Master Tenant to a Sub-Tenant
+
+#### Procedure
+
+1. Navigate to Infrastructure, Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Tenant” drop down, select the Tenant to assign the cloud to. The visibility will automatically be set to “Private” when a cloud is assigned to a sub-Tenant.
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-c907d.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1741E74F-481B-4D67-A2B0-B338A4958C9E-high.png)
+
+When a cloud is assigned to a sub-Tenant, or assigned to the Master Tenant with private visibility, that cloud and all of its resources are only available to the assigned Tenant. The Master Tenant still maintains control and visibility, and can edit the cloud settings or re-assign the cloud.
+
+### Individual Resource Visibility & Assignment
+
+Similar to clouds, individual resources from the Master Tenant can be set to public and available to sub-Tenants, or assigned to sub-Tenants.
+
+By default, any host, virtual machine, bare metal server, network, resource pool, datastore or blueprint added, created or inventoried by an Tenant is assigned to that Tenant. If these resources are in the Master Tenant, they can be assigned to sub Tenants. Assigning one of these resources will make it unavailable to the Master Tenant, but it will still be visible and editable by the Master Tenant. This allows Master Tenant resources to be isolated for use by sub-Tenants while still under the control of the Master Tenant.
+
+Resources assigned to sub-Tenants from the Master Tenant will be visible and available for use by that sub-Tenant, however they cannot be edited or re-assigned by the sub-tenant.
+
+### Set the Visibility of a Host, Virtual Machine or Bare metal Server to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. Select Edit in the resource page to bring up the config modal
+5. From the “Visibility” drop down, select either “Public” or “Private”
+6. Select Save Changes
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-d738d.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A6C1B836-5DF2-47CE-A78A-0A94A1A777C0-high.png)
+
+Assigning a Host, Virtual Machine, or Bare Metal server to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. From the “Actions” dropdown in the the resource page, select Assign Tenant
+5. In the Assign Tenant modal, select the Tenant to assign the resource to.
+6. Select Execute in the modal
+
+![../../_images/configuring_multi_tenancy-3c39f.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0DC2CDEE-E498-4EF1-B0B5-B54260A82FF7-high.png)
+
+The resource will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+### Set the Visibility of a Network to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-bc333.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9AB26FDA-4C5C-4F4C-ACD5-1013B6D3F162-high.png)
+
+### Assign a Network to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Tenant” drop down, select an Tenant to assign the network to.
+4. Select Save Changes in the lower the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-9f15c.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FC41C95A-2672-476A-B22E-2C2541407BB8-high.png)
+
+The Network will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+Set the Visibility or assign a datastore to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Storage
+2. Select the “Data Stores” tab
+3. Select Edit from the “Actions” dropdown in the datastores row
+4. From the “Visibility” drop down, select either “Public” or “Private”
+5. From the “Tenant” drop down, select the Tenant to assign the datastore to.
+
+   NOTE
+
+   If assigned to a sub-tenant, the visibility will be automatically set to private.
+6. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-1e978.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-77B5C886-86F4-40C1-A0D1-DE6EDDA1EBBB-high.png)
+
+### Set the Visibility or assign a Virtual Image to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Provisioning, Virtual Images
+2. Select Edit from the “Actions” dropdown in the Virtual Images row
+3. From the “Visibility” drop down, select either “Public” or “Private”. Public will share the
+4. From the “Tenant” field, start typing the name of the Tenant to assign the Virtual Image to. Matching Tenants will populate, then select the Tenant to add. 
+
+   NOTE
+
+   Virtual Images can be set to Private, but accessible to more that one Tenant
+
+#### Results
+
+#. Repeat step 4 for all Tenants requiring access to the virtual image. .. To remove access for an Tenant, click the “x” next to the Tenant name #. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-d9abe.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-453CA12C-D7A9-4CFE-83D3-B133334EE8C4-high.png)
+
+The Virtual Image will now be available for use by the assigned Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json b/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
new file mode 100644
index 0000000..58e745a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+  "title": "Chef",
+  "ordinal": 378,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html",
+  "topic_cluster": {
+    "clustering_title": "Chef",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md b/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
new file mode 100644
index 0000000..00b0a69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
@@ -0,0 +1,74 @@
+# Chef
+
+## Overview
+
+HPE Morpheus Enterprise integrates with one or multiple Chef servers to be used for bootstrapping while provisioning or as tasks in workflows in the Automation section. These workflows can then be run during provisioning in the provisioning wizard Automation pane, or on an existing Instance by selecting Run Workflows from the Actions menu on the Instance detail page. Workflows can also be added to Instances in the blueprint and app sections.
+
+## Add Chef Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Chef”
+3. Populate the following fields: 
+
+   - Name: Name of the Chef Integration in HPE Morpheus Enterprise
+   - Chef Endpoint: url of chef server api endpoint in <https://api.example.com> format. Do not add /organization/xxxx here, which is populated in the Chef Organization field
+   - Chef Version: 12.3.0 by default, can be changed to use a different/more recent version of chef
+   - Chef Organization: Chef Server Organization
+   - Chef User: Chef Server User
+   - User Private Key: The private key of the user with access to this chef server
+   - Organization Validator: Validator key for the organization
+4. Save Changes
+
+### Results
+
+The added Chef Integration is now available for use in HPE Morpheus Enterprise. The Chef Integration can be added to Clouds or Groups to auto-bootstrap nodes and specify Environment, Node ID, Runlist, Attributes and Tags when creating instances. The Chef integration can also be selected in the Chef Server dropdown when creating a Chef Bootstrap-type Task.
+
+NOTE
+
+Integrating Chef with HPE Morpheus Enterprise enables a user to bootstrap a node using Chef Bootstrap-type Tasks or Chef associations with Clouds or infrastructure Groups. It does not enable users to update run-lists on the Chef server for nodes which have already been bootstrapped.
+
+## Scope Chef Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Scope Chef Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Chef Integration added, a Chef section will appear in the Config section of the provisioning wizard. By default, Chef is enabled, but can be disabled by expanding the Chef section and unchecking Enable Chef.
+
+Chef Integration Provisioning options:
+
+Enable Chef
+:   Select to bootstrap
+
+Chef Environment
+:   Populate Chef environment, or leave as \_default
+
+Chef Node ID
+:   Defaults to instance name, configurable.
+
+Chef Runlist
+:   Add Runlist
+
+CHEF ATTRIBUTES
+:   Add Chef Attributes
+
+CHEF TAGS
+:   Add Chef tags
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json b/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
new file mode 100644
index 0000000..b782521
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+  "title": "Activity",
+  "ordinal": 78,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md b/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
new file mode 100644
index 0000000..9af3272
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
@@ -0,0 +1,61 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. HPE Morpheus Enterprise defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, and so on. This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+## Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+### To View a Recent Activity report:
+
+#### Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+#### Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
+
+### Review
+
+To review the item the activity occurred on, click the name of the activity and it will go to a new page and display that item.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, Groups, and Monitoring Checks.
+
+### To Filter:
+
+#### Procedure
+
+1. Click the filter drop down of type of filter you want to apply.
+2. Select the appropriate filter.
+
+## Alarms
+
+The ALARMS section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus Enterprise but synced and displayed for visibility in HPE Morpheus Enterprise.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
+
+## History
+
+The HISTORY section shows Process History from Instances and Apps processes. This is an aggregate view of the `History` tab in Instance and App details pages.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for HPE Morpheus Enterprise services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json b/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
new file mode 100644
index 0000000..0830010
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+  "title": "Task Results",
+  "ordinal": 111,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html",
+  "topic_cluster": {
+    "clustering_title": "Task Results",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md b/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
new file mode 100644
index 0000000..664d2de
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
@@ -0,0 +1,161 @@
+# Task Results
+
+## Overview
+
+Using Task results, the output from any preceding Tasks within the same Workflow phase is available to be called into additional Tasks. The results are stored on the `results` variable. Since results are available to all Tasks, we can use results from any or all prior Tasks so long as they are executed within the same provision phase.
+
+In script type tasks, if a RESULT TYPE is set, HPE Morpheus Enterprise will store the output on the `results` variable. It’s important to understand that the result type indicates the format of the Task output HPE Morpheus Enterprise should expect. HPE Morpheus Enterprise will parse that output into a Groovy map which can be retrieved and further parsed by resolving the `results` variable. If the RESULT TYPE is incorrectly set, HPE Morpheus Enterprise may not be able to store the Task results correctly. Jump to the section on [Script Config Examples](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1AAB6E42-CAE7-456C-85D2-FC3E917F731C.xml) to see how script results are processed in various example cases.
+
+## Results Types
+
+- Single Value
+  :   Entire task output is stored in `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable.
+- Key/Value pairs
+  :   Expects `key=value,key=value` output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+- JSON
+  :   Expects `key:value,key:value` json formatted output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+
+IMPORTANT
+
+The entire output of a script is treated as results, not just the last line. Ensure formatting is correct for the appropriate result type. For example, if Results Type is `json` and the output is not fully json compatible, the result would not return properly.
+
+IMPORTANT
+
+Task results are not supported for Library Script task types
+
+## Script Config Examples
+
+Single Value using Task Code
+:   Source Task Config
+    :   - NAME: Var Code (single)
+        - CODE: singleExample
+        - RESULT TYPE: Single Value
+        - SCRIPT: `echo "string value"`
+
+    Source Task Output: `string value`
+
+    Results Task Config (using task code in variable)
+    :   - NAME: N/A
+        - CODE: N/A
+        - RESULT TYPE: N/A
+        - SCRIPT: `echo "single: <%=results.singleExample%>"`
+
+    Results Task Output: `single: string value`
+
+Single Value using Task Name
+:   Source Task Config
+    :   NAME
+        :   Var Code
+
+        CODE
+        :   none
+
+        RESULT TYPE
+        :   Single Value
+
+        SCRIPT
+        :   `echo "string value"`
+
+    Source Task Output
+    :   `string value`
+
+    Results Task using task name in variable
+    :   Results Task Script
+        :   `echo "task name: <%=results["Var Code"]%>"`
+
+        Results Task Output
+        :   `task name: test value`
+
+Key/Value Pairs
+:   Source Task Config
+    :   NAME
+        :   Var Code (keyval)
+
+        CODE
+        :   keyvalExample
+
+        RESULT TYPE
+        :   Key/Value pairs
+
+        SCRIPT
+        :   `echo "flash=bang,ping=pong"`
+
+    Source Task Output
+    :   `flash=bang,ping=pong`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "keyval: <%=results.keyvalExample%>"`
+
+        Results Task Output
+        :   `keyval: [flash:bang, ping:pong]`
+
+    Results Task for a single value)
+    :   Results Task Script
+        :   `echo "keyval value: <%=results.keyvalExample.flash%>"`
+
+        Results Task Output
+        :   `keyval value: bang`
+
+JSON
+:   Source Task Config
+    :   NAME
+        :   Var Code (json)
+
+        CODE
+        :   jsonExample
+
+        RESULT TYPE
+        :   JSON
+
+        SCRIPT
+        :   `echo "{\"ping\":\"pong\",\"flash\":\"bang\"}"`
+
+    Source Task Output
+    :   `{"ping":"pong","flash":"bang"}`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "json: <%=results.jsonExample%>"`
+
+        Results Task Output
+        :   `json: [ping:pong, flash:bang]`
+
+    Results Task for a single value
+    :   Results Task Script
+        :   `echo "json value: <%=results.jsonExample.ping%>"`
+
+        Results Task Output
+        :   `json value: pong`
+
+    Multiple Task Results
+    :   Results Task Script
+        :   ```
+            ```
+            echo "single: <%=results.singleExample%>"  
+            echo "task name: <%=results["Var Code"]%>"  
+            echo "keyval: <%=results.keyvalExample%>"  
+            echo "keyval value: <%=results.keyval.flash%>"  
+            echo "json: <%=results.jsonExample%>"  
+            echo "json value: <%=results.jsonExample.ping%>"
+            ```
+            ```
+
+        Results Task Output
+        :   ```
+            ```
+            single: string value  
+            task name: string value  
+            keyval: [flash:bang, ping:pong]  
+            keyval value: bang  
+            json: [ping:pong, flash:bang]  
+            json value: pong
+            ```
+            ```
+
+## Workflow Config
+
+Add one or multiple tasks with Results Type configured to a workflow, and the results will be available to all tasks in the same phase of the workflow via the `<%=results.variables%>` during the workflow execution.
+
+- Task Results are only available to tasks in the same workflow phase
+- Task Results are only available during workflow execution
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json b/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
new file mode 100644
index 0000000..9713d9f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+  "title": "Answer Files",
+  "ordinal": 252,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html",
+  "topic_cluster": {
+    "clustering_title": "Answer Files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md b/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
new file mode 100644
index 0000000..2ab924e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
@@ -0,0 +1,51 @@
+# Answer Files
+
+Answer files are like lists of answers for questions that you know the setup program is going to ask but the user is not prepared to answer. They contain one or more sections, and each section contains one or more properties in the form name=value. Morpheus provides Answer Files for ESXi, CentOS, Ubuntu and XenServer, and user can add their own.
+
+## Add Answer Files
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab then click the Add Answer File button.
+4. From the New Answer File Wizard input the following information 
+
+   Name
+   :   Name of the answer file.
+
+   Description(optional)
+   :   Description of the new answer file.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Script Name
+   :   Name of the new answer file.
+
+   Script Version
+   :   Version of the new answer file.
+
+   Script
+   :   The script for the new answer file.
+5. Save
+
+## Edit Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab
+4. Click the edit icon on the row of the answer file you wish to edit.
+5. Modify information as needed.
+6. Save Changes
+
+## Delete Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab.
+4. Click the delete icon on the row of the answer file you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json b/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
new file mode 100644
index 0000000..1842f68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+  "title": "Overview",
+  "ordinal": 316,
+  "parent_title": "Policies",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md b/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
new file mode 100644
index 0000000..1a8b36e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
@@ -0,0 +1,3 @@
+# Overview
+
+Policies add governance, ease of use, cost-savings, and auditing features to HPE Morpheus Enterprise. HPE Morpheus Enterprise enables end users to create Policies scoped to Users, Roles, Groups, Clouds, Tenants, Networks, Plans, and Global scoping to give Admins full control and governance over their environments. The available scoping will vary from one Policy type to another. See the section below for information on each Policy type and guides for more complex Policy implementation.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json b/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
new file mode 100644
index 0000000..8da090a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+  "title": "Costing",
+  "ordinal": 73,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html",
+  "topic_cluster": {
+    "clustering_title": "Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md b/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
new file mode 100644
index 0000000..519ba0e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
@@ -0,0 +1,7 @@
+# Costing
+
+**Subtopics**  
+
+- **[Budgets](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html)**
+- **[Invoices](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json b/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
new file mode 100644
index 0000000..3542704
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+  "title": "Task Configuration",
+  "ordinal": 109,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html",
+  "topic_cluster": {
+    "clustering_title": "Task Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md b/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
new file mode 100644
index 0000000..bc1c65b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
@@ -0,0 +1,322 @@
+# Task Configuration
+
+## Ansible Playbook
+
+![ansible](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FCAE649B-4E95-4F5B-A897-78C6A01F895D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ANSIBLE REPO:** Select existing Ansible Integration
+- **GIT REF:** Specify tag or branch (Option, blank assumes default)
+- **PLAYBOOK:** Name of playbook to execute, both `playbook` and `playbook.yml` format supported
+- **TAGS:** Enter comma separated tags to filter executed tasks by (ie `--tags`)
+- **SKIP TAGS:** Enter comma separated tags to run the playbook without matching tagged tasks (ie `--skip-tags`)
+
+IMPORTANT
+
+Using different Git Refs for multiple Ansible Tasks in same Workflow is not supported. Git Refs can vary between Workflows, but Tasks in each Workflow must use the same Git Ref.
+
+## Ansible Tower Job
+
+![ansibletower](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AF431C26-FA58-4140-8DAA-09CCA119F769-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TOWER INTEGRATION:** Select an existing Ansible Tower integration
+- **INVENTORY:** Select an existing Inventory, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Inventory
+- **GROUP:** Enter a group name, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Group if it exists. If it does not exist, HPE Morpheus Enterprise will create the Group
+- **JOB TEMPLATE:** Select an existing job template to associate with the Task
+- **SCM OVERRIDE:** If needed, specify an SCM branch other than that specified on the template
+- **EXECUTE MODE:** Select Limit to Instance (template is executed only on Instance provisioned), Limit to Group (template is executed on all hosts in the Group), Run for all (template is executed on all hosts in the Inventory), or Skip Execution (to skip execution of the template on the Instance provisioned)
+
+## Chef bootstrap
+
+![chef](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-531590A7-AFBE-40A7-BBBF-D4E7EB32974A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **CHEF SERVER:** Select existing Chef integration
+- **ENVIRONMENT:** Populate Chef environment, or leave as `_default`
+- **RUN LIST:** Enter Run List, eg `role[web]`
+- **DATA BAG KEY:** Enter data bag key (will be masked upon save)
+- **DATA BAG KEY PATH:** Enter data bag key path, eg `/etc/chef/databag_secret`
+- **NODE NAME:** Defaults to Instance name, configurable
+- **NODE ATTRIBUTES:** Specify attributes inside the `{}`
+
+## Conditional Workflow
+
+![../../_images/conditional.svg](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C6A92829-120A-43A5-AAFA-221E3A1C89EF-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **LABELS:** A comma separated list of Labels for organizational purposes. See elsewhere in HPE Morpheus Enterprise docs for additional details on utilizing Labels
+- **CONDITIONAL (JS):** JavaScript logic which determines the Operational Workflow which is ultimately run. If it resolves to `true`, the “If” Workflow is run and if it resolves to `false` the “Else” Workflow is run
+- **IF OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `true`
+- **ELSE OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `false`
+
+## Groovy script
+
+![groovy](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DA7C204B-DFAC-493A-A877-21B026F00D4D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the Groovy script if not sourcing it from a repository
+
+## Email
+
+![email](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9C895BAB-4D33-430F-8250-668229AB3E8A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **SOURCE:** Choose local to draft or paste the email directly into the Task. Choose Repository or URL to bring in a template from a Git repository or another outside source
+- **EMAIL ADDRESS:** Email addresses can be entered literally or HPE Morpheus Enterprise automation variables can be injected, such as `<%=instance.createdByEmail%>`
+- **SUBJECT:** The subject line of the email, HPE Morpheus Enterprise automation variables can be injected into the subject field
+- **CONTENT:** The body of the email is HTML. HPE Morpheus Enterprise automation variables can be injected into the email body when needed
+- **SKIP WRAPPED EMAIL TEMPLATE:** The HPE Morpheus Enterprise-styled email template is ignored and only HTML in the Content field is used
+
+TIP
+
+To whitelabel email sent from Tasks, select SKIP WRAPPED EMAIL TEMPLATE and use an HTML template with your own CSS styling
+
+## HTTP (API)
+
+![http](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3D6C1D43-48AE-4C22-AB38-7FF3748A8812-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **URL:** An HTTP or HTTPS URL as the HTTP Task target
+- **HTTP METHOD:** GET (default), POST, PUT, PATCH, HEAD, or DELETE
+- **AUTH USER:** Username for username/password authentication
+- **PASSWORD:** Password for username/password authentication
+- **BODY:** Request Body
+- **HTTP HEADERS:** Enter requests headers, examples below:
+
+|  |  |
+| --- | --- |
+| Authorization | Bearer token |
+| Content‐Type | application/json |
+
+- **IGNORE SSL ERRORS:** Mark when making REST calls to systems without a trusted SSL certificate
+
+## Javascript
+
+![javascript](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-20848F50-8905-4E2C-B84A-2964DB407179-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Javascript contents to execute
+
+## jRuby Script
+
+![jruby](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6DDC7639-A017-4555-A527-0F3DD5216833-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the jRuby script is entered here if it’s not being called in from an outside source
+
+## Library Script
+
+![libraryscript](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C1C0F695-54E0-43B9-90F3-A1112041085D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Search for an existing script in the typeahead field
+
+## Library Template
+
+![template](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-296B3993-FE5F-4AB8-B8AE-71D293861775-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TEMPLATE:** Search for an existing template in the typeahead field
+
+## Nested Workflow
+
+![../../_images/nestedworkflow.svg](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-949F99E1-949C-499A-980C-1AB5753BA11D-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **OPERATIONAL WORKFLOW:** The Workflow to be embedded as a Task for reference inside other Workflows
+
+## Powershell Script
+
+![powershell](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-69279397-D83C-4B50-9330-CA25F54BE9B0-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **VERSION:** Select the version of Powershell this Task should run in. Powershell 5 is the default selection, Powershell 6 or 7 must be installed on the target to select those versions
+- **ELEVATED SHELL:** Run script with administrator privileges
+- **IP ADDRESS:** IP address of the PowerShell Task target
+- **PORT:** SSH port for PowerShell Task target (5985 default)
+- **USERNAME:** Username for PowerShell Task target
+- **PASSWORD:** Password for PowerShell Task target
+- **Content:** Enter script to execute if not calling the script in from an outside source
+
+NOTE
+
+Setting the execution target to local requires Powershell to be installed on the HPE Morpheus Enterprise appliance box(es). [Microsoft Documentation](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.2) contains installation instructions for all major Linux distributions and versions.
+
+## Puppet Agent Install
+
+![puppet](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D625B993-30CE-4020-ACA7-B098CF811E3F-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **PUPPET MASTER:** Select Puppet Master from an existing Puppet integration
+- **PUPPET NODE NAME:** Enter Puppet node name. Variables supported eg. `<%= instance.name %>`
+- **PUPPET ENVIRONMENT:** Enter Puppet environment, eg. `production`
+
+## Python Script
+
+![python](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AB6EBB6F-6FB7-48D7-A2F6-EB4F4012B5A8-high.png)
+
+IMPORTANT
+
+Python Tasks use virtual environments. For this reason, `virtualenv` must be installed on your appliances in order to work with Python Tasks. See the information below for more detailed steps to install `virtualenv` on your HPE Morpheus Enterprise appliance node(s).
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Python script to execute is entered here if not pulled in from an outside repository
+- **COMMAND ARGUMENTS:** Optional arguments passed into the Python script. Variables supported eg. `<%= instance.name %>`
+- **ADDITIONAL PACKAGES:** Additional packages to be installed after `requirements.txt` (if detected). Expected format for additional packages: ‘packageName==x.x.x packageName2==x.x.x’, the version must be specified
+- **PYTHON BINARY:** Optional binary to override the default Python binary
+
+NOTE
+
+When troubleshooting errors in Python scripts using line numbers reported in HPE Morpheus Enterprise UI (such as in Task execution histories), you must subtract four line numbers to arrive at the correct line in the Python document. This is because HPE Morpheus Enterprise injects four lines at execution time to add HPE Morpheus Enterprise environment variables.
+
+**Enterprise Proxy Considerations**
+
+Additional considerations must be made in enterprise proxy environments where Python Tasks are run with additional package download requirements. These additional packages are downloaded using `pip` and may not obey global HPE Morpheus Enterprise proxy rules. To deal with this, create or edit the pip configuration file at `/etc/pip.conf`. Your configuration should include something like the following:
+
+```
+```
+[global]  
+proxy = http://some-proxy-ip.com:8087
+```
+```
+
+For more information, review the Pip documentation on using proxy servers [here](https://pip.pypa.io/en/stable/user_guide/#using-a-proxy-server).
+
+**CentOS 7 / Python 2.7 (RHEL system Python)**
+
+With a fresh install of HPE Morpheus Enterprise on a default build of CentOS 7, Python Tasks will not function due to the missing requirement of `virtualenv`.
+
+If you attempt to run a python task, you will get an error similar to the following:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-8ae51ebf-749c-4354-b6e4-11ce541afad5/bin/python: command not found
+```
+```
+
+In order to run HPE Morpheus Enterprise Python Tasks in CentOS 7, install `virtualenv`: `yum install python-virtualenv`
+
+If you require `python3`, you can specify the binary to be used while building the virtual environment. In a default install, do the following: `yum install python3`. Then, in your HPE Morpheus Enterprise Python Task, specify the binary in the PYTHON BINARY field as “/bin/python3”. This will build a virtual environment in `/tmp` using the `python3` binary, which is equivalent to making a virtual environment like so: `virtualenv ~/venv -p /bin/python3`.
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+**CentOS 8 and Python**
+
+In CentOS 8, Python is not installed by default. There is a `platform-python` but that should not be used for anything in userland. The error message with a default install of CentOS 8 will be similar to this:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-cffc9a8f-c40d-451d-956e-d6e9185ade33/bin/python: command not found
+```
+```
+
+The default `virtualenv` for CentOS 8 is the python3 variety, for HPE Morpheus Enterprise to use Python Tasks, do the following: `yum install python3-virtualenv`
+
+If Python2 is required, do the following: `yum install python2` and specify `/bin/python2` as the PYTHON BINARY in your HPE Morpheus Enterprise Task.
+
+This will build a `virtualenv` in `/tmp` using the `python2` binary, which is equivalent to making a `virtualenv` like so: `virtualenv ~/venv -p /bin/python2`
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+## Restart
+
+![restart](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12DFE21D-BC68-4969-B496-340CA3E40690-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+
+## Shell Script
+
+![shellscript](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-66BC263C-CF8F-4199-B05B-99D786BF9288-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SUDO:** Mark the box to run the script as `sudo`
+- **CONTENT:** Script to execute is entered here if not pulled in from an outside repository
+
+TIP
+
+When the EXECUTE TARGET option is set to “Local” (in other words, the Task is run on the appliance itself), two additional fields are revealed: GIT REPO and GIT REF. Use GIT REPO to set the PWD shell variable (identifies the current working directory) to the locally cached repository (ex. /var/opt/morpheus-node/morpheus-local/repo/git/76fecffdf1fe96516e90becdab9de) and GIT REF to identify the Git branch the Task should be run from if the default (typically main or master) shouldn’t be used. If these options are not set, the working folder will be /opt/morpheus/lib/tomcat/temp which would not allow scripts to reference file paths relative to the repository (if needed).
+
+## vRealize Orchestrator Workflow
+
+![vro](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ABE75AA7-6B9F-46FE-9A67-D463924B577D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **vRO INTEGRATION:** Select an existing vRO integration
+- **WORKFLOW:** Select a vRO workflow from the list synced from the selected integration
+- **PARAMETER BODY (JSON):**
+
+## Write Attributes
+
+![wa](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C48074E2-3DB2-4459-98D0-AC5282256582-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ATTRIBUTES:** A JSON map of arbitrary values to write to the attributes property of the target resource
+
+TIP
+
+This is often useful for storing values from one phase of a Provisioning Workflow for access in another phase. See the video demo below for a complete example.
+
+There are a number of ways that a JSON payload can be statically drafted within a Write Attributes Task or called into the Task as a result from a prior Task. Consider the following examples:
+
+To pass in a static JSON map with static values, use the format shown below.
+
+```
+```
+{  
+  "my_key1": "my_value1",  
+  "my_key2": "my_value2"  
+}
+```
+```
+
+To pass in a static JSON map with dynamic values seeded from prior Task results, ensure the RESULT TYPE value of one or more of the prior Tasks in the Workflow phase is set to “Single Value” and refer to the values within the JSON map as shown in the next example. Note that “taskCode1” and “taskCode2” refer to the CODE field value for the Task whose output you wish to reference.
+
+```
+```
+{  
+  "my_key1": "<%=results.taskCode1%>",  
+  "my_key2": "<%=results.taskCode2%>"  
+}
+```
+```
+
+To pass in a dynamic JSON map returned from a prior Task, format your Write Attributes Task as shown in the next example. Ensure that the RESULT TYPE value for the Task returning a JSON map is set to “JSON”. Note that “taskCode” in the example refers to the CODE field value for the Task being referenced. In order for the JSON map to be set correctly and able to be referenced from future Tasks, you must set the “instances” key and call the `encodeAsJSON()` Groovy method as shown in the example.
+
+```
+```
+{  
+  "instances": <%=results.taskCode?.encodeAsJSON()%>  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json b/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
new file mode 100644
index 0000000..32b4806
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+  "title": "Containers",
+  "ordinal": 213,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md b/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
new file mode 100644
index 0000000..91c7c7c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
@@ -0,0 +1,9 @@
+# Containers
+
+![../../_images/infra_compute_header_containers_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ECD57864-C48E-460D-A2E1-5B01CC0F8610-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Container Type Cloud
+
+The containers tab lists all Containers associated with HPE Morpheus Enterprise Instances accessible to the user. Note additional system level containers from Kubernetes and Docker Clusters are not listed here but are accessible in Cluster detail sections.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json b/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
new file mode 100644
index 0000000..e7104d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+  "title": "Plugins",
+  "ordinal": 313,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md b/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
new file mode 100644
index 0000000..bcfe5a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
@@ -0,0 +1,23 @@
+# Plugins
+
+## Overview
+
+HPE Morpheus Enterprise is extendable with custom plugins for Task types, UI tabs, reports, approvals, cypher, and more. Plugins are added from the Plugins tab of the Integration page under Administration (Administration > Integrations > Plugins). Simply browse for a local plugin file (.jar) to add it to the UI. Custom plugins can also be edited or deleted by clicking on the pencil or trash can icons in the corresponding row.
+
+HPE Morpheus Enterprise maintains a repository of internally-developed and vetted plugins at HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/). These plugins can be downloaded and added to HPE Morpheus Enterprise using the instructions in the prior paragraph. Alongside the download link, you can also find helpful readme information that discusses how the plugin can be used and which versions of HPE Morpheus Enterprise it’s compatible with.
+
+With at least one plugin integrated, HPE Morpheus Enterprise will show details on each plugin from the Plugins List View. The following information is displayed:
+
+- **NAME:** The name given to the plugin
+- **DESCRIPTION:** A description value (if any) coded into the plugin
+- **FILE NAME:** The .jar filename
+- **VERSION:** The plugin version number
+- **STATUS:** The status of the plugin, such as “loaded” when the plugin is ready for use
+- **STATUS MESSAGE:** A status message (if any) for the plugin
+- **ENABLED:** If the plugin is enabled, a check mark appears here. Disabled plugins are also grayed out
+
+Additional information about each plugin can be viewed by clicking on the pencil (edit) icon. Most of the information in this modal is read-only but you can enable or disable plugins from this pane.
+
+Please visit the [Morpheus Developer Portal](https://developer.morpheusdata.com) for Plugin Architecture SDK documentation and help getting started with custom Plugin development.
+
+![../../_images/plugins_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E806E13E-76E4-477E-BE44-5A16FC97B809-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json b/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
new file mode 100644
index 0000000..fcd8bbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+  "title": "Troubleshooting",
+  "ordinal": 345,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md b/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
new file mode 100644
index 0000000..436fefc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
@@ -0,0 +1,20 @@
+# Troubleshooting
+
+- [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+**Subtopics**  
+
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7_2.html)**
+- **[Ansible Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html)**
+- **[Attaching Logs to Case](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html)**
+- **[CLI Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html)**
+- **[Cannot Login](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html)**
+- **[How to un-manage an Instance/VM/Host](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html)**
+- **[MySQL Too many connections error](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html)**
+- **[HPE Morpheus Enterprise Agent Install Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html)**
+- **[HPE Morpheus Enterprise UI not loading after upgrade or reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html)**
+- **[Remote Console](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html)**
+- **[SSL Self-signed Certificate Regeneration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html)**
+- **[Unable to Delete Tenant](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html)**
+- **[Unable to Provision a Custom Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json b/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
new file mode 100644
index 0000000..23f2b85
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+  "title": "Options",
+  "ordinal": 152,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html",
+  "topic_cluster": {
+    "clustering_title": "Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md b/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
new file mode 100644
index 0000000..f3cf8ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
@@ -0,0 +1,11 @@
+# Options
+
+Options are user-defined custom inputs that are used throughout HPE Morpheus Enterprise. Depending on the type of Input being created, users may need to create only an Input, or it might need to be paired with an Option List. Option Lists are static or dynamic lists of selections that would be associated with an Input if the user must make choices from a select list or typeahead field. This section discusses how to create different types of Inputs depending on the situation and powerful tools the user can take advantage of, such as dynamically filtered cascading inputs, logically generated Option Lists called from local or remote sources, and more.
+
+**Subtopics**  
+
+- **[Forms](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html)**
+- **[Inputs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html)**
+- **[Option Lists](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html)**
+- **[LDAP Query Variables](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html)**
+- **[Creating an Option List Based on an LDAP Query](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json b/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
new file mode 100644
index 0000000..05b379f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 452,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md b/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
new file mode 100644
index 0000000..b110063
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
@@ -0,0 +1,6 @@
+# Firmware and Driver Lifecycle Management
+
+| S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Morpheus / iLO fails to initialize the server after the SPP update | Server provisioning fails with errors similar to:  - `Base.1.18.ResourceMissingAtURI` - `Drives/64515 not found` - `HTTP null` - Storage object lists drive URIs that cannot be resolved | 1. Verify storage drive URIs:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Systems/1/Storage/<controller> | jq    ```    ``` 2. Validate drive URI exists:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Chassis/<chassis>/Drives/<id> | jq    ```    ``` 3. Confirm SPP was applied recently | Morpheus / iLO logs | Typically caused by stale Redfish drive references after SPP. |
+| 2 | After SPP, Redfish drive tree mismatch | Storage object shows drive count and IDs, but drive URIs return ResourceMissingAtURI | Perform a **Full Cold Power Cycle** (not reboot):   1. Power OFF the server (OS or iLO) 2. Remove both power cables 3. Wait 60 seconds 4. Reconnect power cables 5. Power ON the server | iLO event log, Smart Array logs | Required for Gen11/Gen12 after firmware updates. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json b/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
new file mode 100644
index 0000000..b00032f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+  "title": "Automation Integrations",
+  "ordinal": 532,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md b/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
new file mode 100644
index 0000000..432a272
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
@@ -0,0 +1,14 @@
+# Automation Integrations
+
+- Ansible
+- Ansible Tower
+- Chef
+- Puppet
+
+NOTE
+
+Automation integrations can be added and managed in Administration > Integrations as well. Adding and editing Integrations in Library > Integrationsand Administration > Integrations are the same dataset and additions and updates are reflected in both sections.
+
+NOTE
+
+Role access for `Integrations: Ansible` determines user access to Ansible Integration detail page, which contains Ansible command line and execution access.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json b/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
new file mode 100644
index 0000000..5a1fdd2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+  "title": "Add Load Balancer to Instance",
+  "ordinal": 497,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer to Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md b/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
new file mode 100644
index 0000000..dd5fef8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
@@ -0,0 +1,11 @@
+# Add Load Balancer to Instance
+
+Load Balancers can be added to Instances during Provisioning or to existing Instances. For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+NOTE
+
+For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+**Subtopics**  
+
+- **[Add Load Balancer during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json b/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
new file mode 100644
index 0000000..da4b12f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+  "title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+  "ordinal": 353,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md b/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
new file mode 100644
index 0000000..a6034c5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
@@ -0,0 +1,172 @@
+# HPE Morpheus Enterprise Agent Install Troubleshooting
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+### For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+### SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+### VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+### Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+### Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+### Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+### Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
+
+## Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+### Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+### Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
+
+## Uninstall HPE Morpheus Enterprise Agent
+
+### Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+### Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
+
+## CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json b/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
new file mode 100644
index 0000000..3ecf888
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+  "title": "HPE Morpheus Enterprise Blueprints",
+  "ordinal": 136,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md b/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
new file mode 100644
index 0000000..5f27882
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
@@ -0,0 +1,191 @@
+# HPE Morpheus Enterprise Blueprints
+
+HPE Morpheus Enterprise App Blueprints allow pre-configured full multi-tier application deployments for multiple environments. Blueprints can be provisioned from the Provisioning > Apps section and can be fully configured for one click provisioning. Blueprints can be built within the `Builder` section or by code in the `Raw` section. Blueprints can also be exported as YAML or JSON and created with the HPE Morpheus Enterprise API and CLI.
+
+A unique capability of the YAML/JSON based Morpheus blueprint structure is the ability to have multiple configurations per instance being provisioned within the app blueprint. This can be a scoped configuration that acts as overrides based on selected cloud, group, and/or environment the app is being provisioned in as a target. For example. maybe the “development” environment doesn’t need as many horizontally scaled nodes as the “production” environment. Another great aspect of this configuration markup is a blueprint can be defined as a hybrid cloud blueprint. This makes the app blueprint structure very powerful and in some ways better than alternative infrastructure as code orchestrators. For Example, ARM is locked into Azure, while CloudFormation is locked into AWS. Even Terraform does not allow a tf file to expand its bounds beyond a specific provider type.
+
+## Basic Blueprint Structure
+
+In a Morpheus App Blueprint there are a few structural concepts to be aware of. Firstly there is a concept of a Tier. A Tier is a grouping of instances within an app blueprint. Tiers can be used for a variety of things including sequenced booting of instances or even properly creating endpoint groups and security group contexts in network security tools like Cisco ACI. An example of a Tier structure might be a `Web` tier and a `Database` tier. These tiers can also be marked as connected such that network communication rules can appropriately be defined. A basic 2 Tier blueprint skeleton might look something like this:
+
+```
+```
+name: Tier Example  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers:  
+      - Database  
+    tier:  
+      bootOrder: 1  
+    instances:  
+  Database:  
+    tier:  
+      bootOrder: 0  
+    instances:
+```
+```
+
+This example has defined 2 tiers as yaml properties under the tiers object. They are called Web and Database. A Tier can optionally define its connected tiers which are bi-directional even though only one tier has to define them. This is the linkedTiers array and simply lists the connected tiers by tier name. A Boot Order can also optionally be defined under a nested `{"tier": {"bootOrder": 1}}` object structure.
+
+## Configuration Scopes
+
+Another capability of Morpheus App Blueprint structure is its configuration scoping. This allows properties to be overridden based on the apps target environment or even target group and cloud. For example. Maybe we want to use a larger plan size in production vs. development
+
+An example of that can be done using “environments” overrides.
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              code: container-128  
+         environments:  
+           Production:  
+             groups:  
+               All Clouds Demo:  
+                 clouds:  
+                   AWS Cali:  
+                     plan:  
+                       code: container-256
+```
+```
+
+Note the new environments object. The object graph of the morpheus blueprint structure gets merged and flattened at provision time based on the scope of the configurations provided as well as the users target cloud, group, and environment selection. In the Above example, a selective override was done for the AWS Cali cloud when using a Production Environment and deploying to the group All Clouds Demo. This specific example changes the plan to a larger size. Scoped configurations have various levels of precedence. Cloud is the lowest level of precedence. a cloud configuration in a group is the next level higher and finally an environment configuration in a group in a cloud is the highest level of scoped precedence.
+
+## Getting Started
+
+To get started, it may be best to look at a simple App Blueprint configuration. Docker templates are less complex than virtual machine based templates so lets look at a Blueprint that deploys a single Nginx container to a target cloud:
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers: []  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+                id: 206  
+            volumes:  
+              - rootVolume: true  
+                name: root  
+                size: 1  
+            backup:  
+              createBackup: false  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              id: 68  
+              code: container-128  
+            ports:  
+              - name: HTTP  
+                port: 80  
+                lb: HTTP
+```
+```
+
+Theres some useful things to look at in the above docker example. One is there are different objects based on the different available configuration options for the target provision type. These options are actually data driven and can be extracted from the Inputs api in the morpheus api doc. That is a useful resource to look at while building morpheus blueprints or by using the morpheus-cli which provides prompts for helping build custom morpheus app blueprints.
+
+![../../../_images/templates_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-06C21D16-B31C-492D-9170-EAC44622138F-high.png)
+
+## Creating Morpheus App Blueprints
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Enter a NAME for the Blueprint and select NEXT
+4. Optionally add a Description, Category, and Image for the Blueprint.
+
+### Add Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + to add a Tier
+2. Select or enter a Tier Name.
+3. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+
+### Add Instances to Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in a Tier to add an Instance
+2. Select an Instance Type
+3. Optionally add a name for the Instance. Instances with blank names will automatically be named based off the App name.
+
+#### Results
+
+TIP
+
+You can use the variable `${app.name}` in your instance naming convention to reference the name of the application you’re deploying.
+
+### Add Configurations to Instances
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in an Instance to add a Configuration
+2. Select at least one option from Group, Cloud or Environment.
+3. Select `ADD CONFIG` to create the configuration
+4. Populate the Configuration 
+
+   - Configurations can be fully partially or populated
+   - Fields can be locked or hidden by selecting the Lock icon next to the Field. Locking prevents the field from being editable when provisioning an App using the Blueprint while hidden fields are not revealed to the user at all
+   - ALLOW EXISTING INSTANCE will allow users to add existing Instances to the App when using the blueprint
+
+### Save
+
+Once all desired Tiers, Instances and Configurations are added, select Save. The Blueprint will be created, can be edited after saving, and will available in the Apps section for provisioning.
+
+NOTE
+
+Blueprints are not provisioned when created. To provision a Blueprint, use Provisioning > Apps.
+
+### RAW
+
+#### About this task
+
+Blueprints can be create, edited or Exported in the RAW section when creating or editing a blueprint.
+
+![../../../_images/templates_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2F7949E9-D5DB-4089-970D-854F88DA140D-high.png)
+
+To Export a Blueprint as JSON or YAML:
+
+#### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Edit an existing App by clicking on the pencil icon
+3. On the Edit Blueprint modal, select the Raw tab
+4. Select YAML or JSON from the dropdown in the top right
+5. Click the Export button
+6. Select the configurations to include in the export by selecting or deselecting configurations as needed. Selected configurations will be highlighted
+7. Click the DOWNLOAD CONFIGURATION button
+8. The Blueprint export file will be downloaded to your computer as `{app_name}-config.json or {app_name}-config.yaml`
+
+## Provisioning
+
+To provision a Blueprint, navigate to Provisioning > Apps and select the Blueprint when creating an App. See the [App section](https://docs.morpheusdata.com/en/latest/provisioning/apps/apps.html) of HPE Morpheus Enterprise docs for more on provisioning Apps.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
new file mode 100644
index 0000000..8cd3b68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+  "title": "Costing: User Costing",
+  "ordinal": 61,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: User Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
new file mode 100644
index 0000000..2862449
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
@@ -0,0 +1,31 @@
+# Costing: User Costing
+
+![../_images/4usercosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-19673F2B-9D42-4067-BC83-078B0046D28B-high.png)
+
+The User Costing dashboard allows administrators to analyze costs for a group of Users that meet specific filters. Once the group is selected, total costs by User for the current month and projected totals are displayed. Administrators can identify their costliest Users and anticipate the total cost by User for budgeting purposes.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- User (all matched by search)
+- Group
+- Cloud
+- Period (Current month, last three months, last six months, or last 12 months)
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Users that meet set filters:
+
+- **USERS:** The total number of Users that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Users meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Users meeting dashboard filters
+
+## User List
+
+Each User that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual User:
+
+- **USERNAME:** The username given to the User in HPE Morpheus Enterprise at the time of creation
+- **MONTH TO DATE:** The current month-to-date spend for the individual User listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual User listed
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json b/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
new file mode 100644
index 0000000..9c12a3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+  "title": "Docker Registry",
+  "ordinal": 479,
+  "parent_title": "Containers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Registry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md b/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
new file mode 100644
index 0000000..6acbe73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
@@ -0,0 +1,39 @@
+# Docker Registry
+
+## Overview
+
+Without any additional configuration, HPE Morpheus Enterprise can provision images from Docker’s public hub at <https://hub.docker.com/> using their public API.
+
+However, many organizations maintain private Docker registries for security measures. Additional public and private Docker registries can be added to Morpheus.
+
+## Adding a Docker Registry Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click “New Integration”
+3. Select the Docker Repository Type
+4. Add the following: 
+
+   Name
+   :   Name for the Registry in HPE Morpheus Enterprise
+
+   Repository url
+   :   Docker Registry url or IP address
+
+   Username
+   :   Username if private registry
+
+   Password
+   :   Password if private registry
+5. Save Changes
+
+### Results
+
+NOTE
+
+You must either have signed certificates for your registry or configure your docker host(s) to accept insecure registries
+
+## Provisioning an Instance from Docker Registry
+
+Docker images from the Integrated Registry can be provisioned using the generic Docker Instance Type, or by adding images to Node Types for custom Library Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json b/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
new file mode 100644
index 0000000..6a5ad19
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+  "title": "Tenant Users",
+  "ordinal": 278,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md b/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
new file mode 100644
index 0000000..6a0b90d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
@@ -0,0 +1,86 @@
+# Tenant Users
+
+The Tenant View displays a list of users belonging to the Tenant and their Name, Username, Email, and Role.
+
+From this page: Create, Edit, and Delete users within the Tenant.
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Create Tenant User
+
+### About this task
+
+To create a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name on the row of the Tenant where the user will be added.
+4. Click + ADD USER
+5. From the New User wizard, input the fields below: 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email address
+   - Role (to be inherited by the user)
+   - Password
+   - Any default Windows or Linux credentials
+
+### Results
+
+Click SAVE CHANGES
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Edit a Tenant User
+
+### About this task
+
+To edit a User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the specific Tenant name from the row of available Tenants.
+4. Click the Edit pencil icon for your selected Tenant.
+5. Edit User information 
+
+   NOTE
+
+   Name, Username, Passwords and e-mail addresses cannot be edited on Users created from Identity Source Integrations.
+
+### Results
+
+Click SAVE CHANGES
+
+## Delete Tenant User
+
+### About this task
+
+To delete a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name from the row for the Tenant containing the user.
+4. Click the Delete trashcan icon of the row of the user to delete.
+5. Confirm
+
+## Subtenant User Login
+
+Child Tenant Users can have the same Username as the User on the parent Tenant or any other Tenant. Subtenant Users will now have to login using the subdomain prefix.
+
+IMPORTANT
+
+Subtenant users will no longer be able to login from the main login page without specifying their subdomain.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json b/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
new file mode 100644
index 0000000..6add0ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+  "title": "Persona Access",
+  "ordinal": 343,
+  "parent_title": "Personas",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html",
+  "topic_cluster": {
+    "clustering_title": "Persona Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md b/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
new file mode 100644
index 0000000..19ec4cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
@@ -0,0 +1,30 @@
+# Persona Access
+
+## Configuring Persona Access
+
+### About this task
+
+Access to Personas is controlled by a user’s Role. Additionally, Persona access can be configured on the Tenant Role to set maximum Persona access for any user in the Tenant. By default, new Roles and Roles that existed prior to the creation of Personas will only have access to the Standard Persona. If desired, new Roles can be configured to have access to one or both Personas and existing Roles can be edited in the same way.
+
+TIP
+
+It’s recommended to set access to all Personas to “None” if you intend not to use Personas at all. Under this configuration, HPE Morpheus Enterprise gives access only to the Standard Persona and hides the Persona selection menu from the user. New Roles and Roles that existed prior to creation of the Personas feature are pre-configured in this way.
+
+Edit Persona access on a Role with the following steps:
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Select the desired Role to edit
+3. Go to the Personas tab
+4. Allow access to one or both Personas as needed, changes are saved automatically
+
+### Results
+
+![../_images/1rolePerms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B7E6E923-4BC1-45EC-8A41-9862C023911F-high.png)
+
+## Accessing Alternate Personas
+
+Switch Personas by clicking on your name in the upper-right corner of the application window. If your Role gives you access to any additional Personas, they will be listed here.
+
+![../_images/2switchPersona2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-79453DE4-A795-4FEB-9670-0F214A7163FF-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json b/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
new file mode 100644
index 0000000..29d3e8e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+  "title": "Troubleshooting",
+  "ordinal": 249,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md b/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
new file mode 100644
index 0000000..dcadadf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
@@ -0,0 +1,9 @@
+# Troubleshooting
+
+If you do not get the Morpheus boot menu, there are a few things to check:
+
+- First, make sure the filename is correct. It must be `pxelinux.0`
+- Next, check the TFTP server is responding by using a TFTP client to get the `pxelinux.0` file from the HPE Morpheus Enterprise server using the same host name as you have configured in the DHCP server configuration. Do this test on a machine on the same network as the machines you are trying to boot using PXE
+- Leave the port number as 69 (the default) as this will also check the redirect is working
+- If a GET call on the default port does not work, and the client allows (most do) try using port 6969. If this works, then the redirect is wrong
+- If it will not work on either, check you can access the HPE Morpheus Enterprise server from the network you are on and also check there are no firewalls between the test network and the HPE Morpheus Enterprise Server
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json b/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
new file mode 100644
index 0000000..6d877be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+  "title": "Logs",
+  "ordinal": 256,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md b/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
new file mode 100644
index 0000000..108a442
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
@@ -0,0 +1,176 @@
+# Logs
+
+## Overview
+
+The logging architecture backing HPE Morpheus Enterprise uses the latest and greatest technologies and standards to be able to service large amounts of log traffic as well as facilitate easy viewing. Utilizing Opensearch behind the scenes and buffered log transmission protocols HPE Morpheus Enterprise provides a highly efficient and highly scalable solution for capturing log data from anything provisioned via the system. By utilizing common formats (syslog) it is also very easy to forward logs to external third party log services.
+
+### Configuration
+
+Logging configuration can be setup in the Administration > Settings > Logs section. There are useful settings here, including customizing the retainment policy (7 days by default). This could be expanded to years for PCI compliance purposes or other requirements an organization might have.
+
+NOTE
+
+When increasing the retainment policy of the logging system, it may be necessary to scale out the Opensearch cluster. Please refer to the relevant information with regards to scaling Opensearch and advanced installation options for externalizing the Opensearch cluster.
+
+The Log administration section also provides options for setting custom syslog forward rules. These rules are applied on each individual host therefore keeping the HPE Morpheus Enterprise appliance itself out of the data plane. For information on different syslog formatting rules please refer to the [rsyslog](http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/) documentation.
+
+### Usage
+
+HPE Morpheus Enterprise automatically sets up and configures logging for all of the standard catalog items provisioned through morpheus. This includes both Docker containers as well as virtual machines. Simply view instance-specific logs in instance detail via the “Logs” tab.
+
+There are several filtering capabilities built into the logging UI with more being added continually. Easily toggle log level filters from the dropdown or change the date range filter using the handy date filter component. A chart is also displayed above logs representing the log counts by level over the selected time range (default last 24 hours). A handy pattern search is also available with some rather capable features based on Lucene search syntax.
+
+TIP
+
+It may be useful to review the [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html) for powerful use cases.
+
+There are several other places logs can be viewed. Not only can they be viewed across an application in app detail but also across all instances in the account. The main level `Logs` section provides an ability to query all logs produced by the system. It is also possible to view host-specific logs on a docker host by viewing the host detail page via `Infrastructure`.
+
+NOTE
+
+New features are on the roadmap for the main logs section including saved searches, and handy charting dashboards for garnering insights out of log data.
+
+## Exporting Logs
+
+### Log Settings
+
+There are three main log areas in HPE Morpheus Enterprise
+
+- Agent Logs
+- HPE Morpheus Enterprise Server Logs
+- Activity / Audit Logs
+
+## Agent Logs
+
+When Instances are deployed through HPE Morpheus Enterprise, the installed Agent captures application logs and sends them back to the HPE Morpheus Enterprise server.
+
+In most cases, the built-in HPE Morpheus Enterprise logging features are sufficient for tracking and reviewing Agent logs. However, if needed, HPE Morpheus Enterprise supports integration with advanced logging systems. See the [log integration section](https://docs.morpheusdata.com/en/latest/logs/logging.html#integrations) above for more information.
+
+## HPE Morpheus Enterprise Server Logs
+
+### About this task
+
+The main HPE Morpheus Enterprise application log is in `/var/log/morpheus/morpheus-ui` and the latest log file is named current. This log is archived every 24hrs. There are a number of other log files for the individual infrastructure components as well.
+
+If you wish to export these to an external syslog platform, do the following:
+
+### Procedure
+
+1. Once you have configured your syslog destination (edit rsyslog.conf), create a morpheus-syslog.conf file in the `/etc/rsyslog.d` directory and add the following entries 
+
+   ```
+   ```
+   module(load="imfile" PollingInterval="10")  
+   input(type="imfile" File="/var/log/morpheus/morpheus-ui/current" Tag="morpheus-ui" ReadMode="2" Severity="info" StateFile="morpheus-ui")  
+   input(type="imfile" File="/var/log/morpheus/check-server/current" Tag="check-server" ReadMode="2" Severity="info" StateFile="check-server")  
+   input(type="imfile" File="/var/log/morpheus/guacd/current" Tag="guacd" ReadMode="2" Severity="info" StateFile="guacd")  
+   input(type="imfile" File="/var/log/morpheus/opensearch/current" Tag="opensearch" ReadMode="2" Severity="info" StateFile="opensearch")  
+   input(type="imfile" File="/var/log/morpheus/mysql/current" Tag="mysql" ReadMode="2" Severity="info" StateFile="mysql")  
+   input(type="imfile" File="/var/log/morpheus/nginx/current" Tag="nginx" ReadMode="2" Severity="info" StateFile="nginx")  
+   input(type="imfile" File="/var/log/morpheus/rabbitmq/current" Tag="rabbitmq" ReadMode="2" Severity="info" StateFile="rabbitmq")
+   ```
+   ```
+2. Restart rsyslog
+
+### Results
+
+The log files will now be forwarded to the destination you have defined.
+
+This configuration is valid for an ‘all-in-one’ HPE Morpheus Enterprise server. If the infrastructure components are running on separate servers /clusters, you will need to create the relevant redirects for the logs on those boxes.
+
+## Activity Log
+
+### About this task
+
+The final log type that may require export is the HPE Morpheus Enterprise Activity log. This tracks system changes made by users, for example create and delete instances etc.
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, you should edit the following file: `logback.xml` located at `/opt/morpheus/conf/logback.xml`.
+2. Add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+3. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+4. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+5. Once the service has stopped enter the following at the shell prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+6. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
+
+## morpheus-ssl nginx logs
+
+NOTE
+
+Morpheus does not put a logrotate in for Morpheus-ssl access logs
+
+svlogd will only rotate the current file, nginx is setup to write the access logs to separate files and not stdout.
+
+Implementation of a log rotate is left up to up to end users for files outside of the services. This is done in case end users have a log management solution.
+
+Below is what a suggested configuration looks like for the file `/etc/logrotate.d/morpheus-nginx`:
+
+```
+```
+/var/log/morpheus/nginx/morpheus*access.log {  
+        daily  
+        rotate 14  
+        compress  
+        delaycompress  
+        missingok  
+        notifempty  
+        create 644 morpheus-app morpheus-app  
+        postrotate  
+                [ ! -f /var/run/morpheus/nginx/nginx.pid ] || kill -USR1 `cat /var/run/morpheus/nginx/nginx.pid`  
+        endscript  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json b/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
new file mode 100644
index 0000000..7dadd86
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+  "title": "Getting started with Morpheus and AWS",
+  "ordinal": 361,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with Morpheus and AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md b/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
new file mode 100644
index 0000000..0d6056f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
@@ -0,0 +1,212 @@
+# Getting started with Morpheus and AWS
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with AWS. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get Morpheus installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, Morpheus needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, Morpheus will automatically set up a lab license on installation. A lab license is a time-unlimited license for Morpheus that limits you to 25 managed and discovered workloads. If you have a timed trial or a paid license, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in Morpheus define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on Morpheus groups is available in the [Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html#GUID-E0307462-456B-4D4E-82E3-0BD04A42F824) section. A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling Morpheus through Morpheus API or Morpheus CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![../../_images/1groupConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in Morpheus consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with AWS.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of Morpheus but soon we will see our integrated AWS cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AMAZON” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, give your cloud a “NAME”. Select your Amazon region and enter your credentials in the “ACCESS KEY” and “SECRET KEY” fields. We can also set a number of advanced options here that may be relevant to your AWS use case.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, Morpheus will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first AWS cloud, we can stop for a moment to review what Morpheus gives us from the cloud detail page. We can see that Morpheus gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our AWS cloud configured, Morpheus will automatically sync in available resource pools and data stores.
+
+Resource pools, once Morpheus has had time to ingest them, will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in Amazon. For example, we can restrict access to a specific resource pool within Morpheus completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within Morpheus.
+
+![../../_images/1resourcePools.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5EDE80B8-04C2-42AD-95C9-11EA1E8E8331-high.png)
+
+Often our clients will want to make specific blocks of resources available to certain groups. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![../../_images/2editResourceGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3D217ABE-3194-420B-A2D6-DD5262F136EC-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into Morpheus. Depending on the number of clouds Morpheus has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![../../_images/1networksSection.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html) section of Morpheus Docs.
+
+![../../_images/2addIPAM.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![../../_images/3addIPPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within the AWS cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  NETWORKS tab. Just as with resource pools, we have the ability to make certain networks inactive in Morpheus, or scope them to be usable only for certain groups or tenants.
+
+![../../_images/1cloudNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1A883CF2-9673-460A-B1AC-A1CB858CD226-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, Morpheus comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with the images included in Morpheus by default but have guides in Morpheus Docs for [Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html#GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798) which are consumable in Morpheus.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our AWS cloud.
+
+Navigate to |ProIns|. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/1createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the AWS cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, Morpheus will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+- **SECURITY GROUPS**
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of Morpheus docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends selections made when provisioning the instance. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, Morpheus allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click +ADD.
+
+![../../_images/1addNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: Amazon
+- **AMI IMAGE**: Morpheus Redis 3.0 on Ubuntu 14.04.3 v2
+
+![../../_images/2nodeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B58E92CB-BAAC-4B7B-A743-4E04B13DC487-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![../../_images/3addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![../../_images/4instanceTypeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![../../_images/5openInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: Amazon
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to |ProIns| and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+As before when we manually provisioned an instance, Morpheus will now begin to spin up the new VM. Once the privisioning process has completed, open the instance detail page in Morpheus and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+## Automation and Configuration Management
+
+Morpheus automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the Morpheus Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in [Automation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html). Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![../../_images/1newIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+ NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![../../_images/2configureIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![../../_images/3taskConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![../../_images/4executeTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![../../_images/5newWorkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![../../_images/6automationInProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see Morpheus executing the tasks that were contained in our workflow.
+
+This is just one example of using Morpheus to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) guide in Morpheus docs.
+
+## Conclusion
+
+At this point you should be up and running in Morpheus, ready to consume AWS. This guide only scratches the surface, there is a lot more to see and do in Morpheus. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json b/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
new file mode 100644
index 0000000..504d84d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+  "title": "Morpheus DB Migration",
+  "ordinal": 26,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus DB Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md b/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
new file mode 100644
index 0000000..2d8f77c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
@@ -0,0 +1,80 @@
+# Morpheus DB Migration
+
+If your new installation is part of a migration or you need to move the data from your original Morpheus database, this is easily accomplished by using a stateful dump.
+
+To begin this, stop the Morpheus UI on your original Morpheus server:
+
+```
+```
+[root@app-server-old ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Once this is done you can safely export. To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file:
+
+```
+```
+[root@app-server-old ~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---------------this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Take note of the first `morpheus_password` as it will be used to invoke a dump. Morpheus provides embedded binaries for this task. Invoke it via the embedded path and specify the host. In this example we are using the morpheus database on the MySQL listening on localhost. Enter the password copied from the previous step when prompted:
+
+```
+```
+[root@app-server-old ~] /opt/morpheus/embedded/mysql/bin/mysqldump -u morpheus -h 127.0.0.1 morpheus -p > /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+This file needs to be pushed to the new Morpheus Installation’s backend. Depending on the GRANTS in the new MySQL backend, this will likely require moving this file to one of the new Morpheus frontend servers.
+
+Once the file is in place it can be imported into the backend. Begin by ensuring the Morpheus UI service is stopped on all of the application servers:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Then you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server-new ~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The data from the old appliance is now replicated on the new appliance. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl start morpheus-ui
+```
+```
+
+With the migration complete, you will also need to update the stored password for the appliance backup job as the destination appliance will have a different dynamically-generated MySQL password. We can update that password value by altering the backup directly in the HPE Morpheus Enterprise database.
+
+```
+```
+select * from backup where `name` ='Morpheus Appliance';  
+UPDATE `morpheus`.`backup` SET `ssh_host` = '127.0.0.1', `target_password` = 'its-a-secret' WHERE `id` = '1';
+```
+```
+
+IMPORTANT
+
+After the migration it is important to reset the unique ID of the Morpheus Appliance. This will ensure your new installation will communicate correctly with the Morpheus Hub.
+
+The final step is to generate a new unique ID for the Morpheus Appliance. Firstly run the following SQL command on the database for the new installation:
+
+```
+```
+UPDATE appliance_instance SET hub_unique_id = NULL;
+```
+```
+
+Secondly, re-apply your Morpheus license key within the Morpheus UI via the “Upgrade A License” action within Administration -> Settings -> License
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json b/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
new file mode 100644
index 0000000..4be0915
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 191,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md b/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
new file mode 100644
index 0000000..e3f20db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
@@ -0,0 +1,13 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HPE Morpheus Enterprise HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the HVM cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give HPE Morpheus Enterprise access to NFS.
+
+Start by navigating to the Storage tab of the HVM cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in HPE Morpheus Enterprise and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in HPE Morpheus Enterprise. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
+
+![../../_images/addNfsDatastore.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-90F23A24-CA56-4100-94CD-13EA1247EBD5-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json b/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
new file mode 100644
index 0000000..3e34281
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+  "title": "Post-Provisioning",
+  "ordinal": 418,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html",
+  "topic_cluster": {
+    "clustering_title": "Post-Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md b/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
new file mode 100644
index 0000000..e08eb94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
@@ -0,0 +1,20 @@
+# Post-Provisioning
+
+After provisioning the instance:
+
+- The new instance appears under Provisioning > Instances.
+
+    
+  ![Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EB7CC689-A95F-43C0-8F65-D43E35C97D7B-high.png)
+- To monitor provisioning progress, select the instance from the list.   
+  ![Summary](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AA864681-E71F-4DAA-BC8C-9594A4F366CC-high.png)
+
+  Once provisioning completes successfully, review the tabs as required.
+- To access the instance console, click the Console tab
+- After successful provisioning, verify that the instance and its corresponding bare metal host are listed in:
+  - Under Provisioning > Instances.  
+    ![Provisioning Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-49E0E201-4ED4-41C1-A8F4-D31630076D56-high.png)
+  - Under Infrastructure > Bare Metal.   
+    ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1647C09E-6E21-4A92-A088-1AC8E3A64B52-high.png)
+  - Go to the Instances page to view the instance Status, Health, CPU, Memory, and Storage details.   
+    ![Details](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-55629E53-1010-42C1-BE7F-DCF13B743BBE-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json b/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
new file mode 100644
index 0000000..e63b8d1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+  "title": "Base Cluster Details",
+  "ordinal": 178,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md b/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
new file mode 100644
index 0000000..a1217a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the HVM cluster solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, a host must be a pre-existing Ubuntu 22.04 box with environment and host system requirements contained in this section. HPE Morpheus Enterprise handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to HPE Morpheus Enterprise are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json b/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
new file mode 100644
index 0000000..c2e325e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+  "title": "Usage",
+  "ordinal": 76,
+  "parent_title": "Costing",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md b/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
new file mode 100644
index 0000000..a9581f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
@@ -0,0 +1,35 @@
+# Usage
+
+The Operations  >  Costing  >  Usage section shows billing information for Instances and hosts that have pricing configured on their Service Plan.
+
+IMPORTANT
+
+Pricing must be enabled in Administration > Settings > Provisioning and Service Plans configured with price sets in Administration > Plans & Pricing for pricing to show in the Usage section.
+
+## View Usage
+
+All Instances, discovered resources, virtual images, snapshots are listed by default, with the most recent usage information showing first. When additional details are available, usage records will display a small arrow on the left side of the row. Click this arrow to expand the details for that usage record. Details can include more granular cost breakdowns, such as specific CPU, memory, and/or storage costs for containers (Instances).
+
+Usage records can be filtered by Cloud, type and date:
+
+Cloud
+:   Default view is for all Clouds. Select a Cloud to show Instance, host and other usage for only one Cloud.
+
+Date
+:   Default view shows most current Usage. Select the Date filter to scope to a different date range.
+
+Type
+:   All usage record types are shown by default, select a specific type to filter the list to just one
+
+Example:
+:   Below is an example of a discovered instance from AWS, which shows different usage periods and the pricing that would be related. In this case, the compute and storage are used to calculate the Usage Price when the instance is **Running** but only the storage when the instance is **Stopped**:
+
+    ![../_images/usage_example.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E455650E-5DD7-40E6-BF40-5449281F27C2-high.png)
+
+## API & CLI
+
+Usage information can also be extracted via the HPE Morpheus Enterprise API and CLI, including the ability to extract usage per Tenant.
+
+NOTE
+
+Appropriate Role permissions for Operations: Usage are required to view the Usage section.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json b/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
new file mode 100644
index 0000000..1ab8811
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+  "title": "Morpheus Agent",
+  "ordinal": 42,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md b/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
new file mode 100644
index 0000000..4f746ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
@@ -0,0 +1,17 @@
+# Morpheus Agent
+
+- [Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)
+- [Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)
+- [Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)
+- [CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html)**
+- **[HPE Morpheus Enterprise Agent Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html)**
+- **[Morpheus Agent OS Support](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html)**
+- **[Agent Installation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html)**
+- **[Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)**
+- **[Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)**
+- **[Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)**
+- **[CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json b/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
new file mode 100644
index 0000000..d4ada4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+  "title": "Personas",
+  "ordinal": 340,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html",
+  "topic_cluster": {
+    "clustering_title": "Personas",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md b/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
new file mode 100644
index 0000000..771e93f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
@@ -0,0 +1,11 @@
+# Personas
+
+Personas are alternate views in HPE Morpheus Enterprise UI. A user’s access to the various Personas is controlled by Role permissions. At present, there are four Persona types: Standard, API, Service Catalog, and Virtual Desktop. The Standard Persona is the typical full HPE Morpheus Enterprise UI experience. The Service Catalog Persona is a simplified view where users are presented with pre-configured Instance types, Blueprints, and Workflows to choose from based on their Role. The Virtual Desktop Persona allows administrators to grant user access to remote workstations and applications. The API persona allows almost no access to HPE Morpheus Enterprise UI, it offers API access only for service accounts.
+
+The rest of this section goes through the use of the Service Catalog Persona and Virtual Desktop Persona in greater detail, including how administrators can curate catalog item and virtual desktop selections for their users.
+
+**Subtopics**  
+
+- **[Service Catalog Persona](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html)**
+- **[Virtual Desktop Persona](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html)**
+- **[Persona Access](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..29f92f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 222,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..dfd4c5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,116 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+## Overview
+
+The Domains section is for creating and managing domains for use in HPE Morpheus Enterprise. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
+
+## Adding Domains
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in HPE Morpheus Enterprise
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across HPE Morpheus Enterprise. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. HPE Morpheus Enterprise will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+### Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
+
+## Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group and Tenant access permissions.
+
+NOTE
+
+Only resources assigned to the Master Tenant can be set as Publicly visible. If the Tenant assigned is not the Master Tenant, visibility will automatically change to private. Additionally, only Master Tenant users can set visibility for domains. Domains originating in a subtenant will always be private to that subtenant.
+
+### Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
+
+### Tenant Permissions
+
+When set to public, all Tenants will have visibility into the domain and can join their Instances to the domain. When set to private, users can select specific Tenants which should have access to the domain.
+
+## Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from HPE Morpheus Enterprise by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
+
+## Setting the default domain on a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Setting the default domain on a Network
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Selecting a Domain while provisioning an instance
+
+### Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..515311a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 193,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..51a92dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json b/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
new file mode 100644
index 0000000..bf2d102
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+  "title": "Compute",
+  "ordinal": 450,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md b/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
new file mode 100644
index 0000000..2c1b4ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
@@ -0,0 +1,8 @@
+# Compute
+
+The topic describes troubleshooting procedures for compute.
+
+**Subtopics**  
+
+- **[OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json b/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
new file mode 100644
index 0000000..fa8addd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+  "title": "Add HaProxy container load balancer",
+  "ordinal": 501,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html",
+  "topic_cluster": {
+    "clustering_title": "Add HaProxy container load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md b/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
new file mode 100644
index 0000000..6c232f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
@@ -0,0 +1,33 @@
+# Add HaProxy container load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **HaProxy Container**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Container LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-56213FAB-222F-45BB-A5DD-748546C526A1-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   RESOURCE POOL
+   :   From the drop-down list, select the resource pool.
+
+   HOST
+   :   From the drop-down list, select the host.
+
+   PLAN
+   :   From the drop-down list, select the plan (size of HaProxy container to be provisioned).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json b/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
new file mode 100644
index 0000000..94ff951
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+  "title": "Tenancy",
+  "ordinal": 373,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html",
+  "topic_cluster": {
+    "clustering_title": "Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md b/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
new file mode 100644
index 0000000..ca976a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
@@ -0,0 +1,268 @@
+# Tenancy
+
+HPE Morpheus Enterprise appliances may be multi-tenanted, that is, they may contain multiple isolated environments known as Tenants. Successfully building a multi-Tenanted HPE Morpheus Enterprise environment requires creating and pulling together multiple constructs. This guide aims to describe the pieces needed to create functioning Tenants with Users, identity integrations, Roles, Groups, and whitelabeling. We will also share a Cloud and Library item from the Master Tenant which is provisionable from the new Subtenant.
+
+On installation, a single Tenant is created. This Tenant is often referred to as the Master Tenant and has some special properties that additional created Tenants (known as Subtenants) do not have. Tenants manage their own workloads, may have their own custom whitelabeling, and also have their own users and integrations. The Master Tenant may (or may not) share down integrations, Library items, Roles, and more but Subtenants are fully isolated from each other.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The Master Tenant creates and controls all Subtenants.
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants
+- Subtenants cannot share their resources with other Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant
+
+## Tenant Roles
+
+### About this task
+
+Before even creating the Tenant, we need to understand what a Tenant Role is and ensure that a Tenant Role with correct rights permissions exists. Tenant Roles set the maximum feature permissions levels for any User in the Subtenant and also give (or revoke) access to Clouds, Library items, Tasks, Workflows, and other things integrated or created in and shared from the Master Tenant. Only Master Tenant administrators have the ability to create Tenant Roles.
+
+NOTE
+
+User Roles within the Tenant may be created with lesser permissions than the Tenant Role allows but we will discuss User Roles further in a later section.
+
+In a new environment, the only Tenant Role will be the included “Tenant Admin” Role but this Role is not editable. It’s advisable to create your own Tenant Roles so they may be edited as needed. To get started, we can create a new Tenant Role and copy from the pre-existing “Tenant Admin” Role.
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Click + CREATE ROLE
+3. Set a NAME, TYPE (Tenant Role), and COPY FROM ROLE (Tenant Admin)
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/addTenantRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9D86F36B-590B-424C-A1E6-13B6779D961F-high.png)
+
+Once created, click into the new Role and edit feature permissions if you wish. Remember the Tenant Role is setting the maximum available Role permissions for each feature that Users within the Tenant can have. We’ll worry about scoping resources to the Subtenant (such as Clouds) in a later section.
+
+With a Tenant Role created, we can move on to creating the Tenant itself.
+
+## Create a Tenant
+
+### About this task
+
+We’ll now create a Tenant and apply the Tenant Role we’ve just created.
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Click CREATE TENANT
+3. Name your Tenant and set the Tenant Role in the BASE ROLE field
+4. Click SAVE CHANGES
+
+### Results
+
+The NAME and BASE ROLE are the most important settings and the only two required. See the Tenants section of HPE Morpheus Enterprise documentation to learn more about other settings which may be applied when adding or editing Tenants.
+
+![../../_images/addTenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-702D1FEA-8C54-4BBA-AEC7-7C1575EC9D28-high.png)
+
+With the Tenant created, the rest of the guide will pertain to configuring the new Tenant and demonstrating how to provision new workloads using resources shared down from the Master Tenant.
+
+## Users and User Roles
+
+### About this task
+
+In the prior steps we’ve created a new Tenant and associated our created Tenant Role with it. If you click into the new Tenant you’ll notice that there are currently no users so the new Tenant is still unusable. We could go ahead and create a new User but if this is a new HPE Morpheus Enterprise environment, the new Tenant will not have any User Roles to apply to the new User we wish to create.
+
+To remedy this problem, we can add a “Multi-Tenant User Role” from the Master Tenant. This is essentially a Role Template from which a Role is created and seeded down to each Tenant. Only Master Tenant administrators can create Multi-Tenant User Roles. After creation, edits can be made and permission changes will be filtered down to the child Role that exists within each Subtenant. However, it’s important to know that should the child Role ever be edited in the Subtenant, the link back to the Multi-Tenant User Role will be broken and it will become like any other User Role created in the Subtenant. To prevent this situation, Master Tenant administrators can set a “MULTITENANT LOCKED” option to restrict such edits in the Subtenant.
+
+New Multi-Tenant User Roles are created in Administration > Roles:
+
+### Procedure
+
+1. Click + CREATE ROLE
+2. Provide a NAME, TYPE (User Role), COPY FROM ROLE (if desired)
+3. Mark the boxes to set MULTITENANT ROLE and MULTITENANT LOCKED
+4. Click SAVE CHANGES
+
+### Results
+
+After saving the Role, it will appear in the Master Tenant and will also be seeded down to the Tenant we’ve already created since it is a Multi-Tenant User Role. We’ve also locked the Role so that Subtenant users cannot edit it and thus unlink it from future permissions edits made in the Master Tenant. Keep in mind that no matter what permissions we set, Users in the Subtenant will not be able to exceed permissions set on the Tenant Role as discussed in a prior section. If desired, you can click into this User Role now and edit its permissions to suit your needs.
+
+![../../_images/addUserRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-870C9D97-516B-4D34-8339-550FCB2EA699-high.png)
+
+At this point we’re ready to add a User which will make the Tenant usable. We can create one in the new Tenant by navigating to the Tenant list page (Administration > Tenants) and selecting the Tenant. There are a number of configurations to make when creating a user but when selecting the User’s Role you should see the previously-created Multi-Tenant User Role.
+
+![../../_images/addUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E03CE619-CA56-4601-95F4-61D3F0A0EE7B-high.png)
+
+After saving the new User, we can make the first test of the new Tenant by impersonating the User and entering the Tenant. In the list of Users on the Tenant detail page, click the gear (⚙) icon at the end of the User’s row and select “Impersonate.” You should end up inside the new Tenant operating as the new user. This can be confirmed by making note of the updated name given in the upper-right portion of the application window. To quit impersonating, click on the name and select “Quit Impersonating.”
+
+At this point we’ve created a User manually but it’s important to point out that HPE Morpheus Enterprise can also use an existing identity integration, such as Microsoft Active Directory, to manage User creation and Role assignment. Expand the section below to see an example use case or continue on if you’d prefer to administer your Users directly in HPE Morpheus Enterprise. The complete integration guide elsewhere in HPE Morpheus Enterprise docs also includes common Active Directory troubleshooting steps should those be needed.
+
+Microsoft Active Directory Example
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in‐built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following:
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES.
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Whitelabeling
+
+HPE Morpheus Enterprise allows each Tenant to be customized with its own look and feel through whitelabeling features. Your organization can replace the stock HPE Morpheus Enterprise logo and color scheme with your own logos and colors. Whitelabel settings are held in Administration > Settings > Whitelabel and are mostly self-explanatory. Upload logos and set custom hexadecimal colors in each field. When done, be sure to set the “Enable Whitelabel” configuration and click SAVE all the way at the bottom of the page. If needed, review a more detailed explanation of each [whitelabel setting](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#whitelabel) in HPE Morpheus Enterprise documentation.
+
+![../../_images/whitelabelSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-458BDDBC-723A-4A05-9745-372AC60C08DD-high.png)
+
+## Scoping Clouds to Tenants
+
+### About this task
+
+With the Tenant now created and seeded with a User and Roles, we’re ready to look at how to set up useful provisioning resources. Of course, Tenants are complete (yet isolated) HPE Morpheus Enterprise environments which can create their own Cloud integrations or utilize integrations with other third party technologies (assuming they haven’t been restricted from doing so by the Tenant Role). However, Master Tenant administrators may also choose to share integrations created in the Master Tenant down to Subtenant users.
+
+Many constructs in HPE Morpheus Enterprise have a “Visibility” attribute when viewed from the Master Tenant. This attribute controls whether the construct is “Private” (in other words reserved for a selected Tenant) or Public (available to all Tenants). In our example, we’re going to expose an Amazon AWS Cloud integrated in the Master Tenant down to our newly-created Subtenant. To set the Cloud visibility, use the following steps:
+
+### Procedure
+
+1. Navigate to the Clouds list page (Infrastructure > Clouds)
+2. Edit the Cloud by clicking the pencil icon (✎) in its row
+3. Toggle the VISIBILITY attribute to “Public”
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/editCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BED65BE1-AF4D-4EC6-9680-03FADB9422C3-high.png)
+
+The Cloud is now exposed to the Subtenant but we also need to expose a Resource Pool (A VPC, in Amazon parlance) for Subtenant users to provision into. We do this from the Cloud detail page (Infrastructure > Clouds) > Click on selected Cloud.
+
+1. Select the Resources subtab
+2. Click ACTIONS next to the selected Resource Pool (VPC)
+3. Click Edit
+4. Expand the “Tenant Permissions” section
+5. Set Visibility to Public (alternatively, you could keep the Private visibility and add the new Tenant in the next field)
+6. Click SAVE CHANGES
+
+![../../_images/addResourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7E26EBB1-E238-4E5A-9BE2-ACEB243DDDE0-high.png)
+
+Repeat the same process for Networks and Security Groups, both of which are contained in the Networks subtab of the Cloud detail page.
+
+## Groups
+
+### About this task
+
+The last thing to take a look at before Library items and provisioning are Groups. Groups define which resources a User can access. Group access is defined by the User Role and many resources have a Group access component which allows administrators to control User access to things like Clouds, Networks, Datastores, Resource Pools, Folders and more.
+
+Groups exist solely within the Tenant that creates them, they cannot be shared down from Master Tenant to Subtenants. In order to create a Group for our new Tenant, impersonate the User we’ve created in previous steps. Once working in the Tenant, use the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Groups
+2. Click + CREATE
+3. Set a NAME for the Group and click SAVE CHANGES
+
+### Results
+
+We’ll now add the shared Cloud to the Group:
+
+1. Click on the name of the Group to access the Group detail page
+2. Click on the Clouds tab
+3. Click + ADD
+4. Use the typeahead field to select the shared Cloud
+5. Click SAVE CHANGES
+
+![../../_images/addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DA5D5406-4991-4E35-B064-4B94E55FE9C3-high.png)
+
+At this point the basic configuration steps are complete and we will attempt a provisioning test using built-in Instance Types which are preinstalled with HPE Morpheus Enterprise.
+
+## Provisioning Test
+
+### About this task
+
+At this point, you can conduct a test by attempting to provision one of the basic Instance Types shipped with HPE Morpheus Enterprise for demonstration purposes. To test, we’ll provision a basic Ubuntu box to our AWS Cloud.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Ubuntu Instance Type
+4. Click NEXT
+5. Select the Group and Cloud noting that only resources shared with the Subtenant are selectable
+6. Name the Instance
+7. Click NEXT
+8. On the CONFIGURE tab, select a Resource Pool, Network, and Security Group once again noting that only resources shared with the Subtenant are selectable
+9. Click NEXT
+10. Click NEXT once again
+11. Click COMPLETE
+
+### Results
+
+![../../_images/createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-96B45365-D416-4CFC-9A46-6ADCC0455916-high.png)
+
+After a minute or two, the Instance should be fully provisioned.
+
+## Exposing Custom Instance Types to Subtenants
+
+Master Tenant administrators can also share custom Library items down to Subtenants. Do do this, navigate to Library > Blueprints and select an Instance Type. Click the pencil (✎) icon in the row for the selected Instance Type to edit it. As we’ve done before, update the VISIBILITY setting to Public. In addition, ensure the User Role for the Subtenant User grants access to the selected Instance Type. Once configurations have been made, conduct a similar test to the previous section. When you attempt to provision a new Instance, the new Instance Type should be selectable and the User should be able to provision the custom Instance Type in the same was as the default Instance Type was provisioned in the previous step.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json b/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
new file mode 100644
index 0000000..27962fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+  "title": "Virtual Desktop Persona",
+  "ordinal": 342,
+  "parent_title": "Personas",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Desktop Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md b/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
new file mode 100644
index 0000000..6344475
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
@@ -0,0 +1,64 @@
+# Virtual Desktop Persona
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json b/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
new file mode 100644
index 0000000..bc23897
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+  "title": "Invoices",
+  "ordinal": 75,
+  "parent_title": "Costing",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html",
+  "topic_cluster": {
+    "clustering_title": "Invoices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md b/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
new file mode 100644
index 0000000..33f9fdb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
@@ -0,0 +1,135 @@
+# Invoices
+
+HPE Morpheus Enterprise offers highly-granular costing data through invoices. Invoice views are highly customizable, allowing for nearly unlimited combinations of output columns and filtering. Invoices are based on monthly periods and allow you to slice costs in a highly granular way, as well as predict final monthly costs before the end of the period. As with other HPE Morpheus Enterprise UI pages that support advanced table customization, these views can be saved to provide easy access to costing views specific to varying business needs. By default, the invoice list page will show the last three months’ invoices across all clouds and invoice types but the list can be modified to target differing time periods or resource groupings. Read on in this section to discover the meaning of various invoice types and how this tool can be used to create targeted costing views.
+
+## Invoices for Public vs On-Prem Clouds
+
+HPE Morpheus Enterprise supports live cost syncing for many public clouds, including all of the most commonly-used public clouds like Amazon AWS, Microsoft Azure, and Google Cloud Platform. For these clouds, costing sync is enabled through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). When live costs are synced from public clouds, invoices will be generated for this activity including month-to-date costs, projected monthly totals, historical cost data, and a lot more which is discussed in the following sections.
+
+Additionally, HPE Morpheus Enterprise has implemented a costing service for on-prem clouds to closely mirror the live costing experience through a public cloud. As with public clouds, this costing service is enabled for on-prem clouds through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). Change the setting to “Sync Costing” and save the changes to the cloud integration. From this point, costs will be aggregated into invoices for on-prem clouds in the same way as public clouds including complete line item listings, current costs for the month, month-end projections, and much more as discussed in the next sections.
+
+## Invoice List Page
+
+The invoices list page shows high-level aggregate data on a group of invoices and allows you to locate a specific invoice for a deeper look. By default, invoices from the last three months across all clouds and types are shown here. Depending on settings, this page can automatically refresh itself so the list of displayed invoices and the aggregate information on them is up to date.
+
+![../_images/1listInvoices.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7D08D7CC-C9FD-4013-9B64-78A4F9C8B639-high.png)
+
+### Aggregated Invoice Data
+
+The following aggregate totals are displayed for all invoices picked up by set filters:
+
+- **Periods:** The total number of months in the period determined by your start and end date filters. If no start and end dates are set, a three month period will be shown. If a one-month period is selected, the name of that month (ex. Aug 2020) is shown
+- **Total Invoices:** The total number of invoices captured by current filters
+- **MTD Cost:** The combined month-to-date cost for all invoices captured by current filters
+- **Total Cost:** The expected total month-end cost for all invoices captured by current filters
+
+## Creating Views
+
+### About this task
+
+Invoice list views are highly-customizable allowing for virtually limitless combinations of output columns and filtering. A common set of output columns is provided in a default view but users can add and remove columns from a large list of data points and even save multiple views for easy access to different data sets. Any of your stored views can be set as the default to be displayed each time the invoices list page is active.
+
+To create a new invoices view:
+
+### Procedure
+
+1. Click the gear icon (⚙)
+2. Click on one or more columns from the “Columns” list to add or remove an output field
+3. Click “+ add view”
+4. Provide a name and a description value for your new view
+5. If desired, mark the box to set the new view as your default view so it appears automatically each time the invoices list page is accessed
+6. Click SAVE
+
+### Results
+
+![../_images/2createViews.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E081EF68-3B0E-4A5A-8CFE-8E8B47D87BAD-high.png)
+
+### Available Output Columns
+
+When creating an invoices view, there are many output columns available to select. Consult the list below for more details on each of the available columns:
+
+#### Available Output Columns: Expand for Complete List
+
+- **Invoice ID:** The unique ID in HPE Morpheus Enterprise for the invoice
+- **Type:** The invoice type; Cloud, Container, Group, Server, Instance, Resource, User, or Volume
+- **Ref ID:** An ID for the reference object tied to the invoice (server, instance, cloud, etc.). Reference IDs are reused across invoice types so invoices referring to identical Ref IDs may not necessarily refer to the same reference object
+- **Reference:** The name of the reference object (server, cloud, user, group, etc.) tied to the invoice
+- **Cloud ID:** The internal ID for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Cloud:** The name for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Instance ID:** The internal ID for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Instance:** The name for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Server ID:** The internal ID for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Server:** The name for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Cluster ID:** The internal ID for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Cluster:** The name for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Plan ID:** The internal ID for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Plan:** The name for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Group ID:** The internal ID for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **Group:** The name for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **User ID:** The internal ID for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **User:** The name for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **Tenant ID:** The internal ID for the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Tenant:** The name of the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Period:** The monthly period during which the invoice was generated
+- **Interval:** The length of the invoice billing period, currently all invoices are generated at a one-month interval
+- **Start Date:** The start date and time for the invoice period, typically the first of the month at midnight
+- **End Date:** The end date and time for the invoice period, typically the last day of the month at midnight
+- **Ref Start:** The date and time the reference object is created or the start of the invoicing period if the reference object existed prior to the start of the invoicing period
+- **Ref End:** The date and time the reference object is decommissioned or the end of the invoicing period if the reference object still existed at the end of the period
+- **Compute Cost:** The actual compute costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Cost:** The actual storage costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Cost:** The actual network costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Cost:** The actual additional costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Cost:** The actual month-to-date costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Cost:** The actual total costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Cost:** Compute costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Cost:** Storage costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Cost:** Network costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Cost:** Additional costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Cost:** Month-to-date costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Cost:** Total costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Compute Price:** The actual compute price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Price:** The actual storage price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Price::** The actual network price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Price:** The actual additional price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Price:** The actual month-to-date price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Price:** The actual total price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Price:** Compute price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Price:** Storage price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Price:** Network price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Price:** Additional price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Price:** Month-to-date price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Price:** Total price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Active:** Indicates whether or not the reference object is currently existing and active
+- **Date Created:** The date and time the invoice is created
+
+## Invoice Types
+
+Invoices can reference any of the HPE Morpheus Enterprise workload element types or resource reference types in the list below. Some invoice types are broader and may account for resource costs calculated in other narrower invoice types. For instance, a container-type invoice returns costs for a single node of an Instance while an Instance-type invoice for the same period may be including costs for that same single node. The invoices list view can be filtered to show just one type or all types. Complete descriptions of each invoice type are included below:
+
+- Cloud: In HPE Morpheus Enterprise, a Cloud is any connection into a public cloud, private cloud, hybrid cloud, or bare metal server
+- Container: A single node of a service, in other words, a single node of a HPE Morpheus Enterprise Instance. This could be a virtual machine or Docker container which is part of a HPE Morpheus Enterprise-managed Instance
+- Group: In HPE Morpheus Enterprise, Groups define which resources a user has access to through their role. Clouds are added to Groups and users access Clouds to which their roles give access
+- Server: A server refers to any individual host, virtual machine, or bare metal server that is inventoried or managed by HPE Morpheus Enterprise. This can include servers which are parts of HPE Morpheus Enterprise-managed Instances or inventoried servers from integrated Clouds
+- Instance: A set of containers or virtual machines which correlate to a single horizontally-scalable entity. This could be a single VM or it could be many VMs operating as a service
+- Resource: Resource-type invoices are generated when HPE Morpheus Enterprise cannot determine that the referenced costs belong to any of the other resource reference types in this list
+- User: User-type invoices aggregate the costs of resources owned by a specific HPE Morpheus Enterprise user during the invoicing period
+- Volume: When possible, costs will be tied to known volumes and a volume-type invoice is generated as a result
+
+## Invoice Detail Page
+
+### Summary
+
+The summary tab of the invoice detail page displays a great deal of reference information about the resource identified by the invoice. This will vary depending on the type of resource. In addition, total and projected costs are displayed along with cost breakdowns for compute, storage, network, and other categories. Month-to-date totals and final month projections are given.
+
+### History
+
+The history tab displays the costs and prices for the associated resource over time. This tab is especially valuable for resources that have existed through at least a few invoicing periods to show changes over time. In addition, cost breakdowns for compute, storage, network, and other categories are shown for each invoicing period. These costs can be displayed visually through graphs.
+
+![../_images/4invoiceHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-66262EA5-76D1-41C6-AE62-C1CF505E9976-high.png)
+
+### Line Items
+
+For supported resource types, HPE Morpheus Enterprise includes a tab to display all costing line items. This provides the user with a complete list of line items that make up the costing totals on the invoice.
+
+![../_images/5invoiceLineItem.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-035126CA-FDE7-492E-842A-094558CB1655-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json b/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
new file mode 100644
index 0000000..2fab0df
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+  "title": "Overview",
+  "ordinal": 247,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md b/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
new file mode 100644
index 0000000..d710e5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise provides a simple-to-use Bare Metal boot capability based on PXE. When a server boots and is redirected to the HPE Morpheus Enterprise server for the installation files, they can be configured to be simply passed an OS or Hypervisor (in which case HPE Morpheus Enterprise will see them as Bare Metal servers with no further detail) or they can be brought on as Virtual Machines or Docker Hosts. Installation of the HPE Morpheus Enterprise Agent can also be done during the initial configuration stage.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json b/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
new file mode 100644
index 0000000..6e94d5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+  "title": "VMware Fusion",
+  "ordinal": 476,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-98351F93-76B4-480B-91F1-58E3E3492651.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Fusion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md b/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
new file mode 100644
index 0000000..e3aba07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
@@ -0,0 +1,152 @@
+# VMware Fusion
+
+## Add a VMware Fusion Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select VMware Fusion, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   VMWARE FUSION HOST
+   :   IP or URL of VMware Fusion Host
+
+   WORKING PATH
+   :   Existing folder HPE Morpheus Enterprise will write to on Host
+
+   USERNAME
+   :   Host Username
+
+   PASSWORD
+   :   Host Password
+
+   BRIDGE NAME
+   :   Will auto-populate upon successful authentication with the Fusion Host (E.X. ‘EN0: ETHERNET’)
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.json b/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.json
new file mode 100644
index 0000000..e7a3cab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+  "title": "Restarting the HPE Morpheus Enterprise Agent",
+  "ordinal": 48,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9B75C475-9243-4444-BF22-C43480298274.html",
+  "topic_cluster": {
+    "clustering_title": "Restarting the HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.md b/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.md
new file mode 100644
index 0000000..73b4ff6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9B75C475-9243-4444-BF22-C43480298274.md
@@ -0,0 +1,15 @@
+# Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+## Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+## Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json b/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
new file mode 100644
index 0000000..ceb77c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+  "title": "Requirements",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md b/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
new file mode 100644
index 0000000..340cf4c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
@@ -0,0 +1,17 @@
+# Requirements
+
+HPE Morpheus Enterprise Software is a software-based appliance installation capable of orchestrating many clouds and hypervisors. Before an installation is started it is important to understand some of the base requirements.
+
+In the simplest configuration HPE Morpheus Enterprise needs one Appliance Server. The Appliance Server, by default, contains all the components necessary to orchestrate both VMs and containers. To get started some base requirements are recommended:
+
+**Subtopics**  
+
+- **[Base Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)**
+- **[Storage Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html)**
+- **[Network Connectivity](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html)**
+- **[Components](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html)**
+- **[SELinux](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html)**
+- **[OpenSearch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html)**
+- **[Supported Locales](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json b/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
new file mode 100644
index 0000000..df6d8cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+  "title": "Upgrades & Maintenance",
+  "ordinal": 19,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrades & Maintenance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md b/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
new file mode 100644
index 0000000..aa377ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
@@ -0,0 +1,9 @@
+# Upgrades & Maintenance
+
+**Subtopics**  
+
+- **[Upgrading](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html)**
+- **[morpheus-ctl tips](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html)**
+- **[Morpheus DB Migration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html)**
+- **[Scaling Morpheus Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html)**
+- **[Morpheus UI war files](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..ef62755
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 330,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..ce3d298
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,38 @@
+# License
+
+## Overview
+
+HPE Morpheus Enterprise requires a valid license for provisioning new Instances, Apps and Hosts, and converting existing Instances and Hosts to managed. Licenses can be applied and updated in this section, and the current license status can be checked.
+
+NOTE
+
+HPE Morpheus Enterprise is licensed for a certain number of concurrent workload elements (WLEs) that may be managed or inventoried at any one time. See our [Knowledge Base](https://support.morpheusdata.com/s/article/What-is-a-Workload-Element-or-WE-for-purposes-of-Morpheus-licensing?language=en_US) for specific information on the types of WLEs that count against HPE Morpheus Enterprise licensing.
+
+## Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
+
+## Upgrade License Key
+
+### About this task
+
+To add a new or update an existing License:
+
+### Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+### Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
+
+## Request new License
+
+To request a new license, use the [My HPE Software Center](https://myenterpriselicense.hpe.com) or contact your account manager.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json b/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
new file mode 100644
index 0000000..e9b94f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+  "title": "vRealize Orchestrator",
+  "ordinal": 381,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html",
+  "topic_cluster": {
+    "clustering_title": "vRealize Orchestrator",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md b/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
new file mode 100644
index 0000000..439c4f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
@@ -0,0 +1,185 @@
+# vRealize Orchestrator
+
+The vRealize Orchestrator (vRO) Integration provided for HPE Morpheus Enterprise enables users to easily trigger existing workflows that may already exist in vRealize Orchestrator. Not only can the user trigger these workflows, but they can also be chained easily into non-vRO workflows and process both output and input parameters of a workflow.
+
+## Adding the Integration
+
+Setting up the vRO integration involves some steps which vary depending on the authentication model being used.
+
+NAME
+:   Name of the integration
+
+API URL
+:   Typically, the API URL is run on port 8283. A sample API URL may look like the following example: `https://vrahost.com:8283/`
+
+AUTH TYPE
+:   Chosen based on the authentication provider configured on vRO
+
+CREDENTIALS
+:   Choose `Local Credentials` to enter credentials for this integration or choose to create/use an existing credentials
+
+USERNAME
+:   Username that will be configured on the integration that can authenticate with vRO
+
+PASSWORD
+:   Password that will be configured on the integration for the username that can authentication with vRO
+
+Tenant Token
+:   The domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`
+
+    NOTE
+
+    At times, this can vary depending on how authentication and role assignments for the user have been set up for vRO.
+
+CLIENT ID
+:   The ID used and obtained from the vRO server, typically used when using `OAuth 2.0` Auth Type
+
+### Basic Auth Type
+
+The `Basic` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `vSphere` Authentication Provider. When vRO is configured with this provider, users login to vRO using their vSphere/vCenter credentials, which HPE Morpheus Enterprise will use the same.
+
+NOTE
+
+The `CLIENT ID` field can contain any value. It will be unused with the `Basic` Auth Type
+
+Example of a configured `vSphere` Authentication Provider from the vRO Control Center:
+
+![../../_images/vsphere_auth_provider.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A89B217A-D71D-497C-9346-6E62C493B2B7-high.png)
+
+Example of a configured `Basic` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/basic_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4B3F0F89-D9C0-49D3-B0CE-52017F8F3ADE-high.png)
+
+### OAuth 2.0 Auth Type
+
+The `OAuth 2.0` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `VIDM` option or other OAuth provider.
+
+When using `OAuth 2.0`, the Client ID must be gathered first. This can be found by browsing a file on the actual VRA server using SSH. On the vRA server, run the following command: `grep -i cafe_cli= /etc/vcac/solution-users.properties | sed -e 's/cafe_cli=//'`
+
+Be sure to fill in the tenant token as the domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`.
+
+Example of a configured `OAuth 2.0` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/oauth_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-709086F0-E900-49AD-8D31-0CFD87259E9A-high.png)
+
+### vRA Auth Type
+
+The `vRA` Auth Type should be used when the vRA identity provider is configured for your vRO. The `vRA` Auth Type and `OAuth` Auth Type fields requirements are the same, execept when using `vRA` Auth Type the `Client ID` is no longer needed.
+
+## Using vRealize Orchestrator
+
+One of the first things HPE Morpheus Enterprise does when it is tied into a vRO integration is sync all available workflows by category. These workflows become available when creating a new HPE Morpheus Enterprise task in Library > Automation. HPE Morpheus Enterprise allows a user to map these vRO workflows into the task engine. The task engine allows users to design workflows that chain tasks in order or operate at different phases of a provisioning request. For more information on tasks, please read the Automation documentation.
+
+Creating a task for vRO is simple.
+
+First, go to Library > Automationand create a new task. Enter a Name and a Code, the Code can be used later to reference the results of tasks. Choose a task type of `vRealize Orchestrator Workflow`. A dropdown will appear allowing one to first select the active vRO Integration you would like to use. Once that is selected, a list of workflows becomes available.
+
+NOTE
+
+The next part is where things can get a bit tricky. The parameter body (expected in JSON) format can be a bit difficult to track down. One way is to use the Network Chrome inspector when kicking off a sample workflow from the vRO HTML5 client and grabbing the parameter JSON. Another is to query the API yourself and look at the samples from historical run history.
+
+An example payload for the SSH / Run SSH Command Workflow would look like this:
+
+```
+```
+{  
+    "parameters": [  
+        {  
+            "name": "hostNameOrIP",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "x.x.x.x"  
+                }  
+            }  
+        },  
+        {  
+            "name": "port",  
+            "type": "number",  
+            "value": {  
+                "number": {  
+                    "value": 22  
+                }  
+            }  
+        },  
+        {  
+            "name": "cmd",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "echo \"Hello <%=instance.name%>\""  
+                }  
+            }  
+        },  
+        {  
+            "name": "encoding",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        },  
+        {  
+            "name": "username",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "myuser"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passwordAuthentication",  
+            "type": "boolean",  
+            "value": {  
+                "boolean": {  
+                    "value": true  
+                }  
+            }  
+        },  
+        {  
+            "name": "password",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "password"  
+                }  
+            }  
+        },  
+        {  
+            "name": "path",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "\/var\/lib\/vco\/app-server\/conf\/vco_key"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passphrase",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        }  
+    ]  
+}
+```
+```
+
+Note that all HPE Morpheus Enterprise variables can be injected into the parameter body. In the above example we inject the instance name into the sample command with `<%=instance.name%>` but other values can be used, such as `<%= server.sshHost %>` for the hostname and `<%= server.sshPort %>` for the port. Additional variable examples can be found here: [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+Adding this task to a workflow allows the result parameters to be referenced in subsequent tasks called throughout the workflow. For example, a local script task type could reference the output text of the above ssh command by injecting the following results map: `echo "results.vro: <%=results.vro.find{it.name == 'outputText'}?.value?.string?.value%>"` With this example, `vro` refers back to the “Code” of the vRO task that would contain the ouput we wish to referece. More information on Task Results can be found here: [Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)
+
+Additional output/map examples referencing a previous task with the “Code” of `vrossh`:
+
+- Print all output: `echo '<%=results.vrossh.encodeAsJson().toString() %>'`
+- Print the `outputText` variable/output: `echo "results.vrossh.outputText: <%=results.vrossh.find{it.name == 'outputText'}?.value?.string?.value%>"`
+- Print the `errorText` variable/output: `echo "results.vrossh.errorText: <%=results.vrossh.find{it.name == 'errorText'}?.value?.string?.value%>"`
+- Print the `result` variable/output, returned as a string: `echo "results.vrossh.result: <%=results.vrossh.find{it.name == 'result'}?.value?.string?.value%>"`
+- Print the `exitcode` variable/output, returned as a number: `echo "results.vrossh.exitcode: <%=results.vrossh.find{it.name == 'exitcode'}?.value?.number?.value%>"`
+
+There are very powerful options available for chaining results and injecting variables relevant to the instance being provisioned or even custom inputs from an operational workflow. Please reference the rest of the Automation documentation for examples.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
new file mode 100644
index 0000000..dc8f5f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+  "title": "Syslog",
+  "ordinal": 504,
+  "parent_title": "Logs",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.html",
+  "topic_cluster": {
+    "clustering_title": "Syslog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
new file mode 100644
index 0000000..9755802
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
@@ -0,0 +1,10 @@
+# Syslog
+
+## Adding Syslog Integration
+
+### Procedure
+
+1. Navigate to Administration > Settings > Logs
+2. Expand the HPE Morpheus Enterprise logging section
+3. Add the Syslog forwarding rules
+4. Select QUICK ADD
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json b/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
new file mode 100644
index 0000000..bf90b0e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+  "title": "Add Amazon ELB load balancer",
+  "ordinal": 493,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ELB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md b/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
new file mode 100644
index 0000000..b179c7a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
@@ -0,0 +1,33 @@
+# Add Amazon ELB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ELB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz ELB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C14F7BC3-0BDA-4CF2-A85A-19B1C1EF8694-high.jpg)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..ed469a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 320,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..76ef211
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,142 @@
+# Health
+
+## HPE Morpheus Enterprise Health
+
+![../../_images/morpheusHealth500.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BB8CA295-BF75-426C-941D-EBB1FB9233DC-high.png)
+
+The HPE Morpheus Enterprise Health section provides an overview of the health of your HPE Morpheus Enterprise appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or HPE Morpheus Enterprise memory usage is above 95%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Opensearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+### Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be accessing. By default, HPE Morpheus Enterprise does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the HPE Morpheus Enterprise official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by HPE Morpheus Enterprise processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by HPE Morpheus Enterprise processes (see the Knowledge Base article linked in the TIP box below for more information on how HPE Morpheus Enterprise claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
+
+TIP
+
+It’s common to see a high percentage of system memory being used [due to the way Morpheus allocates and manages memory](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US). If HPE Morpheus Enterprise is performing well, high system memory use is not necessarily an indicator that any action needs to be taken.
+
+### Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Opensearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
+
+## HPE Morpheus Enterprise Logs
+
+The HPE Morpheus Enterprise logs section aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
+
+![../../_images/healthlogs.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..7e56f74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 217,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..992c123
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,116 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+## Overview
+
+The Networks section is for configuring networks across all clouds in HPE Morpheus Enterprise. Existing networks from Clouds added in HPE Morpheus Enterprise will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, HPE Morpheus Enterprise allows administrators to restrict management of HPE Morpheus Enterprise-created Networks through Role permissions.
+
+## Configuring Networks
+
+### DHCP
+
+#### About this task
+
+To configure a network for DHCP:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+#### Results
+
+IMPORTANT
+
+The DHCP flag tells HPE Morpheus Enterprise this network has a DHCP server assigning IP Addresses to hosts. HPE Morpheus Enterprise does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in HPE Morpheus Enterprise , but no DHCP server actually on the network will in most cases cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
+
+### Static and IP Pools
+
+#### About this task
+
+To configure a network for Static IP Assignment:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured HPE Morpheus Enterprise or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your HPE Morpheus Enterprise appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+#### Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
+
+### Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
+
+### Group and Tenant Access
+
+Networks can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection. **Tenant Permissions** control which Tenants may see the Network. Public visibility allows access to the Network for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
+
+### Guest Console SSH Tunnel
+
+In some scenarios, instances that are segregated from the HPE Morpheus Enterprise appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the HPE Morpheus Enterprise web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by HPE Morpheus Enterprise but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in HPE Morpheus Enterprise to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
+
+### Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..ecbf902
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 265,
+  "parent_title": "Tools",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..e4aa089
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,53 @@
+# Archives
+
+## Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html)). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
+
+## Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in HPE Morpheus Enterprise
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether HPE Morpheus Enterprise is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
+
+![../_images/archivelist.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C069FB35-5152-45DA-B2FE-5C7DDE5F3563-high.png)
+
+## Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, HPE Morpheus Enterprise will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
+
+## Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
+
+![../_images/archivedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3A823ED0-F545-4405-AC60-EAF927081936-high.png)
+
+## File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
+
+![../_images/filedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json b/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
new file mode 100644
index 0000000..c6f3925
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+  "title": "Apps",
+  "ordinal": 87,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md b/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
new file mode 100644
index 0000000..7ba12a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
@@ -0,0 +1,10 @@
+# Apps
+
+Apps allow instances having general relationships to be grouped in a clean and organized manner. App functionality enables full control of which instances belong in an app as well setting Firewall and Access Control List (ACL) rules. Use Apps to structure all necessary components into a single place. Add checks and groups for web servers, database nodes, etc.
+
+Apps can be created from Blueprints, which are made in Library > Blueprints > App Blueprints or from Existing Apps.
+
+**Subtopics**  
+
+- **[Creating Apps](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html)**
+- **[Managing Apps](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..37f56f1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 269,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..de3253d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,24 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
+    - When migrating to NFS-backed datastores, setting `async` on the NFS server may improve performance
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json b/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
new file mode 100644
index 0000000..acad863
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+  "title": "Bluecat",
+  "ordinal": 514,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html",
+  "topic_cluster": {
+    "clustering_title": "Bluecat",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md b/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
new file mode 100644
index 0000000..a7e0024
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
@@ -0,0 +1,58 @@
+# Bluecat
+
+## Overview
+
+HPE Morpheus Enterprise integrates with Bluecat IPAM to scope pools to networks for static IP assignment from Bluecat to your HPE Morpheus Enterprise Instances.
+
+## Adding Bluecat to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select Bluecat
+4. Enter in the following information 
+
+   Name
+   :   Name of the Bluecat Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Uncheck to disable sync with the Bluecat endpoint
+
+   URL
+   :   URL of the Bluecat server, ex: `http://10.30.20.10`
+
+   Username
+   :   Username of Bluecat API User. API and root level propagating read access required, read/write access required for target Networks and Domains.
+
+   Password
+   :   Bluecat User password
+
+   Network Filter
+   :   Optionally enter a comma-separated list of `entityIds` for config(s), block(s) or network(s) (ex. `entityId1,entityId2...`) to filter the synced IP pools, networks and domains
+5. Click SAVE CHANGES
+
+### Results
+
+The Bluecat Integration will be saved, IP pools will sync in and populate under Infrastructure  >  Network  >  IP Pools, and Domains will populate in Infrastructure  >  Network  >  Domains. Pools and Domains can also be found in the Bluecat Integration details page, which can be accessed by clicking on the name of the added Bluecat Integration in Infrastructure  >  Network  >  Services.
+
+IMPORTANT
+
+Quick Deployments must be enabled in Bluecat for HPE Morpheus Enterprise to create instantly available DNS records when using Bluecat DNS.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Bluecat IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Bluecat IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network- Networks`
+2. Select a Network name and EDIT, or select ACTIONS - Edit
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json b/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
new file mode 100644
index 0000000..188465b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+  "title": "Using Volume",
+  "ordinal": 448,
+  "parent_title": "Volume Consumption",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html",
+  "topic_cluster": {
+    "clustering_title": "Using Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md b/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
new file mode 100644
index 0000000..519f42c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
@@ -0,0 +1,14 @@
+# Using Volume
+
+## About this task
+
+Perform the following to use the configured volume:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Click Add.
+3. After selecting the HPE BareMetal ILO server for type and specifying the cloud, group, and a name for the instance, click Next to advance to the Configure section.
+4. Click on the + sign next to Volumes to add a volume to this instance.
+5. Specify a name for the volume, desired size, volume type to indicate whether it is a replicated volume or not, the datastore to create it in, and whether it’s a shared volume.   
+   ![Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-090D059F-2321-4377-B832-EEAF50ED173E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json b/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
new file mode 100644
index 0000000..4a45059
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+  "title": "Creating Policies",
+  "ordinal": 318,
+  "parent_title": "Policies",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md b/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
new file mode 100644
index 0000000..67f62e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
@@ -0,0 +1,80 @@
+# Creating Policies
+
+Policies can be created in three different locations.
+
+- Administration > Policies
+- Infrastructure  >  Groups  >  Group  >  Policies
+- Infrastructure  >  Clouds  >  Cloud  >  Policies
+
+Policies can be disabled and re-enabled at anytime.
+
+IMPORTANT
+
+Precedence is applied to matching or conflicting Policies in the following order: Cloud > Group > Role > User > Global.
+
+## To create a Global Policy:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under Filter next to scope select Global
+5. Select SAVE CHANGES
+
+## To create a Policy for a User:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select User a drop down menu will appear below allowing you to select a user
+5. Select SAVE CHANGES
+
+## To create a Policy for a Role:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select Role a drop down menu will appear below allowing you to select a Role
+5. For `APPLY INDIVIDUALLY TO EACH USER IN ROLE`
+   :   - Select for Max Resource/Quota Policies to be calculated per user
+       - Leave unselected to calculate by total usage of all users within that Role.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Cloud:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Cloud the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created or moved into the Group after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select a Cloud by clicking on the name of the Cloud to go to the Cloud Detail page.
+3. Select the `POLICIES` tab in the Cloud Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Type sections below for Configuration options.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Group:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Group the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group by clicking on the name of the Group to go to the Group Detail page.
+3. Select the `POLICIES` tab in the Group Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Types sections below for Configuration options.
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json b/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
new file mode 100644
index 0000000..3a48726
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+  "title": "Workloads: Instance Type Usage",
+  "ordinal": 67,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Type Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md b/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
new file mode 100644
index 0000000..176e82d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Type Usage
+
+![../_images/9instancetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Instance Type Usage dashboard organizes workloads meeting dashboard filters by their Instance type. In additional to counts, administrators can view resource consumption and cost figures by Instance type groupings as well.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance type name (all matching search terms, Morpheus-default Instance types are not included when using the search filter)
+- Metric (apply to see the top Instance types by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **TYPES:** The total number of Instance types represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Type Usage List
+
+Each Instance type represented in the dashboard is listed below the graph. For each Instance type shown, we see the number of Groups the Instance type is represented in, the number of Clouds the Instance type has been provisioned into, and the total amount of memory allotted to workloads of each Instance type.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json b/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
new file mode 100644
index 0000000..b9db20f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+  "title": "Data Encryption",
+  "ordinal": 36,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html",
+  "topic_cluster": {
+    "clustering_title": "Data Encryption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md b/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
new file mode 100644
index 0000000..5905180
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
@@ -0,0 +1,69 @@
+# Data Encryption
+
+By default, Morpheus encrypts sensitive data in the Database using AES encryption mode with GCM. Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files such as `morpheus-secrets.json` and `morpheus.rb` are in plain text as they are only accessible by root.
+
+Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files can be set to an encrypted string using the HPE Morpheus Enterprise crypto utility to generate ENC strings and then using `ENC(string)` as the value in the configuration file.
+
+Additionally a custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 hash, which is used to generate the AES encryption key.
+
+## Generate ENC Strings for morpheus-secrets.json
+
+### About this task
+
+System generated passwords are set in `/etc/morpheus/morpheus-secrets.json`. These entries can be updated to ENC strings with the following steps:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string migrate` which will output ENC() strings for the passwords in morpheus-secrets.json
+2. Update the desired password strings in the `morpheus-secrets.json` config file with the matching ENC() string.
+3. Save `morpheus-secrets.json`
+4. Run `morpheus-ctl reconfigure`
+
+## Generate ENC Strings for custom morpheus.rb entries
+
+### About this task
+
+ENC() strings can be generated for sensitive data set in morpheus.rb, such as the password to an external service.
+
+To generate ENC(0) strings for morpheus.rb entries:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string string $clear_text '$suffix'` which will output strings for the passwords in morpheus-secrets.json 
+
+   - Replace `$clear_text` with the string to be encrypted
+   - If a suffix is defined in morpheus.rb (as described in the next section), replace `$suffix` with your suffix.
+
+   NOTE
+
+   It is advisable to disable bash history logging by running `unset HISTFILE` before running the morphesu-ctl get-crypto-string command and then `set HISTFILE=$HOME/.bash_history` to reenable.
+2. Update the desired password strings in the `morpheus.rb` config file with the matching string output, using `ENC($output)` format 
+
+   - Example: `mysql['morpheus_password'] = 'ENC($ZI5DnaO0quhxKe$kDFD+U2ZeJUuYiNC$F1+czPNyo+3lAdq7V0gcrWwHnkINYqr13cUGrDVyog==)'`
+3. Save `morpheus.rb`
+4. Run `morpheus-ctl reconfigure`
+
+## Encrypted Key Suffix
+
+### About this task
+
+A custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 Hash, which is used in the generation of the system AES encryption key.
+
+DANGER
+
+Setting a custom Encryption Key Suffix affects all data encrypted by HPE Morpheus Enterprise, including database and cypher data. Encryption Key Suffix is required in the event data needs to be migrated or recovered. Once the Encryption Key Suffix is set, data cannot be recovered without it. Store any Encryption Key Suffix externally where it can be referenced for future scenarios.
+
+IMPORTANT
+
+The Encryption Key Suffix cannot be changed or removed after being set. Changing or removing an existing Encryption Key Suffix will prevent data access. If an existing suffix is altered in the morpheus.rb file, it must be restore to its original value.
+
+### Procedure
+
+1. Add `app['encryption_key_suffix'] = '$suffix'` to `/etc/morpheus/morpheus.rb`, replacing `$suffix` with your suffix. 
+
+   DANGER
+
+   Once an Encryption Key Suffix is set and applied via reconfigure, it cannot be altered or removed and data cannot be migrated or recovered without it.
+2. Run `morpheus-ctl reconfigure` 
+
+   - Reconfigure will generate a new encryption key using the suffix and set (ENC) values for the service password in application.yml
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json b/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
new file mode 100644
index 0000000..4103884
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+  "title": "Integrating Hashicorp Vault",
+  "ordinal": 239,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating Hashicorp Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md b/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
new file mode 100644
index 0000000..ee8c9e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
@@ -0,0 +1,27 @@
+# Integrating Hashicorp Vault
+
+The Hashicorp Vault integration is not included with HPE Morpheus Enterprise by default. Download the plugin from HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/) and add the plugin to HPE Morpheus Enterprise through the [Plugins](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) section. This allows users to store credential sets completely outside of HPE Morpheus Enterprise and in Hashicorp Vault, which may be required by your organization’s IT policies.
+
+NOTE
+
+The plugin space is universal and not specific to Tenants. If Subtenant users have access to Administration > Integrations > Plugins, any integrated plugins will be available in all Tenants across the appliance. In most cases, it makes sense to restrict access to this section from Subtenant users through the associated Tenant Role. Instead integrate plugins from the Primary Tenant and expose them to various Subtenants as needed.
+
+Once downloaded, plugins are added to HPE Morpheus Enterprise in Administration > Integrations > Plugins. Simply browse your local filesystem for the JAR file downloaded from HPE Morpheus Enterprise Exchange and its capabilities will immediately be added to the appliance. After adding the plugin, configure access for the plugin to your Vault server. Do this by clicking the Edit (pencil) button in the row for the Vault plugin. Supply a URL for your Vault server and an access token, then save your changes.
+
+NOTE
+
+When creating a Vault integration, it’s recommended that you use a long-lived token. If the token suddenly becomes invalid, HPE Morpheus Enterprise will be unable to write new credential sets to Vault and will be unable to edit or delete any existing ones. Additionally, you won’t be able to use Vault-stored credential sets elsewhere in HPE Morpheus Enterprise, such as when creating new Cloud integrations or populating REST-based Option Lists which require authentication. Should this happen, simply obtain a new token, edit the Vault integration, update the token, and save your changes.
+
+With the plugin added, a new integration type will appear in Infrastructure > Trust > Integrations. Click + ADD, then “Hashicorp Vault Credentials” to get started. The fields in the list below are available for configuration but it’s possible that no configuration will be necessary. If you do not enter a new API URL and TOKEN value, these are taken from the plugin configuration set a moment ago. Similarly, The Vault Secret Engine and Secret Path can be left at default values (or empty) if those values are acceptable. If you need to override the defaults or the URL/token set on the plugin, you may do so here.
+
+- **NAME:** A friendly name for the Vault integration in HPE Morpheus Enterprise
+- **ENABLED:** When marked, this Vault integration will be available to have credentials written to it
+- **API URL:** The URL for the Vault server (ex. <http://xx.xx.xx.xx:8200>)
+- **TOKEN:** A valid API token for the server (see note below)
+- **HASHICORP VAULT SECRET ENGINE:** Select KV Engine version 1 or 2, additional engines may be available in the future
+- **ENGINE MOUNT:** If desired, enter a custom engine mount. By default, if left empty, credentials are written to the “secret/” engine mount
+- **SECRET PATH:** If desired, enter a custom path and HPE Morpheus Enterprise will write new credential sets to that path. By default, if left empty, new credentials are written to “morpheus-credentials/”
+
+When done, click SAVE CHANGES.
+
+With the above process finished, this Vault integration will be available as a storage target when creating new credential sets. In Infrastructure > Trust > Credentials, after clicking + ADD and selecting the type of credential set to add, select the new Vault integration in the CREDENTIAL STORE field (default selection is “Internal”).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json b/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
new file mode 100644
index 0000000..aed0671
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+  "title": "UpCloud",
+  "ordinal": 473,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.html",
+  "topic_cluster": {
+    "clustering_title": "UpCloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md b/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
new file mode 100644
index 0000000..8b66f6a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
@@ -0,0 +1,264 @@
+# UpCloud
+
+## Overview
+
+UpCloud is a cloud hosting provider that offers both Linux and Windows virtual machines on their MAXIOPS infrastructure which is billed as I.A.A.S ( infrastructure-as-a-service ). They have datacenters based in the UK, USA, Germany, Netherlands, Singapore and Finland. Servers can be created a lightning fast 45 seconds with their faster than SSD technology.
+
+## Features
+
+- Virtual Machine Provisioning
+- Containers
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Inventory
+- Cloudinit
+
+## Requirements
+
+### About this task
+
+An UpCloud User with API, Server and Storage permissions is required.
+
+To enable API access for a Main Account UpCloud User:
+
+### Procedure
+
+1. Login to UpCloud
+2. Select My Account  >  User Accounts
+3. Select Change on the target user
+4. Check the box for API connections: Allow API connections from
+5. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+6. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+7. Save
+
+### Results
+
+To Enable API, API, Server and Storage permissions for a SubAccount User:
+
+When creating or editing a Sub Account UpCloud user:
+
+1. Check the box for API connections: Allow API connections from
+2. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+3. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+4. Save
+
+## Adding an UpCloud Cloud
+
+### Configure
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud Button
+3. Select UpCloud from the Add Cloud modal
+4. Select NEXT
+5. Enter the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   USERNAME
+   :   UpCloud User Account Username
+
+   PASSWORD
+   :   UpCloud User Account Password
+
+   ZONE
+   :   Select UpCloud Datacenter to scope cloud to
+
+   INVENTORY
+   :   - Off: Existing UpCloud Servers will not be inventoried in HPE Morpheus Enterprise
+       - Basic: Existing Servers are Inventoried with Power state, Memory and Cores statistics synced.
+       - Full: Existing Servers are Inventoried with Power state, Memory and Cores statistics, plus IP Addresses, Storage Info, and Console VNC Information.
+
+   NOTE
+
+   Full Inventory level recommended. Basic Inventory level can reduce Cloud Sync times when inventorying Datacenters with large amounts of servers. Credentials need to be added by editing the Virtual Machine in order to connect.
+
+   The Cloud can now be added to a Group or configured with additional Advanced options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+### Group
+
+A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+- USE EXISTING: Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+- CREATE NEW: Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+
+### Review
+
+Confirm all settings are correct and select COMPLETE.
+
+The UpCloud Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of:
+
+- UpCloud Servers will added as Virtual Machines (if Inventory is enabled)
+- UpCloud Templates (My Templates) will sync and be added to Library > Virtual Images.
+
+NOTE
+
+The Console tab will only appear for Inventoried Servers if Inventory Level is set to Full
+
+## Provisioning to UpCloud
+
+Instances and Apps can be created using the private Images synced from UpCloud or from the HPE Morpheus Enterprise provided Image Catalog.
+
+## Provision a synced Image
+
+Images synced from UpCloud can be provisioned by using:
+
+- The UPCLOUD Instance Type and selecting the Image from the Image dropdown in the configure section when provisioning and Instance, App, or creating an App Blueprint.
+- Creating custom Library Instance Types and selecting a synced Image when creating a Node Type for the custom Instance Type.
+
+IMPORTANT
+
+Synced images should be configured prior to provisioning by editing the Image in the Library > Virtual Images section.
+
+## Provision a HPE Morpheus Enterprise provided UpCloud Image
+
+HPE Morpheus Enterprise provides a number of pre-configured Images that are available in the default HPE Morpheus Enterprise Catalog when provisioning and Instance, App, or creating an App Blueprint. UpCloud Images are included in the following Instance Types in the default HPE Morpheus Enterprise catalog.
+
+- ACTIVEMQ
+- APACHE
+- CASSANDRA
+- DEBIAN
+- ELASTICSEARCH
+- GRAILS
+- JAVA
+- MONGO
+- MYSQL
+- NGINX
+- PHP
+- RABBITMQ
+- REDIS
+- OMCAT
+- UBUNTU
+- WINDOWS
+- GRAILS
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json b/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
new file mode 100644
index 0000000..3290c6b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+  "title": "Layouts",
+  "ordinal": 129,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html",
+  "topic_cluster": {
+    "clustering_title": "Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md b/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
new file mode 100644
index 0000000..c1aa3e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
@@ -0,0 +1,94 @@
+# Layouts
+
+Layouts are attached to Instance Types. A Layout can only be attached to a single Instance Type and a single Technology. An Instance Type can have one or many Layouts attached to it, allowing for a single Instance Type to work with any Technology type. Node Types are added to Layouts. A Layout can have one or many node types attached to it. Node types can be shared across Layouts of matching Technology types.
+
+IMPORTANT
+
+Once an Instance Type is defined on a Layout and saved, the Instance Type setting and Technology selections on the Layout cannot be changed.
+
+## Layout List View
+
+The default page for Layouts is the Layout list view. Select + ADD to create a new Layout. Layouts can also be created from an Instance Type detail page.
+
+The following fields are displayed for each Layout:
+
+- **INSTANCE TYPE:** Select the Instance Type to associate with the Layout. This attribute is automatically set and not shown when creating the Layout from an Instance Type detail page
+- **NAME:** Links to the Layout detail page
+- **VERSION**
+- **DISPLAY ORDER:** Determines the Layout display order in the provisioning wizard when adding an Instance of the associated Instance Type
+- **DESCRIPTION**
+
+NOTE
+
+The order of Layouts given when an Instance Type is being provisioned is in high-to-low order of the Layout Display Order property. Bear in mind this is reversed from how Service Plans are ordered, which is in low-to-high order based on the Display Order value.
+
+The Actions menu in each row reveals the following options:
+
+- **Permissions:** Scope the Layout to Group(s) to narrow the list of available groups for a chosen Instance Type at provision time
+- **Edit:** Edit the Layout
+- **Delete:** Delete the Layout
+
+NOTE
+
+A Layout that is in use cannot be deleted.
+
+Available Filters:
+
+- **Technology:** Display Layouts by selected Cloud technology
+- **Instance Type:** Display Layouts by the associated Instance Type
+
+## Layout Detail View
+
+The Layout Detail view shows details on the Layout including Name, Short Name, Version, and Category. It also lists all associated Node Types.
+
+- Select a Layout Name from the list page or Instance Type detail page to get to a Layout detail page.
+
+## Layout Configuration Options
+
+Instance Type
+:   Select the Instance Type to add to the new Layout. Custom Instance Types must already be created and one Layout cannot be added to multiple instance types. The Instance Type also cannot be changed after creation.
+
+    NOTE
+
+    Layouts cannot be added to Morpheus pre-defined Instance Types
+
+Name
+:   The name the Layout presents as in the Configuration Options dropdown of the provisioning wizard
+
+Version
+:   The version number or name for the Layout. Layouts in an Instance Type with the same version will all show under the Configuration Options dropdown when that version is selected while provisioning
+
+Description
+:   Description of the Layout, viewable on the Layout list view
+
+Creatable
+:   When checked, this Layout will be selectable at provision time for the associated Instance Type (assuming the Layout is otherwise compatible with provisioning conditions). Instance Types with no Creatable Layouts will not be selectable from the provisioning wizard
+
+Technology
+:   Technology determines which Cloud this layout will be available for and which Node Types can be added to it
+
+Minimum Memory
+:   Defines the minimum amount of memory required for this Layout. Only Service Plans that meet the defined memory minimum will be available during provisioning when this Layout is selected. Custom memory values must also meet this minimum. Entering a minimum memory value of zero (the default value) indicates no minimum. This minimum memory value will override any Virtual Image minimum memory requirements
+
+Workflow
+:   Select a Workflow which will be associated as the Provisioning Workflow for Instances provisioned using this Layout. If a Workflow is defined, it is not shown to the user at provision time and will be run in addition to any Workflows set on the Instance Type, in Workflows Policies, defined in App Blueprints, or selected manually at provision time.
+
+Supports Convert to Managed
+:   Enabled to allow users to select this layout when converting a Discovered workload to Managed
+
+Enable Scaling (Horizontal)
+:   Enables Instances with this layout to use scaling features
+
+Environment Variables
+:   Custom environment variables to be added to the Instance when provisioned
+
+Inputs
+:   Search for and select one or multiple Inputs to add to the Layout. Inputs (except for Hidden Inputs) will appear in Provisioning, App, Blueprint, and Cloning wizards when this layout is selected
+
+Nodes
+:   Single or multiple nodes can be added to a Layout by searching for and selecting the Node(s)
+
+Price Sets
+:   Associate a Price Set with the Layout, Price Sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Layouts become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Layout. If this Layout is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Layout Price Sets Demo**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json b/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
new file mode 100644
index 0000000..4b8c523
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+  "title": "Supported Software Versions",
+  "ordinal": 397,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Software Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md b/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
new file mode 100644
index 0000000..11461cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
@@ -0,0 +1,15 @@
+# Supported Software Versions
+
+**Required Software**
+
+Ensure your environment uses the following software versions before you proceed. Features and behavior may vary across different releases.
+
+- HPE Morpheus Enterprise: Version 8.1.0
+- HPE BMaaS: Version 1.0.0
+
+**Managed Networking and External Storage Requirements**
+
+Install the following integrations only if your environment requires managed networking or external storage:
+
+- HPE ArubaCX Network Integration: Version 1.9.0
+- HPE Alletra MP Integration: Version 1.9.0
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.json b/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
new file mode 100644
index 0000000..c4b49e8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+  "title": "CentOS/RHEL 7 Images",
+  "ordinal": 50,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html",
+  "topic_cluster": {
+    "clustering_title": "CentOS/RHEL 7 Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.md b/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
new file mode 100644
index 0000000..256607e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
@@ -0,0 +1,3 @@
+# CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json b/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
new file mode 100644
index 0000000..382ff0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+  "title": "Distributed Workers",
+  "ordinal": 314,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.html",
+  "topic_cluster": {
+    "clustering_title": "Distributed Workers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md b/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
new file mode 100644
index 0000000..2d2bba7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
@@ -0,0 +1,146 @@
+# Distributed Workers
+
+## Overview
+
+The HPE Morpheus Enterprise distributed worker is installed using the same package as the VDI Gateway worker. Organizations which have already deployed VDI Gateway(s) can use the same worker for both purposes if desired, you’d simply need to update configuration in `/etc/morpheus/morpheus-worker.rb` and run a reconfigure. When creating a distributed worker or VDI Gateway object in HPE Morpheus Enterprise UI, an API key is generated. Adding one or both types of API keys to the worker configuration file determines if the worker is running in VDI gateway and/or distributed worker mode.
+
+### Supported Cloud Types
+
+The following Cloud/Zone types support Distributed Workers
+
+- vmware
+- vmwareCloudAws
+- nutanix
+- openstack
+- xenserver
+- macstadium
+
+## Installation
+
+A distributed worker VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+Package URLs for the distributed worker are available at <https://app.morpheushub.com> in the downloads section.
+
+NOTE
+
+The distributed worker requires that the HPE Morpheus Enterprise appliance has a trusted SSL certificate. This can be accomplished by configuring a public trusted SSL certificate on the HPE Morpheus Enterprise appliance (or load balancer) or ensure the certificate and chain are added to the Java Keystore of the Distributed Worker to trust the certificate.
+
+### Requirements
+
+Table 1. Supported Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE SLES | 12 |
+| Ubuntu | 18.04, 20.04, 22.04 |
+
+- **Memory:** 4 GB RAM minimum recommended
+- **Storage:** 10 GB storage minimum recommended. Storage is required for installation packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity **to** the HPE Morpheus Enterprise appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise worker package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+IMPORTANT
+
+In order to proxy VMware vCenter Cloud traffic through a Distributed Worker, you must have a static public DNS entry for the internal IP address of the vCenter appliance. If this is not done, everything may appear to be working properly when configuring the Cloud but problems will arise at provision time. This is not a HPE Morpheus Enterprise limitation but is a limitation of the VMware SDK client which does not natively support proxies.
+
+Download the appropriate package from HPE Morpheus Enterprise Hub based on your target Linux distribution and version for installation in a directory of your choosing. The package can be removed after successful installation.
+
+```
+```
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+```
+```
+
+Validate the package checksum as compared with the values indicated on Hub. For example:
+
+```
+```
+sha256sum morpheus-worker-$version.distro
+```
+```
+
+Next, install the package using your selected distribution’s package installation command and your preferred options. Example, for RPM:
+
+**rpm**:
+
+```
+```
+$ sudo rpm -ihv morpheus-worker-$version.$distro  
+Preparing...                          ################################# [100%]  
+Updating / installing...  
+   1:morpheus-worker-x.x.x-1.$distro    ################################# [100%]  
+Thank you for installing Morpheus Worker!  
+Configure and start the Worker by running the following command:  
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+## Configuration
+
+With the package installed, we need to add a new distributed worker in HPE Morpheus Enterprise UI. Distributed workers are added in Administration > Integrations > Distributed Workers. To create one, populate the following fields:
+
+- **NAME:** A name for the distributed worker in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the distributed worker
+- **PROXY HOSTS:** A comma-delimited list of global proxy hosts, any endpoint listed here will be proxied through the HPE Morpheus Enterprise worker. For VMware, you must list the host addresses for any vCenter you wish to proxy through the worker. Xen hosts and PowerVC hosts must be listed here as well. Other Cloud types which are supported by the HPE Morpheus Enterprise worker need only have the worker configured on the Edit Cloud modal (Infrastructure > Clouds > Selected Cloud > Editbutton)
+- **ENABLED:** When marked, the selected worker is available for use
+
+IMPORTANT
+
+The proxy host URL entered in the Worker configuration must match the URL set in the Cloud configuration. That is, if you use the URL in the Cloud configuration you must also use it in the Worker configuration. The reverse is also true, if an IP address is used in the Cloud configuration, that should be used in the Worker configuration as well. There are also configuration considerations that must be made for proxying vCenter Cloud traffic through a Distributed Worker. See the “IMPORTANT” box in the “Requirements” section for additional details.
+
+After clicking SAVE CHANGES, an API key is generated and displayed. Make note of this as it will be needed in a later configuration step.
+
+![../../_images/createWorker.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C9464126-F50C-4309-9A8F-892576EBC646-high.png)
+
+With the worker configured in HPE Morpheus Enterprise, the next step is to update supported Cloud integrations which should be proxied through the worker. Select the desired Cloud from the Clouds List Page (Infrastructure > Clouds) and click EDIT from the chosen Cloud’s Detail Page. Within the Connection Options section, choose a configured worker from the WORKER dropdown menu. Click SAVE CHANGES.
+
+![../../_images/addWorkerToCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-42AD2A2E-CE88-4F15-AECE-FC70A4C7B574-high.png)
+
+With the API key in hand and configuration complete in HPE Morpheus Enterprise UI, head back to the worker box. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following:
+
+```
+```
+worker_url = 'https://gateway_worker_url' # This is the worker URL the Morpheus appliance can resolve and reach on 443  
+worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of Morpheus appliance which the worker can reach on port 443  
+worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from Morpheus Appliance VDI Pools > VDI Gateways configuration. For worker only mode, a value is still required but can be any value, including the 'API KEY FOR THIS GATEWAY' default template value  
+worker['worker_key'] = 'DISTRIBUTED WORKER KEY' # Distributed Worker API Key from Administration > Integrations > Distributed Workers configuration  
+worker['proxy_address'] = 'http://proxy.address:1234' # For environments in which the worker must go through a proxy to communicate with the Morpheus appliance or other resources, configure the address  
+worker['no_proxy'] = 'vcenter.example.com,192.168.xx.xx' # A comma-separated list of resources that should be accessed directly and not through the proxy
+```
+```
+
+NOTE
+
+By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+
+After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services:
+
+```
+```
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+TIP
+
+If the reconfigure process fails due to a missing dependency, add the repo that the missing dependency can be found in and run
+
+NOTE
+
+Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+
+Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+## Highly-Available (HA) Deployment
+
+If desired, multiple distributed worker nodes may be associated to the same HPE Morpheus Enterprise appliance to eliminate a single point of failure should a distributed worker node go down. Configure each distributed worker node using the same worker key (process described in the prior section) and add redundancy using as many additional workers nodes as needed. When multiple worker nodes are using the same worker key, proxy calls will always go through the primary worker node when possible. The primary node is the first worker node configured using a specific worker key. When necessary, automatic failover will take place and another active worker node will be used. While proxy calls will always try to use the primary node when available, HPE Morpheus Enterprise Agent communications can be balanced equally across worker nodes by placing a VIP in front of your distributed workers.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json b/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
new file mode 100644
index 0000000..cf3dcdd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+  "title": "Base Requirements",
+  "ordinal": 4,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html",
+  "topic_cluster": {
+    "clustering_title": "Base Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md b/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
new file mode 100644
index 0000000..0ecfcbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
@@ -0,0 +1,38 @@
+# Base Requirements
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x, 9.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+| Rocky | 8, 9 |  |
+
+- **Memory:**[16 GB recommended](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US) for default installations. 8 GB minimum required with 4 GB+ available storage swap space
+- **Storage:** 200 GB storage minimum (see Storage Considerations below)
+- **CPU:** 4-core, 1.4 GHz (or better), 64-bit CPU recommended for all-in-one systems. For a distributed-tier installation, it’s recommended each tier have 2-core, 1.4 GHz (or better), 64-bit CPU
+- Network connectivity from your users to the appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise appliance package
+- HPE Morpheus Enterprise service nodes must be configured to use accurate NTP servers. A service node may be an app node, database node, RabbitMQ, or Elasticsearch node (see HPE Morpheus Enterprise system architecture details further on in the installation section for more details)
+- Required repository access:
+  :   - Prior to installing the HPE Morpheus Enterprise Appliance you will need to ensure that the target server or virtual machine has access to the base YUM/DNF or APT repositories
+      - A RHEL 8 server requires the `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repository be enabled and accessible
+      - A RHEL 7 server requires access to Optional RPMs repo. The repository need to be enabled and accessible
+- An appliance license is required for any operations involving provisioning
+- Current major web browsers supporting modern standards, such as Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge are supported
+- Internet Connectivity (optional)
+  :   - Access to `https://www.hpe.com/support/hpesc`, `https://share.morpheusdata.com`, and `https://d2u3hdjdxt56gx.cloudfront.net` (the share.morpheusdata.com cloudfront domain that share package requests will redirect to) over port 443 required on app nodes when reconfiguring to download embedded packages and plugins.
+      - Access to `https://morpheus-images.morpheusdata.com`, `https://registry.morpheusdata.com`, and `https://playbooks.morpheusdata.com` To download HPE Morpheus Enterprise’ system images and playbooks.
+      - Offline installation requires installing the supplemental package in addition to the regular installation package. Local yum/apt repo access still required for offline installations.
+
+NOTE
+
+Access to `yum` and `apt` repos is still required for offline installations.
+
+- VM and Host Agent Install (optional)
+  :   - Inbound connectivity access from provisioned VMs and container hosts on port 443 (Agent install and communication). Port 80 may be required for older `apt` distros.
+      - An Appliance URL that is accessible/resolvable to all managed hosts. It is necessary for all hosts that are managed by HPE Morpheus Enterprise to be able to communicate with the appliance server ip on port 443. This URL is configured under Administration > Settings.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json b/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
new file mode 100644
index 0000000..36dc8c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+  "title": "Creating a Storage Server",
+  "ordinal": 440,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md b/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
new file mode 100644
index 0000000..753d001
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
@@ -0,0 +1,19 @@
+# Creating a Storage Server
+
+## About this task
+
+This procedure guides you through creating a storage server.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > Servers.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage HVM for type, specify the URL for the storage array, and the credentials.
+5. Click the Save Changes to create the storage server.   
+   ![Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-27BC7480-6D59-4328-A9E6-34871F98D44A-high.png)
+
+## Results
+
+The added storage server appears under Servers.   
+![storage server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-34DE4590-20A0-495D-BF21-0EC690472E30-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json b/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
new file mode 100644
index 0000000..afc0254
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+  "title": "Host Hardware Sensor Data Collection",
+  "ordinal": 189,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html",
+  "topic_cluster": {
+    "clustering_title": "Host Hardware Sensor Data Collection",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+        "clustering_title": "Host Hardware Sensor Data Collection"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md b/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
new file mode 100644
index 0000000..4f18ff0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
@@ -0,0 +1,27 @@
+# Host Hardware Sensor Data Collection
+
+If properly configured, HVM Hosts can display detailed hardware information on the HVM Hosts detail pages. This information includes system health LED state, CPU temperature, ambient temperature, fan speeds, power supply state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BC8DF5F3-1416-4BE4-B58F-CB1926EF7DD2-high.png)
+
+Configuration
+
+In order to surface hardware sensor data into the UI, IPMI tool and it's dependency packages must be installed on each host. Following installation, the host agent must be restarted.
+
+1. Install IPMI tool and its dependency packages (`freeipmi-common`, `ipmitool`, `libfreeipmi17`, `openipmi`)
+
+   NOTE
+
+   This tool can also be installed via apt package manager provided that the corresponding Ubuntu mirrors (main and universe module repos) are enabled. Run `sudo apt update` and then `sudo apt install ipmitool`.
+2. To confirm installation, run `sudo ipmitool -v` and the installed version should be displayed
+3. Restart the host agent with `sudo morpheus-node-ctl restart`
+4. Repeat this process on all cluster hosts
+
+Viewing Hardware Sensor Data
+
+When properly configured, hardware sensor data may be viewed from the host detail page:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM cluster
+3. Select the Health subtab
+4. The hardware sensor states and hardware events are shown in the Sensors and Events subtabs
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json b/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
new file mode 100644
index 0000000..00fd8b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+  "title": "Cluster Layouts",
+  "ordinal": 144,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md b/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
new file mode 100644
index 0000000..9e226b3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
@@ -0,0 +1,13 @@
+# Cluster Layouts
+
+HPE Morpheus Enterprise includes many different types of Cluster Layouts out-of-the-box which support a number of provisioning technologies. Many of these HPE Morpheus Enterprise-provided Cluster Layouts may also be cloned for use in creating custom layouts. Edit or delete user-created Cluster Layouts using the pencil (✎) or trash can (🗑) icons next to the desired layout on the Cluster Layouts list page. See the next section for an
+
+![../../_images/clusterLayouts.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-828B4DE9-16E1-4F18-9F19-FDC0410DB2C6-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise now syncs available (non-preview) AKS k8s versions daily. Existing synced versions that are no longer supported by Azure are automatically disabled. The table below includes available AKS versions at time of v8.0.7 release.
+
+**Subtopics**  
+
+- **[Creating Custom Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json b/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
new file mode 100644
index 0000000..491e9b2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+  "title": "2 Factor Authentication",
+  "ordinal": 335,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md b/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
new file mode 100644
index 0000000..0b0957f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
@@ -0,0 +1,21 @@
+# 2 Factor Authentication
+
+HPE Morpheus Enterprise supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+## Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and HPE Morpheus Enterprise will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
+
+## Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
+
+## Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json b/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
new file mode 100644
index 0000000..12c9afa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+  "title": "Troubleshooting and Diagnostics",
+  "ordinal": 449,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting and Diagnostics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md b/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
new file mode 100644
index 0000000..cca37c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
@@ -0,0 +1,30 @@
+# Troubleshooting and Diagnostics
+
+This section provides a structured approach to diagnose and resolve common issues encountered during compute, OS imaging, networking, and storage operations.
+
+Use the following details to obtain the accurate troubleshooting details:
+
+- Identify the symptom: locate the closest match in the table or subsection.
+- Confirm the likely cause: check the listed items using the provided tools and logs.
+- Apply the suggested fix: perform the recommended actions.
+- Collect diagnostic information: if the issue persists, gather logs and screenshots for support escalation.
+
+When reporting an issue, you require the following diagnostics details:
+
+- **System Details**
+  - Hostname / Device ID
+  - OS version and build
+  - BIOS/Firmware version
+- **Event Details**
+  - Date and time of failure
+  - Step at which failure occurred
+  - Any error messages or codes
+- **Logs**
+  - Relevant log files for the failed component
+  - Screenshots of errors (if applicable)
+
+**Subtopics**  
+
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html)**
+- **[Networking](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json b/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
new file mode 100644
index 0000000..7f3f48f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+  "title": "Catalog Items",
+  "ordinal": 138,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog Items",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md b/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
new file mode 100644
index 0000000..775b46d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
@@ -0,0 +1,19 @@
+# Catalog Items
+
+The Self Service catalog (Library > Blueprints > Catalog Items) is where administrators can create easily-deployable items for consumption by users operating under the “Service Catalog” Persona in HPE Morpheus Enterprise. Catalog items can be fully-configured HPE Morpheus Enterprise Instances or Blueprints, complete with user input through HPE Morpheus Enterprise Inputs, automation Workflows, and more. The catalog items are presented in a simplified interface for ease of deployment without sacrificing configurability for administrators. All available catalog items are built in the Self Service area and users will see relevant items in their catalogs based on Role permissions.
+
+NOTE
+
+For more on Personas and using the Service Catalog persona, see the Personas sections of our documentation.
+
+Access is granted to the Self Service section through the Library: Catalog Items Role permission. Users with Read rights can view the catalog while users with full rights can create and edit catalog items. Users without any rights to Self Service will not be able to access the page at all.
+
+Additionally, a user’s Role determines access to the standard and/or service catalog persona and which service catalog items are available for a user under the service catalog persona. See the Roles section of HPE Morpheus Enterprise documentation for more information on administering Roles.
+
+**Subtopics**  
+
+- **[Viewing the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html)**
+- **[Building Catalog Instances](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html)**
+- **[Building Catalog Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html)**
+- **[Building Catalog Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html)**
+- **[Editing and Deleting from the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json b/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
new file mode 100644
index 0000000..e0ca6ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+  "title": "Identity Management",
+  "ordinal": 487,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md b/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
new file mode 100644
index 0000000..5815bc2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
@@ -0,0 +1,9 @@
+# Identity Management
+
+**Subtopics**  
+
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6_2.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96_2.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E_2.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F_2.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json b/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
new file mode 100644
index 0000000..13cb3eb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+  "title": "Containers",
+  "ordinal": 478,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md b/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
new file mode 100644
index 0000000..414c83a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
@@ -0,0 +1,5 @@
+# Containers
+
+**Subtopics**  
+
+- **[Docker Registry](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json b/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
new file mode 100644
index 0000000..43d1330
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+  "title": "Commvault",
+  "ordinal": 383,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.html",
+  "topic_cluster": {
+    "clustering_title": "Commvault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md b/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
new file mode 100644
index 0000000..c2255c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
@@ -0,0 +1,97 @@
+# Commvault
+
+HPE Morpheus Enterprise integrates with Commvault for selection as a Cloud backup target. Compatible Clouds include VMware and OpenStack. HPE Morpheus Enterprise integrates with your existing Commvault appliance, which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Commvault with HPE Morpheus Enterprise, sharing a Commvault integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Commvault integration as the default backup target for compatible clouds
+- Select Commvault integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Commvault Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Services
+2. Select + ADD
+3. Select Commvault
+4. Fill in the following: 
+
+   Name
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enable the Commvault integration
+
+   Host
+   :   IP or Hostname of the Commvault server.
+
+   Port
+   :   Port number configured to access the Commvault server
+
+       TIP
+
+       Enter the port to connect with the Commvault web server, by default this is port 81. For more, see [Commvault port requirement documentation](https://documentation.commvault.com/11.24/essential/7102_port_requirements_for_commvault.html).
+
+   Username
+   :   Admin Username for Commvault
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. SAVE
+
+## Set Commvault as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Commvault integrations are supported as backup target for VMware and OpenStack Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware or OpenStack Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Commvault integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProviders.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-81075293-A540-4075-BAC0-19F608D18FA8-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Commvault is set as the backup provider, Commvault will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Commvault backup type
+- **Backup Server:** Select the desired server synced from the Commvault backup provider associated with the Cloud
+- **Backup Set:** Select a configured backup set synced from the Commvault backup provider associated with the Cloud
+- **Storage Policy:** Gold, Silver, or Bronze. Select the applicable SLA or retention policy for the workload being provisioned. The meanings of these retention tiers are configurable in Commvault
+- **Backup Name:** A name for the backup in HPE Morpheus Enterprise, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7E2EA78B-D0ED-4017-A07E-8815E86AB7D3-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Commvault
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
new file mode 100644
index 0000000..fbd9f51
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+  "title": "Overview",
+  "ordinal": 293,
+  "parent_title": "Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
new file mode 100644
index 0000000..00eb1cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
@@ -0,0 +1,11 @@
+# Overview
+
+Within HPE Morpheus Enterprise is a wide array of role based access control capabilities. These roles can be managed within the Admin > Roles section of the HPE Morpheus Enterprise UI as well as through the API or CLI. They are designed to be robust enough to fit within a wide array of enterprise and managed service provider scenarios so they can be a bit hard to grasp at first, but should make sense once a few simple concepts are explained. There are two types of roles within HPE Morpheus Enterprise called Tenant and User based roles. Both sets of roles allow restrictions to be imposed on a user at the feature access level. Entire sections within the appliance UI can be hidden based on the specified access levels for features within HPE Morpheus Enterprise. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full. Instance Type access is also common among both role types which allow the administrator to restrict which service catalog items they are allowed to provision within HPE Morpheus Enterprise .
+
+There are several handy tricks for creating new roles within HPE Morpheus Enterprise and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the HPE Morpheus Enterprise UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
new file mode 100644
index 0000000..539da9a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+  "title": "Linux OS Imaging",
+  "ordinal": 414,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html",
+  "topic_cluster": {
+    "clustering_title": "Linux OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
new file mode 100644
index 0000000..5d83976
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
@@ -0,0 +1,95 @@
+# Linux OS Imaging
+
+This section describes the supported Linux distributions and guides for deploying Linux on bare metal using Morpheus. It includes validated OS versions, required virtual image settings, boot loader configuration for unattended installation, and troubleshooting steps for common deployment issues (see Section Troubleshooting for more details).
+
+The following Linux distributions have been validated for deployment:
+
+- Red Hat Enterprise Linux (RHEL) and derivatives
+
+  - RHEL 9.5
+  - Oracle Linux 8.10
+  - Oracle Linux 9.5
+- Ubuntu Server
+
+  - Ubuntu Server 22.04.5 LTS
+  - Ubuntu Server 24.04.3 LTS
+
+## Virtual Image Configuration
+
+When adding a Linux ISO to Library > Virtual Images, ensure the following settings:
+
+- Operating System: Select the appropriate OS (e.g., RHEL 9, Oracle Linux 9, Ubuntu 22.04, Ubuntu 24.04)
+- Is Cloud Init Enabled: Checked
+- Advanced
+
+  - VM Tools Installed: Checked
+
+## Boot Prompt Configuration - RHEL and Oracle Linux
+
+Unmodified RHEL and Oracle Linux ISOs include a default boot menu entry: `Test this media & install OS`.
+
+This entry performs a **full media verification** before installation.
+
+NOTE
+
+- The media check does not cause installation failure.
+- It can, however, delay deployment by 30–60 minutes, particularly in remote or virtual media environments.
+- Skipping the media check is recommended to reduce installation time.
+
+**Supported Options**
+
+- Preferred: Modify the ISO
+  - Adjust the ISO boot loader to remove or bypass the media check from the default boot entry.
+  - Ensures faster, fully unattended deployment.
+- Alternative: Manual Boot Selection
+  - At boot: Select `Install OS` (without media test).
+  - Do NOT select `Test this media & install OS`.
+- **Reference**
+  - Grub menu example (for clarity):
+  - `0 → Install Red Hat Enterprise Linux 9.5`
+  - `1 → Test this media & install Red Hat Enterprise Linux 9.5`
+  - Default entry index `1` triggers the media check.
+- Changing the default to `0` or manually selecting `Install OS` skips verification.
+
+  
+![Test media and install](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-65FC9E75-A386-4A4A-A6BE-591A95640685-high.png)
+
+## Boot Prompt Configuration - Ubuntu Server
+
+Ubuntu Server requires kernel boot parameters to enable unattended installation using cloud-init autoinstall.
+
+Unmodified ISOs do not automatically perform unattended installation.
+
+## Required Manual Step (Unmodified ISO)
+
+At the GRUB boot menu:
+
+- Highlight the default Ubuntu entry.
+- Press **e** to edit.
+- Append the following kernel parameters: `autoinstall ds=nocloud`
+- Boot with the modified entry.
+- Example Boot Entry:
+
+  ```
+  ```
+  menuentry "Ubuntu" {  
+      set gfxpayload=keep  
+      linux   /casper/vmlinuz quiet autoinstall ds=nocloud ---  
+      initrd  /casper/initrd  
+  }
+  ```
+  ```
+
+This enables cloud-init–based unattended installation.
+
+## Licensing and Registration
+
+After installation, register the OS to receive updates and support.
+
+Table 1. License and Registration
+
+     | Distribution | Registration Reference | Notes |
+| --- | --- | --- |
+| RHEL | [Red Hat Subscription-Manager Registration Guide](https://access.redhat.com/solutions/253273?utm_source=chatgpt.com) | Use `subscription-manager` to register and attach subscriptions. |
+| Oracle Linux | [Registering Oracle Linux System with ULN](https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/registering-oracle-linux-system-uln.html?utm_source=chatgpt.com) | Use the `uln_register` tool to register with Oracle Unbreakable Linux Network. |
+| Ubuntu | [Ubuntu 24.04 LTS Release Notes](https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890) | Ubuntu does not require mandatory registration. An optional Ubuntu Pro subscription provides extended security maintenance and support. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
new file mode 100644
index 0000000..245371a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+  "title": "Networking",
+  "ordinal": 453,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html",
+  "topic_cluster": {
+    "clustering_title": "Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
new file mode 100644
index 0000000..16fe6b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
@@ -0,0 +1,15 @@
+# Networking
+
+| S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Cloud Network Mode Configuration | Cloud can operate in **Unmanaged** or **Managed (ArubaCX-Int)** network modes. This choice is made during cloud creation under **Advanced Options**. | Verify the correct network mode selected during cloud creation. | Morpheus UI log | Use Unmanaged for external network control; use Managed for Morpheus-managed ArubaCX switches. |
+| 2 | Unmanaged Network - Default Setup | In Unmanaged mode, Morpheus creates a minimal configuration: a default Resource Pool and a default unmanaged network. The default network is **untagged** and uses **DHCP**. | Ensure the DHCP server exists and the network is configured for an untagged VLAN. | Morpheus UI log | This allows instances to boot with connectivity without extra network configuration. |
+| 3 | Unmanaged Network - Additional VLANs | Users can create additional VLANs/networks as required. | Check VLAN configuration and availability in provisioning options. | Morpheus UI log | Additional networks can be consumed by bare-metal instances. |
+| 4 | Managed Network - ArubaCX Integration | Managed mode uses ArubaCX switches and requires the ArubaCX plugin. | Confirm the ArubaCX plugin is loaded in Morpheus. | Morpheus UI log | Managed networks allow Morpheus to configure VLANs on switches automatically. |
+| 5 | Adding HPE ArubaCX Plugin | The plugin must be loaded to enable managed network features. Follow the procedure Adding HPE BMaaS Integration to load the plugin JAR. | Verify plugin status in Morpheus. | Morpheus UI log | Required before creating network integrations. |
+| 6 | Creating ArubaCX Network Integration | Integration defines switch credentials and switch pairs (typically 2 per rack). | Verify switch IPs, username, and password are correct. | Morpheus UI log | One integration is needed per rack (switch pair). |
+| 7 | Creating Managed Networks | Networks represent VLANs and include attributes like subnet, gateway, DNS, and IP allocation method. | Ensure VLAN ID, trunks, and subnet are correct. | Morpheus UI log | Primary VLAN is untagged, VLAN trunks are tagged. |
+| 8 | Private Network Option | Private networks do not configure a primary VLAN on the uplink, making them inaccessible outside the cloud. | Confirm if the network should be private or public. | Morpheus UI log | Used for internal workload networks only. |
+| 9 | Network Consumption During Provisioning | Networks are attached to physical or bonded interfaces. Primary VLAN is untagged, trunk VLANs are tagged. | Check interface type (physical or bond) and correct VLAN assignment. | Morpheus UI log | Supports Static Bond, LACP Bond, and Switch Independent Bond. |
+| 10 | Bond Interface Configuration | Bond interfaces require two physical ports to form an aggregated link. | Ensure both physical ports are available and correctly mapped. | Morpheus UI log | Bonding provides bandwidth aggregation and redundancy. |
+| 11 | Virtual Network Interfaces | Virtual networks allow tagged VLANs to be configured as IP interfaces on the server OS. | Verify if tagged networks require an IP interface. | Morpheus UI log | If not needed, do not configure the virtual interface. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..fadddcc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 219,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..b4a6e2a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,41 @@
+# Routers
+
+## Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. HPE Morpheus Enterprise supports the creation of the following router types depending on networks that are currently configured:
+
+- Amazon Internet Gateway
+- Huawei Router
+- Neutron Router
+- NSX Edge Gateway
+- NSX Edge Logical Router
+- NSX Cloud Tier0 Gateway
+- NSX Cloud Tier1 Gateway
+- NSX Tier0 Gateway
+- NSX Tier1 Gateway
+- Open Telekom Router
+
+## Create New Router
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
+
+## Editing Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
+
+## Deleting Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
new file mode 100644
index 0000000..732210c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+  "title": "Avamar",
+  "ordinal": 387,
+  "parent_title": "Backups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.html",
+  "topic_cluster": {
+    "clustering_title": "Avamar",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
new file mode 100644
index 0000000..0d510b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
@@ -0,0 +1,57 @@
+# Avamar
+
+HPE Morpheus Enterprise integrates with an existing Avamar appliance which can then be set as the preferred backup solution for any compatible Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Avamar with Morpheus. Once the integration is complete, when editing or adding compatible Clouds, set the Avamar integration as the backup provider for the Cloud. At provision time, set Avamar backup configurations for the workload. When necessary, restore Instances from Avamar backup.
+
+IMPORTANT
+
+Avamar API must be installed on Avamar server (not installed by default)
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Avamar integration as the default backup target for compatible Clouds
+- Select Avamar integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Avamar Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Avamar
+4. Fill in the following: 
+
+   Name
+   :   Name for the Avamar integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When checked, the integration is selectable as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Avamar API server
+
+   Port
+   :   Port number configured to access the Avamar server
+
+   Username
+   :   Admin username for Avamar
+
+   Password
+   :   Password for the user provided. Choose to enter credentials locally or use a securely-stored credential set saved previously
+
+   Tenant
+   :   Avamar Tenant/Domain scoping for the integration
+
+   Hypervisor
+   :   Avamar Hypervisor scoping for the integration
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that adds the integration
+
+           Public
+           :   Available to Subtenants (Master Tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json b/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
new file mode 100644
index 0000000..b745a2a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+  "title": "Costing: Tenant Costing",
+  "ordinal": 60,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tenant Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md b/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
new file mode 100644
index 0000000..50e4e47
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
@@ -0,0 +1,31 @@
+# Costing: Tenant Costing
+
+![../_images/3tenantcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D08A61BD-C24A-4D73-82C0-45BAEBC26DCB-high.png)
+
+The Tenant Costing dashboard aggregates costing totals across all Tenants that meet the filters set on the dashboard. This information helps administrators track the current spend of each Tenant for the current monthly period. It also helps identify the costliest Tenants and to anticipate month-end costs for each individual Tenant.
+
+## Filters
+
+Filter the Tenants pulled into the dashboard by one or more of the following fields:
+
+- Tenant (all matched by search)
+- Cloud
+- Tenant (selected from dropdown)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Tenants that meet set filters:
+
+- **TENANTS:** The total number of Tenants that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Tenants meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Tenants meeting dashboard filters
+- **LAST MONTH:** The total spend in the prior month for all Tenants meeting dashboard filters
+
+## Tenant List
+
+Each Tenant that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Tenant:
+
+- **NAME:** The name given to the Tenant in HPE Morpheus Enterprise at the time of creation
+- **DESCRIPTION:** The Tenant description (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Tenant listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Tenant listed
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json b/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
new file mode 100644
index 0000000..60c0784
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+  "title": "AWS",
+  "ordinal": 389,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html",
+  "topic_cluster": {
+    "clustering_title": "AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md b/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
new file mode 100644
index 0000000..5f9cf6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
@@ -0,0 +1,959 @@
+# AWS
+
+## Overview
+
+AWS is the Amazon public cloud, offering a full range of services and features across the globe in various datacenters. AWS provides businesses with a flexible, highly scalable, and low-cost way to deliver a variety of services using open standard technologies as well as proprietary solutions. This section of documentation will help you get HPE Morpheus Enterprise and AWS connected to utilize the features below:
+
+## Features
+
+- Instance, Service, Infrastructure Provisioning & Synchronization
+- EKS Cluster Creation & Synchronization
+- HPE Morpheus Enterprise Kubernetes, Docker & KVM Cluster Creation
+- ELB Classic Load Balancer Creation & Synchronization
+- ELB Application Load Balancer (ALB) Creation & Synchronization
+- Security Group Creation & Synchronization
+- Security Group Rule Creation & Synchronization
+- Network Synchronization
+- VPC Creation & Synchronization
+- CloudFormation Provisioning & Resource Synchronization
+- Terraform Provisioning & Resource Synchronization
+- Pricing & Costing Synchronization
+- MetaData Tag Creation & Synchronization
+- S3 Bucket Creation & Synchronization
+- Route53 Automation & Synchronization
+- IAM Profile Synchronization and Assignment
+- RDS Support
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Remote Console (SSH & RDP)
+- Lifecycle Management and Resize
+- Restore from Snapshots
+- Elastic IP Assignment
+- Network Pools
+- Enhanced Invoice Costing
+
+## Requirements
+
+AWS IAM Security Credentials
+:   Access Key Secret Key Sufficient User Privileges (see [MinimumIAMPolicies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html#GUID-4A622A6F-E3FD-431B-B748-EF492C316D40) section for more info)
+
+Security Group Configuration for Agent Install, Script Execution, and Remote Console Access
+:   - Typical Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389 (22 & 3389 required for Console. 22 & 5985 required for agent-less comms)
+    - Typical Outbound to HPE Morpheus Enterprise Appliance: 443 (Required for Agent install & comms)
+
+    NOTE
+
+    These are required for HPE Morpheus Enterprise agent install, communication, and remote console access for windows and linux. Other configurations, such as docker instances, will need the appropriate ports opened as well. Cloud-init Agent Install mode does not require incoming access for port 22.
+
+Network(s)
+:   IP assignment required for Agent install, Script Execution, and Console if the HPE Morpheus Enterprise Appliance is not able to communicate with AWS instances private ip’s.
+
+## Adding an AWS Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud
+3. Select AWS
+4. Enter the following:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+#### About this task
+
+REGION
+:   Select AWS Region for the Cloud. AWS Clouds may also be scoped to all regions.
+
+ACCESS KEY
+:   Access Key ID from AWS IAM User Security Credentials.
+
+SECRET KEY
+:   Secret Access Key associated with the Access Key ID.
+
+USE HOST IAM CREDENTIALS
+:   Check to use use Host IAM Credentials
+
+ROLE ARN
+:   Supports security token service (STS) to AssumeRole by entering an AWS Role ARN
+
+EXTERNAL ID
+:   When required to AssumeRole, included the needed External ID
+
+INVENTORY
+:   Basic
+    :   HPE Morpheus Enterprise will sync information on all EC2 Instances in the selected VPC the IAM user has access to, including Name, IP Addresses, Platform Type, Power Status, and overall resources sizing for Storage, CPU and RAM, every 5 minutes. Inventoried EC2 Instances will appear as Unmanaged VM’s.
+
+    Full
+    :   In addition to the information synced from Basic Inventory level, HPE Morpheus Enterprise will gather Resource Utilization metrics for Memory, Storage and CPU utilization per VM.
+
+    Off
+    :   Existing EC2 Instances will not be inventoried
+
+    NOTE
+
+    Cloud Watch must be configured in AWS for HPE Morpheus Enterprise to collect Memory and Storage utilization metrics on inventoried EC2 instances.
+
+USE VPC
+:   Specify if the target account is using EC2-VPC or EC2-Classic Platform. In almost all cases, VPC should be selected, and then select the target VPC from the synced available VPC’s list, or All VPC’s.
+
+#### Procedure
+
+The AWS cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+IMAGE TRANSFER STORE
+:   S3 bucket for Image transfers, required for migrations into AWS.
+
+EBS ENCRYPTION
+:   Enable or disable encryption of EBS Volumes
+
+COSTING KEY
+:   For Gov Cloud pricing only, key for standard managing cost account
+
+COSTING SECRET
+:   For Gov Cloud pricing only, secret for standard managing cost account
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+KMS KEY ID
+:   For specify an AWS KMS key for encrypting EBS Volumes when volume encryption is enabled
+
+## Provisioning and Keypairs
+
+During provisioning, users do not need to create or select a keypair as you would do when provisioning directly from the AWS console. If needed, HPE Morpheus Enterprise will create an AWS keypair without input from the user. In the AWS console and in the HPE Morpheus Enterprise Keypairs Section (Infrastructure > Trust > Key Pairs) you will see these keypairs listed. HPE Morpheus Enterprise will also inventory other keypairs which are created in your integrated AWS clouds and these will be listed out in the HPE Morpheus Enterprise Keypairs section.
+
+These created keypairs are not accessible to the user as you do not see them at creation time and they are encrypted as stored in the HPE Morpheus Enterprise database. To have access to the Instance after provisioning, the user should have his or her user created during provisioning. This is done by creating a Linux user in HPE Morpheus Enterprise [User Settings](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html#linux-settings) and associating a keypair with the user. If you don’t currently have a keypair to use, HPE Morpheus Enterprise can generate one for you in the Keypairs section.
+
+![../../../_images/userKeypair.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A382092A-E8E1-4130-835B-6700A0619EDB-high.png)
+
+With your user set in HPE Morpheus Enterprise User Settings, ensure that your user is being created during Instance provisioning. On the CONFIGURE tab of the Instance provisioning wizard, mark the “CREATE YOUR USER” box. This is normally checked by default if a user is configured in HPE Morpheus Enterprise User Settings but you can confirm that here.
+
+![../../../_images/createUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5670B0FB-6FFF-4925-860C-C8117AA15A1C-high.png)
+
+It’s worth noting that adding your user to the provisioned workload does not replace the keypair used by HPE Morpheus Enterprise during provisioning. Instead it adds the public key for your user to the authorized keys file on the workload which allows you to access it. You can confirm this by catting out the authorized key file on any of your HPE Morpheus Enterprise-provisioned workloads (~/.ssh/authorized\_keys). You will at least see two keys, one for the HPE Morpheus Enterprise service user and one for your own user.
+
+NOTE
+
+In general it should not cause problems if HPE Morpheus Enterprise-generated keypairs are deleted from the AWS console or from the HPE Morpheus Enterprise keypairs section. You would not lose console access to the VM. If needed, however, HPE Morpheus Enterprise will create more keypairs and there is currently no functionality to automatically remove these keypairs. They can be safely ignored, generally speaking there is no need to manually delete them.
+
+## Enhanced Invoice Costing Configuration
+
+AWS cloud integrations in HPE Morpheus Enterprise will sync highly-granular costing data through the use of AWS Costing & Utilization Reports (CUR). If desired, users can turn on costing in the HPE Morpheus Enterprise Cloud configuration without linking a CUR to use AWS Cost Explorer instead. HPE Morpheus Enterprise version 4.2.3 also simplified the way CUR reports can be selected or created in order to sync costing data. The section below discusses setting up enhanced costing through CUR reports both in 4.2.3 and versions prior. For additional details on setting up costing with AWS GovCloud, see the next section.
+
+NOTE
+
+Even with a costing report configured in the Cloud integration as described below, the COSTING value must also be set to “Costing and Reservations” in order for enhanced invoice data to be brought into HPE Morpheus Enterprise. Confirm this setting by editing the Amazon Cloud integration, and checking the COSTING value in the Advanced Options panel before continuing.
+
+**v4.2.3 and Above**
+
+In HPE Morpheus Enterprise 4.2.3+, edit the Amazon cloud integration or create a new Amazon Cloud to get started. On the Create/Edit Cloud modal, open the advanced options section. The relevant fields for configuring invoice costing are shown below:
+
+![../../../_images/0billingFields.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6603376C-13FF-4A08-BCE0-30DD28A95B76-high.png)
+
+In the example case above, a new report and a new S3 bucket are created but HPE Morpheus Enterprise will also sync in buckets and reports that meet the required parameters if they already exist. For reports to be synced they must meet the requirements listed below:
+
+- Hourly time granularity
+- Include resource IDs
+- GZIP compression
+- CSV format
+
+If you don’t currently have a report meeting those criteria, you can create one by selecting “New Report” from the REPORT NAME dropdown menu. A new S3 bucket can be created in similar fashion if needed. You may also want to review the section below on configuration for HPE Morpheus Enterprise 4.2.2 and below to note policies that will be applied to your selected bucket and Cost Explorer permissions required for the AWS cloud user associated with the HPE Morpheus Enterprise Cloud integration.
+
+In the end, the following fields must be filled in order to complete the process:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+Using the HPE Morpheus Enterprise interface to create a CUR, and optionally a new S3 bucket, the IAM user requires permissions in AWS to be successful. By default, only the root user will have access to billing (including CUR), but billing can be enabled for IAM users following Amazon’s documentation for [Activating IAM Access](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/control-access-billing.html). Once IAM access is activated, policies need to be assigned to the user being configured on the cloud in HPE Morpheus Enterprise. If the user is an administrator of the AWS account, no additional policies are needed. Below are some example policies needed for different scenarios:
+
+Creating a new CUR and new S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:PutBucketPolicy",  
+              "s3:CreateBucket",  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Creating a new CUR and using an existing S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Using an existing CUR
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+IMPORTANT
+
+The user configured on the cloud will need access to the objects in the S3 bucket configured on the CUR. If creating the CUR via the HPE Morpheus Enterprise UI, this should be done automatically. If an existing CUR report or existing S3 bucket was selected, ensure the user has permissions to access the objects in the configured S3 bucket. Alternatively, the **COSTING KEY** and **COSTING SECRET** can be used to configure a different user that has access to the S3 bucket.
+
+**v4.2.2 and Below**
+
+Begin by logging into the [AWS Billing Console](https://console.aws.amazon.com/billing/home?#/), then click Create report.
+
+![../../../_images/1billingConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6DE8607B-F2EC-42DB-ABD4-570B5A337D97-high.png)
+
+Include a name for your report and mark the box to “Include resource IDs”. HPE Morpheus Enterprise uses these resource IDs to map costs to various resources. Click Next.
+
+![../../../_images/2reportConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BAA21B68-8956-49FD-958B-97FC16160E26-high.png)
+
+On the following page, begin by identifying an S3 bucket to house reports. Click Configure near the top of the page and select an existing bucket or create a new one.
+
+![../../../_images/4chooseBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7D2040F4-3B7E-4CE5-82C7-2373F73C9F42-high.png)
+
+After identifying the bucket, you must mark the box to accept the default policy being applied to the bucket. Click Save.
+
+![../../../_images/5confirmPolicy.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5BDEF27D-8DC9-4554-A3D0-DAC2B41DEEEE-high.png)
+
+The default policy applied to the bucket is below:
+
+```
+```
+{  
+  "Version": "2008-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:GetBucketAcl",  
+        "s3:GetBucketPolicy"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name"  
+    },  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:PutObject"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name/*"  
+    }  
+  ]  
+}
+```
+```
+
+After choosing a bucket, accepting the default policy, and saving the change, you’re brought back to the report delivery page. By default, CUR reports are saved to a folder at the path `my-report-name/date-folder`. If this bucket already contains CUR reports, you may want to specify a prefix path in the “Report path prefix” field. Outside of this field, use the default values as shown in the screenshot below, then click Next.
+
+![../../../_images/6completeDelivery.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DBCE8764-455B-450D-9C77-F16E527402D5-high.png)
+
+On the following page, make your final review and click Review and Complete. Following this, you will see your newly configured report in the list of CUR report(s).
+
+In addition, the AWS cloud user associated with the integration in HPE Morpheus Enterprise needs IAM policy permission to access Cost Explorer. Attach a policy like the one below to this cloud user:
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Action": [  
+        "ce:DescribeReportDefinitions",  
+        "ce:DescribeCostCategoryDefinition",  
+        "ce:ListCostCategoryDefinitions"  
+      ],  
+      "Resource": [  
+        "*"  
+      ]  
+    }  
+  ]  
+}
+```
+```
+
+NOTE
+
+If the Cost Explorer permissions are granted at the master account level, the user will see all costs for each member account; if granted at the member account, only the costs for that member account are available.
+
+With the AWS console configuration steps complete, we can move back into HPE Morpheus Enterprise. Keep in mind it is only necessary to set up one AWS cloud for Costing since we process all records in the CUR report.
+
+Once back in HPE Morpheus Enterprise, add or edit the relevant AWS cloud integration (Infrastructure > Clouds > + ADD OR click the pencil icon in the row for the chosen AWS integration). Expand the Advanced Options drawer and complete the following fields:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+![../../../_images/7morphConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C5CA9E0D-35CE-4209-BAD7-B2091E1795EC-high.png)
+
+Save changes to your cloud integration.
+
+IMPORTANT
+
+It may take as long as one hour for HPE Morpheus Enterprise to process the next CUR report.
+
+### Global (Costing Aggregator Only) (v5.5.1+)
+
+Costing can be created for specific clouds individually, following the steps previously mentioned. If the same account is added multiple times, using different regions, the same CUR file is available to be selected (if the configured user has access). However, this can become a tedious process in needing to configure the CUR on each cloud added to HPE Morpheus Enterprise. However, HPE Morpheus Enterprise has a region of Global (Costing Aggregator Only), which can be chosen at the time of adding a cloud. This region is not designed for deploying workloads, it is here primarily for syncing costs. This means that the AWS account added as a cloud in HPE Morpheus Enterprise as a Global region can sync the cost for all the other regions of the same account added as clouds into HPE Morpheus Enterprise. When using AWS Organizations, if the AWS account added as a global region is the management account (formerly known as master account) and consolidated billing is enabled, costs for **all** accounts can be sync’d using the Global region. This means when any AWS and/or regions in the organization are added as clouds in HPE Morpheus Enterprise, the appropriate costs are applied to them automatically. It does require that **Costing** is enabled on the cloud to see the costs but a Costing Report does not need to be chosen. This enables the use of one cloud added as Global to sync all costs and apply to all AWS clouds added in HPE Morpheus Enterprise. Additionally, some costs in AWS are not region specific, for example the Global and No Region regions. These costs do not apply to the regions of the clouds added in HPE Morpheus Enterprise. With the Global region added as a cloud in HPE Morpheus Enterprise, you would be able to see these costs that are applicable to your accounts.
+
+## Costing and AWS GovCloud
+
+### About this task
+
+AWS GovCloud delivers Amazon public cloud infrastructure and features in a way that complies with U.S. government standards for security. GovCloud accounts are applied for and must be associated with a pre-existing standard AWS account and the usage and billing data for the GovCloud account is rolled up into that of the standard AWS account. For that reason, Amazon recommends creating a new standard account solely to house the GovCloud account if usage and billing must be tracked separately.
+
+Since GovCloud accounts do not have access to billing data directly, HPE Morpheus Enterprise must be able to access it through the associated standard account. You could do this by creating the HPE Morpheus Enterprise cloud integration through the standard account itself or by integrating the GovCloud account and supplying an Access Key and Secret Key for the standard account when configuring costing. When needed, add the additional credentials for the standard commercial account as described below:
+
+### Procedure
+
+1. Add a new AWS Cloud or edit an existing one
+2. Expand the Advanced Options section
+3. Complete the following fields in addition to other required fields needed to set up costing as described in the previous section: 
+
+   - COSTING KEY: The AWS Key ID for an IAM user with sufficient access who is associated with the standard commercial account
+   - COSTING SECRET: The AWS Secret Key for an IAM user with sufficient access who is associated with the standard commercial account
+   - LINKED ACCOUNT ID: The AWS account number for the standard commercial account in which the IAM user referenced in the prior bullets resides
+4. Save the changes to the AWS Cloud integration
+
+### Results
+
+When credentials are configured correctly, you will be able to select an existing Costing and Usage Report (CUR) from the appropriate S3 bucket if it already exists. If not, you can create one directly from the add/edit AWS Cloud modal in HPE Morpheus Enterprise.
+
+![../../../_images/8govcloudCosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AC3216FF-1BBA-4E49-808F-3B612BC88276-high.png)
+
+## AWS Reserved Instances and Savings Plans
+
+Amazon AWS public cloud offers Reserved Instances (RI) and Savings Plans, which allow organizations with consistent use patterns to reduce cloud spend significantly. HPE Morpheus Enterprise analyzes AWS cloud usage and spend, which allows it to make intelligent recommendations that can lead to significant savings. This data can be reviewed in the Reservation Recommendations and Savings Plan Recommendations tables on any AWS Cloud detail page (Infrastructure > Clouds > Selected Amazon Cloud).
+
+Savings Plans potentially offer greater than 70% savings in exchange for a commitment to consistent usage levels for a 1- or 3-year term. HPE Morpheus Enterprise provides Savings Plan guidance based on learned analytics; allowing you to analyze Savings Plans based on different term commitments and upfront costs to choose the best savings plan.
+
+![../../../_images/savingsPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ED40B92B-4283-4FD5-9536-06034CC07CC0-high.png)
+
+Reserved Instances (RI) provide a discounted hourly rate and optional capacity reservation for EC2 instances. AWS billing automatically applies your RI-discounted rate when the attributes of EC2 instance usage match attributes of an active RI. HPE Morpheus Enterprise provides RI guidance based on learned analytics.
+
+![../../../_images/ri.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A93A0997-98E0-4177-91AF-1CC07D579581-high.png)
+
+To retrieve Reserved Instances and Savings Plans data, the user configured on the cloud will require access to **Cost Explorer**. Below is an example IAM policy with Cost Explorer access:
+
+### Cost Explorer Policy
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "ce:*"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+## AWS IAM Permissions
+
+Below are the AWS IAM Permissions required for HPE Morpheus Enterprise services.
+
+### autoscaling
+
+```
+```
+"autoscaling:AttachInstances",  
+"autoscaling:AttachLoadBalancerTargetGroups",  
+"autoscaling:CreateAutoScalingGroup",  
+"autoscaling:DeleteAutoScalingGroup",  
+"autoscaling:DeleteLaunchConfiguration",  
+"autoscaling:DeletePolicy",  
+"autoscaling:DescribeAutoScalingGroups",  
+"autoscaling:DescribeLaunchConfigurations",  
+"autoscaling:DescribeLoadBalancers",  
+"autoscaling:DescribePolicies",  
+"autoscaling:DetachInstances",  
+"autoscaling:PutScalingPolicy",  
+"autoscaling:UpdateAutoScalingGroup",
+```
+```
+
+### cloudformation
+
+```
+```
+"cloudformation:CreateStack",  
+"cloudformation:DeleteStack",  
+"cloudformation:DescribeStackEvents",  
+"cloudformation:DescribeStackResources",  
+"cloudformation:DescribeStacks",  
+"cloudformation:GetTemplate",  
+"cloudformation:UpdateStack",  
+"cloudformation:ValidateTemplate",
+```
+```
+
+### cloudwatch
+
+```
+```
+"cloudwatch:DeleteAlarms",  
+"cloudwatch:DescribeAlarms",  
+"cloudwatch:GetMetricStatistics",  
+"cloudwatch:PutMetricAlarm",
+```
+```
+
+### costexplorer
+
+```
+```
+"ce:*",
+```
+```
+
+### Cost and Usage Reports
+
+```
+```
+"cur:DescribeReportDefinitions",  
+"cur:PutReportDefinition",
+```
+```
+
+### ec2
+
+```
+```
+"ec2:AllocateAddress",  
+"ec2:AssignPrivateIpAddresses",  
+"ec2:AssociateAddress",  
+"ec2:AttachInternetGateway",  
+"ec2:AttachNetworkInterface",  
+"ec2:AttachVolume",  
+"ec2:AuthorizeSecurityGroupEgress",  
+"ec2:AuthorizeSecurityGroupIngress",  
+"ec2:CancelExportTask",  
+"ec2:CancelImportTask",  
+"ec2:CopyImage",  
+"ec2:CopySnapshot",  
+"ec2:CreateEgressOnlyInternetGateway",  
+"ec2:CreateImage",  
+"ec2:CreateInstanceExportTask",  
+"ec2:CreateInternetGateway",  
+"ec2:CreateKeyPair",  
+"ec2:CreateNatGateway",  
+"ec2:CreateNetworkAcl",  
+"ec2:CreateNetworkAclEntry",  
+"ec2:CreateNetworkInterface",  
+"ec2:CreateRoute",  
+"ec2:CreateSecurityGroup",  
+"ec2:CreateSnapshot",  
+"ec2:CreateSubnet",  
+"ec2:CreateTags",  
+"ec2:CreateVolume",  
+"ec2:CreateVpc",  
+"ec2:DeleteEgressOnlyInternetGateway",  
+"ec2:DeleteInternetGateway",  
+"ec2:DeleteKeyPair",  
+"ec2:DeleteNatGateway",  
+"ec2:DeleteNetworkAcl",  
+"ec2:DeleteNetworkAclEntry",  
+"ec2:DeleteNetworkInterface",  
+"ec2:DeleteRoute",  
+"ec2:DeleteSecurityGroup",  
+"ec2:DeleteSnapshot",  
+"ec2:DeleteSubnet",  
+"ec2:DeleteTags",  
+"ec2:DeleteVolume",  
+"ec2:DeleteVpc",  
+"ec2:DeregisterImage",  
+"ec2:DescribeAccountAttributes",  
+"ec2:DescribeAddresses",  
+"ec2:DescribeAvailabilityZones",  
+"ec2:DescribeClassicLinkInstances",  
+"ec2:DescribeClientVpnConnections",  
+"ec2:DescribeClientVpnEndpoints",  
+"ec2:DescribeConversionTasks",  
+"ec2:DescribeEgressOnlyInternetGateways",  
+"ec2:DescribeExportTasks",  
+"ec2:DescribeImageAttribute",  
+"ec2:DescribeImages",  
+"ec2:DescribeImportImageTasks",  
+"ec2:DescribeImportSnapshotTasks",  
+"ec2:DescribeInstances",  
+"ec2:DescribeInstanceStatus",  
+"ec2:DescribeInstanceTypes",  
+"ec2:DescribeInternetGateways",  
+"ec2:DescribeKeyPairs",  
+"ec2:DescribeNatGateways",  
+"ec2:DescribeNetworkAcls",  
+"ec2:DescribeNetworkInterfaceAttribute",  
+"ec2:DescribeNetworkInterfaces",  
+"ec2:DescribeRegions",  
+"ec2:DescribeRouteTables",  
+"ec2:DescribeSecurityGroupReferences",  
+"ec2:DescribeSecurityGroups",  
+"ec2:DescribeSnapshotAttribute",  
+"ec2:DescribeSnapshots",  
+"ec2:DescribeStaleSecurityGroups",  
+"ec2:DescribeSubnets",  
+"ec2:DescribeTags",  
+"ec2:DescribeTransitGateways",  
+"ec2:DescribeTransitGatewayVpcAttachments",  
+"ec2:DescribeVolumeAttribute",  
+"ec2:DescribeVolumes",  
+"ec2:DescribeVolumeStatus",  
+"ec2:DescribeVpcAttribute",  
+"ec2:DescribeVpcClassicLink",  
+"ec2:DescribeVpcClassicLinkDnsSupport",  
+"ec2:DescribeVpcEndpoints",  
+"ec2:DescribeVpcEndpointServices",  
+"ec2:DescribeVpcPeeringConnections",  
+"ec2:DescribeVpcs",  
+"ec2:DescribeVpnGateways",  
+"ec2:DetachInternetGateway",  
+"ec2:DetachNetworkInterface",  
+"ec2:DetachVolume",  
+"ec2:DisassociateAddress",  
+"ec2:GetPasswordData",  
+"ec2:ImportImage",  
+"ec2:ImportInstance",  
+"ec2:ImportKeyPair",  
+"ec2:ImportSnapshot",  
+"ec2:ImportVolume",  
+"ec2:ModifyImageAttribute",  
+"ec2:ModifyInstanceAttribute",  
+"ec2:ModifyNetworkInterfaceAttribute",  
+"ec2:ModifySnapshotAttribute",  
+"ec2:ModifySubnetAttribute",  
+"ec2:ModifyVolumeAttribute",  
+"ec2:RebootInstances",  
+"ec2:RegisterImage",  
+"ec2:ReleaseAddress",  
+"ec2:ReplaceNetworkAclAssociation",  
+"ec2:ReplaceNetworkAclEntry",  
+"ec2:ResetImageAttribute",  
+"ec2:ResetInstanceAttribute",  
+"ec2:ResetNetworkInterfaceAttribute",  
+"ec2:ResetSnapshotAttribute",  
+"ec2:RevokeSecurityGroupEgress",  
+"ec2:RevokeSecurityGroupIngress",  
+"ec2:RunInstances",  
+"ec2:StartInstances",  
+"ec2:StopInstances",  
+"ec2:TerminateInstances",  
+"ec2:UnassignPrivateIpAddresses",  
+"ec2:UpdateSecurityGroupRuleDescriptionsEgress",
+```
+```
+
+### eks
+
+```
+```
+"eks:*",
+```
+```
+
+### elasticloadbalancing
+
+```
+```
+"elasticloadbalancing:AddTags",  
+"elasticloadbalancing:ApplySecurityGroupsToLoadBalancer",  
+"elasticloadbalancing:AttachLoadBalancerToSubnets",  
+"elasticloadbalancing:CreateListener",  
+"elasticloadbalancing:CreateLoadBalancer",  
+"elasticloadbalancing:CreateRule",  
+"elasticloadbalancing:CreateTargetGroup",  
+"elasticloadbalancing:DeleteListener",  
+"elasticloadbalancing:DeleteLoadBalancer",  
+"elasticloadbalancing:DeleteRule",  
+"elasticloadbalancing:DeleteTargetGroup",  
+"elasticloadbalancing:DescribeLoadBalancers",  
+"elasticloadbalancing:DescribeRules",  
+"elasticloadbalancing:DescribeTargetGroups",  
+"elasticloadbalancing:ModifyListener",  
+"elasticloadbalancing:ModifyTargetGroupAttributes",  
+"elasticloadbalancing:RegisterTargets",  
+"elasticloadbalancing:SetSecurityGroups",  
+"elasticloadbalancing:SetSubnets",
+```
+```
+
+### elasticsearch
+
+```
+```
+"es:DescribeElasticsearchDomains",  
+"es:ListDomainNames",
+```
+```
+
+### iam
+
+```
+```
+"iam:ListGroups",  
+"iam:ListInstanceProfiles",  
+"iam:ListRoles",
+```
+```
+
+### kms
+
+```
+```
+"kms:Decrypt",  
+"kms:GenerateDataKey",
+```
+```
+
+### rds
+
+```
+```
+"rds:AddRoleToDBCluster",  
+"rds:AddTagsToResource",  
+"rds:ApplyPendingMaintenanceAction",  
+"rds:AuthorizeDBSecurityGroupIngress",  
+"rds:CopyDBClusterSnapshot",  
+"rds:CopyDBParameterGroup",  
+"rds:CopyDBSnapshot",  
+"rds:CreateDBCluster",  
+"rds:CreateDBClusterSnapshot",  
+"rds:CreateDBInstance",  
+"rds:CreateDBInstanceReadReplica",  
+"rds:CreateDBSecurityGroup",  
+"rds:CreateDBSnapshot",  
+"rds:DeleteDBCluster",  
+"rds:DeleteDBInstance",  
+"rds:DeleteDBSecurityGroup",  
+"rds:DeleteDBSnapshot",  
+"rds:DescribeAccountAttributes",  
+"rds:DescribeCertificates",  
+"rds:DescribeDBClusterParameterGroups",  
+"rds:DescribeDBClusterParameters",  
+"rds:DescribeDBClusters",  
+"rds:DescribeDBClusterSnapshotAttributes",  
+"rds:DescribeDBClusterSnapshots",  
+"rds:DescribeDBEngineVersions",  
+"rds:DescribeDBInstances",  
+"rds:DescribeDBLogFiles",  
+"rds:DescribeDBParameterGroups",  
+"rds:DescribeDBParameters",  
+"rds:DescribeDBSecurityGroups",  
+"rds:DescribeDBSnapshotAttributes",  
+"rds:DescribeDBSnapshots",  
+"rds:DescribeDBSubnetGroups",  
+"rds:DescribeEngineDefaultClusterParameters",  
+"rds:DescribeEngineDefaultParameters",  
+"rds:DescribeEventCategories",  
+"rds:DescribeEvents",  
+"rds:DescribeOptionGroupOptions",  
+"rds:DescribeOptionGroups",  
+"rds:DescribeOrderableDBInstanceOptions",  
+"rds:ListTagsForResource",  
+"rds:ModifyDBCluster",  
+"rds:ModifyDBClusterParameterGroup",  
+"rds:ModifyDBClusterSnapshotAttribute",  
+"rds:ModifyDBInstance",  
+"rds:ModifyDBParameterGroup",  
+"rds:ModifyDBSnapshotAttribute",  
+"rds:PromoteReadReplica",  
+"rds:RebootDBInstance",  
+"rds:RemoveTagsFromResource",  
+"rds:RestoreDBClusterFromSnapshot",  
+"rds:RestoreDBClusterToPointInTime",  
+"rds:RestoreDBInstanceFromDBSnapshot",  
+"rds:RestoreDBInstanceToPointInTime",  
+"rds:RevokeDBSecurityGroupIngress",  
+"rds:StartDBInstance",  
+"rds:StopDBInstance",
+```
+```
+
+### route53
+
+```
+```
+"route53:ChangeResourceRecordSets",  
+"route53:GetHostedZone",  
+"route53:ListHostedZones",  
+"route53:ListResourceRecordSets",
+```
+```
+
+### s3
+
+```
+```
+"s3:AbortMultipartUpload",  
+"s3:CreateBucket",  
+"s3:DeleteBucket",  
+"s3:DeleteObject",  
+"s3:DeleteObjectVersion",  
+"s3:GetBucketLocation",  
+"s3:GetBucketPolicy",  
+"s3:GetObject",  
+"s3:GetObjectVersion",  
+"s3:ListAllMyBuckets",  
+"s3:ListBucket",  
+"s3:ListBucketMultipartUploads",  
+"s3:ListBucketVersions",  
+"s3:ListMultipartUploadParts",  
+"s3:PutBucketPolicy",  
+"s3:PutObject",
+```
+```
+
+### Systems Manager
+
+```
+```
+"ssm:GetParameters",
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json b/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
new file mode 100644
index 0000000..b638dab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+  "title": "Cannot Login",
+  "ordinal": 349,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html",
+  "topic_cluster": {
+    "clustering_title": "Cannot Login",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md b/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
new file mode 100644
index 0000000..d8cc326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
@@ -0,0 +1,34 @@
+# Cannot Login
+
+## Forgot password
+
+If a user forgets their password, they can use the FORGOT PASSWORD? link on the login page. They can then enter their username or email address to send a reset password email to the email address defined on the user.
+
+If the default or user added SMTP server is not functioning or blocked, a System Admin user can impersonate that user and update their password.
+
+If the System Admin user password needs to be reset and the default or user added SMTP server is not functioning or blocked, please contact Morpheus support for assistance.
+
+## Sub-Tenant user cannot login after 3.4.0 upgrade
+
+HPE Morpheus Enterprise v3.4.0 added support for all subtenant users to login via the main tenant url using subtenant id or subdomain prefix, ie `tenantId\username` or `subdomain\username`.
+
+NOTE
+
+Tenant subdomains can be defined by editing Tenant settings and updating the SUBDOMAIN field.
+
+IMPORTANT
+
+Subtenant local users will no longer be able to login from main login url without using their subtenant id or subdomain prefix.
+
+The login requirements were added in v3.4.0 to allow subtenant users with identity source integration generated user accounts to be able to login to the master tenant, gain API and CLI access, and remove the requirement for usernames to be unique across all tenants.
+
+Previously subtenant users that had local/morpheus generated user accounts could login to their tenant via the master tenant url, while subtenant users that had identity source integration generated user accounts had to use the subtenant specific login url.
+
+In v3.4.0+ all subtenant users can login via the master tenant url by specifying their tenant id or subdomain prefix, `\`, then username. Subtenants can still use the tenant specific login url as well.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `acme` and tenant id `58`. When logging in from the main login url, I now need to enter in: `acme\subuser` and the password. Alternatively the tenant ID can be used, ie `58\subuser`
+
+## Active Directory user suddenly cannot Login
+
+In HPE Morpheus Enterprise v3.4.0 and prior, OU changes in Active Directory can disable logins for AD users who had previously authenticated/have existing user accounts in HPE Morpheus Enterprise. If an Active Directory user cannot login to HPE Morpheus Enterprise after their OU was changed in AD, please contact Morpheus support for a resolution. The OU association for the user(s) can also be manually updated in the database. This issue is resolved in HPE Morpheus Enterprise versions 3.4.1 and higher.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json b/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
new file mode 100644
index 0000000..e5ea32d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+  "title": "Execute Scheduling",
+  "ordinal": 124,
+  "parent_title": "Automation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md b/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
new file mode 100644
index 0000000..32fac17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
@@ -0,0 +1,36 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for Jobs, including Task, Workflow and Backup Jobs. Jobs, which are discussed in greater detail in [another section](https://docs.morpheusdata.com/en/4.2.0/provisioning/jobs/jobs.html#jobs) of HPE Morpheus Enterprise docs, combine either a Task or Workflow with an Execute Schedule to run the selected Task or Workflow at the needed time. Backup Jobs are a special type of Job configured in the Backups section which also use Execute Schedules to time backup runs as needed.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). HPE Morpheus Enterprise execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+## Create Execution Schedules
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that references the time interval is often helpful
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+VISIBILITY
+:   Master Tenant administrators may share Execute Schedules with Subtenants by setting the visibility to Public
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json b/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
new file mode 100644
index 0000000..a212be9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+  "title": "Network Connectivity",
+  "ordinal": 6,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Connectivity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md b/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
new file mode 100644
index 0000000..b5f60e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
@@ -0,0 +1,7 @@
+# Network Connectivity
+
+HPE Morpheus Enterprise primarily operates via communication with its Agent that is installed on all managed VMs or docker hosts. This is a lightweight agent responsible for aggregating logs and stats and sending them back to the client with minimal network traffic overhead. It also is capable of processing instructions related to provisioning and deployments instigated by the appliance server.
+
+The HPE Morpheus Enterprise Agent exists for both Linux and Windows-based platforms and opens NO ports on the guest operating system. Instead it makes an outbound SSL (HTTPS/WSS) connection to the appliance server. This is what is known as the `appliance url` during configuration (in Administration > Settings). When the Agent is started it automatically makes this connection and securely authenticates. Therefore, it is necessary for all VMs and docker based hosts that are managed by HPE Morpheus Enterprise to be able to reach the appliance server IP on port 443.
+
+HPE Morpheus Enterprise has numerous methods to execute Agent installation, including zero open port methods.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json b/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
new file mode 100644
index 0000000..9a6165d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+  "title": "Overview",
+  "ordinal": 275,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md b/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
new file mode 100644
index 0000000..a6c325a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
@@ -0,0 +1,11 @@
+# Overview
+
+A Tenant in HPE Morpheus Enterprise is an isolated environment with unique users and workloads. The Master Tenant is the default Tenant in HPE Morpheus Enterprise, created upon installation. All other Tenants outside of the Master Tenants are Subtenants. These terms are useful in differentiating the Master Tenant (which has a few special privileges) from Subtenants for the sake of discussion but within the product, all Tenants are known simply as Tenants.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The first layer of new Tenants (subtenants) is created from the Master Tenant. Created Tenants may have Tenants of their own
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants. Subtenants may only assign resources to its first layer of children Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant from a higher level Tenant
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json b/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
new file mode 100644
index 0000000..73b2f3d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+  "title": "Remote Storage",
+  "ordinal": 456,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md b/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
new file mode 100644
index 0000000..c001297
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
@@ -0,0 +1,14 @@
+# Remote Storage
+
+Table 1. Remote Storage
+
+        | S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Failure to Integrate HPE Alletra MP Plugin | Issues during plugin loading or integration of the HPE Alletra MP plugin in the Morpheus Enterprise environment. | - Confirm that the plugin `.jar` file is properly loaded as per section 5.2 “Adding HPE BMaaS Integration”. - Check if the correct credentials and URL for the storage array are used. | - **Plugin Logs**: Look for errors during plugin loading. - **System Logs**: Check for authentication or configuration failures. | - Ensure compatibility between the plugin version and Morpheus Enterprise. - Network/firewall issues may prevent communication with the storage array. |
+| 2 | Storage Server Creation Failure | Failure when adding a new storage server (URL, credentials, or type mismatch). | - Verify the URL and credentials for accessing the storage array. - Ensure the correct type (“HPE Alletra Block Storage HVM”) is selected. | - **Storage Server Logs**: Check for error messages related to server creation (authentication issues, network problems). | - An incorrect URL or credentials can prevent server creation. - Make sure the storage server is accessible and reachable from the Morpheus interface. |
+| 3 | Datastore Creation Failure | Issues while creating a datastore, such as selecting an incorrect storage server, or specifying incompatible resource pools or protocols. | - Verify that the storage server was created successfully. - Ensure correct datastore type and resource pool selection. - Ensure "FC" is selected for protocol. | - **Datastore Logs**: Check for errors when trying to create the datastore (incorrect type, wrong resource pool). | - Mismatched storage configuration or resource pool selection can lead to datastore creation failures. - Confirm network configurations for FC protocol. |
+| 4 | Volume Creation Issues | Errors when creating volumes, including failure to assign the correct size, volume type (replicated/unreplicated), or datastore. | - Ensure the storage server is selected correctly. - Verify the volume size and type are correct. - Confirm the datastore is properly associated. | - **Volume Logs**: Errors related to volume creation (incorrect parameters, missing datastore). | - Volume size can only be increased - check the requirements. - Ensure correct replication type (CPP/APP) based on the storage array setup. |
+| 5 | Volume Deletion Failure | Unable to delete volumes due to them being attached to servers or due to incorrect permission settings. | - Confirm the volume is detached from all servers. - Ensure you have the necessary permissions to delete the volume. | - **Volume Deletion Logs**: Look for errors related to detachment or permission issues during deletion. | - Volumes can only be deleted once detached. - Ensure no active processes are using the volume. |
+| 6 | Volume Resize Failure | Unable to resize a volume, typically due to a lack of rescan on the server OS or exceeding size limits. | - Confirm the server OS has rescanned the volume. - Ensure the new size does not exceed any system or storage limits. | - **Volume Resize Logs**: Look for errors when attempting to resize (e.g., "resize failed" messages). | - Resize operations are only allowed for volume increases, not reductions. - Ensure the OS is aware of the new size after the resize. |
+| 7 | Volume Consumption Issues During Provisioning | Difficulty attaching volumes during instance provisioning (shared/unshared, existing/new, replicated/unreplicated). | - Ensure the correct volume type (shared/unshared) is specified. - Verify replication settings (CPP/APP) are correct. - Check if the volume exists and is accessible. | - **Provisioning Logs**: Check for errors related to volume attachment (invalid volume, replication mismatch). | - Volumes must be properly configured before provisioning. - Shared volumes should be attached to all servers within the instance. |
+| 8 | FC Protocol Issues | Issues with FC protocol during volume creation or consumption (e.g., failed attachments or slow response). | - Check if the storage server and datastore are properly configured for FC. - Confirm FC switches and network paths are properly set up. | - **Fibre Channel Logs**: Look for errors indicating FC connectivity or protocol issues. | - FC issues may be related to network misconfigurations or cable/connectivity problems. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json b/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
new file mode 100644
index 0000000..83b4bc0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+  "title": "Jobs",
+  "ordinal": 90,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md b/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
new file mode 100644
index 0000000..c361c49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
@@ -0,0 +1,12 @@
+# Jobs
+
+Jobs are for scheduled execution of Automation Tasks and Workflows. Jobs can be set to execute on a schedule, at one specific point in time, and/or execute manually (on-demand). Jobs are linked to existing Tasks or Workflows, and allow for custom configuration options. Jobs can be associated with Instances, Servers, or have no association, such as a job for an SSH task.
+
+Jobs allow for scheduled execution of nearly anything as Tasks Types include Bash, Powershell, HTTP/API, Ansible, Chef, Puppet, Groovy, Python, jRuby, Javascript, and library scripts and templates, which can be configured for resource, remote, or local execution targets. If you need something to execute on a schedule, HPE Morpheus Enterprise Jobs can deliver.
+
+Jobs are configured in the `JOBS` tab, and the `JOB EXECUTIONS` tab contains Job execution history with result output.
+
+**Subtopics**  
+
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html)**
+- **[Job Executions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json b/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
new file mode 100644
index 0000000..d26ecbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+  "title": "3Par",
+  "ordinal": 519,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html",
+  "topic_cluster": {
+    "clustering_title": "3Par",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md b/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
new file mode 100644
index 0000000..16769ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
@@ -0,0 +1,32 @@
+# 3Par
+
+## Adding 3Par Storage Server
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json b/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
new file mode 100644
index 0000000..a90f717
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+  "title": "Core Functionality",
+  "ordinal": 40,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html",
+  "topic_cluster": {
+    "clustering_title": "Core Functionality",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md b/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
new file mode 100644
index 0000000..b16f97a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
@@ -0,0 +1,8 @@
+# Core Functionality
+
+**Subtopics**  
+
+- **[Morpheus Discovery](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html)**
+- **[Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html)**
+- **[VMware Support Statement](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..5c8b317
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 374,
+  "parent_title": "Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..a3d24ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,19 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333_2.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html)**
+- **[Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html)**
+- **[DNS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html)**
+- **[Identity Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html)**
+- **[ITSM](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB_2.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_3.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
+- **[Supported Integration Versions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json b/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
new file mode 100644
index 0000000..406f351
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+  "title": "MySQL Too many connections error",
+  "ordinal": 352,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html",
+  "topic_cluster": {
+    "clustering_title": "MySQL Too many connections error",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md b/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
new file mode 100644
index 0000000..f96a623
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
@@ -0,0 +1,57 @@
+# MySQL Too many connections error
+
+If you see the following error in the HPE Morpheus Enterprise UI logs:
+
+```
+```
+SqlExceptionHelper - Data source rejected establishment of connection,  message from server: "Too many connections"
+```
+```
+
+it means the number connections between HPE Morpheus Enterprise application and mysql have reached the max\_connections limit set in mysql (default is 151), or the max\_active setting, which limits the number of connections on the HPE Morpheus Enterprise end (default is 150), and the limit needs to be raised, either in HPE Morpheus Enterprise or mysql, or both depending on the number of connections and configuration.
+
+NOTE
+
+The max\_connections setting in mysql and the maximum used connections between an app node and mysql can be viewed in the HPE Morpheus Enterprise ui in the Administration - Health section under Database.
+
+IMPORTANT
+
+In Single HPE Morpheus Enterprise app node configurations, the `max_active` setting on the app node must be less than the `max_connections` setting in mysql.
+
+IMPORTANT
+
+In HA configurations, the `max_active` setting is per app node, and the `max_connections` setting in mysql must be greater than all app nodes `max_active` values combined, ie `(max_active` \* $number\_of\_app\_nodes) <= max\_connections``.
+
+## HPE Morpheus Enterprise `max_active` setting
+
+Edit `/etc/morpheus/morpheus.rb` and add `mysql[‘max_active’] = $value` replacing `$value` with desired desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql. For example, to set max\_active at 150:
+
+```
+```
+mysql[‘max_active’] = 150
+```
+```
+
+Replacing 100 with the desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql.
+
+Run `morpheus-ctl reconfigure` for the setting to be applied. Reconfigure will not restart the ui unless additional ram has been added to the appliance host since the previous reconfigure. To edit the max\_active without a reconfigure, update the `max_active` setting in `/opt/morpheus/conf/application.yml`. Please note the default setting of 150 will be applied upon the next reconfigure unless `max_active` is defined as instructed above in the `morpheus.rb` file.
+
+## mysql `max_connections` setting
+
+IMPORTANT
+
+Customers are responsible for configuring and maintaining external databases used by HPE Morpheus Enterprise. This explains how to set the `max_connections` setting, but the value for the setting needs to be established by a customers qualified db admin.
+
+In mysql prompt,
+
+run `mysql> SET GLOBAL max_connections = $value;`
+
+This will immediately write the variable, however it is only a temporary setting that will be overwritten upon restart of the mysql service.
+
+To persist the `max_connections` setting, edit my.cnf, and add `max_connections = $value` replacing `$value` with desired value, ie to set max\_connections at 300 in in my.cnf, add:
+
+```
+```
+max_connections = 300
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.json b/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
new file mode 100644
index 0000000..0ea5805
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+  "title": "Role Types",
+  "ordinal": 294,
+  "parent_title": "Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html",
+  "topic_cluster": {
+    "clustering_title": "Role Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.md b/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
new file mode 100644
index 0000000..be60dc5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
@@ -0,0 +1,31 @@
+# Role Types
+
+## Tenant Roles
+
+A Tenant based role (formerly called an Account based role) is used to ensure access control enforcement across an entire tenant with many sub-users. This allows the subtenant to manage their own set of internal user based roles without worrying master tenant involvement in setting them up. The master tenant is the only tenant able to create and manage these types of roles. When editing a Tenant, a singular tenant role can be assigned to the account. Users within the tenant can be assigned roles but those user based roles will never be able to supersede the level of access granted by the tenant role. This allows a super administrator the ability to restrict access at the department or organization level without having to worry about per user access control within said tenant.
+
+Tenant roles also have an additional section not in User based roles related to Cloud Access. Cloud Access allows the master tenant the ability to assign cloud integration resources to specific subtenants or groups of subtenants. An example would be granting access to a specific VMware cluster only to a subset of tenants using the tenant based role control.
+
+## User Roles
+
+User roles can be created by any tenant given permission at the tenant role level. These allow tenants to manage their own sets of users and their levels of access. They also allow tenants to control which users have access to specific “Groups” for provisioning into within HPE Morpheus Enterprise. Groups are not cross tenant and therefore need to be controlled within the individual tenant in HPE Morpheus Enterprise.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within HPE Morpheus Enterprise. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+NOTE
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
+
+## Multi-Tenant User Role Lock
+
+As discussed above, Multi-Tenant User Roles are made available within all Subtenants and can be thought of as ‘canned’ user role sets provided to the Subtenant. Master Tenant administrators can prevent changes to these ‘canned’ user roles by marking the box labeled ‘MULTITENANT LOCKED’ when creating or editing the role. In addition to preventing Subtenant administrators from modifying permissions of the role copied down to their Subtenant, this option also ensures Master Tenant administrators can propagate new changes to that role. Modification of the role by the subtenant (if allowed) breaks the link back to the Master Tenant and the copy of the role within the Subtenant will become its own unlinked role.
+
+NOTE
+
+Multi-tenant role lock applies only to permission sets on the Features, Report Types, Personas and VDI Pools tabs. Permissions in other tabs (such as Groups, Instance Types, Blueprints or Catalog Item Types) tabs are not locked. Similarly, changes made to the role on these tabs in the master tenant are not synced down.
+
+## Editing User Roles in other Tenants
+
+Administrators in the Primary Tenant have the unique ability to edit feature permissions for User Roles that exist within other Tenants (Subtenants). In order to view the Roles within the Tenant, navigate to the Tenant detail page (Administration > Tenants) and select the Roles tab. Click the pencil (✎) icon to the right of a Role in the list to edit basic information, such as the name and description of the Role. Click on the name of the Role to view its complete permission set and edit the permissions if desired. This will update the feature access rights of users in the selected Tenant which have the Role.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json b/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
new file mode 100644
index 0000000..383f357
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+  "title": "Azure Stack",
+  "ordinal": 391,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Stack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md b/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
new file mode 100644
index 0000000..46d1026
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
@@ -0,0 +1,300 @@
+# Azure Stack
+
+## Overview
+
+Azure Stack is Microsoft’s Azure Cloud for on-premises environments. Azure Stack contains the core Azure services, allowing organizations to take advantage of Azure’s offerings with the security, compliance, and financial benefits of hosting it in their own data-centers.
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Group Sync & Selection
+- Network Sync & Selection
+- Security Group Sync & Selection
+- Storage Account Sync & Selection
+- Marketplace Search and Provisioning
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Availability Set Support
+- Azure Load Balancers
+- Azure Storage
+- Docker Host Provisioning & Management
+- Service Plan Sync
+- Pricing Sync with markup options
+- Cost Estimator
+
+Combine these features with public Azure and HPE Morpheus Enterprise can provide a single pane of glass and self service portal for managing instances scattered across both Azure offerings.
+
+## Requirements
+
+### Azure Stack Accessibility
+
+By default, the Azure Stack management url’s are not accessible from an external network. Port mappings and DNS must be configured for communication between the HPE Morpheus Enterprise Appliance and Azure Stack.
+
+IMPORTANT
+
+In order to communicate with Azure Stack, HPE Morpheus Enterprise must be able to reach the internal Azure Stack network. The Azure Stack Portal needs to be exposed to the HPE Morpheus Enterprise Appliances’ network with corresponding entries added to DNS.
+
+One option to expose the Internal Azure Stack network to the HPE Morpheus Enterprise Appliances network is to use the `Expose-AzureStackPortal.ps1` powershell script from <https://gallery.technet.microsoft.com/scriptcenter/Expose-the-Azure-Stack-7ef68b19>. An Azure Stack Port Mapping Tool is also available.
+
+Below is a sample output from the script for reference:
+
+```
+```
+[Admin Portal] Created port mappings on 10.30.23.120 to 192.168.102.8  
+[Admin Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Admin Portal] DNS: 10.30.23.120 - adminportal.local.azurestack.external adminmanagement.local.azurestack.external  
+[Tenant Portal] Created port mappings on 10.30.23.121 to 192.168.102.10  
+[Tenant Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Tenant Portal] DNS: 10.30.23.121 - portal.local.azurestack.external management.local.azurestack.external  
+[Blob Storage] Created port mappings on 10.30.23.122 to 192.168.102.4  
+[Blob Storage] Ports: 80 443  
+[Blob Storage] DNS: 10.30.23.122  *.blob.local.azurestack.external  
+VERBOSE: DNS delegation/forwarding is optional, change the DNS records on MAS-DC01 manually (dnsmgmt.msc from Host).  
+[DNS Delegation] Created port mappings on 10.30.23.120 to 192.168.200.224  
+[DNS Delegation] Ports: 53 (TCP/UDP)  
+[DNS Delegation] DNS: local.azurestack.external NS 10.30.23.120  
+[DNS Delegation] Change records on MAS-DC01 manually `if` you plan to use DNS forwarding.  
+[DNS Delegation] Change records back to the original internal IPs before running this script again.  
+VERBOSE: App Service detected and external IPs specified, creating mappings.  
+[App Service API] Created port mappings on 10.30.23.123 to 192.168.102.17  
+[App Service API] Ports: 443  
+[App Service API] DNS: 10.30.23.123  api.appservice.local.azurestack.external  
+[App Service Apps] Created port mappings on 10.30.23.124 to 192.168.102.15  
+[App Service Apps] Ports: 80 443 21 990  
+[App Service Apps] DNS: 10.30.23.124  *.appservice.local.azurestack.external
+```
+```
+
+### Azure Stack Resources
+
+The following resources need to be created and configured inside Azure Stack for successful provisioning:
+
+- Resource Group(s)
+- Virtual Network(s)
+- Storage Account(s)
+- Network Security Group(s)
+
+  - Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389
+  - Outbound ports open to HPE Morpheus Enterprise Appliance: 80, 443
+
+NOTE
+
+Proper Network and Network Security Group configuration is required for HPE Morpheus Enterprise agent install, communication, and remote console access. Other configurations, such as docker instances, will need the appropriate ports opened as well.
+
+### Required Credentials & Permissions
+
+Credentials to integrate HPE Morpheus Enterprise with Azure Stack are located in both the public Azure Portal and the Private Azure Stack Portal. The Azure Active Directory Application used must be an owner of the Azure Stack subscription.
+
+Azure Portal:
+:   - Azure Active Directory Application Credentials
+    - Directory ID
+    - Management URL
+    - Identity Resource URL
+    - Application ID
+    - Key Value
+
+Azure Stack Portal:
+:   - Azure Stack Subscription ID
+    - Active Directory App from Azure portal added as owner of the Azure Stack Subscription in Azure Stack.
+
+## Adding an Azure Stack Cloud
+
+### Configure
+
+#### Procedure
+
+1. In the HPE Morpheus Enterprise UI, navigate to Infrastructure  >  Clouds and Select + CREATE CLOUD
+2. Select AZURE STACK (PRIVATE) from the Clouds list and select NEXT
+3. In the Configure section, enter: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   IDENTITY URL
+   :   <https://login.microsoftonline.com>
+
+   MANAGEMENT URL\*
+   :   Azure AD Azure Stack Administrator app or Microsoft Azure Stack Administrator app url. Example: <https://adminmanagement.local.azurestack.external/>
+
+   IDENTITY RESOURCE URL
+   :   Azure AD Azure Stack Administrator App ID URI Example: <https://adminmanagement.xxxxxxx.onmicrosoft.com/4a80e607-4259-4ac6-83e2-2fabeaf2eh83>
+
+   BASE DOMAIN
+   :   This should match the base domain in your Management url. Example: local.azurestack.external
+
+   SUBSCRIPTION ID
+   :   Subscription ID from Azure Stack portal (this is different from the Subscription ID in you Azure portal used when configuring Azure Stack)
+
+   TENANT ID
+   :   This is the Directory ID from the Azure AD directory
+
+   CLIENT ID
+   :   Application ID of Azure AD app with Azure Stack permissions granted, and has been added as an owner of the Azure Stack subscription (in the Azure Stack portal).
+
+   CLIENT SECRET
+   :   Key Value of Application ID used above
+
+       NOTE
+
+       Once all credentials are entered and validated, the Location and Resource Group fields will populate.
+
+   Location
+   :   Select an Azure Stack region for the cloud to scope to. This typically will be “local”.
+
+   Resource Group
+   :   Select All or a single Resource Group to scope the cloud to. Selecting a single Resource Group will only sync resources in that Resource Group and disable Resource Group selection during provisioning. All will sync all resources and allow specifying the Resource Group during provisioning.
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise.
+4. The Azure Stack cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+   NOTE
+
+   All fields and options can be edited after the Cloud is created.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+5. Once all options are configured, select NEXT to add the cloud to a Group. 
+
+   GROUP
+   :   A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+   USE EXISTING
+   :   Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+
+   CREATE NEW
+   :   Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+6. Confirm all settings are correct and select COMPLETE. The Azure Stack Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of: 
+
+   - Virtual Machines (if Inventory Existing Instances is enabled)
+   - Networks
+   - Virtual Images/Blueprints
+   - Network Security Groups
+   - Storage Accounts
+   - Marketplace Catalog
+   - Availability Sets
+
+   TIP
+
+   Synced Networks can be configured or deactivated from the Networks section in this Clouds detail page, or in the Infrastructure  >  Networks section.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json b/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
new file mode 100644
index 0000000..a3364cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+  "title": "Scale Thresholds",
+  "ordinal": 122,
+  "parent_title": "Automation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html",
+  "topic_cluster": {
+    "clustering_title": "Scale Thresholds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md b/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
new file mode 100644
index 0000000..7e9a0ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
@@ -0,0 +1,55 @@
+# Scale Thresholds
+
+Scale Thresholds are pre-configured settings for auto-scaling Instances. When adding auto-scaling to an instance, existing Scale Thresholds can be selected to determine auto-scaling rules.
+
+## Creating Scale Thresholds
+
+### Procedure
+
+1. Navigate to Library > Automation > Scale Thresholds
+2. Select + ADD
+3. Populate the following:
+
+### Results
+
+NAME
+:   Name of the Scale Threshold
+
+AUTO UPSCALE
+:   Enable to automatically upscale per Scale Threshold specifications
+
+AUTO DOWNSCALE
+:   Enable to automatically downscale per Scale Threshold specifications
+
+MIN COUNT
+:   Minimum node count for Instance. Auto-scaling will not downscale below MIN COUNT, and will auto upscale if the MIN COUNT is not met)
+
+MAX COUNT
+:   Maximum node count for Instance. Auto-scaling will not upscale past MAX COUNT, and will auto downscale if MAX COUNT is exceeded.
+
+ENABLE MEMORY THRESHOLD
+:   Check to set auto-scaling by specified memory utilization threshold (%)
+
+MIN MEMORY
+:   Enter MIN MEMORY % for triggering downscaling.
+
+MAX MEMORY
+:   Enter MAX MEMORY % for triggering upscaling.
+
+ENABLE DISK THRESHOLD
+:   Check to set auto-scaling by specified disk utilization threshold (%)
+
+MIN DISK
+:   Enter MIN DISK % for triggering downscaling.
+
+MAX DISK
+:   Enter MAX DISK % for triggering upscaling.
+
+ENABLE CPU THRESHOLD
+:   Check to set auto-scaling by specified overall CPU utilization threshold (%)
+
+MIN CPU
+:   Enter MIN CPU % for triggering downscaling.
+
+MAX CPU
+:   Enter MAX CPU % for triggering upscaling.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json b/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
new file mode 100644
index 0000000..c6c08e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+  "title": "Apps",
+  "ordinal": 257,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md b/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
new file mode 100644
index 0000000..35f5e79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
@@ -0,0 +1,18 @@
+# Apps
+
+App monitors are very useful for seeing an aggregation of failures or impact based on a set of checks and groups. App monitors typically correlate to Apps provisioned from HPE Morpheus Enterprise Blueprints but can also be manually created and organized. They can be great for visualizing the customer impact a failure might have or even keeping up on a screen in a NOC. To create an App monitor:
+
+Name
+:   A friendly name for the new app monitor in HPE Morpheus Enterprise
+
+Description
+:   An optional description value to identify the app monitor
+
+Max Severity
+:   The maximum severity incident a failed app may create. This setting overrides check and group max severity settings
+
+Affects Availability
+:   When checked, this failed app impacts system-wide availability calculations
+
+App Checks
+:   Use the typeahead field to select as many checks as needed to complete the app monitor. Checks are created in Monitoring > Checks and must exist prior to creating the app monitor
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json b/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
new file mode 100644
index 0000000..4b084c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+  "title": "Trust",
+  "ordinal": 236,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md b/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
new file mode 100644
index 0000000..60991a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
@@ -0,0 +1,15 @@
+# Trust
+
+The Trust section is where credentials, SSH keypairs, and SSL certificates are stored. In addition, related integrations to outside technologies can be made in this section as well. Integration types include HPE Morpheus Enterprise Cypher and Hashicorp Vault for externalized credential storage. Continue onto the next section for more on standing up an external Cypher credential store.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html)**
+- **[Integrating Hashicorp Vault](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html)**
+- **[Installing and Integrating an External Cypher Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html)**
+- **[Add SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html)**
+- **[Delete SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html)**
+- **[Trust Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json b/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
new file mode 100644
index 0000000..7d5c147
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+  "title": "Add Workflow",
+  "ordinal": 114,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html",
+  "topic_cluster": {
+    "clustering_title": "Add Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md b/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
new file mode 100644
index 0000000..98f263f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
@@ -0,0 +1,21 @@
+# Add Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar
+2. Select Automation from the sub-navigation menu
+3. Click the Workflows tab to show the Workflows tab panel
+4. Click the + Add dropdown and select a Workflow type (Operational or Provisioning, see the section above for more on Workflow type differences)
+5. From the New Workflow Wizard input a name for the workflow
+6. Optionally input a description and a target platform
+7. Add Tasks and Inputs using the typeahead fields, Tasks must be added to the appropriate phases for Provisioning Workflows
+8. If multiple tasks are added to the same execution phase, their execution order can be changed by selecting the grip icon and dragging the task to the desired execution order
+9. For multi-Tenant environments, select Public or Private visibility for the Workflow
+10. For Operational Workflows, optionally mark “Allow Custom Config” from the Advanced Options section if needed. See the next section for more on this selection
+11. Click the SAVE CHANGES button to save
+
+## Results
+
+NOTE
+
+When setting Workflow visibility to Public in a multi-Tenant environment, Tenants will be able to see the Workflow and also execute it directly from the Workflows list (if it’s an Operational Workflow). They will not be able to edit or delete the Workflow.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..369870f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 309,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..6601de8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,183 @@
+# Users
+
+## Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Tenant
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. From the Actions menu in each User row, the option is given to Impersonate the User, Edit, or Remove the User.
+
+In HPE Morpheus Enterprise 4.2.1 and higher, click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role create/edit page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in HPE Morpheus Enterprise, as it is synced from the Identity Source.
+
+## Create User
+
+### About this task
+
+Users can be created from Administration > Users or Administration > Tenants > (selected Tenant) > Users tab`.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+### Procedure
+
+1. Navigate to either Administration > Users or Administration > Tenants > Select a Tenant``.
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive Provisioning and Policy email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s).
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into HPE Morpheus Enterprise, but their user data will remain.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+
+### Results
+
+NOTE
+
+Instance Resource Limits for a user are now configured through [Policies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html#GUID-B0152179-D5F5-49E3-9CDD-E6BD2573DC0F)
+
+1. Select SAVE CHANGES.
+
+## Edit User
+
+### About this task
+
+User settings can be edited from Administration > Users, Administration > Tenants > Select a Tenant > Userstab`, or from User Settings.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in HPE Morpheus Enterprise, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click ACTIONS on the row of the user to edit.
+4. Select EDIT in the ACTIONS dropdown.
+5. Make changes.
+6. Select SAVE CHANGES.
+
+### Results
+
+To edit a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to edit.
+5. Select **EDIT** in the ACTIONS dropdown.
+6. Make changes.
+7. Select SAVE CHANGES.
+
+## User Settings
+
+### About this task
+
+Additional settings for a User can be found in the User Settings section, including:
+
+- User Photo
+- Default Group
+- Default Cloud
+- API Access
+
+To access User Settings:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings
+
+### Results
+
+To edit the User you are currently logged in as from User Settings:
+
+1. Select your name in the header
+2. Select User Settings
+3. Make changes.
+4. Select SAVE.
+
+## API Access
+
+### About this task
+
+API and CLI Access Tokens can be regenerated from the User Settings section.
+
+To regenerate a CLI or API Access Token:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings.
+3. Select API ACCESS under the Windows Settings section.
+4. Select ACTIONS for the Client ID the token will be generated for.
+5. Select Regenerate.
+6. Copy the Generated Access Token. 
+
+   IMPORTANT
+
+   The Access Token will be masked after User Setting are saved.
+7. Select SAVE.
+
+## Delete User
+
+### About this task
+
+To delete a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Select ACTIONS on the row of the user to delete.
+4. Select REMOVE in the ACTIONS dropdown.
+5. Confirm
+
+### Results
+
+To delete a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to delete.
+5. Select **REMOVE** in the ACTIONS dropdown.
+6. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
new file mode 100644
index 0000000..0ee4f01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+  "title": "Ansible",
+  "ordinal": 376,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
new file mode 100644
index 0000000..1d228de
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
@@ -0,0 +1,295 @@
+# Ansible
+
+## Overview
+
+Ansible is a configuration management engine that is rapidly growing in popularity in the IT and DevOPS community. While it lacks some of the benefits at scale that solutions such as Chef or Puppet offer. It is very easy to get started and allows engineers to develop tasks in a simplistic markup language known as YAML. HPE Morpheus Enterprise integrates with an existing repository of playbooks as the master in a master-slave Ansible architecture.
+
+HPE Morpheus Enterprise not only supports Ansible but greatly enhances Ansible to do things that it could not do in its native form. For example, Ansible can now be configured to run over the HPE Morpheus Enterprise agent communication bus. This allows playbooks to be run against instances where SSH/WinRM access may not be feasible due to networking restrictions or other firewall constraints. Instead it can run over the HPE Morpheus Enterprise Agent which only requires port 443 access back to the HPE Morpheus Enterprise appliance URL.
+
+This integration supports both Linux-based and Windows platforms for playbook execution and can also be configured to query secrets from HPE Morpheus Enterprise Cypher services (similar to Vault).
+
+## Requirements
+
+- Minimum Ansible Version Requirement is 2.7.x
+- For agentless non-commandbus, sshpass is required
+- For Windows non-agent command bus, pywinrm is required
+- `Integrations: Ansible` User Role Permission required for access to Ansible Details Pages and Ansible tabs in Groups and Clouds
+- Calling HPE Morpheus Enterprise Cypher secrets into Ansible scripts requires the Python `requests` module which is not part of the Python standard library. For Ubuntu 18.04 or 20.04 run `sudo apt install python-requests` or `sudo apt install python3-requests`, respectively. For RHEL/CentOS, run `sudo yum install python2-requests`
+
+NOTE
+
+Installing Ansible on the HPE Morpheus Enterprise appliance is a requirement. In some cases, this is handled automatically but in certain situations you may have to install manually. See the section below on [troubleshooting Ansible](https://docs.morpheusdata.com/en/latest/troubleshooting/Ansible_Troubleshooting.html) for installation steps.
+
+## Add Ansible Integration
+
+### Procedure
+
+1. Navigate to Library > Integrationsand select + New Integration
+2. Select Integration Type “Ansible”
+3. Populate the following fields: 
+
+   Name
+   :   Name of the Ansible Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enabled by default
+
+   Ansible Git URL
+   :   https or git url format of the Ansible Git repo to use
+
+   Keypair
+   :   For private Git repos, a keypair must be added to HPE Morpheus Enterprise and the public key added to the git account.
+
+   Playbooks Path
+   :   Path of the Playbooks relative to the Git url.
+
+   Roles Path
+   :   Path of the Roles relative to the Git url.
+
+   Group Variable Path
+   :   Path of the Group Variables relative to the Git url.
+
+   Host Variables Path
+   :   Path of the Host Variables relative to the Git url.
+
+   Use Ansible Galaxy
+   :   Install roles defined in `requirements.yml`
+
+   Enable Verbose Logging
+   :   Enable to output verbose logging for Ansible task history
+
+   Use Morpheus Agent Command Bus
+   :   Enable for Ansible Playbooks to be executed via Morpheus Agent Command Bus instead of SSH
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Ansible on Windows
+
+When executing Ansible playbooks on Windows platforms, a few requirements must be met:
+
+- `pywinrm` may need to be installed on the HPE Morpheus Enterprise Appliance via `pip install pywinrm`
+- An Ansible Integration must be scoped to a Group or Cloud for Ansible to execute on Windows, as HPE Morpheus Enterprise assumes Ansible local when no group or cloud is scoped to Ansible. The playbooks do not need to be executed solely in the Group or Cloud, one just needs to be scoped to an Ansible Integration for Ansible Windows to run properly.
+
+## Scope Ansible Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Cloud, a new “ANSIBLE” tab will appear on the Cloud details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Scope Ansible Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Group, a new “ANSIBLE” tab will appear on the Group details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Integration added, an Ansible section will appear in the Config section of the provisioning wizard. By default, Ansible is enabled, but can be disabled by expanding the Ansible section and unchecking Enable Ansible.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible
+:   Select to bootstrap
+
+Ansible Group
+:   Ansible Inventory Group. Use existing group or enter a new group name to create a new group. Leaving this field blank will place instance in the “unassigned” inventory group.
+
+    NOTE
+
+    An instance can belong to multiple groups by separating group names with a comma
+
+Playbook
+:   Playbook(s) to run. The .yml extension is optional.
+
+## Running Playbooks
+
+Playbooks can also be run on all inventory groups, individual groups, or added as a task and ran with workflows.
+
+To run Ansible on all or a single inventory group, in the Ansible tab of the HPE Morpheus Enterprise Group page, select the Actions dropdown and click Run.
+
+In the Run Ansible modal, you can then select all or an individual group, and then all or a single Playbook, as well as add custom tags.
+
+Playbook’s can also be added as tasks to workflows in the Library > Automationsection, and then selected in the Automation pane during provisioning of new instances, when creating app blueprints, or ran on existing instances using the Actions  >  Run Workflow on the Instance or Host pages.
+
+## Using variables
+
+HPE Morpheus Enterprise variables can be used in playbooks.
+
+Use Case:
+:   Create a user as instance hostname during provisioning.
+    :   Below is the playbook. Add this playbook to a task and run it as a workflow on the instance.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['instance']['hostname'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['instance']['hostname'] }}` is the format of using HPE Morpheus Enterprise Variables
+
+    Create a user with a name which you enter during provisioning using a custom Instance type.
+    :   This instance type has a Text Input that provides a text box to enter a username. The fieldName of the Input in this case would be username. Below is the playbook.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['customOptions']['username'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['customOptions']['username'] }}` will be the format.
+
+## Using Secrets
+
+Another great feature with using Ansible and HPE Morpheus Enterprise together is the built in support for utilizing some of the services that HPE Morpheus Enterprise exposes for automation. One of these great services is known as Cypher (please see documentation on [Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html) for more details). Cypher allows one to store secret data in a highly encrypted way for future retrieval. Referencing keys stored in cypher in your playbooks is a matter of using a built-in lookup plugin for ansible.
+
+```
+```
+- name: Add a user  
+  win_user:  
+    name: "myusername"  
+    password: "{{ lookup('cypher','secret=password/myusername') }}"  
+    state: present
+```
+```
+
+By using the `{{ lookup('cypher','secret=password/myusername') }}` syntax. One can grab the value directly out of the key for use. This lookup plugin also supports a few other fancy shortcuts. In this above example the password/ mountpoint is capable of autogenerating passwords if they have not previously been defined and storing them within cypher for reference later.
+
+Another capability is accessing properties from within a key in cypher. The value of a key can also be a JSON object which can be referenced for properties within. For example:
+
+```
+```
+{{ lookup('cypher','secret=secret/myjsonobject:value') }}
+```
+```
+
+This would grab the value property off the nested json data stored within the key.
+
+Cypher is very powerful for storing these temporary or permanent secrets that one may need to orchestrate various tasks and workflows within Ansible.
+
+## Custom Inventory Entries
+
+With Morpheus it is possible to add custom inventory entries that exist outside of morpheus host/server entry. This is global across cloud or group and is done on the integration details page of the Ansible integration. To add a custom inventory entry navigate to Library > Integrations> (Your specific Ansible integration). Click on the `ACTIONS` button, then click `EDIT INVENTORY`. Inventory should be in the default Ansible ini format.
+
+![../../_images/ansible_inventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0099BB05-0B08-41BB-856E-5403C2315926-high.png)
+
+## Using Ansible over the HPE Morpheus Enterprise Agent Command Bus
+
+In many environments, there may be security restrictions on utilizing SSH or WinRM to run playbooks from an Ansible server on the appliance to a target machine. This could be due to being a customer network (in the environment of an MSP ), or various security restrictions put in place by tighter industries (i.e. Government, Medical, Finance).
+
+Ansible can get one in trouble in a hurry. It is limited in scalability due to its fundamental design decisions that seem to bypass concepts core to all other configuration management frameworks (i.e. Chef and Puppet). Because of its lack of an agent, the Ansible execution binary itself has to handle all the load and logic of executing playbooks on all the machines in the inventory of an Ansible project. This differs from other tools where the workload is distributed across the agents of each vm. Because of this (reaching out) approach, Ansible is very easy to get started with, but can be quite a bit slower as well as harder to scale up. However, HPE Morpheus Enterprise offers some solutions to help mitigate these issues and increase scalability while, at the same time improving security.
+
+### How does the HPE Morpheus Enterprise Agent Command Bus Work?
+
+One of the great things about HPE Morpheus Enterprise is it’s Agent Optional approach. This means that this functionality can work without the Agent, however the agent is what adds the security benefits being represented here. When an instance is provisioned (or converted to managed) within HPE Morpheus Enterprise, an agent can be installed. This agent opens a secure websocket back to the HPE Morpheus Enterprise appliance (over port 443). This agent is responsible for sending back logs, guest statistics, and a command bus for automation. Since it is a WebSocket, bidirectional communication is possible over a STOMP communication bus.
+
+When this functionality is enabled on an Ansible integration, a connection\_plugin is registered with Ansible of type morpheus and morpheus\_win. These direct bash or powershell commands, in their raw form, from Ansible to run over a HPE Morpheus Enterprise api. The Ansible binary sends commands to be executed as an https request over the API utilizing a one time execution lease token that is sent to the Ansible binary. File transfers can also be enacted by this API interface. When HPE Morpheus Enterprise receives these commands, they are sent to the target instances agent to be executed. Once they have completed a response is sent back and updated on the ExecutionRequest within HPE Morpheus Enterprise. Ansible polls for the state and output on these requests and uses those as the response of the execution. This means Ansible needs zero knowledge of a machines target ip address, nor its credentials. These are all stored and safely encrypted within HPE Morpheus Enterprise.
+
+It has also been pointed out that this execution bus is dramatically simpler than utilizing pywinrm when it comes to orchestrating Windows as the winrm configurations can be cumbersome to properly setup, especially in tightly secured Enterprise environments.
+
+## Using Ansible Galaxy
+
+HPE Morpheus Enterprise can use a `requirements.yml` file to define Ansible roles to download prior to running your playbook. Place `requirements.yml` into the root of your Git repository and make sure Use Ansible Galaxy is checked in the integration. Roles will be installed in the root of the repository if a directory is not defined in Roles Path.
+
+- Example requirements.yml:
+
+```
+```
+- src: https://github.com/geerlingguy/ansible-role-java  
+  name: java
+```
+```
+
+- Example playbook.yml:
+
+```
+```
+- hosts: all  
+  gather_facts: true  
+  roles:  
+    - java
+```
+```
+
+## Troubleshooting Ansible
+
+- When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in the ui logs in /var/log/morpheus/morpheus-ui/current​ which can be tailed by running `morpheus-ctl tail morpheus-ui`.
+- Verify Ansible is installed on the HPE Morpheus Enterprise Appliance.
+
+  Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+  If Ansible is not installed, follow these instructions to install, or use your preferred installation method:
+
+  Ubuntu:
+
+  ```
+  ```
+  sudo apt-get install software-properties-common  
+  sudo apt-add-repository ppa:ansible/ansible  
+  sudo apt-get update  
+  sudo apt-get install ansible
+  ```
+  ```
+
+  CentOS:
+
+  ```
+  ```
+  sudo yum install epel-release  
+  sudo yum install ansible
+  ```
+  ```
+
+  Then create the working Ansible directory for HPE Morpheus Enterprise:
+
+  ```
+  ```
+  mkdir -p /opt/morpheus/.ansible/tmp  
+  chown -R morpheus-local. /opt/morpheus/.ansible  
+  chmod -R 775 /opt/morpheus/.ansible
+  ```
+  ```
+- Validate the git repo is authorizing and the paths are configured correctly.
+
+  The public and private ssh keys need to be added to the HPE Morpheus Enterprise appliance via “Infrastructure > Keys& Certs” and the public key needs to be added to the git repo via user settings. If both are set up right, you will see the playbooks and roles populate in the Ansible Integration details page.
+- The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+- When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+- If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..15c4172
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 333,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json b/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
new file mode 100644
index 0000000..8d06661
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+  "title": "Administration",
+  "ordinal": 273,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md b/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
new file mode 100644
index 0000000..e9042c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
@@ -0,0 +1,16 @@
+# Administration
+
+There are several administrative integrations built into HPE Morpheus Enterprise that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html)**
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users & User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56_2.html)**
+- **[Policies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json b/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
new file mode 100644
index 0000000..e50ed34
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+  "title": "Volume Consumption",
+  "ordinal": 447,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Consumption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md b/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
new file mode 100644
index 0000000..ccfd118
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
@@ -0,0 +1,23 @@
+# Volume Consumption
+
+Consumption of volume is typically done through compute instance provisioning, where the user can specify volumes to attach to, whether existing volumes or new volumes to be created. It can also be done using the reconfigure action.
+
+## Instance Provisioning
+
+During instance provisioning, the user can specify volumes to be attached to the servers within the instance. There are various types of volumes user can specify.
+
+## Sharing
+
+Volumes can be shared or unshared (attached to a specific server only). Specifying a shared volume means a single volume is attached to all the servers within that instance. Specifying an unshared volume means a volume is created for each server within the instance and exported to the corresponding server.
+
+## Existing vs New
+
+The user can specify a new volume to be created or specify to attach to an existing volume. Existing volume is applicable only to shared volumes.
+
+## Replicated vs Unreplicated
+
+When creating new volumes, the user can specify that the volume is unreplicated or replicated. Depending on the storage array deployed and the HA configuration, replicated volumes can be specified as CPP (classic peer persistence) or APP (active peer persistence).
+
+**Subtopics**  
+
+- **[Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
new file mode 100644
index 0000000..995506b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+  "title": "Overview",
+  "ordinal": 57,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
new file mode 100644
index 0000000..4428a55
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The HPE Morpheus Enterprise Analytics engine gives administrators the tools to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. Analytics dashboards can be organized into three primary categories based on their measurement intentions: costing, utilization, and workloads. Each dashboard type is discussed in further detail below.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json b/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
new file mode 100644
index 0000000..18d949c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+  "title": "SolarWinds IPAM",
+  "ordinal": 515,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html",
+  "topic_cluster": {
+    "clustering_title": "SolarWinds IPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md b/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
new file mode 100644
index 0000000..0bd39c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
@@ -0,0 +1,90 @@
+# SolarWinds IPAM
+
+## Features
+
+- Automate static IP assignment across environments using Solarwinds IPAM
+- Network pool sync: Network pools can be set on networks in HPE Morpheus Enterprise for automated IP allocation and record creation
+- Optional Network Pool allocation and record sync. `Inventory Existing` option syncs all individual IP records and corresponding status. Inventory is not required for provisioning
+- Grid and list displays with IP record overlays and color coding for static, available, reserved and transient status
+- Manual IP Host record creation from Network Pool detail pages
+
+## Adding SolarWinds to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select SolarWinds
+4. Enter in the following information 
+
+   Name
+   :   Name of the SolarWinds Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable sync with the SolarWinds endpoint
+
+   URL
+   :   URL of the SolarWinds server, ex: `http://10.30.20.10:17778`
+
+   Username
+   :   Username of SolarWinds API User. See the NOTE box below for information on minimum rights requirements
+
+   Password
+   :   SolarWinds User password
+5. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+At minimum you will need credentials for a user with API and root-level propagating read access, as well as read/write access for target networks and domains. For a quicker solution, you can also use an account with the Power User role in situations where you aren’t concerned with providing only the minimum required access.
+
+## Consuming SolarWinds in HPE Morpheus Enterprise
+
+On saving your new integration, SolarWinds networks will be synced and can be viewed by navigating to Infrastructure  >  Network  >  IP POOLS. They’re also viewable from the detail section of the SolarWinds integration at Infrastructure  >  Network  >  INTEGRATIONS  >  (your SolarWinds integration)  >  NETWORK POOLS.
+
+![../../_images/networkpools.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4DA0027F-E1C3-4F28-80BC-929C5E44ADA2-high.png)
+
+Host records can also be viewed here by clicking on the name of a SolarWinds network.
+
+![../../_images/hostrecords.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-374CAAAE-F29E-46E2-93D5-F1B68E9A6477-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise SolarWinds integration does not support zone record syncing despite the presence of the ZONES tab on the integration detail page. This is a UI feature carried over from other networking integrations and is not supported at this time.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available SolarWinds IP in an IP/Network Pool and create the corresponding DNS records. HPE Morpheus Enterprise will also remove the records upon teardown. To enable this, add an SolarWinds IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL typeahead field, search for and select the name of the selected IP/Network Pool. 
+
+   - Gateway, DNS, and CIDR must be populated for static/pool IP assignment
+   - Select ALLOW IP OVERRIDE, if desired, to allow selecting between DHCP, static IP address entry, and pool address selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP POOLS
+2. Click + ADD
+3. Enter the following 
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/createhost1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7ACA8930-1EBE-46C3-93A0-FF538FFF439B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..61afdb5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 175,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..20757a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json b/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
new file mode 100644
index 0000000..bd00ad6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+  "title": "vCloud Director",
+  "ordinal": 474,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.html",
+  "topic_cluster": {
+    "clustering_title": "vCloud Director",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md b/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
new file mode 100644
index 0000000..9f7ecac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
@@ -0,0 +1,314 @@
+# vCloud Director
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Datastores
+- Brownfield VM management and migration
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- IP Pool Support
+- Multi-NIC Interfaces
+- Kubernetes and Docker
+- Proxy Support
+- Image Builder
+- Monthly estimated pricing and usage tracker
+- Custom plan discovery and utilization at provision time
+
+## Configuration
+
+### Add vCD Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select VCLOUD DIRECTOR from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   NOTE
+
+   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. You do not need both despite the fact that all four of those fields are indicated as required fields.
+
+   API URL
+   :   vCloud Director API Url
+       :   Example: `https://org.vcd.company.com`
+
+   CREDENTIALS
+   :   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. These may be locally entered (select Local Credentials), locally entered and stored securely for future use (select “username and password” or “api token, tenant” from within the “New Credentials” section), or a pre-existing credential set may be selected from the HPE Morpheus Enterprise secure credential store. Depending on the selection, additional fields will appear (or some may disappear) to facilitate your choice
+
+   USERNAME
+   :   vCD Organization Administrator or System Administrator User
+
+       - User must have an Organizational Administrator or System Administrator Role
+       - Username must be in the format of <name>@<org>
+       - When using a user with the System Administrator role, give the username in the format of <username>@system. Additionally, ensure this user has permission set correctly, such as to view objects created by the organization administrator if needed. Otherwise, things like catalogs and vApps created by the Organization Administrator might not be visible to HPE Morpheus Enterprise
+       - In some cases, it may not be advisable to use the system administrator user. This is because some environments will have API access turned off for the system administrator for security reasons as the user would be able to remove key pieces of infrastructure. If your system administrator user does have API access and you understand the risks, you can authenticate HPE Morpheus Enterprise with this user
+
+   PASSWORD
+   :   Password for the user indicated above
+
+   API TOKEN
+   :   A generated API token for the service account user
+
+   TENANT
+   :   The Tenant to which the service account user authenticates
+
+   ORG
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   VDC
+   :   Select VDC. Dropdown populates upon successful authorization.
+
+   API VERSION
+   :   Full version required which much be in the “xx.x” format. When applicable, do not drop a trailing “0” (Ex. `31.0`). HPE Morpheus Enterprise will attempt to discover the API version, which would make this field optional. However, vCD allows disabling of the API versions API. In such an environment, the user would need to specify the API version here
+
+   CATALOG
+   :   Optionally select a vCD catalog to store HPE Morpheus Enterprise artifacts or use the default “morpheus\_auto” catalog
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise
+
+   Enable Hypervisor Console
+   :   Mark to use VNC hypervisor console for the HPE Morpheus Enterprise console rather than the default SSH or RDP connection methods
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+## How to create vCloud Director templates for Morpheus
+
+### To create a Windows Template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build.
+
+#### Procedure
+
+1. Apply any service packs / updates to the operating system.
+2. Set the Network location to Private the below PowerShell will set the location. 
+
+   ```
+   ```
+   Get-NetConnectionProfile | Set-NetconnectionProfile -NetworkCategory private
+   ```
+   ```
+3. Configure WinRM to allow remote management and open the firewall. 
+
+   - To do this, under local computer Administrator, open a command prompt and run `winrm quickconfig`
+4. Install VMware tools
+5. Install .Net at least 4.5
+6. Enable remote PowerShell this can be done in PowerShell. 
+
+   ```
+   ```
+   Enable-PSremoting
+   ```
+   ```
+7. Shutdown the virtual machine and convert to a template. 
+
+   NOTE
+
+   Do not run sysprep
+
+### To create a Linux Centos template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install vmware tools
+6. Install git by running `yum install git`
+7. epel-release
+8. selinux set to permissive (enforced can cause problems with cloud-init)
+
+### To create a Linux Ubuntu template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Ensure you have set a root password
+4. Install cloud-init by running `sudo apt install cloud-init`
+5. Install cloud-utils-growpart `sudo apt install cloud-utils`
+6. Install desired hypervisor drivers (Virto, Open-VM Tools)
+7. Install git by running `sudo apt install git`
+8. As Debian 9 includes network manager ensure this is disabled. Change the below file
+
+#### Results
+
+```
+```
+/etc/NetworkManager/NetworkManager.conf
+```
+```
+
+to the following:
+
+```
+```
+managed=false
+```
+```
+
+We also recommend disabling network manager and setting the network adapter to eth0 rather than the automatically assigned name. See a more detailed guide on VMware image prep [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware_templates.html?highlight=vmware%2520image%2520prep#creating-a-centos-rhel-7-image).
+
+To import your template into vCloud director you will need to login as either an administrator or organisation administrator.
+
+Once logged into vCloud director you will then need select `Manage Organizations` and then select your organization.
+
+From within the organisation click on `Catalogues` > select an existing catalogue or create a new catalogue.
+
+NOTE
+
+Please note once you connect HPE Morpheus Enterprise to your vCD environment, it will create a catalogue called Auto HPE Morpheus Enterprise. This is a working catalogue and is ignored by HPE Morpheus Enterprise when searching for images, so any images in the catalogue will not be synced into HPE Morpheus Enterprise
+
+Open the catalogue and select the import template from vCenter and then browse the data stores for your templates. Select your template and the type in a new name and description then check the copy template into vCloud director.
+
+Once you click ok the import process will begin. When the import has completed the template will appear in HPE Morpheus Enterprise within Library > Virtual Images
+
+If the image does not appear within the virtual images you may need to use the filters to filter the virtual images by the vmware ( vmdk / ovf / ova) type.
+
+You may also need to refresh the cloud. To do this go to Infrastructure  >  Clouds > select the vCloud Director cloud > selectRefresh.
+
+​
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.json b/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
new file mode 100644
index 0000000..e2cb6e8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+  "title": "phpIPAM",
+  "ordinal": 508,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html",
+  "topic_cluster": {
+    "clustering_title": "phpIPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.md b/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
new file mode 100644
index 0000000..251c04e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
@@ -0,0 +1,30 @@
+# phpIPAM
+
+## Configuration
+
+### Procedure
+
+1. Within phpIPAM dashboard, enable api in Administration > phpIPAMsettings > featuresettings. Toggle API switch to `on` and save.
+2. Go to Admin > API > create API key.
+3. Create unique App ID.
+4. Enable `read/write/admin` access under App Permissions.
+5. Under App Security select `SSL with User Token`.
+
+## Add phpIPAM integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select + ADD > IPAM > phpIPAM
+3. Enter the following: 
+
+   - Name
+   - URL
+     :   Add `/api/` to end of URL ex. `http://10.30.20.196/api/`
+   - App ID
+     :   From phpIPAM API Key
+   - Username
+   - Password
+   - Enable or Disable SSL SNI Verification
+   - Enter Network Filter
+4. Select SAVE IPAM INTEGRATION
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json b/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
new file mode 100644
index 0000000..efea875
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+  "title": "Creating an HPE BMaaS Cloud",
+  "ordinal": 402,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an HPE BMaaS Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md b/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
new file mode 100644
index 0000000..9f3d9e5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
@@ -0,0 +1,38 @@
+# Creating an HPE BMaaS Cloud
+
+## About this task
+
+Creating an HPE BMaaS Cloud integrates physical infrastructure into the Morpheus management plane, establishing a logical boundary for bare-metal resources to enable group-based policies and proxy configurations. This setup allows for onboarding HPE ProLiant servers for automated provisioning and lifecycle management.
+
+To create an **HPE BMaaS Cloud** in Morpheus for HPE ProLiant bare-metal operations, follow this procedure:
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds in the Morpheus interface.
+2. Click the + Add button.
+3. Locate and select the HPE BMaaS Cloud type as HPE Bare Metal (BMaaS), and then click Next.  
+   ![Create Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C875F0A7-EDDE-42E3-B87B-DE90F18B9A51-high.png)
+4. Enter the name, code, Labels, Location, and complete any additional required details for the cloud.   
+   ![Cloud Configure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0C50D8A2-3CA6-416E-AA73-0DA3FA82167B-high.png)
+5. **Optional:**  In Provisioning Command, select a Proxy for provisioned bare metal instances if required, then click Next.  
+   ![Provisioning Command](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-172BEA46-96D8-4D0D-83D8-B0D6428A0ED5-high.png)
+6. For the group, you may either select Use Existing or Create New: 
+
+   - To use an existing group, choose Use Existing and select the desired group from the drop-down list.   
+     ![Existing Group](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6EC50EB8-DE0B-43B4-A168-B43E3A87CAB5-high.png)
+   - To create a new group, select Create New and follow the on-screen prompts.   
+     ![Create New](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-213FFFF2-8183-4E33-A2A3-9437A433373E-high.png)
+7. Click Next to review your cloud configuration details, then click Complete to finalize cloud creation.
+
+   NOTE
+
+   By default, the Network Mode is set to Unmanaged for the created Bare metal cloud. If you need to use ArubaCX integration, modify the Bare metal cloud and set the Network Mode to the ArubaCX-Integration.
+
+## Results
+
+After completion, the newly created group appears in the list of groups.   
+![Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3917DB5B-D58F-4FFF-A06C-40BD5401CFE7-high.png)
+
+**Subtopics**  
+
+- **[Default Unmanaged Network Support](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json b/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
new file mode 100644
index 0000000..eebf637
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+  "title": "Templates",
+  "ordinal": 158,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html",
+  "topic_cluster": {
+    "clustering_title": "Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md b/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
new file mode 100644
index 0000000..18d9384
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
@@ -0,0 +1,11 @@
+# Templates
+
+Templates can be created directly in HPE Morpheus Enterprise and/or sourced from version control, depending on the type. They can be used to help users consume IaC technologies, generate configuration files, utilize scripts or store security scan packages. Once stored, they can be used with provisioned Instances, configured as part of Tasks or Workflows, or run regularly as part of security scan Jobs. Each section below discusses template types in greater detail.
+
+**Subtopics**  
+
+- **[Spec Templates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html)**
+- **[File Templates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html)**
+- **[Script Templates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html)**
+- **[Security Packages](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ED404402-F168-4635-ADEB-02609465196E.html)**
+- **[Cluster Packages](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.json b/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
new file mode 100644
index 0000000..c371764
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+  "title": "Automation Integrations",
+  "ordinal": 375,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.md b/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
new file mode 100644
index 0000000..0391986
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
@@ -0,0 +1,10 @@
+# Automation Integrations
+
+**Subtopics**  
+
+- **[Ansible](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html)**
+- **[Ansible Tower](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html)**
+- **[Chef](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html)**
+- **[Puppet](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html)**
+- **[Terraform](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html)**
+- **[vRealize Orchestrator](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json b/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
new file mode 100644
index 0000000..cc4369a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+  "title": "Guidance",
+  "ordinal": 71,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html",
+  "topic_cluster": {
+    "clustering_title": "Guidance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md b/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
new file mode 100644
index 0000000..6b99eae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
@@ -0,0 +1,93 @@
+# Guidance
+
+## Overview
+
+The Operations  >  Guidance section shows recommendations for resource and cost optimization. By analyzing the CPU, RAM, and Storage activity of Instances and Hosts, HPE Morpheus Enterprise can recommend actions for sizing and power state. Guidance is customizable to show recommendations based on 30, 60, or 90 day periods, this dropdown toggle is visible on the Guidance list page (Operations > Guidance). Guidance thresholds are also customizable, they can be edited in Administration > Settings > Guidance.
+
+### Configuration
+
+#### About this task
+
+Guidance is configured per Cloud and is turned off by default.
+
+To turn on HPE Morpheus Enterprise Guidance for a Cloud:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click EDIT
+3. Expand the Advanced Options section in the Edit Cloud modal
+4. In the Guidance dropdown, select Manual
+5. Click SAVE CHANGES
+
+#### Results
+
+Guidance recommendations will begin to appear in the guidance section when generated.
+
+NOTE
+
+It will take approximately seven days before HPE Morpheus Enterprise gathers sufficient data to make guidance recommendations.|morpheus| Guidance is significantly improved when the Agent is installed on provisioned workloads. When the Agent is not installed, HPE Morpheus Enterprise still makes a best effort to provide relevant guidance recommendations.
+
+Once Guidance has been turned on for a Cloud, HPE Morpheus Enterprise will determine if a guidance recommendation should be made once every 30 minutes. In the event that no recommendations can be made, no entry will be added to the list of suggested guidances. As the guidance list continues to grow, sorting and filtering may become necessary to focus on the recommendations that are relevant to the user at the time.
+
+It’s important to note that acting on recommendations is entirely manual at this time. In many cases, Morpheus provides one-click action to take the recommended steps but Guidance recommendations cannot be taken automatically. This is a feature that is being explored for a future update but has not been tagged for any specific release version at this time. In addition, it’s recommended that HPE Morpheus Enterprise Agent be installed to maximize the benefits of Guidance. While Guidance will still work without installing the Agent, the greatly-enhanced statistics provided by the Agent will significantly improve Guidance recommendations.
+
+To see more detail on a Guidance recommendation in your list, click on the (i) button at the far right side of each list row. This will open a detail modal that gives additional information on the Guidance entry. In some cases, such as with sizing and shutdown recommendations, the user can simply click the “EXECUTE” button to take the recommended action as shown below.
+
+![The execute button allows the user to immediately take action on a sizing recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6493DA77-2790-4079-9636-57D2B389DBCD-high.png)
+
+Other types of Guidance recommendations, such as reserve compute recommendations, must be taken in the cloud and Morpheus does not offer the execute button.
+
+![The execute button is not present on a reserve compute recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-88431DCD-48BE-4414-BC59-89F31565FE07-high.png)
+
+NOTE
+
+The IGNORE button will remove the recommendation from the UI. Subsequent recommendations of the same type will NOT display for the same object (VM, Cloud etc) again unless the original recommendation is resolved.
+
+### Recommendations
+
+To view and act on Guidance recommendations, navigate to Operations  >  Guidance.
+
+The Guidance list contains the following details:
+
+Severity Icon
+:   Indicates the severity of the recommended action.
+
+Type
+:   Recommended action Type
+
+Metric
+:   Guidance Metric used for recommended action.
+
+Action
+:   Recommended Action for the Instance or Host, such as “Reduce Host memory” or “Shutdown Instance”
+
+RESOURCE
+:   The Instance or Host targeted
+
+SAVINGS
+:   Shows projected Monthly Costs savings if recommended action is taken.
+
+DATE
+:   Date and Time stamp the recommended action was generated.
+
+Information Link
+:   Click to view details on the recommendation.
+
+NOTE
+
+Guidance Actions are not automatically triggered at this time.
+
+### Filters
+
+Search
+:   Search for Guidance recommendations
+
+Type
+:   Filter by Sizing or Shutdown Guidance Types.
+
+Severity
+:   Filter by Guidance Severity of All, Info, Warning, or Critical.
+
+Metric
+:   Filter by All, Memory, CPU, or Power Guidance Metrics.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json b/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
new file mode 100644
index 0000000..833566b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+  "title": "AWS Route53",
+  "ordinal": 484,
+  "parent_title": "DNS",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html",
+  "topic_cluster": {
+    "clustering_title": "AWS Route53",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md b/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
new file mode 100644
index 0000000..3ca30c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
@@ -0,0 +1,78 @@
+# AWS Route53
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with Amazon Route 53 to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in Route 53 Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add Route 53 Integration
+
+### About this task
+
+Route 53 can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   Route 53
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   REGION
+   :   AWS Region for the Integration
+
+   ACCESS KEY
+   :   AWS User IAM Access Key
+
+   SECRET KEY
+   :   AWS User IAM Secret Key
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, Route 53 Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring Route 53 with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..6b313b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 110,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..10ffdf2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1,40 @@
+# Task Management
+
+## Adding Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary signficiantly based on the selected Task type. More details on each Task type are contained in the preceding sections.
+6. Once done, click SAVE CHANGES
+
+### Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference HPE Morpheus Enterprise variables which pertain to the specific Instance the Task is being run against. HPE Morpheus Enterprise includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and HPE Morpheus Enterprise will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus Enterprise API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
+
+![../../_images/taskvars.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BA459071-AEAD-4E96-8DB9-FD67DDE9ABC5-high.png)
+
+## Editing Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
+
+## Deleting Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json b/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
new file mode 100644
index 0000000..6bd4d93
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+  "title": "Kubernetes Blueprints",
+  "ordinal": 135,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md b/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
new file mode 100644
index 0000000..863a6fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
@@ -0,0 +1,39 @@
+# Kubernetes Blueprints
+
+HPE Morpheus Enterprise allows you to store Kubernetes configuration YAML files for easy deployment on-demand. Kubernetes Blueprints can be built by pulling in Kubernetes spec stored as a HPE Morpheus Enterprise Spec Template object, those tracked under version control in a Git repository, or you can write them directly in the New Blueprint modal.
+
+To create a new Kubernetes Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Kubernetes. NEXT
+
+In the Cluster Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Complete the Kubernetes Configuration section as follows depending on your Config Type selection.
+
+To consume a HPE Morpheus Enterprise Spec Template containing Kubernetes spec:
+
+- **CONFIG TYPE:** “Kubernetes Spec”
+- **SPEC TEMPLATE:** Use the typeahead field to locate the desired Spec Template
+
+To draft or paste configuration directly in the New Blueprint modal:
+
+- **CONFIG TYPE:** “Kubernetes Yaml Spec”
+- **CONFIG:** Enter your YAML configuration template here
+
+To consume YAML configuration files tracked in a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new Kubernetes Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json b/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
new file mode 100644
index 0000000..0a14f98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+  "title": "LDAP Query Variables",
+  "ordinal": 156,
+  "parent_title": "Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html",
+  "topic_cluster": {
+    "clustering_title": "LDAP Query Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md b/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
new file mode 100644
index 0000000..8bad4f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
@@ -0,0 +1,29 @@
+# LDAP Query Variables
+
+The current user and dependant parameters are loaded into the query using the <%=phrase%> syntax.
+
+```
+```
+LDAP Query Variables (Example <%=user.email%>)
+```
+```
+
+```
+```
+ user {  
+    accountId,  
+    attributes,  
+    displayName,  
+    email,  
+    firstName,  
+    id,  
+    lastName,  
+    linuxUsername,  
+    username,  
+    windowsUsername  
+ }  
+ customOptions {  
+    fieldName  
+ }
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..655747e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 107,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..6f710f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,60 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
+
+## Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A HPE Morpheus Enterprise-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the HPE Morpheus Enterprise appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
+
+## Execute Options
+
+- **Continue on Error:** When marked, Workflows containing this Task will continue and will remain in a successful state if this Task fails
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) HPE Morpheus Enterprise will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
+
+## Source Options
+
+Task configuration code may be entered in a number of ways depending on the Task type. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing. Not every Task type supports every sourcing type listed here.
+
+- **Local:** The Task configuration code is written directly in HPE Morpheus Enterprise in a large text area. HPE Morpheus Enterprise includes syntax highlighting for supported Task languages for easier debugging and script writing
+- **Repository:** Source the Task configuration code from an integrated Git or Github repository. This requires a pre-existing integration with a Github or other Git-based repository. See the [relevant integration guides](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for full details on creating such an integration. Specify the path to the appropriate file through the WORKING PATH field. The appropriate branch may also be specified (if a branch other than ‘main’ is required) in the BRANCH/TAG field. To reference a tag from this field, use the following syntax: `refs/tags/<tag-name-here>`. Unless otherwise specified, Task config is sourced fresh from the repository each time the Task is invoked which ensures the latest code is always used
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
+
+## Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. If the Task is to be part of an Operational Workflow, mark the same box on the Workflow rather than on the Task to see the text area at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json b/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
new file mode 100644
index 0000000..40ff061
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+  "title": "Boot Volume Selection During Instance Creation for Local Storage",
+  "ordinal": 438,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md b/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
new file mode 100644
index 0000000..76cf228
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
@@ -0,0 +1,47 @@
+# Boot Volume Selection During Instance Creation for Local Storage
+
+During Morpheus instance creation, the provisioning workflow will **delete existing logical volumes**, **create a boot volume**, and then **identify the correct disk device** using the device’s unique identifier (UID).
+
+The boot volume is determined by matching the device UID found in the storage controller to the corresponding Linux device path.
+
+## Log Details
+
+When creating a Morpheus instance, you may see the following log entries:
+
+```
+```
+[2026-02-09 02:45:39,023] ... Deleting all logical volumes on server  
+[2026-02-09 02:45:42,887] ... Attempting to create boot volume  
+[2026-02-09 02:45:43,470] ... Waiting for device discovery complete. Success  
+[2026-02-09 02:45:44,442] ... GET /redfish/v1/.../Drives/2556 -> error: ResourceMissingAtURI ... Retrying in 10 seconds...  
+[2026-02-09 02:45:44,442] ... Boot volume for server created with unique identifier: 600508B1001C40706B7600592D4A5C5A
+```
+```
+
+The logs show:
+
+- Logical volumes are cleared on the server.
+- Morpheus creates a new boot volume.
+- The system waits for Redfish device discovery to complete.
+- If a drive is not yet visible, it may return `ResourceMissingAtURI` and retry.
+- Once the boot volume is created, it logs the unique device identifier.
+- How Boot Volume is Determined.
+
+For OS installation, the boot volume is identified based on the **device UID**. Depending on the server storage controller, the device UID format differs
+
+Table 1. UID Format
+
+       | Storage Device | Name | RAID Type | Identifiers.DurableNameFormat | Identifiers.DurableName |
+| --- | --- | --- | --- | --- |
+| HPE MegaRAID (MR216i-o) Storage Controller | BootVolume | RAID1 | NAA | 600508B1001C40706B7600592D4A5C5A |
+| HPE NVMe SHIELD (NS204i) Boot Device | BootVolume | RAID1 | EUI | 1234:5678:9ABC:DEF0 |
+
+## Finding the Device Path
+
+Once the device UID is known (from the storage controller), the provisioning script searches for the matching device in `/dev/disk/by-id/`
+
+The script looks for the **first entry that contains the UID** (or a stripped version of the UID). These entries are **stable identifiers** that point to the actual Linux block device.
+
+Once a match is found, the script resolves the symbolic link to determine the real boot device path, which will be in the form: `/dev/sdX`
+
+This `/dev/sdX` path is then used for OS installation.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json b/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
new file mode 100644
index 0000000..8e4ead1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+  "title": "Unisys Stealth",
+  "ordinal": 516,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html",
+  "topic_cluster": {
+    "clustering_title": "Unisys Stealth",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md b/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
new file mode 100644
index 0000000..0b502d8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
@@ -0,0 +1,182 @@
+# Unisys Stealth
+
+## Introduction
+
+Unisys Stealth is a network security tool for safeguarding sensitive information across shared networks. By creating pre-defined communities of interest (COIs) and curating user access to these groups, the need to create separate networks for handling restricted data is reduced.
+
+HPE Morpheus Enterprise includes a full integration with Stealth allowing administrators to create and manage COIs, work with configurations and roles, and provision new endpoints into COIs.
+
+## Stealth Concepts
+
+- **Communities of Interest (COIs):** A collection of endpoints cryptographically separated so they can only communicate to each other
+- **Endpoints:** Any system or device with a Stealth agent
+- **Configuration:** Tells the endpoints which authorization methods and services to use for obtaining COI membership
+- **Role:** Defines COI membership. Users and groups are assigned to a role which grants access to that role’s COIs
+- **Filters:** Customizes Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints
+
+## Integrating Stealth with HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Click + ADD
+3. Complete the following fields: 
+
+   - NAME: A name for this Stealth integration in HPE Morpheus Enterprise
+   - API HOST: The address for the server hosting Stealth (ex: <https://x.x.x.x:8448>)
+   - USERNAME: A username for the portaladmin, or the user who logs into the web console
+   - PASSWORD: A password for the account
+   - MANAGER USERNAME: A username for the manager account
+   - MANAGER PASSWORD: A password for the manager account
+4. Click ADD SECURITY INTEGRATION
+
+### Results
+
+![../../_images/add_stealth.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E5EFDABE-E6AE-4E24-A24A-E39E52F95B1D-high.png)
+
+## Summary View
+
+The default view when accessing a Stealth integration in HPE Morpheus Enterprise is the Summary view. In addition to basic information about the Stealth server itself, we can see system status, license and service information.
+
+![../../_images/stealth_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2EDC17EA-E415-404A-936D-E6FCC06BD235-high.png)
+
+## Endpoints
+
+Endpoints are any system or device with a Stealth agent. Stealth endpoints can be provisioned in HPE Morpheus Enterprise in the same way other cloud resources are provisioned. With Stealth integrated, workloads provisioned on the appointed networks are assigned Stealth configuration and a Stealth role during the provisioning process. Based on a user’s assigned roles and COIs assigned to those roles, only workloads on the appointed COIs will be visible to the user. Additionally, workloads can only see other workloads within their COI.
+
+NOTE
+
+Machines on the same network which are not Stealth-managed will be able to see and communicate with each other but will not be able to see workloads which are assigned to a Stealth COI.
+
+### Endpoints View
+
+The endpoints view will display all available Stealth-managed resources. Endpoints are not created here but will be synced into this view as they are created (through HPE Morpheus Enterprise provisioning or outside creation). Stealth-managed endpoints can be deleted by clicking the trash can icon at the end of each row in this view.
+
+The following fields are exposed in the endpoints list view:
+
+- **DISPLAY NAME**
+- **NAME**
+- **DESCRIPTION**
+
+## Configurations
+
+Configurations in Stealth are the top-level construct and house COIs, roles, groups, users and endpoints. Your Stealth integration will include at least one configuration but often they will include more.
+
+Configurations are primarily created and managed from the Stealth console but we can opt to remove them from HPE Morpheus Enterprise by clicking the trash can icon at the end of each row on the configurations list page. Configurations are selected along with a Stealth role at provision time in HPE Morpheus Enterprise.
+
+### Configurations View
+
+The following fields are exposed in the configurations list view:
+
+- **NAME:** The name of the configuration
+- **DESCRIPTION:** A description value for the configuration
+
+## Roles
+
+Users are placed into roles which are associated with COIs. A user’s role(s) determine which COIs he or she will be able to see and access. Roles are synced into HPE Morpheus Enterprise once the integration process is complete and can be viewed in the Roles list view. Roles can also be created from the HPE Morpheus Enterprise integration as described later in this section.
+
+### Roles View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the role
+- **DESCRIPTION:** A description value for the role
+
+NOTE
+
+More detail on each item in the roles list can be revealed by clicking on the (i) icon in each row, including the COIs associated with the role.
+
+### Creating Stealth Roles
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > Roles
+2. Click + CREATE ROLE
+3. Complete the following fields: 
+
+   - NAME: The name for the new role
+   - DESCRIPTION: A description value for the new role
+   - CONFIGURATION: Select an existing Stealth configuration to associate with the role
+   - ROLE TYPE: Identifies how the role is used. Can be Global (for roles used to isolate endpoints and users), Service (for roles used by endpoints in service mode to access an authorization service) or WorkGroup (for roles used by endpoints in normal operation)
+   - FILTER SET: Choose a filter set to apply to the role to allow or deny clear text communication with non-Stealth-managed endpoints
+   - COIs: Select the COIs to be associated with the role
+   - PROVISION CHANGES:
+4. Click ADD ROLE
+
+#### Results
+
+![../../_images/add_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FE9AB72A-8680-480B-98F5-3795480217A0-high.png)
+
+## COIs (Communities of Interest)
+
+COIs exist within configurations and create a logical separation between endpoints in separate COIs. Communication between endpoints in the COI is encrypted and those outside the COI are unable to see or access endpoints despite being on the same network.
+
+On completing the integration, HPE Morpheus Enterprise will sync in existing COIs. COIs can also be created from HPE Morpheus Enterprise UI which is described later in this section. COIs are deleted by clicking on the trash can icon at the end of each row in the COIs list view.
+
+### COIs View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the COI
+- **DESCRIPTION:** A description value for the COI
+
+### Creating Stealth COIs
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > COIs
+2. Click + CREATE COI
+3. Complete the following fields: 
+
+   - NAME: The name for the new COI
+   - DESCRIPTION: A description value for the new COI
+   - TYPE: Workgroup or Service
+   - DIRECTION: Default (enables COI to accept inbound and initiate outbound tunnels), Initiate (restricts the COI to only initiate outbound tunnels), or Accept (restricts the COI to only accept inbound tunnels)
+4. Click CREATE COI
+
+#### Results
+
+![../../_images/create_coi.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EA1DA1E2-1AB6-494A-A776-013769EB3C4D-high.png)
+
+## Filters
+
+Filters customize Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints.
+
+Filters are synced into HPE Morpheus Enterprise when integrating with Stealth and are viewable from the filters list view. They are created and managed from within the Stealth console itself.
+
+When accessing the filters list view, all filter sets are displayed. Each filter set can be expanded to view the individual filters within. Information on each filter is displayed once the filter set has been expanded to reveal the individual filters.
+
+## Provisioning with Stealth
+
+In order to provision new Stealth-managed endpoints, Stealth must be integrated with HPE Morpheus Enterprise as described above. In addition, Stealth must be selected as the Security Server for the cloud you’re provisioning into. Security servers can be selected at the time a new Cloud integration is created or by editing an existing Cloud integration.
+
+### Choosing a Cloud Security Server
+
+#### About this task
+
+Assuming the Cloud is already integrated with HPE Morpheus Enterprise, use the steps below to set the security server and activate Stealth prompts at provision time. The steps to set the security server during the time the cloud is initially integrated with HPE Morpheus Enterprise is very similar.
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds > (Your Selected Cloud)
+2. Click EDIT
+3. Click on Advanced Options to reveal additional selections
+4. In the dropdown for SECURITY SERVER, choose an existing Stealth integration
+
+### Provisioning to a Stealth-enabled Cloud
+
+#### About this task
+
+Once we have selected our Stealth integration as the security server for at least one Cloud in HPE Morpheus Enterprise, new Instances (endpoints) can be provisioned and managed by Stealth.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Instance Type, Cloud, and Group making sure to choose a Cloud that has been set up for an existing Stealth integration
+4. On the Configure tab of the provisioning wizard, choose a Stealth Configuration and a Stealth Role according to the needs of the machine(s) being provisioning
+5. Once the provisioning process is complete, the new Stealth-managed endpoints will be available and restricted based on the Stealth implementation
+
+#### Results
+
+![../../_images/provision_endpoint.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C5EBFD40-8381-4497-9E9F-05EEC4AB65F6-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..dd95902
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 506,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..1a23f68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,15 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[Infoblox](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html)**
+- **[phpIPAM](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html)**
+- **[NSX](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html)**
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
+- **[NSX Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html)**
+- **[Cisco ACI](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html)**
+- **[Bluecat](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html)**
+- **[SolarWinds IPAM](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html)**
+- **[Unisys Stealth](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html)**
+- **[EfficientIP SOLIDserver](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json b/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
new file mode 100644
index 0000000..3e81830
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+  "title": "Hyper-V",
+  "ordinal": 459,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.html",
+  "topic_cluster": {
+    "clustering_title": "Hyper-V",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md b/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
new file mode 100644
index 0000000..b737769
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
@@ -0,0 +1,179 @@
+# Hyper-V
+
+Hyper-V is the virtualized server computing environment introduced by Microsoft. Hyper-V is consumed by HPE Morpheus Enterprise as a private cloud offering and is a common hypervisor technology in data centers. HPE Morpheus Enterprise provides an avenue to aggregate Hyper-V resources together to allow efficient and seamless deployment of applications as a virtual machine (VM) or Docker host in the world of Hyper-V.
+
+## Features
+
+- Virtual Machine Provisioning
+- Discovery of Existing Instances
+- Containers
+- Backups / Snapshots
+- Resources Groups
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Veeam Integration
+- Lifecycle Management and Resize
+- Unique Kerberos Authentication
+
+## Getting Started
+
+To get started, a few prerequisites must first be met. The Hyper-V host must be installed with its firewall enabled and it can either be joined to a domain or standalone. The Hyper-V host must also have the external network of Hyper-V configured and it can share this network with the management operating system. A user account that is part of the local administrators group on the Hyper-V host is also required. This document covers Hyper-V 2008 and Hyper-V 2012.
+
+## Understanding WinRM
+
+HPE Morpheus Enterprise uses WinRM to communicate to the Hyper-V host for deployment of the HPE Morpheus Enterprise Agent. The HPE Morpheus Enterprise Agent allows for the host dashboard to be populated with information in the form of graphs that cover CPU, Network, Storage, and memory consumption. Furthermore, this Agent provides logging and monitoring capabilities.
+
+If Windows Remote Management (WinRM) is not installed and configured, WinRM scripts do not run and the WinRM command line tool cannot perform data operations or allow for the HPE Morpheus Enterprise Agent to be installed. WinRM uses HTTP port 5985 or HTTPS port 5986 for communications.
+
+To better understand all of the default settings of WinRM please refer to the [following page](https://msdn.microsoft.com/en-us/library/aa384372%28v=vs.85%29.aspx) in Microsoft documentation.
+
+## Native Authentication
+
+To configure WinRM with default settings (WINRM\_NATIVE)
+
+Type the following command at a command prompt:
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the Runas command at a command prompt.
+
+When the tool displays `Make these changes [y/n]?`, type `y`.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. By default Kerberos is enabled and if domain authentication is not being used we want to disable that. Issue the below commands to setup basic authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth '@{Basic="true"}'  
+$ winrm set winrm/config/service '@{AllowUnencrypted="true"}'  
+$ winrm set winrm/config/service/Auth '@{Kerberos="false"}'
+```
+```
+
+## Domain Authentication
+
+To configure WinRM with Domain Authentication (WINRM\_INTERNAL)
+
+Type the following command at a command prompt
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the runas command at a command prompt.
+
+When the tool displays Make these changes [y/n]?, type y.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. Issue the below commands to setup domain authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth @{Basic="true"}  
+$ winrm set winrm/config/service @{AllowUnencrypted="false"}  
+$ winrm set winrm/config/service/Auth @{Kerberos="true"}
+```
+```
+
+Kerberos authentication will also need to be configured on the HPE Morpheus Enterprise appliance to support Windows domain accounts to access the remote host with WINRM\_INTERNAL connection type.
+
+On the HPE Morpheus Enterprise appliance the krb5-user package must be installed.
+
+For Ubuntu the command is as follows:
+
+```
+```
+$ sudo apt-get install krb5-user
+```
+```
+
+For Centos the command is as follows:
+
+```
+```
+$ sudo yum install krb5-workstation pam_krb5 -y
+```
+```
+
+Create a file in /etc called krb5.conf and replace the domain name with the name of the domain to be used. In this case we used HPE Morpheus Enterprise .com as the domain.
+
+```
+```
+[libdefaults]  
+        default_realm = |morpheus| .COM  
+            dns_lookup_kdc = true  
+            verify_ap_req_nofail = false  
+        default_tgs_enctypes = rc4-hmac  
+        default_tkt_enctypes = rc4-hmac  
+[realms]  
+        |morpheus| .COM = {  
+                kdc = win-ad.|morpheus| .COM:88  
+                admin_server = win-ad.|morpheus| .COM:749  
+     }  
+[domain_realm]  
+    .|morpheus| .COM = |morpheus| .COM  
+        |morpheus| .COM = |morpheus| .COM  
+[login]  
+     krb4_convert = true  
+     krb4_get_tickets = false
+```
+```
+
+After creation of the krb5.conf a keytab file is also required. See below for instructions on how to create a keytab file. <http://www.itadmintools.com/2011/07/creating-kerberos-keytab-files.html>
+
+## Adding Hyper-V as a Private Cloud
+
+The Hyper-V host is prepared for HPE Morpheus Enterprise to communicate with it via WinRM so the Hyper-V private cloud is ready to be configured. Create a group and then create a HPE Morpheus Enterprise cloud for Hyper-V. Populated the information as show in Figure 1: specific for the environment being configured.
+
+![../../../_images/hyperv1_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-23A922A0-C860-4705-AA64-BF5363B4B77A-high.png)
+
+NOTE
+
+The working path, vm path, and disk path should be created on the Hyper-V host by the Hyper-V administrator. If these paths are not created they will need to be setup and the Hyper-V settings will need to adjusted to reference them.
+
+![../../../_images/hyperv2_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F3DBACFA-EE94-4CE0-AF6F-D79405736F55-high.png)
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Hyper-V or create a new one. These are managed from the Admin > Plans& Pricing section.
+
+![../../../_images/hyperv3_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F6FDCC9D-AFEE-4EF5-B32C-A8B200171F83-high.png)
+
+## Docker
+
+So far this document has covered how to add the Hyper-V cloud integration and has enabled users the ability to provision virtual machine-based instances via the Add Instance catalog under the Provisioning menu. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into Hyper-V (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there click + ADD CLUSTER to add a Hyper-V Docker Host. A cluster is created when adding Docker hosts, even when only one host is needed.
+
+HPE Morpheus Enterprise views a Docker host just like any other hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Admin | Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..bf42788
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 197,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..38f279e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..b23dbce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 187,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..874a2b5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json b/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
new file mode 100644
index 0000000..9897304
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+  "title": "Deployment",
+  "ordinal": 480,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md b/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
new file mode 100644
index 0000000..2718a65
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
@@ -0,0 +1,6 @@
+# Deployment
+
+**Subtopics**  
+
+- **[Git](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html)**
+- **[Github](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json b/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
new file mode 100644
index 0000000..50a7021
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+  "title": "Instances",
+  "ordinal": 83,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md b/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
new file mode 100644
index 0000000..bfffb3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
@@ -0,0 +1,26 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self service features and spinning up both VMs and containers. In HPE Morpheus Enterprise it may be advisable to cover the definition of a few terms used within the application so as to reduce confusion. These concepts are also covered in greater detail in the [Provisioning Concepts](https://docs.morpheusdata.com/en/latest/provisioning/concepts/concepts.html) section.
+
+Instance
+:   A set of containers or virtual machines that can correlate to a single horizontally-scalable entity or a service suite, like a database. It is important to note that an Instance can contain one or more containers/VMs depending on the Instance type and configuration.
+
+Container
+:   Typically a docker container provisioned via a HPE Morpheus Enterprise Docker host.
+
+Virtual Machine
+:   A virtualized compute server provisioned onto various hypervisor hosts.
+
+The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, instance type, or category.
+
+NOTE
+
+Instances listed are determined by group access and role permissions. When filtered to show Instances of “All Statuses”, any Instances which are in a state of pending removal due to a delayed delete policy in place are not shown under this filter. Instead you must filter for “Pending Removal” to see these Instances and prevent deletion, if desired.
+
+The Instance list contains important information about each instance, including the instance name, environment tag, instance type icon, IP address and port info, Instance version, the number of virtual machines or containers in the instance, the group the instance is in, and the cloud or clouds the instance is in.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html)**
+- **[Instance Details](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json b/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
new file mode 100644
index 0000000..96008bc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+  "title": "Components",
+  "ordinal": 7,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html",
+  "topic_cluster": {
+    "clustering_title": "Components",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md b/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
new file mode 100644
index 0000000..20686cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
@@ -0,0 +1,13 @@
+# Components
+
+The Appliance Server automatically installs several components for the operation of HPE Morpheus Enterprise. This includes:
+
+- RabbitMQ (Messaging)
+- MySQL (Logistical Data store)
+- Opensearch (Logs / Metrics store)
+- Tomcat (HPE Morpheus Enterprise Application)
+- Nginx (Web frontend)
+- Guacamole (Remote console service for clientless remote console)
+- Check Server (Monitoring Agent for custom checks added via UI)
+
+All of these are installed in an isolated way using chef zero to `/opt/morpheus`. It is also important to note these services can be offloaded to separate servers or clusters as desired. For details check the installation section and high availability.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..3e0a752
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 475,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..a8629b5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,591 @@
+# VMware vCenter
+
+## Overview
+
+VMware is a very common cloud integration choice supported by HPE Morpheus Enterprise . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so HPE Morpheus Enterprise covers a broad feature set in vCenter.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Affinity Groups
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
+
+## VMware Permissions
+
+When integrating VMware vCenter with HPE Morpheus Enterprise, users must supply credentials for a vCenter account and HPE Morpheus Enterprise will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that HPE Morpheus Enterprise can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict HPE Morpheus Enterprise only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a HPE Morpheus Enterprise Cloud integration.
+
+### Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my HPE Morpheus Enterprise integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
+
+### Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows HPE Morpheus Enterprise to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in HPE Morpheus Enterprise, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, HPE Morpheus Enterprise will look into this folder to onboard VMware images into HPE Morpheus Enterprise.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
+
+### Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in HPE Morpheus Enterprise without running into permissions errors.
+
+## Creating a HPE Morpheus Enterprise VMware Image
+
+HPE Morpheus Enterprise comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within HPE Morpheus Enterprise.
+
+NOTE
+
+A HPE Morpheus Enterprise appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple HPE Morpheus Enterprise Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via HPE Morpheus Enterprise.
+
+## Creating a Windows Image
+
+### Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
+
+### Image Preparation
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+#### Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and HPE Morpheus Enterprise Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+#### Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
+
+## Creating a CentOS/RHEL 7 Image
+
+### About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+### Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within HPE Morpheus Enterprise , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
+
+### Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+## Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+### Prepare The New CentOS 8/RHEL8 Image
+
+#### Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
+
+### SELinux Settings
+
+#### About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+#### Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
+
+### Network Interfaces
+
+#### About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+#### Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
+
+### Final VMWare Tasks
+
+#### Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the HPE Morpheus Enterprise side
+4. Refresh the HPE Morpheus Enterprise Cloud to allow the new template to sync
+
+## Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
+
+## A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json b/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
new file mode 100644
index 0000000..70ae73e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+  "title": "Overview",
+  "ordinal": 203,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md b/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
new file mode 100644
index 0000000..034a7d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
@@ -0,0 +1,9 @@
+# Overview
+
+The OpenShift integration adds a new Cluster type, which can be added to HPE Morpheus Enterprise from the Clusters list page (Infrastructure > Clusters). Once a pre-existing OpenShift cluster is integrated, HPE Morpheus Enterprise can onboard any currently-running virtualized workloads along with the cluster hosts, network objects, storage objects, and virtual images needed to provision additional virtualized workloads. In addition to a new Cluster type, the OpenShift integration adds a new Instance Type to the provisioning wizard, which is used to provision new Instances to any integrated Clusters.
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise and is not part of the product by default. Information on accessing the plugin and adding it to the HPE Morpheus Enterprise appliance is included in a subsequent section.
+
+NOTE
+
+The OpenShift integration with HPE Morpheus Enterprise is currently limited to support of virtualized workloads only. There is not currently support for container-based workloads.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json b/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
new file mode 100644
index 0000000..00457ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+  "title": "Policies",
+  "ordinal": 315,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html",
+  "topic_cluster": {
+    "clustering_title": "Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md b/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
new file mode 100644
index 0000000..f54fdbc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
@@ -0,0 +1,8 @@
+# Policies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html)**
+- **[Creating Policies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json b/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
new file mode 100644
index 0000000..de009be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+  "title": "Workloads: Instance Usage",
+  "ordinal": 68,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md b/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
new file mode 100644
index 0000000..ea33ef2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Usage
+
+![../_images/10instanceusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-70A9C315-58C0-4BF7-94E0-3F370A17D1E4-high.png)
+
+The Instance Usage dashboard shows Instance counts, resource utilization, and cost breakdowns by Cloud. Administrators can set filters to limit the workloads that are considered for dashboard analysis and then see the results given by Cloud groupings.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Usage List
+
+All Clouds represented in the dashboard are listed here. For each Cloud, we see the total Instance count, total memory allotted, total storage allotted, total CPU cores, and the total price.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json b/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
new file mode 100644
index 0000000..36b4619
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+  "title": "HA Installation Overview",
+  "ordinal": 17,
+  "parent_title": "Installation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html",
+  "topic_cluster": {
+    "clustering_title": "HA Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md b/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
new file mode 100644
index 0000000..94b277a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
@@ -0,0 +1,47 @@
+# HA Installation Overview
+
+HPE Morpheus Enterprise provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability (HA) configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the HPE Morpheus Enterprise HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the HPE Morpheus Enterprise appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Messaging Tier. Each of these tiers have their own recommendations for High availability deployments.
+
+IMPORTANT
+
+This is a sample configuration only. Customer configurations and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment.
+
+## Application Tier
+
+The application tier is easily installed with the same apt or yum repository package that HPE Morpheus Enterprise is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. They can be configured across all regions and placed behind a central load-balancer or geo-based load balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is shared storage, which is necessary when it comes to maintaining deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. Alternatively, a simple NFS cluster can also be used to handle the shared storage structure. Alternatively, supported (Platform as a Service) PaaS offerings can be used that provide a NFS compatible shared storage, eliminating the need to manage the underlying infrastructure.
+
+## Transactional Database Tier
+
+The Transactional Database tier consists of a MySQL compatible database. It is recommended that a lockable clustered configuration be used, such as a Galera cluster, which can also provide high availability. Alternatively, supported PaaS offerings can be used that provide a mySQL compatible database, eliminating the need to manage the underlying infrastructure.
+
+## Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an Opensearch cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a java based system and does require a sizable chunk of memory for larger data sets. Alternatively, supported PaaS offerings can be used that provide an Opensearch compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. Alternatively, supported PaaS offerings can be used that provide a RabbitMQ compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## HA Installation Architectures
+
+3-Node HA (Recommended)
+:   In this architecture, all tiers are deployed on three machines by HPE Morpheus Enterprise during the installation, with the exception of the Transactional Database Tier. This provides HA not just for the HPE Morpheus Enterprise Application Tier but all underlying tiers that support HPE Morpheus Enterprise. The Transactional Database Tier will remain external, either as a separate cluster or PaaS, following the supported services. An external MySQL cluster must still be set up outside of the HPE Morpheus Enterprise app nodes.
+
+Distributed HA
+:   In this architecture, the tiers do not need to reside on the same machines, each can be hosted by a supported cluster or PaaS offering. This provides flexibility and reuse of already existing technologies such as RabbitMQ or Opensearch. Each tier should be architected to provide HA following the vendor’s documentation, to ensure no downtime for the HPE Morpheus Enterprise Application Tier.
+
+## Supported PaaS Offerings
+
+The Morpheus Application Tier can be deployed to any public or private cloud. Morpheus has underlying technologies that support the Application Tier, which can be automatically installed and embedded on the applications nodes. Alternatively, the services can be provided externally and not be embedded. Many cloud providers have Platform as a Service (PaaS) offerings of these underlying technologies but some are not native or don’t provide the performance required. Below is a list of PaaS offerings that are supported to be used for Morpheus:
+
+Table 1. PaaS Offering Support
+
+       | Cloud | Messaging (RabbitMQ) | Log (Opensearch) | Database (mySQL) | Shared Storage (NFS) |
+| --- | --- | --- | --- | --- |
+| AWS | Amazon MQ | Amazon OpenSearch | Amazon Aurora | Elastic File System |
+| GCP | N/A | N/A | mySQL Instance | Cloud Filestore |
+| Azure | N/A | N/A | N/A | Storage Account |
+| OCI | N/A | N/A | N/A | N/A |
+| Alibaba | N/A | N/A | N/A | N/A |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json b/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
new file mode 100644
index 0000000..75a366d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+  "title": "Upgrading Overview",
+  "ordinal": 21,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md b/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
new file mode 100644
index 0000000..4369bbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
@@ -0,0 +1,190 @@
+# Upgrading Overview
+
+IMPORTANT
+
+Known issue with embedded Opensearch upgrade: When upgrading to v5.4.8+, v5.4.9 or v5.5.1, there is a potential issue with embedded Opensearch clustering on rolling upgrades and existing data migration for all embedded Opensearch architechtures. Refer to the Release Notes for additional informaiton.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Upgrade Requirements
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and VM node packages from the package-repo when appliance free space is needed.
+
+IMPORTANT
+
+BACKUP YOUR DATABASE before the upgrade! You can use the [appliance backup job in Morpheus](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#create-a-backup-job), then [rollback and restore your appliance](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#restoring-an-appliance-from-backup) if needed. Make sure you download the backup before you do the upgrade!
+
+- For firewall/proxy/acl considerations, the domain for Appliance, Supplemental and Agent packages was changed recently to <https://downloads.morpheusdata.com> from <https://downloads.gomorpheus.com>. Please update ACL’s to allow access to <https://downloads.morpheusdata.com> when necessary.
+
+### v8.1.1 Compatibility & Breaking Changes
+
+When installing and upgrading to HPE Morpheus Enterprise v8.1.1, refer to the following to ensure compatibility.
+
+#### Breaking Changes
+
+- 7.0.8, 8.0.0: On first ui startup after upgrade, HPE Morpheus Enterprise will normalize all IPv6 records within HPE Morpheus Enterprise-type pools. There will be a warning in appliance logs warning how many records will be normalized. This takes between 5-15 minutes per 1m records
+- 7.0.8, 8.0.0: Updated the AccountUsage table in the appliance database to accept LONGTEXT data type to prevent data from oversetting the table in specific scenarios. Note that this schema change will take time for databases with large numbers of account usage records
+- 6.3.0: Version 6.3.0 is the first version to require Plugin API 1.0.0+. Small changes will need to be made in order to make plugins created for prior versions of HPE Morpheus Enterprise compatible with 6.3.0+. See the [related article in our KnowledgeBase](https://support.morpheusdata.com/s/article/Making-plugins-compatible-with-Morpheus-6-3-0?language=en_US) on the small changes that will need to be made to ensure plugin compatibility
+- 6.2.2, 6.0.7 v8.0.7 contains embedded MySQL v8 upgrade when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1. BACKUP YOUR DATABASE PRIOR TO UPGRADE when using embedded MySQL (all-in-one appliances)
+- 6.2.2, 6.0.7 Minimum v6.x required to upgrade to v8.0.7 for environments using embedded RabbitMQ. Environments running 5.5.x or earlier using embedded RabbitMQ must upgrade to v6.0.0 - v6.0.6, or 6.1.0 - 6.2.1 prior to upgrading to v8.0.7
+- 6.2.2, 6.0.7 Rolling upgrades for HA environments using embedded RabbitMQ and/or embedded Elasticsearch services are not supported when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1
+- 6.1.1 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records when upgrading from any version other than 6.0.3
+- 6.1.1 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades from any version other than 6.0.3 are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.1.1: NSX-V networking integration support is removed and no longer supported as of HPE Morpheus Enterprise 6.1.1
+- 6.0.3 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records.
+- 6.0.3 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.0.0: NSX-V support is deprecated though still supported as of HPE Morpheus Enterprise 6.0.0. It will be removed and unsupported in 6.1.1 and higher.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, many third party integrations have been moved out of the core installer package and converted to HPE Morpheus Enterprise plugins. As a result, during the upgrade process your appliance will need to be able to access share.morpheusdata.com, the online repository for all HPE Morpheus Enterprise plugins. Where this is not possible, users may instead apply the supplemental installer package which is also available at HPE Morpheus Enterprise Hub alongside the main installer package.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, older service specific system provided Instance Types and Layouts were deprecated and disabled. Updating to 6.0.0 will not affect existing Instances that are associated with the disabled types, however existing catalog item configurations, blueprints and api requests that use disabled Instance Types and layouts will need to be updated.
+- 5.5.2: VM Node Packages: Due to build java version requiremnets, the i386.deb and i386.rpm (32-bit) VM Node Packages can no longer be updated, and remain on v3.2.9.
+- 5.4.12: Guacd: Guacd is now complied iwth libssh2-1.10.0 on all platforms. Appliances on SLES15 may need openssl-devel manually installed for guacd to succesfully compile.
+- 5.4.12: Session Manager: Morpheus features a new session manager that was necessary in order to resolve expiring connections from the agents due to a Spring framework update. This new session manager no longer requires Sticky Sessions and they can now be turned off at the load balancer if so desired. However, keeping them on is totally reasonable as well as it reduces overall system load. Rolling restarts no longer kick you out of your session if sticky sessions are off as it distributes your session data across the morpheus nodes in an HA environment. Additionally, overall system load is reduced as a result of the new session manager.
+- 5.4.9: HPE Morpheus Enterprise 5.4.9 adds the “Provisioning: State” Role permission. This permission determines access to the State tab for Terraform-backed Instances and is set to “None” by default. On upgrade, only System Admin users will be able to see the State tab for these Instances. For other users who should have this access, edit their Roles to include “Provisioning: State” permissions.
+- 5.4.5: Warning: Database indexes added for account\_usage and metadata\_tag tables. Customers with very large account\_usage and/or metadata\_tag tables (10 million+) may experience slower initial morpheus-ui loading time after upgrading to 5.4.5, as well as additional database load.
+- 5.4.5: ‘AVI Load Balancer’ renamed to ‘NSX Advanced Load Balancer’
+- 5.4.5: Cloud Types disabled by default: Dell, HPE (NOT HPE Oneview), Supermicro and Cloud Foundry. Users would still be able to re-enable this clouds in the appliance settings. Does not affect existing Clouds.
+- 5.4.5: A10 Load Balancer type has been disabled, and will no longer be an option when adding new Load Balancers. This does not affect existing Load Balancers.
+- 5.4.5: HPE Morpheus Enterprise Cluster type “Combo Cluster” renamed to “KVM/Docker Cluster”
+- 5.4.5: Greenfield managed vm’s (provisioned with HPE Morpheus Enterprise) can no longer be deleted in HPE Morpheus Enterprise without removing the actual vm/infrastructure. Restriction does not apply to brownfield vm’s that have been converted to managed.
+- 5.4.4: The Venafi and AppDynamics integrations are deprecated in v5.4.4 and will be removed in v5.4.5. AppDynamic will return as a plugin at a later date.
+- 5.4.4: The morpheus-ui logging configuration file has changed from logback.groovy to logback.xml in v5.4.4 (/opt/morpheus/conf/logback.xml). The logback.groovy file from previous versions can be removed, and any updates to logback.groovy will not result in any logging configuration changes.
+- 5.4.3: vCloud Director: Support for integrations with vCD 9 ended
+- 5.4.3: HPE Morpheus Enterprise Worker/Gateway v5.4.3 packages are now available. Existing Worker & Gateway nodes must be upgraded to v5.4.3 for compatibility with HPE Morpheus Enterprise v5.4.3 Appliances.
+- 5.4.2: vCloud Director: vCD 9.x will no longer be supported by Morpheus
+- 5.4.2: ServiceNow: Instance and Blueprint specific exposures will be removed from ServiceNow plugin support. More advanced configurations of Instances and Blueprints, in addition to Workflows, can be exposed utilizing Catalog Items
+- 5.4.2: After upgrading, it is recommended that you manually perform one “Daily” refresh Amazon Clouds to ensure availability of Amazon Service Plans for each region. To manually refresh a Cloud, navigate to Infrastructure > Clouds > (Selected Amazon Cloud) and select “Daily” from the REFRESH dropdown menu. If this is not done, HPE Morpheus Enterprise may not show Amazon Service Plans in the provisioning wizard until after Midnight UTC following the upgrade when the next automatic Daily sync would run.
+- 5.3.3: Support for OpenStack v2 Identity API is removed
+- 5.3.2+: The local code repository path moved from `/var/opt/morpheus/morpheus-ui/repo` to `/var/opt/morpheus/morpheus-local/repo` to reduce potential shared storage issues and performance restrictions. The reconfigure process creates the folders and sets the paths in application.yml, no manual intervention is needed unless symlinks exisit on `/var/opt/morpheus/morpheus-ui/repo/git` which will need to be removed prior to reconfiguring - 5.3.2+ The deprecated `/var/opt/morpheus/morpheus-ui/repo` path will be automatically deleted in a future release but can be manually recursively deleted at any time for storage reclamation.
+- 5.3.2+: Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+- 5.2.9: OpenStack v2 Identity API is deprecated as of v5.2.9 (and is removed as of v5.3.3)
+- 5.2.6, 5.3.1: Appliance & Agent java version updated to `8u292-b10`. jdk8u292 disables TLS 1.0 and 1.1 by default
+- 5.2.3+: `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repo access required for RHEL 8+ Appliances, replacing the previous PowerTools/powertools requirement
+- 5.2.1 & 4.2.5: API: Metadata: Metadata tags now referred to as `tags` and labels now referred to as `labels`. Previously metadata tags were referred to as `metadata` and labels were referred to as `tags`
+- 5.0.0+: When upgrading to 5.0.0+ from 4.x.x, any bearer tokens that have been generated are deleted which requires users to request new bearer tokens
+- 4.2.4: For appliances with externalized MySQL databases, due to MySQL deprecation of the “EDT” timezone you may need to update your database timezone to UTC or another compatible value. If this is not done, you will receive errors referencing timezone and HPE Morpheus Enterprise will not start. HPE Morpheus Enterprise should handle this change automatically for all-in-one appliances.
+- 4.2.1+: Tasks: Python: Virtual environment are now used for Python Tasks. Note: `virtualenv` is required on all Appliance App nodes
+- 4.2.1+: Puppet: HPE Morpheus Enterprise integration now supports version 6+. Puppet versions prior to 6 are no longer supported
+- 4.2.1+: Clouds: VirtualBox, VirtuSteam, and MetaCloud Cloud Types are no longer supported or available
+- 4.2.1+: Appliance: OS: Ubuntu 14.04 has reached its end of life (EOL) and is no longer supported as a Morpheus Appliance Host Operating System. Any HPE Morpheus Enterprise Appliance running on 14.04 must be upgraded to 16.04, 18.04, 20.04, 22.04 or 24.04 BEFORE upgrading to 4.2.1+. Upgrades on 14.04 will not succeed
+
+#### HPE Morpheus Enterprise Application OS
+
+HPE Morpheus Enterprise can be installed on the following platforms. Please note the table below is for HPE Morpheus Enterprise Application OS support, not HPE Morpheus Enterprise Agent OS Support.
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| CentOS | 7.x (deprecated). 8.x (stream) 9.x (stream) |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+
+#### Services
+
+##### v8.1.1 Service Versions & Compatibility
+
+Table 2. v8.1.1 Service Versions and Compatibility
+
+      | Service | Compatible Branch | Current Installer Version | Updated in v8.1.1 |
+| --- | --- | --- | --- |
+| Plugin API | 1.3.3 | 1.3.3 |  |
+| Morpheus Worker | 5.4.8+ |  |  |
+| MySQL | v8.0 | v8.0.40 | Yes |
+| MySQL (FIPS) | v8.0 | v8.0.36 |  |
+| OpenSearch | v8.9+ | v8.15.5 |  |
+| RabbitMQ | v3.5-3.13 | v3.13.7 |  |
+| Tomcat |  | v9.0.106 |  |
+| Nginx |  | v1.26.2 |  |
+| OpenSSL |  | 1.1.1w, 1.0.2u (FIPS) |  |
+| Java |  | 17.0.14+7 |  |
+| Java (MacOS Agent) |  | 11.0.14+9 |  |
+
+##### HPE Morpheus Enterprise Agent & Node Package Versions
+
+Table 3. v8.1.1 Agent & Node Package Versions
+
+     | Package | Version | v8.1.1 changes from v8.1.0 |
+| --- | --- | --- |
+| Morpheus Node and VM Node Packages | 3.3.11 | Updated to 3.3.11 |
+| Morpheus Linux Agent | v3.1.0 | Updated to v3.1.0 |
+| Morpheus Windows Agent | v2.6.1.0 | No changes |
+| Morpheus macOS Agent | v2.4.0 | No changes |
+
+##### HPE Morpheus Enterprise Software Upgrade Paths
+
+Depending on the specific changes from version to version, HPE Morpheus Enterprise may support rolling upgrades for multi-node HA appliances. For some version hops, specific changes such as database schema modifications may make the upgrade unsuitable for a rolling upgrade. Use this table to confirm if a rolling upgrade will be possible in each case. Instructions for both rolling and non-rolling upgrades are contained in this documentation.
+
+Table 4. v8.1.1 Upgrade Paths
+
+                   | From Version | To 8.0.1 | To 8.0.2 | To 8.0.3 | To 8.0.4 | To 8.0.5 | To 8.0.6 | To 8.0.7 | To 8.0.8 | To 8.0.9 | To 8.0.10 | To 8.0.11 | To 8.0.12 | To 8.0.13 | To 8.1.0 | To 8.1.1 | To 8.1.2 |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Versions 6.0.0 - 7.0.11 | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.0 | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.1 | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.2 | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.3 | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.4 | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.5 | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.6 | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.7 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.8 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.9 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.10 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.11 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.12 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.13 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.1.0 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ |
+| 8.1.2 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ |
+
+#### Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 5. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json b/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
new file mode 100644
index 0000000..6715e84
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+  "title": "Puppet",
+  "ordinal": 379,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html",
+  "topic_cluster": {
+    "clustering_title": "Puppet",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md b/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
new file mode 100644
index 0000000..a0af7da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
@@ -0,0 +1,61 @@
+# Puppet
+
+Each HPE Morpheus Enterprise Puppet integration ties to a specific Puppet Master and makes it easy to install the Puppet Agent onto target Instances and Servers. Once integrated, we can trigger the agent installation by creating Puppet Agent Install Tasks through HPE Morpheus Enterprise automation or at provision time when spinning up instances in Clouds associated with a Puppet integration.
+
+## Add Puppet Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click + NEW INEGRATION
+3. Select Integration type “Puppet”
+4. Populate the following fields 
+
+   - Name: A friendly name for this Puppet integration in HPE Morpheus Enterprise
+   - Enabled: When marked, this Puppet integration will be available to users at provision time and when creating Tasks
+   - Puppet Master (Hostname): The resolvable DNS name to the Puppet Master, communicating on port 443 by default
+   - Allow Immediate Execution: Yes or No (See additional details below)
+5. Click SAVE CHANGES 
+
+   ![../../_images/new_puppet_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-89930173-D087-4C3D-AD78-83569C611401-high.png)
+
+### Allow Immediate Execution
+
+When adding or editing a Puppet integration, users have the option to “Allow Immediate Execution”. Using this feature will connect to the Puppet Master after the Puppet Agent is installed and force configuration application immediately. This is an optional convenience feature, if it’s not used, the Puppet Master will still apply configuration to the node on its own schedule. Using this feature requires supplying SSH credentials. If you do not wish to provide SSH credentials to HPE Morpheus Enterprise select “No” to opt out of this feature and they do not need to be provided.
+
+## Associating a Puppet Integration with a Cloud
+
+### About this task
+
+By associating a Puppet Integration with a Cloud, users are able to automatically install the Puppet Agent, select a Puppet environment, and supply a Puppet Node Name at provision time. The integration association is made when adding or editing a Cloud integration in HPE Morpheus Enterprise.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Identify the Cloud to associate with Puppet and edit it by clicking on the pencil icon at the right end of the row
+3. In the EDIT CLOUD modal, expand the Advanced Options section
+4. In the CONFIG MANAGEMENT dropdown, choose the Puppet integration
+5. Save changes to the Cloud integration
+
+## Creating Puppet Agent Install Tasks
+
+### About this task
+
+Puppet Agent Install Tasks automate the process of installing the Puppet Agent, selecting the Puppet environment, and supplying the Puppet Node Name. We can run this Task on-demand as needed for individual Instances or servers or add them to workflows to build a Puppet Agent installation step into larger automation suites.
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Select the Tasks tab
+3. Click + ADD
+4. From the “Type” field, select Puppet Agent Install
+5. Complete the fields as needed to target a specific Puppet Master and to identify Puppet environment and node names
+6. Save changes
+
+### Results
+
+![../../_images/puppet_task.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F59908B8-FAEC-4C47-859E-087396FDCB98-high.png)
+
+## Installing Puppet Agent at Provision Time
+
+With a Puppet integration associated with a Cloud (as described above), users can opt to install the Puppet Agent at provision time. When provisioning into an associated Cloud, a new “Puppet” section will appear on the CONFIGURE tab of the provisioning wizard. Here users can select a specific Puppet Master, select the Puppet environment, and select a Puppet node name. During provisioning, the Puppet Agent will be automatically installed and configured for the selected Master.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json b/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
new file mode 100644
index 0000000..fabb9db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+  "title": "Provisioning Concepts",
+  "ordinal": 81,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md b/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
new file mode 100644
index 0000000..70f85a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
@@ -0,0 +1,31 @@
+# Provisioning Concepts
+
+HPE Morpheus Enterprise is a powerful infrastructure-agnostic Cloud Application Management Platform. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+HPE Morpheus Enterprise refers to itself as a CAMP (Cloud Application Management Platform) as opposed to a (Cloud Management Platform). While that may seem minor, it actually is a big deal. Many CMP applications start at the IaaS layer and work up to the application layer (often needing additional PaaS architectures to fill out the model). HPE Morpheus Enterprise was designed from a middle-ground perspective. As such, some concepts are a bit different. This provides a more complete platform that allows for greater capabilities out of the box as will be seen when these concepts are covered.
+
+## Instances
+
+HPE Morpheus Enterprise starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in Amazon AWS. In HPE Morpheus Enterprise, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines or several Docker containers.
+
+For example, in the HPE Morpheus Enterprise Instance wizard, MongoDB is an option and contains several Instance configurations. One of these configurations is a full MongoDB cluster consisting of either seven virtual machines or seven Docker containers. Rather than representing these directly as seven individual “instances”, HPE Morpheus Enterprise groups them together into a singular Instance of a service that contains multiple containers or virtual machines within it. This even allows for Instance actions that can be performed to expand capacity on an Instance (either horizontally or vertically). In the past, a database server may have been representative of a singular server, but this model has drastically changed in a big data world. This same concept also can apply to something like a simple Apache web server where there are 10 copies of a web server which are horizontally scaled out to handle traffic.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. HPE Morpheus Enterprise simply helps simplify the management model for tracking these services.
+
+## Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, HPE Morpheus Enterprise will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance. Node is just a generic naming representation when referring to these types of items. The public HPE Morpheus Enterprise developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was since updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as Virtual Machines. In fact, one can even think of a Docker Host as a Hypervisor (which we do).
+
+## Hosts / Servers
+
+This concept is mostly tailored to users of HPE Morpheus Enterprise who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of HPE Morpheus Enterprise that is quite powerful. This singular concept is what allows HPE Morpheus Enterprise to ingest “brownfield” environments. We do not need to start clean. HPE Morpheus Enterprise can be integrated into existing environments and manage existing virtual machines. The way HPE Morpheus Enterprise does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of HPE Morpheus Enterprise and the HPE Morpheus Enterprise Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
+
+## Apps
+
+On top of all the previous concepts, HPE Morpheus Enterprise provides an Apps layer. An App is a collection of Instances linked together via application tiers. Tiers allow the user to define segregated sections of connectivity between the various elements (Instances) within an application. Once these Instances are all linked together in an application concept, this may affect Instance environments and provide service discovery capabilities for them to cross connect. There are several service discovery aspects within HPE Morpheus Enterprise as well as integrations with services.
+
+## App Blueprints
+
+An App Blueprint allows a user to define an application structure for easy reproducibility and deployment into various environments. They can be used to mix and match various Instance types to provision an application dependent on multiple layers of services.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json b/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
new file mode 100644
index 0000000..5d37100
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+  "title": "Credentials",
+  "ordinal": 237,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md b/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
new file mode 100644
index 0000000..b8615e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials can be securely stored internally on the appliance or stored in an external Cypher integration, more information about setting up and integrating with an external Cypher store are in the next section. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in HPE Morpheus Enterprise UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json b/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
new file mode 100644
index 0000000..bc78425
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+  "title": "Plans",
+  "ordinal": 289,
+  "parent_title": "Plans",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md b/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
new file mode 100644
index 0000000..4804def
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
@@ -0,0 +1,118 @@
+# Plans
+
+Plans types include Service Plans and Price Plans. Service Plans determine the memory, storage and cores configuration during provisioning and reconfigure.
+
+## Service Plans
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
+
+### Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in HPE Morpheus Enterprise
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. See [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
+
+### Create Service Plan
+
+#### About this task
+
+HPE Morpheus Enterprise offers a few distinct types of service plans, each with different data fields to track and valid Price Set types which can be associated. For more on Service Plan configuration, see the preceding section.
+
+Price Sets can be added to the Plan at creation time so often it makes sense to create the Prices and associate them with Price Sets before creating the Plan. Additional instructions for creating Prices and Price Sets are in the next section. With the Price Sets ready, continue with the instructions below to create Price Plans of various types.
+
+#### Procedure
+
+1. Navigate to Administration > Plans & Pricing (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. On the Price Sets tab, associate all relevant Price Sets with the Plan. The desired Price Sets must already exist. If needed, you may save the Plan at this point and come back to associate Price Sets later
+5. Click SAVE CHANGES
+
+### Add Price Set(s) to Plan
+
+#### Procedure
+
+1. Select a Price Unit to list available Price Sets which have the selected Price Unit. Available Price Sets are filtered to show only those which are relevant for the Plan type you’ve selected
+2. Select a Price Set from the list and click + ADD
+3. Add additional Price Sets if desired (multiple Price Sets can be associated with a Plan)
+4. Added Price sets can be removed from a Plan by clicking the 🗑 icon
+5. Once all Price Sets have been added, select SAVE CHANGES
+
+#### Results
+
+TIP
+
+The +ADD button must be clicked after selecting a Price Set or it will not be added to a Plan.
+
+### Service Plan Permissions
+
+Group and Tenant Access permissions determine availability of a Service Plan.
+
+- Group Access determines what Groups the Service Plan will be available in for Provisioning and Reconfigure.
+- Group Access settings only apply to the Tenant they are configured in, as Groups are not multi-tenant.
+- For multi-tenant environments, the Master Tenant can set Tenant Permissions to determine if the Service Plan is available to all Tenants (public visibility) or assign the Service Plan to one or multiple Tenants.
+
+### Removing Plans
+
+Plans can be removed by navigating to the Service Plans list page (Administration > Plans & Pricing > Plans), opening the ACTIONS menu for a Plan, and then selecting “Remove”. Removing a Plan makes it no longer visible, however, it does not hard delete the Plan as the record must remain for any existing associations’ usage and price tracking. Synced Plans should be deactivated rather than removed.
+
+## Load Balancer Price Plans
+
+Load Balancer Price Plans configure pricing for Load Balancers and Load Balancer Virtual Servers.
+
+Load Balancer Price Plan Configuration:
+
+- **NAME:** The name of the Load Balancer Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **LOAD BALANCER TYPE:** Select the load balancer type the Price Plan should be associated with
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Load Balancer Price Sets may be associated with Load Balancer-type and Load Balancer Virtual Server-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Virtual Image Price Plans
+
+Virtual Image Price Plans configure pricing for Virtual Images. Pricing is associated per Price and Price Set configurations, but in general applies to Images with location records in the Price Plans specified Cloud type. Virtual Image Price Plans are for setting pricing for Virtual Image storage, not for adding pricing to resources that use Virtual Images associated with Virtual Image Price Plans. Virtual Image Price Plans do not apply to uploaded Virtual Images that have not been copied to a location in the specified Cloud type yet.
+
+Virtual Image Price Plan Configuration:
+
+- **NAME:** The name of the Virtual Image Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Virtual Image Pricing applies to Virtual Images with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Virtual Image Price Sets may be associated with Storage-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Snapshot Price Plans
+
+Snapshot Price Plan Configuration:
+
+- **NAME:** The name of the Snapshot Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Snapshot Pricing applies to Snapshots with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Snapshot Price Sets must have at least one Storage-type Price but may also have Datastore-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json b/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
new file mode 100644
index 0000000..04448f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+  "title": "Navigation Updates",
+  "ordinal": 530,
+  "parent_title": "See Also",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html",
+  "topic_cluster": {
+    "clustering_title": "Navigation Updates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md b/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
new file mode 100644
index 0000000..cea3df9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
@@ -0,0 +1,38 @@
+# Navigation Updates
+
+[  ](https://www.youtube.com/embed/B46qgEwoblY)
+
+v8.0.7 contains major changes to the UI navigation structure. The following table lists updated paths for affected sections.
+
+NOTE
+
+API endpoints are not affected by the UI navigation changes
+
+Table 1.
+
+     | Target | Old Path | New Path |
+| --- | --- | --- |
+| Blueprints | provisioning > blueprints | library > blueprints |
+| Automation | provisioning > automation | library > automation |
+| Tasks | provisioning > automation > tasks | library > automation > tasks |
+| Workflows | provisioning > automation > workflows | library > automation > workflows |
+| Executions | provisioning > automation > executions | provisioning > executions |
+| Scale Thresholds | provisioning > automation > scale thresholds | library > automation > scale thresholds |
+| Power Scheduling | provisioning > automation > power scheduling | library > automation > power scheduling |
+| Execute Scheduling | provisioning > automation > execute scheduling | library > automation > execute scheduling |
+| Automation Integrations | provisioning > automation > integrations | library > integrations |
+| Security Packages | provisioning > jobs > security packages | library > templates > security packages |
+| Virtual Images | provisioning > virtualimages | library > virtualimages |
+| Library | provisioning > library | library |
+| Instance Types | provisioning > library > instance types | library > blueprints > instance types |
+| Layouts | provisioning > library > layouts | library > blueprints > layouts |
+| Node Types | provisioning > library > node types | library > blueprints > node types |
+| Option Types (Inputs) | provisioning > library > option types | library > options > inputs |
+| Option Lists | provisioning > library > option lists | library > options > option types |
+| File Templates | provisioning > library > file templates | library > templates > file templates |
+| Scripts | provisioning > library > scripts | library > templates > script templates |
+| Spec Templates | provisioning > library > spec templates | library > templates > spec templates |
+| Cluster Layouts | provisioning > library > cluster layouts | library > blueprints > cluster layouts |
+| Catalog/Self Service | tools > selfservice | library > blueprints > catalog items |
+| Service Catalog | service catalog persona | provisioning > catalog& service catalog persona |
+| Logs | logs | monitoring > logs |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json b/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
new file mode 100644
index 0000000..43de9d1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+  "title": "Getting started with HPE Morpheus Enterprise and VMware",
+  "ordinal": 362,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md b/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
new file mode 100644
index 0000000..2305222
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
@@ -0,0 +1,514 @@
+# Getting started with HPE Morpheus Enterprise and VMware
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of HPE Morpheus Enterprise with VMWare. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in HPE Morpheus Enterprise that is beyond the scope of this guide. For more, consult the complete HPE Morpheus Enterprise documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/4.1.0/getting_started/requirements/requirements.html#requirements). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a lab license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on HPE Morpheus Enterprise groups is [here](https://docs.morpheusdata.com/en/4.1.1/infrastructure/groups/groups.html#groups). A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![The new group dialog box showing a name for the group filled in](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with VMWare vCenter.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated vCenter cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “VMWARE VCENTER” and click the “NEXT” button.
+
+![The list of clouds available to integrate with, vCenter is selected](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-37B199A3-DCEC-41E4-AE0B-8BE8A37EA55B-high.png)
+
+On the “CONFIGURE” tab, we’re asked to set the initial connection strings into vSphere. The **API URL** should be in the following format: <https:/>/<URL>/sdk. The **USERNAME** should be in [user@domain](mailto:user%40domain) format.
+
+![The create cloud dialog box with relevant fields filled](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-670B6AE2-46C2-4917-A452-B8D72082823E-high.png)
+
+HPE Morpheus Enterprise allows vCenter clouds to be scoped to the **VDC** and **CLUSTER** or even the specific **RESOURCE POOL** if you choose. Once you’ve entered your URL and credentials, these dropdown menus will become populated.
+
+The **RPC MODE** setting determines how HPE Morpheus Enterprise will connect to VMs and make configuration and scripting calls if [Morpheus Agent](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent) is not installed. In a VMware environment, it is recommended to select **Vmware Tools** but WinRM/SSH are able to be used to configure the guest directly. If using WinRM, ensure it is configured on the virtual image, discusssed below.
+
+Additionally, we can opt to **INVENTORY EXISTING INSTANCES** to begin polling VMs for statistics and rightsizing recommendations as well as **ENABLE HYPERVISOR CONSOLE** to use native vSphere console with port 443 connectivity between HPE Morpheus Enterprise and ESXi hosts.
+
+To move on, expand the “Advanced Options” section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), and **AGENT INSTALL MODE**.
+
+![The advanced options section of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5564447E-D7BC-4DE8-832D-D63909A3B49E-high.png)
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+![The group tab of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-21078778-ABE2-4EC9-A236-0F982B727DDB-high.png)
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first VMware cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our VMware cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in vCenter. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise.
+
+![The list of synced resource pools in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5E044CF2-DC63-48CA-BFE5-FB99E8B3CA6B-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![The edit resource pools dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12509E33-3DEA-47DD-8838-3D4B76599043-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “RESOURCES” tab to the “DATA STORES” tab on our cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![The list of synced data stored in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9D16EAEE-4391-4B7B-B0FA-D46DB90A3E59-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific groups. This ensures that the members of each group are only able to consume the data stores they should have access to.
+
+![The edit data stores dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-14F14768-224B-4188-A052-48C37F755907-high.png)
+
+## Configuring Folders
+
+Still within the “RESOURCES” tab, within the “FOLDERS” subtab we see the folders discovered from the vCenter Cloud. Edit folder configurations by selecting “ACTIONS” from the end of the row, then clicking “Edit”. Consider the following configurations for specific folders:
+
+- **DEFAULT:** If selected, this folder will be pre-selected when provisioning new Instances to this Cloud (See the Folder option on the CONFIGURE tab of the Instance provisioning wizard)
+- **IMAGE TARGET:** HPE Morpheus Enterprise will look in the image target folder(s) to onboard VMware images
+
+After saving the changes, you’ll see any folders set as default or image target indicated in the folders list.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![The list of configured neworks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+![The add IPAM integration dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a HPE Morpheus Enterprise-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, HPE Morpheus Enterprise will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, HPE Morpheus Enterprise will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![Creating a |morpheus|-type IP pool](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within a VMware cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain groups or tenants.
+
+![Viewing networks on the cloud detail page](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D8873C52-F566-49ED-AE8C-825EA4B169B1-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, HPE Morpheus Enterprise comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with images included in HPE Morpheus Enterprise by default in this guide but it’s important to discuss how to prep custom images as well.
+
+### Creating a Windows Image
+
+The following versions of Windows Server are supported:
+
+- 2008 R2
+- 2012
+- 2012 R2
+- 2016
+- 2019
+- 2022
+
+To start, create a new Windows VM in vCenter using a base version of your selected Windows build.
+
+NOTE
+
+It’s recommended to make the VMDK drive as small as possible for your purposes as this generally speeds cloning and deploy times. Morpheus provisioning and post-deploy scripts allow to to expand the drive to any size that you need.
+
+Once the VM is created, ensure VMware Tools is installed on the operating system. This will ensure the virtual machine can communicate correctly with vCenter but also if the cloud was configured to use `RPC MODE` of `Vmware Tools`, and the HPE Morpheus Enterprise agent is not installed, HPE Morpheus Enterprise can communicate with the virtual machine directly for tasks and other processes.
+
+NOTE
+
+If the cloud was configured to use `RPC MODE` of `SSH/WinRM`, it will be necessary to configure WinRM on the virtual machine. Ensure WinRM is allowed from your Morpheus appliance through the local Windows firewall. Also, run the following command to enable WinRM in the guest: `winrm quickconfig`
+
+Next, install .NET 4.5.2 or higher as a [requirement](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/agentInstallation.html#agent-install-requirements) for the Morpheus agent.
+
+Finally, choose a method that will be used to customize the operating system:
+
+- Guest Customization
+- Sysprep
+- Cloudbase-Init
+
+#### Using Guest Customization (Recommended)
+
+HPE Morpheus Enterprise can utilize the vCenter guest customizations feature, creating its own customization specification and applying it at deployment. There are no other changes needed in the guest operating system when using this method. Turn off the virtual machine and convert it to a template Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **VMware Guest Customization?** is checked.
+
+#### Using Windows Sysprep
+
+HPE Morpheus Enterprise can inject an unattend file via CD-ROM to override the default sysprep process when preparing a virtual machine. Run the following command from the guest operating system to sysprep the operating system: `C:\Windows\System32\sysprep /oobe /generalize /shutdown` The unattend file created on the virtual machine can be ignored, no changes will be needed. Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Sysprepped/Generalized Image?** is checked.
+
+NOTE
+
+If **VMware Guest Customization?** is enabled on the virtual image or if using static IP addresses or IP pools when provisioning, ensure a Sysprep has not been performed in the guest. In such cases, a guest customization will always be performed.
+
+#### Using Cloudbase-init
+
+IMPORTANT
+
+Some admins may struggle with using Cloudbase-Init, especially if they are not familiar with cloud-init (used in Linux). It is recommended to use either **Guest Customization** or **Windows Sysprep** if the admins are more famililar with those tools.
+
+HPE Morpheus Enterprise can inject a cloud-init file via CD-ROM to override the default sysprep process when preparing a virtual machine, if the Cloudbase-Init service is installed. Download Cloudbase-Init from <https://cloudbase.it> for your appropriate architecture. Run the installer and keep the default settings. Below is an example of the final settings page: ![Cloudbase-Init settings](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ABBCBC9E-8CE1-4EE2-B15D-EC25F255D11A-high.png) At the end of the installer, options will be available to sysprep and shutdown the virtual machine. Checkmark both boxes and click **Finish**: ![Cloudbase-Init sysprep](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-14880EC6-E2C4-486D-AEA8-D66AE8573877-high.png) Once started, the sysprep process should continue until the virtual machine shutsdown. ![Cloudbase-Init progress](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A52DA0FA-2608-4AE6-B741-DC4B98D23778-high.png) Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Is Cloud Init Enabled?** is checked.
+
+### Creating a CentOS/RHEL Image
+
+Create a new machine in vCenter and install a base version of your preferred Linux distro.
+
+NOTE
+
+If you are using cloud-init as part of your image, you will need to ensure your virtual machine has a cdrom.
+
+Before installing the operating system, set up a single ext or xfs partition without a swap disk. Next, install the distro applying any updates to the operating system or security updates. Once the operating system is running and updated, install the following:
+
+```
+```
+yum install cloud-init  
+yum install cloud-utils-growpart  
+yum install open-vm-tools  
+yum install git  
+yum install epel-release
+```
+```
+
+Set selinux to permissive as the enforced setting can cause problems with cloud-init:
+
+```
+```
+sudo vi /etc/selinux/config
+```
+```
+
+#### Cloud-Init
+
+We’ll get started by installing cloud-init using the following command:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+NOTE
+
+The above command will install some core dependencies for cloud-init and automation later as you work with your provisioned instances. For example, we install Git here as it is used for Ansible automation. If you had no plans to use Ansible, this installation could be skipped. The dracut-modules-growroot is responsible for resizing the root partition upon initial boot which was potentially adjusted during provisioning.
+
+One key benefit of using cloud-init is that we don’t have to lock credentials into the blueprint. We recommend configuring a default cloud-init user that will get created automatically when the VM is booted by cloud-init. We can define that default user in Administration > Settings > Provisioning > Cloud-Init
+
+#### Network Interfaces
+
+As of CentOS 7, network interface naming conventions have changed. You can check this by running ifconfig and noting that the primary network interface has some value similar to “ens2344”. The naming is dynamic and typically set based on hardware ID. We don’t want this to fluctuate when provisioning this blueprint in our VMware environments. To accomplish this end, we will rename the interface back to “eth0” using the steps below.
+
+First, adjust the bootloader to disable interface naming:
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The next step is to adjust network scripts in CentOS. Start by confiming the presence of a file called /etc/sysconfig/network-scripts/ifcfg-eth0. Once confirmed, run the following script:
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to confirm there is a new ifcfg-eth0 config created to replace the old config file. Confirm this config exists after running and if not you will have to build your own:
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+For more on CentOS/RHEL image prep, including additional configurations for specific scenarios, take a look at the [VMware image prep](https://docs.morpheusdata.com/en/4.1.1/integration_guides/Clouds/vmware/vmware_templates.html#gotchas) page in HPE Morpheus Enterprise Docs.
+
+#### Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Disable assignment of new styled names for network interfaces (instead of `ens###` they will be `eth#`):
+
+```
+```
+sudo sed -i -e 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"/' /etc/default/grub
+```
+```
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our vCenter cloud.
+
+Navigate to Provisioning > Instances. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![Selecting an instance type to provision](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the vCenter cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [here](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in Administration > Plans & Pricing.
+- **VOLUMES and DATASTORES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click “NEXT”.
+
+![The configure tab of the create instance dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B494FF9C-4564-4F58-B523-3D6661254037-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click “COMPLETE”.
+
+![Confirming the instance to be provisioned](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BD9754FE-0F3F-45CD-BE37-86185EF667BF-high.png)
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends on your environment and selections made when provisioning the instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisiioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+![Monitoring privisioning progress on the instance detail page](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6CD6B5F1-88DE-44D1-9E25-29FB61D81345-high.png)
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click “+ADD”.
+
+![Adding a new node type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: VMware
+- **VM IMAGE**: HPE Morpheus Enterprise Redis 3.0 on Ubuntu 14.04.3 v2
+
+NOTE
+
+Within the “VMware VM Options” section you should add anything that will always be used for this node, regardless of the specific deployment details. This can include LDAP Authentication, bash scripts that should run on installation, among other things.
+
+![Configuring options for the new node](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0C9573F1-448E-41A1-B2CD-B8F3D6111B7B-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![Adding a new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![Configuring the new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![Opening our newly created instance type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: VMware
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+![Configuring the new layout](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-70C1E76A-8246-418B-956B-D8542254955E-high.png)
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to Provisioning > Instances and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+![Searching for our custom instance type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-905B43B4-EABB-4271-A555-97203C7A87E5-high.png)
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+![Configuring the newlt created instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8D733786-5795-4A40-A81F-F832B79E3B71-high.png)
+
+As before when we manually provisioned an instance, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on your environment but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the privisioning process has completed, open the instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+![Confirming creation of the new instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C9C8D9D2-E462-48F1-B679-A96B28ABAED3-high.png)
+
+## Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in the [Automation section](https://docs.morpheusdata.com/en/4.1.1/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![Adding a new automation integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![Configuring the new Ansible integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to Library > Automation, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![Configuring the new task](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to Provisioning > Instances and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![Executing the new task](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in Library > Automationwe will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![Creating a workflow for our task](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to Provisioning > Instances and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![Running the new workflow on provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+## Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume VMware. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/4.1.1/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json b/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
new file mode 100644
index 0000000..ef98fd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+  "title": "Blueprint Development Overview",
+  "ordinal": 127,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprint Development Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md b/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
new file mode 100644
index 0000000..f3b8dd1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
@@ -0,0 +1,5 @@
+# Blueprint Development Overview
+
+When provisioning, the User selects an INSTANCE TYPE from the provisioning wizard. At this stage, we can present custom INPUTS to the User which alter deployment in ways the administrator predetermines. Based on the selected Cloud technology and Version, the User is presented with applicable LAYOUTS selections. LAYOUTS can take advantage of Workflows which automate Tasks and can utilize a wide range of DevOps automation technologies. One or more NODE TYPES is associated with the LAYOUT. NODE TYPES are the bridge between LAYOUTS and Images. NODE TYPES can also take advantage of File Templates for custom configuration and Scripts which can be queued to run at any stage of the Instance lifecycle.
+
+![../../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json b/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
new file mode 100644
index 0000000..26616bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+  "title": "Labels",
+  "ordinal": 102,
+  "parent_title": "Library",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md b/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
new file mode 100644
index 0000000..cbf3d31
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
@@ -0,0 +1,45 @@
+# Labels
+
+Labels Video Demo
+
+Labels are a categorization feature designed to allow easier filtering of list views in the HPE Morpheus Enterprise Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Workflows
+- Jobs
+- Instance Types
+- Instances
+- Layouts
+- Node Types
+- Servers
+- Virtual Images
+- Inputs
+- Option Lists
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists anywhere in the current Tenant. When a label is removed from a construct and no other constructs also have that label, HPE Morpheus Enterprise will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+![../_images/labels.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EF84CC50-D2E4-4906-9051-655D7B15CE65-high.png)
+
+## Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
+
+## Running Automation Against Label Targets
+
+The HPE Morpheus Enterprise automation constructs Jobs, Tasks, and Workflows can be run against Instance Labels or Server Labels. When creating the Job or executing the Task or Workflow, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
+
+![../_images/executeLabel.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FC1AD46A-80E3-46F9-95D0-3D679C53E596-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json b/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
new file mode 100644
index 0000000..1866e87
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+  "title": "Remote Console",
+  "ordinal": 355,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Console",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md b/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
new file mode 100644
index 0000000..6e1dce8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
@@ -0,0 +1,204 @@
+# Remote Console
+
+HPE Morpheus Enterprise has a built in Remote Console for Instances, Hosts, Virtual Machines and Bare Metal. The following information reviews the Roles Settings, Protocols, and Requirements necessary to configure and troubleshoot Remote Console access.
+
+## Role Settings
+
+User Role settings determine if the Console tab or `Open Console` Action appear for a user, and if a login prompt is presented or the user is automatically logged in when using the Console.
+
+- Remote Console (None, Provisioned, Full)
+  :   None
+      :   The user will not have access to remote console.
+
+      Provisioned
+      :   The user will only have remote console access for Instances they provisioned.
+
+      Full
+      :   The user will have remote console access for all instances they have access to.
+- Remote Console: Auto Login (No, Yes)
+  :   No
+      :   A login prompt will be present in the console for Linux platforms, and the main login screen will present for Windows platforms.
+
+      Yes
+      :   HPE Morpheus Enterprise will automatically login to the remote console using the credentials defined on the VM or Host. For provisioned Instances, the credentials are defined either from the credentials defined on the Virtual Image used, added via cloud-init or VMware Tools using the global cloud-init settings (Administration - Provisioning) or the Linux or Windows settings defined in User Settings. For Instances created when converting a VM or Host to managed, the credentials are entered when converting to managed. These credentials can be changed by editing the underlying VM or Host of the Instance.
+
+NOTE
+
+If the credentials defined on the VM or Host are not valid, and the `Remote Console: Auto Login` Role setting is set to `Yes`, the console will not be able to connect and no console window or login prompt will be presented. The credentials on the underlying VM or Host must be edited or `Remote Console: Auto Login` Role setting can be set to `No` for a login prompt to present in the console. Credentials cannot be changed from an Instance view, only in the Infrastructure VM or Host view.
+
+## Protocols
+
+Platform Type and Cloud Settings determines the protocol and port used for Remote Console connections.
+
+- SSH
+  :   The SSH protocol will be used for Linux and OSX platform types, and 22 is the default port used.
+- RDP
+  :   The RDP (Remote Desktop) protocol will be used for Windows platform types over port 3389 by default.
+- VNC
+  :   The VNC protocol will be used for all platform types in Clouds with the `Hypervisor Console` option enabled in cloud settings. VNC connection are made directly to the Hypervisor Host over port 443.
+
+NOTE
+
+Alternative ports can be configured per VM or Host by editing the VM or Host and editing the Port field in the RPC host section.
+
+### SSH
+
+For all Linux and OSX platform types, HPE Morpheus Enterprise will use the SSH protocol via port 22 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will SSH using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for SSH Connectivity
+
+- SSH Enabled on the target VM or Host
+- Port 22 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+### RDP
+
+For all Windows platform types, HPE Morpheus Enterprise will use the RDP protocol via port 3389 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will RDP using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for RDP Connectivity
+
+- Remote Access enabled on the target VM or Host and Remote Desktop enabled in the Windows Firewall settings. If the VM or Host is on a different network than the HPE Morpheus Enterprise appliance, public access for Remote Desktop must be enabled in the Firewall settings.
+- Port 3389 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+NOTE
+
+If Remote Console: Auto Login is set to No in a users Role permissions, Allow connections only from computers running Remote Desktop with Network Level Authentication in the Windows System Properties  >  Remote settings must be DISABLED for Remote Console to connect.
+
+### VNC (VMware Hypervisor Console)
+
+When the `Hypervisor Console` option is enabled in cloud settings, the VNC protocol will be used for all platform types that Cloud.
+
+When using VNC Hypervisor Console, the HPE Morpheus Enterprise Appliance connects directly to the host the VM is on, not directly to the VM.
+
+HPE Morpheus Enterprise features Remote Console support directly to hypervisors. To enable this feature a few prerequisites must be met:
+
+- The HPE Morpheus Enterprise Appliance must have network access to the host the VM is on over 443.
+- The HPE Morpheus Enterprise Appliance must be able to resolve the hypervisor hostnames.
+
+NOTE
+
+VNC connections for VMs and Hosts in VMware type clouds are made directly to the ESXi hosts, not vCenter.
+
+Unlike SSH and RDP, valid credentials do not need to be set on the VM or Host records in HPE Morpheus Enterprise for VNC hypervisor console connections. An IP address is also not required on the VM or Host for VNC hypervisor console connections. HPE Morpheus Enterprise will be able to connect to the VM or Host as soon as the `Host (Hypervisor)` record is set, which can be viewed in the Info section on the VM or Host detail page.
+
+NOTE
+
+- Auto-login is not supported for Hypervisor Console. Auto-login role settings do not apply to console connecting when using Hypervisor Console. Please note Hypervisor Console sessions persist on the ESXi host and once a user manually logs in to the VM they will continue to be logged in, even if the console tab/window in HPE Morpheus Enterprise is closed, until they manually log out.
+- Copy and Paste and Text selection in Linux terminals is not supported when using VNC (VMware Hypervisor Console).
+- In HPE Morpheus Enterprise versions 3.2.0 and higher, a newer Guacamole version is installed that is not compatible with MacOS Platform Types over VNC.
+
+## Copy and Paste
+
+### About this task
+
+NOTE
+
+Copy and Paste for Text is supported for SSH and RDP protocols only. Use of this functionality requires the Role permission of “VDI: Copy/Paste” set to Full.
+
+To Copy text from the console:
+
+### Procedure
+
+1. Select text in the Console window.
+2. Click the COPY button at the top of the Console window.
+3. The selected text is copied to the users clipboard.
+
+### Results
+
+To Paste text into console:
+
+1. Copy text on the local computer to you clipboard
+2. Right click into the “Paste Text Here” field at the top of the Console window. The field will the display “Text Copied, Use Console to Paste.”
+3. Right click into the console window.
+4. The text is pasted into the VM.
+
+## Guacamole
+
+### Overview
+
+HPE Morpheus Enterprise uses Apache Guacamole, a clientless remote console. Guacamole is installed on the HPE Morpheus Enterprise Appliance during the initial reconfigure. In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+The Guacamole proxy daemon, guacd, is used for all Remote Console connections and must be running for Remote Console functionality.
+
+### Troubleshooting guacd
+
+#### About this task
+
+If all console connections are not functioning, the Guacamole proxy daemon (guacd) process may not be running or have a stuck process preventing console connections. This is evident when only the header appears in the console tab/window, and no console window appears below the header and no connection status is show in the console header. The following commands can be used on the HPE Morpheus Enterprise Appliance to restore console functionality.
+
+`morpheus-ctl status`
+:   Lists all local HPE Morpheus Enterprise services including guacd and their states. If guacd is stopped, it will need to be started again for Remote Console to function.
+
+`morpheus-ctl start guacd`
+:   Starts the guacd process
+
+`morpheus-ctl stop guacd`
+:   Stops the guacd process
+
+`morpheus-ctl kill guacd`
+:   Forcefully kills the guacd process
+
+`morpheus-ctl restarts guacd`
+:   Restarts the guacd process
+
+`morpheus-ctl tail guacd`
+:   Tails the guacd current and state logs, located by default at `/var/log/morpheus/guacd/`. This log is useful when troubleshooting console connections, guacamole service status, and to determine the protocol being used for the Remote Console connection.
+
+If guacd continues to stop even after being started, or if guacd is running and no properly configured console connections are functioning, there may be a stuck guacd or multiple guacd processes running, which will need to killed and guacd started again.
+
+To kill all guacd processes on the HPE Morpheus Enterprise Appliance and start guacd again:
+
+#### Procedure
+
+1. Kill the morpheus gaucd proccess: `morpheus-ctl kill guacd`
+2. Grep for all running guacd processes: `sudo ps -aux | grep guacd` and note the guacd pid(s) (minus the process from the grep)
+3. Kill all running guacd processes: `kill -9 pid` replacing pid with the pid(s) of the target processes
+4. Start guacd again: `morpheus-ctl start guacd`
+5. Tail the guacd logs to verify guacd is started and listening: `morpheus-ctl tail guacd` The log output will resemble below when guacd is properly running: 
+
+   ```
+   ```
+   guacd[16899]: INFO:       Guacamole proxy daemon (guacd) version 0.9.14 started  
+   guacd[16899]: INFO:       Listening on host 127.0.0.1, port 4822
+   ```
+   ```
+6. Additional information in the guacd logs appears when HPE Morpheus Enterprise is making a console connection. A successful conneciton will resemble: 
+
+   ```
+   ```
+   guacd[24725]: INFO: Creating new client for protocol "ssh"  
+   guacd[24725]: INFO: Connection ID is "$24f67856-f050-4a17-83eb-9101g0cd8869"  
+   guacd[24743]: INFO: Current locale does not use UTF-8. Some characters may not render correctly.  
+   guacd[24743]: INFO: User "@63102f19-eff4-412e-b1f9-718405f55782" joined connection "$24f67856-f050-4a17-83eb-9101g0cd8869" (1 users now present)  
+   guacd[24743]: INFO: Auth key successfully imported.  
+   guacd[24743]: INFO: SSH connection successful.
+   ```
+   ```
+
+### Guacamole Version
+
+#### About this task
+
+In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole version 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+Note Guacamole version 0.9.14 is not compatible with MacOS Platform Types over VNC on ESXi v6.0 or prior (6.5 is supported). If necessary, the guacamole version can be reverted to 0.9.9.
+
+To revert the guacamole version from 0.9.14 to 0.9.9.
+
+#### Procedure
+
+1. Kill guacd - `morpheus-ctl kill guacd`
+2. Check if any guacd processes are still running `ps -aux | grep guac`
+3. If so, kill the processes `kill -9 pid` with id being the actual process id, like 16101.
+4. Go to the guac 0.9.9 directory: `cd /var/opt/morpheus/guacamole-server-0.9.9`
+5. Run: `make install`
+6. Start guacd: `morpheus-ctl start guacd`
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json b/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
new file mode 100644
index 0000000..582e12b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+  "title": "Setting an Optional Landing URL",
+  "ordinal": 307,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html",
+  "topic_cluster": {
+    "clustering_title": "Setting an Optional Landing URL",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md b/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
new file mode 100644
index 0000000..66ef113
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
@@ -0,0 +1,5 @@
+# Setting an Optional Landing URL
+
+On login, by default, Users will land on the Dashboard page (Operations > Dashboard). However, User and Tenant Roles may have custom landing URLs set. Setting a custom landing URL on the Tenant Role will apply globally to all Users within the Tenant. Landing URLs set on the User Role will supersede the landing URL set on the Tenant Role (if any). No Tenant Role is applied to the Master Tenant so the custom landing URL can only be set on the User Role for these Users.
+
+To set a custom landing URL, create or edit a Role. Set the custom landing URL in the “LANDING URL” field. For example, set `/provisioning/instances` and the Users having that Role will land on the Instances list page each time they log in. Other paths may be used depending on the desired landing page.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json b/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
new file mode 100644
index 0000000..3b39382
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+  "title": "Storage Management",
+  "ordinal": 437,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md b/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
new file mode 100644
index 0000000..87dce27
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
@@ -0,0 +1,14 @@
+# Storage Management
+
+There are two types of storage that are available for an instance to consume. One is the local storage available on the compute server used to create an instance. The other is the remote storage (SAN), using the Alletra MP storage array.
+
+At present, there is no support for the management of the local storage through HPE Morpheus. They are used to install the OS image, and any storage available beyond that is up to the user to configure and use. They cannot be managed from HPE Morpheus.
+
+The remote storage is fully manageable. The user can create/update/delete volumes and manage their attachment to compute servers.
+
+**Subtopics**  
+
+- **[Boot Volume Selection During Instance Creation for Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html)**
+- **[Volume Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html)**
+- **[Volume Consumption](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json b/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
new file mode 100644
index 0000000..7564c5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+  "title": "Xen Server",
+  "ordinal": 477,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.html",
+  "topic_cluster": {
+    "clustering_title": "Xen Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md b/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
new file mode 100644
index 0000000..af4f227
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
@@ -0,0 +1,152 @@
+# Xen Server
+
+## Add a Xen Server Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select Xen, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   IP or URL of Xen Host. ex: xenserver.domain.com
+
+   CUSTOM PORT
+   :   Port for non standard xen server clouds
+
+   USERNAME
+   :   Xen Host Username
+
+   PASSWORD
+   :   Xen Host Password
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json b/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
new file mode 100644
index 0000000..861e19e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+  "title": "Provisioning the Cluster",
+  "ordinal": 181,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md b/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
new file mode 100644
index 0000000..76b8318
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
@@ -0,0 +1,27 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, this example is starting with three provisioned Ubuntu 22.04 boxes. I also have a HPE Morpheus Enterprise-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+![../../_images/createHpevmCluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F721FD37-B1E8-48D5-A817-E9A23048CACD-high.png)
+
+HPE Morpheus Enterprise gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in HPE Morpheus Enterprise, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+![../../_images/createClusterTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-15EB662D-9111-4C88-826F-235318761007-high.png)
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. When Ceph initializes, it needs to be pointed to an initial data device. Configure this in the **DATA DEVICE** field. At this time, only one device may be given but in the near future, an update will allow for multiple devices to be configured which would be added to the total Ceph storage as one large volume. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-model` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY**configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+Click NEXT to move to the Review tab for final review, and COMPLETE to kick off cluster provisioning.
+
+![../../_images/createClusterBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus Enterprise will run scripts to install KVM, install Ceph, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json b/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
new file mode 100644
index 0000000..9accc24
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+  "title": "Terraform",
+  "ordinal": 380,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md b/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
new file mode 100644
index 0000000..d72c9e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
@@ -0,0 +1,499 @@
+# Terraform
+
+## Requirements
+
+### Role Access
+
+- In order to see the Terraform App Blueprint type option and create Terraform App Blueprints in Library > Blueprints > App Blueprints, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+- In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+- Existing Terraform Blueprints must be added before they can be provisioned from Provisioning > Apps.
+- In order to provision Terraform Apps, the user must have Role permissions for Provisioning: Apps set to Full.
+
+### Github/Git Repo
+
+- To use .tf files from a Git repo, a Git or Github integration needs to be configured in Administration > Integrations. If one is not configured, .tf or .tf.json files can be manually drafted in HPE Morpheus Enterprise and added to Terraform App Blueprints but they could not be sourced from version control repositories.
+
+### Supported App Provisioning Targets
+
+- VMware
+- Amazon AWS
+- Microsoft Azure
+- Google Cloud Platform (GCP)
+- Oracle Cloud
+
+NOTE
+
+Additional clouds are planned for later releases.
+
+## Terraform Installation
+
+The first time you attempt to provision a Terraform App, you may come across an error indicating that Terraform is not installed:
+
+```
+```
+bash: line 1: terraform: command not found
+```
+```
+
+### Command Not Found Error Screenshot
+
+![../../_images/1commandNotFound.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-544D6493-88F5-42A8-A371-34CBF5087BB9-high.png)
+
+This likely means you’ve not yet configured Terraform Settings within HPE Morpheus Enterprise global settings. Navigate to Administration > Settings > Provisioning and scroll down to the Terraform Settings section. By default, the Terraform Runtime field is set to “Manual”. When set this way, HPE Morpheus Enterprise will attempt to use Terraform as installed on the appliance box and it may not be currently installed. To have HPE Morpheus Enterprise manage the Terraform installation process for you and manage Terraform versioning on a per-App basis, set the Terraform Runtime to “Auto”. You should also set the Default Terraform Version field as well. When a version is set on a Terraform Spec Template or Terraform App Blueprint, that version will supersede the default version indicated in global settings.
+
+### Configured Terraform Runtime Screenshot
+
+![../../_images/2configuredTfRuntime.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1F6CCDC8-4ED4-49DD-ABF3-DE0929CF7011-high.png)
+
+IMPORTANT
+
+HPE Morpheus Enterprise appliances which do not have access to the Internet will need to leave Terraform Runtime settings on “Manual” and ensure Terraform is installed appropriately on the appliance. Install Terraform in the /usr/sbin/terraform directory and make sure it’s owned by the morpheus-local user.
+
+## Creating Terraform App Blueprints
+
+### About this task
+
+In order to provision Terraform apps, Terraform App Blueprints must be created first.
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Name the Blueprint and select Terraform type. 
+
+   NOTE
+
+   In order to see the Terraform Blueprint type option, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+4. Select NEXT
+5. Configure the following: 
+
+   NAME
+   :   Friendly name for the App Blueprint in HPE Morpheus Enterprise
+
+   DESCRIPTION
+   :   Description for your App Blueprint shown in the Apps list (optional)
+
+   CATEGORY
+   :   A category for your App (optional)
+
+   IMAGE
+   :   Add reference icon for your App Blueprint to make it more identifiable at provision time (optional)
+
+   CONFIG TYPE (select Terraform Specs, Terraform (.tf), Terraform.json, or Git Repository)
+
+   Terraform (.tf)
+
+   CONFIG
+   :   Draft or paste in .tf content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform (.tf.json)
+
+   CONFIG
+   :   Draft or paste in .tf.json content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform Specs
+
+   SPEC TEMPLATE
+   :   Using the typeahead field, select all Terraform-type Spec Templates which make up your App. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+
+   Git Repository
+
+   SCM INTEGRATION
+   :   Select a Github or Git integration that has been added in Administration > Integrations and which contains relevant .tf files. Integrations must be pre-existing prior to creating the App Blueprint.
+
+   Repository
+   :   Select a repository which contains relevant .tf files from the Github or Git integration selected in the prior step.
+
+   BRANCH OR TAG
+   :   Select the Git branch containing the desired version of .tf files for the App. “master” is chosen by default if no value is entered.
+
+   WORKING PATH
+   :   Enter the repo path for the .tf file(s). `./` is default if no value is entered.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+6. Select COMPLETE
+
+### Results
+
+HPE Morpheus Enterprise will scan the blueprint to check for validity and will surface any errors which need correcting before the App Blueprint can be saved. Your Terraform App is ready to be provisioned from Provisioning > Apps.
+
+## Cloud Profiles
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+## Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+### Create a Terraform Profile
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+#### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+## Provisioning Terraform Apps
+
+### About this task
+
+NOTE
+
+Terraform App Blueprints must be added to Library > Blueprints > App Blueprints before they can be provisioned. At least one Terraform App Blueprint must exist before Terraform Apps can be provisioned from Provisioning > Apps.
+
+NOTE
+
+In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select + ADD
+3. Choose an existing Terraform App Blueprint
+4. Select NEXT
+5. Enter a NAME for the App and select the Group, Default Cloud and Environment (optional)
+6. Select NEXT
+7. Configure the following sections: 
+
+   App Settings
+
+   BACKEND TYPE
+   :   Internal is the default selection and the most secure choice. This sends the Terraform state back to the appliance via HTTP loopback to be stored in the appliance database. Users may also select Local which will write Terraform state to the local filesystem first before being stored in the database and removed from the local filesystem. If unsure, use the default Internal value. Backend Type selection is currently only available for Terraform Apps. Selecting Backend Type for Terraform Instance Types is a planned future feature addition.
+
+   VALIDATE PLAN
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not perform its typical validation to ensure the Terraform spec is valid. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   RUN APPLY
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not apply the plan at completion of the App wizard. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   Terraform Variables Populate any required or optional variables here. Variables whose values are stored in an associated tfvars file sourced from HPE Morpheus Enterprise Cypher are masked from the user. Variables stored in any Terraform Cloud Profile associated with the selected Cloud also are automatically masked. Other variables will be presented in the Terraform Variables section for user entry and any configured default values on the Terraform spec will be pre-loaded. Advanced Options
+
+   REFRESH MODE
+   :   Set an interval at which HPE Morpheus Enterprise should automatically check the App for drift from the Terraform spec. If set to Manual, HPE Morpheus Enterprise will never perform automatic checks and the user must do so when desired. The results of drift checks are reported on the App detail page and users may apply the plan at any time to bring the App back into alignment with the Terraform spec.
+
+   INITIAL STATE
+   :   Paste in existing Terraform state to onboard an existing Terraform App for HPE Morpheus Enterprise management. Though the field is small, it will accept large, multiline Terraform state. When creating an App from existing state, users may want to skip plan validation or may not want to apply right away. Opt out of these functions by unmarking the corresponding box in the App Settings section.
+
+   NOTE
+
+   Terraform state import is a new feature. At this time, some state file components may break the import process. This feature is being iterated on rapidly to increase coverage to as many application types and conditions as possible.
+
+   Terraform Preview Review the Terraform App components here, including any providers invoked, variables surfaced from the App spec, resources to be created, and .tf files utilized. There is no user input to be entered into this section.
+8. Select NEXT
+9. HPE Morpheus Enterprise will now validate the App (unless the user has opted out of this check) and surface any errors which would cause provisioning issues. If all is well, click COMPLETE
+
+### Results
+
+TIP
+
+Review the App in the Terraform Preview section. If any config data needs to be edited, select the RAW tab, edit the config, and then select the BUILDER tab once again. The config changes from the RAW edit will be updated in the preview section for further review. Permanent edits can be made by editing the App Blueprint, pushing .tf changes to your code repository, or Terraform Spec Templates (depending on how the .tf files are sourced for your App Blueprint).
+
+The Terraform App will begin to provision.
+
+Once provisioning is completed, note the State tab in the App details page (Provisioning > Apps > select the App). This tab contains subsections related to state management which is discussed in greater detail in the next section.
+
+## Terraform App State Management
+
+State management is handled from the State Tab of the Terraform App detail page (Provisioning > Apps > selected App). With the tab selected, the Terraform command field will be present regardless of the selected subsection. Use this field to send Terraform commands to your apps just like using Terraform from the command line. Press return on the keyboard or click on the “play” button to the right of the text field to execute the commmand.
+
+TIP
+
+“terraform” is automatically entered for each command as printed along the left edge of the text field. Thus, you don’t need to enter “terraform” with each command sent. Entering “state” or “plan” is equal to entering “terraform state” or “terraform plan” from the command line.
+
+![../../_images/appDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5AB2D1E8-EFB9-43FA-82CE-0229BA99CD63-high.png)
+
+When Terraform commands are executed against the application, HPE Morpheus Enterprise provides progress bars and command output in the UI. Command output is shown underneath the Terraform command field. Users can dismiss individual output windows by clicking the “x” button in the upper-right of each window. All command output can be dismissed by clicking the blue “x” button to the right of the command field itself.
+
+Within the ACTIONS reside four selections: Refresh State, Apply State, Edit Inputs, and Edit STATE. Selecting Refresh State is equivalent to using the “terraform plan” command from the command line. This will read the existing state of any existing objects which are part of the App and compare their current configuration against the prior state. Any differences will be noted in the output. If differences are discovered, the App is considered to be in a “drift” state. This drift status is shown in the UI when the user is viewing the “State” subsection (which is described in greater detail in the next section). The output of the Refresh State command, including detailed information about changes Terraform would make to App objects to in order to realign them with the App spec are shown in the UI.
+
+![../../_images/planOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E81EA071-D055-4481-B6FF-CE9642A07B68-high.png)
+
+The Apply State selection brings up a modal which allows the user to view the App spec once again. This includes being able to view and edit Terraform variables if needed. After making any needed edits, click NEXT and HPE Morpheus Enterprise will validate the App once again, just like it did at provision time. On the next tab of the wizard, HPE Morpheus Enterprise will show the user and planned changes that would be executed if the user completes the modal. An output will be shown as if “terraform plan” were run from the command line. Make note of any App objects which would be created, altered, or destroyed if the actions are accepted as HPE Morpheus Enterprise would immediately take them if desired. When ready, click COMPLETE. This will execute all planned changes as if the user had run “terraform apply -auto-approve” from a terminal session.
+
+Edit Inputs allows for editing of Input values without going through the process of applying state. Edit State displays the state in a large text area for direct editing.
+
+### State Subsection
+
+The State Subsection shows the current drift state of the App. This includes when HPE Morpheus Enterprise has last checked for drift and whether the App is currently in a “Drift” or “No Drift” state. If the App is currently in a Drift state, users can select Refresh State from the ACTIONS menu to identify which objects and attributes have deviated from the App configuration.
+
+![../../_images/stateSubsection.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6BEDAC1D-B4E0-4E17-83F3-7A3AD9036241-high.png)
+
+### Specs Subsection
+
+The Specs Subsection will show the user all HPE Morpheus Enterprise Spec Templates (Library > Templates > Spec Templates) which make up the App. Users may even edit Spec Template config directly from this view by clicking the Edit (pencil) icon to the right of each Spec Template listed.
+
+TIP
+
+Editing a Spec Template here will detach it from the source object, essentially making it a brand new object that exists only here. All future updates to that Spec Template would have to be made here going forward. In most cases, it’s advisable to edit the Spec Template directly at the source. For example, if this Spec Template were sourced from an integrated version control repository (ex. Github), it’s likely the best option to make a new commit into your repository and then let Terraform handle the process of bringing your App in line with the new specifications.
+
+![../../_images/editSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4FB5CB67-B878-424C-BA28-531EEB556CB0-high.png)
+
+### Plan Subsection
+
+This section displays the output of the most recent “terraform plan” run against your App. This will either indicate that your infrastructure (App) matches the configuration or it will indicate that a drift of some sort has taken place.
+
+### Input Subsection
+
+This section lists all Terraform inputs, such as variables, which are relevant to the App. Variable values are shown unless they are flagged as sensitive in your configuration. All variables sourced from a HPE Morpheus Enterprise Cypher tfvars mount will automatically be masked.
+
+### Output Subsection
+
+This section lists all configured Terraform output.
+
+## Terraform Instance Type Example
+
+Terraform Spec can also be used within the HPE Morpheus Enterprise Instance Type construct in addition to App Blueprints and Apps. Expand the section below to see a complete end-to-end example of a Terraform Instance Type from drafting new Spec Templates through to provisioning.
+
+### Terraform Instance Type Example
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+**AWS Subnet by Count**
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+**AWS Terraform Default Vars**
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+**AWS Provider Role Assume**
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+**AWS Terrform Locals**
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+**AWS VPC**
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json b/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
new file mode 100644
index 0000000..8c5f149
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+  "title": "File Shares",
+  "ordinal": 232,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md b/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
new file mode 100644
index 0000000..60fc81c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
@@ -0,0 +1,495 @@
+# File Shares
+
+File Shares are for Backup, Archives, Deployment and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
+
+## Supported File Share Types
+
+- Azure
+- CIFS (Samba Windows File Sharing)
+- Dell EMC ECS Share
+- Dell EMC Isilon Share
+- Local Storage
+- NFSv3
+
+## Azure File Shares
+
+### About this task
+
+To Add an Azure File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name for the file share in HPE Morpheus Enterprise.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the file share
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name or, to add a new Share, enter a new name and mark the Create Bucket box below
+
+   CREATE BUCKET
+   :   Mark if the share entered in SHARE NAME does not exist and needs to be created
+
+   DEFAULT BACKUP TARGET
+   :   Sets this file share as the default backup target when creating Backups. If selected, the option to UPDATE EXISTING BACKUPS will appear. Mark to update existing backups to this file share
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this file share as the default storage target when creating deployment archives
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this file share as the default storage target when uploading Virtual Images from the Virtual Images section or when importing Images from Instance Actions
+
+   RETENTION POLICY
+   :   None
+       :   Files in the share will not be automatically deleted or backed up
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the file share
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup target
+
+               BACKUP BUCKET
+               :   Search for and then select the desired backup bucket
+
+       DELETE OLD FILES
+       :   This option will delete files from this share after a set amount of days
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the share
+6. Select SAVE CHANGES
+
+### Results
+
+The file share will be created and displayed in the file shares tab.
+
+- To browse, upload, download, or delete files from this file share, select the name of the share from the File Shares tab.
+- To edit the file share, select the edit icon or select the name of the share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Re-pointing a file share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a file share, select the trash icon or select the name of the file share and click DELETE.
+
+  WARNING
+
+  When deleting a file share, all Deployment versions and Backups associated with the file share will be deleted.
+
+## CIFS File Shares
+
+### About this task
+
+To Add a CIFS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC Isilon File Shares
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Local Storage File Shares
+
+### About this task
+
+IMPORTANT
+
+Local Storage refers to local to the HPE Morpheus Enterprise Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app.morpheus-app /path` on the HPE Morpheus Enterprise Appliance.
+
+NOTE
+
+HPE Morpheus Enterprise will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## NFSv3 File Shares
+
+### About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save HPE Morpheus Enterprise will create a persistent mount owned by `morpheus-app.morpheus-app` on the HPE Morpheus Enterprise Appliance for the NFSv3 File Share. The HPE Morpheus Enterprise appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before HPE Morpheus Enterprise is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
new file mode 100644
index 0000000..1c6eb46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+  "title": "Full HA Upgrade",
+  "ordinal": 24,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html",
+  "topic_cluster": {
+    "clustering_title": "Full HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
new file mode 100644
index 0000000..4458eed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
@@ -0,0 +1,301 @@
+# Full HA Upgrade
+
+Full HA configurations represent multiple app nodes with external (non-system) MySQL, RabbitMQ and Opensearch Clusters or Services.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Overview
+
+When upgrading to v8.1.1 only services local to the Morpheus App node(s) will be upgraded. For fully distributed configurations (Full HA) where MySQL, RabbitMQ and Opensearch are external, the upgrade process will not upgrade these services.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for externalized MySQL, Elasticsearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+### Full HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.1.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Elasticsearch and RabbitMQ services are external to the App nodes. The following steps assume 3 app nodes, adjust accordingly.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### Full HA Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch the UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui  
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with ``morpheus-ctl tail morpheus-ui``.
+   ```
+   ```
+4. Once App Node 2 upgrade has completed and the UI is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`.
+2. Download the upgrade package from My HPE Software Center and transfer to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. Once App Node 2 upgrade has completed and the ui is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### Full HA RPM Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.1.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Opensearch and RabbitMQ services are external to the App nodes.
+
+#### Full HA Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.1. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.1 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.1 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+2. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 2 upgrade has completed and the UI is available, upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json b/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
new file mode 100644
index 0000000..2888385
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+  "title": "Analytics",
+  "ordinal": 56,
+  "parent_title": "Operations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html",
+  "topic_cluster": {
+    "clustering_title": "Analytics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md b/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
new file mode 100644
index 0000000..12f80cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
@@ -0,0 +1,18 @@
+# Analytics
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html)**
+- **[Costing: Cloud Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html)**
+- **[Costing: Group Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html)**
+- **[Costing: Tenant Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html)**
+- **[Costing: User Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html)**
+- **[Costing: Workload Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html)**
+- **[Costing: Budget Analysis](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html)**
+- **[Costing: Tag Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html)**
+- **[Utilization: Utilization vs Cost](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html)**
+- **[Capacity: Capacity Planning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html)**
+- **[Workloads: Instance Type Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html)**
+- **[Workloads: Instance Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html)**
+- **[Workloads: Blueprint Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html)**
+- **[Workloads: Apps Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json b/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
new file mode 100644
index 0000000..2f81cbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+  "title": "Monitoring Groups",
+  "ordinal": 259,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md b/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
new file mode 100644
index 0000000..1ccf715
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
@@ -0,0 +1,22 @@
+# Monitoring Groups
+
+Group monitors can only contain checks and can be edited or created in Monitoring  >  Groups. Besides simply adding and removing checks to a group there are a few other useful options that can be customized in a group:
+
+Name
+:   A friendly name for the group monitor in HPE Morpheus Enterprise
+
+Min Checks
+:   This specifies the minimum number of checks within the group that must be happy to keep the group from becoming unhealthy
+
+Max Severity
+:   The maximum severity incident a failed check may create. This setting overrides a check’s max severity setting
+
+Affects Availability
+:   If checked, a failing group monitor impacts system-wide availability calculations
+
+Checks
+:   Use the typeahead field to select pre-existing checks for the group monitor. If check(s) need to be created, this can be done in Monitoring > Checks
+
+NOTE
+
+Some useful information can also be seen on the detail page of a check. For example, the average response time of all checks within the group, or an aggregated check history can be viewed.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json b/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
new file mode 100644
index 0000000..d836307
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+  "title": "Overview",
+  "ordinal": 126,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md b/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
new file mode 100644
index 0000000..39712ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
@@ -0,0 +1,18 @@
+# Overview
+
+The Blueprints section is used to compose provisioning catalogs. The Blueprints section is composed of:
+
+- Instance Types
+- Layouts
+- Node Types
+- App Blueprints
+- Catalog Items
+- Cluster Layouts
+
+Additionally, items from Options and Templates sections are incorporated to call in custom options for users, IaaS spec files, scripts, and more. See Options and Templates within HPE Morpheus Enterprise Library for more information on creating or sourcing the items below from version control. In some cases, they may need to be pre-existing for the most efficient creation of Blueprints.
+
+- Inputs
+- Option Lists
+- File Templates
+- Scripts
+- Spec Templates
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json b/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
new file mode 100644
index 0000000..4658fd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+  "title": "Add Load Balancer during Provisioning",
+  "ordinal": 498,
+  "parent_title": "Add Load Balancer to Instance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md b/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
new file mode 100644
index 0000000..5471a5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
@@ -0,0 +1,55 @@
+# Add Load Balancer during Provisioning
+
+## About this task
+
+In the Instance Provisioning wizard, Load Balancers can be configured in the Automation > LoadBalancer section.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select + ADD.
+3. Select an Instance Type that supports scaling. (ENABLE SCALING (HORIZONTAL) flagged on Instance Type configuration)
+4. Proceed with Instance configuration to the Automation section.
+5. Fill in the following: 
+
+   VIP ADDRESS
+   :   Define IP Address for the Virtual Server
+       :   - Example: 10.30.23.191
+
+   VIP PORT
+   :   Define port for the Virtual Server
+       :   - Example: 80
+
+   VIP HOSTNAME
+   :   Define hostname that will resolve to the VIP IP.
+       :   - Example: jwDemoHaApp59.den.example.com
+
+   VIRTUAL SERVICE NAME
+   :   Define name for the Virtual Service. Defaults to `${instance.name}`
+
+   BALANCE MODE
+   :   Specify balance mode for the VIP
+       :   - Least Connections
+           - Round Robin
+
+   STICKY MODE
+   :   Specify sticky session options for the VIP
+       :   - Source IP
+           - Cookie
+
+   SHARED VIP ADDRESS
+   :   Select if VIP is shared, then enter DIRECT VIP ADDRESS
+
+   SSL CERT
+   :   SSL Certificate that will be applied to the VIP.
+       :   - No SSL
+           - Select existing Certificate from Infrastructure  >  Keys & Certs or from a Trust Provider Integration.
+
+       USE EXTERNAL ADDRESS FOR BACKEND NODES
+       :   - Select if traffic from LB to Backend Nodes needs to be sent to the External Addresses, or leave deselected to use Internal Addresses for Backed Nodes.
+6. Optionally configure auto-scaling configuration in the `Scale` section
+7. Select NEXT and provision the Instance.
+
+## Results
+
+After all nodes in the Instance are provisioned, the LB configuration will be added to the Instance and Virtual Servers, Services and Servers will be created and configured on the NetScaler. The Load Balancer settings and status will be visible in the Instance details page LOAD BALANCER section, with additional details, links, and configurations options available in the `SCALE` tab.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json b/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
new file mode 100644
index 0000000..80abe65
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+  "title": "Image Prep (Windows)",
+  "ordinal": 192,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md b/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
new file mode 100644
index 0000000..6a00d18
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
@@ -0,0 +1,102 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and HPE Morpheus Enterprise Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in HPE Morpheus Enterprise that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in HPE Morpheus Enterprise. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in HPE Morpheus Enterprise, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to HPE Morpheus Enterprise. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+![../../_images/provisionMvmInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9DE2A41A-C675-4E94-819C-7DB350F6B8DA-high.png)
+
+On the GROUP tab, select the Group and Cloud containing the target HVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+![../../_images/groupTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5C1016FB-39ED-4A2E-9D73-3CE2F1C29456-high.png)
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+![../../_images/configTabTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8B62B5BD-FAF8-40F3-84C6-E905D7E4E72F-high.png)
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, HPE Morpheus Enterprise will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the HPE Morpheus Enterprise appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in HPE Morpheus Enterprise. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+![../../_images/importImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FBFB8AA8-171F-4668-BD6A-CAE4F5870AA8-high.png)
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to HPE Morpheus Enterprise API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in HPE Morpheus Enterprise. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. HPE Morpheus Enterprise library items can now be created from this image by adding new Node Types, Layouts, and Instance Types. The complete steps for building a library item go beyond the scope of this particular guide but more detail on that process is available elsewhere in HPE Morpheus Enterprise UI documentation. Once the library items are created, new Instances may be provisioned complete with HPE Morpheus Enterprise Agent installed.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json b/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
new file mode 100644
index 0000000..b5b2654
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+  "title": "Configuring Access with Clouds, Groups, and Roles",
+  "ordinal": 372,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Access with Clouds, Groups, and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md b/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
new file mode 100644
index 0000000..5012a05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
@@ -0,0 +1,55 @@
+# Configuring Access with Clouds, Groups, and Roles
+
+As you get started, it’s vital to understand constructs such as Clouds and Groups as they are implemented in HPE Morpheus Enterprise. Deploying an effective strategy for dividing organizational resources and people groups under these constructs will ensure all parties have convenient access to the resources they need. Map currently-existing strategies for splitting resources and controlling costs into HPE Morpheus Enterprise and your teams will have access only to resources allocated to their department.
+
+This guide discusses the constructs of Clouds, Groups, Roles, Users, and Policies while also presenting an example use case for allocating resources and distributing access under these umbrellas. We’ll end up with a permissions structure represented by the diagram below and step through each part of the implementation process.
+
+![../../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+## Clouds
+
+Clouds have broad meaning in HPE Morpheus Enterprise and can be integrations into public clouds, private clouds, or bare metal servers. You can read more about Clouds in HPE Morpheus Enterprise Docs [here](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/clouds.html).
+
+In our example case, the organization has an Azure account and three separate departmental projects consolidated under separate resource groups. The HPE Morpheus Enterprise integration with Azure public cloud allows users to scope the Cloud to one specific resource group, if desired. We will do so in this case because it will allow us to restrict our users to the appropriate Azure resource groups in a later step. In the screenshot below, note how I am scoping the HPE Morpheus Enterprise Azure Cloud to a specific resource group when adding or editing the Cloud. This process will be repeated two additional times to create the three HPE Morpheus Enterprise Clouds we need. Complete details on integrating HPE Morpheus Enterprise with Azure public cloud are [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/azure/azure.html) in HPE Morpheus Enterprise Docs.
+
+![../../_images/1configCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-04D720D8-D7A9-44B8-8585-DBDEDD802C3D-high.png)
+
+## Groups
+
+[Groups](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html) in HPE Morpheus Enterprise allow administrators to determine which Clouds their users have access to. Part of defining a Role, which we’ll see in the next section, is selecting which Groups are associated with the Role. One or multiple Clouds are added to each Group and passed to users through their assigned Roles.
+
+When creating a Cloud, it must be added to a Group. Additionally, Clouds can be added to a Group at any time from the Clouds tab on the Group detail page (Infrastructure > Groups > Specific Group). In the example case diagrammed above, one Cloud (Azure cloud account scoped to a specific resource group) is associated with each Group but often Groups will contain many Clouds. In the screenshot below, I am adding an Azure Cloud to a Group that is currently empty.
+
+![../../_images/2addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0AB9B625-EF46-4CA2-B797-B86D533F52B4-high.png)
+
+## Roles
+
+HPE Morpheus Enterprise Roles determine user access to many things, including application features, Groups, configured Instance Types, configured Blueprints, Personas, and Catalog Item configurations for the Service Catalog Persona. It’s important to note that a user can have multiple Roles and will take the most permissive rights across all of these Roles. In many cases, this greatly simplifies Role configuration for administrators as it prevents the need to create highly-specific individual Roles that can suit every case. To illustrate this for our example case, I will create a set of Roles to handle Group access for my users and another set of Roles to give access to the correct feature permissions.
+
+For this example case, I’ll start by creating one Role for each of the three Groups we created in the previous step. By default, a new Role will have all feature permissions set to “None” as shown below meaning we can skip directly to the Group Access tab.
+
+![../../_images/3roleFeatureAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E0F14807-7823-4651-8193-7E2F04ADC12E-high.png)
+
+On the Group Access tab, I will toggle the Global Access setting to Custom and give access only to one Group as shown in the next image. By doing this for each of our Groups created in the last section, we can easily control Group access for each user by applying one or more of our Group Roles to their user which we will do in the next section.
+
+![../../_images/4roleGroupAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1F85B206-FDB4-478F-BCEC-96E7184EF31F-high.png)
+
+In addition to Roles for handling Group access, we need additional Role sets which will control our feature access. For example, we might have highly permissive feature access for administrators and more restrictive ones for developers or other users who have specific responsibilities requiring access to just a few specific areas of the UI. These additional Roles are created in the same way as the Group Roles we just created but all Group access will be set to “None” and the appropriate feature access will be configured on the “Feature Access” tab.
+
+## Users
+
+With the groundwork laid in the previous steps, we can easily configure permissions for any user accounts we might add to HPE Morpheus Enterprise. In the screenshot below, I’m adding a user account for a developer at my organization. I’ve applied one Role to handle correct Group access for this user and I’ve applied the “Developer” role to give only the feature access needed for this user to carry out his or her responsibilities.
+
+![../../_images/5newUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-295DFC03-0A0D-4350-B2DB-30692FE51851-high.png)
+
+## Policies
+
+One final consideration for this example case is policy application. HPE Morpheus Enterprise enables administrators to place fine-grained governance scoped to specific users, Roles, Groups, Clouds, Tenants, or globally. You can read more about policies in HPE Morpheus Enterprise docs [here](https://docs.morpheusdata.com/en/latest/administration/policies/policies.html) but we will also create some that apply to the example case discussed in this guide.
+
+Policies are created from the Administration menu in the Policies section. In the screenshot below, I’ve created a new policy and chosen to scope it to a Group. In this case, I’m creating a maximum VMs policy but there are many other types which are listed in our documentation linked above.
+
+![../../_images/6policies.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-21C24B9B-7C14-48A8-AB21-9D31F5DF44DC-high.png)
+
+## Conclusion
+
+At this point, we’ve completed implementation of the access structure. As new users are added, we can easily give them the Group and feature access they need. We can also easily add or edit the policies that are in place or add new Clouds and distribute access to existing users. The key is understanding the relationship between the HPE Morpheus Enterprise constructs discussed in this guide. Armed with that understanding, the example case presented here can be expanded to suit the needs of large-scale enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json b/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
new file mode 100644
index 0000000..32f238c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+  "title": "Resources",
+  "ordinal": 214,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html",
+  "topic_cluster": {
+    "clustering_title": "Resources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md b/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
new file mode 100644
index 0000000..b44eed8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
@@ -0,0 +1,1018 @@
+# Resources
+
+![../../_images/infra_compute_header_resources_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F4C1D71D-FBE1-47F2-A56D-36C1E419CA22-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Resource Type Cloud
+
+Resources represent objects that do not map to VM or Container types in HPE Morpheus Enterprise, such as IAC resources from Terraform, Cloudformation or ARM Templates like VPC’s, Gateways, Users, Policies, Brokers, API’s, Endpoints, Directories, ACL’s, Routes… well anything really. All resources created from IAC Templates map to iac provider resource types and HPE Morpheus Enterprise maintains a resource object record from the mapped resource.
+
+Expand the **Resource Types** table below to see all Resource types that will be mapped to Resource objects in HPE Morpheus Enterprise:
+
+## Resource Types
+
+The following Resource Types are mapped when provisioning IAC templates including Terraform and CloudFormation templates.
+
+| ICON | RESOURCE NAME | PROVIDER | RESOURCE TYPE | MORPHEUS TYPE |
+| --- | --- | --- | --- | --- |
+| ../../_images/aws-resource.png | Accessanalyzer Analyzer | terraform | accessanalyzerAnalyzer | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate | terraform | acmCertificate | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate Validation | terraform | acmCertificateValidation | accountResource |
+| ../../_images/aws-resource.png | Acmpca Certificate Authority | terraform | acmpcaCertificateAuthority | accountResource |
+| ../../_images/azure-securitycenter.png | Advanced Threat Protection | terraform | AdvancedThreatProtection | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api | cloudFormation | Api | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Authorizer | cloudFormation | Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Deployment | cloudFormation | Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Domain Name | cloudFormation | DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration | cloudFormation | Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration Response | cloudFormation | IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Mapping | cloudFormation | ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Model | cloudFormation | Model | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route Response | cloudFormation | RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Stage | cloudFormation | Stage | accountResource |
+| ../../_images/aws-ec2.png | Ami | terraform | ami | accountResource |
+| ../../_images/aws-ec2.png | Ami Copy | terraform | amiCopy | accountResource |
+| ../../_images/aws-ec2.png | Ami From Instance | terraform | amiFromInstance | accountResource |
+| ../../_images/aws-ec2.png | Ami Launch Permission | terraform | amiLaunchPermission | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-resource.png | API | terraform | API | accountResource |
+| ../../_images/azure-resource.png | API Authorization Server | terraform | APIAuthorizationServer | accountResource |
+| ../../_images/azure-resource.png | API Backend | terraform | APIBackend | accountResource |
+| ../../_images/azure-resource.png | API Certificate | terraform | APICertificate | accountResource |
+| ../../_images/azure-resource.png | API Diagnostic | terraform | APIDiagnostic | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Account | terraform | apiGatewayAccount | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Api Key | terraform | apiGatewayApiKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Authorizer | terraform | apiGatewayAuthorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Base Path Mapping | terraform | apiGatewayBasePathMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Client Certificate | terraform | apiGatewayClientCertificate | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Deployment | terraform | apiGatewayDeployment | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Part | terraform | apiGatewayDocumentationPart | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Version | terraform | apiGatewayDocumentationVersion | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Domain Name | terraform | apiGatewayDomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Gateway Response | terraform | apiGatewayGatewayResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration | terraform | apiGatewayIntegration | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration Response | terraform | apiGatewayIntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method | terraform | apiGatewayMethod | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Response | terraform | apiGatewayMethodResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Settings | terraform | apiGatewayMethodSettings | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Model | terraform | apiGatewayModel | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Request Validator | terraform | apiGatewayRequestValidator | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Resource | terraform | apiGatewayResource | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Rest Api | terraform | apiGatewayRestApi | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Stage | terraform | apiGatewayStage | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan | terraform | apiGatewayUsagePlan | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan Key | terraform | apiGatewayUsagePlanKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Vpc Link | terraform | apiGatewayVpcLink | accountResource |
+| ../../_images/azure-resource.png | API Group | terraform | APIGroup | accountResource |
+| ../../_images/azure-resource.png | API Group User | terraform | APIGroupUser | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider AD | terraform | APIIdentityProviderAD | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Facebook | terraform | APIIdentityProviderFacebook | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Google | terraform | APIIdentityProviderGoogle | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Microsoft | terraform | APIIdentityProviderMicrosoft | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Twitter | terraform | APIIdentityProviderTwitter | accountResource |
+| ../../_images/azure-resource.png | API Logger | terraform | APILogger | accountResource |
+| ../../_images/azure-resource.png | API Management | terraform | APIManagement | accountResource |
+| ../../_images/azure-resource.png | API Named Value | terraform | APINamedValue | accountResource |
+| ../../_images/azure-resource.png | API OpenID Provider | terraform | APIOpenIDProvider | accountResource |
+| ../../_images/azure-resource.png | API Operation | terraform | APIOperation | accountResource |
+| ../../_images/azure-resource.png | API Operation Policy | terraform | APIOperationPolicy | accountResource |
+| ../../_images/azure-resource.png | API Policy | terraform | APIPolicy | accountResource |
+| ../../_images/azure-resource.png | API Product | terraform | APIProduct | accountResource |
+| ../../_images/azure-resource.png | API Product API | terraform | APIProductAPI | accountResource |
+| ../../_images/azure-resource.png | API Product Group | terraform | APIProductGroup | accountResource |
+| ../../_images/azure-resource.png | API Product Policy | terraform | APIProductPolicy | accountResource |
+| ../../_images/azure-resource.png | API Property | terraform | APIProperty | accountResource |
+| ../../_images/azure-resource.png | API Schema | terraform | APISchema | accountResource |
+| ../../_images/azure-resource.png | API Subscription | terraform | APISubscription | accountResource |
+| ../../_images/azure-resource.png | API User | terraform | APIUser | accountResource |
+| ../../_images/azure-resource.png | API Version Set | terraform | APIVersionSet | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api | terraform | apigatewayv2Api | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api Mapping | terraform | apigatewayv2ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Authorizer | terraform | apigatewayv2Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Deployment | terraform | apigatewayv2Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Domain Name | terraform | apigatewayv2DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration | terraform | apigatewayv2Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration Response | terraform | apigatewayv2IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Model | terraform | apigatewayv2Model | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route | terraform | apigatewayv2Route | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route Response | terraform | apigatewayv2RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Stage | terraform | apigatewayv2Stage | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Vpc Link | terraform | apigatewayv2VpcLink | accountResource |
+| ../../_images/azure-appconfiguration.png | App Configuration | terraform | AppConfiguration | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | App Cookie Stickiness Policy | terraform | appCookieStickinessPolicy | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Analytics Item | terraform | AppInsightsAnalyticsItem | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights API Key | terraform | AppInsightsAPIKey | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Web Test | terraform | AppInsightsWebTest | accountResource |
+| ../../_images/azure-resource.png | App Service | terraform | AppService | accountResource |
+| ../../_images/azure-resource.png | App Service Active Slot | terraform | AppServiceActiveSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate | terraform | AppServiceCertificate | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate Order | terraform | AppServiceCertificateOrder | accountResource |
+| ../../_images/azure-resource.png | App Service Environment | terraform | AppServiceEnvironment | accountResource |
+| ../../_images/azure-resource.png | App Service Host Binding | terraform | AppServiceHostBinding | accountResource |
+| ../../_images/azure-resource.png | App Service Network Swift Connection | terraform | AppServiceNetworkSwiftConnection | accountResource |
+| ../../_images/azure-resource.png | App Service Plan | terraform | AppServicePlan | accountResource |
+| ../../_images/azure-resource.png | App Service Slot | terraform | AppServiceSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Source Control Token | terraform | AppServiceSourceControlToken | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Policy | terraform | appautoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Scheduled Action | terraform | appautoscalingScheduledAction | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Target | terraform | appautoscalingTarget | accountResource |
+| ../../_images/azure-compute.png | Application Definition | terraform | ApplicationDefinition | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-applicationinsights.png | Application Insights | terraform | ApplicationInsights | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/aws-resource.png | Appmesh Mesh | terraform | appmeshMesh | accountResource |
+| ../../_images/aws-resource.png | Appmesh Route | terraform | appmeshRoute | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Node | terraform | appmeshVirtualNode | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Router | terraform | appmeshVirtualRouter | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Service | terraform | appmeshVirtualService | accountResource |
+| ../../_images/aws-appsync.png | Appsync Api Key | terraform | appsyncApiKey | accountResource |
+| ../../_images/aws-appsync.png | Appsync Datasource | terraform | appsyncDatasource | accountResource |
+| ../../_images/aws-appsync.png | Appsync Function | terraform | appsyncFunction | accountResource |
+| ../../_images/aws-appsync.png | Appsync Graphql Api | terraform | appsyncGraphqlApi | accountResource |
+| ../../_images/aws-appsync.png | Appsync Resolver | terraform | appsyncResolver | accountResource |
+| ../../_images/aws-athena.png | Athen Named Query | cloudFormation | NamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Database | terraform | athenaDatabase | accountResource |
+| ../../_images/aws-athena.png | Athena Named Query | terraform | athenaNamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Workgroup | terraform | athenaWorkgroup | accountResource |
+| ../../_images/azure-automation.png | Automation Account | terraform | AutomationAccount | accountResource |
+| ../../_images/azure-automation.png | Automation Certificate | terraform | AutomationCertificate | accountResource |
+| ../../_images/azure-automation.png | Automation Credential | terraform | AutomationCredential | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Config | terraform | AutomationDSCConfig | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Node Config | terraform | AutomationDSCNodeConfig | accountResource |
+| ../../_images/azure-automation.png | Automation Job Schedule | terraform | AutomationJobSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Module | terraform | AutomationModule | accountResource |
+| ../../_images/azure-automation.png | Automation Runbook | terraform | AutomationRunbook | accountResource |
+| ../../_images/azure-automation.png | Automation Schedule | terraform | AutomationSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Boolean | terraform | AutomationVariableBoolean | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Datetime | terraform | AutomationVariableDatetime | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Int | terraform | AutomationVariableInt | accountResource |
+| ../../_images/azure-automation.png | Automation Variable String | terraform | AutomationVariableString | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Attachment | terraform | autoscalingAttachment | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Group | terraform | autoscalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Lifecycle Hook | terraform | autoscalingLifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Notification | terraform | autoscalingNotification | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Policy | terraform | autoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Schedule | terraform | autoscalingSchedule | accountResource |
+| ../../_images/azure-compute.png | Availability Set | terraform | AvailabilitySet | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener | cloudFormation | Listener | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Certificate | cloudFormation | ListenerCertificate | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Rule | cloudFormation | ListenerRule | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Target Group | cloudFormation | TargetGroup | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh | cloudFormation | Mesh | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Node | cloudFormation | VirtualNode | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Router | cloudFormation | VirtualRouter | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Service | cloudFormation | VirtualService | accountResource |
+| ../../_images/aws-elb.png | AWS Application Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Group | cloudFormation | AutoScalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Launch Configuration | cloudFormation | LaunchConfiguration | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Lifecycle Hook | cloudFormation | LifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Policy | cloudFormation | ScalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Scheduled Action | cloudFormation | ScheduledAction | accountResource |
+| ../../_images/aws-elb.png | AWS Elastic Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-elasticsearch-service.png | AWS Elasticsearch Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-sdb.png | AWS SDB Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Resource Policy | cloudFormation | ResourcePolicy | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Rotation Schedule | cloudFormation | RotationSchedule | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret | cloudFormation | Secret | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret Target Attachment | cloudFormation | SecretTargetAttachment | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set | cloudFormation | ConfigurationSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set Event Destination | cloudFormation | ConfigurationSetEventDestination | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Filter | cloudFormation | ReceiptFilter | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule | cloudFormation | ReceiptRule | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule Set | cloudFormation | ReceiptRuleSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Template | cloudFormation | Template | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Subscription | cloudFormation | Subscription | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic | cloudFormation | Topic | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic Policy | cloudFormation | TopicPolicy | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue | cloudFormation | Queue | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue Policy | cloudFormation | QueuePolicy | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Geo Match Set | cloudFormation | GeoMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rate Based Rule | cloudFormation | RateBasedRule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Regex Pattern Set | cloudFormation | RegexPatternSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL Association | cloudFormation | WebACLAssociation | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-workspaces.png | AWS Workspace | cloudFormation | Workspace | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/aws-backup.png | Backup Plan | terraform | backupPlan | accountResource |
+| ../../_images/azure-backup.png | Backup Policy File Share | terraform | BackupPolicyFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Policy VM | terraform | BackupPolicyVM | accountResource |
+| ../../_images/azure-backup.png | Backup Protected File Share | terraform | BackupProtectedFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Protected VM | terraform | BackupProtectedVM | accountResource |
+| ../../_images/aws-backup.png | Backup Selection | terraform | backupSelection | accountResource |
+| ../../_images/azure-backup.png | Backup Storage Account | terraform | BackupStorageAccount | accountResource |
+| ../../_images/aws-backup.png | Backup Vault | terraform | backupVault | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/aws-resource.png | Batch Compute Environment | terraform | batchComputeEnvironment | accountResource |
+| ../../_images/aws-resource.png | Batch Job Definition | terraform | batchJobDefinition | accountResource |
+| ../../_images/aws-resource.png | Batch Job Queue | terraform | batchJobQueue | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Registration | terraform | BotChannelRegistration | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Slack | terraform | BotChannelSlack | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Direct Line | terraform | BotDirectLine | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/aws-resource.png | Budgets Budget | terraform | budgetsBudget | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/aws-resource.png | Cloud9 Environment Ec2 | terraform | cloud9EnvironmentEc2 | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack | terraform | cloudformationStack | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set | terraform | cloudformationStackSet | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set Instance | terraform | cloudformationStackSetInstance | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Distribution | terraform | cloudfrontDistribution | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Origin Access Identity | terraform | cloudfrontOriginAccessIdentity | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Public Key | terraform | cloudfrontPublicKey | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Cluster | terraform | cloudhsmV2Cluster | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Hsm | terraform | cloudhsmV2Hsm | accountResource |
+| ../../_images/aws-cloudtrail.png | Cloudtrail | terraform | cloudtrail | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Dashboard | terraform | cloudwatchDashboard | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Permission | terraform | cloudwatchEventPermission | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Rule | terraform | cloudwatchEventRule | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Target | terraform | cloudwatchEventTarget | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination | terraform | cloudwatchLogDestination | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination Policy | terraform | cloudwatchLogDestinationPolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Group | terraform | cloudwatchLogGroup | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Metric Filter | terraform | cloudwatchLogMetricFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Resource Policy | terraform | cloudwatchLogResourcePolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Stream | terraform | cloudwatchLogStream | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Subscription Filter | terraform | cloudwatchLogSubscriptionFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Metric Alarm | terraform | cloudwatchMetricAlarm | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Project | terraform | codebuildProject | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Source Credential | terraform | codebuildSourceCredential | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Webhook | terraform | codebuildWebhook | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Repository | terraform | codecommitRepository | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Trigger | terraform | codecommitTrigger | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy App | terraform | codedeployApp | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Config | terraform | codedeployDeploymentConfig | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Group | terraform | codedeployDeploymentGroup | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline | terraform | codepipeline | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline Webhook | terraform | codepipelineWebhook | accountResource |
+| ../../_images/aws-codestar.png | Codestarnotifications Notification Rule | terraform | codestarnotificationsNotificationRule | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool | terraform | cognitoIdentityPool | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool Roles Attachment | terraform | cognitoIdentityPoolRolesAttachment | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Provider | terraform | cognitoIdentityProvider | accountResource |
+| ../../_images/aws-resource.png | Cognito Resource Server | terraform | cognitoResourceServer | accountResource |
+| ../../_images/aws-resource.png | Cognito User Group | terraform | cognitoUserGroup | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool | terraform | cognitoUserPool | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Client | terraform | cognitoUserPoolClient | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Domain | terraform | cognitoUserPoolDomain | accountResource |
+| ../../_images/aws-resource.png | Config Aggregate Authorization | terraform | configAggregateAuthorization | accountResource |
+| ../../_images/aws-resource.png | Config Config Rule | terraform | configConfigRule | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Aggregator | terraform | configConfigurationAggregator | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder | terraform | configConfigurationRecorder | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder Status | terraform | configConfigurationRecorderStatus | accountResource |
+| ../../_images/aws-resource.png | Config Delivery Channel | terraform | configDeliveryChannel | accountResource |
+| ../../_images/aws-resource.png | Config Organization Custom Rule | terraform | configOrganizationCustomRule | accountResource |
+| ../../_images/aws-resource.png | Config Organization Managed Rule | terraform | configOrganizationManagedRule | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Account | terraform | CosmosDBAccount | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Cassandra Keyspace | terraform | CosmosDBCassandraKeyspace | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Database | terraform | CosmosDBGremlinDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Graph | terraform | CosmosDBGremlinGraph | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Collection | terraform | CosmosDBMongoCollection | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Database | terraform | CosmosDBMongoDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Container | terraform | CosmosDBSQLContainer | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Database | terraform | CosmosDBSQLDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Table | terraform | CosmosDBTable | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/aws-resource.png | Cur Report Definition | terraform | curReportDefinition | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/aws-vpc.png | Customer Gateway | terraform | customerGateway | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory | terraform | DataFactory | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Data Lake Storage | terraform | DataFactoryDataLakeStorage | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Integration Runtime | terraform | DataFactoryIntegrationRuntime | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Dataset | terraform | DataFactoryMySQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Link | terraform | DataFactoryMySQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Pipeline | terraform | DataFactoryPipeline | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Dataset | terraform | DataFactoryPostgreSQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Link | terraform | DataFactoryPostgreSQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Link | terraform | DataFactorySQLServerLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Table | terraform | DataFactorySQLServerTable | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Trigger Schedule | terraform | DataFactoryTriggerSchedule | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Account | terraform | DataLakeAnalyticsAccount | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Firewall Rule | terraform | DataLakeAnalyticsFirewallRule | accountResource |
+| ../../_images/azure-storage.png | Data Lake Filesystem | terraform | DataLakeFilesystem | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store | terraform | DataLakeStore | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store File | terraform | DataLakeStoreFile | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store Firewall Rule | terraform | DataLakeStoreFirewallRule | accountResource |
+| ../../_images/azure-datashare.png | Data Share Account | terraform | DataShareAccount | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Project | terraform | DatabaseMigrationProject | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Service | terraform | DatabaseMigrationService | accountResource |
+| ../../_images/azure-databricks.png | Databricks Workspace | terraform | DatabricksWorkspace | accountResource |
+| ../../_images/aws-resource.png | Datapipeline Pipeline | terraform | datapipelinePipeline | accountResource |
+| ../../_images/aws-resource.png | Datasync Agent | terraform | datasyncAgent | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Efs | terraform | datasyncLocationEfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Nfs | terraform | datasyncLocationNfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location S3 | terraform | datasyncLocationS3 | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Smb | terraform | datasyncLocationSmb | accountResource |
+| ../../_images/aws-resource.png | Datasync Task | terraform | datasyncTask | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Cluster | terraform | daxCluster | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Parameter Group | terraform | daxParameterGroup | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Subnet Group | terraform | daxSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | Db Cluster Snapshot | terraform | dbClusterSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Event Subscription | terraform | dbEventSubscription | accountResource |
+| ../../_images/aws-rds.png | Db Instance | terraform | dbInstance | accountResource |
+| ../../_images/aws-rds.png | Db Instance Role Association | terraform | dbInstanceRoleAssociation | accountResource |
+| ../../_images/aws-rds.png | Db Option Group | terraform | dbOptionGroup | accountResource |
+| ../../_images/aws-rds.png | Db Parameter Group | terraform | dbParameterGroup | accountResource |
+| ../../_images/aws-rds.png | Db Security Group | terraform | dbSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | Db Snapshot | terraform | dbSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Subnet Group | terraform | dbSubnetGroup | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host | terraform | DedicatedHost | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host Group | terraform | DedicatedHostGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Network Acl | terraform | defaultNetworkAcl | accountResource |
+| ../../_images/aws-vpc.png | Default Route Table | terraform | defaultRouteTable | accountResource |
+| ../../_images/aws-vpc.png | Default Security Group | terraform | defaultSecurityGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Subnet | terraform | defaultSubnet | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc | terraform | defaultVpc | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc Dhcp Options | terraform | defaultVpcDhcpOptions | accountResource |
+| ../../_images/aws-resource.png | Devicefarm Project | terraform | devicefarmProject | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/aws-resource.png | Directory Service Conditional Forwarder | terraform | directoryServiceConditionalForwarder | accountResource |
+| ../../_images/aws-resource.png | Directory Service Directory | terraform | directoryServiceDirectory | accountResource |
+| ../../_images/aws-resource.png | Directory Service Log Subscription | terraform | directoryServiceLogSubscription | accountResource |
+| ../../_images/azure-compute.png | Disk Encryption Set | terraform | DiskEncryptionSet | accountResource |
+| ../../_images/aws-resource.png | Dlm Lifecycle Policy | terraform | dlmLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Dms Certificate | terraform | dmsCertificate | accountResource |
+| ../../_images/aws-resource.png | Dms Endpoint | terraform | dmsEndpoint | accountResource |
+| ../../_images/aws-resource.png | Dms Event Subscription | terraform | dmsEventSubscription | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Instance | terraform | dmsReplicationInstance | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Subnet Group | terraform | dmsReplicationSubnetGroup | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Task | terraform | dmsReplicationTask | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS AAAA Record | terraform | DNSAAAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CAA Record | terraform | DNSCAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS PTR Record | terraform | DNSPTRRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster | terraform | docdbCluster | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Instance | terraform | docdbClusterInstance | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Parameter Group | terraform | docdbClusterParameterGroup | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Snapshot | terraform | docdbClusterSnapshot | accountResource |
+| ../../_images/aws-resource.png | Docdb Subnet Group | terraform | docdbSubnetGroup | accountResource |
+| ../../_images/aws-directconnect.png | Dx Bgp Peer | terraform | dxBgpPeer | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection | terraform | dxConnection | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection Association | terraform | dxConnectionAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway | terraform | dxGateway | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association | terraform | dxGatewayAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association Proposal | terraform | dxGatewayAssociationProposal | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface | terraform | dxHostedPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface Accepter | terraform | dxHostedPrivateVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface | terraform | dxHostedPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface Accepter | terraform | dxHostedPublicVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface | terraform | dxHostedTransitVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface Accepter | terraform | dxHostedTransitVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Lag | terraform | dxLag | accountResource |
+| ../../_images/aws-directconnect.png | Dx Private Virtual Interface | terraform | dxPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Public Virtual Interface | terraform | dxPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Transit Virtual Interface | terraform | dxTransitVirtualInterface | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Global Table | terraform | dynamodbGlobalTable | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table | terraform | dynamodbTable | accountResource |
+| ../../_images/aws-dynamodb.png | DynamoDB Table | cloudFormation | Table | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table Item | terraform | dynamodbTableItem | accountResource |
+| ../../_images/aws-ec2.png | Ebs Default Kms Key | terraform | ebsDefaultKmsKey | accountResource |
+| ../../_images/aws-ec2.png | Ebs Encryption By Default | terraform | ebsEncryptionByDefault | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot | terraform | ebsSnapshot | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot Copy | terraform | ebsSnapshotCopy | accountResource |
+| ../../_images/aws-ec2.png | Ebs Volume | terraform | ebsVolume | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Availability Zone Group | terraform | ec2AvailabilityZoneGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Capacity Reservation | cloudFormation | CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Capacity Reservation | terraform | ec2CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Authorization Rule | cloudFormation | ClientVpnAuthorizationRule | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Endpoint | cloudFormation | ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Endpoint | terraform | ec2ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Network Association | terraform | ec2ClientVpnNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Route | cloudFormation | ClientVpnRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Target Network Association | cloudFormation | ClientVpnTargetNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Customer Gateway | cloudFormation | CustomerGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 DHCP Options | cloudFormation | DHCPOptions | accountResource |
+| ../../_images/aws-ec2.png | EC2 Egress Only Internet Gateway | cloudFormation | EgressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP | cloudFormation | EIP | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP Association | cloudFormation | EIPAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Fleet | cloudFormation | EC2Fleet | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Fleet | terraform | ec2Fleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Flow Log | cloudFormation | FlowLog | accountResource |
+| ../../_images/aws-ec2.png | EC2 Host | cloudFormation | Host | accountResource |
+| ../../_images/aws-ec2.png | EC2 Instance | cloudFormation | Instance | instance |
+| ../../_images/aws-ec2.png | EC2 Internet Gateway | cloudFormation | InternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Launch Template | cloudFormation | LaunchTemplate | accountResource |
+| ../../_images/aws-ec2.png | EC2 Nat Gateway | cloudFormation | NatGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl | cloudFormation | NetworkAcl | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl Entry | cloudFormation | NetworkAclEntry | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface | cloudFormation | NetworkInterface | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Attachment | cloudFormation | NetworkInterfaceAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Permission | cloudFormation | NetworkInterfacePermission | accountResource |
+| ../../_images/aws-ec2.png | EC2 Placement Group | cloudFormation | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route Table | cloudFormation | RouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Egress | cloudFormation | SecurityGroupEgress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Spot Fleet | cloudFormation | SpotFleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet | cloudFormation | Subnet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Cidr Block | cloudFormation | SubnetCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Network Acl Association | cloudFormation | SubnetNetworkAclAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Route Table Association | cloudFormation | SubnetRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter | terraform | ec2TrafficMirrorFilter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter Rule | terraform | ec2TrafficMirrorFilterRule | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Session | terraform | ec2TrafficMirrorSession | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Target | terraform | ec2TrafficMirrorTarget | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway | terraform | ec2TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway | cloudFormation | TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Attachment | cloudFormation | TransitGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment | terraform | ec2TransitGatewayPeeringAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment Accepter | terraform | ec2TransitGatewayPeeringAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route | terraform | ec2TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route | cloudFormation | TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table | terraform | ec2TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table | cloudFormation | TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Association | terraform | ec2TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Association | cloudFormation | TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Propagation | terraform | ec2TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Propagation | cloudFormation | TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment | terraform | ec2TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway VPC Attachment | cloudFormation | TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment Accepter | terraform | ec2TransitGatewayVpcAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume | cloudFormation | Volume | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume Attachment | cloudFormation | VolumeAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC | cloudFormation | VPC | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Cidr Block | cloudFormation | VPCCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC DHCP Options Association | cloudFormation | VPCDHCPOptionsAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint | cloudFormation | VPCEndpoint | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Connection Notification | cloudFormation | VPCEndpointConnectionNotification | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service | cloudFormation | VPCEndpointService | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service Permissions | cloudFormation | VPCEndpointServicePermissions | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Gateway Attachment | cloudFormation | VPCGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Peering Connection | cloudFormation | VPCPeeringConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection | cloudFormation | VPNConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection Route | cloudFormation | VPNConnectionRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway | cloudFormation | VPNGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway Route Propagation | cloudFormation | VPNGatewayRoutePropagation | accountResource |
+| ../../_images/aws-resource.png | Ecr Lifecycle Policy | terraform | ecrLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository | terraform | ecrRepository | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository Policy | terraform | ecrRepositoryPolicy | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Capacity Provider | terraform | ecsCapacityProvider | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Cluster | terraform | ecsCluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Service | terraform | ecsService | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Service | cloudFormation | Service | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Task Definition | terraform | ecsTaskDefinition | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Task Definition | cloudFormation | TaskDefinition | accountResource |
+| ../../_images/aws-efs.png | Efs File System | terraform | efsFileSystem | accountResource |
+| ../../_images/aws-efs.png | EFS FileSystem | cloudFormation | FileSystem | accountResource |
+| ../../_images/aws-efs.png | Efs Mount Target | terraform | efsMountTarget | accountResource |
+| ../../_images/aws-efs.png | EFS Mount Target | cloudFormation | MountTarget | accountResource |
+| ../../_images/aws-vpc.png | Egress Only Internet Gateway | terraform | egressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | Eip | terraform | eip | accountResource |
+| ../../_images/aws-ec2.png | Eip Association | terraform | eipAssociation | accountResource |
+| ../../_images/aws-eks.png | EKS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-eks.png | Eks Cluster | terraform | eksCluster | accountResource |
+| ../../_images/aws-eks.png | Eks Fargate Profile | terraform | eksFargateProfile | accountResource |
+| ../../_images/aws-eks.png | Eks Node Group | terraform | eksNodeGroup | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | cloudFormation | Application | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | terraform | elasticBeanstalkApplication | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | cloudFormation | ApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | terraform | elasticBeanstalkApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | cloudFormation | ConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | terraform | elasticBeanstalkConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | terraform | elasticBeanstalkEnvironment | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | cloudFormation | Environment | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Cluster | cloudFormation | CacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Cluster | terraform | elasticacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Parameter Group | terraform | elasticacheParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Parameter Group | cloudFormation | ParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Replication Group | terraform | elasticacheReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Replication Group | cloudFormation | ReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Security Group | terraform | elasticacheSecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Subnet Group | terraform | elasticacheSubnetGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Subnet Group | cloudFormation | SubnetGroup | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain | terraform | elasticsearchDomain | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain Policy | terraform | elasticsearchDomainPolicy | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Pipeline | terraform | elastictranscoderPipeline | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Preset | terraform | elastictranscoderPreset | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb | terraform | elb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb Attachment | terraform | elbAttachment | accountResource |
+| ../../_images/aws-emr.png | EMR Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-emr.png | Emr Cluster | terraform | emrCluster | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Fleet Config | cloudFormation | InstanceFleetConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Instance Group | terraform | emrInstanceGroup | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Group Config | cloudFormation | InstanceGroupConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Security Configuration | terraform | emrSecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Security Configuration | cloudFormation | SecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Step | cloudFormation | Step | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Domain | terraform | EventGridDomain | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Event Subscription | terraform | EventGridEventSubscription | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Topic | terraform | EventGridTopic | accountResource |
+| ../../_images/azure-messaging.png | Event Hub | terraform | EventHub | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Authorization Rule | terraform | EventHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Consumer Group | terraform | EventHubConsumerGroup | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Disaster Recovery Config | terraform | EventHubDisasterRecoveryConfig | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace | terraform | EventHubNamespace | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace Authorization Rule | terraform | EventHubNamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Authorization | terraform | ExpressRouteCircuitAuthorization | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Firewall | terraform | Firewall | accountResource |
+| ../../_images/azure-network.png | Firewall Application Rule Collection | terraform | FirewallApplicationRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Network Rule Collection | terraform | FirewallNetworkRuleCollection | accountResource |
+| ../../_images/aws-vpc.png | Flow Log | terraform | flowLog | accountResource |
+| ../../_images/aws-resource.png | Fms Admin Account | terraform | fmsAdminAccount | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/aws-fsx.png | Fsx Lustre File System | terraform | fsxLustreFileSystem | accountResource |
+| ../../_images/aws-fsx.png | Fsx Windows File System | terraform | fsxWindowsFileSystem | accountResource |
+| ../../_images/azure-resource.png | Function App | terraform | FunctionApp | accountResource |
+| ../../_images/azure-resource.png | Function App Slot | terraform | FunctionAppSlot | accountResource |
+| ../../_images/aws-resource.png | Gamelift Alias | terraform | gameliftAlias | accountResource |
+| ../../_images/aws-resource.png | Gamelift Build | terraform | gameliftBuild | accountResource |
+| ../../_images/aws-resource.png | Gamelift Fleet | terraform | gameliftFleet | accountResource |
+| ../../_images/aws-resource.png | Gamelift Game Session Queue | terraform | gameliftGameSessionQueue | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault | terraform | glacierVault | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault Lock | terraform | glacierVaultLock | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Accelerator | terraform | globalacceleratorAccelerator | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Endpoint Group | terraform | globalacceleratorEndpointGroup | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Listener | terraform | globalacceleratorListener | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Database | terraform | glueCatalogDatabase | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Table | terraform | glueCatalogTable | accountResource |
+| ../../_images/aws-glue.png | Glue Classifier | terraform | glueClassifier | accountResource |
+| ../../_images/aws-glue.png | Glue Connection | terraform | glueConnection | accountResource |
+| ../../_images/aws-glue.png | Glue Crawler | terraform | glueCrawler | accountResource |
+| ../../_images/aws-glue.png | Glue Job | terraform | glueJob | accountResource |
+| ../../_images/aws-glue.png | Glue Security Configuration | terraform | glueSecurityConfiguration | accountResource |
+| ../../_images/aws-glue.png | Glue Trigger | terraform | glueTrigger | accountResource |
+| ../../_images/aws-glue.png | Glue Workflow | terraform | glueWorkflow | accountResource |
+| ../../_images/aws-resource.png | Guardduty Detector | terraform | guarddutyDetector | accountResource |
+| ../../_images/aws-resource.png | Guardduty Invite Accepter | terraform | guarddutyInviteAccepter | accountResource |
+| ../../_images/aws-resource.png | Guardduty Ipset | terraform | guarddutyIpset | accountResource |
+| ../../_images/aws-resource.png | Guardduty Member | terraform | guarddutyMember | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Admin Account | terraform | guarddutyOrganizationAdminAccount | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Configuration | terraform | guarddutyOrganizationConfiguration | accountResource |
+| ../../_images/aws-resource.png | Guardduty Threatintelset | terraform | guarddutyThreatintelset | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Hadoop Cluster | terraform | HDInsightHadoopCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight HBase Cluster | terraform | HDInsightHBaseCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Kafka Cluster | terraform | HDInsightKafkaCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight ML Services Cluster | terraform | HDInsightMLServicesCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Query Cluster | terraform | HDInsightQueryCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight R Cluster | terraform | HDInsightRCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Spark Cluster | terraform | HDInsightSparkCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Storm Cluster | terraform | HDInsightStormCluster | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-storage.png | HPC Cache | terraform | HPCCache | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/aws-iam.png | IAM Access Key | cloudFormation | AccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Access Key | terraform | iamAccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Account Alias | terraform | iamAccountAlias | accountResource |
+| ../../_images/aws-resource.png | Iam Account Password Policy | terraform | iamAccountPasswordPolicy | accountResource |
+| ../../_images/aws-iam.png | IAM Group | cloudFormation | Group | accountResource |
+| ../../_images/aws-resource.png | Iam Group | terraform | iamGroup | accountResource |
+| ../../_images/aws-resource.png | Iam Group Membership | terraform | iamGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy | terraform | iamGroupPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy Attachment | terraform | iamGroupPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Instance Profile | terraform | iamInstanceProfile | accountResource |
+| ../../_images/aws-resource.png | IAM Instance Profile | cloudFormation | InstanceProfile | accountResource |
+| ../../_images/aws-iam.png | IAM Managed Policy | cloudFormation | ManagedPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Openid Connect Provider | terraform | iamOpenidConnectProvider | accountResource |
+| ../../_images/aws-iam.png | Iam Policy | terraform | iamPolicy | accountResource |
+| ../../_images/aws-resource.png | IAM Policy | cloudFormation | Policy | accountResource |
+| ../../_images/aws-resource.png | Iam Policy Attachment | terraform | iamPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Role | terraform | iamRole | accountResource |
+| ../../_images/aws-resource.png | IAM Role | cloudFormation | Role | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy | terraform | iamRolePolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy Attachment | terraform | iamRolePolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam Saml Provider | terraform | iamSamlProvider | accountResource |
+| ../../_images/aws-resource.png | Iam Server Certificate | terraform | iamServerCertificate | accountResource |
+| ../../_images/aws-iam.png | Iam Service Linked Role | terraform | iamServiceLinkedRole | accountResource |
+| ../../_images/aws-resource.png | IAM Service Linked Role | cloudFormation | ServiceLinkedRole | accountResource |
+| ../../_images/aws-iam.png | Iam User | terraform | iamUser | accountResource |
+| ../../_images/aws-resource.png | IAM User | cloudFormation | User | accountResource |
+| ../../_images/aws-iam.png | IAM User Group Addition | cloudFormation | UserToGroupAddition | accountResource |
+| ../../_images/aws-resource.png | Iam User Group Membership | terraform | iamUserGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam User Login Profile | terraform | iamUserLoginProfile | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy | terraform | iamUserPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy Attachment | terraform | iamUserPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam User Ssh Key | terraform | iamUserSshKey | accountResource |
+| ../../_images/azure-compute.png | Image | terraform | Image | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Target | terraform | inspectorAssessmentTarget | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Template | terraform | inspectorAssessmentTemplate | accountResource |
+| ../../_images/aws-resource.png | Inspector Resource Group | terraform | inspectorResourceGroup | accountResource |
+| ../../_images/aws-ec2.png | Instance | terraform | Instance | instance |
+| ../../_images/aws-vpc.png | Internet Gateway | terraform | internetGateway | accountResource |
+| ../../_images/azure-iot-central-application.png | IOT Central Application | terraform | IOTCentralApplication | accountResource |
+| ../../_images/aws-resource.png | Iot Certificate | terraform | iotCertificate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub | terraform | IOTHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Access Policy | terraform | IOTHubAccessPolicy | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Consumer Group | terraform | IOTHubConsumerGroup | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS | terraform | IOTHubDPS | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS Certficiate | terraform | IOTHubDPSCertficiate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Queue | terraform | IOTHubEndpointQueue | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Storage | terraform | IOTHubEndpointStorage | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Topic | terraform | IOTHubEndpointTopic | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Fallback Route | terraform | IOTHubFallbackRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Route | terraform | IOTHubRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Shared Access Policy | terraform | IOTHubSharedAccessPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy | terraform | iotPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy Attachment | terraform | iotPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Role Alias | terraform | iotRoleAlias | accountResource |
+| ../../_images/aws-resource.png | Iot Thing | terraform | iotThing | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Principal Attachment | terraform | iotThingPrincipalAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Type | terraform | iotThingType | accountResource |
+| ../../_images/aws-resource.png | Iot Topic Rule | terraform | iotTopicRule | accountResource |
+| ../../_images/aws-ec2.png | Key Pair | terraform | keyPair | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault | terraform | KeyVault | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Analytics Application | terraform | kinesisAnalyticsApplication | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Firehose Delivery Stream | terraform | kinesisFirehoseDeliveryStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | terraform | kinesisStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | cloudFormation | Stream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream Consumer | cloudFormation | StreamConsumer | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Video Stream | terraform | kinesisVideoStream | accountResource |
+| ../../_images/aws-resource.png | Kms Alias | terraform | kmsAlias | accountResource |
+| ../../_images/aws-resource.png | Kms Ciphertext | terraform | kmsCiphertext | accountResource |
+| ../../_images/aws-resource.png | Kms External Key | terraform | kmsExternalKey | accountResource |
+| ../../_images/aws-resource.png | Kms Grant | terraform | kmsGrant | accountResource |
+| ../../_images/aws-resource.png | Kms Key | terraform | kmsKey | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Cluster | terraform | KustoCluster | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database | terraform | KustoDatabase | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database Principal | terraform | KustoDatabasePrincipal | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Event Data Connection | terraform | KustoEventDataConnection | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | cloudFormation | Alias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | terraform | lambdaAlias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | cloudFormation | EventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | terraform | lambdaEventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | cloudFormation | Function | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | terraform | lambdaFunction | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function Event Invoke Config | terraform | lambdaFunctionEventInvokeConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | terraform | lambdaLayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | cloudFormation | LayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version Permission | cloudFormation | LayerVersionPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | terraform | lambdaPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | cloudFormation | Permission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Provisioned Concurrency Config | terraform | lambdaProvisionedConcurrencyConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Version | cloudFormation | Version | accountResource |
+| ../../_images/aws-ec2.png | Launch Configuration | terraform | launchConfiguration | accountResource |
+| ../../_images/aws-ec2.png | Launch Template | terraform | launchTemplate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb | terraform | lb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Cookie Stickiness Policy | terraform | lbCookieStickinessPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener | terraform | lbListener | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Certificate | terraform | lbListenerCertificate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Rule | terraform | lbListenerRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Ssl Negotiation Policy | terraform | lbSslNegotiationPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group | terraform | lbTargetGroup | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group Attachment | terraform | lbTargetGroupAttachment | accountResource |
+| ../../_images/aws-resource.png | Licensemanager Association | terraform | licensemanagerAssociation | accountResource |
+| ../../_images/aws-resource.png | Licensemanager License Configuration | terraform | licensemanagerLicenseConfiguration | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Domain | terraform | lightsailDomain | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Instance | terraform | lightsailInstance | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Key Pair | terraform | lightsailKeyPair | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip | terraform | lightsailStaticIp | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip Attachment | terraform | lightsailStaticIpAttachment | accountResource |
+| ../../_images/azure-compute.png | Linux VM Scale Set | terraform | LinuxVMScaleSet | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Backend Server Policy | terraform | loadBalancerBackendServerPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Listener Policy | terraform | loadBalancerListenerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Policy | terraform | loadBalancerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-network.png | Local Network Gateway | terraform | LocalNetworkGateway | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-machinelearning.png | Machine Learning Workspace | terraform | MachineLearningWorkspace | accountResource |
+| ../../_images/aws-resource.png | Macie Member Account Association | terraform | macieMemberAccountAssociation | accountResource |
+| ../../_images/aws-resource.png | Macie S3 Bucket Association | terraform | macieS3BucketAssociation | accountResource |
+| ../../_images/aws-vpc.png | Main Route Table Association | terraform | mainRouteTableAssociation | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-compute.png | Managed Application | terraform | ManagedApplication | accountResource |
+| ../../_images/azure-compute.png | Managed Disk | terraform | ManagedDisk | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-database.png | MariaDb Configuration | terraform | MariaDbConfiguration | accountResource |
+| ../../_images/azure-database.png | MariaDb Database | terraform | MariaDbDatabase | accountResource |
+| ../../_images/azure-database.png | MariaDb Firewall Rule | terraform | MariaDbFirewallRule | accountResource |
+| ../../_images/azure-database.png | MariaDb Server | terraform | MariaDbServer | accountResource |
+| ../../_images/azure-database.png | MariaDb Virtual Network Rule | terraform | MariaDbVirtualNetworkRule | accountResource |
+| ../../_images/azure-compute.png | Marketplace Agreement | terraform | MarketplaceAgreement | accountResource |
+| ../../_images/aws-resource.png | Media Convert Queue | terraform | mediaConvertQueue | accountResource |
+| ../../_images/aws-resource.png | Media Package Channel | terraform | mediaPackageChannel | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/aws-resource.png | Media Store Container | terraform | mediaStoreContainer | accountResource |
+| ../../_images/aws-resource.png | Media Store Container Policy | terraform | mediaStoreContainerPolicy | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/aws-mq.png | MQ Broker | cloudFormation | Broker | accountResource |
+| ../../_images/aws-mq.png | Mq Broker | terraform | mqBroker | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration | cloudFormation | Configuration | accountResource |
+| ../../_images/aws-mq.png | Mq Configuration | terraform | mqConfiguration | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration Association | cloudFormation | ConfigurationAssociation | accountResource |
+| ../../_images/azure-database.png | MS SQL Database | terraform | MSSQLDatabase | accountResource |
+| ../../_images/azure-database.png | MS SQL Elastic Pool | terraform | MSSQLElasticPool | accountResource |
+| ../../_images/azure-database.png | MS SQL Security Alert Policy | terraform | MSSQLSecurityAlertPolicy | accountResource |
+| ../../_images/azure-database.png | MS SQL Server | terraform | MSSQLServer | accountResource |
+| ../../_images/azure-database.png | MS SQL Vm | terraform | MSSQLVm | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment | terraform | MSSQLVulnerabilityAssessment | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment Rule Baseline | terraform | MSSQLVulnerabilityAssessmentRuleBaseline | accountResource |
+| ../../_images/aws-resource.png | Msk Cluster | terraform | mskCluster | accountResource |
+| ../../_images/aws-resource.png | Msk Configuration | terraform | mskConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Configuration | terraform | MySQLConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Database | terraform | MySQLDatabase | accountResource |
+| ../../_images/azure-database.png | MySQL Firewall Rule | terraform | MySQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | MySQL Server | terraform | MySQLServer | accountResource |
+| ../../_images/azure-database.png | MySQL Virtual Network Rule | terraform | MySQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-messaging.png | Namespace Authorization Rule | terraform | NamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Nat Gateway | terraform | NatGateway | accountResource |
+| ../../_images/aws-vpc.png | Nat Gateway | terraform | natGateway | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster | terraform | neptuneCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Instance | terraform | neptuneClusterInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Parameter Group | terraform | neptuneClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Snapshot | terraform | neptuneClusterSnapshot | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster Parameter Group | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Event Subscription | terraform | neptuneEventSubscription | accountResource |
+| ../../_images/aws-neptune.png | Neptune Parameter Group | terraform | neptuneParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Subnet Group | terraform | neptuneSubnetGroup | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Pool | terraform | NetAppPool | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/aws-vpc.png | Network Acl | terraform | networkAcl | accountResource |
+| ../../_images/aws-vpc.png | Network Acl Rule | terraform | networkAclRule | accountResource |
+| ../../_images/azure-network.png | Network DDos Protection Plan | terraform | NetworkDDosProtectionPlan | accountResource |
+| ../../_images/azure-network.png | Network Gateway | terraform | NetworkGateway | accountResource |
+| ../../_images/azure-network.png | Network Interface | terraform | NetworkInterface | accountResource |
+| ../../_images/aws-vpc.png | Network Interface | terraform | networkInterface | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Gateway Backend Address Pool Association | terraform | NetworkInterfaceApplicationGatewayBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Security Group Association | terraform | NetworkInterfaceApplicationSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Attachment | terraform | networkInterfaceAttachment | accountResource |
+| ../../_images/azure-network.png | Network Interface Backend Address Pool Association | terraform | NetworkInterfaceBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Nat Rule Association | terraform | NetworkInterfaceNatRuleAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Security Group Association | terraform | NetworkInterfaceSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Sg Attachment | terraform | networkInterfaceSgAttachment | accountResource |
+| ../../_images/azure-network.png | Network Packet Capture | terraform | NetworkPacketCapture | accountResource |
+| ../../_images/azure-network.png | Network Profile | terraform | NetworkProfile | accountResource |
+| ../../_images/azure-network.png | Network Security Group | terraform | NetworkSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Network Security Rule | terraform | NetworkSecurityRule | accountResource |
+| ../../_images/azure-network.png | Network Watcher | terraform | NetworkWatcher | accountResource |
+| ../../_images/azure-network.png | Network Watcher Flow Log | terraform | NetworkWatcherFlowLog | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub | terraform | NotificationHub | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Authorization Rule | terraform | NotificationHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Namespace | terraform | NotificationHubNamespace | accountResource |
+| ../../_images/aws-resource.png | Opsworks Application | terraform | opsworksApplication | accountResource |
+| ../../_images/aws-resource.png | Opsworks Custom Layer | terraform | opsworksCustomLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Ganglia Layer | terraform | opsworksGangliaLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Haproxy Layer | terraform | opsworksHaproxyLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Instance | terraform | opsworksInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Java App Layer | terraform | opsworksJavaAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Memcached Layer | terraform | opsworksMemcachedLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Mysql Layer | terraform | opsworksMysqlLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Nodejs App Layer | terraform | opsworksNodejsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Permission | terraform | opsworksPermission | accountResource |
+| ../../_images/aws-resource.png | Opsworks Php App Layer | terraform | opsworksPhpAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rails App Layer | terraform | opsworksRailsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rds Db Instance | terraform | opsworksRdsDbInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Stack | terraform | opsworksStack | accountResource |
+| ../../_images/aws-resource.png | Opsworks Static Web Layer | terraform | opsworksStaticWebLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks User Profile | terraform | opsworksUserProfile | accountResource |
+| ../../_images/aws-resource.png | Organizations Account | terraform | organizationsAccount | accountResource |
+| ../../_images/aws-resource.png | Organizations Organization | terraform | organizationsOrganization | accountResource |
+| ../../_images/aws-resource.png | Organizations Organizational Unit | terraform | organizationsOrganizationalUnit | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy | terraform | organizationsPolicy | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy Attachment | terraform | organizationsPolicyAttachment | accountResource |
+| ../../_images/azure-network.png | Packet Capture | terraform | PacketCapture | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Adm Channel | terraform | pinpointAdmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Channel | terraform | pinpointApnsChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Sandbox Channel | terraform | pinpointApnsSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Channel | terraform | pinpointApnsVoipChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Sandbox Channel | terraform | pinpointApnsVoipSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint App | terraform | pinpointApp | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Baidu Channel | terraform | pinpointBaiduChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Email Channel | terraform | pinpointEmailChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Event Stream | terraform | pinpointEventStream | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Gcm Channel | terraform | pinpointGcmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Sms Channel | terraform | pinpointSmsChannel | accountResource |
+| ../../_images/azure-compute.png | Placement Group | terraform | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | Placement Group | terraform | placementGroup | accountResource |
+| ../../_images/azure-network.png | Point To Site VPN Gateway | terraform | PointToSiteVPNGateway | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Configuration | terraform | PostgreSQLConfiguration | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Database | terraform | PostgreSQLDatabase | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Firewall Rule | terraform | PostgreSQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Server | terraform | PostgreSQLServer | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Virtual Network Rule | terraform | PostgreSQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-power-bi.png | PowerBI | terraform | PowerBI | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-network.png | Private Endpoint | terraform | PrivateEndpoint | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Proxy Protocol Policy | terraform | proxyProtocolPolicy | accountResource |
+| ../../_images/azure-network.png | Public IP | terraform | PublicIP | accountResource |
+| ../../_images/azure-network.png | Public IP Prefix | terraform | PublicIPPrefix | accountResource |
+| ../../_images/aws-resource.png | Qldb Ledger | terraform | qldbLedger | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight Group | terraform | quicksightGroup | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight User | terraform | quicksightUser | accountResource |
+| ../../_images/aws-resource.png | Ram Principal Association | terraform | ramPrincipalAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Association | terraform | ramResourceAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share | terraform | ramResourceShare | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share Accepter | terraform | ramResourceShareAccepter | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster | terraform | rdsCluster | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Endpoint | terraform | rdsClusterEndpoint | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Instance | terraform | rdsClusterInstance | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Parameter Group | terraform | rdsClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster ParameterGroup | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-rds.png | RDS DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group | cloudFormation | DBSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group Ingress | cloudFormation | DBSecurityGroupIngress | accountResource |
+| ../../_images/aws-rds.png | RDS DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | RDS Event Subscription | cloudFormation | EventSubscription | accountResource |
+| ../../_images/aws-rds.png | Rds Global Cluster | terraform | rdsGlobalCluster | accountResource |
+| ../../_images/aws-rds.png | RDS Option Group | cloudFormation | OptionGroup | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Redis Cache | terraform | RedisCache | accountResource |
+| ../../_images/azure-recovery.png | Redis Firewall Rule | terraform | RedisFirewallRule | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | terraform | redshiftCluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Parameter Group | cloudFormation | ClusterParameterGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group | cloudFormation | ClusterSecurityGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group Ingress | cloudFormation | ClusterSecurityGroupIngress | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Subnet Group | cloudFormation | ClusterSubnetGroup | accountResource |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json b/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
new file mode 100644
index 0000000..9a4a490
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+  "title": "Tenants",
+  "ordinal": 274,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md b/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
new file mode 100644
index 0000000..c2c0c72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
@@ -0,0 +1,9 @@
+# Tenants
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html)**
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html)**
+- **[Tenant Users](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html)**
+- **[Configuring Tenants and Resources for Multi-Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json b/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
new file mode 100644
index 0000000..ccf3f7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+  "title": "Cloud Access Levels",
+  "ordinal": 299,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Access Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md b/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
new file mode 100644
index 0000000..8a35df7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
@@ -0,0 +1,13 @@
+# Cloud Access Levels
+
+When creating or editing a Tenant Role, Master Tenant administrators can choose which publicly-visible Clouds to share with Tenants having the current Role. Access can be completely restricted or administrators can choose between Read and Full access.
+
+## Read Access
+
+Master Tenant administrators can opt to give other Tenants read-level access to any integrated Clouds through the Tenant Role. A read-only Cloud allows the Master Tenant to assign resources for viewing by Subtenant users but not allow them to perform any actions or provision new Instances.
+
+With read-level access, Subtenant users will have access to the Cloud detail page (Infrastructure > Clouds). From the Summary subtab on the Cloud detail page, high-level information on Cloud resources are shown regardless of specific resources that have been shared with the Subtenant. Other metrics, such as costing, resource percentages (CPU, Memory, and Storage), VM counts and host counts will only be populated when servers in the Cloud have been assigned to the Tenant.
+
+## Full Access
+
+With full access, Subtenant users also have access to the Cloud detail page (Infrastructure > Clouds > Specific Cloud) and see the same level of detail as Subtenants with read-only rights. However, with full access, Subtenant users can also perform many actions including the addition of Clusters, Hosts, and VMs, changing networks, and more. This cloud will also be selectable as a provisioning target for Subtenant users when deploying Instances or Apps.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json b/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
new file mode 100644
index 0000000..e146c41
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+  "title": "Image Management",
+  "ordinal": 405,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html",
+  "topic_cluster": {
+    "clustering_title": "Image Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md b/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
new file mode 100644
index 0000000..89986eb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
@@ -0,0 +1,7 @@
+# Image Management
+
+The topic describes about image catalog and uploading various images.
+
+**Subtopics**  
+
+- **[Image Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json b/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
new file mode 100644
index 0000000..110e7cb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+  "title": "Mapping",
+  "ordinal": 250,
+  "parent_title": "Boot",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Mapping",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md b/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
new file mode 100644
index 0000000..fd59117
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
@@ -0,0 +1,51 @@
+# Mapping
+
+## Add Mapping
+
+### Procedure
+
+1. Select the Mapping tab then click the Add Mapping button.
+2. From the New Mapping Wizard input the following information: 
+
+   Match Pattern
+   :   Mac address separated by ‘:’ or an ip address filter
+
+   Description(optional)
+   :   Description of the new mapping.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Operating System
+   :   List of operating systems for the mapping.
+
+   Boot Image
+   :   Lists available PXE boot images.
+
+   Answer File
+   :   Lists available answer files.
+
+   Cloud
+   :   Lists the available clouds.
+
+   Server Mode
+   :   List of server modes:: unmanaged, Managed, Bare metal host, Container host, VM host, and Container & VM host.
+3. Save
+
+### Results
+
+Once the mapping is added, and the target host is powered on, the {morpheus} PXE menu will load and PXE boot will start.
+
+## Edit Mapping
+
+### Procedure
+
+1. Click the edit icon on the row of the mapping you wish to edit.
+2. Modify information as needed.
+3. Click the Save Changes button to save.
+
+### Results
+
+Delete Mapping
+
+1. Click the delete icon on the row of the mapping you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json b/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
new file mode 100644
index 0000000..507f2a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+  "title": "Managed Networks",
+  "ordinal": 431,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html",
+  "topic_cluster": {
+    "clustering_title": "Managed Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md b/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
new file mode 100644
index 0000000..b14607f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
@@ -0,0 +1,13 @@
+# Managed Networks
+
+The managed network mode is used when the network infrastructure is to be managed by Morpheus. In this case, the user can select ArubCX-Int during the cloud creation.
+
+## Adding HPE ArubaCX Plugin
+
+In the managed network mode, the Aruba CX switches are supported as managed switches. To enable that, the ArubaCX plugin needs to be loaded.
+
+You can load the ArubaCX plugin jar using the Administration > Integrations.
+
+**Subtopics**  
+
+- **[Creating ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..1fd659d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 53,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..bf9d43a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,12 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2277183A-E315-4439-A885-C111A77C7154.html)**
+- **[Reports](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html)**
+- **[Analytics](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html)**
+- **[Costing](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html)**
+- **[Approvals](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json b/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
new file mode 100644
index 0000000..41b47cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+  "title": "Whitelabel",
+  "ordinal": 323,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html",
+  "topic_cluster": {
+    "clustering_title": "Whitelabel",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md b/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
new file mode 100644
index 0000000..4b31d70
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
@@ -0,0 +1,114 @@
+# Whitelabel
+
+## Whitelabel Settings
+
+### Overview
+
+HPE Morpheus Enterprise Tenants can be WhiteLabeled with custom Logos, Colors, Copy, and custom CSS. Sub-Tenants can be individually white-labeled, or the Master Tenant Whitelabel can apply to all Sub-Tenants.
+
+Enable Whitelabel
+:   Turns on the configured Whitelabel settings. Disabling will return the Appliance to the default colors and logos, but the configured options will remain saved and will apply if Whitelabel is re-enabled.
+
+Appliance Name
+:   Replaces HPE Morpheus Enterprise in page titles.
+
+Header Logo
+:   Top left header logo. Uploaded image is resized to 38 pixels high with a proportional width at that height.
+
+Disable Support Menu
+:   Enable this flag to hide the support dropdown menu in the header.
+
+Support Menu Links
+:   Customize support links. Label Code can be used for translations and is optional. Be sure to specify fully qualified url if linking to external sites.
+
+Security Banner
+:   The Security Banner section in `/admin/settings#!whitelabel` displays content on the login screen for Security and Consent messaging and warnings.
+    :   - Applicable at Global and Tenant levels
+        - Security Banner input field accepts plain text and markdown
+        - Content is displayed below login section in scoped `/login/auth` pages.
+
+Footer Logo
+:   Footer Logo in bottom left. Uploaded image is resized to 27 pixels high with a proportional width at that height.
+
+Login Logo
+:   Logo shown on Login screen. Uploaded image is resized to 192 pixels wide with an unbound height proportional to that locked width.
+
+Favicon
+:   Must be a .ico file type.
+
+Reset
+:   When selected and Whitelabel settings are saved, associated logo is returned to blank default value.
+
+### Colors
+
+Update Colors by entering HEX value or selecting the Color Selector pop-up next to each filed and selecting a color.
+
+- Header Background
+- Header Foreground
+- Nav Background
+- Nav Foreground
+- Nav Hover
+- Primary Button Bg
+- Primary Button Fg
+- Primary Button Hover Bg
+- Primary Button Hover Fg
+- Footer Background
+- Footer Foreground
+- Login Background
+
+### Override CSS
+
+Override CSS settings by entering CSS in Override CSS field.
+
+Example: (this will add one continues background image to the Header)
+
+```
+```
+header #topHeader {  
+        background-image: url(http://image_url.png);  
+        }  
+header {  
+        background-image: url(http://image_url.png);  
+        }
+```
+```
+
+### Copy
+
+Add custom Copyright String, Terms of Use, Privacy Policy contained in the Footer text and links in the App and on the login page and emails.
+
+Available Copy fields
+
+- Copyright String
+- Terms and Privacy String
+- Terms of Use
+- Privacy Policy
+
+  NOTE
+
+  Terms of Use and Privacy Policy Footer links will load internal pages at `https://applaince_url/privacy-policy` and `https://applaince_url/terms-of-use` displaying the entered info as plain text. The Terms and Privacy String will update the legal text displayed on the HPE Morpheus Enterprise login page. This field takes any custom HTML markup allowing you to link to the internal legal pages or to your own outside legal pages if you prefer.
+
+### ​UI Loading Page
+
+When the HPE Morpheus Enterprise UI is restarted or loading, a default “Morpheus is Loading” page is displayed. This page can be changed by adding the following to `/etc/morpheus/morpheus.rb` and adjusting the values.
+
+NOTE
+
+`morpheus-ctl reconfigure` must be ran for any chnages to `/etc/morpheus/morpheus.rb` to take effect.
+
+```
+```
+nginx['web_root_internal'] = "/opt/morpheus/embedded/nginx/html"  
+nginx['loading_pages']['max_loops'] = 6 * 10 # 10 secs per loop x 6 times to get 60 seconds * 10 to get to 10 minutes  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['iteration_time'] = 10_000  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json b/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
new file mode 100644
index 0000000..cbf8b29
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+  "title": "Monitoring the Cluster",
+  "ordinal": 208,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md b/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
new file mode 100644
index 0000000..916ba43
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
@@ -0,0 +1,20 @@
+# Monitoring the Cluster
+
+After onboarding the cluster into HPE Morpheus Enterprise, a new Cluster object is added to the Clusters list page. Clicking into the Cluster reveals the Cluster detail page. Note the following subtabs and the cluster details we can monitor in each:
+
+- **Nodes:** Master and worker nodes making up the cluster are shown here. Click into any of them to see a node detail page
+- **VMs:** A list of all virtual machines within the scope of the OpenShift cluster are shown. When creating or editing the cluster, an option is given to inventory all existing instances. If selected, all running virtual machines will be onboarded and shown here even if they were provisioned outside of HPE Morpheus Enterprise. If this option is not selected, then only the OpenShift virtual machines provisioned through HPE Morpheus Enterprise are shown. High level details about each virtual machine are also shown, such as power state and resource usage. Click into any virtual machine to see a detail page with additional options
+- **Virtual Images:** A list of virtual images synced to HPE Morpheus Enterprise is shown. Only custom user images are synced, images which are part of the large OpenShift default catalog are not synced. Click into any virtual image to see a detail page and to edit configurations for any images, if necessary
+
+  IMPORTANT
+
+  Virtual Images used for provisioning OpenShift workloads from HPE Morpheus Enterprise must be updated to set appropriate properties prior to use. Edit the Virtual Image to uncheck the "Install Agent?" configuration and check either "Is Cloud Init Enabled?" or "Sysprepped/Generalized Image" depending on the workload-type. Ensure the OpenShift template has VirtIO drivers and QEMU VM agent tools installed. For Windows images, only the "Sysprepped/Generalized Image" option is currently supported. Do not use the Cloudbase-init option until support is added. For Linux-based images, HPE Morpheus Enterprise expects standardized NIC names (eth0, eth1, etc) on templates so that cloud-init can reliably apply network configuration. For Windows templates, HPE Morpheus Enterprise relies on OpenShift standard interface naming (ex. Ethernet Instance 0) in templates. Currently on Windows Instances, configuration of the first network interface is supported as part of deployment via Sysprep.
+- **Networks:** NetworkAttachmentDefinitions (NADs) define virtual network interfaces that can be attached to VMs, acting as network bridges
+
+IMPORTANT
+
+Edit and update synced network objects (OpenShift NADs) in HPE Morpheus Enterprise with appropriate IPv4/IPv6 configuration details (DHCP, Gateway, DNS, Subnet, etc.)
+
+TIP
+
+IP Pools can be associated with the network definitions synced from OpenShift. These can be Morpheus-type IP Pools created within the HPE Morpheus Enterprise UI or can be IP Pools sourced from IPAM integrations. If IP Pools are used, HPE Morpheus Enterprise can manage IP addresses across the Instance lifecycle (claim a free address at provision time, release an address at teardown, etc)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json b/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
new file mode 100644
index 0000000..b028c51
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+  "title": "Agent Installation",
+  "ordinal": 46,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md b/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
new file mode 100644
index 0000000..d163a4e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
@@ -0,0 +1,185 @@
+# Agent Installation
+
+There are many methods to install the HPE Morpheus Enterprise Agent on supported targets. All Agent installation methods are executing a script on the target that calls back to the HPE Morpheus Enterprise appliance over port 443.
+
+IMPORTANT
+
+All Agent installation methods require the Target (VM or Host) to resolve and reach the appliance URL over port 443. In addition to the main Appliance URL (in Administration > Settings), additional Appliance URLs can be set per cloud in the Advanced Options section of the Create/Edit Cloud modal. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+## Basic Installation Steps
+
+### Procedure
+
+1. An Agent installation method is used to get the install script onto the target VM or Host
+2. The Agent installation script is executed on the target VM or Host, installing the Agent and all dependencies
+3. The Agent is started and makes a websocket connection to the configured Appliance URL over port 443 using the target VM or Host API key
+
+### Results
+
+It is important to note these are three separate steps with varying requirements. The first requires a path to get the script on the target. The second requires successful execution of the Agent installation script. The third requires a successful websocket connection. Requirements for the successful execution of each step are covered in the sections below.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Modes
+
+Agent Installation Method is determined by:
+
+- The AGENT INSTALL MODE setting on target Cloud: - SSH / WinRM / Guest Execution - Cloud Init / Unattend (when available)
+- Platform / OS type on Virtual Image or target (VM or Host)
+- Virtual Image configuration
+- RPC Mode setting (VMware Clouds only)
+
+## Agent Installation Methods
+
+The Morpheus Agent can be installed with a variety of automated methods. It is important to note these methods simply get the Agent install script to the target. Successful execution of the Agent install script is not directly related to the Agent install method.
+
+SSH
+:   HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+    `curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+WinRM
+:   HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+VMware Tools
+:   HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+Cloud-Init
+:   HPE Morpheus Enterprise executes agentInstall.sh via cloud-init runcmd
+
+Cloudbase-Init
+:   HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+Windows Unattend
+:   HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+Manual
+:   User executes agentInstall.sh or agentInstall.ps1 manually on the VM or Host. These scripts can be obtained on the VM or Host detail page via Actions > DownloadAgent Script
+
+### SSH
+
+#### Process
+
+HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+`curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+#### Requirements
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+#### Process
+
+HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+#### Requirements
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install
+
+### VMware Tools
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+#### Requirements
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init, Guest Customizations, or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install.
+
+### Cloud-Init
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh via Cloud-Init runcmd
+
+#### Requirements
+
+- Cloud-Init is installed on Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Cloud-Init User is configured in the Administration > Settings > Provisioning section
+
+### Cloudbase-init
+
+#### Process
+
+HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+#### Requirements
+
+- Cloudbase-Init is installed on the Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Windows Administrator password defined in the Administration > Settings > Provisioning section
+
+### Windows Unattend
+
+#### Process
+
+HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+#### Requirements
+
+VMware
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “FORCE GUEST CUSTOMIZATION?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record when using DHCP
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+Nutainx/SCVMM/Openstack
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “ENABLED SYSPREP?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+### Manual
+
+#### Process
+
+- From the VM or Host record page (`/infrastructure/servers/${id}`) run ACTIONS > `Download Agent Script`
+- This is will generate an Agent install script based off the target OS and platform, Appliance URL, and API key
+- Manually execute the downloaded script on the Target VM or Host
+
+## Agent Install Requirements
+
+Table 1.
+
+          |  |  |  |  |  |  |  |  |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Agent Installation Requirements | | | | | | | |
+| Requirement | Agent Installation Method | | | | | | |
+| SSH | WINRM | VMWARE TOOLS | CLOUD‐INIT | CLOUDBASE‐INIT | UNATTEND | MANUAL |
+| Target (vm/host) to resolve and reach Appliance URL over 443 | YES | YES | YES | YES | YES | YES | YES |
+| Target (vm/host) to resolve and reach Appliance URL over 80 | Ubuntu 14.04 Only |  | Ubuntu 14.04 Only | Ubuntu 14.04 Only |  |  | Ubuntu 14.04 Only |
+| Websockets enabled when using load balancer | YES | YES | YES | YES | YES | YES | YES |
+| Access to Target VM/Host on port 22 | YES | NO | NO | NO | NO | NO | NO |
+| Access to Target VM/Host on port 5985 | NO | YES | NO | NO | NO | NO | NO |
+| Vmware Tools installed and flagged on Virtual Image | NO | NO | YES | NO | NO | YES | NO |
+| Syspreped Image and Sysprep Enabled flagged on Virtual Image (Nutanix, Openstack, SCVMM) | NO | NO | NO | NO | NO | YES | NO |
+| Force Guest Customizations flagged on Virtual Image | NO | NO | DHCP | NO | NO | DHCP | NO |
+| Cloud‐Init installed and flagged on Virtual Image | NO | NO | NO | YES | YES | NO | NO |
+| Global Cloud‐Init user populated in Administration > Settings > Provisioning | NO | NO | NO | YES | NO | NO | NO |
+| Windows Administrator Password populated in Administration > Settings > Provisioning | NO | NO | NO | NO | YES | YES | NO |
+| Access to configured YUM or APT repos | NO but will cause delay in Agent Install | N/A | NO but will cause delay in Agent Install | NO but will cause delay in Agent Install | N/A | N/A | NO but will cause delay in Agent Install |
+| .net >=4.5.2 (Windows, Morpheus >= 4.1.2) | N/A | YES | YES | N/A | YES | YES | YES |
+| User with Sudo Access set on Virtual Image (Greenfield) | YES | N/A | YES | NO | N/A | N/A | N/A |
+| Administrator User (SID 500) set on Virtual Image (Greenfield) | N/A | YES | YES | N/A | NO | N/A | N/A |
+| User with Sudo Access set on VM/Host Record (Brownfield) | YES | N/A | YES | N/A | N/A | N/A | N/A |
+| Administrator User (SID 500) set on VM/Host Record (Brownfield) | N/A | YES | YES | N/A | N/A | N/A | N/A |
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../../../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json b/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
new file mode 100644
index 0000000..442d8b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+  "title": "Creating an Option List Based on an LDAP Query",
+  "ordinal": 157,
+  "parent_title": "Options",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Option List Based on an LDAP Query",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md b/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
new file mode 100644
index 0000000..af98f68
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
@@ -0,0 +1,51 @@
+# Creating an Option List Based on an LDAP Query
+
+## About this task
+
+In Morpheus version 4.2.1 and higher, Option Lists can be populated from LDAP queries. This gives users the ability to search Active Directory, capture objects, and present them as custom options where needed.
+
+It’s recommended that you connect LDAP-type Option Lists to Typeahead-type Inputs as the list of returned selections can be very large. This also allows you to select multiple options from the list, presuming you’ve allowed for that when creating the Input.
+
+Populating LDAP-type Option Lists requires knowledge of LDAP query syntax. This guide provides one example and there are many publicly-available resources for help writing additional queries.
+
+## Procedure
+
+1. Create a new Option List (Library > Options > Option Lists > ADD)
+2. Enter a name for the new LDAP Option List
+3. Change the Type value to LDAP and the relevant fields will appear as shown in the screenshot:
+4. Enter the LDAP URL in the following format (an example is also shown as a placeholder in the UI form field): 
+
+   ```
+   ```
+   ldap[s]://<hostname>:<port>/<base_dn>
+   ```
+   ```
+5. Enter the fully qualified username with @ suffix syntax, such as: user@ad.mycompany.com
+6. Enter the account password
+7. Enter your LDAP query. You can even inject variables into your query structure to query based on the value the user has entered into the typeahead field as shown in the example below: 
+
+   ```
+   ```
+   (&(objectClass=user)(cn=<%=phrase%>*))
+   ```
+   ```
+8. Finally, enter a translation script which will convert the returned LDAP object into a list of name:value pairs you can work with in Morpheus. The example script below shows the user DisplayName and sets the value to the SAMAccountName: 
+
+   ```
+   ```
+   for(var x=0;x < data.length ; x++) {  
+     var row = data[x];  
+     var a = {};  
+     if(row.displayName != null) {  
+       a['name'] = row.displayName;  
+     } else {  
+       a['name'] = row.sAMAccountName;  
+     }  
+     a['value'] = row.sAMAccountName;  
+     results.push(a);  
+   }
+   ```
+   ```
+9. Click SAVE CHANGES 
+
+   ![../../_images/ldap_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F3A370B1-BB00-4177-8AF4-D6E5A2975918-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json b/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
new file mode 100644
index 0000000..cdb3e0a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+  "title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 364,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md b/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
new file mode 100644
index 0000000..a368ace
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
@@ -0,0 +1,358 @@
+# Automated Single-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. In this guide, we will create a custom Instance Type for SuiteCRM which can then be selected during provisioning. Once configured, the provisioning process is completely automated and results in SuiteCRM and a database installed on a single node. There is also an accompanying guide which automates the process for deployed SuiteCRM as a multi-tiered application consisting of a MySQL database on one node and the SuiteCRM application on a second node.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a single-node application:
+
+- Instance Types
+- Layouts
+- Node Types
+- Cypher
+- Archive
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. This could be used to create a provisionable Instance Type on any HPE Morpheus Enterprise-supported Cloud type and it’s intentionally left open-ended to be useful for any environment. As I’m building the example, I’ll show screenshots targeting a build for VMware vCenter Clouds. Despite the screenshots, this guide is useful for any environment.
+
+## Create a HPE Morpheus Enterprise Archive for Install Files
+
+HPE Morpheus Enterprise Archives allow you to store files which can then be made available for download in scripts or by users. Archives are backed by buckets or file shares which must exist prior to creating the Archive. Buckets could be backed by Amazon S3, for example. File Shares could be backed by an NFS file share or even point directly to a local folder on the appliance itself. In this example, we’ll use an S3-backed bucket. With an Amazon AWS Cloud already integrated with HPE Morpheus Enterprise, we can even create the S3 bucket itself without leaving HPE Morpheus Enterprise UI.
+
+To create a new bucket, navigate to Infrastructure > Storage. From the Buckets tab, click + ADD and then select “AWS S3 Bucket”. The example bucket configuration is shown below. Bear in mind if you make any changes you may need to carefully confirm Task configurations and calls to Cypher or Archive to ensure they match any changes you’ve made.
+
+- **NAME:** Automation Training S3 Bucket (this is simply a friendly name for the bucket within HPE Morpheus Enterprise)
+- **Storage Service:** Select your pre-existing AWS Cloud
+- **BUCKET NAME:** Enter a unique name for the bucket (this much conform to AWS bucket naming rules, consult AWS documentation if needed)
+- **CREATE BUCKET:** Checked
+- **REGION:** The AWS region to create the bucket in
+- **ACTIVE:** Checked (this makes it available for use in HPE Morpheus Enterprise)
+
+![../../_images/newBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F1FDC927-C674-4E43-A0EC-C9347212EEC5-high.png)
+
+With the bucket created, we can now create the Archive. Start by going to Tools > Archives and clicking + ADD. In the new Archive, we need to configure the following:
+
+- **NAME:** Software Archive
+- **BUCKET:** Select the bucket we just created
+- **PUBLIC URL:** Checked (this automatically creates a public download URL when files are added to the Archive)
+
+NOTE
+
+If you don’t name your Archive “Software Archive” as indicated here, you will have to make manual changes to Task config later in this guide.
+
+At this point, you should go ahead and download the installation ZIP file for SuiteCRM. You can access version 7.14.3 [here](https://github.com/salesagility/SuiteCRM/releases). This guide is designed for version 7.14.3. If you opt to download a different version please note that changes might be needed to the automation scripts to account for any changes to the installation or configuration processes for that version.
+
+Click on the newly created Archive and note there are no files contained in it. Under the Files tab, click + ADD. Slide the installation ZIP file onto the modal and wait for the file to be successfully uploaded. Click DONE. We’ve now added the installation ZIP file and it is visible in the list of files on the Files tab.
+
+Click on the name of the newly added file to access the File detail page. While here, click on the Scripts tab and you’ll see syntax examples for how this and other files might be accessed in your automation scripts. You’ll see this syntax used later in this example as we access the ZIP file directly from this Archive and automate the installation process. Generated links can be viewed from the Links tab and a record of it will be visible on the History tab.
+
+![../../_images/fileDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the MariaDB root user password as a Cypher entry. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here’s we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dba/mariadb\_root
+- **VALUE:** Password123?
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/cypherMaria.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-9196BD2B-DED5-4018-891A-19D5BCE27DA4-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** SuiteCRM DB Name (The name for the Input object in HPE Morpheus Enterprise)
+- **LABEL:** SUITECRM (Labels are a categorizing feature in HPE Morpheus Enterprise)
+- **FIELD NAME:** databaseNameSCRM (The internal property which the input value is assigned to)
+- **SHOW ON EDIT:** Checked (By checking this box, we can view this Input value when editing the Instance after provisioning)
+- **DISPLAY VALUE ON DETAILS:** Checked (By checking this box, we will see the value of this Input on the detail page for the provsioned Instance)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** SuiteCRM DB Name (The label the user will see next to the field at provsion time)
+- **REQUIRED:** Checked (By checking this box, the Input will be required at provision time)
+
+### Database Name Input
+
+![../../_images/dbNameInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C19EB913-4A34-4D5D-A85A-C0620C2BDFCF-high.png)
+
+Click SAVE CHANGES. Then, create two additional Inputs:
+
+- **NAME:** SuiteCRM DB User
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databaseUserSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Text
+- **LABEL:** SuiteCRM DB User
+- **REQUIRED:** Checked
+
+### Database Username Input
+
+![../../_images/dbUserInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CFB7E6DB-864A-4995-B1EB-A77E2D08ABA9-high.png)
+
+- **NAME:** SuiteCRM DB Password
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databasePassSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Password (Password type Inputs are masked on screen when entered by the user)
+- **LABEL:** SuiteCRM DB Password
+- **REQUIRED:** Checked
+
+### Database Password Input
+
+![../../_images/dbPassInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-35947404-36DD-48AC-A3FF-2E57EE6B68FF-high.png)
+
+## Create File Templates
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. Navigate to Library > Templates > File Templates and click + ADD. Enter the following:
+
+- **NAME:** suitecrm - conf
+- **LABELS:** SUITECRM
+- **FILE NAME:** suitecrm.conf
+- **FILE PATH:** /etc/apache2/sites-available
+- **PHASE:** Provision
+- **TEMPLATE:** See below for the complete template, note how we’re able to dynamically resolve HPE Morpheus Enterprise variables within the template
+- **FILE OWNER:** root
+- **SETTING NAME:** suitecrm
+- **SETTING CATEGORY:** App
+
+```
+```
+<VirtualHost *:80>  
+   ServerAdmin admin@localhost  
+   ServerAlias "<%=server.externalIp%>"  
+   DocumentRoot /var/www/html/suitecrm  
+   <Directory /var/www/html/suitecrm/>  
+        Options FollowSymlinks  
+        AllowOverride All  
+        Require all granted  
+   </Directory>  
+   ErrorLog ${APACHE_LOG_DIR}/error.log  
+   CustomLog ${APACHE_LOG_DIR}/access.log combined  
+   <Directory /var/www/html/suitecrm/>  
+          RewriteEngine on  
+          RewriteBase /  
+          RewriteCond %{REQUEST_FILENAME} !-f  
+          RewriteRule ^(.*) index.php [PT,L]  
+  </Directory>  
+</VirtualHost>
+```
+```
+
+![../../_images/filetemplate.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-58E7A9A8-1822-4B60-9860-CA3DFDD3870B-high.png)
+
+## Create Tasks
+
+At this point, we need to create three automation Tasks. One will set the Apache config file we just created, another will be a Bash script Task to actually install and configure SuiteCRM on the box, and the third will be another Bash script Task which will restart the Apache service.
+
+To create a Library Template Task, navigate to Library > Automation > Tasks. Click + ADD. Enter the following:
+
+- **NAME:** suitecrm file template
+- **CODE:** suitecrmfiletemplate
+- **LABELS:** SUITECRM
+- **TYPE:** Library Template (The proper fields will appear once the Type is set)
+- **TEMPLATE:** suitecrm - conf (Select the File Template we already created from this dropdown menu)
+- **EXECUTE TARGET:** Resource
+
+![../../_images/libtemtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3ADB5F3A-1E18-46BD-9DF2-4D467460BEB6-high.png)
+
+Now create the first Bash Task which will install and configure SuiteCRM on a newly-provisioned box:
+
+- **NAME:** suitecrm - single node
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **CONTENT:** Expand the section below to see the script content. Note how Cypher secrets and custom option (Input) values are invoked in this script
+- **EXECUTE TARGET:** Resource
+
+### Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/dba/mariadb_root')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+PHP_VERSION="8.1"  
+MARIADB_VERSION="mariadb-10.11"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+    sleep 120  
+fi  
+#Install apache, start service and enable on boot  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Install MariaDB, start service and enable on boot  
+curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | \  
+sudo bash -s ----mariadb-server-version="$MARIADB_VERSION"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enablemariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -e "ALTER USER 'root'@'localhost' IDENTIFIED BY '$RPass';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='root' \  
+AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass-e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.db WHERE Db='test' \  
+OR Db='test\_%';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+#Create the SuiteCRM User  
+mysql -u root -p$RPass-e "CREATE User '$SCRMUser'@'localhost' \  
+IDENTIFIED BY '$SCRMPass';"  
+#Create the SuiteCRM database  
+mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO \  
+$SCRMUser@localhost IDENTIFIED BY '$SCRMPass';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php$PHP_VERSIONlibapache2-mod-php$PHP_VERSION \  
+php$PHP_VERSION-common php$PHP_VERSION-mysql php$PHP_VERSION-gmp \  
+php$PHP_VERSION-curl php$PHP_VERSION-intl php$PHP_VERSION-mbstring \  
+php$PHP_VERSION-xmlrpc php$PHP_VERSION-gd php$PHP_VERSION-bcmath \  
+php$PHP_VERSION-imap php$PHP_VERSION-xml php$PHP_VERSION-cli \  
+php$PHP_VERSION-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+  sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" \  
+/etc/php/$PHP_VERSION/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+file_url="<%= archives.link('Software Archive', 'SuiteCRM-7.14.3.zip',1200) %>"  
+wget $file_url-O "./SuiteCRM-7.14.3.zip"--no-check-certificate  
+apt-get install unzip -y  
+unzip SuiteCRM-7.14.3.zip -d /var/www/html  
+mv /var/www/html/SuiteCRM-7.14.3/ /var/www/html/suitecrm  
+cd/var/www/html/suitecrm  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/installtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E9CE3244-8398-46FB-B6BD-70FBB18B51D8-high.png)
+
+Finally, we’ll add the Apache restart Task. Configure a new Task as shown below:
+
+- **NAME:** suitecrm apache restart
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local
+- **CONTENT:** Expand the section below to see the script content
+- **EXECUTE TARGET:** Resource
+
+### Restart Task Content
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/restarttask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B205F51E-1A3C-4DEB-8FA7-7E59213395B6-high.png)
+
+## Create the Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provisioning phase so that SuiteCRM will be installed, the Apache config file will be set, and the Apache service will be restarted automatically when the Instance is provisioned.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRM - single node
+- **LABELS:** SUITECRM
+- **PLATFORM:** Linux
+- **TASKS:** Expand the Provision section and begin typing the names of our Tasks in the Search field. After adding them, they can be reordered but they should be set such that the install script is run first, the file template is set second, and the Apache restart is run last
+
+Click SAVE CHANGES
+
+![../../_images/provworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4CD1EFEA-943C-40B9-AC3E-7431042CBD21-high.png)
+
+## Create a Custom Library Item
+
+Having created Cypher entries, Inputs, and Tasks, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. We’ll create a new SuiteCRM Library entry that will be available to some or all users (depending on Role permissions) in the provisioning wizard. This will allow them to stand up single node SuiteCRM appliances with just a few clicks. In HPE Morpheus Enterprise there are three layers to such Library items: Instance Types, Layouts, and Node Types. We’ll create the Instance Type first:
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** Custom SuiteCRM
+- **CODE:** custSuiteCRM
+- **CATEGORY:** Apps
+- **LABELS:** SUITECRM
+- **ICON:** If desired, search the file system on your local computer for a SuiteCRM logo icon for easier identification of this Instance Type at provision time
+
+![../../_images/instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0E99A5BF-3532-4F17-94B0-F80D1F98A54F-high.png)
+
+Click SAVE CHANGES. After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** SuiteCRM - Single Node
+- **VERSION:** 7.14.3
+- **LABELS:** SUITECRM
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **MINIMUM MEMORY:** 2048 (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **WORKFLOW:** Select the Workflow we’ve already created, “SuiteCRM - single node”
+- **INPUTS:** Search and find the three custom Inputs we created earlier
+
+![../../_images/layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-87B329F6-4D66-4D7C-8D9B-65796365436F-high.png)
+
+Once the configurations are entered, click SAVE CHANGES. After creating the Layout, we need to associate a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. Node Types are compute images and will be relevant types for the destination Cloud technology (AMIs for provisioning on AWS or VMware virtual images for vCenter Clouds, etc.) In this case, we’re simply going to point to a default Ubuntu image in an appropriate format which is supplied by HPE Morpheus Enterprise. You can associate Node Types with your own custom virtual images as well when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** Custom Ubuntu 22.04 Node
+- **SHORT NAME:** ubuntu2204
+- **VERSION:** 22.04
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **VM IMAGE:** Select the included Ubuntu 18.04 image
+
+Click SAVE CHANGES
+
+![../../_images/nodetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-851F39FE-55AA-4EE3-85A8-94FD5E6ADA2C-high.png)
+
+## Provision the SuiteCRM Instance Type
+
+At this point, the setup is finished and SuiteCRM will be available as an Instance Type option for your users. We’ll go ahead and walk through the provisioning process at this point just to take a look.
+
+To begin provisioning, navigate to Provisioning > Instances and click + ADD. From the list of Instance Types, select the “SUITE\_CRM” Instance Type we just created, click NEXT. From the Group tab, select a Group which contains a destination Cloud relevant to the Instance configuration and then select the Cloud you’d like to provision the app onto. Click NEXT. From the Configuration Tab, select the Layout we created and configure a plan, Resource Pool, and network which makes sense for your environment and the compute needs of the workload. You’ll then notice the Input fields we created where you’ll need to enter a SuiteCRM database name, Username, and Password. Click NEXT. On the Automation tab, we do not need to select a Workflow as our Workflow is already set on the Layout. Click NEXT and click COMPLETE.
+
+![../../_images/provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-43E0CE55-E46C-408F-AA4F-F0320E933520-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_INSTANCE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json b/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
new file mode 100644
index 0000000..5ea4dd8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+  "title": "Capacity and Planning",
+  "ordinal": 13,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity and Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md b/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
new file mode 100644
index 0000000..76dd551
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
@@ -0,0 +1,33 @@
+# Capacity and Planning
+
+There are many different architectures HPE Morpheus Enterprise can be deployed as. However, the most common architectures are an All-In-One (AIO) single node and a 3-Node Highly Available (HA) cluster. These architectures can have many variables to determine the capacity of each node, as each users’ environment will be different. Example factors that determine the capacity are:
+
+- Number of virtual machines (VMs)/systems/instances that HPE Morpheus Enterprise will manage, also know as Workload Elements (WLEs)
+- If the WLEs will have agents installed
+- The number of clouds added to HPE Morpheus Enterprise
+- The technologies used, such as: Kubernetes, Terraform, ARM, etc.
+- The number of concurrent worflows
+- Number of active users
+
+Although there are many factors that can contribute to the capacity planning, even outside the list above, below are recommended initial specifications.
+
+Table 1. Recommendations
+
+        | Architecture | # of CPUs per node | Memory (GB) per node | Local Storage (GB) per node | Shared Storage (NFS) | Supported WLEs |
+| --- | --- | --- | --- | --- | --- |
+| AIO | 4 | 16 | 200 | N/A | 5,000 |
+| AIO | 4 | 32 | 400 | N/A | 10,000 |
+| 3‐Node HA | 4 | 16 | 400 | 50 | 10,000 |
+| 3‐Node HA | 8 | 32 | 400 | 50 | 20,000 |
+
+In the above recommendations, an AIO can support ~5,000 WLEs with agents installed at the base requirements. Due to ease of installation and maintenance, an AIO architecture should be strongly considered for environments that will manage less than a few thousand WLEs. Consider the significantly increased complexity of multi-node architectures and opt for an AIO appliance unless there is a specific compelling reason (such as high capacity needs or a zero downtime requirement) to select anything else. However, the AIO architecture cannot tolerate failure and will be unavailable during upgrades, unlike the 3-Node HA, which is the likely choice for ensuring zero downtime upgrades and high availability. A 3-Node HA architecture could support ~15,000 WLEs with agents installed (3 x 5,000) at the base requirements but it is best to consider the possible loss of a node, which would be an effective support of ~10,000 WLEs with agents installed (2 x 5,000).
+
+In the case of both the AIO and 3-Node HA architectures, HPE Morpheus Enterprise nodes can be **scaled up** to a maximum of 32GB of memory, which can support more WLEs per node. Adding more CPU or memory is possible, without adding additional nodes. Also, in the case of the 3-Node HA architecture, HPE Morpheus Enterprise can be **scaled out**, which can support additional WLEs per node added and provides additional redundancy, whereas the AIO configuration cannot add additional nodes. The 3-Node HA architecture should always have an odd number of nodes for quorum.
+
+IMPORTANT
+
+Customer architectures and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment, which can help right-size the environment
+
+Additional information around the various architectures can be found here:
+
+[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html) [HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json b/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
new file mode 100644
index 0000000..20f6b55
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+  "title": "Azure Active Directory SSO (SAML)",
+  "ordinal": 283,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Active Directory SSO (SAML)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md b/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
new file mode 100644
index 0000000..f55cc8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
@@ -0,0 +1,204 @@
+# Azure Active Directory SSO (SAML)
+
+Azure Active Directory Single Sign-on can be added as a Identity Source in HPE Morpheus Enterprise using the SAML Identity Source Type. The Azure AD SSO configuration is slightly different than other SAML providers, and this guide will assist in adding a Azure AD SSO Identity Source.
+
+## Create Azure Enterprise Application
+
+### Procedure
+
+1. Login to the [Azure Portal](https://portal.azure.com)
+2. Navigate to: Azure Active Directory  >  Enterprise Applications
+3. Click the `+ New application` button at the top
+4. Click the `+ Create your own application` button at the top
+5. Ensure `Integrate any other application you don't find in the gallery (Non-gallery)` is selected and enter a name for the app. Common examples are: `MorpheusSSO`
+6. Click the `Create` button at the bottom and wait for it to complete
+7. Once created, you’ll be in the `Overview` of the application created. Navigate to the `Single sign-on` section from the left pane
+8. Choose `SAML` as the Single sign-on method
+9. Copy both the `Login URL` and `Logout URL` in Step 4, we’ll need these in some of the next steps
+10. Before we can continue configuring the application, the configuration needs to be generated in HPE Morpheus Enterprise for more data
+
+## Create an Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### About this task
+
+Azure requires inputting the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` in the Azure SSO configuration before it provides the Endpoints and Certificate necessary to add the Integration into HPE Morpheus Enterprise. In order to get the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` to input into Azure SSO configuration, we need to create a `Azure AD SAML SSO` integration in HPE Morpheus Enterprise first.
+
+To add the integration:
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Click the IDENTITY SOURCES button in the Tenant detail page
+5. Click the + ADD IDENTITY SOURCE button
+6. Select `Azure AD SAML SSO` from the `TYPE` dropdown
+7. Add 
+
+   - Name
+   - (Optional) Description
+   - Paste the `Login URL` copied from Azure into the `LOGIN REDIRECT URL` field
+   - Paste the `Logout URL` copied from Azure into the `SAML LOGOUT REDIRECT URL` field
+8. This is the minimum information needed for now, which will let us generate the details needed from HPE Morpheus Enterprise. We’ll return to this configuration page later to enter more information.
+9. Click the SAVE CHANGES button 
+
+   IMPORTANT
+
+   Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+   Upon saving, the Entity ID (`Identifier (Entity ID)`) and SP ACS URL (`Reply URL (Assertion Consumer Service URL)`) will be provide in the Identity Source list view. Copy these for use in Azure SSO configuration.
+
+   ![../../_images/saml_setup.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C3ECE586-166D-49EB-85B2-42D73E125E79-high.png)
+
+## Configure Azure Enterprise Application
+
+### About this task
+
+This guide assumes an Azure AD Enterprise Application has already been created. Please refer to documentation above, if this has not already been configured.
+
+### Procedure
+
+1. Navigate to: Azure Active Directory  >  Enterprise Applications  >  Single sign-on
+2. Choose `SAML` as the Single sign-on method
+3. On Step 1 (`Basic SAML Configuration`), click the `Edit` button and enter the following: 
+
+   - Identifier (Entity ID)
+     :   Enter the `Entity ID` URL from the HPE Morpheus Enterprise Identity Source Integration above
+   - Reply URL (Assertion Consumer Service URL)
+     :   Enter the `SP ACS URL` from the HPE Morpheus Enterprise Identity Source Integration above
+   - Logout URL
+     :   Enter the following format: `https://yourUrl/login/` If this is a sub tenant, the format may instead be the following: `https://yourUrl/login/account/1` The login URL can be found under IDENTITY SOURCES in the tenant
+4. On Step 2 (`Attributes and Claims`), click the `Edit` button
+5. Click the `Add a group claim` button at the top
+6. Choose `All groups` and ensure `Group ID` is selected for the `Source attribute` dropdown 
+
+   NOTE
+
+   You can also choose `Security groups`, which ever makes more sense for the organization
+7. Close the pane and return to the Enterprise Application in the `Single sign-on` section
+8. On Step 3 (`SAML Certificates`), click the `Download` link next to `Certificate (Base64)` and `Federation Metadata XML` 
+
+   NOTE
+
+   The files will download, keep them available for later configuation in HPE Morpheus Enterprise
+9. Navigate to `Users and Groups` in the left pane
+10. Click the `Add user/group` button
+11. Add Azure groups to this application that will be able to login to HPE Morpheus Enterprise 
+
+    NOTE
+
+    the object ID for each of these groups, as they will be used later when configuring HPE Morpheus Enterprise to map the group to roles
+12. Once groups have been added, click the `Assign` button at the bottom
+
+## Configure the Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise using `Username and Password`, as usual
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Select IDENTITY SOURCES in the Tenant detail page
+5. Click the pencil (edit) next to the integration created previously
+6. Ensure the `SAML REQUEST` field is set to `Self Signed` 
+
+   NOTE
+
+   A custom RSA signature can be used here if needed, if required by the orgnaization
+7. Ensure the `SAML RESPONSE` field is set to `Validate Assertion Signature` 
+
+   NOTE
+
+   With this setting, if the assertion signature ever changes in the Azure Enterprise Application, this would need to be updated to match
+8. Edit/view the downloaded `Federation Metadata XML` (`.xml` extension) file from the previous section 
+
+   NOTE
+
+   It is recommended to use `Microsoft Edge`, or another browser, to view the contents
+9. In the `Federation Metadata XML` file, locate the `<X509Certificate> </X509Certificate>` under the `<Signature>` section. Copy the entire contents between the `<X509Certificate>` and `</X509Certificate>`, it is very long
+10. Paste the value copied from the `Federation Metadata XML` file into the `Public Key (Optional)` box, below the `SAML RESPONSE` dropdown
+
+## Configure Role Mappings
+
+### About this task
+
+Role mappings will map Azure AD Groups to Morpheus Roles. Azure AD users will be assigned Roles in HPE Morpheus Enterprise upon signing in based on their Group Membership in Azure AD.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+DEFAULT ROLE
+:   Role a Azure AD user will be assigned by default upon signing in to HPE Morpheus Enterprise using this Identity Source.
+
+REQUIRED AZURE AD GROUP OBJECT ID
+:   Object ID of Azure AD Group a user must be a member of to be authorized to sign in to HPE Morpheus Enterprise. Users not belonging to this Group will not be authorized to login to HPE Morpheus Enterprise. This field is optional, and if left blank, any user from the Azure AD App will be able to sign in to HPE Morpheus Enterprise and will be assigned the Default Role if no Role Mappings match AD Group membership.
+
+GROUP ASSERTION ATTRIBUTE NAME
+:   Enter `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` for Azure AD SSO
+
+Additional Role Mappings
+:   The existing Roles in HPE Morpheus Enterprise will be listed. To map a HPE Morpheus Enterprise Role to an Azure AD Group, enter the Object ID of the desired Azure AD Group in the Role Attribute Value field for the corresponding HPE Morpheus Enterprise Role.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added. The Identity Source can be edited anytime to deactivate or change Role Mappings or other values.
+
+NOTE
+
+If Role mappings are edited after Azure AD SSO users have signed into HPE Morpheus Enterprise, currently logged in users will need to log out of HPE Morpheus Enterprise for the new Role mappings to take effect, when applicable.
+
+### Procedure
+
+1. Under the `Role Azure Group Mappings` secton, verify the `DEFAULT ROLE` dropdown has the role in HPE Morpheus Enterprise selected that all users will be assigned by default 
+
+   - It is recommended that this role contains no permissions, which ensures that anyone who authenticates gets no access
+2. Under the `Role Azure Group Mappings` secton, you will see role names listed. Next to these are text boxes with `Assertion Attribute Mappings` inside. Enter group object IDs from Azure into these text boxes. This will map the Azure AD groups to specific roles in Morpheus
+3. Finally, click `Save Changes` at the bottom of the page 
+
+   Here is an example of the configuration above:
+
+   ![../../_images/saml_setup_complete.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5666456C-8FE1-4305-816E-FD051CC4636F-high.png)
+
+## Azure Group Lookups
+
+When a user in azure ad has more that 150 group attributes, Azure does not include the group claims in the SAML response, and HPE Morpheus Enterprise is required to query Microsoft Graph to obtain the users group attribute values. When there are users that are members of more that 150 groups, populate the `Azure Group Lookups` section in order for those users to be able to use the Azure AD SAML SSO integration, otherwise no groups will be obtained and proper role mappings cannot occur.
+
+AZURE TENANT ID
+:   Add Azure AD Tenant ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Tenant ID
+
+AZURE APP ID
+:   Add Azure AD Application (Client) ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Application (Client) ID
+
+AZURE APP SECRET
+:   Add Azure Application (Client) Secret if user group membership will exceed 150. See [Generate a Client Secret](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-0A7984C3-E094-45D6-B2D9-ED3179A79988) for information on creating an Azure Application (Client) Secret
+
+ROLE LINK ATTRIBUTE NAME
+:   default: <http://schemas.microsoft.com/claims/groups.link>. This is not normally changed.
+
+## Logging Into HPE Morpheus Enterprise with Azure AD SAML
+
+### Procedure
+
+1. Navigate to the HPE Morpheus Enterprise URL
+2. A new button will appear to allow sign-in using Azure AD SAML, with the same name as the integration. Click the button 
+
+   ![../../_images/sign_in_page.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1FEC124E-FF68-4E72-9872-1D336777E8E5-high.png)
+3. Sign-in with your Microsoft/Azure account 
+
+   ![../../_images/ms_signin.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF8B57F9-055B-4A8C-AEB5-95ABA09BD3DF-high.png)
+
+   NOTE
+
+   If no local users other than the System Admin have been created, “USERNAME AND PASSWORD” option will not be displayed, only the SAML option.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json b/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
new file mode 100644
index 0000000..4be9074
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+  "title": "Adding Functionality Through Operational Workflows",
+  "ordinal": 366,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Functionality Through Operational Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md b/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
new file mode 100644
index 0000000..df4ce34
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
@@ -0,0 +1,113 @@
+# Adding Functionality Through Operational Workflows
+
+Operational Workflows, in HPE Morpheus Enterprise, are logically arranged sets of individual automation Tasks designed to accomplish some function. They can be executed on a one-off basis as needed or set on a timed execution schedule, similar to a cron job. While they’re often used to orchestrate some facet of cloud resource management, they can also be used to speed and standardize creation of HPE Morpheus Enterprise constructs.
+
+As an example case for this guide, we’ll create an Operational Workflow which will allow Primary Tenant administrators to create Groups within Subtenants. This is not natively-available functionality as Groups are not a tenanted construct in HPE Morpheus Enterprise. They exist solely within the Tenant that created them and cannot be shared or viewed by others.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Groups
+- Cypher
+- Tasks
+- Workflows
+- Inputs
+- HPE Morpheus Enterprise API
+
+## Initial Considerations
+
+Since we’re creating Groups in a second Tenant, you’ll need to have at least one other Tenant in your appliance (Administration > Tenants). You’ll also need access to a user account within the Subtenant which has rights to create Groups. You could use a pre-existing user account or create a service user for automated processes like this one.
+
+Impersonate or log in with your service account and create an API Key. API Keys are created by clicking on the user’s name in the upper-right corner of the application window, then clicking User Settings. On the User Settings page, click API ACCESS. Next to one of the entries (it doesn’t matter which one but be careful about overwriting a key that is already in use), click ACTIONS and then Generate. Copy the Access Token into a secure place you can retrieve it from in the next step. You will not be able to see this key again after closing the modal containing the API Keys. Return to your primary HPE Morpheus Enterprise account in the original Tenant to continue with the guide.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the API Key for our service account user so we can call it into automation scripts in a later step. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/subusertoken
+- **VALUE:** Enter HPE Morpheus Enterprise API Key for the Subtenant user
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/createcypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EF5395A9-F584-4E5D-B77C-11ED02BF2822-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, Workflows, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. In this case, the Inputs will be associated with our Operational Workflow. We will create three so the user can define a name for the new Group and optionally provide a code and/or location value if desired.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** Subtenant Group Name (The friendly name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** subgroupname (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** Subtenant Group Name (The label the user sees next to the input field)
+- **REQUIRED:** Checked (A name value is required for our Group so this Input should be marked required. The other two Inputs we’ll create will not be required as they are optional fields when creating a Group)
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createinput.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1081A234-C0CA-4B22-82F1-EE91843663DD-high.png)
+
+Create two more Inputs in a similar fashion with the following configuration:
+
+### Code Input
+
+- **NAME:** Subtenant Group Code
+- **FIELD NAME:** subgroupcode
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Code
+- **HELP BLOCK:** Optional Code Value (I opted to enter help block text to make it clearer to the user that this is an optional input)
+- **REQUIRED:** Unchecked
+
+### Location Input
+
+- **NAME:** Subtenant Group Location
+- **FIELD NAME:** subgrouplocation
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Location
+- **HELP BLOCK:** Optional Location Value
+- **REQUIRED:** Unchecked
+
+## Create Task
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ve written a Python script outside HPE Morpheus Enterprise and tracked it in a Github repository. Since my Github account is integrated with HPE Morpheus Enterprise, I can simply refer to the script in a new Task. This prevents me from having to cut and paste code and also ensures the latest version of my code in executed every time the Task is invoked. Integrating with version control is optional, for simplicity you can also draft a quick script directly in HPE Morpheus Enterprise if you’d prefer. If you want to view, copy, or fork the code, you can see it [here](https://github.com/ahark86/morpheus-group-create/blob/master/main.py). New Github integrations can be added in Administration > Integrations.
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Subtenant Group Create - Task
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Repository (Select Local to draft or paste code directly into HPE Morpheus Enterprise)
+- **FILE PATH:** main.py (In my case, the script is in the root of the repository so I can simply refer to it by filename)
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the HPE Morpheus Enterprise API Key from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US).
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5C031817-0262-4BF2-919F-0B9677FB0559-high.png)
+
+## Create Operational Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. Provisioning Workflows (which aren’t used in this guide) are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need an Operational Workflow which are run on-demand when needed or on timed intervals.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** Subtenant Group Create
+- **PLATFORM:** All
+- **TASKS:** Subtenant Group Create - Task
+- **INPUTS:** Find Subtenant Group Name, Subtenant Group Code, and Subtenant Group Location using the typeahead field. I think it makes most sense to order them with Name first but it’s not required
+
+Once done, click SAVE CHANGES
+
+![../../_images/createworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-680497EC-0916-4C46-9821-E3DC1A379126-high.png)
+
+## Execute Workflow
+
+After saving the new Operational Workflow, you’ll be left on the Workflows list page. From here we can try the new Workflow. Click on the gear icon at the far-right part of the row, then click Execute. Our three Inputs should be visible. We can see the Name field is marked as required (as we configured) and our help block text underneath the optional Inputs. Complete each field (Context Type can be left at None) and click EXECUTE.
+
+![../../_images/executeworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E459787E-142E-4A07-819A-E280C1C9021C-high.png)
+
+Once again login in as or impersonate your service account user within the Subtenant. Navigate to Infrastructure > Groups and inspect the list. You should now see that our Group has been created here.
+
+![../../_images/grouplist.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1D03AA1C-1895-4C61-86EB-10C99456022D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json b/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
new file mode 100644
index 0000000..634c500
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+  "title": "CLI Troubleshooting",
+  "ordinal": 348,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html",
+  "topic_cluster": {
+    "clustering_title": "CLI Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md b/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
new file mode 100644
index 0000000..9749045
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
@@ -0,0 +1,11 @@
+# CLI Troubleshooting
+
+If you have installed the HPE Morpheus Enterprise CLI successfully and get a successful login but see this error `Error Communicating with the Appliance. SSL_connect returned=1 errno=0 state=error: certificate verify failed`
+
+run the command
+
+```
+```
+morpheus remote update {appliancename} --insecure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..cbfb9b2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 104,
+  "parent_title": "Automation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..ae29fd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,10 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html)**
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html)**
+- **[Task Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json b/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
new file mode 100644
index 0000000..46bbf3d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+  "title": "Users & User Groups",
+  "ordinal": 308,
+  "parent_title": "Administration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html",
+  "topic_cluster": {
+    "clustering_title": "Users & User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md b/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
new file mode 100644
index 0000000..b32b98b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
@@ -0,0 +1,6 @@
+# Users & User Groups
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json b/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
new file mode 100644
index 0000000..06252ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+  "title": "Creating Instances",
+  "ordinal": 84,
+  "parent_title": "Instances",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md b/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
new file mode 100644
index 0000000..1b51298
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
@@ -0,0 +1,41 @@
+# Creating Instances
+
+The Instance catalog is the one-stop shop for selecting items to be provisioned and pieced together. It contains not only basic container and VM options but also tailored services for SQL databases, NoSQL databases, cache stores, message busses, web servers, and even full-fledged apps. The list contains a lot of items to choose from and they are represented to the user based on what provisioning engines are enabled and integrated in the HPE Morpheus Enterprise environment.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances section. A modal will display allowing the catalog to be searched. Once an item is selected it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) thereby restricting access to non-sanctioned catalog items, as well as added to via the Library section. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple cloud integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. If the environment is new and these do not yet exist, it may be advisable to refer to one of our starter guides, such as the guide on getting started with HPE Morpheus Enterprise and [VMware](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html). The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is mostly useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. Datastore for VMware or Network). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such.
+
+Configuration options provided in this screen are very powerful. An example is MySQL where a Master/Slave or Master/Master layout can be selected. These configurations will automatically deploy two MySQL VMs or containers and link them together to provide replication. These types of configurations exist for a wide range of Instance types and are optimized for high performance and scale. It is even possible to provision entire sharded MongoDB clusters.
+
+One last step before the Instance can be provisioned is the Automation step. This wizard step may or may not appear depending on the capabilities of the Instance type or previous configurations in the account. It is here one can easily select a post-provisioning workflow to run (see more on Tasks and Workflows elsewhere in HPE Morpheus Enterprise documentation), assign a load balancer, or even configure the backup job that gets created.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes (typically a container configuration will be rather quick if the Instance type has previously been provisioned before).
+
+## Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for HPE Morpheus Enterprise to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with HPE Morpheus Enterprise, EC2 instances pre-existing on an Amazon AWS account, or virtual machines that are running on a KVM host. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for HPE Morpheus Enterprise to automatically onboard these resources. Not only will HPE Morpheus Enterprise inventory these instances at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, HPE Morpheus Enterprise allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Assign to the primary Tenant or one of the Subtenants
+- Select a Group (this dropdown contains a filtered list of Groups which the associated Cloud is in)
+- Username and password for a seeded account
+- Opt to install HPE Morpheus Enterprise Agent or not (for more on HPE Morpheus Enterprise Agent, click [here](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/morpheus_agent.html))
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Select a version number for the Instance (such as 20.04 for a basic Ubuntu Instance)
+- Select a Layout, Instance Types often have multiple Layout configurations
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by adding it to an App or expanding the Instance horizontally with added nodes.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json b/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
new file mode 100644
index 0000000..1e93fb6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+  "title": "Installing iSUT on Deployed Instances (Optional)",
+  "ordinal": 425,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html",
+  "topic_cluster": {
+    "clustering_title": "Installing iSUT on Deployed Instances (Optional)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md b/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
new file mode 100644
index 0000000..d84cff8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
@@ -0,0 +1,25 @@
+# Installing iSUT on Deployed Instances (Optional)
+
+## About this task
+
+To enable driver inventory and updates within the operating system, iSUT and AMS must be installed on each deployed instance.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the target instance.
+
+   NOTE
+
+   Since the workflow requires iLO credentials, only one instance can be selected at a time. Multiple instances cannot be targeted for a single iSUT/AMS install.
+3. Click Actions > Run Workflow.
+4. Select the appropriate workflow:
+   1. Download and Install iSUT and AMS (Linux), or
+   2. Download and Install iSUT and AMS (Windows)
+5. Enter the **iLO credentials** for the targeted bare metal server.
+
+   NOTE
+
+   These are iLO credentials, not OS credentials.
+6. Click Execute.
+7. Monitor progress from the History tab until the workflow completes.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json b/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
new file mode 100644
index 0000000..626db65
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+  "title": "Alert Rules",
+  "ordinal": 262,
+  "parent_title": "Overview",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html",
+  "topic_cluster": {
+    "clustering_title": "Alert Rules",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md b/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
new file mode 100644
index 0000000..9ed07e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
@@ -0,0 +1,12 @@
+# Alert Rules
+
+Alert Rules provide a powerful means to configure who gets notified in various scenarios. These scenarios include targeting specific checks, groups, or apps, and adding the appropriate recipients to be notified during a situation in which those filters are impacted.
+
+- **Min Duration:** This setting delays notification to the recipients by the entered number of minutes required for the incident to be opened.
+- **Min Severity:** Some executives might want to be notified of an outage but only if the severity impact goes above a certain level. This is very useful for scoping escalations.
+
+To add recipients to a rule just start typing their name in the Recipients section towards the button of the edit form. An auto-complete list will start populating with contact names. Once one is selected a delivery method can be selected as well as whether or not they should be notified of any escalation changes and/or closed incidents. The delivery methods available depend on the type of contact information configured for your contact. If needed, contacts can be created or edited in Monitoring  >  Contacts.
+
+TIP
+
+A recipient can be in multiple alert rules and can even be configured to be notified via different methods depending on the rule. A useful example might be to alert someone via email for lower severity incidents but SMS for critical severity levels.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json b/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
new file mode 100644
index 0000000..5aa0e28
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+  "title": "Add SSL Certificate",
+  "ordinal": 243,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html",
+  "topic_cluster": {
+    "clustering_title": "Add SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md b/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
new file mode 100644
index 0000000..ae1cf17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
@@ -0,0 +1,13 @@
+# Add SSL Certificate
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, click + ADD
+3. From the Add SSL Certificate wizard input the following as needed: 
+
+   - Name
+   - Domain Name
+   - Key File
+   - Cert File
+   - Root Cert
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json b/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
new file mode 100644
index 0000000..7cee703
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+  "title": "Data Stores",
+  "ordinal": 234,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md b/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
new file mode 100644
index 0000000..d70694d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
@@ -0,0 +1,30 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, HPE Morpheus Enterprise will onboard all existing data stores and administrators can then make them available to Groups or Tenants as needed. At provision time, when applicable based on Cloud and Layout, users can select the data store they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
+
+## Create Data Stores
+
+To a limited extent, data stores can be created from this view. Currently, data store creation is restricted to VMware data store creation on 3Par volumes. In order to create such a data store you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and HPE Morpheus Enterprise will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
+
+## Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store, and which Tenants have access. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Tenants:** Primary Tenant users can opt to make the data store available to all Tenants (public visibility) or to selected Tenants (private visibility with specific Tenants selected). Subtenant users will only be able to make data stores visible to their own Tenant
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..ec96a34
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 271,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..abf8f5f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json b/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
new file mode 100644
index 0000000..9af8983
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+  "title": "ServiceNow Monitoring Integration",
+  "ordinal": 505,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.html",
+  "topic_cluster": {
+    "clustering_title": "ServiceNow Monitoring Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md b/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
new file mode 100644
index 0000000..4d1e1a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
@@ -0,0 +1,28 @@
+# ServiceNow Monitoring Integration
+
+NOTE
+
+A ServiceNow Integration must be already configured in Administration > Integrations to enable the ServiceNow Monitoring Integration. Refer to the [ServiceNow](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html) configuration guide for more information.
+
+Enabled
+:   Enables the ServiceNow Monitoring Integration
+
+Integration
+:   Select from a ServiceNow Integration added in Administration > Integrations
+
+New Incident Action
+:   The Service Now action to take when a Morpheus incident is created.
+
+Close Incident Action
+:   The Service Now action to take when a Morpheus incident is closed.
+
+Incident Severity Mapping
+
+Table 1.
+
+    |  |  |
+| --- | --- |
+| HPE Morpheus Enterprise Severity | ServiceNow Impact |
+| Info | Low/Medium/High |
+| Warning | Low/Medium/High |
+| Critical | Low/Medium/High |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json b/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
new file mode 100644
index 0000000..21eb5c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+  "title": "Provisioning",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md b/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
new file mode 100644
index 0000000..30270b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
@@ -0,0 +1,14 @@
+# Provisioning
+
+There are several capabilities in the HPE Morpheus Enterprise provisioning engine. Things ranging from application / service deployments via containers, virtual machines, and even bare metal. Deployment management and app template construction are also core aspects of the provisioning engine. Take advantage of custom tasks and workflows within any environment by building tasks and workflows from those tasks. There is a lot of information to cover with regards to provisioning but HPE Morpheus Enterprise makes it intuitive and smooth.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html)**
+- **[Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html)**
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html)**
+- **[Executions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html)**
+- **[Code](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json b/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
new file mode 100644
index 0000000..c3ddae5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+  "title": "Viewing the Self Service Catalog",
+  "ordinal": 139,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md b/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
new file mode 100644
index 0000000..c12fe0e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
@@ -0,0 +1,5 @@
+# Viewing the Self Service Catalog
+
+The complete Self Service catalog can be viewed by clicking on Catalog from the Provisioning menu. The complete list of items available for the Self Service catalog are shown here but users working in the Service Catalog Persona will see only those allowed based on their user role. In addition to the name and type of each catalog item, we can also see a description and whether not the catalog item is featured or active. Featured items are given special visibility in the Service Catalog Persona and inactive items will not appear as provisioning options.
+
+![../../_images/catalogList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E3A8EE0B-A475-4D68-B6C5-626CB50D9772-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json b/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
new file mode 100644
index 0000000..83a4c51
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+  "title": "Creating Resource Pools",
+  "ordinal": 404,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Resource Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md b/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
new file mode 100644
index 0000000..35b7dad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
@@ -0,0 +1,13 @@
+# Creating Resource Pools
+
+## About this task
+
+This section describes how to create a resource pool within your HPE ProLiant Bare Metal Cloud in Morpheus. Resource pools help you organize and allocate servers for provisioning and management.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds. Select the cloud and click the Resources tab.
+2. Click the + Add Resource Pool.
+3. Enter a name and complete any additional required details for the resource pool and then click Next.   
+   ![New Resource Pool](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0192576F-1954-421D-8C37-5CF3A41C0C7D-high.png)
+4. Click Save Changes to finalize resource pool creation.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json b/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
new file mode 100644
index 0000000..7a35991
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+  "title": "Price Phase Task Utilization",
+  "ordinal": 118,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html",
+  "topic_cluster": {
+    "clustering_title": "Price Phase Task Utilization",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md b/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
new file mode 100644
index 0000000..9e3c367
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
@@ -0,0 +1,52 @@
+# Price Phase Task Utilization
+
+Price Phase Tasks Video Demo
+
+Price Phase Tasks allow computed pricing for any workload in any Cloud (even public Clouds) to be overridden based on custom logic designed by the user. The variable “spec” is fed into the Task which represents the Instance configuration. The Task can be designed to use the Instance config data and compute an appropriate price for the Instance. HPE Morpheus Enterprise expects a return payload in the format below for the price override to work correctly. If used, pricing computed via Task replaces any other costing data which would have been applied to the workload (such as pricing based on the Service Plan). The user will see price estimates based on the Price Phase Task in the Instance provisioning wizard where the Service Plan pricing would otherwise be shown. Additionally, since Workflows which invoke Price Phase Tasks are tied to the Layout, the user can see different pricing depending on which Instance Type Layout is selected.
+
+NOTE
+
+Price Phase Tasks are only invoked if the Workflow is tied to a Layout.
+
+The return payload should be a JSON array of “priceData” objects. priceData objects should contain values for each of the keys in the table below:
+
+| Key | Description | Data Type | Possible Values |
+| --- | --- | --- | --- |
+| incurCharges | Indicates the Instance state when this charge should be applied | String | **Running:** Charge is incurred while the workload is in a running state, **Stopped:** Charge is incurred while the workload is in a stopped or shutdown state, **Always:** This charge is always applied. Some charges may apply simultaneously, for example, “Always” and “Running” states will apply while the workload is running. |
+| currency | Indicates the currency in which the charge will be applied | String | Enter any three‐letter currency code which HPE Morpheus Enterprise supports for its pricing, such as “USD”, “CAD”, or “GBP” |
+| unit | Indicates the time interval at which the charge is applied | String | Enter “minute”, “hour”, “day”, “month”, or “year” |
+| cost | Indicates the amount applied as cost for each configured time unit interval that passes. This is the cost to you, not the price with markup which the customer would see. | Number | A numerical amount such as “3.00” or “34.23” |
+| price | Indicates the amount applied as price for each configured time unit interval that passes. This is the price to the customer with any built‐in markup you need to apply. | Number | A numerical amount such as “3.00” or “34.23” |
+
+A number of different Task types could be used in this phase. As long as the Task is returning the required JSON array, the Task will work correctly. Below is an example using a Groovy Task. This is simply outputting a static payload though in a real world scenario you’d likely use Task logic to output a dynamic array based on the Instance configuration.
+
+```
+```
+def rtn = [  
+  priceData: [  
+    [  
+      incurCharges: 'always',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 2.0,  
+      price: 2.0  
+    ],  
+    [  
+      incurCharges: 'running',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 3.0,  
+      price: 3.0  
+    ],  
+    [  
+      incurCharges: 'stopped',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 1.0,  
+      price: 1.0  
+    ]  
+  ]  
+]  
+return rtn
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..b935ee5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 518,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..0d109a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,9 @@
+# Storage
+
+**Subtopics**  
+
+- **[3Par](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html)**
+- **[AzureStorage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html)**
+- **[Dell ECS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html)**
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
+- **[Isilon](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json b/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
new file mode 100644
index 0000000..520873b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+  "title": "Creating and Running Security Scan Jobs",
+  "ordinal": 93,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running Security Scan Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md b/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
new file mode 100644
index 0000000..7d6a6f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
@@ -0,0 +1,86 @@
+# Creating and Running Security Scan Jobs
+
+Security Scan Jobs allow users to create and schedule SCAP program (Security Content Automation Program) scans for groups of managed systems. These Jobs can call in existing SCAP packages and checklists, which are used to scan the targeted systems on-demand or on a scheduled basis. Historical data for these scans is saved in the Job Execution list and in the software section of server detail pages. Detailed scan reports can also be viewed for each system as needed once the scan is complete. See the [SCAP documentation](https://csrc.nist.gov/CSRC/media/Projects/Security-Content-Automation-Protocol/documents/docs/scap-nistir-7343.pdf) on the NIST website for information on developing your own scanning procedures.
+
+NOTE
+
+Creating and editing Security Scan Jobs requires the “Security: Scanning” Role permission set to Full. Viewing Security Scan Jobs and seeing the results for scanned servers requires at least a Read-level permission.
+
+## Add a new Security Scan Job
+
+### About this task
+
+NOTE
+
+New security scan packages are added in HPE Morpheus Enterprise Library rather than here in the Jobs section. Ensure you have uploaded the desired security package in Library > Templates > Security Packages before proceeding with new security Job creation.
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click +ADD
+3. Set the Job type to “Security Scan Job” and provide a friendly name for the Job
+4. Click NEXT 
+
+   ![../../_images/2new_job.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E8A3A8C8-27F1-48F1-8B98-2AF3AAE6E121-high.png)
+5. Select a security package, see the previous section to add a new one
+6. Enter your Scan Checklist (XML document) and Security Profile (XCCDF document), more information on these can be found in the SCAP documentation linked above
+7. Set a schedule or leave as Manual to only run this scan on-demand (new execution schedules can be created in Library > Automationif needed)
+8. Set a specific power state target if desired. This indicates whether the Job should run against workloads having any power state, just an “on” power state, or just an “off” power state
+9. Set the context, can be Instance or Server. Select as many Instances or Servers as needed for this scanning run
+10. Click NEXT
+11. After final review, click COMPLETE 
+
+    ![../../_images/3job_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-77399E18-27B9-465D-885C-F34C86B2EA19-high.png)
+
+## Running Security Scan Jobs
+
+### About this task
+
+Once created, Security Scan Jobs will run based on the configured schedule. They can also be run on-demand when needed:
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click MORE
+3. Click “Execute” 
+
+   ![../../_images/4execute_scan.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-ECB853BF-5ACC-4D03-BCC3-AF5A1D2706A3-high.png)
+
+## Viewing Completed Security Scan Jobs
+
+### About this task
+
+To view a list of completed Security Scan Jobs (and Jobs of other types):
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Job Executions Tab
+2. Additional details can be viewed by clicking (i) 
+
+   ![../../_images/5execution_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-486B12EC-23D0-4977-9075-9BAE63439855-high.png)
+
+### Results
+
+To view scan results for specific servers:
+
+1. Navigate to the server detail page (Infrastructure > Hosts > Virtual Machines tab > Selectedserver)
+2. Click on the Software tab part way down the page, then click on the Security subtab
+3. High level details on previous scans is viewable here
+
+   ![../../_images/6server_results.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FEF15F44-AFFC-4639-B948-E5077F44A1AA-high.png)
+4. To view the full report, click (i)
+
+   ![../../_images/7scan_report.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-87EF931F-9CF2-4909-BD82-654F0658AE7D-high.png)
+
+## Security Drift
+
+In addition to tracking the scan results over time as described in the previous section, HPE Morpheus Enterprise also provides detail into the change from the most recent scan to the one prior. This information is displayed in the Software tab (and Security subtab) of the detail page for the virtual machine (accessed from the associated Instance detail page or at Infrastructure > Hosts > Virtual Machines). The information surfaced by this view is listed below. If there is no change, you’ll simply see a “No Drift” message.
+
+- **Title:** The criteria for the test that has newly passed or failed
+- **Severity:** The severity level for the indicated security requirement
+- **Result:** The indicator for whether this test has newly passed or failed
+- **New Pass:** The number of tests that have newly passed compared to the prior scan
+- **New Fail:** The number of tests that have newly failed compared to the prior scan
+- **Status:** An indicator of the change in security posture since the prior scan. A net gain in test failures will yield a negative status indicator while net gains in passed tests (or no change) will yield a positive status indicator
+
+![../../_images/8securityDrift.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A56F50AC-F22B-4AB1-84B2-AE09A887951C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json b/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
new file mode 100644
index 0000000..a8953e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+  "title": "Oracle Cloud",
+  "ordinal": 467,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md b/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
new file mode 100644
index 0000000..a2c8aa4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
@@ -0,0 +1,230 @@
+# Oracle Cloud
+
+## Required Permissions
+
+Integrating Oracle Public Cloud with HPE Morpheus Enterprise requires access to a service account with at least the permission set listed below. When creating an Oracle Cloud integration scoped to a specific compartment, the service account needs access only to the listed resource families within the chosen compartment. If the Cloud will be scoped to all compartments, the service account will need access to the listed resource families at the root compartment.
+
+### Oracle Cloud Policy Requirements
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage cluster-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage compute-management-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage data-catalog-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage dns in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage file-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage instance-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage object-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage virtual-network-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage volume-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+## Add Oracle Public Cloud
+
+IMPORTANT
+
+A Keypair (both public and private key) must be added to HPE Morpheus Enterprise with the Public Key in ssh-rsa format. The Public Key in PEM format needs to be added to Oracle Cloud users keys in Oracle Cloud console for authentication.
+
+NOTE
+
+Information on uploading the Public Key and generating Tenancy’s OCID and User’s OCID can be found at <https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm>
+
+To get started, navigate to Infrastructure > Clouds. Click + ADD and select Oracle Public Cloud to begin a new one. Configure the following options for the new Cloud:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+TENANCY OCID
+:   The OCID string from Tenancy Information section in Oracle Cloud
+
+USER OCID
+:   OCID String for the OPC API user
+
+SELECT KEY PAIR
+:   Select a keypair added to HPE Morpheus Enterprise matching the public key added to specified OPC API user
+
+REGION
+:   Select the OPC region (populates after successful account authentication)
+
+COMPARTMENT
+:   Choose to scope the Cloud to all compartments or to one specific compartment (populates after successful account authentication)
+
+INVENTORY
+:   Turn on for HPE Morpheus Enterprise to discover and sync existing VMs
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Enable Live Costing for Oracle Public Cloud
+
+Morpheus version 4.2.1 and higher support live costing data from the Oracle Cloud metering API. In order to authenticate with this API, edit your existing Oracle Cloud account integration or begin the process of newly integrating an account that wasn’t previously consumable in HPE Morpheus Enterprise (Infrastructure > Clouds > +ADD).
+
+In the advanced options section of the add/edit cloud modal for Oracle Public Cloud, the COSTING KEY and COSTING SECRET fields must be completed to work with metering API data in HPE Morpheus Enterprise. Unlike the OCI API authentication used to initially integrate Oracle Cloud, the metering API uses token-based authentication. We must access a Client ID and Client Secret value from the Oracle Public Cloud console to complete these fields.
+
+![../../../_images/1editcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CA223A6F-8A57-42C6-B371-5D9F07D3DDBA-high.png)
+
+Navigate to Oracle cloud sign in page, the URL for which is similar to the following example:
+
+`https://idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/signin`
+
+If you’re not redirected to the admin console similar to the one pictured below, log out and replace ‘signin’ at the end of the URL with ‘adminconsole’ as in the following example:
+
+`https:// idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/adminconsole`
+
+You’ll immediately be redirected back to the same signin page but in doing that you should be taken to the admin console after authenticating your session once again.
+
+![../../../_images/2adminconsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E1A971F2-CCF2-4FCF-BCAB-4E9EC09A92EE-high.png)
+
+Create a new application and select the type “Confidential Application”.
+
+![../../../_images/3confapp.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B6335CF7-81F9-4564-9377-E3B26BCA269F-high.png)
+
+On the Details tab, enter a “Name” value and click “Next”.
+
+![../../../_images/4appdetails.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B1C6E805-6451-4525-8A6F-F96C9D28BA31-high.png)
+
+On the Client tab, choose to “Configure this application as a client now” to reveal additional fields. Then, in the Authorization section, mark the boxes for “Client Credentials” and “JWT Assertion”.
+
+![../../../_images/5appauth.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5B10DEAF-82FB-461E-A804-8D2586512948-high.png)
+
+In the Token Issuance Policy section, click the “+Add Scope” button. Click the right-facing arrow button in the row for “CloudPortalResourceApp”. Mark the box to give read access for metering and click “Add”.
+
+![../../../_images/6meteringread.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F724B49C-D954-4EB3-BDAF-20A717A770AA-high.png)
+
+Click “Next” until the “Finish” button is shown, then click “Finish”
+
+The Client ID and Client Secret value will be shown at this point. If these values need to be referenced in the future, simply edit the application and go to the Configuration tab. The Client ID and Client Secret are shown in the General Information section.
+
+![../../../_images/7secretvalues.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-AACE06F0-9EBF-414D-9414-AFC686F70DE7-high.png)
+
+Back in HPE Morpheus Enterprise, enter these values in the COSTING KEY and COSTING SECRET fields of the add/edit cloud modal for your Oracle Public Cloud integration. You also need to fill in the IDENTITY SERVICE value. This value can be found in the URL for your Oracle admin console as shown in the image below. It will be in a format `idcs-xxxxxx`.
+
+![../../../_images/8identityservice.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E608C9F2-141F-4075-9B0D-B3A5EC53F46A-high.png)
+
+Save changes to the Cloud.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json b/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
new file mode 100644
index 0000000..52ba2a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+  "title": "Digital Ocean",
+  "ordinal": 393,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.html",
+  "topic_cluster": {
+    "clustering_title": "Digital Ocean",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md b/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
new file mode 100644
index 0000000..01449da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
@@ -0,0 +1,143 @@
+# Digital Ocean
+
+## Add a Digital Ocean Cloud
+
+DigitalOcean Cloud Integration Detail fields:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   DigitalOcean Username
+
+API Key
+:   Personal access tokens/Key from the DigitalOcean API  >  Tokens/Keys section.
+
+Data Center
+:   Select DigitalOcean DataCenter Region
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json b/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
new file mode 100644
index 0000000..7b7cd32
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+  "title": "SAML Integration",
+  "ordinal": 286,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html",
+  "topic_cluster": {
+    "clustering_title": "SAML Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md b/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
new file mode 100644
index 0000000..9be9152
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
@@ -0,0 +1,150 @@
+# SAML Integration
+
+## Overview
+
+The HPE Morpheus Enterprise SAML identity source integration allows customers to add user SSO to HPE Morpheus Enterprise, authenticated by external login SAML providers.
+
+![../../_images/samlLoginGeneric.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0A6CC774-6C13-4B74-B7A5-C8D414D5D46A-high.png)
+
+## Adding a SAML Integration
+
+### About this task
+
+To add a SAML integration:
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a tenant.
+3. Select IDENTITY SOURCES in the Tenant detail page
+4. Select + ADD IDENTITY SOURCE.
+5. Select SAML SSO from the TYPE field
+6. Add a Name and optional Description for the SAML integration
+
+### Results
+
+![../../_images/saml.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FEB50132-F13C-491F-83D8-FEABA6E7BB0C-high.png)
+
+There are 4 sections with fields that need to be populated depending on the desired configuration:
+
+- SAML Configuration
+- Role Mappings
+- Role Options
+- Assertion Attribute Mappings
+
+## SAML Configuration
+
+LOGIN REDIRECT URL
+:   This is the SAML endpoint HPE Morpheus Enterprise will redirect to when a user signs into HPE Morpheus Enterprise via SAML
+
+SAML LOGOUT REDIRECT URL
+:   The URL HPE Morpheus Enterprise will POST to when a SAML user logs out of HPE Morpheus Enterprise
+
+INCLUDES SAML REQUEST PARAMETER
+:   **Yes** (recommended) - the AuthN request will be sent via the ?SAMLRequest= parameter in the URL (GET)
+
+    **No** - the AuthN request will be submitted in the body of the request (POST)
+
+    NOTE
+
+    The SAML SP documentation should mention which binding to use but GET is most common
+
+SAML REQUEST
+:   **No Signature** - No signature is used on the SAML request
+
+    **Self Signed** - A self-signed X.509 Certificate is generated after clicking SAVE CHANGES. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+    **Custom RSA Signature** - Import a custom RSA Private Key and respective X.509 Certificate. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+SAML RESPONSE
+:   **Do Not Validate Assertion Signature** - The SAML response signature from the SAML SP will not be validated
+
+    **Validate Assertion Signature** - The SAML response signature from the SAML SP will be validated. Enter the SAML SP X.509 certificate in the **Public Key** field. This must be in PEM format
+
+IMPORTANT
+
+Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+## Role Mappings
+
+DEFAULT ROLE
+:   Role any SAML user will be assigned by default
+
+ROLE ATTRIBUTE NAME
+:   The name of the attribute/assertion field that will map to HPE Morpheus Enterprise roles, such a MemberOf
+
+REQUIRED ROLE ATTRIBUTE VALUE
+:   Attribute/assertion value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+<HPE Morpheus Enterprise ROLE NAME>
+:   Additional roles that can be mapped to a user, which will add to the DEFAULT ROLE. Attribute value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+## Role Options
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+## Assertion Attribute Mappings
+
+GIVEN NAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user First Name
+
+SURNAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user Last Name
+
+EMAIL ATTRIBUTE
+:   SAML SP field value to map to HPE Morpheus Enterprise user email address
+
+![../../_images/saml_assertion_attribute_mappings.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A5E51597-2545-4462-AD43-F82AB88434E7-high.png)
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added.
+
+In the Identity Sources section, important information for configuration of the SAML integration is provided. Use the SP ENTITY ID and SP ACS URL for configuration on the external login SAML provider side.
+
+NOTE
+
+In some cases, the SAML provider may need these values before providing the LOGIN REDIRECT URL and other values. When creating the integration, the NAME and LOGIN REDIRECT URL can contain any values, then selecting SAVE CHANGES will generate the above values. The NAME and LOGIN REDIRECT URL can be edited later, once the SAML configuration is created in the SAML provider.
+
+- ENTITY ID
+- SP ACS URL
+- LOGIN REDIRECT URL
+- SP METADATA
+
+![../../_images/identity_sources_info.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-112ECB06-8A2B-4025-B4CB-B57B7F12A12B-high.png)
+
+Sample Metadata code output:
+
+```
+```
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?><EntityDescriptor entityID="https://someip.com/saml/eDKL60P25" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"><SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"><NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat><AssertionConsumerService index="0" isDefault="true" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://someip.com/externalLogin/callback/eDKL60P25"/></SPSSODescriptor></EntityDescriptor>
+```
+```
+
+NOTE
+
+Different SAML providers will have different field names and requirements. An Okta SAML Dev environment was used for the example integration in this article.
+
+## Okta SAML SSO
+
+For Okta SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : Identity Provider Single Sign-On URL
+- ENTITY ID: Audience URI (SP Entity ID)
+- SP ACS URL: Single sign on URL
+
+## Onelogin SAML SSO
+
+For Onelogin SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : SAML 2.0 Endpoint (HTTP)
+- SAML LOGOUT REDIRECT URL : SLO Endpoint (HTTP)
+- SIGNING PUBLIC KEY : X.509 Certificate
+- ENTITY ID: ACS (Consumer) URL Validator
+- SP ACS URL: ACS (Consumer) URL
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json b/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
new file mode 100644
index 0000000..41fde69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+  "title": "OS Imaging",
+  "ordinal": 451,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html",
+  "topic_cluster": {
+    "clustering_title": "OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md b/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
new file mode 100644
index 0000000..ba7861a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
@@ -0,0 +1,7 @@
+# OS Imaging
+
+| S. No. | Symptom | Additional Details | Common Checks | Log Files | **Remarks** |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Windows Setup fails before completion | - Do **not** dismiss error dialogs immediately, as this may remove diagnostic information. - Use **iLO Remote Console** to access the system. - Press **Shift + F10** to open a command prompt in the Windows PE environment. | **Disk layout** – Confirm the primary disk is attached to the local RAID controller.  **AutoUnattend.xml** – Verify the file exists and defines required partitions:   - EFI System Partition (500 MB) - Microsoft Reserved Partition (128 MB) - Primary OS partition | Relevant setup logs may be found in:   - `X:\Windows\Panther` - `C:\$WINDOWS.~BT\Sources\Panther`   Key files:   - `setupact.log` - `setuperr.log` | Use logs to identify the specific failure stage and error code. |
+| 2 | RHEL / Oracle Linux  (Autoinstall via Kickstart) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F1: Installer UI - Alt + F2: Interactive shell - Alt + F3: Installation logs | **Key Logs:**   - `/var/log/anaconda/anaconda.log` - `/var/log/anaconda/syslog` - `/root/anaconda-ks.cfg` - `/root/original-ks.cfg` - `/root/post-ks.log` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to validate disk and network configuration before retrying installation. |
+| 3 | Ubuntu Linux  (Autoinstall via Curtin and Subiquity) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F2 or Ctrl + Alt + F2: Interactive shell - Installer runs on TTY1 | **Key Logs**   - `/var/log/installer/curtin-install.log` - `/var/log/installer/early-commands.log` - `/var/log/installer/subiquity-client*` - `/var/log/installer/subiquity-server*` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to check network and storage configuration, then review logs for errors. |
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..cb9510e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 149,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..ea00ba5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,83 @@
+# Configuring Virtual Images
+
+## System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
+
+## User Images
+
+Typically HPE Morpheus Enterprise does not have sufficient metatdata to successfully provision synced User Images. After integrating clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+### To edit and configure an existing Virtual Image:
+
+#### Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   HPE Morpheus Enterprise does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json b/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
new file mode 100644
index 0000000..47db3ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+  "title": "Morpheus Discovery",
+  "ordinal": 41,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Discovery",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md b/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
new file mode 100644
index 0000000..2b1859f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
@@ -0,0 +1,28 @@
+# Morpheus Discovery
+
+Morpheus has the ability to ingest existing environments. Existing running workloads will be inventoried into Morpheus and displayed in the UI. In 5-7 days Morpheus will start making recommendations based off of usage and pricing.
+
+NOTE
+
+Workloads that are inventoried do not have to be converted to managed.
+
+Once inventoried, Morpheus can provide valuable data for that instance:
+
+- Morpheus will know about networks
+- Start aggregating cost on public clouds
+- Start tracking usage
+- Some Clouds offer statistical details ( Amazon / VMware)
+- Power Status
+
+Right away inventorying existing environments will provide you with immediate insight to that environment. Once an existing workload has been discovered it can be converted to managed. Once converted to managed, Morpheus can deliver more capabilities and features.
+
+NOTE
+
+Workloads do not need the agent installed to be managed
+
+Once a workload is managed:
+
+- Enforce expiration/shutdown policies. This helps reign in environments (sprawl) and reduce cost.
+- Can tell what instance type it is
+- Can install agent (agent is optional)
+- Installing agent provides credentials and allows you to run workflows against it (day 2 operations)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json b/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
new file mode 100644
index 0000000..0770901
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+  "title": "User Roles",
+  "ordinal": 302,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html",
+  "topic_cluster": {
+    "clustering_title": "User Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md b/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
new file mode 100644
index 0000000..cf7f685
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
@@ -0,0 +1,16 @@
+# User Roles
+
+User Roles can be single or multitenant. A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
+
+**Subtopics**  
+
+- **[Create a Single Tenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html)**
+- **[Create a MultiTenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json b/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
new file mode 100644
index 0000000..312c5c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+  "title": "Cherwell",
+  "ordinal": 489,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html",
+  "topic_cluster": {
+    "clustering_title": "Cherwell",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md b/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
new file mode 100644
index 0000000..8c67d88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
@@ -0,0 +1,53 @@
+# Cherwell
+
+## Add Cherwell Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Cherwell` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   HOST
+   :   Url of the Cherwell Instance
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Cherwell user’s password
+
+   CLIENT KEY
+   :   Provide your Cherwell client key
+
+   CREATED BY USER
+   :   This is the full name of a user in the Cherwell system. When a new change management record is created in the Cherwell system, this user will be added to the record as the user that created it.
+
+   START DAYS FROM NOW
+   :   Number of days from now to set proposed start date
+
+   END DAYS FROM NOW
+   :   Number of days from now to set proposed end date
+
+   CUSTOM MAPPING
+   :   This is an optional json object that allows the custom setting of the Cherwell fields on the Change Request object.
+
+       NOTE
+
+       The keys in the map correspond to the name of the field on the Change Request in Cherwell that you would like to set (see <https://bertram.d.pr/1Ziuhy> for a reference). In addition, the value in the map corresponds to the value you wish to use. Within the value, Morpheus variables may be used. Here is an example for setting the Description is:
+
+       ```
+       ```
+       {  
+       "Description":"Created from Morpheus by ${instance.createdByUsername} in ${zone.name}"  
+       }
+       ```
+       ```
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.json b/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
new file mode 100644
index 0000000..dbaa0bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+  "title": "Job Executions",
+  "ordinal": 94,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html",
+  "topic_cluster": {
+    "clustering_title": "Job Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.md b/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
new file mode 100644
index 0000000..df5c568
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
@@ -0,0 +1,24 @@
+# Job Executions
+
+## Required Role Permissions
+
+Access and capabilities for the **Job Executions** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Job Executions`
+:   - None: Cannot access Provisioning: Job Executions section
+    - Read: Can access Provisioning: Job Executions section
+
+The Job Executions tab contains execution history of completed Jobs, including any process outputs and error messages. Information included in the Job Executions list includes:
+
+- Execution Status Icon
+- **Job Name - Task Name - Result Error Message:** The title of each execution includes the Job Name, Task or Workflow name (for Task and Workflow job types), and execution result error messages (when applicable) separated by hyphens (-). The title also links to the Job Execution detail page
+- **Start Date:** The date and time the Job Execution kicked off. When expanded, the start date and time of each individual Task are also shown
+- **Duration:** The time taken for the Job to complete. When expanded, the time to complete each individual Task is also shown
+- **User:** The user who executed or scheduled the Job
+
+Additional details and actions are available per execution:
+
+- Select an execution name to go to the Job Execution Detail page
+- Select the ⌃ icon at the end of the row to expand the execution and view additional details, including task process output
+- Select the 📋 icon to copy process output to local clipboard
+- Select the ⌄ icon at the end of an expanded to to collapse additional execution details
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..16ef622
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 194,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..c32da46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json b/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
new file mode 100644
index 0000000..ea86288
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+  "title": "Creating ArubaCX Network Integration",
+  "ordinal": 432,
+  "parent_title": "Managed Networks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html",
+  "topic_cluster": {
+    "clustering_title": "Creating ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md b/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
new file mode 100644
index 0000000..97a72a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
@@ -0,0 +1,21 @@
+# Creating ArubaCX Network Integration
+
+## About this task
+
+The network integration allows the user to specify the switch information. It is expected that there are 2 switches per rack acting as the top-of-rack (ToR) switches. You need to specify information for a switch pair for a rack. If there are more than 1 rack, then information for the switch pair for each rack is required.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network > Integrations.
+3. Click the Add to add a new integration.
+4. Select **HPE**Aruba CX Switches under the Networking section.   
+   ![Aruba CX Switches](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-EFC5C2DB-4496-480A-8039-50B8F31AAC5E-high.png)
+5. Enter the following details for the network integration: 
+
+   - **Name** for network integration
+   - **Username/Password** for the switches
+   - **Switch pair IP Addresses** for each pair of switches
+
+   ![Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6902768F-0D2B-472A-8F9F-6F8A7B286581-high.png)
+6. Click the Add Network Integration to create the Network Integration.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json b/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
new file mode 100644
index 0000000..3a2ac41
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+  "title": "Prerequisites",
+  "ordinal": 204,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md b/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
new file mode 100644
index 0000000..c9d8415
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
@@ -0,0 +1,7 @@
+# Prerequisites
+
+- HPE Morpheus Enterprise appliance running version 8.0.13 or higher
+- At least one pre-existing OpenShift 4.x cluster, which can communicate back to the HPE Morpheus Enterprise appliance on the HTTPS port
+- Access to a full administrator account for each cluster which will be integrated
+- Ability for the HPE Morpheus Enterprise appliance to communicate with the OpenShift API on port 6443
+- Ability for the HPE Morpheus Enterprise appliance to communicate with each provisioned VM on port 22 for SSH and on port 3389 for Windows RDP
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json b/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
new file mode 100644
index 0000000..523c740
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+  "title": "Isilon",
+  "ordinal": 523,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html",
+  "topic_cluster": {
+    "clustering_title": "Isilon",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md b/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
new file mode 100644
index 0000000..cda08b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
@@ -0,0 +1,132 @@
+# Isilon
+
+## Add Dell EMC Isilon Storage Server
+
+### About this task
+
+IMPORTANT
+
+Enable insecure mode on the NFS settings. This allows non-root ports to be used. Setting the insecure/privileged mode will require a restart of the Isilon nodes.
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Add Dell EMC Isilon File Share
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..a571fcc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 183,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..d56ad92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,14 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Host Hardware Sensor Data Collection](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json b/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
new file mode 100644
index 0000000..ddd1452
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+  "title": "Adding Volume",
+  "ordinal": 443,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md b/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
new file mode 100644
index 0000000..d228ec1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
@@ -0,0 +1,17 @@
+# Adding Volume
+
+## About this task
+
+Perform the following procedure to create a new volume:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Add button.
+3. Select the storage server to create the volume in and click Next.   
+   ![Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-88533534-DD97-4462-88F4-443E815641B6-high.png)
+4. Select the required volume type, unreplicated, CPP replicated, or APP replicated, and click Next.   
+   ![Select Type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3E92F9CE-3785-4A3B-B5EF-BAADC8E40E1C-high.png)
+5. On the Configure screen, specify the volume name, size, datastore in which the volume needs to be created, shared/unshared. You can optionally specify the server/instance to export the volume, depending on whether it is unshared/shared.
+6. Click Complete to finish adding the volume.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8DC7D478-39B9-47ED-9F9A-4B6D87200464-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json b/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
new file mode 100644
index 0000000..99fa1ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+  "title": "Network Usage",
+  "ordinal": 435,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html",
+  "topic_cluster": {
+    "clustering_title": "Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md b/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
new file mode 100644
index 0000000..e7d3aa2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
@@ -0,0 +1,15 @@
+# Network Usage
+
+Networks are attached to interfaces on a compute server. The interfaces can be the physical ports themselves or bond interfaces that combine two physical ports into an aggregated pipe. Bond interfaces provide the benefits of aggregated bandwidth on a single interface and also high availability by providing port-level redundancy.
+
+Once the decision is made on what kind of interfaces to use, networks can be chosen from the preconfigured list to attach to the network interfaces. This determines which VLANs are configured on which switch ports (or LAGs). As mentioned earlier, the primary VLAN is provisioned as an untagged VLAN, and the trunk VLANs are provisioned as tagged VLANs on the server ports.
+
+The supported bond types are:
+
+- Static Bond: This uses an L2+L3-based hash on the server OS and a static LAG on the switches.
+- LACP Bond: This uses the LACP mode on the server OS and LACP LAG on the switches.
+- Switch Independent Bond: This uses the balance-tlb mode on Linux servers and the switch-independent mode on Windows. The switch is configured as independent physical ports.
+
+**Subtopics**  
+
+- **[Specifying Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json b/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
new file mode 100644
index 0000000..77c87e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+  "title": "Trust Integrations",
+  "ordinal": 245,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html",
+  "topic_cluster": {
+    "clustering_title": "Trust Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md b/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
new file mode 100644
index 0000000..265019e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
@@ -0,0 +1,3 @@
+# Trust Integrations
+
+This area lists integrations with external services to manage secrets, keys, and certificates. New Cypher integrations can be created here. See [our guide](https://docs.morpheusdata.com/en/latest/infrastructure/keypairs_certificates/keypairs_certs.html#installing-and-integrating-an-external-cypher-appliance) on installing and integrating an external Cypher store for full details. Additionally, some other external trust services may be populated here, such as NSX certificate services.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json b/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
new file mode 100644
index 0000000..7be75f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+  "title": "Overview",
+  "ordinal": 230,
+  "parent_title": "Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md b/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
new file mode 100644
index 0000000..0cb36a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
@@ -0,0 +1,11 @@
+# Overview
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in HPE Morpheus Enterprise.
+
+## Role Requirements
+
+There are two Role permissions for the Infrastructure  >  Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage give Full, Read or No access to the Infrastructure  >  Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
+
+## Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is var/opt/morpheus/morpheus-ui/. Its is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure  >  Storage section to avoid running out of disk space on the HPE Morpheus Enterprise Appliance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json b/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
new file mode 100644
index 0000000..3695418
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+  "title": "UCS Manager",
+  "ordinal": 472,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.html",
+  "topic_cluster": {
+    "clustering_title": "UCS Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md b/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
new file mode 100644
index 0000000..c87b46d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
@@ -0,0 +1,75 @@
+# UCS Manager
+
+## Overview
+
+The HPE Morpheus Enterprise UCS Manager Integration enables UCS M B and C Chassis Inventory, VM and Container Host Bare Metal Provisioning, PXE boot with IPMI, Storage Profile, SAN Connection Profile, Server Pool, BIOS Profile, Boot Profile, Maintenance Profile, UUID Pool and Disk Group Profile sync.
+
+## Adding UCS Manager Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select UCS MANAGER from the Clouds list
+4. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   UCS MANAGER
+   :   IP or hostname of UCS Manager
+
+   USERNAME
+   :   UCS Manager User
+
+   PASSWORD
+   :   UCS Manager Password
+
+   ORGANIZATION
+   :   - EXISTING (select)
+       - NEW (create)
+         :   - ORG NAME
+               :   Enter name for the new Organization
+
+   SERVER PREFIX
+   :   String provisioned servers will be prefixed with
+
+   DATA DISK MODE
+   :   - LVM data disk
+       - Single Disk
+
+   DATA VOLUME
+   :   Defaults to `/dev/sdb` \* Check to enable SOFTWARE RAID
+
+   NET INTERFACE
+   :   Defaults to eth0
+5. Select NEXT
+6. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+7. Select NEXT
+8. Review and then Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json b/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
new file mode 100644
index 0000000..0c2fe79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+  "title": "Oracle VM",
+  "ordinal": 466,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle VM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md b/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
new file mode 100644
index 0000000..bfa1aa3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
@@ -0,0 +1,150 @@
+# Oracle VM
+
+## Add an Oracle VM Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+API URL
+:   Oracle VM API URL. ex: <https://10.20.30.40:7002/ovm/core/wsapi/rest>
+
+USERNAME
+:   Oracle VM User
+
+PASSWORD
+:   Oracle VM User Password
+
+REPOSITORY
+:   Available repositories will auto-populate upon successful authentication with the above credentials. Select appropriate repository for this Cloud.
+
+SERVER POOL
+:   Available server pools will auto-populate upon successful authentication with the above credentials. Select appropriate server pool for this Cloud.
+
+Inventory Existing Instances
+:   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..f98ee7e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 325,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..46c6dd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,68 @@
+# Provisioning
+
+## Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Show Pricing
+:   Displays or hides Pricing in Provisioning wizard and Instance and Host detail pages.
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and HPE Morpheus Enterprise will track issued sequence numbers and use the next available number each time.
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
+
+## Cloud-Init Settings
+
+HPE Morpheus Enterprise can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
+
+## Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
+
+## PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
+
+## App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
+
+## Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, HPE Morpheus Enterprise will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint (only up to v1.5.5). When selecting “manual”, HPE Morpheus Enterprise will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json b/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
new file mode 100644
index 0000000..5e3607a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+  "title": "Instance Details",
+  "ordinal": 85,
+  "parent_title": "Instances",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md b/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
new file mode 100644
index 0000000..56eedde
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
@@ -0,0 +1,53 @@
+# Instance Details
+
+The instance detail page is where you can view and fully manage an instance. To get to an instance detail page, navigate to Provisioning > Instances, and click on an Instance. Please note Instance details and actions will differ between Instance types and user permissions.
+
+There are several sections within an Instance page that provide useful capabilities to the user.
+
+![../../_images/instanceDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1E7A4007-3C1F-4E44-A046-41A0C62111AA-high.png)
+
+Summary
+:   Basic information, stats and status information
+
+    - **Availability:** The Instance availability is the percentage of time the Instance is up. When stopping Instances, the option is given to mute monitoring if you wish for intentional down time not to count against the availability
+    - **Response Time:** If listed as “N/A” (Not Applicable), the Instance does not have any Checks set against it or does not have any Checks set against it that report a response time. Agent Checks, for example, do not report a response time. Some Checks, such as Docker Checks for Docker containers, require HPE Morpheus Enterprise to ping the container which reports a response time.
+
+Deploy
+:   Track deployment history for instance types that support deployments or manually kick off a deployment (only visible for Instance Types that support deployments)
+
+Settings
+:   Some Instance Types support custom configuration settings (for example, MySQL presents the my.ini)
+
+Resources
+:   VMs, containers, or other resources associated with the Instance are listed here. Some Instance Types, such as XaaS Instances, will not have resources and the tab is not displayed
+
+Runtime
+:   View the environment variables presented to the Instances or exported to the Instances via Apps (more on this in the Apps section). Users may also see Imported environment variables that may be referenced by the running Instance.
+
+    For Instances that support load balancing and auto scaling, configure auto scaling thresholds and load balancer settings in the Scale subsection that pertain to a particular Instance.
+
+    The software subsection will show any tracked software which is Installed as part of the provisioning process and is being tracked.
+
+Storage
+:   See storage information associated with the Instance including the list of volumes and controllers which are associated with each machine that makes up the Instance.
+
+Network
+:   Useful for configuring network interfaces for your VMs or security groups which allow access to the Instance.
+
+Monitoring
+:   Quick summary of the monitoring system and all checks that were configured to test the state of the Instance. Stats views (memory, cpu, etc.) can be zoomed out to a 90-day view if desired (in global settings, ensure your stats retention setting will support this). Logs and guidance for the individual Instance are also shown in their respective subtabs.
+
+Backups
+:   Quick backup dashboard. Useful for viewing historical backups and snapshots as well as adding new backup jobs.
+
+History
+:   See historical information related to automation which has been run against the Instance. This is useful for examining automation which was run as part of a phase of a Provisioning Workflow. Users can also drill into the Workflows to examine individual Tasks, including viewing the output from these Tasks to confirm success or troubleshoot issues.
+
+Costing
+:   Invoices pertaining to the Instance are displayed here. See the Instance level or host level invoices along with individual line items. In the History subtab view historical pricing data to monitor trends. In the Prices subtab view any prices which have been created and used to build a metered costing profile for the workload.
+
+Console
+:   Access the Instance or container via a client-less Console supporting SSH, RDP, VNC, or even hypervisor-level remote consoles.
+
+Wiki
+:   View the Wiki page for this Instance or edit the existing Wiki page (which may currently be blank). The content field supports markdown formatting, see the main Wiki section of HPE Morpheus Enterprise documentation for additional details.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..61cfe59
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 511,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..f3c4a88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,160 @@
+# HPE Aruba CX DSS
+
+## Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus Enterprise Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a HPE Morpheus Enterprise `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for HPE Morpheus Enterprise environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM Cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. HPE Morpheus Enterprise integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM Hosts in the HVM Cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM Cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
+
+## Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM Hosts are added or removed from the HVM Cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
+
+## Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in HPE Morpheus Enterprise
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM Cluster
+
+  - Ensure all hosts within the HVM Cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- HPE Morpheus Enterprise appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the HPE Morpheus Enterprise Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
+
+## Adding HPE Aruba CX DSS Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+### Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
+
+## Manage Security Groups and Rules in Morpheus
+
+To manage security groups and rules in Morpheus, follow these steps:
+
+1. Navigate to Infrastructure > Network > Security Groups
+2. Select + ADD
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7883AC52-480A-4E33-AB01-6703E3A41809-high.png)
+3. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2145D633-F35B-41FC-950C-363353E38E8B-high.png)
+4. Within the new Security Group, select + Add Rule
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2BA30350-BAC9-420C-90A3-381E66B9AF9D-high.png)
+5. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CA593188-8380-492C-AAA7-08766D278427-high.png)
+
+## Create HPE ANW DSS Port Group Network
+
+### About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-02143765-1935-4568-A755-9A6B134CA122-high.png)![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BF4B2385-7813-4CB8-912B-DCF724834F47-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
+
+## Delete HPE ANW DSS Port Group Network
+
+### About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
+
+## View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json b/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
new file mode 100644
index 0000000..ec20e97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+  "title": "ESXi",
+  "ordinal": 394,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.html",
+  "topic_cluster": {
+    "clustering_title": "ESXi",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md b/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
new file mode 100644
index 0000000..d0029da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
@@ -0,0 +1,159 @@
+# ESXi
+
+## About this task
+
+The ESXi Cloud type enables managing and provisioning to ESXi hosts, even without the ESXi API enabled.
+
+IMPORTANT
+
+The VMware ESXi integration is for adding a single ESXi / vSphere Hypervisor host. If you have vCenter please use the VMWare vCenter cloud type for full vSphere integraiton features.
+
+To get started with VMware ESXi, simply add a VMware ESXi Cloud in either the Infrastructure  >  Clouds or Infrastructure  >  Groups section.
+
+## Procedure
+
+1. Select `+ Create Cloud` Button
+2. Select ESXi from the Add Cloud modal
+3. Select NEXT
+4. Provide the following information. 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   - ESXi Host name or IP address
+   - Username ( This is normally root )
+   - Password
+
+## Results
+
+NOTE
+
+If you receive the message “Error! Invalid cloud config” Please ensure you have ssh enabled on the ESXi host.
+
+## Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+## CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+## INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+## Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+IMPORTANT
+
+ESXi provisioning require a vmx file, which is not included in an OVF/OVA export from vCenter. A proper vmx file must be included when adding a vmdk/ovf/ova image to Virtual Images in Morpheus for successful provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..e0cb1b1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 188,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json b/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
new file mode 100644
index 0000000..3262739
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+  "title": "morpheus-ctl tips",
+  "ordinal": 25,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html",
+  "topic_cluster": {
+    "clustering_title": "morpheus-ctl tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md b/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
new file mode 100644
index 0000000..a393646
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
@@ -0,0 +1,63 @@
+# morpheus-ctl tips
+
+`morpheus-ctl` is useful beyond reconfigures and starting the ui, and many commands can be run across all services, or scoped to a singe service.
+
+Some common commands include:
+
+morpheus-ctl status
+:   Lists all the installed services and their current status
+
+morpheus-ctl start (service)
+:   This starts all services if no service is specified, or starts the specified service. For example,
+
+    - `morpheus-ctl start/stop/restart/kill` on an all-in-one appliance will start, stop, restart or kill mysql, opensearch, rabbitmq, check-server, guacd and the morpheus-ui, one by one.
+    - `morpheus-ctl start/stop/restart/kill morpheus-ui` will only start, stop, restart or kill the morpheus-ui service, leaving the other service in their current state. Same goes for `morpheus-ctl start/stop/restart/kill mysql`, `morpheus-ctl start/stop/restart/kill opensearch` etc.
+
+`morpheus-ctl` commands:
+
+```
+```
+General Commands:  
+  cleanse  
+    Delete *all* morpheus data, and start from scratch.  
+  help  
+    Print this help message.  
+  reconfigure  
+    Reconfigure the application.  
+  show-config  
+    Show the configuration that would be generated by reconfigure.  
+  uninstall  
+    Kill all processes and uninstall the process supervisor (data will be preserved).  
+ Service Management Commands:  
+   graceful-kill  
+     Attempt a graceful stop, then SIGKILL the entire process group.  
+   hup  
+     Send the services a HUP.  
+   int  
+     Send the services an INT.  
+   kill  
+     Send the services a KILL.  
+   once  
+     Start the services if they are down. Do not restart them if they stop.  
+   restart  
+     Stop the services if they are running, then start them again.  
+   service-list  
+     List all the services (enabled services appear with a *.)  
+   start  
+     Start services if they are down, and restart them if they stop.  
+   status  
+     Show the status of all the services.  
+   stop  
+     Stop the services, and do not restart them.  
+   tail  
+     Watch the service logs of all enabled services.  
+   term  
+     Send the services a TERM.  
+ Opensearch Commands:  
+   open-util  
+     Backup/Restore OpenSearch data  
+ Firewall Commands:  
+   firewall-enable-blocking  
+     Enables firewall blocking mode.
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json b/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
new file mode 100644
index 0000000..2ef2f93
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+  "title": "Getting Started with Terraform Instance Types",
+  "ordinal": 369,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started with Terraform Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md b/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
new file mode 100644
index 0000000..983152a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
@@ -0,0 +1,203 @@
+# Getting Started with Terraform Instance Types
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+## Terraform Instance Types in Action
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+## Spec Templates
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+### AWS Subnet by Count
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+### AWS Terraform Default Vars
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+### AWS Provider Role Assume
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+### AWS Terrform Locals
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+### AWS VPC
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+## Inputs and Option Lists
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+## Instance Type
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+## Layout
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+## Provisioning
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+## Review the New Instance
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json b/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
new file mode 100644
index 0000000..368eec6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+  "title": "Helm Blueprints",
+  "ordinal": 134,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html",
+  "topic_cluster": {
+    "clustering_title": "Helm Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md b/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
new file mode 100644
index 0000000..7edf706
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
@@ -0,0 +1,27 @@
+# Helm Blueprints
+
+If you’re using Helm Charts to manage Kubernetes applications, HPE Morpheus Enterprise allows you to bring them in from a Git repository as a Blueprint. The selected repository must be integrated with HPE Morpheus Enterprise before creating the Blueprint.
+
+To create a new Helm Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Helm. Click guilabel:NEXT.
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+In the Helm Configuration section, complete the following fields as needed to sync in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **CHART PATH:** The path to the folder within the repository containing your configuration files, enter “./” if this is the top level folder within the repository
+- **CONFIG:** Config files within your selected folder are displayed here for confirmation
+
+Once finished, click COMPLETE.
+
+Your new Helm Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..1c71898
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 241,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..ffc566b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,65 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+## Add Existing Key Pair
+
+### About this task
+
+To generate a existing Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
+
+## Generate Key Pair
+
+### About this task
+
+To generate a Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+### Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
+
+## Delete Key Pair
+
+### About this task
+
+To Delete Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json b/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
new file mode 100644
index 0000000..7590b6a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+  "title": "OpenShift Clusters",
+  "ordinal": 202,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html",
+  "topic_cluster": {
+    "clustering_title": "OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md b/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
new file mode 100644
index 0000000..6793095
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
@@ -0,0 +1,11 @@
+# OpenShift Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html)**
+- **[Adding the OpenShift Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html)**
+- **[Adding OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html)**
+- **[Provisioning into OpenShift](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json b/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
new file mode 100644
index 0000000..6604651
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+  "title": "SELinux",
+  "ordinal": 10,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md b/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
new file mode 100644
index 0000000..633687f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
@@ -0,0 +1,7 @@
+# SELinux
+
+If not required by organizational policy, we recommend setting SELinux to “Permissive” or “Disabled” modes to prevent any unnecessary security-related issues. HPE Morpheus Enterprise versions 3.6.0 and higher do support “Enforcing” mode if it is required by your organization due to IT policies. Set the mode appropriately prior to running the HPE Morpheus Enterprise installer and it will make the required changes based on your chosen SELinux context.
+
+IMPORTANT
+
+Setting SELinux to “Enforcing” mode requires policies to be configured correctly in order for the HPE Morpheus Enterprise appliance to function correctly.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json b/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
new file mode 100644
index 0000000..b5de7a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+  "title": "Code",
+  "ordinal": 96,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html",
+  "topic_cluster": {
+    "clustering_title": "Code",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md b/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
new file mode 100644
index 0000000..ac6d5b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
@@ -0,0 +1,37 @@
+# Code
+
+NOTE
+
+In v5.3.2+, `provisioning/deployments` is moved to `provisioning/code`.
+
+Provisioning > Code contains the Repositories, Deployments and Code Integrations sections.
+
+## Required Role Permissions
+
+Access and capabilities for the **Code** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents.
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents.
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
+
+**Subtopics**  
+
+- **[Repositories](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html)**
+- **[Import and Export](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html)**
+- **[Deployments](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html)**
+- **[Code Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json b/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
new file mode 100644
index 0000000..1d4e228
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+  "title": "Github",
+  "ordinal": 482,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html",
+  "topic_cluster": {
+    "clustering_title": "Github",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md b/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
new file mode 100644
index 0000000..5a5d8cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
@@ -0,0 +1,92 @@
+# Github
+
+Integrate your Github account with HPE Morpheus Enterprise and have access to all your public and private repositories within the platform. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Integrated Github repositories also populate the Code list page (Provisioning > Code) where repositories can be browsed and individual files can be viewed. Repositories can be configured as [import and export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html?highlight=import#import-and-export) targets from Code detail pages as well. Each time code from your repositories is invoked in Tasks, Workflows, Spec Templates, and more, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Generating a Personal Access Token (Classic)
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens (described in the next section). To create a new access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Tokens (classic)”
+7. Click Generate new token
+8. Click “Generate new token (classic)”
+9. Give the new token at least access to everything in the “repo” scope
+10. Click Generate token
+11. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+We recommend using a long-lived token, Github even includes the option to have no expiration on your tokens (for classic personal access tokens only, not fine-grained tokens). Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Generating a Fine-Grained Token
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens. To create a new fine-grained access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Fine-grained tokens”
+7. Click Generate new token
+8. Give the token access to all repositories unless you will only need to work with specific repositories within HPE Morpheus Enterprise
+9. Click Generate token
+10. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+Fine-grained tokens can be created with an expiration date of up to one year. Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Creating an Integration
+
+### About this task
+
+New Github integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need a Github access token to complete this step, see the prior section for instructions on obtaining a Github access code.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Github
+4. Configure the following: 
+
+   - NAME: A friendly name for the Github integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, this Github integration is active and any code repositories are available for building HPE Morpheus Enterprise automation and other constructs within the platform
+   - USERNAME: The username for your Github account
+   - PASSWORD: Copy your access token here rather than in the “ACCESS TOKEN” field. See the “Important” box below for additional details
+   - ACCESS TOKEN: Do not use this field. See the “Important” box below for additional details
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
+
+### Results
+
+IMPORTANT
+
+Your access token should be pasted into the PASSWORD field and not the ACCESS TOKEN field. If the ACCESS TOKEN field is used, the repository will create successfully and many features will work. However, in Code detail pages (Provisioning > Code > Selected code detail page), you will not be able to browse files in private Github repositories unless the access token is pasted into the PASSWORD field. New Github integrations should be created by pasting the access token in the PASSWORD field and the ACCESS TOKEN field should be ignored.
+
+NOTE
+
+In certain cases, it can take several seconds for the integration process to complete and the ADD INTEGRATION modal to be dismissed.
+
+## Viewing an Integrated Github Account
+
+When authentication is successful, click into the new Github integration from the list of available integrations. The Organizations tab will list each organization the Github account is associated with. The Repositories tab lists all public and private repositories which are associated with the account. We can also click in to each repository to view its files and folders, as well as create specific types of automation or Spec Templates from the files directly in this view.
+
+![../../_images/github.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-19D7B591-B18D-4BB5-A378-425A0110A7C7-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json b/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
new file mode 100644
index 0000000..2619779
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+  "title": "Overview",
+  "ordinal": 105,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md b/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
new file mode 100644
index 0000000..512aba1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
@@ -0,0 +1,7 @@
+# Overview
+
+There are many Task Types available, including scripts added directly, scripts and templates from the Library section, recipes, playbooks, puppet agent installs, and http (api) calls. Tasks are primarily created for use in Workflows, but a single Task can be executed on an existing instance via Actions  >  Run Task.
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json b/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
new file mode 100644
index 0000000..58726a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+  "title": "Compute",
+  "ordinal": 210,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md b/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
new file mode 100644
index 0000000..e2ae8e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
@@ -0,0 +1,23 @@
+# Compute
+
+![../../_images/infra_compute_header_5.4.3.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-04AE9DB4-27C9-40E0-8E37-1BCFA3CD8C32-high.png)
+
+NOTE
+
+The Infrastructure `Hosts` page from previous versions has been renamed to `Compute` and updated with `Container` and `Resource` sections.
+
+The Infrastructure  >  Compute section provides a universal stage for viewing and managing Hosts, Virtual Machines, Containers, Resources, and Bare Metal across Clouds.
+
+In this section you can:
+
+- View & Manage and Hosts, Virtual Machines, Containers, Resources, Bare Metal and Hypervisors
+- Add manual Virtual Machines and Bare Metal Hosts
+- Convert Hosts, Virtual Machines and Bare Metal to Managed
+
+**Subtopics**  
+
+- **[Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html)**
+- **[Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html)**
+- **[Resources](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html)**
+- **[Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json b/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
new file mode 100644
index 0000000..5bafccf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+  "title": "Features",
+  "ordinal": 205,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md b/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
new file mode 100644
index 0000000..624c03c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
@@ -0,0 +1,14 @@
+# Features
+
+- Adds a new Cluster type, which is used to onboard pre-existing OpenShift clusters into HPE Morpheus Enterprise
+- Enables inventory synchronization for workloads provisioned outside of HPE Morpheus Enterprise in the OpenShift console
+- Monitor high-level cluster health details such as host numbers, alarms, and high CPU, memory or disk use situations
+- Monitor individual host and VM health details such as high CPU, memory, disk use, or network I/O situations
+- Onboard network objects, device-agnostic storage objects, and virtual images to enable OpenShift provisioning from the HPE Morpheus Enterprise provisioning wizard UI
+- Supports IPv4 and IPv6 networking
+- Adds new Instance Type to the HPE Morpheus Enterprise provisioning wizard for easy provisioning of new OpenShift virtualized workloads
+- VM provisioning supports the use of existing templates and service plans
+- Interface with Morpheus-type IP Pools or IP Pools sourced from IPAM integrations throughout the lifecycle of OpenShift workloads
+- Utilize the HPE Morpheus Enterprise automation engine for provisioning and for day two operations across the Instance lifecycle
+- Supports HPE Morpheus Enterprise labels and tagging features for resource organization
+- Provides guest console access into OpenShift-hosted virtual machines
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..80a1743
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 224,
+  "parent_title": "Network",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..8d59ca1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,49 @@
+# Integrations
+
+## Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations. These services can also be added in the Administration > Integrations section.
+
+The following integrations are currently supported:
+
+Networking
+
+- Cisco ACI
+- VMWare NSX
+
+IPAM
+
+- Infoblox
+- Bluecat
+- phpIPAM
+
+Security
+
+- Cisco ACI
+
+DNS
+
+- Microsoft DNS
+- PowerDNS
+- Route 53
+
+## Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json b/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
new file mode 100644
index 0000000..1069f3c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+  "title": "Policy Types",
+  "ordinal": 317,
+  "parent_title": "Policies",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md b/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
new file mode 100644
index 0000000..b205c81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
@@ -0,0 +1,117 @@
+# Policy Types
+
+Approve Delete
+:   Sets an approval requirement for deleting Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow. On delete request, Instances will be shut down and only deleted if approved.
+
+Approve Provision
+:   Sets an approval requirement for provisioning Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Reconfigure
+:   Sets an approval requirement for reconfiguring Instances and servers within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Workflow Execute
+:   If enabled, when Workflows are executed on workloads within the Policy scope, an Approval is generated. This could apply when a Workflow is executed from the Workflows list page or from the detail page for an Instance or server. Approvals can be targeted to HPE Morpheus Enterprise internal Approvals or targeted to a third-party integration (such as ServiceNow). The Workflow will not begin to execute until after the approval is granted.
+
+Backup Creation
+:   Disable or enable the ability to create a backup when provisioning an instance.
+
+Backup Targets
+:   A master account can determine storage provider options for backups with Backup Targets policies.
+
+Budget
+:   Sets a maximum total combined price for all instances in the Group, Cloud, Tenant or owned by the User this policy is applied to.
+
+Cluster Resource Name
+:   The name of Cluster hosts (master and workers) when creating Kubernetes, Docker and KVM Clusters. Pre-populates a fixed or editable Resource Name value for the cluster using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Cypher Access
+:   Granularly set LIST, READ, WRITE, and DELETE access to arbitrary Cypher secret paths scoped globally or to specific Roles and Users. See the section below for a guide to establishing a Cypher access policy.
+
+Delayed Delete
+:   Delayed Delete Policies allow for soft deletion of Instances and Apps. Instead of deleting immediately, Instances and Apps with a Delayed Delete policy applied will be shutdown upon deletion request and hidden by default from the UI. The Instance/App will then be in `Pending Removal` status. In order to see Instances pending deletion on the Instances list page (Provisioning > Instances), you must filter for “Pending Removal” status. These Instances will not show when filtered for “All Statuses”
+
+Expiration
+:   Sets an expiration timeframe in days after which the Instance will be deleted. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration. See HPE Morpheus Enterprise [Knowledge Base](https://support.morpheusdata.com/s/article/How-to-create-an-extensions) for more information about Expiration policies
+
+File Share Storage Quota
+:   Sets a Storage Quota for File Share usage (in GB) to scoped User, Role, Tenant or Global.
+
+Hostname
+:   The `hostname` or `computer name` which is set in the OS and DNS. On some platforms, hostnames are restricted by length, spaces, and/or special characters. Pre-populates a fixed or editable name for hostnames/machine names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Instance Name
+:   Pre-populates a fixed or editable name for Instance Names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings. Note that it’s not recommended administrators include “>”, “<”, “%”, “$”, or “=” in naming policies
+
+Instance Networks
+:   When an Instance is provisioned within the scope of the Policy (Group or Cloud scoping is supported), the network selected on the Policy is automatically set and locked in the provisioning wizard to force provisioning onto the selected network.
+
+Max Containers
+:   Sets the max number of Containers for the Group or Cloud the Policy is added to.
+
+Max Cores
+:   Sets the max number of total of Cores combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Hosts
+:   Sets the max number of total Hosts in the Group or Cloud the Policy is added to.
+
+Max Load Balancer Pools
+:   Sets the max number of load balancer pools within the policy scope
+
+Max Memory
+:   Sets the max number of total of RAM combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Pool Members
+:   Sets the maximum number of members in a load balancer pool
+
+Max Snapshots
+:   Set the maximum number of Snapshots that may be stored for each Instance or VM within the scope. Once the limit is met, HPE Morpheus Enterprise will warn the user when attempting to create more snapshots until the number is reduced
+
+Max Storage
+:   Sets the max number of total of Storage combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Virtual Servers
+:   Sets the maximum number of virtual servers within the policy scope
+
+Max VMs
+:   Sets the max number of Virtual Machines for the Group or Cloud the Policy is added to.
+
+Message of the Day (MOTD)
+:   Message of the Day”” Policy for displaying Alerts in HPE Morpheus Enterprise. Configurable as a pop-up or full-page notification with Info, Warning and Critical message types.
+
+    NOTE
+
+    Requires role permission: `Admin: Message Of the Day` set to “Full” to create and manage MOTD Policies.
+
+Network Quota
+:   Limits the number of networks that can be created within the policy’s scope
+
+Object Storage Quota
+:   Sets a Storage Quota for Object Storage usage (in GB) to scoped User, Role, Tenant or Global.
+
+Power Scheduling
+:   Adds a Power Schedule for the Instances in a Group or Cloud. Power Schedules can be created in Library > Automation > Power Scheduling
+
+Router Quota
+:   Limits the number of routers that can be created within the policy’s scope
+
+Shutdown
+:   Sets a shutdown timeframe in days upon provision after which the Instance will be stopped. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration.
+
+Storage Server Storage Quota
+:   Sets a Storage Quota for selected Storage Server (in GB), applied Globally or per specified Tenants.
+
+Tags
+:   Requires the user to add compliant Tags at provision time, this can be enforced on a strict or passive basis
+
+    NOTE
+
+    Tag scanning and enforcement is currently only available for Azure, Amazon, Google, and VMware clouds. For a more comprehensive guide on implementing Tag Policies, see the associated article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-work-with-cloud-tagging-policies?language=en_US).
+
+User Creation
+:   Controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+User Group Creation
+:   Forces User Creation of members in the selected User Group during Provisioning.
+
+Workflow
+:   Workloads provisioned within the scope of the Policy will have the indicated Workflow applied and the Tasks executed within the proper phase of the Instance lifecycle
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json b/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
new file mode 100644
index 0000000..4cb25b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+  "title": "NSX Cloud",
+  "ordinal": 512,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html",
+  "topic_cluster": {
+    "clustering_title": "NSX Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md b/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
new file mode 100644
index 0000000..a4f1b53
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
@@ -0,0 +1,31 @@
+# NSX Cloud
+
+NSX Cloud is a networking solution that allows administrators to define networking and security policies for applications running in private and public clouds. When integrated with HPE Morpheus Enterprise, users can apply an NSX Cloud integration with VMware vCenter-type Clouds. This offers robust syncing and manipulation of NSX Cloud constructs as well as the ability to consume those networks when provisioning to VMware Cloud targets.
+
+## Features
+
+- Sync and manage DHCP servers
+- Sync and manage DHCP relays
+- Sync and manage network segments
+- Sync and manage distributed firewall rules
+- Sync and manage tier-1 routers
+- Sync and manage groups, including management groups and compute groups
+- Integration with VMware-type Clouds
+
+## Integrating with VMware Clouds
+
+Integration with a VMware Cloud requires the Cloud integration to be pre-existing. If you need to integrate a VMware Cloud first, refer to the [VMware Cloud integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html) in HPE Morpheus Enterprise UI documentation for full details. If you are creating the VMware Cloud now, bear in mind that you will need to update firewall inbound rules to allow the HPE Morpheus Enterprise appliance to connect with VMware. If this step is not done, any attempts to create that Cloud integration will fail. Log into the NSX Cloud web console and click on the Security tab. Within the security tab, go to the Gateway Firewall section and the Management Gateway tab within it. Edit the list of sources for your vCenter inbound rules. The IP address for the HPE Morpheus Enterprise appliance should be among the allowed inbound addresses.
+
+To begin a new NSX Cloud integration, navigate to Infrastructure > Network > Integrations. Click + ADD and then click “NSX Cloud”. Make the following configurations to create the integration with NSX Cloud:
+
+- **NAME:** A friendly name for the NSX Cloud integration in HPE Morpheus Enterprise
+- **VISIBILITY:** This option is only available from the Master Tenant. Select “Public” to make the NSX Cloud integration available to all Tenants. Select “Private” to reserve the integration for the Master Tenant
+- **API HOST:** The API access URL for NSX Cloud. Your API URL will look something like this: <https://nsx-xx-xx-xx-xx.rp.vmwarevmc.com/vmc/reverse-proxy/api/orgs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/sddcs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx>
+- **API KEY:** An API token granting sufficient access for HPE Morpheus Enterprise to work with all relevant NSX constructs
+- **CLOUD:** Select the VMware Cloud integration that NSX Cloud should integrate with
+
+Once done, click ADD NETWORK INTEGRATION. After a brief moment, the new integration will be created and will appear alongside other network integrations on the network integration list page. We can verify that NSX Cloud and the VMware Cloud are integrated by editing the VMware Cloud (Infrastructure > Clouds > Selected VMware Cloud > EDITbutton). Expand the Advanced Options panel of the EDIT CLOUD modal and the NSX Cloud integration should be set under the NETWORK MODE configuration.
+
+## Managing NSX Cloud
+
+With the integration complete, you can now examine the detail section for the new integration. From the network integration list page (Infrastructure > Network > Integrations), select the NSX Cloud integration that was just created. From this section, we can create, manage, and delete DHCP servers and relays, network segments, firewall rules, tier-1 routers, and groups.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.json b/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.json
new file mode 100644
index 0000000..6b188f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+  "title": "Windows OS Imaging",
+  "ordinal": 412,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E55D4270-ED77-4161-8712-45824C891713.html",
+  "topic_cluster": {
+    "clustering_title": "Windows OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.md b/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.md
new file mode 100644
index 0000000..9898e36
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E55D4270-ED77-4161-8712-45824C891713.md
@@ -0,0 +1,38 @@
+# Windows OS Imaging
+
+This section provides guidance and requirements for deploying **Windows Server on bare metal** using Morpheus Enterprise. It covers required virtual image settings, Windows-specific boot considerations, current licensing limitations, and high-level troubleshooting guidance for failed installations.
+
+The following Windows distributions are supported for deployment:
+
+- Windows Server 2019
+- Windows Server 2022
+- Windows Server 2025
+
+## Virtual Image Configuration
+
+When adding a Windows ISO to the **Morpheus Virtual Images Library**, the following settings **must** be configured:
+
+- Is Cloud Init Enabled: Unchecked
+- Cloud Guest Customization: Checked
+- Sysprepped / Generalized Image: Checked
+- Install Agent: Checked
+- Advanced
+  - VM Tools Installed: Checked
+
+## Windows Install Image Index
+
+By default, Morpheus installs Image Index 2, which typically corresponds to Windows Server Standard (Desktop Experience).
+
+To deploy a different Windows edition:
+
+1. Navigate to Library > Operating Systems.
+2. Add a new Operating System entry with **Platform = Windows**.
+3. Specify the desired Windows Install Index.
+4. Complete the required fields (Vendor, OS Version, Category, OS Name, Codename, OS Family).
+5. Associate the Windows Virtual Image with this Operating System.
+
+You can use the existing Windows Operating System as reference templates.
+
+**Subtopics**  
+
+- **[Boot Prompt Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json b/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
new file mode 100644
index 0000000..ba4e5f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+  "title": "Tenant Role Permission Sections",
+  "ordinal": 298,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md b/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
new file mode 100644
index 0000000..8bb3768
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
@@ -0,0 +1,34 @@
+# Tenant Role Permission Sections
+
+Features
+:   Controls Tenant access level for sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Clouds
+:   Controls Tenant access level for Clouds. This list includes Clouds integrated from the Master Tenant and shared publicly. Tenants given this Tenant Role will have either Full, Read, or None access levels to a given Cloud. See the section below for more information on Cloud Access levels.
+
+Instance Types
+:   Controls Tenant access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls Tenant access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls Tenant access for each report type in the Reports section (Operations > Reports). The Tenant must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls Tenant access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls Tenant access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters within the associated Tenant
+
+VDI Pools
+:   Controls Tenant access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls Tenant access to Workflows. Only selected Workflows will be shared down to Tenants having the associated Role
+
+Tasks
+:   Controls Tenant access to Tasks. Only selected Tasks will be shared down to Tenants having the associated Role
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json b/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
new file mode 100644
index 0000000..860f33f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+  "title": "Provisioning a Workload",
+  "ordinal": 182,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md b/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
new file mode 100644
index 0000000..8718650
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. The system default Ubuntu Instance Type contains a compatible Layout for HVM deployment. Add an Instance from the Instances list page (Provisioning > Instances). After selecting the Instance Type, choose a Group that allows for selection of the HPE Morpheus Enterprise-type Cloud containing the HVM cluster.
+
+![../../_images/groupCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-87BE27BB-2F87-4323-B45A-8A8D0C89DE4B-high.png)
+
+After moving to the next tab, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the Ceph volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+![../../_images/configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-36A8D9F5-3920-45A7-A6A6-1803A8897B35-high.png)
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json b/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
new file mode 100644
index 0000000..eaec917
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+  "title": "Roles and Identity Sources",
+  "ordinal": 295,
+  "parent_title": "Roles",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md b/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
new file mode 100644
index 0000000..9ab871a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to HPE Morpheus Enterprise for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the HPE Morpheus Enterprise role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within HPE Morpheus Enterprise. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Tenant management or user management in Administration > Tenants or Administration > Users, and has to be configured on a per-tenant basis. Additionally, administrators may opt to lock users to their mapped role in HPE Morpheus Enterprise or keep the roles unlocked to manually administer roles in one-off scenarios.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json b/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
new file mode 100644
index 0000000..ad79050
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+  "title": "Importing Pre-Provisioned Server",
+  "ordinal": 419,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html",
+  "topic_cluster": {
+    "clustering_title": "Importing Pre-Provisioned Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md b/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
new file mode 100644
index 0000000..1249b22
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
@@ -0,0 +1,13 @@
+# Importing Pre-Provisioned Server
+
+Importing a Pre-Provisioned server enables administrators to bring existing physical servers and associated resources (networks and storage) into HPE Morpheus. This is the initial step in migrating an existing workload cluster into Morpheus management. It is completed in two phases:
+
+- **Import**: Import existing servers as Pre-Provisioned resources.
+- **Convert to Managed**: Convert imported servers into managed instances, creating Morpheus instances with associated network and storage attachments.
+
+This process is performed one workload cluster at a time, and each cluster can contain one or more servers. Once the initial server is converted, additional imported servers can be added to the same instance using the Add Node operation.
+
+**Subtopics**  
+
+- **[Import Pre-Provisioned Servers](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html)**
+- **[Add Additional Nodes to the Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json b/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
new file mode 100644
index 0000000..c4626bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+  "title": "Deleting Volume",
+  "ordinal": 444,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md b/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
new file mode 100644
index 0000000..926bfdc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
@@ -0,0 +1,12 @@
+# Deleting Volume
+
+## About this task
+
+This procedure allows the users to delete a volume. A volume can be deleted only after it is detached from all the servers.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Delete for the volume to be deleted.
+3. Click the Delete on the confirmation screen.   
+   ![Delete Volume](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4385EF29-CF09-4386-B7D5-20D68EC1B8F9-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json b/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
new file mode 100644
index 0000000..8a423df
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+  "title": "Bare Metal",
+  "ordinal": 215,
+  "parent_title": "Compute",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html",
+  "topic_cluster": {
+    "clustering_title": "Bare Metal",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md b/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
new file mode 100644
index 0000000..86a2cbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
@@ -0,0 +1,10 @@
+# Bare Metal
+
+![../../_images/infra_compute_header_bm_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-26D91B4A-96E5-45CF-AC5E-4234F1F3AA28-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Bare Metal hosts are from discovered, PXE Boot or manually added Bare Metal hosts. Bare Metal hosts that are also Hypervisors will be listed in the Hosts section.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json b/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
new file mode 100644
index 0000000..9ea94c5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+  "title": "Networks Configuration",
+  "ordinal": 433,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html",
+  "topic_cluster": {
+    "clustering_title": "Networks Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md b/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
new file mode 100644
index 0000000..81b856c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
@@ -0,0 +1,16 @@
+# Networks Configuration
+
+Once the network integration is created, networks can be created using the specific network integration that was created. Networks essentially define the VLAN that they represent along with other attributes such as the subnet’s IPv4 prefix, IP address allocation method, gateway address, DNS, etc. The screenshot below shows those details.
+
+The VLAN Trunks specifies the trunk VLANs to be added when this network is consumed by an instance. The VLAN ID field represents the primary VLAN for this network. This VLAN is configured as the untagged VLAN when this network is consumed by an instance.
+
+The Network Service corresponds to the network integration that was created. This specifies that the network is to be created in the infrastructure (switches) specified in the network integration selected.
+
+The Private checkbox specifies that the network is a private network. By default, all networks are public. If private is selected, the primary VLAN in this network is not configured on the uplink connection. This would render them unreachable from outside of the cloud infrastructure. This is typically used for workload networks that are used to communicate between only the workload servers and other infrastructure within the private cloud.
+
+The configuration of a network will result in the primary VLAN in that network being provisioned on the network switches. The server ports are configured when those networks are consumed during the provisioning of a compute instance.
+
+**Subtopics**  
+
+- **[Creating Network Using the ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html)**
+- **[Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json b/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
new file mode 100644
index 0000000..429f1cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+  "title": "Add FortiADC load balancer",
+  "ordinal": 500,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html",
+  "topic_cluster": {
+    "clustering_title": "Add FortiADC load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md b/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
new file mode 100644
index 0000000..5d199df
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
@@ -0,0 +1,48 @@
+# Add FortiADC load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **FortiADC**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![FortiADC lb](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-70A960BC-376C-493B-A101-3E02EB65C9C2-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the FortiADC API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the FortiADC API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter FortiADC service account username.
+   :   **PASSWORD \***: Enter FortiADC service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new FortiADC Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new FortiADC Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new FortiADC Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json b/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
new file mode 100644
index 0000000..5a24bd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+  "title": "Add Additional Nodes to the Instance",
+  "ordinal": 422,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Add Additional Nodes to the Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md b/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
new file mode 100644
index 0000000..ff8bbc9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
@@ -0,0 +1,20 @@
+# Add Additional Nodes to the Instance
+
+## About this task
+
+To convert a Pre-Provisioned server into a fully provisioned node, and to make it part of an existing instance, the Add Node action is used, from the context of the Instance to which it is desired to be added.
+
+Once an instance is created with the first converted node, you can add other imported servers to the same instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the newly created instance.
+3. Click Add Node. ![Add node action](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-E34393DB-6064-4C8B-B3CA-6AC91E7546D5-high.png)
+4. Select Pre-Provisioned.
+5. Choose the imported server and provide the required details.
+6. Click Execute. ![Execute Action](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CCCDD2C8-A5AF-4EBD-9902-85ACA1A99155-high.png)
+
+## Results
+
+This converts the selected imported server into a managed node and adds it to the existing instance.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json b/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
new file mode 100644
index 0000000..fee232d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+  "title": "User Guides",
+  "ordinal": 360,
+  "parent_title": "Guides",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html",
+  "topic_cluster": {
+    "clustering_title": "User Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md b/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
new file mode 100644
index 0000000..dd9e1a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
@@ -0,0 +1,18 @@
+# User Guides
+
+**Subtopics**  
+
+- **[Getting started with Morpheus and AWS](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html)**
+- **[Getting started with HPE Morpheus Enterprise and VMware](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html)**
+- **[Getting started with HPE Morpheus Enterprise and Azure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html)**
+- **[Automated Single-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html)**
+- **[Automated Multi-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html)**
+- **[Adding Functionality Through Operational Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html)**
+- **[Creating XaaS Instance Types with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html)**
+- **[Morpheus Virtual Desktops](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html)**
+- **[Getting Started with Terraform Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html)**
+- **[Backing Up and Restoring HPE Morpheus Enterprise Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html)**
+- **[Cloud Resource Tagging with Morpheus](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html)**
+- **[Cypher Policies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-0060B753-B50F-4F2A-A500-BABB38426A84_2.html)**
+- **[Configuring Access with Clouds, Groups, and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html)**
+- **[Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json b/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
new file mode 100644
index 0000000..daa646d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+  "title": "Add Azure load balancer",
+  "ordinal": 494,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html",
+  "topic_cluster": {
+    "clustering_title": "Add Azure load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md b/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
new file mode 100644
index 0000000..794c532
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
@@ -0,0 +1,27 @@
+# Add Azure load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Azure Load Balancer**. 
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Azure LB](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C6A8AF5C-33DF-49FE-9EEA-C205AE35F54B-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions.
+
+   RESOURCE GROUP
+   :   Select the Resource Group for the load balancer.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json b/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
new file mode 100644
index 0000000..edffd72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+  "title": "Delete SSL Certificate",
+  "ordinal": 244,
+  "parent_title": "Trust",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html",
+  "topic_cluster": {
+    "clustering_title": "Delete SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md b/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
new file mode 100644
index 0000000..be44533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
@@ -0,0 +1,11 @@
+# Delete SSL Certificate
+
+## About this task
+
+To Delete SSL Certificate:
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected SSL Certificate
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..504af75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 169,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..94c8d83
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,191 @@
+# Clouds
+
+## Overview
+
+Clouds are integrations or connections to public, private, hybrid clouds, or bare metal servers. Clouds can belong to many groups and contain many hosts. The clouds view includes clouds status, statistics, tenant assignment, and provides the option to add, edit, delete new clouds. HPE Morpheus Enterprise supports most Public Clouds and Private Clouds.
+
+### Supported Cloud Types
+
+- Alibaba Cloud
+- Amazon
+- Azure (Public)
+- Azure Stack (Private)
+- Canonical MaaS
+- Cloud Foundry
+- Dell (Cloud type for PXE and manually added Dell EMC Hosts)
+- DigitalOcean
+- Google Cloud
+- HPE (Cloud type for PXE and manually added HPE Hosts)
+- Huawei
+- Hyper-V
+- IBM Cloud
+- IBM Cloud Platform
+- Kubernetes
+- MacStadium
+- Morpheus (Generic Cloud type for PXE/Bare Metal and manually added Hosts)
+- Nutanix
+- Open Telekom Cloud
+- OpenStack
+- Oracle Public Cloud
+- Oracle VM
+- Platform 9
+- SCVMM
+- Supermicro (Cloud type for PXE and manually added Supermicro Hosts)
+- UCS
+- UpCloud
+- vCloud Air (OVH)
+- VMWare ESXi
+- VMware Fusion
+- VMWare on AWS
+- VMware vCenter
+- VMware vCloud Director
+- XenServer
+
+Information on each cloud type can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Creating Clouds
+
+Clouds can be added from Infrastructure  >  Clouds or in Infrastructure  >  Groups  >  (select Group)  >  Clouds. Individual Guides for adding specific Cloud Types can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, current month costs, average monthly costs, resource utilization statistics, and resource counts for Container Hosts, Hypervisors, Bare Metal, Virtual Machines, and Unmanaged resources.
+
+![../../_images/clouddetailview1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-79A36EB1-C3D0-4D23-9067-DD12ABD6EDB7-high.png)
+
+To view the Cloud List View, select the name of a Cloud to display the clouds Detail View.
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud. Depending on the Cloud, choose to force a standard Cloud sync (occurs every five minutes by default) or a nightly sync. When syncing Costing data, HPE Morpheus Enterprise will force a pull of costing data for your specified period. If opting to “rebuild” the costing data, HPE Morpheus Enterprise will delete all costing data from the Cloud for that period and attempt to rebuild the data by calling the Cloud API.
+
+DELETE
+:   Delete the Cloud from HPE Morpheus Enterprise
+
+IMPORTANT
+
+All Instances and managed Hosts and VM’s associated with the Cloud must be removed prior to deleting a cloud.
+
+### Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Load Balancers
+:   The load balancers tab panel displays available load balancers in the cloud including the name, description, type, cloud and host. You can add a load balancer from this tab by clicking ADD LOAD BALANCER.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
+
+Policies
+:   Manages Policies enforced on the Cloud. Setting a policy on this tab is equal to creating a policy in Administration > Policies and scoping it to the selected Cloud.
+
+Profiles
+:   Manages Terraform, Key/Value Profiles that create custom object associated secrets and metadata that will automatically be mapped per Cloud selection during provisioning and automation.
+
+## Deleting Clouds
+
+### About this task
+
+To delete a cloud:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+### Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud. To remove Instances, hosts and VMs from HPE Morpheus Enterprise without deleting the Cloud resources they represent, select Delete on the host or VM, unselect “Remove Infrastructure”, and select “Remove Associated Instances” if Instance are associated with the selected Hosts or VMs.
+
+## Cloud Profiles
+
+### Role Permissions
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+### Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+#### Create a Terraform Profile
+
+##### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+##### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+### Key/Value Store Profiles
+
+- Key/Value Profiles (Key/Value Store) expand provisioning, automation, billing and reporting capabilities by allowing dynamic custom object specific metadata in provisioning and automation mappings
+- Key/Value Profile entries are available using `<%=cloud.profile.key%>`
+- Terraform Profiles are limited to one Profile per Cloud, however multiple key/value pairs can be added to a single profile
+
+#### Create a Key/Value Profile
+
+##### Procedure
+
+1. Navigate to `/infrastructure/clouds/` and select a Cloud
+2. Select the `Profiles` tab
+3. Select + ADD PROFILE
+4. Select Key/Value Profile Type
+5. Enter key/value entries, selecting + to add additional entries
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..bbd3e7e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 336,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..0d4f866
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json b/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
new file mode 100644
index 0000000..2789a58
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+  "title": "OpenSearch Configuration",
+  "ordinal": 11,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html",
+  "topic_cluster": {
+    "clustering_title": "OpenSearch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md b/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
new file mode 100644
index 0000000..ab74f81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
@@ -0,0 +1,496 @@
+# OpenSearch Configuration
+
+Starting with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. All HPE Morpheus VM Essentials Software versions already use OpenSearch — this change only affects HPE Morpheus Enterprise appliance upgrades. Hewlett Packard Enterprise continues to support both Elasticsearch and OpenSearch for external clusters.
+
+During upgrade, the reconfigure process will:
+
+- Automatically disable the old Elasticsearch service
+- Start OpenSearch in its place
+- Migrate the Elasticsearch PKCS12 CA to PEM format if `secure_mode` is enabled
+
+No changes to /etc/morpheus/morpheus.rb are required. Existing `elasticsearch[...]` settings are bridged to the `opensearch` namespace automatically (see Notes for details on key precedence).
+
+Data (indices) must be migrated separately using `morpheus-ctl migrate-elasticsearch` (see upgrade sections below, or run `morpheus-ctl migrate-elasticsearch help` on an appliance after upgrade for more info).
+
+## What the settings control
+
+| Setting | opensearch.yml | Purpose |
+| --- | --- | --- |
+| `enable` | — | Enable/disable the embedded OpenSearch service. Set to `false` when using an external cluster. Default `true`. |
+| `es_hosts` | `cluster.initial_master_nodes`, `discovery.seed_hosts` | Cluster membership and discovery. For external clusters, lists the external hosts. |
+| `node_name` | `node.name` | Unique name for this node within the cluster. |
+| `host` | `network.host` or `network.bind_host` | Interface to bind to. Default `127.0.0.1`. Set to `0.0.0.0` for cluster use. |
+| `publish_ip` | `network.publish_host` | The IP other nodes use to reach this node. Falls back to Ohai's `node['ipaddress']` if not set. |
+| `secure_mode` | `plugins.security.disabled: false`, TLS config | Enables TLS on HTTP and transport layers, generates certs, runs securityadmin.sh. |
+| `cluster` | `cluster.name` | Cluster name. Defaults to `morpheus`. Must be the same on all nodes. |
+| `use_tls` | — | Connect to OpenSearch over HTTPS. Automatically set to `true` when `secure_mode` is enabled on the embedded service. Set manually for external TLS clusters. |
+| `auth_user` | — | Username for Morpheus to authenticate with OpenSearch. Used for external clusters. When nil and `secure_mode` is enabled, the auto-created `morpheus` internal user is used. |
+| `auth_password` | — | Password for `auth_user`. Used for external clusters. |
+| `replica_count` | `numberOfReplicas` | Number of index replicas. Default `1`. Set to `0` for single-node deployments. |
+| `admin_dn` | `plugins.security.authcz.admin_dn` | Distinguished name for the admin certificate. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+| `nodes_dn` | `plugins.security.nodes_dn` | Distinguished name for trusted node certificates. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+
+## Ports
+
+For embedded clusters, ensure the following ports are open between all cluster nodes:
+
+- **9200** — HTTP (client queries)
+- **9300** — Transport (inter-node communication and cluster formation)
+
+## Notes
+
+- You can use either `elasticsearch[...]` or `opensearch[...]` keys in morpheus.rb. The `elasticsearch` keys are bridged to `opensearch` automatically. If the same key is set under both namespaces, the `opensearch[...]` value takes precedence.
+- The reconfigure strips `127.0.0.1` from `es_hosts` when more than one host is present, so you don't need to exclude it.
+- In secure mode, `admin_dn` and `nodes_dn` default to `O=Morpheus,OU=Ops,CN=<node_name>` and are set automatically per node. These only need to be overridden when using custom certificates (see below).
+
+## Custom certificates (admin\_dn and nodes\_dn)
+
+When using your own certificates instead of the auto-generated ones, set `admin_dn` and `nodes_dn` to match the subject DN of your certificates. These values map to `plugins.security.authcz.admin_dn` and `plugins.security.nodes_dn` in opensearch.yml.
+
+- `admin_dn` — Identifies the certificate authorized to run administrative operations (e.g., `securityadmin.sh`). Only requests signed by a certificate matching this DN can modify the security index.
+- `nodes_dn` — Identifies certificates trusted for inter-node transport communication. Nodes will reject transport connections from certificates that don't match.
+
+To extract the subject DN from an existing certificate:
+
+```
+```
+openssl x509 -in /path/to/cert.pem -noout -subject -nameopt RFC2253
+```
+```
+
+Set the values in /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['admin_dn'] = 'CN=admin,OU=MyTeam,O=MyOrg'  
+opensearch['nodes_dn'] = 'CN=node,OU=MyTeam,O=MyOrg'
+```
+```
+
+If the admin and node certificates share the same DN (common when a single wildcard or shared cert is used), both values can be set to the same string. With the default auto-generated certificates, these are set to `O=Morpheus,OU=Ops,CN=<node_name>` per node and do not need to be configured manually.
+
+## Setting the HPE Morpheus Enterprise user password
+
+When `secure_mode` is enabled, reconfigure creates an internal OpenSearch user named `morpheus` that HPE Morpheus Enterprise uses to authenticate with OpenSearch. The password for this user is auto-generated and stored in /etc/morpheus/morpheus-secrets.json under the `elasticsearch.morpheus_password` key. No manual configuration is needed in the default case.
+
+To set a custom password, add it to /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['morpheus_password'] = 'my-custom-password'
+```
+```
+
+## Encrypting the password
+
+Passwords in morpheus.rb can be stored in encrypted form using the `ENC{...}` wrapper. During reconfigure, the recipe detects the `ENC` prefix and decrypts the value automatically. Plaintext values are used as-is.
+
+To generate an encrypted string:
+
+```
+```
+morpheus-ctl get-crypto-string string 'my-custom-password'
+```
+```
+
+This outputs an encrypted value that can be used in morpheus.rb:
+
+```
+```
+opensearch['morpheus_password'] = 'ENC{aBcDeFgHiJkLmNoPqRsTuVwXyZ...}'
+```
+```
+
+The encryption uses the appliance's `encryption_key_suffix` (from /etc/morpheus/morpheus-secrets.json), so the encrypted value is specific to that appliance. All nodes in the cluster share the same secrets file contents, so the same encrypted string works on all nodes.
+
+Any password setting in morpheus.rb supports this format (under either the `opensearch[...]` or `elasticsearch[...]` namespace), including `morpheus_password` and `auth_password`. As with other settings, `opensearch[...]` takes precedence over `elasticsearch[...]` if both are set.
+
+## Single Node
+
+A single-node setup uses the embedded OpenSearch service with default settings. No morpheus.rb changes are required unless enabling secure mode.
+
+## Single Node — Fresh Install
+
+The embedded OpenSearch service starts automatically after the initial reconfigure. No configuration is needed:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+To enable secure mode, add to /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['secure_mode'] = true
+```
+```
+
+## Single Node — Upgrading from Elasticsearch
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new HPE Morpheus Enterprise package. Do **NOT** run reconfigure yet.
+
+**Step 2 — Export data**
+
+After upgrading the package (but before reconfigure), export Elasticsearch data. The old Elasticsearch binary is preserved in the new package to allow this:
+
+```
+```
+morpheus-ctl migrate-elasticsearch export --dir /var/opt/morpheus/es-migration
+```
+```
+
+**Step 3 — Reconfigure**
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The old Elasticsearch service is disabled automatically and OpenSearch starts in its place. If `secure_mode` was enabled, the Elasticsearch PKCS12 CA is automatically migrated to PEM format.
+
+**Step 4 — Import data**
+
+```
+```
+morpheus-ctl migrate-elasticsearch import --dir /var/opt/morpheus/es-migration
+```
+```
+
+This strips Elasticsearch-specific `_type` metadata from the exported data and bulk-imports it into OpenSearch.
+
+**Step 5 — Cleanup (optional)**
+
+After verifying the data is intact, migrate-elasticsearch will present the option to remove the old Elasticsearch files. This can also be done manually:
+
+```
+```
+rm -rf /opt/morpheus/embedded/elasticsearch-*  
+rm -rf /var/opt/morpheus/elasticsearch-*  
+rm -rf /var/opt/morpheus/es-migration
+```
+```
+
+## 3-Node Embedded Cluster
+
+## 3-Node Embedded Cluster — Prerequisites
+
+**Networking**
+
+- All 3 nodes must be able to reach each other on:
+
+  - **Port 9200 (TCP)** — HTTP API (client queries, health checks)
+  - **Port 9300 (TCP)** — Transport (inter-node communication, cluster formation, shard replication)
+- Each node needs a stable, routable IP address or resolvable hostname that the other nodes can reach (no NAT between nodes)
+- Both IP addresses and hostnames are supported in `es_hosts` and `publish_ip`
+
+**Configuration**
+
+- Each node must have:
+
+  - The same `es_hosts` hash listing all 3 nodes
+  - A unique `node_name`
+  - A unique `publish_ip` matching that node's routable IP
+  - `host` set to `0.0.0.0` (default `127.0.0.1` only listens locally and will not allow cluster formation)
+- All nodes must share the same `cluster` name (defaults to `morpheus` — only set this if you need to change it)
+
+**Secure Mode**
+
+- When `secure_mode` is enabled, TLS is used on both HTTP and transport layers
+- All nodes must share the **same root CA** — Node 1 must be reconfigured first to generate the CA, then the CA files are copied to the remaining nodes before their first reconfigure
+- Each node auto-generates its own node certificate signed by the shared CA
+
+**Example nodes:**
+
+- Node 1: `10.0.0.1` (morpheus-1)
+- Node 2: `10.0.0.2` (morpheus-2)
+- Node 3: `10.0.0.3` (morpheus-3)
+
+## Fresh Install — Without Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+**Node 1** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'
+```
+```
+
+**Node 2** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'
+```
+```
+
+**Node 3** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'
+```
+```
+
+**Apply**
+
+Run on all three nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Nodes can be reconfigured in any order. The cluster will form once all nodes are up and can reach each other on ports 9200 and 9300.
+
+## Fresh Install — With Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Secure mode enables TLS on both the HTTP and transport layers. Each node generates its own node certificate, but all nodes must share the **same root CA** so they trust each other.
+
+**Step 1 — Configure and reconfigure Node 1 first**
+
+Node 1 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Node 1:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+This generates the root CA and node certificate at:
+
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem
+
+**Step 2 — Copy the root CA to Nodes 2 and 3**
+
+Copy both CA files from Node 1 to the same path on Nodes 2 and 3 **before** running reconfigure on them:
+
+```
+```
+# From Node 1:  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node3:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node3:/opt/morpheus/embedded/opensearch-2.18.0/config/
+```
+```
+
+Set ownership on Nodes 2 and 3:
+
+```
+```
+chown morpheus-es:morpheus-es /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca*.pem
+```
+```
+
+**Step 3 — Configure and reconfigure Nodes 2 and 3**
+
+Node 2 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'  
+opensearch['secure_mode'] = true
+```
+```
+
+Node 3 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Nodes 2 and 3:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Each node will skip CA generation (the files already exist) and generate its own node certificate signed by the shared CA.
+
+## Upgrading from a 3-Node Elasticsearch Cluster
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on all 3 nodes. Do **not** run reconfigure yet.
+
+**Step 2 — Export data**
+
+After upgrading the package (but before reconfigure), export Elasticsearch data on **one node** (the data is cluster-wide). The old Elasticsearch binary is preserved in the new package to allow this:
+
+```
+```
+morpheus-ctl migrate-elasticsearch export --dir /var/opt/morpheus/es-migration
+```
+```
+
+This will:
+
+- Query all available indices and their sizes
+- Prompt you to select which indices to export (or export all)
+- Verify sufficient disk space (requires ~2x index size for JSON format)
+- Write each index as a JSON file to the export directory
+
+**Step 3 — Reconfigure**
+
+**Without secure mode** — No special ordering is required. Run on all 3 nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The old Elasticsearch service is disabled automatically and OpenSearch starts in its place. The existing morpheus.rb cluster settings (`es_hosts`, `node_name`, `host`, `publish_ip`) carry over unchanged.
+
+**With secure mode** — No special ordering is required. The existing Elasticsearch cluster already shares a single CA via the PKCS12 truststore on each node. During reconfigure, each node independently extracts the same CA from its local truststore and uses it to generate its OpenSearch node certificate.
+
+Run on all 3 nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+On each node, the recipe will:
+
+- Detect the old PKCS12 truststore at /var/opt/morpheus/elasticsearch\*/local/elastic-stack-ca.p12
+- Extract the shared CA certificate and key to PEM format (root-ca.pem and root-ca-key.pem)
+- Generate a new OpenSearch node certificate signed by the migrated CA
+- Disable the old Elasticsearch service
+
+It is assumed existing Elasticsearch clusters use the same CA. When all nodes extract the same CA, they will trust each other's certificates and form a cluster without any manual certificate copying.
+
+**Step 4 — Import data**
+
+Once all 3 nodes are reconfigured and the OpenSearch cluster is formed, import the data on **one node**:
+
+```
+```
+morpheus-ctl migrate-elasticsearch import --dir /var/opt/morpheus/es-migration
+```
+```
+
+This strips Elasticsearch-specific `_type` metadata from the exported data and bulk-imports it into OpenSearch.
+
+**Step 5 — Cleanup (optional)**
+
+After verifying the data is intact in OpenSearch, migrate-elasticsearch will present the option to remove the old Elasticsearch files. This can also manually be done on the other nodes with:
+
+```
+```
+rm -rf /opt/morpheus/embedded/elasticsearch-*  
+rm -rf /var/opt/morpheus/elasticsearch-*  
+rm -rf /var/opt/morpheus/es-migration
+```
+```
+
+## External Cluster
+
+When using an externally managed OpenSearch (or Elasticsearch) cluster, disable the embedded service and point Morpheus at the external hosts.
+
+## External Cluster — Fresh Install
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Add the following to /etc/morpheus/morpheus.rb on each Morpheus appliance node:
+
+```
+```
+opensearch['enable'] = false  
+opensearch['es_hosts'] = {'os-node1.example.com' => 9200, 'os-node2.example.com' => 9200, 'os-node3.example.com' => 9200}  
+opensearch['auth_user'] = 'morpheus'  
+opensearch['auth_password'] = 'the-external-cluster-password'
+```
+```
+
+If the external cluster uses TLS:
+
+```
+```
+opensearch['use_tls'] = true
+```
+```
+
+Then reconfigure:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The embedded OpenSearch service will not be started. Morpheus will connect directly to the external cluster using the provided hosts and credentials.
+
+- `auth_user` and `auth_password` are sent to the external cluster for authentication. These must match a user configured on the external cluster.
+- `auth_password` supports the `ENC{...}` encrypted format (see Encrypting the password).
+- Do not set `secure_mode` — that setting controls the embedded service's certificate generation and security plugin. For external TLS clusters, use `use_tls` instead.
+- `replica_count` can be adjusted to match the external cluster's topology (default `1`).
+
+## Upgrading with an External Cluster
+
+If the existing Morpheus installation was already configured to use an external Elasticsearch or OpenSearch cluster, the upgrade is straightforward — no data migration is needed on the appliance side since the data lives on the external cluster. The external cluster does not need to be migrated to OpenSearch; Morpheus supports both.
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on each appliance node.
+
+**Step 2 — Reconfigure**
+
+No morpheus.rb changes are needed. The existing `elasticsearch[...]` settings are bridged automatically.
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.json b/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.json
new file mode 100644
index 0000000..e4c6406
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+  "title": "Security Packages",
+  "ordinal": 162,
+  "parent_title": "Templates",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-ED404402-F168-4635-ADEB-02609465196E.html",
+  "topic_cluster": {
+    "clustering_title": "Security Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.md b/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.md
new file mode 100644
index 0000000..245fbe2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-ED404402-F168-4635-ADEB-02609465196E.md
@@ -0,0 +1,20 @@
+# Security Packages
+
+The Security Packages Section is for uploading SCAP packages which can then be consumed in Security Scan Jobs (Provisioning > Jobs).
+
+## Add a new Security Package
+
+### Procedure
+
+1. Navigate to Library > Templates > Security Packages
+2. Click +ADD > SCAP Package
+3. Provide a name in addition to a URL to source the package
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Currently URL is the only source option for security packages
+
+![../../_images/1add_package.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-8BD09052-92FA-4310-AE20-7EF52079B937-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json b/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
new file mode 100644
index 0000000..ba8a867
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+  "title": "Creating a Datastore",
+  "ordinal": 441,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md b/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
new file mode 100644
index 0000000..c1a973e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
@@ -0,0 +1,19 @@
+# Creating a Datastore
+
+## About this task
+
+This procedure guides you through creating a Datastore. The datastore acts as a container for volumes and must be created before volumes can be created.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > DataStores.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage Baremetal for type, select your cloud, the storage server previously created, FC as the protocol type, and the Resource Pool that applies to this storage server.
+5. Click the Save to create the DataStore.   
+   ![Add Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4455C3A5-99BD-49B4-86A3-C2CB67FDD579-high.png)
+
+## Results
+
+The added data store appears under Data Store.   
+![Data Store](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-A1A160B8-E303-4B49-85E6-20044732C34B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json b/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
new file mode 100644
index 0000000..98a1a82
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+  "title": "CloudFormation Blueprints",
+  "ordinal": 133,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html",
+  "topic_cluster": {
+    "clustering_title": "CloudFormation Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md b/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
new file mode 100644
index 0000000..680a6bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
@@ -0,0 +1,46 @@
+# CloudFormation Blueprints
+
+CloudFormation Blueprints consume new or existing CloudFormation templates to create easily-deployable application stacks. CloudFormation templates in HPE Morpheus Enterprise are JSON or YAML-formatted text documents that declare all relevant AWS resources needed for the provisioned application. They can be created directly in the New Blueprint modal or pulled in from existing Git repositories.
+
+If needed, Amazon has educational resources available for getting started with CloudFormation. They can be found in the [AWS CloudFormation documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html).
+
+To create a new CloudFormation Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select CloudFormation. Click NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+In some cases, you must explicitly acknowledge that your template contains certain capabilities in order for the application to successfully be deployed. There is more information on this in Amazon’s documentation [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html). If any of the following capabilities are contained in your application, acknowledge them by marking any of the following boxes that apply:
+
+- **CAPABILITY\_IAM**
+- **CAPABILITY\_NAMED\_IAM**
+- **CAPABILITY\_AUTO\_EXPAND**
+
+Continuing on with the CloudFormation Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “CloudFormation Template JSON (.json)”
+- **CONFIG TYPE:** “CloudFormation Template YAML (.yaml)”
+- **CONFIG:** Enter your configuration here
+
+In the CloudFormation Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new CloudFormation Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..24d7434
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 338,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..5f5ba72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json b/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
new file mode 100644
index 0000000..ce8d648
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+  "title": "IBM Cloud",
+  "ordinal": 460,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F003BCEE-0E64-412A-9045-295910E15A5A.html",
+  "topic_cluster": {
+    "clustering_title": "IBM Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md b/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
new file mode 100644
index 0000000..d38afce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
@@ -0,0 +1,133 @@
+# IBM Cloud
+
+IBM Cloud offers a wide set of cloud computing services including compute, storage, database, networking, and more. It is deployed in data centers across the world and its services can scale to meet the needs of small development teams as well as large-scale enterprises. HPE Morpheus Enterprise integrates with IBM Cloud to offer virtual machine provisioning, brownfield discovery, and lifecycle management.
+
+## Integrating IBM Cloud with HPE Morpheus Enterprise
+
+### About this task
+
+Connecting an IBM Cloud account with HPE Morpheus Enterprise is a simple process requiring only an API key. You can create an API key from the IBM Cloud web console if you don’t currently have access to one. Integrating with HPE Morpheus Enterprise requires a user API key. If needed, create one by clicking “Manage” in the upper menu bar of the IBM Cloud web console and clicking “Access (IAM)”. Select “Users” from the left navigation menu and click on the desired user. Create a new API Key from within the API Keys section and store the API Key in a secure place to retrieve in the next step. It’s recommended that you integrate HPE Morpheus Enterprise using an IBM Cloud admin account to ensure you won’t run into any blockers while working in HPE Morpheus Enterprise. Using HPE Morpheus Enterprise role-based access you can limit which IBM Cloud constructs and capabilities are accessible to your users.
+
+With the API key created, head back to HPE Morpheus Enterprise and continue with the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Click + ADD
+3. Complete the following required fields:
+
+### Results
+
+- **NAME:** A friendly name for the cloud inegration in HPE Morpheus Enterprise
+- **USERNAME:** Enter “apikey” (Do not enter your IBM Cloud username or anything other than “apikey”)
+- **API Key:** The API key value
+- **DATACENTER:** Select the IBM Cloud data center
+- **OBJECT STORE:** If desired and if any are found, select an object store
+
+1. Click NEXT
+2. Select a Group for this Cloud or create a new one if desired
+3. Complete the wizard to save the new integration
+
+![../../../_images/1createCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-55120133-3640-459B-B4C4-796C4CC5C741-high.png)
+
+Once the wizard has completed, the new IBM Cloud integration will appear alongside other Clouds currently available in HPE Morpheus Enterprise. If you’ve selected to automatically onboard existing resources, those will appear shortly.
+
+IBM Cloud integrations also support a number of advanced options which were not discussed as part of the initial integration set up discussed above. For more information on the advanced options, consult the section below.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json b/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
new file mode 100644
index 0000000..5134370
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+  "title": "Overview",
+  "ordinal": 281,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md b/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
new file mode 100644
index 0000000..0234f78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on any Tenant detail page (Administration > Tenants > Selected Tenant) or on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in HPE Morpheus Enterprise so at first log in users are assigned the appropriate role.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json b/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
new file mode 100644
index 0000000..043fd27
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+  "title": "Service Catalog Persona",
+  "ordinal": 341,
+  "parent_title": "Personas",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html",
+  "topic_cluster": {
+    "clustering_title": "Service Catalog Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md b/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
new file mode 100644
index 0000000..286f6fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
@@ -0,0 +1,53 @@
+# Service Catalog Persona
+
+The Service Catalog Persona presents a simplified catalog where users can select and deploy Instances or Blueprints with pre-defined configuration with just a few clicks and without presenting an overwhelming list of options.
+
+## Configuring Catalog Item Access
+
+Within the Service Catalog Persona, users are presented with Catalog Items based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items (and no access to the Service Catalog Persona). When enabling Service Catalog Persona access for User Roles, you will also need to give access to some or all Catalog Items.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Dashboard
+
+The default page for the Service Catalog Persona is the Dashboard. The Dashboard shows a selection of featured catalog items, a listing of the last few items the user has ordered, and a selection from the user’s inventory.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-98CB46CB-C852-48BE-8F39-09E5E676BCCE-high.png)
+
+## Catalog
+
+The catalog shows the complete list of pre-defined catalog items available to the user for provisioning. Catalog items are not created in the Service Catalog Persona. For more on creating catalog items, see the [Self Service section](https://docs.morpheusdata.com/en/latest/tools/self-service.html) (Tools > SelfService) of HPE Morpheus Enterprise docs.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-782B5419-8EEF-4E93-A621-974E15760B4A-high.png)
+
+## Inventory
+
+The Inventory Page reveals the complete list of items which have been ordered by the user and provisioned. Users will only see their own items in this section.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-BA083368-6AF1-4E7D-A035-B175C86AED03-high.png)
+
+## Inventory Detail
+
+Access the detail page for an item in your inventory by clicking the View Details link. The page displayed will look very similar to an Instance or App detail page in the Standard Persona. Highly detailed information on the health of the Instance or App are shown here. We can also take actions against Instances such as running Tasks or Workflows, reconfiguring the Instance, controlling the power state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-193E867C-87CF-49A6-B994-AC2CEE9B6D08-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-B4E37C64-41C3-4CF9-8D36-47260212AEC6-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Click “Review Order”. When reviewing your order, each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-6A53CB8B-6B6D-40A5-AEB3-AF96A7D8917B-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can be viewed in Inventory and additional details can be accessed through the Inventory item detail page.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json b/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
new file mode 100644
index 0000000..4a38c81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+  "title": "Overview",
+  "ordinal": 288,
+  "parent_title": "Plans",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md b/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
new file mode 100644
index 0000000..47efcc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
@@ -0,0 +1,9 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from HPE Morpheus Enterprise, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to HPE Morpheus Enterprise-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance.
+
+Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time. Price sets are associated with plans, which is how HPE Morpheus Enterprise can compute cost values even for Instances running in private, on-prem Clouds.
+
+The Plans & Pricing section is where Plans, Prices Sets and Prices are managed. These concepts are associated with each other in the following way: Prices are added to Prices Sets, and Price Sets are added to Plans. Plans include Service Plans, Load Balancer Price Plans, Virtual Image Prices Plans and Snapshot Price Plans. Price sets can be agnostic and available for any Plan, or specific to a Region Code, Cloud or even a specific Resource Pool. Prices are configured per Price Type and can be added to Price Set configurations that support the Price Type. Master Tenant Prices can apply to all Tenants or be assigned to a single Tenant.
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json b/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
new file mode 100644
index 0000000..dac952a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+  "title": "Microsoft DNS",
+  "ordinal": 485,
+  "parent_title": "DNS",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html",
+  "topic_cluster": {
+    "clustering_title": "Microsoft DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md b/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
new file mode 100644
index 0000000..9c25dee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
@@ -0,0 +1,328 @@
+# Microsoft DNS
+
+The HPE Morpheus Enterprise Microsoft DNS integration is developed as an official plugin separate from the core product. It is easily added and uploaded to any HPE Morpheus Enterprise appliance. Download the plugin from the official plugin repository <share.morpheusdata.com > \_ and add it to the appliance from the plugin management UI section (Administration > Integrations > Plugins).
+
+The MSDSN integration automates DNS record creation and DNS record cleanup both manually or automatically during workload provisioning to a configured Cloud or Group. It should be noted that this integration is typically not needed when joining a Windows VM to an Active Directory Domain as typically this automatically creates a DNS record.
+
+## Prepare DNS Server(s)
+
+NOTE
+
+This section will assume a the DNS server is in an Active Directory environment and joined to the domain. The process may be different for other configurations.
+
+The easiest method to prepare DNS server(s) is to use a service account that is added to the `DnsAdmins` and `Remote Management Users` groups, either in Active Directory (if DNS is on domain controllers) or the local groups of a member server. The `DnsAdmins` group will provide permissions for the service account to make DNS changes, such as creating/deleting A and PTR records. The `Remote Management Users` group will allow HPE Morpheus Enterprise to connect to the server(s) via WinRM.
+
+Additionally, ensure firewall rules have been updated if needed to allow WinRM through. In some cases, the default WinRM rules allow `Private` and `Domain` networks but not `Public`. Enable `Public` if the network HPE Morpheus Enterprise is connected is considered `Public`, or disable the firewall if permitted. If a jump box is required (discussed below), then ensure the firewall is configured to allow the jump box to connect to the DNS server instead.
+
+Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+### Minimum Permissions
+
+Some organizations may require that users cannot be added to the `DNSAdmin` group, mentioned previously. If this is a requirement, the following process/permissions would be required to ensure HPE Morpheus Enterprise can connect successfully. This process may be required on each DNS server, depending on the environment. Note that if HPE Morpheus Enterprise adds additional functionality at a later time, these permissions may need to be updated to support those features.
+
+- Run `dnsmgmt.msc`
+- Right-click the DNS server object and choose `Properties`
+- Add the service account to the user list and ensure the following permissions are applied:
+
+  - Read
+  - Create all child objects
+  - Delete all child objects
+- Run `wmimgmt.msc`
+- Right-click `WMI Control (Local)` and choose `Properties`
+- Click the `Security` tab
+- Set the following permissions for each of the below nodes:
+
+  - `CIMV2`
+  - `MicrosoftDNS`
+  - `Microsoft => Windows => DNS` (only the DNS node)
+- Hightlight the node and click the `Security` button
+- Click the `Advanced` button
+- Click the `Add` button to add the service account to the list
+- Ensure the `Applies to` field is set to `This namespace and subnamespaces`
+- Set the following permissions:
+
+  - Enable Account
+  - Remote Enable
+  - Execute Methods
+- Finally, restart Windows Management Instrumentation Service or the server. This is required for the change in permissions to take place.
+
+Additional support reference: <https://support.morpheusdata.com/s/article/How-to-give-C?language=en_US>
+
+## (Optional) Prepare Jump Box
+
+In some environments, HPE Morpheus Enterprise may not be allowed to access the DNS servers directly, as they may be on segregated networks. In this case, HPE Morpheus Enterprise can utilize a member server as a “jump box” that can access the DNS servers directly, the jump box will be used to interact with the DNS server instead. If this is a requirement, follow the below process to prepare the jump box.
+
+- Add the service account to the `Remote Management Users` group of the jump box, which will allow WinRM to access
+- Verify the firewall allows WinRM from HPE Morpheus Enterprise
+- Create or edit the following registry key by running `regedit`:
+
+  - Navigate to: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb`
+  - Create or edit `ProtectionPolicy` DWORD (32-bit) Value
+  - Set `ProtectionPolicy` value to `1`
+- Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+## Adding a Microsoft DNS integration
+
+For appliances with the MSDNS plugin installed, the option to create an integration is available. Navigate to Administration > Integrations and click + NEW INTEGRATION to create a new one.
+
+- **NAME:** A friendly name for the integration in HPE Morpheus Enterprise
+- **RPC SERVER** Enter the name of the server brokering access to the Microsoft DNS Services. This is the Windows server HPE Morpheus Enterprise will connect to directly. In most cases, the RPC SERVER will be a Windows domain-joined server with the DNS Server tools installed. HPE Morpheus Enterprise will use this server to connect and manage DNS
+- **RPC PORT:** This configuration is visible if “USE AGENT FOR RPC” is unmarked. The WinRM port number 5985/5986, default is 5985
+- **USE AGENT FOR RPC:** Select this option to have the plugin use a configured agent to handle the HPE Morpheus Enterprise to Windows RPC connection. The RPC SERVER should be an Instance (in other words, a managed VM) which is part of the same HPE Morpheus Enterprise environment where the integration is added. The HPE Morpheus Enterprise Agent must also be configured to logon as the DNS Service user account. In most cases, customers would only use this option when using an intermediate server to access DNS services
+- **CREDENTIALS:** Provide account credentials for a service account. You may use credentials already stored in HPE Morpheus Enterprise or create new Username/Password credentials
+- **DNS SERVER:** If the RPC SERVER is not the server hosting DNS Services, then add the FQDN name of the DNS server here. Leave blank if the RPC SERVER is also the DNS Server
+- **ZONE FILTER:** The ZONE FILTER is a comma separated list of glob-style filters which can be used to specify the zones that HPE Morpheus Enterprise will import and sync. Glob style filters apply to the zone name only and at a domain level. The `\*` character matches any legal DNS character [-] 0 or more times. Wildcarding stops at the . (period), leave blank to import all forward and reverse zones
+- **SERVICE TYPE:** This configuration is visible if the DNS SERVER is not blank. This option informs the plugin how the RPC SERVER should contact the DNS SERVER. There are 3 supported options: **local** when the RPC SERVER is the DNS Server (ie when DNS SERVER is blank in which case local is the default and only option), **wmi** which is used when the RPC SERVER contacts the DNS Server over WMI (Windows RPC, this is the recommended and default option when using an intermediate RPC SERVER), and **winrm** which is used when the RPC SERVER connects to DNS SERVER over a WinRM session (this is not often used due to WinRM restrictions on domain controllers)
+- **INVENTORY EXISTING:** Have the integration import and sync all DNS records for the matching Zones. Using this option is not recommended for installations with large namespaces
+- **CREATE POINTERS:** Have DNS create a PTR record when the forward record is created
+
+NOTE
+
+If you’re not using an intermediate server, the RPC SERVER will also be the DNS Server. The HPE Morpheus Enterprise Windows Agent should be set to log in using these credentials.
+
+## Domains
+
+Once the integration is added, Microsoft DNS Domains will sync and listed under Infrastructure > Network > Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Infrastructure > Network > Domains
+
+## Configuring Microsoft DNS with Clouds and Groups
+
+DNS Integrations are available in the `DNS Integration` dropdown in Cloud and Group settings. HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the `Advanced Options` section.
+3. In the `DNS Integration` dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the `Edit` button for the Group
+3. Expand the `Advanced Options` section.
+4. In the `DNS Integration` dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
+
+## Using Zone Filters
+
+In this example a ZONE FILTER string of
+
+`*.morpheus.com, *.10.in-addr.arpa, d*.us.morpheus.com`
+
+would
+
+**IMPORT**`test.morpheus.com, prod.morpheus.com` but **NOT** `mydomain.test.morpheus.com` which has a 4th level
+
+**IMPORT**`32.10.in-addr.arpa, 33.10.in-addr.arpa` but **NOT** `12.11.in-addr.arpa` or `10.in-addr.arpa` (which has 3 levels)
+
+**IMPORT**`denver.us.morpheus.com` and `delaware.us.morpheus.com` but **NOT** `ohio.us.morpheus.com` (wildcard at 4th level)
+
+## Improved Integration Validation
+
+Recent versions of this integration have improved the error handling and validation. RPC connectivity and access to DNS Services is tested at the time the integration dialog is saved. The dialog will not save unless validation is passed successfully. The integration dialog will hint where problems occur but you should check the HPE Morpheus Enterprise Health logs (Administration > Health > Morpheus Logs) to see detailed messages.
+
+TIP
+
+To force the integration to save you can uncheck the ENABLED checkbox. Doing this disables the validation testing allowing you to save the integration dialog contents and perform troubleshooting without having to reenter configurations. When the issue is resolved, edit the integration and set the integration to ENABLED. Validation will then be performed on the save.
+
+## Custom Powershell Module Script
+
+Recent versions of this integration include a custom Powershell Module script (.ps1 file) which is maintained by the plugin and transferred to the RPC SERVER when the integration is added. The Powershell script file contains functions designed to handle the interface between Morpheus and DNS. The script uses the standard Windows DNS-Server module (Windows feature RSAT-DNS-Server). The script file is MD5 checked each time the integration syncs and the module is refreshed from the plugin if the checksum fails. The custom script is stored in the **%LOCALAPPDATA%** folder for the integration service account user.
+
+The module contains custom functions designed to interface with the MSDNS plugin via JSON.
+
+- Having the Powershell module installed on the RPC SERVER offers some performance benefits as HPE Morpheus Enterprise now can call on the modules functions to perform tasks
+- The Powershell functions test RPC connectivity and DNS service connectivity on each sync refresh ensuring the integration is healthy
+- The module uses a standard JSON interface between Windows RPC SERVER and HPE Morpheus Enterprise
+- The module overcomes restrictions imposed on HPE Morpheus Enterprise WinRM connections authenticating with NTLM
+
+IMPORTANT
+
+For version 2.1.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v32.ps1` and for version 2.3.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v34.ps1`. The HPE Morpheus Enterprise health logs will log the status of the HPE Morpheus Enterprise Powershell file on each refresh. For example: `INFO c.m.m.MicrosoftDnsPluginHelper - testHelperFileScript - Checking for valid Helper script fileName: morpheusDnsPluginHelper_v32.ps1 - MD5: 698d8e6ad0bf7f64d9e9ccac962e4ab1`
+
+## Secure credential cache file
+
+The HPE Morpheus Enterprise Powershell functions use a technique where script blocks are executed with Invoke-Command passing a credential object. This effectively creates a new session from RPC SERVER using kerberos overcoming the restrictions imposed by Windows on the original Morpheus NTLM connection. Credentials are cached using the Windows Data Protection API meaning only the user account who created the credential can decrypt it and only on the original Windows server. The credential cache is stored in `%LOCALAPPDATA%\S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` where `S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` is the Service Account SID.
+
+NOTE
+
+If “USE AGENT FOR RPC” is checked, there is no need to create a new session since the original session is already Kerberos, however the credentials are still cached.
+
+## Troubleshooting Connections
+
+### Service Account Requirements
+
+The service account used to access DNS via the plugin must meet the following requirements:
+
+- If using an intermediate server as the RPC SERVER, the service account should be a member of local `administrators` group on the RPC SERVER
+- If “USE AGENT FOR RPC” is checked, the HPE Morpheus Enterprise Windows Agent service must be configured to login as the service account. The service account will require `Log on as a Service` rights in the RPC SERVER local policy
+- If not using an intermediate server, the service account must be a member of `Remote Management Users` on the RPC SERVER as a minimum in order to access the RPC SERVER from HPE Morpheus Enterprise via WinRM. Membership of `administrators` however, is recommended
+- The service account must be a member of the domain global group `DNS Admins`
+- To Access Microsoft DNS WMI namespaces, the service account must be granted access to the DNS WMI classes
+
+### RPC SERVER requirements
+
+When using an intermediate server as the RPC SERVER, the following requirements must be met:
+
+- The RPC SERVER must be a Windows Server which is a member of a domain or forest which is trusted to access the DNS namespace
+- The RPC SERVER must have the Microsoft Windows feature RSAT-DNS-Server installed
+- If planning to “USE AGENT FOR RPC” then the Windows server must have a HPE Morpheus Enterprise Windows Agent installed and this agent must report into the HPE Morpheus Enterprise environment where the DNS Integration is being added or configured. Ideally, HPE Morpheus Enterprise will have deployed the RPC SERVER as an Instance
+- If not planning to “USE AGENT FOR RPC” then the RPC server must have WinRM configured and must be reachable over WinRM from the HPE Morpheus Enterprise appliance
+- When using an intermediate server to access DNS Services, the computer account of the RPC SERVER must be configured for delegation `Trusted for Delegation to any service (Kerberos only)`. Use Active Directory Users and Computers, locate the computer account for RPC SERVER. Click properties and select the Delegation tab and choose the option `Trust this computer for delegation to any service (Kerberos only)`
+
+## Using the plugin test Service page
+
+Recent versions of this integration have the ability to run a connection test via the HPE Morpheus Enterprise appliance. Users must have full access to the Integrations permission to test a Microsoft DNS plugin connection. For example, to test connectivity to an integration with id value of 5, browse to the following URL in HPE Morpheus Enterprise: `https://my.morpheus.appliance/plugin/msdns/service?integrationId=5`
+
+The plugin will run a series of tests using details from the integration dialog.
+
+NOTE
+
+Tests can be run even if the integration ENABLED checkbox is unmarked allowing troubleshooting with the integration offline.
+
+The results are output in the browser in JSON.
+
+In the example below, inspect the `serviceProfile`. Here, the `rpcType` is “agent” so “USE AGENT FOR RPC” is checked and the `serviceType` is “wmi”. The `rpcSession` and `serviceSession` show the connection details, logon types and group membership for the RPC and service sessions. The `dnsServer` section shows the FQDN and version of the DNS server and if populated indicates a successful test (status = 0).
+
+If the test is unsuccessful, a status code other than 0 is returned and any error will be listed in the “Errors” section
+
+```
+```
+Morpheus Microsoft DNS Integration Service Profile  
+Discovered service profile for Microsoft DNS integration : 5  
+Rpc Connection Status true  
+Successful rpc response from spie-mo-w-3011 via agent: Command completed successfully  
+Errors  
+{  
+}  
+Rpc Output  
+{  
+    "status": 0,  
+    "cmdOut": {  
+        "serviceProfile": {  
+            "rpcHost": "SPIE-MO-W-3011",  
+            "rpcType": "agent",  
+            "serviceHost": "ip-c61302.myad.net",  
+            "serviceType": "wmi",  
+            "useCachedCredential": false  
+        },  
+        "dnsServer": {  
+            "computerName": "IP-C61302.myad.net",  
+            "version": "10.0.17763"  
+        },  
+        "rpcSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "serviceSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "domainSOAServers": {  
+            "nameToQuery": "ip-c61302.myad.net",  
+            "fqdn": "ip-c61302.myad.net",  
+            "dcList": [  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61301.myad.net"  
+                },  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61302.myad.net"  
+                }  
+            ]  
+        }  
+    },  
+    "errOut": null  
+}
+```
+```
+
+## DNS Record validation and Error Handling
+
+- DNS records are now fully validated before they are created. Only record types A, AAAA, CNAME and PTR are currently supported
+- Adding a DNS Record which already exists (ie FQDN and IP address match an existing record in DNS) would normally return an error (code 9711), this is masked to a success to prevent HPE Morpheus Enterprise aborting the provision
+- Removing a HPE Morpheus Enterprise DNS Record that does not exist in DNS (error 9714) is also masked to success to have HPE Morpheus Enterprise delete its copy
+- If a fwd record is created but the PTR record fails (due to missing PTR zone error 9715), this is also masked to success to prevent HPE Morpheus Enterprise aborting the Provision
+- All errors are logged to the HPE Morpheus Enterprise health logs (Administration > Health > Morpheus Logs).
+
+## AWS Directory Services Support
+
+Support is included for AWS Active Directory service.
+
+- Access is only possible via a correctly configured intermediate server (RPC SERVER) hosted in AWS and having the DNS Management Tools installed
+- The DNS SERVER must be the fully qualified name of one of the AWS Domain controllers
+- The Service Account should be a member of AWS Delegated Domain Name System Administrators, AWS Delegated Kerberos Delegation Administrators and AWS Delegated Server Administrators (for access to RPC SERVER)
+- The RPC SERVER computer object should be trusted for delegation for all Kerberos Services on the AWS Directory Service domain controllers. This can be performed using AD Users and Computers to modify the properties of the RPC SERVER Computer object. Right click the computer object, select properties and open the Delegation tab. Select the Radio button `Trust this computer for delegation to any service (Kerberos Only)`. Click OK to Save
+
+NOTE
+
+It is possible to finely tune the delegation so that the RPC SERVER computer object can only delegate to specific services if this is required.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json b/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
new file mode 100644
index 0000000..b565555
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+  "title": "Reconfiguring Volume",
+  "ordinal": 446,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html",
+  "topic_cluster": {
+    "clustering_title": "Reconfiguring Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md b/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
new file mode 100644
index 0000000..38a7adb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
@@ -0,0 +1,19 @@
+# Reconfiguring Volume
+
+## About this task
+
+Reconfiguration allows the user to make changes to volumes consumed by a compute instance post-provisioning. This is achieved through the Reconfigure action on the instance.
+
+New volumes can be created and attached to the compute instance. These can be shared or unshared volumes. Any volume attached to the compute instance can be resized to increase the size of the volume. Any attached volume can be detached. However, volumes cannot be deleted from the Reconfigure action. Volumes can be deleted only from the infrastructure management section.
+
+All these operations work in the context of a compute instance and are not specific to a compute server within the instance.
+
+## Procedure
+
+1. Navigate to Provision > Instance.
+2. Click on the compute instance you want to reconfigure and access the details of the instance.
+3. Click on Actions and select Reconfigure.   
+   ![Action Reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-DE3C1BD1-CF86-4745-BF9D-F88C65D2E407-high.png)
+4. In the Reconfigure wizard, make the changes desired to add a new volume, resize an existing volume or click the trash icon to detach a volume from the instance.   
+   ![Reconfigure Instance](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-12FE7650-4E11-449B-907A-4AB15A132992-high.png)
+5. Click on Reconfigure.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json b/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
new file mode 100644
index 0000000..39cc54a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+  "title": "Morpheus API & CLI",
+  "ordinal": 527,
+  "parent_title": null,
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus API & CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md b/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
new file mode 100644
index 0000000..6de0d35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
@@ -0,0 +1,4 @@
+# Morpheus API & CLI
+
+- [API Documentation](https://apidocs.morpheusdata.com)
+- [CLI Documentation](https://clidocs.morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json b/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
new file mode 100644
index 0000000..6732a1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+  "title": "VMware Support Statement",
+  "ordinal": 52,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Support Statement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md b/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
new file mode 100644
index 0000000..95b085a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
@@ -0,0 +1,18 @@
+# VMware Support Statement
+
+## About this task
+
+Morpheus Data will support customers who run HPE Morpheus Enterprise products on supported operating systems, irrespective of whether they are running in VMware environments or not. Morpheus Data supports operating systems, not specific hardware configurations. Accordingly, VMware operates as a hardware abstraction layer.
+
+VMware supports a set of certified operating systems and hardware. The customer and VMware will be responsible for any interactions or issues that arise at the hardware or operating system layer as a result of their use of VMware.
+
+Morpheus Data will not require clients to recreate and troubleshoot every issue in a non-VMware environment; however, Morpheus Data does reserve the right to request our customers to diagnose certain issues in a native certified operating system environment, operating without the virtual environment. Morpheus Data will only make this request when there is reason to believe that the virtual environment is a contributing factor to the issue.
+
+Any time spent on investigation of problems that may, in the sole opinion of Morpheus Data be related to VMware, will be handled in the following fashion:
+
+## Procedure
+
+1. Morpheus Data will provide standard support to all HPE Morpheus Enterprise products.
+2. If a problem is encountered while HPE Morpheus Enterprise is/are running in a VMware environment, the client may be required to recreate the problem on a non-VMware server unit, at which time Morpheus Data will provide regular support.
+3. The client can authorize Morpheus Data to investigate the VMware-related items at normal time and materials rates. If such investigation shows that the problem is VMware related, the client may contract Morpheus Data to provide a software change to resolve the issue if such a resolution is possible.
+4. Regardless of the problem type or source, if the problem is determined to be a non VMware-related issue, time spent on investigation and resolution will be covered as part of regular maintenance and support will be provided as usual.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json b/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
new file mode 100644
index 0000000..031525f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+  "title": "Provisioning an Instance",
+  "ordinal": 417,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md b/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
new file mode 100644
index 0000000..fb5d011
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
@@ -0,0 +1,31 @@
+# Provisioning an Instance
+
+## About this task
+
+Perform the following steps to provision an instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.   
+   ![Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-C7BB967B-5DC0-4932-8F24-0AD471BB5430-high.png)
+2. Click the + ADD.
+3. In the TYPE tab, select the Instance Type as HPE Bare Metal (ILO) SERVER.  
+   ![Type](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D8ED39AD-773F-408D-9AC6-075C86E99337-high.png)
+4. In the GROUP tab, complete the Instance Summary fields.  
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-7F89FF6E-7D74-47A0-8C79-7564B839ED39-high.png)
+5. In the CONFIGURE tab, complete the Configuration Options:
+
+   1. Layout: Select the appropriate layout from the drop-down list (for example, Single iLO Server).
+   2. Service Plan: Choose one of the following:
+
+      - Generic Plan: Any iLO
+      - Specific Plan: For example, DL360.Gen10Plus.1-32C.129-256GiB
+   3. Resource Pool: Select the required resource pool from the drop-down list.
+   4. Volumes: Configure storage volumes as required. Refer to the Storage section for details.
+   5. Networks: Configure network settings as required. Refer to the Networking section for details.
+   6. Image: Select the Bare Metal OS image from the drop-down list.
+   7. Baremetal Host(s): Select the target Bare Metal host(s) from the drop-down list if specific server(s) are desired.  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-CC32AE45-9726-469E-B453-4ADF3113B80B-high.png)
+6. In the AUTOMATION tab, select the appropriate options, then click Next.
+7. In the REVIEW tab, verify the configuration summary and click Complete.   
+   ![Review](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-86C9130B-3808-4D68-AD5F-75D408B4B4C8-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json b/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
new file mode 100644
index 0000000..17e984f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+  "title": "Requirements",
+  "ordinal": 80,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md b/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
new file mode 100644
index 0000000..6761dbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
@@ -0,0 +1,231 @@
+# Requirements
+
+Provisioning Instances and Apps typically involves many steps beyond starting a workload. HPE Morpheus Enterprise is centered around automating everything desired for your application to be fully operational, including networking, storage, hostnames, domains, dns, licenses, scripts/automation, scaling, load balancers, security, accessibility, governance, auditing, monitoring, backups, costs, sizing and on and on. Point being there is a lot that goes on when spinning up an instance or app, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Images or SKIP AGENT INSTALL is selected when provisioning.
+
+## VM Provision Steps
+
+While an infinite number of steps can happen when provisioning an Instance or App using VM(s) in HPE Morpheus Enterprise, the basic order is:
+
+- Look for Virtual Image
+
+  HPE Morpheus Enterprise will check if the Virtual Image set on the Node Type or selected during provisioning is already available in the source Cloud. If not and it is an Uploaded/Local Image, HPE Morpheus Enterprise will attempt to upload the Image to the target Cloud.
+
+  **Upload Image**
+
+  For Uploaded/Local Images that do not exist in the target cloud, HPE Morpheus Enterprise will need to upload the Image. Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, HPE Morpheus Enterprise will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, HPE Morpheus Enterprise will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, HPE Morpheus Enterprise will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   HPE Morpheus Enterprise will run Guest Customizations via VMware VM Tools, including network config when assigning static IP’s.
+- Wait for Power On status and Network info
+
+  HPE Morpheus Enterprise will wait to hear back from the target cloud/hypervisor that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, HPE Morpheus Enterprise will skip waiting for network.
+- Finalize
+
+  By default this will include Agent Installation and any post-provision scripts or workflows or integration automation steps.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for longs periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
+
+## Virtual Images
+
+While containers are the future, the most common provisioning method involves Virtual Machines, and the most important part of Provisioning a VM is the Virtual Image. When provisioning a VM, HPE Morpheus Enterprise will need to do a few things depending on the location of the Virtual Image and if agent install, console access, and script execution is desired.
+
+Synced Images need to be properly configured
+:   HPE Morpheus Enterprise gathers as much metadata for synced images as possible, but depending on the cloud, os, image configuration, agent install settings, by default the synced Virtual Images may not be ready to provision until configured. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, and networks and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to HPE Morpheus Enterprise are configured during the Add Virtual Image process, however HPE Morpheus Enterprise in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required and network and image configurations can cause upload failures, resulting in provisioning issues.
+
+Marketplace Images
+:   AWS and Azure marketplace Images can be provisioned using the generic Amazon or Azure Instance Types, or added as Virtual Images as scoped to Node Types for custom Instance Types. Marketplace items provisioned/added to HPE Morpheus Enterprise still fall upon the requirements of the target Cloud, such as matching the region with the Image and licensing.
+
+### Synced Images
+
+When a Cloud is added to HPE Morpheus Enterprise, all available Images/Templates records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These Image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type, ie VMware, Amazon, Azure, Openstack etc Instance Types, or by creating custom Instance Types and selecting the Image on a Node Type.
+
+NOTE
+
+Synced Virtual Images are just meta-data records in HPE Morpheus Enterprise pointing to the Image in the target Cloud. The actual Image files are not copied/imported to HPE Morpheus Enterprise.
+
+Before provisioning a synced Virtual Images, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the Image, but editing will not change the name of the actual Image.
+
+Operating System
+:   Specifies the Platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the Platform for all Images without Operating System specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Service Plans options during provisioning. Service Plans that do not meet the Minimum Memory value set on the Virtual Image will not be provided as Service Plan choices.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are collected for agent-less hosts and vm’s from VMware and AWS clouds).
+
+Username
+:   Existing Username on the Image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the Existing User on the image if Username is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is /var/opt/morpheus/morpheus-ui/VMs. Additional Storage Providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in runcmd and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Permissions
+:   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. No impact on single-tenant environments.
+    :   Visibility
+        :   Private
+            :   Image is only available in the specified Tenants below.
+
+            Public
+            :   Image is available to all Tenants.
+
+        Tenant
+        :   If Visibility is set to Private, specify Tenants the Image will be available for.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM based Hypervisors.
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+Enabled Sysprep?
+:   Applicable to Nutanix Only. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject Unattend.xml through the Nutanix API (v3+ only)
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-Init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
+
+### Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to HPE Morpheus Enterprise. To provision, HPE Morpheus Enterprise will need to upload the Image to the target Cloud upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a Local Virtual Image has been uploaded to a Cloud, subsequent provisions will use the Image local to the cloud instead of uploading again as long as the copied image is still available in the source Cloud.
+
+## Agent Install
+
+When provisioning an instance, there are some network and configuration requirements to successfully install the morpheus agent. Typically when a vm instance is still in the provisioning phase long after the vm is up, the instance is unable to reach HPE Morpheus Enterprise, or depending on agent install mode, HPE Morpheus Enterprise is unable to reach the instance.
+
+The most common reason an agent install fails is the provisioned instance cannot reach the HPE Morpheus Enterprise Appliance via the appliance\_url set in Administration > Settings over both 443 and 80. When an instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the appliance\_url or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main appliance\_url in Administration > Settings, additional appliance\_urls can be set per cloud in the Advanced options of the cloud configuration pane when creating or editing a cloud. When this field is populated, it will override the main appliance url for anything provisioned into that cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting agent installations.
+
+### Agent Install Modes
+
+There are 3 Agent install modes:
+
+- ssh/winrm
+- VMware Tools
+- cloud-init
+
+#### For All Agent Install modes
+
+When an instance is provisioned and the agent does not install, verify the following for any agent install mode:
+
+- The HPE Morpheus Enterprise appliance\_url (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The appliance\_url begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise Appliance from provisioned VM’s and container hosts on port 443 (needed for agent communication)
+- Private (non-morpheus provided) vm images/templates must have their credentials entered. These can be entered/edited in the Library > Virtual Images section but clicking the Actions dropdown of an image and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to clouds network sections for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or cloud appliance.
+
+### SSH/Winrm
+
+#### Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+![../_images/agent_ssh.gif](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D2F4F5EE-5377-4E4A-A6E8-DAD6ED4FBD80-high.gif)
+
+#### Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+### VMware tools (vmtools) rpc mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
+
+### Cloud-Init agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image/blueprint has Cloud-Init (linux) or Cloudbase-Init (windows) installed
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json b/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
new file mode 100644
index 0000000..dabb143
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+  "title": "Integrations",
+  "ordinal": 311,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md b/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
new file mode 100644
index 0000000..40e121e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
@@ -0,0 +1,26 @@
+# Integrations
+
+NOTE
+
+To add and edit certain integrations such as Ansible Tower, vRO, Chef and Puppet, the user must have FULL permission for “Library: Integrations” in addition to “Admin: Integrations”.
+
+To add an integration select + ADD and choose your integration. Many HPE Morpheus Enterprise-supported integrations can be configured in this section, though not all. Some integrations, such as networking integrations, must be configured within their own areas of the application. The following integrations can be configured in this section:
+
+- Chef
+- Puppet
+- Ansible
+- Ansible Tower
+- vRealize Orchestrator
+- Microsoft DNS
+- PowerDNS
+- Route 53
+- Bind DNS
+- Git
+- Github
+- Docker Repositories
+- Jenkins
+- ServiceNow
+- Cherwell
+- Remedy
+
+Refer the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) for each specific integration type for more detailed information on setup steps and features supported by the integration.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json b/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
new file mode 100644
index 0000000..912f746
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+  "title": "Initial Appliance Setup",
+  "ordinal": 39,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Appliance Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md b/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
new file mode 100644
index 0000000..2786f2d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
@@ -0,0 +1,80 @@
+# Initial Appliance Setup
+
+## Appliance Setup
+
+### About this task
+
+After installation, log into the appliance at the URL presented upon completion. An initial setup wizard walks through the first account and user creations.
+
+### Procedure
+
+1. Enter Master Account name 
+
+   - Typically, the Master Account name is your Company name.
+2. Create Master User 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email Address
+   - Password \* Must be at least 8 characters long and contain one each of the following: Uppercase letter, lowercase letter, Number, Special Character
+3. Enter Appliance Name & Appliance URL 
+
+   - The Appliance Name is used for white labeling and as a reference for multi-appliance installations.
+   - The Appliance URL is the URL all provisioned instances will report back to. Example: <https://example.morpheusdata.com>. The Appliance URL can be changed later, and also set to a different URL per cloud integration.
+4. Optionally Enable or Disable Backups, Monitoring, or Logs from this screen. 
+
+   NOTE
+
+   You may adjust these settings from the Administration section.
+
+   NOTE
+
+   The Master Account name is the top-level admin account.
+
+   NOTE
+
+   The Master User is the system super user and will have full access privileges.
+
+### Results
+
+Upon completing of the initial appliance setup, you will be taken to the Administration > Settings page, where you will add your License Key.
+
+## Login Methods
+
+Master Tenant
+
+- Enter username (or email address) and password
+
+Subtenant
+
+To login, subtenants can either use the master tenant URL with `subtenant\username` formatting:
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
+
+Or use the tenant specific URL which can be found and configured under Administration > Tenants > Select Tenant > IdentitySources.
+
+![../../_images/tenant_url.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-24D6CCD6-E864-4CA6-8D91-5EFDFB50CB33-high.png)
+
+IMPORTANT
+
+In 3.4.0+ Subtenant users will no longer be able to login from the main login url without specifying their subdomain.
+
+## Configure Cloud-init Global Settings
+
+When using cloud-init, cloudbase-init, VMware Tools customizations, or Nutanix Sysprep, Global Linux User and Windows Administrator credentials can be set using the settings in Administration > Settings > Provisioning. It is recommended to define these settings after installation unless credentials are defined per Virtual Image for Provisioning.
+
+## Add a License Key
+
+In order to provision anything in HPE Morpheus Enterprise, a HPE Morpheus Enterprise License Key must be applied.
+
+If you do not already have a license key, one may be requested from <https://app.morpheushub.com> or from your HPE Morpheus Enterprise representative.
+
+In the Administration > Settings section, select the LICENSE tab, paste your License Key and click UPDATE
+
+![../../_images/license_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-1DE90FFC-D78A-4AEC-B168-D1AF1DF3E611-high.png)
+
+When the license is accepted, your license details will populate in the Current License section.
+
+If you receive an error message and your license is not accepted, please check it was copied in full and then contact your HPE Morpheus Enterprise representative. You can also verify the License Key and expiration at <https://app.morpheushub.com>.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json b/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
new file mode 100644
index 0000000..1a11e32
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+  "title": "Power Scheduling",
+  "ordinal": 123,
+  "parent_title": "Automation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html",
+  "topic_cluster": {
+    "clustering_title": "Power Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md b/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
new file mode 100644
index 0000000..808fd36
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
@@ -0,0 +1,114 @@
+# Power Scheduling
+
+Set weekly schedules for shutdown and startup times for Instances and VM’s, apply Power Schedules to Instances pre or post-provisioning, apply Power Schedule policies on Group or Clouds, or use Guidance to automatically recommend and apply optimized Power Schedules.
+
+## Create Power schedules
+
+### Procedure
+
+1. Navigate to Library > Automation > Power Scheduling
+2. Select + ADD
+3. Configure the following options: 
+
+   NAME
+   :   Name of the Power Schedule
+
+   DESCRIPTION
+   :   Description for the Power Schedule
+
+   TIME ZONE
+   :   Time Zone the Power Schedule times correlate to.
+
+   TYPE
+   :   Power On
+       :   Power Up and then Down at scheduled times
+
+       Power off
+       :   Power Down then Up at scheduled times
+
+       Enabled
+       :   Check for Power Schedule to be Active. Uncheck to disable Power Schedule.
+
+       DAYS
+       :   Slide the start and end time controls for each day to configure each days Schedule. Green sections indicate Power on, red sections indicate Power Off. Time indicated applies to selected Time Zone. The sliders can be used to set time in 15-minute steps, for single-minute granularity click the pencil icon and enter a specific time down to the minute.
+
+   ![../../_images/powerSchedule.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3FAFD413-3475-44A9-811A-575B689D836D-high.png)
+4. Select SAVE CHANGES
+
+### Results
+
+TIP
+
+To view the Instances a power schedule is currently set on, select the name of a Power Schedule to go to the Power Schedule Detail Page.
+
+## Add Power Schedule to Instance
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Select an Instance
+3. Select EDIT
+4. In the POWER SCHEDULE dropdown, select a Power Schedule.
+5. Select SAVE CHANGES
+
+## Add Power Schedule to Virtual Machine
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Compute  >  Virtual Machines
+2. Select a Virtual Machine
+3. Select EDIT
+4. Expand the Advanced Options section
+5. In the POWER SCHEDULE dropdown, select a Power Schedule.
+6. Select SAVE CHANGES
+
+## Add Power Schedule Policy
+
+### About this task
+
+NOTE
+
+Power Schedule Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD
+3. Select TYPE Power Schedule
+4. Configure the Power Schedule Policy: 
+
+   NAME
+   :   Name of the Policy
+
+   DESCRIPTION
+   :   Add details about your Policy for reference in the Policies tab.
+
+   Enabled
+   :   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Clouds Instances until re-enabled.
+
+   ENFORCEMENT TYPE
+   :   - User Configurable: Power Schedule choice is editable by User during provisioning.
+       - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+   POWER SCHEDULE
+   :   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+   SCOPE
+   :   Global
+       :   Applies to all Instances created while the Policy is enabled
+
+       Group
+       :   Applies to all Instances created in or moved into specified Group while the Policy is enabled
+
+       Cloud
+       :   Applies to all Instances created in specified Cloud while the Policy is enabled
+
+       User
+       :   Applies to all Instances created by specified User while the Policy is enabled
+
+       Role
+       :   Applies to all Instances created by Users with specified Role while the Policy is enabled
+
+   Permissions- TENANTS
+   :   Leave blank to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+5. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..0bcf1bf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 322,
+  "parent_title": "Settings",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..54e61d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,189 @@
+# Appliance
+
+## Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the HPE Morpheus Enterprise API. For example, if you were designing a web application which needed to make AJAX calls to HPE Morpheus Enterprise API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Incident Retainment
+:   Enter the number of days HPE Morpheus Enterprise should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the HPE Morpheus Enterprise appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured HPE Morpheus Enterprise Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of HPE Morpheus Enterprise documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
+
+Dashboards to Display
+:   A typeahead field which will show all Dashboards available to the appliance from Dashboard-type plugins. Select all desired Dashboards and they will be displayed in the order set. Dashboards can be dragged up and down the list to set the order correctly.
+
+## Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+## User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
+
+## Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide HPE Morpheus Enterprise the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the HPE Morpheus Enterprise server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into HPE Morpheus Enterprise, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the HPE Morpheus Enterprise appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your HPE Morpheus Enterprise server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
+
+## Twilio SMS Settings
+
+Configure SMS text message delivery for HPE Morpheus Enterprise alerts. Previously, customers could use HPE Morpheus Enterprise’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all HPE Morpheus Enterprise nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
+
+## Proxy Settings
+
+The HPE Morpheus Enterprise Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+
+  : Specifies the hostname or IP address of the proxy server.
+- Proxy Port
+
+  : Specifies the port number used by the proxy server to communicate.
+- Proxy User
+
+  : Specifies the username used to authenticate with the proxy server.
+- Proxy Password
+
+  : Specifies the password associated with the proxy user account.
+- Proxy Domain
+
+  : Specifies the authentication domain for the proxy user.
+- Proxy Workstation
+
+  : Specifies the workstation name used for proxy authentication.
+- No Proxy
+
+  : Specifies a list of hosts that should bypass the proxy.
+
+## Currency Settings
+
+In HPE Morpheus Enterprise, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, HPE Morpheus Enterprise allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
+
+## Integrating With a Currency Exchange Provider
+
+### Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+### Results
+
+The service is now integrated and can be used as described in the next section.
+
+## Consuming Currency Exchange in HPE Morpheus Enterprise
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
+
+## Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json b/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
new file mode 100644
index 0000000..aec444b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+  "title": "Adding the OpenShift Plugin",
+  "ordinal": 206,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html",
+  "topic_cluster": {
+    "clustering_title": "Adding the OpenShift Plugin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md b/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
new file mode 100644
index 0000000..f782676
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
@@ -0,0 +1,13 @@
+# Adding the OpenShift Plugin
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise, which is not included in the product by default.
+
+1. To download the plugin, navigate to the plugin share site (share.morpheusdata.com) and browse or search for the OpenShift plugin
+2. With the plugin downloaded to your workstation, navigate to the plugins list page (Administration > Integrations > Plugins) in HPE Morpheus Enterprise UI
+3. Click Add
+4. Browse for the plugin JAR or drag and drop it onto the target
+5. Click Upload
+
+After a few brief moments, the new plugin will be added. This plugin adds a new Cluster type, which can be added from the Clusters list page (Infrastructure > Clusters) and also adds a new Instance Type which can be provisioned from the Instance provisioning wizard once a compatible cluster is integrated.
+
+Further configuration and usage details are covered in later sections of this guide.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json b/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
new file mode 100644
index 0000000..de6493e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+  "title": "See Also",
+  "ordinal": 529,
+  "parent_title": null,
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.html",
+  "topic_cluster": {
+    "clustering_title": "See Also",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md b/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
new file mode 100644
index 0000000..ec3d0f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
@@ -0,0 +1,14 @@
+# See Also
+
+**Subtopics**  
+
+- **[Navigation Updates](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html)**
+- **[Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798_2.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA_2.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2_2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42_2.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD_2.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F_2.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8_2.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json b/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
new file mode 100644
index 0000000..fc9455f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+  "title": "Failover",
+  "ordinal": 190,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md b/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
new file mode 100644
index 0000000..ebaad69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
@@ -0,0 +1,17 @@
+# Failover
+
+HVM supports automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+This three-node cluster has three VMs running on the first host:
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json b/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
new file mode 100644
index 0000000..adaa1ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+  "title": "Provisioning Images",
+  "ordinal": 150,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md b/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
new file mode 100644
index 0000000..f77c843
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, HPE Morpheus Enterprise will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced, marketplace, or previously copied images, no image stream from S3 through the HPE Morpheus Enterprise Appliance to the destination cloud will take place.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json b/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
new file mode 100644
index 0000000..7d4ff4c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+  "title": "Creating Apps",
+  "ordinal": 88,
+  "parent_title": "Apps",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md b/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
new file mode 100644
index 0000000..6510e27
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
@@ -0,0 +1,56 @@
+# Creating Apps
+
+New Apps can be created from Blueprints or using existing Instances.
+
+## Creating Apps from Blueprints
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select an existing App Blueprint and click NEXT. 
+
+   NOTE
+
+   App Blueprints must be created in Library > Blueprints > App Blueprints to appear as options when provisioning an App.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected.
+4. Click NEXT. Blueprint configurations matching the Group, Cloud and Environment selections will auto-populate the configurations of the Instances in the App. If no Blueprint Configuration matched the Group, Cloud or Env selections, the Instances will have default configurations.
+5. Configure your Instances. Depending on the Blueprint Configurations settings, instances may already be fully configured. Fields that are locked in a Blueprint cannot be edited when creating an App. 
+
+   NOTE
+
+   Once an Instance is fully configured, a green checkmark will appear next to the Instance. Instances that have required fields that need populated will have a red X and must be completed. If your Blueprint is already fully configured, you can simply select COMPLETE!
+6. Select COMPLETE and the App will be created, and the Instances will begin provisioning.
+
+### Results
+
+![../../_images/apps_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-F0EDC63A-480C-4013-AC6D-A1C51BA13CC7-high.png)
+
+## Creating Apps from Existing Instances
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select `APP FROM EXISTING INSTANCES` from the Blueprints list and click NEXT.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected. 
+
+   NOTE
+
+   Only instances within the selected Group and Cloud will be available to be added to the App.
+4. In the STRUCTURE section, select + to add a Tier
+5. Select or enter a Tier Name.
+6. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+7. In the STRUCTURE section, select + in a Tier to add an Instance
+8. Select the Instance Type of the Existing Instance to be added to the App.
+9. In the STRUCTURE section, select the Instance.
+10. In the CONFIGURATION section, select the Cloud the Existing Instance is in. Existing INSTANCES that match the Group, Cloud and Instance Types set will populate.
+11. Select the desired Instance from the INSTANCES list. Selected instance will show in the SELECTED INSTANCE section. 
+
+    NOTE
+
+    Only one existing Instance can be added per Instance. To add multiple Existing Instances, repeat the step above including adding an Instance for each Existing Instance to be added to the App.
+12. Once all Existing Instances have been selected, click COMPLETE.
+13. A new App will be created out of the Existing Instances.
+
+### Results
+
+![../../_images/apps_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-2EECD2F1-36D5-4E56-B12D-99872F54B075-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json b/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
new file mode 100644
index 0000000..fd500bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+  "title": "Boot Prompt Configuration",
+  "ordinal": 413,
+  "parent_title": "Windows OS Imaging",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Prompt Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md b/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
new file mode 100644
index 0000000..8675424
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
@@ -0,0 +1,30 @@
+# Boot Prompt Configuration
+
+Unmodified Microsoft Windows Server ISOs display a Press any key to boot CD/DVD… prompt, which will interrupt unattended bare metal deployments.
+
+Two approaches are supported:
+
+- Option 1: Use a Modified ISO (Recommended)
+- Option 2: Manual Console Interaction
+
+## Option 1: Use a Modified ISO (Recommended)
+
+Use a Windows ISO with the boot prompt removed. A script to generate such an ISO is available at `https://github.com/HewlettPackard/hpegl-metal-os-windows-iso`
+
+Only the resulting ISO is required. A prebuilt Windows Server 2022 Evaluation ISO with this modification is also available and suitable for testing environments.
+
+## Option 2: Manual Console Interaction
+
+If using an unmodified ISO:
+
+1. Create the instance as usual.
+2. When the instance enters provisioning, open the Remote Console.
+3. Press Enter when prompted to boot from the installation media.
+
+## Windows Licensing Considerations
+
+At present, Windows licensing is not supported during bare metal provisioning.
+
+Only Evaluation editions or versions that do not require a Product Key in AutoUnattend.xml can be deployed.
+
+The modified Windows Server 2022 ISO referenced above is an Evaluation edition and is suitable for testing.
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json b/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
new file mode 100644
index 0000000..f85783b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+  "title": "Installation Overview",
+  "ordinal": 15,
+  "parent_title": "Installation",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html",
+  "topic_cluster": {
+    "clustering_title": "Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md b/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
new file mode 100644
index 0000000..d86e675
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
@@ -0,0 +1,111 @@
+# Installation Overview
+
+IMPORTANT
+
+HPE Morpheus Enterprise v4.2.0 enhanced security configuration restricts incoming appliance connections to TLS v1.2, potentially impacting front-end load balancer monitoring/health checks that support only TLS v1.1 or lower, as well as HPE Morpheus Enterprise Agent installations for Windows nodes using .net versions that do not support TLS v1.2. Refer to TLS
+
+HPE Morpheus Enterprise comes packaged as a `debian` or `yum` based package. The default configuration installs all required services on a single vm or bare metal Host. Morpheus can be configured in a distributed architecture to use one or multiple external services, and multiple application Hosts can be configured for High Availability configurations.
+
+All components required for Morpheus are installed and configured by default during the Morpheus `reconfigure` command. The Morpheus config file, `morpheus.rb`, can optionally be configured to point the Morpheus App to external services (distributed configuration).
+
+Morpheus can optionally be configured to use external Database, Messaging, and/or Search Tiers. This means instead of installing, for example, MySQL on the same host as the Morpheus App, the Morpheus configuration file (morpheus.rb) is setup to point to an external MySQL host, cluster or service, and MySQL will not be installed or configured on the Appliance Host.
+
+## Install Packages
+
+HPE Morpheus Enterprise Release Package URLs can be obtained from My HPE Software Center.
+
+## Configuration Options
+
+- Single Host (All-In-One/default)
+  :   All tiers running on a single host. The reconfigure process installs all required services. This is the default configuration.
+- Single Hosts with Distributed Service(s)
+  :   Transactional Database, Non-Transactional Database, and/or Message tiers are externalized, with the remaining services on a single host. The reconfigure process installs all services not set to false in `/etc/morpheus/morpheus.rb`
+- Clustered Hosts with Distributed Transactional Database (3-Node HA)
+  :   Application, Message and Non-Transactional tiers are installed and clustered on three or more hosts, with all three hosts pointing to externalized database tier. The reconfigure process installs all services except mySQL.
+- App Host(s) with Distributed Services (Full HA)
+  :   Application tier is installed on one or more hosts. All UI hosts point to externalized Transactional Database, Non-Transactional Database, and Message Tiers. The reconfigure process installs only Application services.
+
+## Distributed Configurations
+
+Morpheus provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the Morpheus HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the Morpheus appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Message Tier. Each of these tiers have their own recommendations for High availability deployments that we need to cover.
+
+### Application Tier
+
+The application tier is easily installed with the same Debian or yum repository package that Morpheus is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. These machines should also have at least 8gb of Memory. They can be configured across all regions and placed behind a central load-balancer or Geo based load-balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is a shared storage means is necessary when it comes to maintaining things like deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. If not using those options a simple NFS cluster can also be used to handle the shared storage structure.
+
+### Transactional Database Tier
+
+The Transactional database tier usually consists of a MySQL-compatible database. It is recommended that a lockable clustered configuration be used. There are several documents online related to configuring and setting up such a cluster but it most simply can be laid out in a many-master configuration. There can be some nodes setup with replication delay as well as some with no replication delay. It is common practice to have no replication delay within the same region and allow some replication delay cross region. This does increase the risk of job run overlap between the 2 regions however, the concurrent operations typically self-correct and this is a non-issue.
+
+### Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an OpenSearch (version 7.6.0) cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a Java-based system and does require a sizable chunk of memory for larger data sets. 8 GB is recommended and more nodes can be added to scale either horizontally or vertically.
+
+### Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster, it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. The ports necessary to forward in a Rabbit MQ cluster are (5672, and 61613). A RabbitMQ cluster can run on smaller memory machines depending on how frequent large requests bursts occur. 4 - 8 GB of Memory is recommended to start.
+
+## Pros/Cons
+
+### Single Host
+
+Advantages
+:   - Simple Installation - Morpheus Installs all required services
+    - Simple Configuration - Morpheus configures all required services
+    - Simple Maintenance - All service connections and credentials are local - All logs are local - All Data is local (by default)
+    - Not dependent on network connections for vital services - Facilitates speed and reliability
+
+Disadvantages
+:   - Single point of failure
+    - Individual services cannot be scaled
+    - Upgrades require (minimal) downtime
+    - Single region
+
+### Single Hosts with Distributed Service(s)
+
+Advantages
+:   - Individual services can be scaled
+    - Managed Services such as RDS can be utilized
+
+Disadvantages
+:   - Single region
+    - External services require additional configuration and maintenance
+    - Morpheus is subject to network performance, configuration and availability
+    - Increased Installation time possible
+
+### Clustered Hosts with Distributed Transactional Database
+
+Advantages
+:   - Database can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - RabbitMQ and Opensearch Clusters
+
+Disadvantages
+:   - External Database services requires additional configuration and maintenance
+    - App Host Clustering requires additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+
+### App Host(s) with Distributed Services
+
+Advantages
+:   - Individual services can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - Multi region support
+
+Disadvantages
+:   - External services require additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure Requirements
+    - Increased Networking requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+    - Rabbit Load balancer required
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json b/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
new file mode 100644
index 0000000..6023a79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_1",
+  "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+  "title": "Costing: Budget Analysis",
+  "ordinal": 63,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007621en_us",
+  "version": "8.1.1",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007621en_us&page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Budget Analysis",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_2",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md b/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
new file mode 100644
index 0000000..88ec790
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_1/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
@@ -0,0 +1,25 @@
+# Costing: Budget Analysis
+
+![../_images/6budgetanalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007621en_us/GUID-D7C44885-681F-4B92-8D83-E5EB52F25660-high.png)
+
+The Budget Analysis dashboard allows administrators to filter and view budgets in one place in order to keep track of progress against budget over time. Budgets in HPE Morpheus Enterprise (Operations > Budgets) are tied to a specific scope (Account, Tenant, Cloud, Group, or User) and budgets of the same scope are viewed together in this dashboard. A scope filter must be set in order for data to be populated into the dashboard. Once a scope is selected, the search bar can be utilized to return only budgets within the selected scope whose “Name” meets the search terms.
+
+## Filters
+
+Filter the budgets pulled into the dashboard by one or more of the following fields:
+
+- Budget name (all matched by search)
+- Scope (This is a required field, data is not populated into the dashboard until a scope is specified)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all budgets that meet set filters:
+
+- **BUDGETS:** The total number of budgets that meet set filters
+- **MONTH TO DATE:** The total spend in the current month against the selected budgets
+- **BUDGETS TO DATE:** The total amount budgeted to date among budgets selected by the dashboard filters (from the start of the year to the end of the current interval)
+- **TO BUDGET:** The difference between the COST TO DATE and BUDGETS TO DATE value, should be close to $0 if the costs are appropriately tracking against the budgeted amounts
+
+## Budget List
+
+Each budget with its own graph and breakdown is displayed going down the page. The format of the information presented depends on the interval that the specific budget is configured for.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json b/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
new file mode 100644
index 0000000..89a8a3c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+  "title": "SSL Self-signed Certificate Regeneration",
+  "ordinal": 356,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Self-signed Certificate Regeneration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F",
+        "clustering_title": "SSL Self-signed Certificate Regeneration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md b/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
new file mode 100644
index 0000000..0099ff5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.md
@@ -0,0 +1,19 @@
+# SSL Self-signed Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year self-signed non-trusted SSL certificate. Below details the process to regenerate this certificate and key.
+
+## Replacing both the certificate and private key
+
+### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/` that end in `.crt` and `.key`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
+
+## Replacing only the certificate
+
+### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/` it ends in `.crt`
+2. Run Reconfigure `morpheus-ctl reconfigure`
+3. Restart NGINX `morpheus-ctl restart nginx`
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json b/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
new file mode 100644
index 0000000..82ade96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+  "title": "Settings",
+  "ordinal": 321,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html",
+  "topic_cluster": {
+    "clustering_title": "Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1",
+        "clustering_title": "Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md b/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
new file mode 100644
index 0000000..90deb87
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.md
@@ -0,0 +1,18 @@
+# Settings
+
+The Administration > Settings section sets global configuration parameters for the HPE Morpheus Enterprise appliance, whitelabeling, provisioning, monitoring, backups, logs, software licenses, and the license for HPE Morpheus Enterprise itself.
+
+**Subtopics**  
+
+- **[Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html)**
+- **[Whitelabel](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html)**
+- **[Email Templates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5_2.html)**
+- **[Clients](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html)**
+- **[Environments](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html)**
+- **[Software Licenses](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html)**
+- **[License](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html)**
+- **[Utilities](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json b/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
new file mode 100644
index 0000000..f02c546
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+  "title": "Load Balancers",
+  "ordinal": 227,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md b/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
new file mode 100644
index 0000000..f19daaa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.md
@@ -0,0 +1,88 @@
+# Load Balancers
+
+The Load Balancers tab list currently available Load Balancers, which you can select, edit or delete, and is where you can create new or integrate with external Load Balancers.
+
+## Configuration parameters to add a new load balancer
+
+Following parameters are required configure the respective load balancers:
+
+Amazon ALB
+:   - Scheme
+    - Internal
+    - Internet-Facing
+    - Amazon Subnets (Select + to add additional) \* Specify the subnets to enable for your load balancer. You can specify only one subnet per Availability Zone. You must specify subnets from at least two Availability Zones to increase the availability of your load balancer.
+    - Amazon Security Groups (Select + to add additional)
+
+      For details, see [Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html).
+
+Azure load balancer
+:   - Cloud
+    - Resource Group \* Populated from cloud selection
+
+      For details, see [Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html).
+
+Citrix NetScaler
+:   - API Host
+    - API Port
+    - Username
+    - Password
+
+      For details, see [Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html).
+
+F5 BigIP (v11.4+)
+:   - API Host
+    - API Port
+    - Username
+    - Password
+    - Management URL
+
+      For details, see [Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html).
+
+FortiADC
+:   - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - INTERFACE (synced on auth)
+
+      For details, see [Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html).
+
+HaProxy Container (Internal, will create a HaProxy container, must have available docker host to provision to)
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - Plan \* Select the size of HaProxy container to be provisioned
+
+      For details, see [Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html).
+
+NSX load balancer
+:   - NSX
+    - Name
+    - Description
+    - Enabled
+    - Admin State
+    - Size
+    - Tier-1 Gateways
+    - Log Level
+
+      For details, see [Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html).
+
+NSX Advanced load balancer
+:   - Group
+    - Cloud
+    - Name
+    - Description
+    - API HOST
+    - API PORT
+    - USERNAME
+    - PASSWORD
+    - AVI CLOUD
+
+      For details, see [Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html).
+
+Upon saving, your new load balancer will be added to the load balancers list and available in the load balancer drop-down list under the Provisioning Wizard Automation Section for Instance Types that have scaling enabled.
+
+### Load Balancer Detail Pages
+
+In the main Load Balancer page, select an existing Load Balancer to go to that Load Balancers Details Page, which lists Stats, Settings, Actions and Virtual Servers for that load balancer.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json b/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
new file mode 100644
index 0000000..2407c42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+  "title": "Ansible Troubleshooting",
+  "ordinal": 346,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5",
+        "clustering_title": "Ansible Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md b/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
new file mode 100644
index 0000000..c004156
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.md
@@ -0,0 +1,52 @@
+# Ansible Troubleshooting
+
+When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in UI logs at `/var/log/morpheus/morpheus-ui/current​`. These can be tailed by running `morpheus-ctl tail morpheus-ui`.
+
+## Verify Ansible is installed on the HPE Morpheus Enterprise Appliance
+
+Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+### If Ansible is not installed
+
+Follow these instructions to install, or use your preferred installation method
+
+Ubuntu:
+
+```
+```
+sudo apt-get install software-properties-common  
+sudo apt-add-repository ppa:ansible/ansible  
+sudo apt-get update  
+sudo apt-get install ansible python-requests
+```
+```
+
+CentOS:
+
+```
+```
+sudo yum install epel-release  
+sudo yum install ansible python-requests
+```
+```
+
+Then create the working Ansible directory for Morpheus:
+
+```
+```
+sudo mkdir /opt/morpheus/.ansible  
+sudo chown morpheus-app.morpheus-app /opt/morpheus/.ansible
+```
+```
+
+## Validate Git repo authorization and the configured paths
+
+The public and private SSH keys need to be added to the HPE Morpheus Enterprise appliance via Infrastructure  >  Keys & Certs and the public key needs to be added to the Git repo via user settings. If both are set up correctly, you will see the playbooks and roles populate in the Ansible Integration details page.
+
+The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+
+When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+
+NOTE
+
+If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json b/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
new file mode 100644
index 0000000..aa8610f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+  "title": "Provisioning a New Server",
+  "ordinal": 415,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a New Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C",
+        "clustering_title": "Provisioning a New Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md b/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
new file mode 100644
index 0000000..b32899d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.md
@@ -0,0 +1,9 @@
+# Provisioning a New Server
+
+Provisioning a new server allows onboarding new, unmanaged HPE ProLiant servers into a Bare Metal Cloud environment, enabling HPE Morpheus to manage their lifecycle, including automated OS deployment and hardware monitoring.
+
+**Subtopics**  
+
+- **[Importing HPE ProLiant Bare Metal Servers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html)**
+- **[Provisioning an Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html)**
+- **[Post-Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json b/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
new file mode 100644
index 0000000..cc9840e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+  "title": "CyberArk Conjur",
+  "ordinal": 526,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html",
+  "topic_cluster": {
+    "clustering_title": "CyberArk Conjur",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-030A6638-D9C6-492A-A021-8634B29738F7",
+        "clustering_title": "CyberArk Conjur"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md b/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
new file mode 100644
index 0000000..7d03d98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-030A6638-D9C6-492A-A021-8634B29738F7.md
@@ -0,0 +1,63 @@
+# CyberArk Conjur
+
+HPE Morpheus Enterprise supports integration with CyberArk Conjur for stored credential sets as well utilization of Conjur-stored secret values via HPE Morpheus Enterprise Cypher service. This works identically to built-in credential storage and built-in Cypher functionality with the exception that your Conjur server is the storage backend rather than the HPE Morpheus Enterprise appliance itself. In some cases, this may help to consolidate secret management into one central place or it even may be a requirement to satisfy internal security policies at some organizations.
+
+CyberArk Conjur integration is not included with HPE Morpheus Enterprise out of the box. It is developed as an official plugin and may be applied to any HPE Morpheus Enterprise appliance that needs it. See the HPE Morpheus Enterprise plugin repository website for access to the latest version of the plugin.
+
+## Applying the Plugin
+
+The latest version of the CyberArk Conjur plugin is available at the HPE Morpheus Enterprise [plugin share site](https://share.morpheusdata.com/). Select the pane for the correct plugin and click the DOWNLOAD button. The plugin JAR file will be downloaded to the local computer you’re working on.
+
+![../../_images/share.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C8A10069-9604-4478-904C-F916186AB33E-high.png)
+
+With the plugin downloaded, head back to HPE Morpheus Enterprise to apply the plugin to your appliance. Plugins are added by navigating to Administration > Integrations > Plugins and clicking ADD. Drop the plugin JAR file onto the target and click UPLOAD. It may take a few moments for the plugin to be applied successfully and for the modal to be dismissed after clicking the upload button.
+
+![../../_images/addPlugin.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ED50E88D-DE3D-419D-9071-B86CFBFD5BDD-high.png)
+
+Once the plugin is added, we configure the connection details here. Edit the new Conjur plugin by clicking the pencil (✎) icon from its row in the list. Configure the following fields:
+
+- **NAME:** A friendly name for the new integration to identify it within HPE Morpheus Enterprise
+- **ENABLED:** Mark the box to make this integration active and available
+- **CONJUR API URL:** The full URL for the Conjur server, usually listening on port 8443
+- **CONJUR USERNAME:** The Conjur user account you wish to authenticate with. This user should have read, write, and execute access to the variables configured within the Conjur policy
+- **CONJUR USERNAME API KEY:** The API key for user entered in the prior field
+- **CONJUR ORGANIZATION:** The Conjur account in which the user and variables reside
+- **CLEAR SECRET ON DELETION:** When marked, secret values will be cleared when deleted from HPE Morpheus Enterprise
+
+IMPORTANT
+
+Variables are predefined by Conjur policies. This integration does not allow users to create variables but does allow you to read and update their values. If the plugin is configured to clear secrets that are deleted from HPE Morpheus Enterprise, the variable value is updated with an empty value as there is no concept of fully deleting secrets in the Conjur API. If the plugin is configured not to clear secrets on deletion, the secret object is deleted from HPE Morpheus Enterprise without altering it on the Conjur backend.
+
+By applying and configuring the plugin, the appliance now has the Conjur/Cypher integration available. If you don’t intend to use the credential store integration, you can stop here and look ahead to the feature demonstration further ahead in this guide. If you do intend to use the credential store integration as well, there’s one additional configuration step to take in the next section.
+
+## Adding A Conjur Trust Integration
+
+In order to use Conjur with HPE Morpheus Enterprise credentials, we must also add a Conjur-type integration in Infrastructure > Trust > Integrations. By applying the plugin in the previous step, we now have the ability to add this type of integration. From the Trust integrations list page, click + ADD and select “Conjur.” It’s important to note that you **do not** need to again configure the API URL and Conjur login credentials as we just did in the previous step. You may configure them here if you wish, such as if you were making multiple integrations with multiple Conjur appliances, but if you’re simply integrating with the same appliance and user account, this is unnecessary. Simply give the new Trust integration a friendly name for reference in HPE Morpheus Enterprise and indicate the desired mount point for secrets you wish to consume as done in the screenshot below.
+
+NOTE
+
+In many cases, you don’t have to configure the connection details when adding a Conjur Trust integration. See the paragraph above.
+
+![../../_images/addTrustInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AE830924-B765-498F-98B6-154E38F1A4A5-high.png)
+
+## Conjur and Credential Stores
+
+With configurations completed, we can take a look at how HPE Morpheus Enterprise is able to interface with Conjur as a credential store. As mentioned at the beginning of this guide, variables are created by Conjur policies and not by HPE Morpheus Enterprise. We can reference existing variables and update the secret values stored within.
+
+As an example, there is a variable named `BotApp/secretVar` in the target Conjur appliance. When configuring the Trust integration (in the prior section), the `BotApp/` mount point was referenced (see the screenshot in the last section). When creating stored credential sets in HPE Morpheus Enterprise against this Conjur credential store, reference the rest of the variable path as the NAME value on the credential set. In this case, the credential set will be named `secretVar` to complete the `BotApp/secretVar` path as shown in the screenshot below. Be sure to also select Conjur as the CREDENTIAL STORE value rather than the default “Internal.”
+
+![../../_images/credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4DCB5DDF-130A-4847-912C-CAE31A96EDBE-high.png)
+
+After saving and going back to the Conjur appliance, the value stored at the referenced variable has been updated. This credential set is also available for use anywhere HPE Morpheus Enterprise allows users to utilize them, such as when integrating new Clouds, authenticating REST calls to populate Option Lists, and many other places.
+
+## Conjur and Cypher
+
+In addition to stored credential sets, the CyberArk Conjur plugin also enables integration with HPE Morpheus Enterprise Cypher. Just as calls can be made to internally-stored secret values with Cypher, Conjur variable endpoints may be referenced to onboard secret strings into automation Tasks.
+
+In the screenshot below, see a simple shell script Task which echoes out a secret value stored in Conjur. As you can see, the `conjur/` mount point is referenced along with the rest of the path to the variable which should be accessed. After executing the Task, we can check the execution history and see that the Conjur-stored value is indeed echoed back out.
+
+![../../_images/cypherTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DE2D6E0C-3988-42C1-8C27-2F31438CDED9-high.png)
+
+If desired, the value stored in Conjur could also be updated through the HPE Morpheus Enterprise Cypher UI. Navigate to Tools > Cypher and click + ADD. Note the `conjur` mount point is included in the example list of available mount points shown in the modal. By creating a new Cypher entry at the `conjur` mount point which references an existing Conjur variable path, the value in Conjur can be overwritten. If you’ve configured the plugin to clear secrets on deletion, you can also update the stored value with an empty string when you delete the Cypher object in HPE Morpheus Enterprise. For our example case, we could update the value in Conjur by creating a Cypher entry at the mount point `conjur/BotApp/secretVar`.
+
+![../../_images/cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F2FAE481-318A-42D8-A12B-D1904246CF52-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json b/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
new file mode 100644
index 0000000..5368f47
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+  "title": "Utilities",
+  "ordinal": 331,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.html",
+  "topic_cluster": {
+    "clustering_title": "Utilities",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5",
+        "clustering_title": "Utilities"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md b/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
new file mode 100644
index 0000000..cbda40a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0336B7CB-78A8-4980-BF2F-663F5E1B0EF5.md
@@ -0,0 +1,16 @@
+# Utilities
+
+System administrators have access to a utilities panel with the following options:
+
+- **Reindex all searchable data:** Execute
+- **Toggle Maintenance Mode:** Enable
+
+NOTE
+
+Maintenance mode cleanly places HPE Morpheus Enterprise into a state where maintenance can be performed on the appliance. This drains any active sessions and queues so an auto-scaling group can scale down. It also drains active sessions across services. Restarting HPE Morpheus Enterprise UI disables maintenance mode.
+
+NOTE
+
+When using HPE Morpheus Enterprise in a Highly Available (HA) environment, it is important to navigate to a node directly and enable maintenance mode, as opposed to using the load balancer virtual IP (VIP). A local host entry to the specific node may be required to ensure the correct node enters mainteance mode. In fact, it is recommended to use the [analogous API endpoint](https://apidocs.morpheusdata.com/reference/setappliancesettingsmaintenancemode) to toggle a specific node into maintenance mode to avoid redirects back to the VIP address.
+
+A HPE Morpheus Enterprise node in maintenance mode can still be accessible through the load balancer VIP/target group and can queue requests but will not process anything in queue, while in maintenance mode. A node can be removed/paused from the load balancer VIP or have VIP health checks implemented, if the node UI/API will become inaccessible due to maintenance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json b/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
new file mode 100644
index 0000000..a977180
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+  "title": "Storage",
+  "ordinal": 229,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-034C870E-F6DE-4D0B-950B-23A627D33C65",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md b/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
new file mode 100644
index 0000000..67d4a20
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.md
@@ -0,0 +1,14 @@
+# Storage
+
+NOTE
+
+In v3.5.2 STORAGE PROVIDERS has been split out into BUCKETS and FILE SHARES sections.
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html)**
+- **[Storage Buckets](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html)**
+- **[File Shares](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html)**
+- **[Volumes](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html)**
+- **[Data Stores](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html)**
+- **[Servers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
new file mode 100644
index 0000000..60895f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+  "title": "ARM Blueprints",
+  "ordinal": 132,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html",
+  "topic_cluster": {
+    "clustering_title": "ARM Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4",
+        "clustering_title": "ARM Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
new file mode 100644
index 0000000..53baef2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.md
@@ -0,0 +1,41 @@
+# ARM Blueprints
+
+ARM Blueprints provide a simple and repeatable way of deploying infrastructure-as-code to Azure Clouds. Objects and properties are defined in a JSON file and are provisionable on-demand in |ProApp|
+
+To create a new ARM Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select ARM. NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The ARM template itself is defined in the ARM Configuration section. Using the Config Type dropdown menu, we can opt to write or paste JSON configuration directly into this modal, or we can choose to bring in a JSON which we’re keeping under version control in a Git repository.
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+If writing or pasting your configuration JSON directly into the modal, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** ARM Template JSON (.json)
+- **CONFIG:** Your JSON configuration template
+
+If bringing in a template from a Git repository, fill out the following fields:
+
+- **OS TYPE:** Identify the resources to be created as Linux or Windows
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new ARM Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json b/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
new file mode 100644
index 0000000..8a8dda5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+  "title": "File Templates",
+  "ordinal": 160,
+  "parent_title": "Templates",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html",
+  "topic_cluster": {
+    "clustering_title": "File Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D",
+        "clustering_title": "File Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md b/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
new file mode 100644
index 0000000..d10d769
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.md
@@ -0,0 +1,60 @@
+# File Templates
+
+File Templates are for generating config files, such as my.cnf, opensearch.yml, morpheus.rb, or any text file. With full config map variable support, Template Files are dynamically generated during a Workflow phase or ad hoc via Instance actions.
+
+File Templates can also be exposed on Instances in the Settings Tab. Ensure the Instance Type supports settings, and Category is defined in Advance Options on the Library Template config.
+
+NOTE
+
+HPE Morpheus Enterprise variables are supported in Library Templates using `<%= variable.var %>` format
+
+Examples:
+
+HA Proxy Config (haproxy.cfg)
+
+- FILE NAME: haproxy.cfg
+- FILE PATH: /config/haproxy.cfg
+- PHASE: Pre Provision
+- TEMPLATE:
+- SETTING NAME: haproxyConfig
+- SETTING CATEGORY: haproxy
+
+```
+```
+#!/bin/bash  
+global  
+ maxconn 256  
+ log /dev/log local0 warning  
+ log-tag <%=logTag%>  
+defaults  
+ mode http  
+ timeout connect 5000ms  
+ timeout client 50000ms  
+ timeout server 50000ms  
+ log global  
+frontend http-in  
+ bind *:<%=container.externalPort%>  
+ default_backend servers  
+backend servers  
+ # server server1 127.0.0.1:80 maxconn 32
+```
+```
+
+mysql config (mysqld.cnf)
+
+- FILE NAME: mysqld.cnf
+- FILE PATH: /config/mysqld.cnf
+- PHASE: Pre Provision
+
+```
+```
+#!/bin/bash  
+[mysqld]  
+pid-file= /var/run/mysqld/mysqld.pid  
+socket= /var/run/mysqld/mysqld.sock  
+datadir= /var/lib/mysql  
+# Disabling symbolic-links is recommended to prevent assorted security risks  
+symbolic-links=0  
+explicit_defaults_for_timestamp = 1
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json b/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
new file mode 100644
index 0000000..67b4751
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+  "title": "DNS",
+  "ordinal": 483,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html",
+  "topic_cluster": {
+    "clustering_title": "DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E",
+        "clustering_title": "DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md b/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
new file mode 100644
index 0000000..e8dc256
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.md
@@ -0,0 +1,7 @@
+# DNS
+
+**Subtopics**  
+
+- **[AWS Route53](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html)**
+- **[Microsoft DNS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html)**
+- **[PowerDNS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json b/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
new file mode 100644
index 0000000..dafd911
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+  "title": "Policy Types",
+  "ordinal": 319,
+  "parent_title": "Policies",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0441F3DD-FF73-49C0-8900-718B95266989",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md b/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
new file mode 100644
index 0000000..fc7ce11
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0441F3DD-FF73-49C0-8900-718B95266989.md
@@ -0,0 +1,262 @@
+# Policy Types
+
+## Cypher Policies
+
+HPE Morpheus Enterprise allows administrators to set robust Cypher policies, which determine global, role, and/or specific user access to configured Cypher secret mount points. A number of considerations should be made when deploying Cypher Access policies, including how user role permissions will interact with the policy and how conflicts between overlapping policies are resolved.
+
+### Role Permissions
+
+User Role permissions (Administration > Roles) greatly affect Cypher access. Cypher access Role permissions are set from the Features tab of the selected Role under “Tools: Cypher”. The Role permission should be set based on the highest level of access to any one individual Cypher entry needed for the specific Role. For example, if the Role needs no access to any Cypher entries, set the feature permission to “None” and hide the Cypher UI from the Role completely. Alternatively, if the Role needs to use and decrypt even one Cypher entry, set the feature permission to “Full Decrypt”. The complete set of available permissions are below:
+
+- **NONE:** Cypher UI hidden
+- **READ:** Cypher UI present, entries can be listed
+- **USER:** Cypher UI present, user sees and can use their own entries, user can create new entries
+- **FULL:** Cypher UI present, user sees and can use all entries, user can create new entries, user cannot decrypt any entries
+- **FULL DECRYPT:** Full access to Cypher features including the ability to decrypt secrets
+
+### Cypher Access Policies
+
+Like other Policy types, Cypher Access Policies are created in Administration > Policies. Click + ADD POLICY to create new. Set the type to “Cypher Access” and the relevant configuration options will be displayed. In addition to the type, enter a name for the Policy in the top section.
+
+![../../_images/polname.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F8F43DED-7C86-4242-8B6E-37376AC02AEE-high.png)
+
+In the next section, enter the key path to which the Policy will apply. In addition to static entries that point to one specific Cypher entry, this field supports pattern matching with regex. For example, enter “.\*” to refer to all Cypher entries or “secret/.\*” to refer to all entries under the secret mount point.
+
+In addition to the path, set the privileges users in the Policy scope should have on the indicated path.
+
+- **LIST:** See the entries on the indicated path listed in the Cypher UI
+- **READ:** Decrypt the entries on the indicated path
+- **WRITE:** Add new entries on the indicated path
+- **UPDATE:** Edit Cypher entries on the indicated path
+- **DELETE:** Delete entries on the indicated path
+
+![../../_images/polconfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3073851F-5D93-4F03-94A1-C77B7D140E46-high.png)
+
+Finally, set the scope for the Policy. Cypher Access Policies support Global, Role, and User scope. For example, you may want to block off sets of Cypher entries for various departments within your organization. If you have existing Roles in HPE Morpheus Enterprise for each department, you can set up Role-scoped Policies to ensure they can only list, use, and add Cypher entries which are relevant to their own department.
+
+![../../_images/polfilter.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-63A43C98-F636-420D-828D-19BF24B01237-high.png)
+
+IMPORTANT
+
+When Cypher Access Policies conflict, the Policy with the longest path string length (typically the most specific) takes precedence. For example, a Policy giving LIST and READ access to “secret/aws/.\*” would be superseded by a Policy giving NO access to “secret/aws/my-secret-key”. In such a case, the user would see everything at the “secret/aws/.\*” path except the one indicated in the more specific Policy. When Policies targeting the same path differ only in their scope, the following scope precedence is applied: Role > User > Global. For example, if a Role-scoped Policy targeting “.\*” grants LIST and READ while a User-scoped Policy targeting the same path grants LIST, the user would be granted the rights in the Role-scoped Policy.
+
+### Cloud Profiles
+
+Terraform Cloud Profiles are created on each Cloud detail page (Infrastructure > Clouds > Selected Cloud > ProfilesTab), encrypted in Cypher, and create a Cypher entry that is visible both on the Profile tab of the Cloud detail page and in Cypher. When added to a Cloud they create a Cypher entry at path tfvars/profile/cloud/$cloudCode/variables. If a Cloud profile Cypher entry is restricted by a Cypher Access policy, it will be (or will not be) listable/readable/deletable as dictated by the Policy but still will be viewable from the Cloud detail page if the user has sufficient permissions. Restricting or granting access to Cloud profiles via Policy does not affect access on the Cloud. Other Role permissions, such as “Admin: Profiles”, “Infrastructure: Clouds”, and Cloud/Group access must be used to restrict access via Cloud detail pages.
+
+### Example Policy
+
+In my example organization, I have one department that needs access to AWS-related secrets and another department that needs access to Azure-related secrets. There are many other secrets stored in my appliance but I don’t want either of these departments to access any of those.
+
+![../../_images/cypherlist.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E85ADD10-D850-4AC0-B155-027367EC2C47-high.png)
+
+For the first department, I’ve set up a Policy that allows them to list and read (including use and decryption rights) AWS secrets. A second Policy specifically excludes them from seeing one specific entry. The Policy with the more specific path will supersede the more generic Policy that includes a wildcard.
+
+![../../_images/pollist.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1FF1D390-EB0B-4C24-9289-4AF2717D8895-high.png)
+
+By impersonating the user, we see they indeed have access to just the two desired Cypher entries.
+
+![../../_images/user1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3BD14A79-055F-4C2E-AF21-EDE494DAB877-high.png)
+
+For the second department, I have set up a Policy that allows them to list and read (including use and decryption rights) Azure secrets.
+
+![../../_images/cypherlist2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6FD23103-1276-4EBB-AC2A-15440A479D4D-high.png)
+
+By impersonating the user once again, we see they indeed have access only to Azure entries.
+
+![../../_images/user2cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E2E311FD-BE92-4152-A79B-AB71DBA890B9-high.png)
+
+## Expiration Policies
+
+Expiration policies set an expiration timeframe for any instance provisioned into the cloud, role, group or by the user the policy is added to. When an instance expires, it is terminated and deleted.
+
+Configuration options for expiration policies:
+
+Expiration Type
+:   - User Configurable- expiration timeframe is editable during provisioning
+    - Fixed Expiration- user cannot change expiration timeframe
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being removed.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the expiration date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to expire.
+
+Notification Message
+:   Customizable message for notification emails. The default message is `Instance ${instance?.name} is set to expire on ${instance?.expireDate}`
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+Instances with expirations show the time until expiration in the instance detail pane. Instances with active expiration policies can be extended by selecting the EXTEND NOW button in the instance detail pane. The extension length is set in the policy by the RENEWAL DAYS field.
+
+Expirations can also be added to any instance during provisioning by entering the number of days in the EXPIRATION DAYS field in the Lifecycle section of the automation section of the provisioning wizard. Expiration can be added to any instance even if no policies have been created.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Instance and Host Names
+
+Naming Policies will populate a fixed or editable name for instances, hosts and hostnames. The Name Pattern field uses ${variable} string interpolation.
+
+NAMING TYPE
+:   User Configurable
+    :   Naming pattern will pre-populate during provisioning but can be edited by the user.
+
+    Fixed Name
+    :   Naming pattern will pre-populate during provisioning and cannot be changed.
+
+NAME PATTERN
+:   The Name Pattern field uses Static text and/or `${variable}` string interpolation, such as `morpheus${cloudCode}${type}${sequence+3000}`
+
+    An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+    Commonly used variables for naming patterns include:
+
+    ```
+    ```
+    ${groupName}  
+    ${groupCode}  
+    ${cloudName}  
+    ${cloudCode}  
+    ${type}  
+    ${accountId}  
+    ${account}  
+    ${accountType}  
+    ${platform}  
+    ${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+    ${userId}  
+    ${username}  
+    ${userInitials}  
+    ${provisionType}  
+    ${instance.instanceContext} # Environment Code  
+    ${sequence} # results in 1  
+    ${sequence+100} # results in 101  
+    ${sequence.toString().padLeft(5,'0')} #results in 00001
+    ```
+    ```
+
+    Cloud codes and Group codes are fields found in their respective configuration panes.
+
+AUTO RESOLVE CONFLICTS
+:   HPE Morpheus Enterprise will automatically resolve naming conflicts by appending a sequential -number to the name when enabled.
+
+## Shutdown Policies
+
+Shutdown policies dictate the number of days an instance is allowed to run before it is shut down. Shutdown is consistent across cloud types i.e.: in VMware, a VM is powered off. In AWS, an instance is stopped. Etc.
+
+Configuration options for shutdown policies:
+
+Shutdown Type
+:   User Configurable
+    :   Shutdown timeframe is editable during provisioning.
+
+    Fixed Expiration
+    :   User cannot change shutdown timeframe during provisioning.
+
+Expiration Days
+:   Configures the number of days the instance is allowed to exist before being shut down.
+
+Renewal Days
+:   If the instance is renewed, this is the number of days by which the shutdown date is increased.
+
+Notification Days
+:   This allows an email notice to be sent out X days before the instance is set to shut down.
+
+Notification Message
+:   Customizable message for notification email.
+
+Auto Approve Extensions
+:   Enable this to auto-approve extension requests, bypassing approval workflows.
+
+NOTE
+
+Expiration and Shutdown Policies will be enforced on Instances created when converting a discovered host to managed.
+
+## Provision Approval
+
+HPE Morpheus Enterprise Provision Approvals enable an approval workflow via internal HPE Morpheus Enterprise approval or via ServiceNow workflow. If a ServiceNow integration is present, the ServiceNow option is enabled. The Approval workflow to be selected is dynamically created by querying the ServiceNow Workflow table in the integrated ServiceNow instance.
+
+This ServiceNow approval integration enables users to use the HPE Morpheus Enterprise Self-Service provisioning portal to provision new instances and still respect the required ServiceNow business approval workflow.
+
+## Power Schedules
+
+Power Schedules set daily times to shutdown and startup instances. Power schedule can be created and managed in Library > Automation > Power Scheduling
+
+NOTE
+
+Power Schedule Policies will apply to Instances created in a Group or Cloud after the Policy is enabled, and will not apply to pre-existing Instances.
+
+Configuration options for Power Schedule Policies:
+
+DESCRIPTION
+:   Add details about your Policy for reference in the Policies tab.
+
+Enabled
+:   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Groups Instances until re-enabled.
+
+ENFORCEMENT TYPE
+:   - User Configurable: Power Schedule choice is editable by User during provisioning.
+    - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+POWER SCHEDULE
+:   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## Max Resources
+
+Max Resource policies allow setting quotas for Clouds, Groups, Roles or Users for maximum amount of Memory, Storage, Cores, Hosts, VM’s, or Containers that can be created in the Cloud, Group, Role or by the User the Policy is assigned to.
+
+Configuration options for Max Resources Policies:
+
+Max Containers
+:   Sets the maximum combined total of Containers in Instances per Policy Scope.
+
+Max Cores
+:   Sets the maximum combined total of Cores in Instances per Policy Scope.
+
+Max Hosts
+:   Sets the maximum total of Hosts per Policy Scope.
+
+Max Memory
+:   Sets the maximum combined total of RAM (capacity) for Instances per Policy Scope.
+
+Max Storage
+:   Sets the maximum combined total of Storage (capacity) for Instances per Policy Scope.
+
+Max VMs
+:   Sets the maximum total of managed Virtual Machines per Policy Scope.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+
+## User Creation
+
+The User Creation policy controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+Configuration options for User Creation Policies:
+
+TYPE
+:   User Creation
+
+DESCRIPTION
+:   Description to identify the policy config
+
+Enabled
+:   Policies enforcement can be disabled or enabled at any time.
+
+ENFORCEMENT TYPE
+:   - User Configurable: User Creation choice is editable by User during provisioning.
+    - Fixed: User cannot change User Creation setting during provisioning.
+
+CREATE USER
+:   Check to allow or force user creation. Uncheck to disable by default or force no user creation.
+
+TENANTS
+:   Leave blank for the Policy to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json b/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
new file mode 100644
index 0000000..f118c5f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+  "title": "NSX",
+  "ordinal": 509,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html",
+  "topic_cluster": {
+    "clustering_title": "NSX",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D",
+        "clustering_title": "NSX"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md b/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
new file mode 100644
index 0000000..c105e3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.md
@@ -0,0 +1,115 @@
+# NSX
+
+## Overview
+
+VMware NSX offers network virtualization allowing for creation and management of software-based virtual networks in an efficient and programmatic way. HPE Morpheus Enterprise offers a full-featured integration with NSX, including Project scoping for NSX 4+ integrations. HPE Morpheus Enterprise will ingest and expose its networking abstractions in the following sections of the HPE Morpheus Enterprise NSX integration:
+
+- SUMMARY
+- TRANSPORT ZONES
+- DHCP
+- SEGMENTS
+- FIREWALL
+- TIER-1 GATEWAYS
+- TIER-0 GATEWAYS
+- EDGE CLUSTERS
+- GROUPS
+
+This guide goes through the process of integrating an existing NSX installation with HPE Morpheus Enterprise and working with the associated objects synced in with the integration. For more on installing NSX and an overview of its concepts, please review the [NSX overview documentation](https://docs.vmware.com/en/VMware-NSX-Data-Center/2.0/com.vmware.nsxt.install.doc/GUID-10B1A61D-4DF2-481E-A93E-C694726393F9.html) provided by VMware.
+
+## NSX Tagging
+
+An NSX integration can apply Instance and VM tags to VMs in NSX, if desired. To apply this, mark the box for “APPLY VM TAGS” when adding or editing an NSX integration.
+
+![../../_images/applyTags.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0DEECD00-D8E9-4B5D-98C9-A07FB86C1CDE-high.png)
+
+Once this configuration is set on the integration, any tags that are applied to applicable Instances through the provisioning wizard at provision time will be applied to those VMs in NSX. In the example below, I’ve set one tag on the new Instance in the provisioning wizard:
+
+![../../_images/setTag.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-806F0064-33EE-43D9-83EB-B8A9BBF0BE93-high.png)
+
+Once provisioning is complete, the tags are confirmed to be visible in the NSX console as well:
+
+![../../_images/showNsx.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-64F1C009-4585-4F84-BBFD-FFD85FEF51D7-high.png)
+
+## NSX Projects
+
+Projects in NSX are analogous to tenants in other products and are a part of NSX version 4+. Projects allow for the isolation of networking abstractions into individual tenants within a single NSX appliance. If your organization is already utilizing NSX Projects, you are probably very familiar with their concept and execution but others can find high-level details about them [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+HPE Morpheus Enterprise supports a full-featured integration with NSX, including the ability to scope the HPE Morpheus Enterprise integration to a specific Project the service user can access. Using Project-scoped integrations allows multiple NSX integrations to be made to the same NSX appliance and ensures HPE Morpheus Enterprise users are siloed to only the NSX Projects they can access.
+
+## Add NSX Integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select Select + ADD > VMWare NSX
+3. Enter the following: 
+
+   - NAME: Name for the NSX Integration in HPE Morpheus Enterprise
+   - VISIBILITY: Public (available to all HPE Morpheus Enterprise Tenants) or Private (available only to the current Tenant). This option is shown only in the HPE Morpheus Enterprise Master Tenant
+   - API HOST: URL of the NSX Manager (ex. <https://x.x.x.x/api>)
+   - CREDENTIALS: A pre-stored credential set can be used to create this integration. If “Local Credentials” is selected, USERNAME and PASSWORD fields are presented and must be filled
+   - USERNAME: NSX service account username. Prior to NSX version 4, this is likely an admin account with access to all networking constructs. In NSX version 4 and higher, this could be an admin for access to default space constructs or it could be a Project-specific user depending on the access needs of the integration being created
+   - PASSWORD: The password for the NSX service account entered above
+   - PROJECT: As soon as an API HOST and credentials are provided, HPE Morpheus Enterprise will attempt to authenticate with the NSX appliance. When authentication is successful and a NSX 4+ appliance is detected, a PROJECT field will appear and the dropdown will be pre-populated with Projects accessible to the service user account
+   - VMWARE CLOUD: Select the existing VMware cloud associated with this NSX integration
+4. Select ADD NETWORK INTEGRATION
+
+### Results
+
+Once the NSX Integration is added HPE Morpheus Enterprise will sync in existing Transport Zones, DHCP servers and relays, Segments, firewall groups and rules, Gateways, Edge Clusters, and Groups. We can manage these synced items from within HPE Morpheus Enterprise UI, including the ability to create, edit, and delete them.
+
+NOTE
+
+The available tabs on the integration detail page will be dependent on the Project selected when the integration was created. Just like in NSX, the default view (and thus integrations scoped to the default Project) will have access to all constructs whereas individual Projects will not. Integrations scoped to individual Projects can view the DHCP, Segments, Firewall, Tier-1 Gateways, and Groups tabs but not the other tabs described here. These limitations are identical to those in the NSX console UI. More information on NSX Projects is available [here](https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-52180BC5-A1AB-4BC2-B1CE-666292505317.html).
+
+## Summary View
+
+The SUMMARY tab contains the default view when accessing an NSX integration. From the summary view we can see the status of the NSX server, and details about interfaces and group status.
+
+## Transport Zones
+
+Access Transport Zones by selecting the Transport Zones tab. The default view of the Transport Zones tab lists Transport zones and presents some detail about them such as name, traffic type, status, and more. The integration allows for creation of new Transport Zones, editing and deleting.
+
+![../../_images/1tz.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E5021E3F-6EC5-433B-9471-40D7563D0107-high.png)
+
+## DHCP
+
+DHCP servers and relays are displayed on the DHCP tab. View information such as names and server addresses. The integration allows for creation of new servers and relays, editing and deleting.
+
+![../../_images/1dhcp.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B3C32D7F-69D9-462D-9766-55EE13CAD643-high.png)
+
+## Segments
+
+Access Segments by from the Segments tab. The summary view includes high-level information such as status, name, network name and CIDR. The integration allows for creating, editing and deleting NSX Segments
+
+![../../_images/1segments.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D72DEE9B-2CF2-40E3-9256-5C4FE66E2794-high.png)
+
+## Firewall
+
+Firewall Groups and Rules are accessible from the Firewall tab. From the summary view, Groups can be expanded to view Rules within. From the ACTIONS menu, create new Groups by selecting “Create Group”. When a Group has been expanded, the “Create Rule” selection within the ACTIONS menu will also be accessible and a new rule can be created within the selcted Group. The integration allows for viewing, creating, editing and deleting Firewall Groups and Rules.
+
+![../../_images/1firewall.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-04A798AB-AD05-4547-97F6-515C09BE616A-high.png)
+
+## Tier-0 Gateways
+
+Access Tier-0 Gateways from the Tier-0 Gateways tab. The integration allows creating, editing and deleting Tier-0 Gateways.
+
+![../../_images/1t0.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E58BC69D-9E6A-44E7-8181-4B7597235E5F-high.png)
+
+## Tier-1 Gateways
+
+Access Tier-1 Gateways from the Tier-1 Gateways tab. The integration allows creating, editing and deleting Tier-1 Gateways.
+
+![../../_images/1t1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ECFD21E1-3744-46E8-9A14-3A07AE2EA2EB-high.png)
+
+## Edge Clusters
+
+View Edge Clusters from the Edge Clusters tab. The default view lists each Edge Cluster with name, member type, cluster profile, and more. The integration allows viewing and limited editing of Edge Clusters.
+
+![../../_images/1edgeclusters.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-42A4E243-3B5E-45C6-AC05-01E63382D520-high.png)
+
+## Groups
+
+NSX Groups are viewed from the Groups tab. The default view lists each Group alone with member details. The HPE Morpheus Enterprise NSX integration allows for creating, editing and deleting Groups.
+
+![../../_images/1groups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C6C0EDD3-C289-4A0A-B449-038EF1E08D17-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json b/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
new file mode 100644
index 0000000..4b50964
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+  "title": "Mac Stadium",
+  "ordinal": 462,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-06D232B4-F473-44C5-AD24-AECD128273E5.html",
+  "topic_cluster": {
+    "clustering_title": "Mac Stadium",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06D232B4-F473-44C5-AD24-AECD128273E5",
+        "clustering_title": "Mac Stadium"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md b/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
new file mode 100644
index 0000000..db5dd45
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06D232B4-F473-44C5-AD24-AECD128273E5.md
@@ -0,0 +1,136 @@
+# Mac Stadium
+
+## Overview
+
+MacStadium is a provider of enterprise-class hosting solutions for Apple Mac infrastructure. It can be used to deploy a hosted private cloud for large-scale CI/CD or even a single Mac mini to test an iOS app. It allows virtualized Mac build machines
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json b/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
new file mode 100644
index 0000000..90c71c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+  "title": "To create a Tenant Role:",
+  "ordinal": 306,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html",
+  "topic_cluster": {
+    "clustering_title": "To create a Tenant Role:",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC",
+        "clustering_title": "To create a Tenant Role:"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md b/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
new file mode 100644
index 0000000..93c7423
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.md
@@ -0,0 +1,14 @@
+# To create a Tenant Role:
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “Tenant Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select SAVE CHANGES
+
+## Results
+
+After saving, the Role will be created and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json b/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
new file mode 100644
index 0000000..1bc8e57
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+  "title": "Workloads: Blueprint Usage",
+  "ordinal": 69,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Blueprint Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B",
+        "clustering_title": "Workloads: Blueprint Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md b/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
new file mode 100644
index 0000000..b79ecb0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.md
@@ -0,0 +1,32 @@
+# Workloads: Blueprint Usage
+
+![../_images/11blueprintusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C67DA833-C730-4887-9672-7E63FABC0841-high.png)
+
+The Blueprint Usage dashboard lists all provisioned Apps that meet filters set on the dashboard. Once the desired group of Apps is filtered into the dashboard, administrators will see the total provisioned from each Blueprint, total number of Instances created from the Apps, and costing details.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **TYPES:** The total number of App types represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **MONTH TO DATE:** The total month-to-date spend for all Apps shown in the dashboard
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Blueprint Usage List
+
+All Blueprints which have a currently-existing App provisioned from them and selected in the dashboard filters are listed here. The name and type of the Blueprint is listed along with the total number of Instances across all provisionings, total Groups, total Clouds, and the total count of all Apps from that Blueprint.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json b/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
new file mode 100644
index 0000000..2e6b0c1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+  "title": "Docker Clusters",
+  "ordinal": 199,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2",
+        "clustering_title": "Docker Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md b/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
new file mode 100644
index 0000000..e2782a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.md
@@ -0,0 +1,71 @@
+# Docker Clusters
+
+## About this task
+
+Provisions a new Docker Cluster managed by Morpheus.
+
+To create a new Docker Cluster:
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Docker Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Docker Cluster
+
+   RESOURCE NAME
+   :   Name for Docker Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+5. Select NEXT
+6. Populate the following (options depend on Cloud Selection and will vary): 
+
+   LAYOUT
+   :   Select from available layouts.
+
+   PLAN
+   :   Select plan for Docker Host
+
+   VOLUMES
+   :   Configure volumes for Docker Host
+
+   NETWORKS
+   :   Select the network for Docker Master & Worker VM’s
+
+   NUMBER OF HOSTS
+   :   Specify the number of hosts to be created
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+7. Select NEXT
+8. Select optional Workflow to execute
+9. Select NEXT
+10. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json b/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
new file mode 100644
index 0000000..7da478f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+  "title": "Volume Management",
+  "ordinal": 442,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05",
+        "clustering_title": "Volume Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md b/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
new file mode 100644
index 0000000..b038916
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.md
@@ -0,0 +1,10 @@
+# Volume Management
+
+Volume life cycle management can be performed under the Infrastructure > Storage > Volumes tab. It allows the user to perform create/resize/delete operations.
+
+**Subtopics**  
+
+- **[Adding Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html)**
+- **[Deleting Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html)**
+- **[Resizing Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html)**
+- **[Reconfiguring Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json b/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
new file mode 100644
index 0000000..7c128e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+  "title": "Adding OpenShift Clusters",
+  "ordinal": 207,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html",
+  "topic_cluster": {
+    "clustering_title": "Adding OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-092B4E74-3662-4E21-9DA0-67958362DBE4",
+        "clustering_title": "Adding OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md b/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
new file mode 100644
index 0000000..05dd0ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.md
@@ -0,0 +1,24 @@
+# Adding OpenShift Clusters
+
+NOTE
+
+Adding an OpenShift cluster requires a pre-existing Group and Private Cloud-type Cloud. See Groups and Clouds documentation elsewhere in this user manual for more details on those constructs.
+
+To onboard an OpenShift cluster, begin by collecting an API token and API URL from OpenShift. Bear in mind the integration user with HPE Morpheus Enterprise must be a full administrator user.
+
+1. Log into the OpenShift console
+2. In the far top-right of the application window, click on the name of the logged in user to expand a small dropdown menu
+3. Click "Copy login command"
+4. Click "Display Token"
+5. On the resulting screen, both the API URL and the API token can be copied. You will need to enter these values directly into the "Add Cluster" modal within HPE Morpheus Enterprise in the next step
+
+With the authentication details available, head back to HPE Morpheus Enterprise to add a new OpenShift cluster:
+
+1. Navigate to Infrastructure > Clusters
+2. Click + Add Cluster
+3. Select "RED HAT OPENSHIFT CLUSTER" and click Next
+4. On the Group tab, select the HPE Morpheus Enterprise Group to associate with the cluster and click Next
+5. On the Name tab, you must at least configure a "Cluster Name" attribute and select a Cloud. The "Cluster Name" is a friendly name to identify the OpenShift cluster in HPE Morpheus Enterprise. The Cloud configuration requires you to select a pre-existing Private Cloud-type Cloud. There are optional configurations here as well, such as applying Labels or adding a description
+6. On the Configure tab, select the Layout that corresponds closest to the version of OpenShift running on the cluster. Integration with HPE Morpheus Enterprise requires OpenShift version 4.x at minimum. On this tab, you'll also enter the API URL and service token collected earlier. If "Inventory Existing Instances" is checked, HPE Morpheus Enterprise with automatically onboard any virtualized workloads which are currently running on the cluster and any that are provisioned directly from the OpenShift console in the future. Click Next
+7. On the Review tab, click Complete
+8. Within a short time, the new OpenShift cluster will appear on the clusters list page alongside any other cluster that may currently be running
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json b/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
new file mode 100644
index 0000000..bebcb48
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+  "title": "Common Ports & Requirements",
+  "ordinal": 350,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md b/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
new file mode 100644
index 0000000..512d7ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | DNS Resolution from node to appliance url Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Admin – >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration – >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node | user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node | user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json b/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
new file mode 100644
index 0000000..39cb7f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+  "title": "Plans",
+  "ordinal": 287,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md b/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
new file mode 100644
index 0000000..53f180b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.md
@@ -0,0 +1,8 @@
+# Plans
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html)**
+- **[Price Sets](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html)**
+- **[Prices](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json b/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
new file mode 100644
index 0000000..6598a7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+  "title": "Environments",
+  "ordinal": 328,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.html",
+  "topic_cluster": {
+    "clustering_title": "Environments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5",
+        "clustering_title": "Environments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md b/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
new file mode 100644
index 0000000..72b30f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0A516D6F-CF1A-4470-8ABB-A7432A1E08D5.md
@@ -0,0 +1,34 @@
+# Environments
+
+## Overview
+
+The Environments section is where you create and manage your environment labels, which are available in the Environment dropdown during Instance or App provisioning. An Instance’s environment label can be changed by editing the Instance.
+
+### Creating Environments
+
+#### Procedure
+
+1. Select + Create Environment
+2. Populate the following for the New Environment: 
+
+   Name
+   :   The friendly name for the environment in HPE Morpheus Enterprise
+
+   Code
+   :   Shortcode used for API and CLI
+
+   Description
+   :   Environment description displayed on the Environments list page
+
+   Display Order
+   :   The order in which environments are presented when provisioning, a value of “0” will position the environment at the top of the list
+
+   Visibility
+   :   - Private: Available only in the Tenant the environment is created in
+       - Public: Available for all Tenants. Public is only applicable for environments created in the the Master Tenant.
+
+#### Results
+
+NOTE
+
+User-created environments can be edited, hidden, or removed from the Actions menu on the environments list page. HPE Morpheus Enterprise-default environments can only be hidden from users during provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json b/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
new file mode 100644
index 0000000..25faeeb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+  "title": "Wiki",
+  "ordinal": 72,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html",
+  "topic_cluster": {
+    "clustering_title": "Wiki",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3",
+        "clustering_title": "Wiki"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md b/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
new file mode 100644
index 0000000..e6d3ced
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.md
@@ -0,0 +1,50 @@
+# Wiki
+
+The Morpheus Wiki is a tenant-wide, RBAC-controlled, auditable Wiki that allows easy UI, API and CLI access to information, notes, configurations or any other data needed to be referenced or shared with others. Wiki pages can be created directly from the Wiki tab of the detail page for various resource types, including Clouds, Groups, Servers, Instances, Clusters, and Self-Service Persona Catalog Items. Wiki pages created this way are automatically categorized under the appropriate resource type. Additional Wiki pages and custom categories can be created when viewing the whole Wiki at Operations  >  Wiki. Here you will also see the complete Wiki, including pages created on various object detail pages which are categorized appropriately.
+
+![wiki](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F0F0DA3A-4058-45D6-AECA-8A5BEF62FDBA-high.png)
+
+## Highlights
+
+- Main Wiki section is at Operations > Wiki
+- Wiki tabs are on Clouds, Groups, Instances, Hosts, VMs, Bare Metal, and Clusters detail pages
+- Additional Wiki Pages and Categories can be created from Operations  >  Wiki
+- When a Wiki tab is populated, a Page is automatically added and accessible at Operations  >  Wiki
+- One Wiki is created per Tenant. There is no multi-tenant access to Wikis
+- The Wiki is accessible from the UI, CLI and API.
+- Wiki access is RBAC-controlled via the Operations: Wiki permission in User and Tenant Roles (None, Read and Full)
+- Page updates are stamped with the “Last Updated By” user and the time the edit was made
+- Wiki pages can be searched from `/operations/wiki` or navigated from `/operations/wiki-page/page-index`
+- All wiki pages are encrypted using AES 256-bit encryption
+- Wiki pages use Flexmark for Markdown. Annotate your Wiki pages with headers, text styling, code blocks, hyperlinks, and more as needed
+- Create a new page with title “Home” to replace the default Wiki landing page that ships with HPE Morpheus Enterprise
+
+NOTE
+
+The Wiki replaces Notes. Notes are automatically migrated to corresponding Wiki pages when upgrading HPE Morpheus Enterprise to 4.0.0+.
+
+## Creating Wikis
+
+The Wiki service ties into assets throughout the environment. Create pages for Instances, hosts, groups, Clouds, and even clusters directly on their detail pages (see the Wiki tab). Users may also just create general notes pages in the centralized Wiki section (Operations > Wiki) in Markdown format.
+
+Creating your first page is as simple as clicking the Create Page button from the Wiki home page (Operations > Wiki).
+
+![create wiki](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4029426C-1AA2-4873-AE1C-CB4677EFB0F7-high.png)
+
+Write down some content, give the page a title, and click SAVE. The Wiki will also keep track of who last edited a page and when. The beauty of this Wiki is that it’s clean and easy to write down notes related to various parts of your application deployment or infrastructure without going to an external tool. Many HPE Morpheus Enterprise constructs, such as Instances, hosts, and more, also have their own Wiki page. Navigate to the detail page for the selected construct, open the Wiki tab, and click EDIT to add content.
+
+IMPORTANT
+
+All wiki pages are encrypted using AES-256 bit encryption. Though we don’t advise storing passwords in a Wiki document (services like Cypher are for that), role-based access control also can properly restrict access to content related to Instances or hosts which the user may not have access to.
+
+## Hosting Images
+
+It’s possible to add images to your Wiki pages and images can be sourced from the Internet, a Cloud storage bucket (like an AWS S3 Bucket), or even from files stored to the HPE Morpheus Enterprise appliance’s local file system. Within your Wiki page markdown, add your image using the following syntax:
+
+```
+```
+![my alt text](https://myimage.com/image.jpg)
+```
+```
+
+The text within the square brackets [] sets the HTML “alt” description for the image and the URL within parentheses () is the “src” URL for the image. The HPE Morpheus Enterprise [Archives](https://docs.morpheusdata.com/en/latest/tools/archives.html) feature is a great resource for hosting images for use in Wiki. Archives can target cloud storage buckets or even file shares on the HPE Morpheus Enterprise appliance local storage. HPE Morpheus Enterprise generates an access URL for each file stored in Archives, simply target this URL in your markdown to show an image stored in HPE Morpheus Enterprise Archives within your Wiki pages.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json b/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
new file mode 100644
index 0000000..c112c41
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+  "title": "Uploading OS Images Using NFS",
+  "ordinal": 411,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using NFS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870",
+        "clustering_title": "Uploading OS Images Using NFS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md b/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
new file mode 100644
index 0000000..240c9c8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using NFS
+
+## About this task
+
+NFS allows OS images to be stored on a shared Linux file server.
+
+## Procedure
+
+1. Configure an NFSv3 file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the NFS share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json b/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
new file mode 100644
index 0000000..97a08b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+  "title": "Import Trusted Certificates",
+  "ordinal": 35,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html",
+  "topic_cluster": {
+    "clustering_title": "Import Trusted Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0BBD18FA-91D0-406A-B004-3F068114DE70",
+        "clustering_title": "Import Trusted Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md b/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
new file mode 100644
index 0000000..87790cb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.md
@@ -0,0 +1,61 @@
+# Import Trusted Certificates
+
+## About this task
+
+IMPORTANT
+
+The following applies to upgrades after modifying the java keystore.
+
+Steps to import trusted certificates to HPE Morpheus Enterprise after an upgrade.
+
+## Procedure
+
+1. Obtain the full SSL certificate chain in PEM format.
+2. Copy them to each appliance and place them in the `/etc/morpheus/ssl/trusted_certs` directory.
+3. Run morpheus-ctl reconfigure on each appliance, note you don’t need to stop Morpheus before you run this.
+4. Run the following command as root: 
+
+   ```
+   ```
+   export PATH=/opt/morpheus/sbin:/opt/morpheus/sbin:/opt/morpheus/embedded/sbin:/opt/morpheus/embedded/bin:$PATH
+   ```
+   ```
+5. Run the following command for each certificate in the chain, adjusting the file and alias name as needed. Answer yes for the root certificate when asked it you want to trust it. 
+
+   ```
+   ```
+   /opt/morpheus/embedded/java/jre/bin/keytool -import -keystore /opt/morpheus/embedded/java/jre/lib/security/cacerts -trustcacerts -file /etc/morpheus/ssl/trusted_certs/root_ca.pem -alias some_alias -storepass changeit
+   ```
+   ```
+6. Verify by running: 
+
+   ```
+   ```
+   openssl s_client -connect host:port -showcerts -tls1_2
+   ```
+   ```
+7. You should get an output similar to: 
+
+   ```
+   ```
+   New, TLSv1/SSLv3, Cipher is ECDHE-RSA-AES256-GCM-SHA384  
+   Server public key is 2048 bit  
+   Secure Renegotiation IS supported  
+   No ALPN negotiated  
+   SSL-Session:  
+   Protocol : TLSv1.2  
+   Cipher  : ECDHE-RSA-AES256-GCM-SHA384  
+   Session-ID: 5D9E820E4FF2A73A9977BA663E6029AA5415FEE85F49D8B1E541F5997C8E1FB2  
+   Session-ID-ctx:  
+   Master-Key: 29EEC2E7750C659AECB9942902D9A87B824E571522812B718420FC08F8D2ACE68CB16EC812A7D90B12A86D1970FFD81C  
+   Key-Arg  : None  
+   PSK identity: None  
+   PSK identity hint: None  
+   SRP username: None  
+   Start Time: 1547219217  
+   Timeout  : 7200 (sec)  
+   Verify return code: 0 (ok) #<----------------
+   ```
+   ```
+8. If the certificates are installed correctly you should see `Verify return code: 0 (ok)`. If they were not installed correctly then you will see a return similar to: `Verify return code: 21 (unable to verify the first certificate)`
+9. Repeat for all App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json b/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
new file mode 100644
index 0000000..966c372
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+  "title": "EfficientIP SOLIDserver",
+  "ordinal": 517,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html",
+  "topic_cluster": {
+    "clustering_title": "EfficientIP SOLIDserver",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB",
+        "clustering_title": "EfficientIP SOLIDserver"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md b/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
new file mode 100644
index 0000000..6976231
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.md
@@ -0,0 +1,113 @@
+# EfficientIP SOLIDserver
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+
+## Required Role Permissions
+
+### Add, edit and remove EfficientIP SOLIDserver integrations
+
+- Infrastructure: Network Integration: Full
+
+### View and edit synced IP pools
+
+- Infrastructure: Network IP Pools: Full
+
+### View networks and add synced IP pools to networks
+
+- Infrastructure: Networks: Full or Group
+
+### View and edit synced DNS zones, including creation of zone records
+
+- Infrastructure: Network Domains: Full
+
+## Adding EfficientIP SOLIDserver Integration
+
+### About this task
+
+The EfficientIP SOLIDserver integration type is a plugin that must be added to HPE Morpheus Enterprise before the option to create one will be available. In the future, users will be able to download this and other plugin types from a centralized marketplace. For now, the plugin jar file can be compiled from a public Github repository or can be requested from your account team. See the [Plugins Section](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) of HPE Morpheus Enterprise documentation for more on the process of uploading the plugin JAR to your appliance.
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations and click + ADD
+2. Under the IPAM section, select EfficientIP SOLIDserver
+3. Configure the following: 
+
+   - NAME: Friendly name for this EfficientIP SOLIDserver integration
+   - ENABLED: When checked, this integration will be accessible in HPE Morpheus Enterprise
+   - API URL: The FQDN for the EfficientIP server, not a specific path
+   - USERNAME: The username for an EfficientIP service account. Bear in mind this account will need API access as well as the rights to work with pools, zones, and records you wish to consume from HPE Morpheus Enterprise
+   - PASSWORD: The password for the above named account
+   - THROTTLE RATE: In larger environments, it may be necessary to introduce a rate limit on calls to the EfficientIP API from HPE Morpheus Enterprise. If the EfficientIP console UI becomes less responsive than it was prior to integration with HPE Morpheus Enterprise, it may be due to a high number of API calls in the background from HPE Morpheus Enterprise. In such a case, start with a 50ms throttle rate and adjust accordingly depending on performance
+   - DISABLE SSL SNI VERIFICATION: If necessary, disable the check for a valid SSL certificate on the EfficientIP server
+   - INVENTORY EXISTING: When checked, used IP space will be continually synced between HPE Morpheus Enterprise and EfficientIP. If left unchecked, only IP space claimed (and freed) from HPE Morpheus Enterprise is shown on the detail page for the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+Once saved, HPE Morpheus Enterprise will begin to onboard data from EfficientIP. EfficientIP networks are viewable in Infrastructure > Network > IP Pools under the IP Pools tab. Depending on EfficientIP configuration, you may see up to two “types” of Network Pools sync from EfficientIP, SOLIDserver Subnet and SOLIDserver Pool. In EfficientIP, “pools” are an optional construct that subdivides subnets. In HPE Morpheus Enterprise, both constructs are synced which gives an additional layer of organization when linking Network Pools with Networks (described in the next section) for organizations that use the pools construct. Within a selected IP Pool, host records will also sync and can be viewed in a grid or list layout. DNS Zones are synced under Infrastructure > Network > Domains. By clicking into the domain, DNS Zone records can be viewed.
+
+![../../_images/pool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8125D46A-139B-415D-A7F1-C47CE46A6FD8-high.png)
+
+## Adding IP Pools to Networks
+
+### About this task
+
+At provision time, HPE Morpheus Enterprise can automatically assign the next available IP address in an EfficientIP pool and create the corresponding DNS records. HPE Morpheus Enterprise can also clean up DNS records and free up IP address space on teardown. In order to enable this functionality, add an EfficientIP IP Pool as the Network Pool for an existing network (or networks).
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select a network to view the network detail page and click EDIT
+3. In the typeahead field for NETWORK POOL, search for and select the EfficientIP pool
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Gateway, DNS and CIDR must be populated for static/pool IP assignment. If desired, select “Allow IP Override” to allow selecting between DHCP, Static entry, and pool selection at provision time. Finally, deselect “DHCP server” if a DHCP server will not be used on the network (only static and/or IP Pool assignment).
+
+## Creating Host Records
+
+### Procedure
+
+1. Select an EfficientIP Network Pool from Infrastructure > Network > IP Pools
+2. Select + ADD
+3. Configure the following:
+
+### Results
+
+- **HOSTNAME:** The hostname for the record
+- **IP ADDRESS:** The IP address for the host record
+- **DOMAIN:** Select an EfficientIP zone
+- **CREATE DNS RECORDS:** If selected, DNS A and PTR records will be created in EfficientIP
+
+1. Click SAVE CHANGES
+
+![../../_images/createhost.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-327856E4-74AE-4477-87F4-DF8DB6390B2F-high.png)
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select an EfficientIP zone from the domains list at Infrastructure > Network > Domains
+2. Click + ADD on the Zone Records tab
+3. Configure the following:
+
+### Results
+
+- **NAME:** The name for the records (hostname)
+- **TYPE:** The record type: A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+- **CONTENT:** The content of the record, such as IP address or A record
+- **TTL:** The time to live value
+
+1. Click SAVE CHANGES
+
+![../../_images/createzone.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C64B7661-39C6-4ED3-A6C7-0C57521C7794-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json b/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
new file mode 100644
index 0000000..5287554
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+  "title": "Common Ports & Requirements",
+  "ordinal": 8,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html",
+  "topic_cluster": {
+    "clustering_title": "Common Ports & Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE",
+        "clustering_title": "Common Ports & Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md b/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
new file mode 100644
index 0000000..af2ddc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.md
@@ -0,0 +1,22 @@
+# Common Ports & Requirements
+
+The following chart is useful for troubleshooting Agent install, Static IP assignment, Remote Console connectivity, and Image transfers.
+
+Table 1. Common Ports & Requirements
+
+         | Feature | Method | OS | Source | Destination | Port | Requirement |
+| --- | --- | --- | --- | --- | --- | --- |
+| Agent Communication | All | All | Node | Appliance | 443 | DNS Resolution from node to appliance url |
+| Agent Install | All | Linux | Node | Appliance | 80 | Used for appliance yum and apt repos |
+|  | SSH | Linux | Appliance | Node | 22 | DNS Resolution from node to appliance url Virtual Images configured SSH Enabled on Virtual Image |
+|  | WinRM | Windows | Appliance | Node | 5985 | Not required for agent installation in VMware vCenter and vCloud Director type clouds. Otherwise, access from HPE Morpheus Enterprise App Nodes to Instance Node on 5985 Virtual Images configured WinRM Enabled on Virtual Image(winrm quickconfig) |
+|  | Cloud‐init | Linux |  |  |  | Cloud‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | Cloudbase‐init | Windows |  |  |  | Cloudbase‐init installed on template/image Cloud‐init settings populated in User Settings or in Administration  >  Settings  >  Provisioning Agent install mode set to Cloud‐Init in Cloud Settings |
+|  | VMtools | All |  |  |  | VMtools installed on template Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning when using Static IP’s Existing User credentials entered on Virtual Image when using DHCP RPC mode set to VMtools in VMware cloud settings. |
+| Static IP Assignment & IP Pools | Cloud‐Init | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) Cloud‐init/Cloudbase‐init installed on template/image Cloud‐init settings populated in Morpheus user settings or in Administration  >  Settings  >  Provisioning |
+|  | VMware Tools | All |  |  |  | Network configured in Morpheus (Gateway, Primary and Secondary DNS, CIDR populated, DHCP disabled) VMtools installed on Template/Virtual Image |
+| Remote Console | SSH | Linux | Appliance | Node | 22 | ssh enabled on node user/password set on VM or Host in Morpheus |
+|  | RDP | Windows | Appliance | Node | 3389 | RDP Enabled on node user/password set on VM or Host in Morpheus |
+|  | Hypervisor Console | All | Appliance | Hypervisor Hosts | 443 | Hypervisor host names resolvable by morpheus appliance |
+| Morpheus Catalog Image Download |  | All | Appliance | AWS S3 | 443 | Available space at `/var/opt/morpheus/` |
+| Image Transfer | Stream | All | Appliance | Datastore | 443 | Hypervisor Host Names resolvable by Morpheus Appliance |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json b/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
new file mode 100644
index 0000000..2191c4d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+  "title": "Adding HPE BMaaS Integration",
+  "ordinal": 401,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE BMaaS Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50",
+        "clustering_title": "Adding HPE BMaaS Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md b/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
new file mode 100644
index 0000000..2fc58d8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.md
@@ -0,0 +1,21 @@
+# Adding HPE BMaaS Integration
+
+## Prerequisites
+
+This procedure describes how to integrate the HPE BMaaS with your Morpheus Enterprise environment.
+
+## About this task
+
+To install the **HPE BMaaS** plugin, perform the following steps:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Administration > Integrations.
+3. Select the Plugins tab and click Add button.
+4. Drag the HPE BMaaS `JAR` file into the Drop Files Here area, or click Add File to select it manually. ![Add Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4551F618-EBCF-470F-80C1-64A815379B94-high.png)
+5. Click the Upload.
+
+## Results
+
+After a successful upload, the HPE BMaaS is available for use.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json b/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
new file mode 100644
index 0000000..3c8e6c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+  "title": "Creating and Running an SPP Update Job",
+  "ordinal": 426,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running an SPP Update Job",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E",
+        "clustering_title": "Creating and Running an SPP Update Job"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md b/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
new file mode 100644
index 0000000..e822246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.md
@@ -0,0 +1,54 @@
+# Creating and Running an SPP Update Job
+
+## About this task
+
+This procedure describes how to create and execute a HPE Morpheus Job to perform firmware and driver updates using an HPE SPP image.
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs.
+2. Click Add.
+3. Enter a name for the job.
+
+   NOTE
+
+   - Separate jobs are required for different server generations (for example, Gen10 vs Gen11).
+   - Create separate jobs for **Dry Run** and **Deploy** executions.
+4. Select Workflow Job as the Job Type and click Next.
+5. Select Deploy SPP as the workflow.
+6. Enter the SPPVIRTUALIMAGE value using the ID of the Virtual Image created earlier.
+7. Select a DEPLOYMODE:
+
+   - `DryRun`: Performs inventory only
+   - `Deploy`: Applies firmware and/or driver updates
+8. For SPP Deploy Content, choose one of the following:
+
+   - Firmware only
+   - Drivers only
+   - Firmware and Drivers
+
+   NOTE
+
+   Driver inventory and updates require iSUT and AMS to be running on the target servers.
+9. In the Nodes field, enter the iLO details for each target server in JSON format (minimum 1 server, maximum 30 servers). For example:
+
+   ```
+   ```
+   [  
+     {  
+       "ilo_ip":"1.2.3.4",  
+       "ilo_user":"user1",  
+       "ilo_password":"password1"  
+     },  
+     {  
+       "ilo_ip":"1.2.3.5",  
+       "ilo_user":"user2",  
+       "ilo_password":"password2"  
+     }  
+   ]
+   ```
+   ```
+10. **Optional:**  Create a schedule, or leave the job as Manual.
+11. Select Run Now if you want to execute the job immediately.
+12. Click Next, review the settings, and click Complete.
+13. If the job was not run immediately, click the **gear icon** next to the job and select Execute.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json b/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
new file mode 100644
index 0000000..a8545f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+  "title": "Jobs",
+  "ordinal": 91,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-101B0634-4367-4B11-ACA0-923AC1CA635E",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md b/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
new file mode 100644
index 0000000..1f7bffc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.md
@@ -0,0 +1,19 @@
+# Jobs
+
+## Required Role Permissions
+
+Provisioning: Jobs
+
+- **None:** Cannot access Provisioning > Jobs > Jobs tab
+- **Read:** Can access Provisioning > Jobs > Jobs tab but cannot create, edit, or delete Jobs
+- **Full:** Full permissions to create, view, edit, and delete Jobs
+
+Provisioning: Job Executions
+
+- **None:** Cannot access Provisioning > Jobs > Job Executions tab
+- **Read:** Can access and view Provisioning > Jobs > Job Executions tab including job execution history, status, and Job output
+
+**Subtopics**  
+
+- **[Creating Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html)**
+- **[Creating and Running Security Scan Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json b/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
new file mode 100644
index 0000000..66c307a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+  "title": "Clients",
+  "ordinal": 327,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html",
+  "topic_cluster": {
+    "clustering_title": "Clients",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10BE13E9-1014-4162-97E7-A1056FED89B3",
+        "clustering_title": "Clients"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md b/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
new file mode 100644
index 0000000..c9a1735
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.md
@@ -0,0 +1,24 @@
+# Clients
+
+## Overview
+
+HPE Morpheus Enterprise includes pre-configured OAuth clients and allows the user to create as many additional clients as they’d like. The pre-configured clients are editable but cannot be deleted. Once configured, access tokens may be generated or re-generated from the [API Access section](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html). Their expiration times may be viewed as well. Client settings are available only in the Primary Tenant and affect all Tenants.
+
+## Creating an OAuth Client
+
+To create a new OAuth Client, click + ADD and configure the following:
+
+- **CLIENT ID:** A reference name for the client in HPE Morpheus Enterprise
+- **SECRET:** An optional OAuth client secret
+- **ACCESS TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the token should be enabled
+- **REFRESH TOKEN VALIDITY INTERVAL (SECONDS):** The length of time (in seconds) during which the refresh token should be enabled
+
+Once the client is configured, click SAVE CHANGES.
+
+## Editing and Deleting OAuth Clients
+
+From the OAuth client list view (Administration > Settings > Clients), click the pencil (✎) or trash can (🗑) icons to edit or delete the OAuth Client.
+
+NOTE
+
+Pre-configured HPE Morpheus Enterprise-default clients may be edited but not deleted. User-created clients may be edited or deleted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json b/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
new file mode 100644
index 0000000..5bfc2ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+  "title": "Creating Service Plans for GPU Hardware Passthrough",
+  "ordinal": 195,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Service Plans for GPU Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-10D04894-711A-400A-98A7-A3DECE437CDA",
+        "clustering_title": "Creating Service Plans for GPU Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md b/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
new file mode 100644
index 0000000..f8abe51
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-10D04894-711A-400A-98A7-A3DECE437CDA.md
@@ -0,0 +1,7 @@
+# Creating Service Plans for GPU Hardware Passthrough
+
+When utilizing GPU hardware, it may be most convenient to use a custom Service Plan. This allows administrators to pre-configure the number of discrete hardware cards to attach to the VM at provision time. Once provisioned, the specified number of GPUs will be attached to the VM. For workloads which are provisioned and torn down regularly, this will save additional steps of manually attaching GPUs available from the pool. On teardown, attached devices of all types are released back to the pool. Though in some cases utilizing Service Plans may be most convenient, as you’ll see in the next sections it is not strictly required. It is also possible to manually attach GPUs or other hardware types on any existing VMs running on the HVM Cluster.
+
+To create a new Service Plan, navigate to Administration > Plans. Click + Add and then Service Plan. In the New Service Plan modal, first set the PROVISION TYPE configuration to “KVM.” This will update the available configuration fields and reveal the GPU COUNT configuration. Use this configuration to set the number of GPU hardware cards which should be attached to provisioned VMs using this Service Plan. All other configuration fields for Service Plans go beyond the scope of this section. When finished, click SAVE CHANGES.
+
+![../../_images/gpuPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FEF30612-0724-4835-9310-79D70E4641F1-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json b/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
new file mode 100644
index 0000000..cdee858
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+  "title": "Blueprints",
+  "ordinal": 125,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA",
+        "clustering_title": "Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md b/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
new file mode 100644
index 0000000..0727bc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.md
@@ -0,0 +1,12 @@
+# Blueprints
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html)**
+- **[Blueprint Development Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html)**
+- **[Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html)**
+- **[Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html)**
+- **[Node Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html)**
+- **[App Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html)**
+- **[Catalog Items](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html)**
+- **[Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json b/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
new file mode 100644
index 0000000..2715812
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+  "title": "Linux Settings",
+  "ordinal": 337,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html",
+  "topic_cluster": {
+    "clustering_title": "Linux Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-12450828-47CC-4F83-9E94-AF80242C2E3A",
+        "clustering_title": "Linux Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md b/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
new file mode 100644
index 0000000..77a2800
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.md
@@ -0,0 +1,14 @@
+# Linux Settings
+
+When provisioning a Linux-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Linux user
+- **Password:** The password that will be used with your Linux user (optional if specifying key)
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+- **SSH Key:** Select a pre-existing SSH key pair object in Morpheus. Required of not specifying password and creating your user during provisioning, or required if ssh password authentication has been disabled.
+
+WARNING
+
+If your users Linux Settings password and/or key are not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_linux_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-98554851-1F7D-4D05-A502-2FB93933551A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json b/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
new file mode 100644
index 0000000..4d691ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+  "title": "Spec Templates",
+  "ordinal": 159,
+  "parent_title": "Templates",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html",
+  "topic_cluster": {
+    "clustering_title": "Spec Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444",
+        "clustering_title": "Spec Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md b/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
new file mode 100644
index 0000000..e3ba103
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.md
@@ -0,0 +1,35 @@
+# Spec Templates
+
+Spec Templates allow HPE Morpheus Enterprise users to leverage several major Infrastructure-as-Code solutions. These are typically JSON or YAML-based configuration files which make creating and managing multiple resource types easier. HPE Morpheus Enterprise allows users to create and/or manage a collection of these templates for different solutions and from different sources.
+
+HPE Morpheus Enterprise currently supports Spec Templates of the following types:
+
+- Kubernetes Spec
+- Helm Chart
+- Terraform
+- ARM Template
+- CloudFormation Template
+- OneView Server Profile Template
+- UCS Service Profile Template
+
+HPE Morpheus Enterprise also allows users to leverage templates pulled from URL sources, online repositories (such as GitHub), or you can write a template locally inside the “NEW SPEC TEMPLATE” modal.
+
+TIP
+
+To see HPE Morpheus Enterprise Spec Templates in action, take a look at our guide on [creating custom Instance Types using Terraform](https://docs.morpheusdata.com/en/latest/getting_started/guides/terraform_instances.html) or see our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-use-Spec-Templates-to-create-a-custom-instance-type?language=en_US) for another example where a CloudFormation Spec Template is used to create a provisionable custom Instance Type.
+
+## Creating a Spec Template
+
+### Procedure
+
+1. Navigate to Library > Templates > Spec Templates
+2. Click + ADD
+3. Complete the following fields, then click SAVE CHANGES:
+
+### Results
+
+- **NAME**
+- **TYPE:** See the previous section for a complete list of Spec Template types
+- **SOURCE:** Local, Repository, or URL
+- **CONTENT:** If this is a local Spec Template, supply the template in this field. If the template is supplied through a URL or online repository, the CONTENT field will change to allow the user to point HPE Morpheus Enterprise to that resource
+- **VERSION:** (Only displayed on Terraform Spec Templates) Enter a Terraform version number to force a specific version when provisioning your Terraform Instance Type or App, assuming your Terraform Runtime setting (Administration > Settings > Provisioning Tab) is “auto”. If Terraform Runtime is set to “manual”, HPE Morpheus Enterprise will use the version of Terraform installed on the appliance box
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json b/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
new file mode 100644
index 0000000..139c7a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+  "title": "App Blueprints",
+  "ordinal": 131,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.html",
+  "topic_cluster": {
+    "clustering_title": "App Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-133E4178-5B4C-4BFF-8213-2662774F0B37",
+        "clustering_title": "App Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md b/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
new file mode 100644
index 0000000..a813211
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-133E4178-5B4C-4BFF-8213-2662774F0B37.md
@@ -0,0 +1,20 @@
+# App Blueprints
+
+App Blueprints support a vast array of providers and configurations with programmatic markup or Infrastructure as Code capabilities. Blueprints configs can be manually added or scoped to a git repo. HPE Morpheus Enterprise blueprints allows for full automation configuration, locked fields, tiered boots, and linked tiers with exported evars. All blueprints have permission settings for controlling group and tenant access.
+
+App Blueprint Types
+:   - HPE Morpheus Enterprise
+    - Terraform
+    - ARM (Azure)
+    - CloudFormation (AWS)
+    - Kubernetes
+    - Helm
+
+**Subtopics**  
+
+- **[ARM Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-038058DD-CC8D-41F7-AF14-DB01B16993C4.html)**
+- **[CloudFormation Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html)**
+- **[Helm Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html)**
+- **[Kubernetes Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html)**
+- **[HPE Morpheus Enterprise Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html)**
+- **[Terraform Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json b/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
new file mode 100644
index 0000000..7ea6168
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+  "title": "Huawei Cloud",
+  "ordinal": 458,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.html",
+  "topic_cluster": {
+    "clustering_title": "Huawei Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-13940199-9CEA-485B-87AF-AB47536CD6AE",
+        "clustering_title": "Huawei Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md b/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
new file mode 100644
index 0000000..7b2f2eb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-13940199-9CEA-485B-87AF-AB47536CD6AE.md
@@ -0,0 +1,306 @@
+# Huawei Cloud
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- Huawei OBS buckets (create, manage, delete, and discovery)
+- Huawei SFS (create, manage, and delete)
+
+## Integrate Huawei Cloud with HPE Morpheus Enterprise
+
+To integrate Huawei Cloud with HPE Morpheus Enterprise, we’ll gather the following pieces of information:
+
+- Account Name
+- Identity (IAM) API URL
+- Project
+- Username
+- Password
+
+Begin by logging into your [Huawei Cloud console](https://console-intl.huaweicloud.com/console). If you’re not currently logged in, you will be prompted to do so. Once on the console page, hover over your username in the upper-right corner of the application window and select “My Credentials”.
+
+![../../../_images/1credentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-073462C5-393F-4B31-B939-5DB39532766C-high.png)
+
+From the credentials page, we can gather the Account Name and the Project Name, record them for later when we provide the integration information to HPE Morpheus Enterprise.
+
+![../../../_images/2account_project.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0EA453C5-849B-4F01-AA40-AEDFFCC3A737-high.png)
+
+To gather the API endpoint URL, take a look at the complete list of [endpoints](https://developer.huaweicloud.com/en-us/endpoint). If a specific endpoint exists for your region, use it. In any other case use the endpoint for all regions. It will be formatted like this: <https://iam.myhuaweicloud.com/v3>.
+
+![../../../_images/3identity_api_endpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8DEF10C6-F6CD-4E55-9D76-D67AA280E6CF-high.png)
+
+With this information gathered, and presuming you know the credentials for the service account you wish to use, we can move back into HPE Morpheus Enterprise-UI.
+
+IMPORTANT
+
+Integrating HPE Morpheus Enterprise with Huawei Cloud requires a service account that has programmatic access.
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Huawei Cloud and click NEXT. The information we’ve gathered will be plugged into the CREATE CLOUD modal. The DOMAIN ID field will accept the Account Name field we gathered. Your completed CREATE CLOUD modal will look similar to the one pictured below:
+
+![../../../_images/4add_cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-029DC867-5A63-4F28-9423-F5C3C5C2141F-high.png)
+
+After clicking NEXT, add this new Cloud to a Group or create a new Group. On finalizing the wizard, Huawei Cloud will be integrated into HPE Morpheus Enterprise and ready for provisioning. If you opted to inventory existing workloads, those will be onboarded shortly.
+
+## Add/Edit Huawei Cloud Modal Fields
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity endpoint. See the integration steps above for more detail
+
+DOMAIN ID
+:   The DOMAIN ID field takes the “Account Name” as shown on the [Basic Informati](https://account-intl.huaweicloud.com/usercenter/?locale=en-us#/userindex/accountInfo) of the account. See the integration steps above for more detail
+
+PROJECT
+:   The target project name. See the integration steps above for more detail
+
+USERNAME
+:   The service account username. See the integration steps above for more detail
+
+PASSWORD
+:   The integration service account password. See the integration steps above for more detail
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK image type
+
+Image Store
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VMs
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment.
+
+TIP
+
+When using the RAW image format, you can bypass the image conversion service within the cloud leading to quicker performance. Other image formats are converted to RAW format and back when performing various actions. Using the RAW format from the start will bypass these conversion steps.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Huawei Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud includes the capability to work with Huawei Scalable File Service (SFS). SFS is shared file storage hosted on Huawei Cloud. By integrating HPE Morpheus Enterprise with Huawei Cloud you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Huawei Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Huawei Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+![../../../_images/1editServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DD161EBC-E99E-449A-8B3E-BA8C021C3670-high.png)
+
+Additionally, Huawei SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click + ADD to begin and set the storage server type value to “Huawei SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/2addServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E7F8C4A2-D408-4C34-9C04-C9C7C27A20F0-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to file shares displayed to those whose names match the search terms.
+
+![../../../_images/3shareList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9FD9B522-BF4F-42A5-A282-16726D330F86-high.png)
+
+We can drill into individual file shares by clicking on their hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking + ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+A “Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Huawei SFS file shares can be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking + ADD. Select the type “Huawei SFS Share”. Set the storage service field to a pre-existing Huawei SFS server. A friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones are required fields.
+
+![../../../_images/4addShare.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E135CE4B-C1C8-44C1-9F18-328901E4C10F-high.png)
+
+## Huawei Object Storage Service (OBS)
+
+The HPE Morpheus Enterprise integration with Huawei Cloud also supports Object Storage Service (OBS). HPE Morpheus Enterprise will automatically onboard existing OBS servers and buckets shortly after completing the cloud integration. Before you can add a new OBS server from HPE Morpheus Enterprise, you must know or generate a key and secret value from the Huawei console and must provide a Huawei OBS API endpoint.
+
+### Generate a Key and Secret
+
+From the Huawei web console, log into the account used to integrate Huawei Cloud with HPE Morpheus Enterprise. Hover over your account name in the upper-right corner of the application window and click “My Credentials”. Select “Access Keys” from the left-hand sidebar. To create a new key, click + Create Access Key. Complete the two-factor authentication steps in the box that appears.
+
+![../../../_images/1createKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4FC170FA-49EF-4072-A6F4-42311AB880D9-high.png)
+
+Once the key is generated, download or record the key and store it in a safe location. The key will not be viewable or available for download again after this point.
+
+### Create OBS Server in HPE Morpheus Enterprise
+
+With the key and secret value in hand from the previous section, navigate to Infrastructure > Storage > Servers. Click + ADD. On changing the server type to Huawei OBS, you will see the fields for the access key and the secret key. OBS API endpoints can be found in [Huawei endpoint documentation](https://developer.huaweicloud.com/en-us/endpoint). Include those three values in the Create Server modal along with a friendly name for use in HPE Morpheus Enterprise UI. Just like with SFS objects, we can choose to scope the server to all or specific Tenants at this time.
+
+![../../../_images/2addObsServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BFC92FBB-94A2-46A8-ABFC-E7397C7C6E9E-high.png)
+
+### Create Huawei OBS Bucket
+
+With an OBS server onboarded or created in HPE Morpheus Enterprise, you’re able to create and manage Huawei OBS buckets as needed. To create a new bucket, navigate to Infrastructure > Storage > Buckets. Click + ADD and select “Huawei OBS Bucket”. The following fields are required when creating a Huawei OBS bucket:
+
+- **NAME**: A friendly name for use in HPE Morpheus Enterprise UI
+- **STORAGE SERVICE**: Choose the OBS server to associate the new bucket with
+- **BUCKET NAME**: The name of the bucket in Huawei Cloud, this must be unique
+- **STORAGE CLASS**: If needed, view the [discussion of storage classes](https://support.huaweicloud.com/en-us/eu-west-0-usermanual-obs/en-us_topic_0050937852.html) in Huawei support documentation
+- **BUCKET ACL**: Public Read, Public Read/Write, or Private
+- **BUCKET POLICY**: Public Read, Public Read/Write, or Private
+- **STORAGE QUOTA**: Set to 0 for no quota
+
+Once finished, click SAVE CHANGES
+
+![../../../_images/3createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6A0E3B1B-0B05-4CA3-BBF6-E319A6DD6390-high.png)
+
+## Network and Router Creation
+
+Once a Huawei Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Huawei Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Huawei Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Huawei Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the Huawei project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json b/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
new file mode 100644
index 0000000..eb739af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+  "title": "OAuth 2.0 Credentials",
+  "ordinal": 238,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html",
+  "topic_cluster": {
+    "clustering_title": "OAuth 2.0 Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F",
+        "clustering_title": "OAuth 2.0 Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md b/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
new file mode 100644
index 0000000..03f2f8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.md
@@ -0,0 +1,22 @@
+# OAuth 2.0 Credentials
+
+HPE Morpheus Enterprise supports storage of credential sets for retrieving temporary access tokens, through OAuth 2.0, and using the tokens to access some resource. These credential sets can be used with REST-type Option Lists to retrieve information behind this type of authentication wall. Once stored, the credential can be used with as many Option Lists as needed and potentially in other areas of the product in the future.
+
+To create a new credential set, click + ADD and then select “OAuth 2.0”. Complete the following, not all fields are present or required in every context:
+
+- **CREDENTIAL STORE:** Select “Internal” or an integrated external Cypher store (if any). See the next section for instructions on standing up and integrating with an external Cypher store
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **GRANT TYPE:** Client Credentials or Password Credentials
+- **ACCESS TOKEN URL:** The authorization server’s token endpoint
+- **CLIENT ID:** The client ID for an app registered with the target service
+- **CLIENT SECRET:** The client secret, often needed when requesting access outside the context of a specific user
+- **USERNAME:** (Only present with “Password Credentials” Grant Type) The username for a user with target data access
+- **PASSWORD:** (Only present with “Password Credentials” Grant Type) The password for the user indicated above
+- **SCOPE:** The scope of access requested to the target resource
+- **CLIENT AUTHENTICATION:** “Send as basic auth header” or “Send client credentials in body” - Indicates how HPE Morpheus Enterprise should issue the token received in requests to the target resource
+
+Once done, click ADD CREDENTIALS.
+
+With the OAuth 2.0 credential set stored, they can be set on REST-type Option Lists to source data from behind a compatible authentication wall. With a REST-type Option List open (Library > Options > Option Lists), click the CREDENTIALS dropdown and select the credential set you’ve created. Alternatively, you can add a credential set directly in the add/edit Option List modal if needed. Option Lists can be associated with Select List or Typeahead-type Inputs and applied to Layouts, Instance Types, Workflows, and more to allow for customization at provision or Workflow execution time. Additional details on creating Option Lists can be found in the Library section of HPE Morpheus Enterprise docs.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json b/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
new file mode 100644
index 0000000..84b28b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+  "title": "Advanced morpheus.rb Settings",
+  "ordinal": 30,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html",
+  "topic_cluster": {
+    "clustering_title": "Advanced morpheus.rb Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78",
+        "clustering_title": "Advanced morpheus.rb Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md b/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
new file mode 100644
index 0000000..c15d7e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.md
@@ -0,0 +1,124 @@
+# Advanced morpheus.rb Settings
+
+Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work.
+
+```
+```
+app['encryption_key_suffix'] = '$suffix'  
+  # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+appliance_url 'https://morpheus.appliance-url.com'  
+  # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+  # The appliance_url cannot exceed 64 characters  
+  # The appliance_url must not contain a trailing `/`.  
+bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+opensearch['auth_user'] = 'morpheus-es-user'  
+opensearch['enable'] = true  
+opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+opensearch['host'] = "127.0.0.1"  
+opensearch['port'] = "9200"  
+opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+opensearch['use_tls'] = false  
+↓ The following Opensearch settings are only valid for Internal/Embedded Opensearch services  
+opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+opensearch['memory_alloc_arena_max'] = 2  
+opensearch['memory_map_max'] = 65536  
+opensearch['memory_map_threshold'] = 131072  
+opensearch['memory_top_pad'] = 131072  
+opensearch['memory_trim_threshold'] = 131072  
+opensearch['open_files'] = 204800  
+opensearch['secure_mode'] = false  
+opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+opensearch['xmx'] = 0.25  
+guacd['guacamole_enabled'] = false  
+guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+mysql['enable'] = true  
+mysql['host'] = {'127.0.0.1' => 3306}  
+mysql['use_tls'] = false  
+mysql['morpheus_db_user'] = 'morpheus-db-user'  
+mysql['morpheus_password'] = 'morpheus-db-password'  
+mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+mysql['tmp_dir'] = '/tmp/mysql'  
+mysql['log_dir'] = '/var/log/morpheus/mysql'  
+mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+mysql['max_connections'] = 151  
+mysql['max_allowed_packet'] = 67108864  
+mysql['mysql_connect_timeout'] = 60000  
+mysql['mysql_max_reconnects'] = 2  
+mysql['mysql_queries_before_retry_source'] = 0  
+mysql['mysql_seconds_before_retry_source'] = 300  
+nginx['cache_max_size'] = '5000m'  
+nginx['enable'] = true  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['max_loops'] = 60 # seconds  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['log_format_name'] = 'custom'  
+nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+nginx['ssl_company_name'] = "Morpheus, LLC"  
+nginx['ssl_country_name'] = "US"  
+nginx['ssl_email_address'] = "personal@email.com"  
+nginx['ssl_locality_name'] = "San Mateo"  
+nginx['ssl_organizational_unit_name'] = "DevOps"  
+nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+nginx['ssl_session_timeout'] = "5m"  
+nginx['ssl_state_name'] = "CA"  
+nginx['worker_connections'] = 10240  
+nginx['workers'] = integer calculated from number of cpus  
+nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+rabbitmq['enable'] = true  
+rabbitmq['host'] = '127.0.0.1'  
+rabbitmq['port'] = '5672'  
+rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+rabbitmq['vhost'] = 'morpheus'  
+↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+rabbitmq['heartbeat'] = nil  
+rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+rabbitmq['nodename'] = 'rabbit@localhost'  
+rabbitmq['port'] = '5672'  
+rabbitmq['use_tls'] = false  
+repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+ui['kerberos_config'] = nil  
+ui['kerberos_login_config'] = nil  
+ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+ui['max_memory_mb'] = nil  
+ui['memory_alloc_arena_max'] = 2  
+ui['memory_map_max'] = 65536  
+ui['memory_map_threshold'] = 131072  
+ui['memory_top_pad'] = 131072  
+ui['memory_trim_threshold'] = 131072  
+ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+ui['support_links'] = {  
+  'name' => ['url', 'i18n'],  
+  'name1' => ['url1', i18n1'],  
+  'name2' => ['url2', i18n2']  
+} #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+ui['xmx'] = 0.25
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json b/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
new file mode 100644
index 0000000..d3d58d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+  "title": "Overview",
+  "ordinal": 226,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md b/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
new file mode 100644
index 0000000..ce51737
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.md
@@ -0,0 +1,31 @@
+# Overview
+
+HPE Morpheus Enterprise provisions the following load balancers:
+
+- Amazon ALB (Application Load Balancer)
+- Azure Load Balancer
+- HaProxy Container
+
+and integrates with the following external load balancers:
+
+- Citrix NetScaler
+- F5 BigIP (v11.4+)
+- FortiADC
+- NSX
+- NSX Advanced
+
+Once created or integrated, load balancers are available as an option to be added during provision time or post-provisioning.
+
+Once a load balancer is added to an instance, you can manually scale or configure auto-scaling based on thresholds or schedules, and burst across clouds with cloud priority.
+
+In the load balancers page there are two sections:
+
+Load Balancers
+:   View or edit existing load balancers, add new load balancers.
+
+Virtual Servers
+:   View and link to Instances that are attached to load balancers.
+
+## Group and Tenant Access
+
+Load balancers can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the load balancer resource. Only workloads being provisioned to the selected Groups would have visibility to the load balancer. Workloads provisioned to other Groups would not see the load balancer as an available selection. **Tenant Permissions** control which Tenants may see the load balancer. Public visibility allows access to the load balancer for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json b/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
new file mode 100644
index 0000000..1111bb6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+  "title": "Adding HPE SPP to the Virtual Image Library",
+  "ordinal": 424,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html",
+  "topic_cluster": {
+    "clustering_title": "Adding HPE SPP to the Virtual Image Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-151B596B-EE69-4D4B-8C80-964A90D3523C",
+        "clustering_title": "Adding HPE SPP to the Virtual Image Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md b/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
new file mode 100644
index 0000000..433ba42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.md
@@ -0,0 +1,28 @@
+# Adding HPE SPP to the Virtual Image Library
+
+## About this task
+
+This procedure describes how to add an HPE Service Pack for ProLiant (SPP) ISO to the Morpheus Virtual Images library for use in firmware and driver update workflows.
+
+1. Obtain the appropriate HPE SPP ISO for the target ProLiant server generation.
+
+   NOTE
+
+   A separate ISO is required for each server generation (for example, Gen10 and Gen11).
+2. In the Morpheus appliance, navigate to Library > Virtual Images.
+3. Click Add > SPP.
+4. Enter a name for the image (for example, `HPE Gen10 SPP 2025.09.00`).
+5. From the Operating System drop-down list, select the appropriate **HPE SPP for Gen…** entry.
+6. Add the SPP ISO using one of the following methods:
+   - Upload the locally downloaded ISO file, or
+   - Select **URL / PATH** and paste the full URL for the ISO.
+7. Leave all other properties at their default values.
+8. Click Save Changes.
+
+   NOTE
+
+   When uploading a local file, wait for the upload to complete.
+9. In the Virtual Images list, wait until:
+   - Source shows `Uploaded`
+   - Status shows `Active`
+10. Record the **ID** of the Virtual Image entry. This ID is required when creating the update job.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json b/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
new file mode 100644
index 0000000..7d9eebf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+  "title": "Orchestrating Load Balancers",
+  "ordinal": 228,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html",
+  "topic_cluster": {
+    "clustering_title": "Orchestrating Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-151C50C5-5883-4137-A9B0-EAF5F8087117",
+        "clustering_title": "Orchestrating Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md b/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
new file mode 100644
index 0000000..590d37f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.md
@@ -0,0 +1,40 @@
+# Orchestrating Load Balancers
+
+A large part of application orchestration and automation involves tying various web services and backend services into different load balancer configurations. If the automation tool is unable to communicate or integrate with this aspect of your infrastructure, a lot of gaps will be created in the full orchestrated flow of application deployment. This is why Morpheus provides deep integration with load balancers and explicit definitions with catalog items as to how they are connected to provisioned instances. Some of the functionality includes:
+
+- Public Cloud Load Balancer Support
+- Private Cloud Load Balancer Support
+- Port Type definitions (Profiles like HTTP/HTTPS or UDP)
+- SSL Certificate Management and SSL Certificate Upload
+- SSL Passthrough or Forced Redirect
+
+Not only does Morpheus have an ability to provision HAProxy based load balancer containers for easy consumption in development environments, but also has direct tie ins with several Load Balancer Types:
+
+- F5 BigIP
+- Netscaler
+- NSX Advanced Load Balancer
+- Amazon ELB
+- Amazon ALB
+- Azure Load Balancer
+- Fortinet
+- Openstack Octavia
+- HA Proxy
+- NSX
+
+Morpheus exposes configuration options during provisioning of an Instance relevant and common to each supported LB Integration. In some cases, Morpheus also provides direct management and sync support for VIP configurations on the various Load Balancers (such as F5, and NSX Advanced Load Balancer), However in a day to day orchestrated workflow this would not be the ideal means by which a user should consume load balancer services.
+
+By tying the Load Balancer associations into the provisioning of instances and the definition of the instance catalog item, the lifecycle of the VIP can more easily be maintained throughout the lifecycle of whatever application may be deployed.
+
+## Setting up an Instance for Load Balancer Consumption
+
+Several of the provided Morpheus instance types are ready to go with load balancer orchestration out of the box (Apache, Nginx, Tomcat, Node.js, etc). It is also fairly easy to extend existing generic instance types during provisioning to be tied to load balancers or to set up said catalog items in advanced for such functionality.
+
+When creating a custom Instance Type (in Library), one can define a list of exposed ports that the node type within the instance exposes. When defining these exposed ports it prompts for a Name, Port Number, and LB Type. The LB Type is what enables load-balancer functionality. This can either be HTTP,HTTPS, or TCP. This specification helps build the correct profile for the VIP as well as setup the appropriate types of Health Monitors within the target load balancer integration.
+
+Now, when a user consumes this custom instance type (either through single instance provisioning or full application blueprint provisioning), a section appears in the Automation phase of provisioning. Each port that is defined that exposes a load-balancer gets a dropdown to choose which load balancer integration attach to the exposed port and various prompts become available.
+
+These prompts control features ranging from target VIP Address to selecting an SSL Certificate to be applied to the VIP. These SSL Certificates will even go so far as to create SSL Profiles in integrations for things like an F5 automatically for the application.
+
+Once the instance is provisioned, as part of the final phase, the load balancer configuration will be applied and maintained on the instance. This association can be manipulated after the fact via the “Scale” tab found on the Instance Detail page.
+
+Another benefit to associating load-balancers this way is that the pool members are automatically maintained during scaling events, either via auto-scaling thresholds or manual node additions / removals.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json b/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
new file mode 100644
index 0000000..6ceec10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+  "title": "Overview",
+  "ordinal": 171,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1621A716-2765-4655-B4D0-C95B8416F4D3",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md b/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
new file mode 100644
index 0000000..d7d78dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.md
@@ -0,0 +1,22 @@
+# Overview
+
+Infrastructure  >  Clusters is for creating and managing Kubernetes Clusters, HPE Morpheus Enterprise manager Docker Clusters, KVM Clusters, or Cloud specific Kubernetes services such as EKS, AKS and GKE.
+
+## Cluster Types
+
+Table 1.
+
+     |  |  |  |
+| --- | --- | --- |
+| **Name** | **Description** | **Provider Type** |
+| Kubernetes Cluster | Provisions by default a Kubernetes cluster consisting of 1 Kubernetes Master and 3 Kubernetes Worker nodes. Additional system layouts available including Master clusters. Custom layouts can be created. | Kubernetes |
+| Docker Cluster | Provisions by default a Morpheus controlled Docker Cluster with 1 host. Additional hosts can be added. Custom layouts can be created. Existing Morpheus Docker Hosts are automatically converted to Clusters upon 4.0.0 upgrade. | Docker |
+| EKS Cluster | Amazon EKS (Elastic Kubernetes Service) Clusters | Kubernetes |
+| AKS Cluster | Azure AKS (Azure Kubernets Service) Clusters | Kubernetes |
+| Ext Kubernetes | Brings an existing (brownfield) Kubernetes cluster into HPE Morpheus Enterprise | Kubernetes |
+| GKE Cluster | Google Cloud GKE (Google Kubernetes Engine) Clusters | Kubernetes |
+| HVM Cluster | A KVM‐based virtualization solution. See the detailed section below on HVM Clusters for complete use documentation. | KVM |
+
+NOTE
+
+Refer to clusterLayouts for supported Clouds per Cluster Type.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json b/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
new file mode 100644
index 0000000..0ea9e0e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+  "title": "Diagrams",
+  "ordinal": 344,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html",
+  "topic_cluster": {
+    "clustering_title": "Diagrams",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B",
+        "clustering_title": "Diagrams"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md b/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
new file mode 100644
index 0000000..cd3fbc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.md
@@ -0,0 +1,45 @@
+# Diagrams
+
+The HPE Morpheus Enterprise diagram repository contains many diagrams related to HPE Morpheus Enterprise appliance architectures, HPE Morpheus Enterprise concepts, and reference diagrams for integrating HPE Morpheus Enterprise with third-party technologies.
+
+## Appliance Architectures
+
+### All-in-one (single node) Installation
+
+![../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+### 3-node High Availability (HA) Installation
+
+![../_images/morpheus-3node-ha.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EF3C066B-2133-4DBC-8E53-1C23C38740D4-high.png)
+
+### Fully Distributed High Availability (HA) Installation
+
+![../_images/FullDistributedSingleSite.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6791DB71-7757-41D2-985E-8E45863D89CD-high.png)
+
+## HPE Morpheus Enterprise Concepts
+
+### Cloud-Group-Role Relationship
+
+![../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+### Library Items
+
+![../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
+
+### Mapping Morpheus Constructs to Public and Private Cloud Constructs
+
+![../_images/awsAndMorpheusConstructs.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-921BCD31-0FFD-4AB6-98C5-9FA5BCC5E31C-high.png)
+
+## Third-Party Technology Integration
+
+### Zerto
+
+![../_images/morpehus_zerto_chart.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+### Veeam
+
+![../_images/MorpheusVeeamIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-42CD5807-1040-4713-9939-451BA81D9190-high.png)
+
+### Mapping Identity Source Groups to Morpheus Roles
+
+![../_images/mapIdentityToMorpheus.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-58D1993D-5964-4804-877B-ECF3112E147E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json b/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
new file mode 100644
index 0000000..02dc88d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+  "title": "Unmanaged Networks",
+  "ordinal": 430,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html",
+  "topic_cluster": {
+    "clustering_title": "Unmanaged Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1741A126-636E-4A96-812C-48A8B7A25E88",
+        "clustering_title": "Unmanaged Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md b/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
new file mode 100644
index 0000000..d365967
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1741A126-636E-4A96-812C-48A8B7A25E88.md
@@ -0,0 +1,23 @@
+# Unmanaged Networks
+
+The unmanaged Network mode is used when the network infrastructure is not managed by HPE Morpheus.
+
+In this case, there is a minimal configuration that is created as default when the cloud gets created with the network mode set to `Unmanaged network`. This minimal configuration includes a default Resource Pool that can be used to associate compute servers with, and a default unmanaged network that is available during instance provisioning to attach with compute servers.
+
+The default unmanaged network is configured as an untagged network with DHCP as the IP allocation method. This allows a compute instance provisioned to come up with network connectivity without any specific network configuration required from the user.
+
+The unmanaged network assumes:
+
+- The network infrastructure to be configured correctly for the untagged network to work correctly.
+- A DHCP server stood up in the infrastructure for that network.
+
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DD9E1A8A-D473-4DDE-9761-DD613DCF1F4B-high.png)
+
+Users can create other networks (VLANs) if required, in addition to the default unmanaged network, and use them in their BM instance.
+
+NOTE
+
+- If the ALLOW IP OVERRIDE checkbox is selected (allows selection of DHCP or static IP or IP Pool), ensure that the CIDR and GATEWAY fields are configured correctly.
+- At present, only one physical interface is supported for the unmanaged network mode.
+
+The network consumption by an instance is the same as for managed networks.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json b/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
new file mode 100644
index 0000000..647a724
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+  "title": "Library",
+  "ordinal": 101,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html",
+  "topic_cluster": {
+    "clustering_title": "Library",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-17B067B3-32C3-4DE7-82DE-B6033C235495",
+        "clustering_title": "Library"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md b/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
new file mode 100644
index 0000000..83c9187
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.md
@@ -0,0 +1,13 @@
+# Library
+
+**Subtopics**  
+
+- **[Labels](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html)**
+- **[Automation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html)**
+- **[Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1191CCE3-E610-468E-95EE-ED08BA64A6BA.html)**
+- **[Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html)**
+- **[Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html)**
+- **[Templates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html)**
+- **[Library Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html)**
+- **[Operating Systems](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html)**
+- **[Variables](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json b/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
new file mode 100644
index 0000000..f3c2220
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+  "title": "Morpheus Virtual Desktops",
+  "ordinal": 368,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Virtual Desktops",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74",
+        "clustering_title": "Morpheus Virtual Desktops"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md b/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
new file mode 100644
index 0000000..0849dc5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.md
@@ -0,0 +1,450 @@
+# Morpheus Virtual Desktops
+
+## VDI Pools Overview
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
+
+## Virtual Desktop Persona Overview
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json b/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
new file mode 100644
index 0000000..5cd2e28
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+  "title": "Costing: Cloud Costing",
+  "ordinal": 58,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Cloud Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-180B8370-AEF2-45C1-9E72-99FF796CB222",
+        "clustering_title": "Costing: Cloud Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md b/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
new file mode 100644
index 0000000..27158e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.md
@@ -0,0 +1,39 @@
+# Costing: Cloud Costing
+
+![../_images/1cloudcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-429BA931-09F3-4CC2-AC8E-45B3D0167664-high.png)
+
+The Cloud Costing dashboard breaks down total costs by cloud type, cloud region, and individual cloud. This includes reporting the total number of clouds that meet your filters, the month-to-date running total, the projected monthly spend, among other useful metrics.
+
+## Filters
+
+Filter the Clouds pulled into the dashboard by one or more of the following fields:
+
+- Cloud (all matched by search)
+- Group
+- Cloud (selected from dropdown)
+- Tenant
+- Tag (Key)
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Clouds that meet set filters:
+
+- **CLOUDS:** The total number of Clouds that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Clouds meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Clouds meeting dashboard filters
+- **CLOUD TYPES:** The number of distinct cloud types that meet the dashboard filters, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud types
+- **REGIONS:** The total number of regions represented by Clouds meeting the dashboard filters
+
+In addition to the totals described above, graphs visualize the percentage of these totals accounted for by specific Clouds, Cloud types, and Cloud regions.
+
+## Cloud List
+
+Each Cloud that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Cloud:
+
+- **TYPE:** The Cloud type, such as Amazon AWS, Microsoft Azure, VMware, or any other HPE Morpheus Enterprise-supported Cloud type
+- **NAME:** The name given to the Cloud in HPE Morpheus Enterprise at the time of integration
+- **LOCATION:** The Cloud location (if available)
+- **REGION:** The Cloud region (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Cloud listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Cloud listed
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json b/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
new file mode 100644
index 0000000..4d92f4d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+  "title": "Security Groups",
+  "ordinal": 223,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html",
+  "topic_cluster": {
+    "clustering_title": "Security Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1",
+        "clustering_title": "Security Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md b/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
new file mode 100644
index 0000000..269452d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.md
@@ -0,0 +1,81 @@
+# Security Groups
+
+Infrastructure  >  Network - Security Groups
+
+## Overview
+
+A Security Group acts as a virtual firewall that controls the traffic for one or more Instances. When you launch an instance, you associate one or more Security Groups with the instance. You add rules to each Security Group that allow traffic to or from its associated Instances. You can modify the rules for a Security Group at any time; the new rules are automatically applied to all Instances that are associated with the Security Group.
+
+IMPORTANT
+
+The local firewall setting must be enabled for Security Groups to be applied in the guest firewall (iptables). The local firewall setting can be enabled in Infrastructure > Clouds > Click the Cloud > Edit > Advanced Options > LocalFirewall (On/Off)
+
+IMPORTANT
+
+When then local firewall setting is enabled, Morpheus will automatically set an iptable rule to allow incoming connections on tcp port 22 from the Morpheus Appliance.
+
+IMPORTANT
+
+If the local firewall setting is configured on a cloud that supports Security Groups natively (AWS for example), the local firewall setting is ignored and the guest firewall will not be modified. Security Groups will be attached to the instance as normal
+
+## Add Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the + Add Security Group button.
+3. From the Security Group Wizard input a name, and description.
+4. Save Changes
+
+## Add Security Group Rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to add a rule to.
+3. From the Security Group page click the + Add Rule button.
+4. From the Rule Wizard select the rule type and input source and depending on the type selected protocol and input a port range.
+5. Save Changes
+
+## Edit Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to edit a rule in.
+3. Click the edit icon on the row of the Security Group rule you wish to edit.
+4. Modify information as needed.
+5. Save Changes
+
+## Delete Security Group rule
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network - Security Groups
+2. Click the name of the Security Group you wish to delete a rule from.
+3. Click the delete icon on the row of the Security Group rule you wish to delete.
+
+## Add Cloud Security Group
+
+### About this task
+
+To add Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the desired cloud to add a Security Group
+3. Click the Networks tab
+4. Within the “Security Groups” section, click on a Security Group to edit its rules
+5. Alternatively, click + ADD SECURITY GROUP to create a new one
+
+## Remove Cloud Security Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click the name of the cloud to remove the Security Group from.
+3. Click the Security Groups tab.
+4. Click the Edit Security Groups button.
+5. Click the - (Minus) button of the Security Group from the Added Security Groups list to remove.
+6. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json b/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
new file mode 100644
index 0000000..8ac5082
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+  "title": "Building Catalog Blueprints",
+  "ordinal": 141,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728",
+        "clustering_title": "Building Catalog Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md b/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
new file mode 100644
index 0000000..626f291
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.md
@@ -0,0 +1,62 @@
+# Building Catalog Blueprints
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+HPE Morpheus Enterprise Blueprints allow for full multi-tier application deployment. In the Self Service catalog, user can create catalog items based on pre-existing App Blueprints. If new Blueprints need to be created for the Service Catalog, see other sections of HPE Morpheus Enterprise docs on building App Blueprints of various supported types. Just like with catalog Instances, we can pre-configure Blueprints and present them to users viewing the Service Catalog Persona view for easy, one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Blueprint. The modal window will appear to configure and add a new catalog Blueprint.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIGURE:** Click CONFIGURE to use the familiar App provisioning wizard to tie Blueprint and App deployment configuration to the Catalog Item
+- **APP SPEC:** Inject App spec here for any fields required to provision an App from your Blueprint. You may also inject any overrides to the existing Blueprint spec that are desired. App Spec configuration must be YAML, a simple example that names the App and sets the Group and Cloud is included below:
+
+  ```
+  ```
+  #Example App Spec  
+  name: '<%= customOption.appName %>'  
+  group:  
+    name: Dev Group  
+  environment: Dev  
+  tiers:  
+    Web:  
+      instances:  
+        - instance:  
+            type: nginx  
+            cloud: Dev AWS  
+    App:  
+      instances:  
+        - instance:  
+            type: apache  
+            cloud: Dev AWS
+  ```
+  ```
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+
+  NOTE
+
+  App spec custom option variables should be single quoted in YAML: `cloud: '<%= customOption.cloud %>'`. Additionally, not all variables are available here as many are unknown until provisioning. Users may use any custom Input values (customOption) as well as name or hostname values which are resolved as part of naming policy evaluation.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json b/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
new file mode 100644
index 0000000..cf7c180
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+  "title": "Creating Roles",
+  "ordinal": 301,
+  "parent_title": "Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1AC5F825-20D5-4B28-936A-2DD024250026",
+        "clustering_title": "Creating Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md b/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
new file mode 100644
index 0000000..09ff635
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1AC5F825-20D5-4B28-936A-2DD024250026.md
@@ -0,0 +1,6 @@
+# Creating Roles
+
+**Subtopics**  
+
+- **[User Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html)**
+- **[Tenant Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json b/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
new file mode 100644
index 0000000..a5ee028
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+  "title": "Create a MultiTenant User Role",
+  "ordinal": 304,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html",
+  "topic_cluster": {
+    "clustering_title": "Create a MultiTenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1B184F05-C570-446E-8C3A-FC24792DE213",
+        "clustering_title": "Create a MultiTenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md b/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
new file mode 100644
index 0000000..222c262
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1B184F05-C570-446E-8C3A-FC24792DE213.md
@@ -0,0 +1,28 @@
+# Create a MultiTenant User Role
+
+## About this task
+
+A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+6. Select the MULTITENANT ROLE checkbox
+7. Optionally select the MULTITENANT LOCKED checkbox \* When enabled, the FEATURE ACCESS settings in the Role will not be editable by subtenants. Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+8. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
new file mode 100644
index 0000000..a9b7fc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+  "title": "Volumes",
+  "ordinal": 233,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.html",
+  "topic_cluster": {
+    "clustering_title": "Volumes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4",
+        "clustering_title": "Volumes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
new file mode 100644
index 0000000..7409f80
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1BF34D63-AEE2-4305-BB8C-B625A1E6B1C4.md
@@ -0,0 +1,176 @@
+# Volumes
+
+Volumes sync or created in HPE Morpheus Enterprise can be viewed in Infrastructure- Storage - Volumes. Volumes can be added for Storage Servers integrated with HPE Morpheus Enterprise in the Infrastructure- Storage - Servers section.
+
+## Volumes Types
+
+The available Volume Types list and filterable by are:
+
+- 3Par Volume
+- Alibaba Cloud SSD
+- Alibaba Efficiency Disk
+- Alibaba Cloud Disk
+- AWS gp2
+- AWS io1
+- AWS sc1
+- AWS st1
+- Azure Volume
+- Azure Disk
+- Bluemix Disk
+- Bluemix SAN
+- Bluemix SAN
+- CD ROM
+- DO Disk
+- ECS Block Storage
+- ECS Object Storage
+- ECS Shared File System
+- Floppy Disk
+- Google Standard
+- HP Enclosure Disk
+- Oracle iSCSI
+- Isilon NFS Volume
+- Nutanix IDE
+- Nutanix SATA
+- Nutanix SCSI
+- Open Telekom Volume
+- Openstack Disk
+- Openstack Volume
+- Oracle Block Volume
+- Oracle Disk
+- Oracle Virtual Volume
+- SCVMM Datastore
+- Softlayer Disk
+- Softlayer SAN
+- Softlayer SAN
+- Disk
+- UpCloud Disk
+- UpCloud MaxIOPS
+- NULL
+- NULL
+- VMWare Datastore
+- VMWare Disk
+
+## CREATE VOLUME
+
+At least one Storage Server Integration from Infrastructure- Storage - Servers is required to create volumes from Infrastructure- Storage - Volumes.
+
+### 3par
+
+#### About this task
+
+To Add a 3Par Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select 3Par from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the 3par Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   3Par Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+       PROVISION TYPE
+       :   - FULL
+           - TPVV
+           - SNP
+           - PEER
+           - UNKNOWN
+           - TDVV
+
+       Click COMPLETE
+       :   Select COMPLETE
+
+### Dell EMC ECS
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC ECS from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the DELL EMC ECS Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   ECS Block Storage ECS Object Storage ECS Shared File System
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+   Click COMPLETE
+   :   Select COMPLETE
+
+### Dell EMC Isilon
+
+#### About this task
+
+To Add a Dell EMC ECS Volume:
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the VolumeS tab, Click the + ADD button.
+4. Select Dell EMC Isilon from the dropdown list
+5. From the CREATE VOLUME Wizard input the following: 
+
+   SELECT TYPE
+   :   STORAGE SERVER
+       :   Name of the Dell EMC Isilon Storage Server added in Infrastructure- Storage - Servers
+
+       GROUP
+       :   Select Storage Group
+
+       VOLUME TYPE
+       :   Isilon NFS Volume
+
+       Click NEXT
+       :   Select NEXT
+
+   CONFIGURE
+   :   NAME
+       :   Name of the Volume
+
+       ALLOWED IP’s
+       :   Specify IP Addresses to limit accessibility to the File Share
+           :   Leave blank for open access
+               :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+       VOLUME SIZE
+       :   Specify size of the Volume (in MB)
+
+   Click COMPLETE
+   :   Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json b/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
new file mode 100644
index 0000000..63a26f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+  "title": "Add Citrix NetScaler Integration",
+  "ordinal": 495,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html",
+  "topic_cluster": {
+    "clustering_title": "Add Citrix NetScaler Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42",
+        "clustering_title": "Add Citrix NetScaler Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md b/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
new file mode 100644
index 0000000..ce789e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.md
@@ -0,0 +1,48 @@
+# Add Citrix NetScaler Integration
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Citrix NetScaler**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Citrix LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E18D9A6C-6C61-4C00-9B2C-45F95C2FEEF7-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the NetScaler API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the NetScaler API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NetScaler service account username.
+   :   **PASSWORD \***: Enter NetScaler service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new NetScaler Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new NetScaler Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new NetScaler Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json b/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
new file mode 100644
index 0000000..a7fb957
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+  "title": "Add Virtual Image",
+  "ordinal": 151,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html",
+  "topic_cluster": {
+    "clustering_title": "Add Virtual Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4",
+        "clustering_title": "Add Virtual Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md b/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
new file mode 100644
index 0000000..5b416f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.md
@@ -0,0 +1,124 @@
+# Add Virtual Image
+
+## About this task
+
+Virtual Images can be upload to HPE Morpheus Enterprise from local files or URL’s. Amazon and Azure Marketplace metadata can also be added to the Virtual Images library, enabling the creation of custom catalog Instance Type from Marketplace images (no image is transferred to HPE Morpheus Enterprise when adding Marketplace images).
+
+WARNING
+
+Be conscious of your Storage Provider selection. The default Storage Provider is the HPE Morpheus Enterprise Appliance at `/var/opt/morpheus/morpheus-ui/vms`. Uploading large images to the HPE Morpheus Enterprise Appliance when there is inadequate space will cause upload failures and impact Appliance functionality. Ensure there is adequate space on your selected Storage Provider. Additional Storage Provider can be added at Infrastructure  >  Storage, which can be configured as the default Virtual Image Store or selected when uploading Images.
+
+NOTE
+
+VMware-type OVF Virtual Images do not support mounted ISO uploads
+
+To Add Virtual Image:
+
+## Procedure
+
+1. Select + Add in the Virtual Images page.
+2. Select Image format: 
+
+   - Alibaba
+   - Amazon AMI
+   - Azure Marketplace
+   - Digital Ocean
+   - ISO
+   - PXE Boot
+   - QCOW2
+   - RAW
+   - VHD
+   - VMware (vmdk/ovf/ova)
+3. Configure the following on the Virtual Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+
+   NOTE
+
+   Default Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage. Ensure local folders are owned by morpheus-app.morpheus-app if used.
+
+   WARNING
+
+   Provisioning will fail if Cloud init Enabled is checked and Cloud-Init is not installed on the Image.
+
+   NOTE
+
+   Existing Image credentials are required for Linux Images that are not Cloud-Init enabled and for Windows Images when Guest Customizations are not used. Cloud-Init and Windows user settings need to be configured in Administration > Settings > Provisioning when using Cloud-Init or Guest Customizations and new credentials are not set on the Virtual Image.
+4. Upload Image
+   :   Images can be uploaded by File or URL:
+       :   File
+           :   Drag and Drop the image file, or select Add File to select the image file.
+
+           Url
+           :   Select the URL radio button, and enter URL of the Image.
+
+       NOTE
+
+       The Virtual Image configuration can be saved when using a URL and the upload will finish in the background. When selecting/drag and dropping a file, the image files must upload completely before saving the Virtual Image record or the Image will not be valid.
+5. Save Changes.
+
+## VMware - VM Templates Copies
+
+In a VMware environment, you may have a single VM template that you use across different vCenters. Uploading an image to HPE Morpheus Enterprise, mentioned in the Add Virtual Image section, is one method to solve this. Alternatively, an organization may decide to create a VM template in one vCenter and then transfer it to other vCenters, which then could be sync’d into HPE Morpheus Enterprise.
+
+If all the vCenters are added as Clouds into HPE Morpheus Enterprise and the templates are named the same in each vCenter, they will be aggregated under a single virtual image in HPE Morpheus Enterprise. This means that as you deploy to the various vCenter Clouds in HPE Morpheus Enterprise using this virtual image, it will choose the correct VM template to use based on the Cloud deployed to.
+
+This eliminates the need for creating multiple Node Types for each virtual image if the templates were named differently in each vCenter. This can reduce the overhead of maintaining multiple Node Types and reduces user selections. As well, this can reduce the cloning time of VMs by avoiding network transfers of images between geographic locations, ensuring the closest VM template is selected.
+
+HPE Morpheus Enterprise supports VMware Content Libraries storing VM templates and syncing into HPE Morpheus Enterprise, the same as a template in a folder. Additionally, the Content Library can be used to house the same template in multiple libraries. If they have the same name, these templates will be aggregated under a single virtual image. If the Content Library is stored on a datastore that the target host/cluster has access to, it will use that library first, to reduce the cloning time. If the Content Library is not stored in a datastore accessible by the cluster/host, a copy of the VM template will be performed to the target host/cluster instead.
+
+NOTE
+
+VM templates are a **Data Center** level object. The same process above applies to a single VMware cloud with multiple logical data centers. It will not apply to clusters, as a template is not associated with a cluster, only when it is converted to a VM.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json b/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
new file mode 100644
index 0000000..132c157
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+  "title": "Roles",
+  "ordinal": 292,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md b/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
new file mode 100644
index 0000000..9f2a764
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.md
@@ -0,0 +1,9 @@
+# Roles
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html)**
+- **[Role Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html)**
+- **[Roles and Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html)**
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html)**
+- **[Creating Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1AC5F825-20D5-4B28-936A-2DD024250026.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json b/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
new file mode 100644
index 0000000..25b952c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+  "title": "Overview",
+  "ordinal": 255,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md b/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
new file mode 100644
index 0000000..c54c519
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1D5A54E2-B165-47BD-82D6-6FB5002B8B2A.md
@@ -0,0 +1,15 @@
+# Overview
+
+HPE Morpheus Enterprise provides great monitoring features out of the box. Anything provisioned within HPE Morpheus Enterprise automatically gets a check created in the monitoring service. These checks are organized hierarchically in “Groups” and “Apps”. This makes it easy to gain a perspective as to what a customer or full stack facing impact is in the event of a particularly instance failure. This also takes into account redundancy layers when it comes to calculating the applications overall uptime percentage.
+
+HPE Morpheus Enterprise also includes a monitoring integration with ServiceNow.
+
+**Subtopics**  
+
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html)**
+- **[Checks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html)**
+- **[Monitoring Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html)**
+- **[Incidents](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html)**
+- **[Contacts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html)**
+- **[Alert Rules](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json b/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
new file mode 100644
index 0000000..5e27e0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+  "title": "Editing and Deleting from the Self Service Catalog",
+  "ordinal": 143,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html",
+  "topic_cluster": {
+    "clustering_title": "Editing and Deleting from the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E",
+        "clustering_title": "Editing and Deleting from the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md b/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
new file mode 100644
index 0000000..b04dae8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.md
@@ -0,0 +1,3 @@
+# Editing and Deleting from the Self Service Catalog
+
+Once created, Service Catalog items can be edited or deleted from the Catalog Items list view (Library > Blueprints > Catalog Items). Click the pencil icon in the relevant row to edit the Service Catalog item or the trash can icon to delete it. Alternatively, Service Catalog items can be made inactive to remove them as provisioning options rather than deleting them.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json b/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
new file mode 100644
index 0000000..0fa5c2d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+  "title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+  "ordinal": 370,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html",
+  "topic_cluster": {
+    "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E710344-0932-4A51-B605-18AEF716E46F",
+        "clustering_title": "Backing Up and Restoring HPE Morpheus Enterprise Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md b/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
new file mode 100644
index 0000000..a101779
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E710344-0932-4A51-B605-18AEF716E46F.md
@@ -0,0 +1,115 @@
+# Backing Up and Restoring HPE Morpheus Enterprise Appliance
+
+HPE Morpheus Enterprise includes built-in tools for backing up managed Instances as well as the appliance itself. Use this guide to configure a location and schedule for backing up your HPE Morpheus Enterprise appliance. This guide also includes steps for restoring or migrating your appliance from the created backup. The steps are the same whether your appliance is deployed in a single node or distributed architecture.
+
+The built-in HPE Morpheus Enterprise appliance backup functionality backs up the MySql data. In addition to the database, it’s advisable to back up your shared storage (at `/var/opt/morpheus/morpheus-ui`) and the morpheus.rb configuration file.
+
+NOTE
+
+The destination HPE Morpheus Enterprise appliance must be running the same version as that which the backup was taken from.
+
+## Create A Backup Job
+
+### About this task
+
+A Backup Job in HPE Morpheus Enterprise holds the schedule timing and retention count for automated backups. If you already have a Job configured, you can move on to the next section. If currently-existing options do not make sense for your backup needs or if none currently exist, create a new execution schedule. See the execute scheduling section of this documentation for additional information on creating these schedules. To begin a new schedule, use the following steps:
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Click on the “Execute Scheduling” tab
+3. Click + ADD
+4. Enter schedule timing using `cron` notation
+5. Click SAVE
+
+### Results
+
+With the execution schedule created, we can move on to creating the Backup Job itself. A Backup Job includes both the backup retention count and an execution schedule (which we just created).
+
+1. Navigate to Backups > Jobs
+2. Click + ADD
+3. Name the Job, then configure the retention count and select the correct execution schedule
+4. Click SAVE
+
+## Integrate a Bucket or File Share
+
+### About this task
+
+When configuring a HPE Morpheus Enterprise appliance backup, a storage location is selected. If you already have the destination bucket or file share integrated with HPE Morpheus Enterprise, skip to the next section. To integrate a new storage bucket, follow the steps below:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. Click on the Buckets or File Shares tab depending on your chosen storage type
+3. Click + ADD
+4. Select the appropriate bucket or file share type
+5. Complete the required fields and click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Additional guidance on integrating each of the supported bucket and file share types can be found in storage documentation.
+
+## Configuring HPE Morpheus Enterprise Appliance Backup
+
+### About this task
+
+With the groundwork laid in the previous sections, we’re ready to enable and configure HPE Morpheus Enterprise appliance backup.
+
+### Procedure
+
+1. Navigate to Administration > Settings > Backups
+2. Slide the switch labeled “Backup Appliance”
+3. Click SAVE
+
+### Results
+
+On saving this change, a text link labeled “Backup” will be activated which will take you directly to the automatically-generated appliance backup job. Click this link to continue.
+
+1. Click the EDIT button
+2. Enter a name for the appliance backup job if you wish to change it from the default
+3. Select the appropriate storage bucket or file share
+4. Choose a pre-created backup job. If you do not have an existing backup job that fits, a retention count and schedule can be manually created in this modal. If you manually configure retention counts and schedules in addition to associating a Job, the Job values will override any manual settings.
+5. Click SAVE CHANGES
+
+At this point, your appliance will be automatically backed up on the schedule you chose and stored in the selected location. An appliance backup will store backup copies of the appliance MySQL database. Should you need to restore or migrate your database from backup, follow the steps in the next section of this guide.
+
+## Restoring the HPE Morpheus Enterprise Manager from Backup
+
+Begin by ensuring the Morpheus UI service is stopped on the HPE Morpheus Enterprise Manager VM. Connect to the manager over SSH from your workstation **bearing in mind that most commands in this process will require sudo or root access.** Enter the following command:
+
+```
+```
+[root@app-server~] morpheus-ctl stop morpheus-ui
+```
+```
+
+To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file. View it like so:
+
+```
+```
+[root@app-server~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---- this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Make note of the first `morpheus_password` value as indicated above.
+
+Copy the SQL database backup from the backup bucket or file share to the destination Manager VM at path `/tmp/morpheus_backup.sql`. Then, you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The database backup is now replicated on the new Manager VM. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server~] morpheus-ctl start morpheus-ui
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json b/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
new file mode 100644
index 0000000..4aa30ed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+  "title": "Approvals",
+  "ordinal": 77,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html",
+  "topic_cluster": {
+    "clustering_title": "Approvals",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD",
+        "clustering_title": "Approvals"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md b/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
new file mode 100644
index 0000000..d16dd46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.md
@@ -0,0 +1,161 @@
+# Approvals
+
+HPE Morpheus Enterprise and Service Now Approvals
+
+## Overview
+
+Policies can be created for Groups and Clouds to require approvals for actions with the built-in HPE Morpheus Enterprise approvals engine, or via a ServiceNow integration. Approvals can be configured for Provisioning and Lifecycle extensions.
+
+## Configuring Approvals
+
+### About this task
+
+Configuring HPE Morpheus Enterprise for Approvals
+
+To configure HPE Morpheus Enterprise for approvals:
+
+### Procedure
+
+1. Configure Roles for Approval access
+2. Optionally configure a ServiceNow Integration for ServiceNow approvals. 
+
+   - Please note ServiceNow integration is not required for Internal Approvals.
+3. Create approvals policies for: 
+
+   - Internal Approvals
+   - SNOW Approvals
+
+### Configure Roles
+
+Configure User Role access settings in Administration > Roles > (Role) > Operations: Approvals.
+
+- All Users with a Role applied containing Operations: Approvals set to Full will have approval authority, and be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to Read will be able to view Approval requests and history, but will not be able to Approve, Deny or Cancel approval requests.
+- All Users with a Role applied that has Operations: Approvals set to None will not have access to the Operations: Approvals section, and such will not be able to see or act on approval requests.
+- Regardless of Role settings, any instance or app provisioned by any user to a group or cloud with an active Approval policy applied will require approval before the instance or app will provision.
+
+### ServiceNow Approvals
+
+#### About this task
+
+Configure ServiceNow integration for SNOW Approvals
+
+#### Procedure
+
+1. Navigate to Admin > Integrations
+2. Select + NEW INTEGRATION
+3. Select ServiceNow from the Type dropdown in the Integration modal and enter: 
+
+   - Name
+     :   Name of the integration in HPE Morpheus Enterprise
+   - Enabled
+     :   Leave checked to enable the integration.
+   - Host
+     :   URL of the ServiceNow host (ex: <https://ven0000.service-now.com>)
+   - User
+     :   A User in ServiceNow that is able to access the REST interface and create/update/delete incidents, requests, requested items, item options, catalog items, workflows, etc.
+   - Password
+     :   Password for User above
+4. Save Changes
+
+#### Results
+
+HPE Morpheus Enterprise then configures the integration with ServiceNow, syncs ServiceNow workflows which are available when creating approvals policies. (This process can take up to 5 minutes depending on the size of the workflow table in ServiceNow.)
+
+### Create Approval Policies
+
+- Policies applied to a Group are created in Infrastructure > Groups > (group) > Policies tab.
+- Policies applied to a Cloud are created in Infrastructure > Clouds > (cloud) > Policies tab.
+
+#### To create an Approval policy:
+
+##### Procedure
+
+1. Navigate to the Policies tab in the Group or Cloud to which the policy will apply.
+2. Select + ADD POLICY to open the New Policy wizard
+3. Select Provision Approval from the Type dropdown
+4. Add an optional description
+5. Leave Enabled selected for this Policy to be active once saved.
+   :   - Enabled can be deselected to disable to policy.
+6. In the config section, select either Internal Approvals or ServiceNow Approvals: 
+
+   - Internal Approvals
+     :   Approval requests will be managed within HPE Morpheus Enterprise via the Operations: Approvals section.
+   - ServiceNow Approvals
+     :   Approval requests will be managed with ServiceNow (SNOW). Please note a ServiceNow integration (Admin: Integrations) must be configured prior to SNOW Approval policy generation.
+
+         - For ServiceNow Approvals, select the appropriate ServiceNow workflow for this policy. Please note the workflows presented are created in ServiceNow and synced with HPE Morpheus Enterprise .
+7. Add the HPE Morpheus Enterprise Accounts to which this policy will apply, or leave the Accounts field blank to apply to all accounts.
+8. Save
+
+##### Results
+
+Upon saving, a new policy is created in the Group or Cloud Policies tab.
+
+NOTE
+
+SNOW Approvals will take a few moments to save as the policy is generated.
+
+## Managing Approval Requests
+
+Once Instance approval policies are added to a Group or Cloud, any Instance or App provisioned into that Group or Cloud will create an approval request entry in the Operations  >  Approvals section.
+
+NOTE
+
+User Role permission Operations: Approvals  >  FULL is required to manage Approvals.
+
+- To Approve, Deny, or Cancel an internal approval request, select the request and use the Actions dropdown.
+- To Cancel a ServiceNow Approval request, select the request and use the Actions dropdown. ServiceNow approvals are managed in ServiceNow.
+
+NOTE
+
+Instances requiring provisioning approval will have a PENDING status until approved.
+
+Each Approval Request will have:
+
+- Name: A name for the approval in HPE Morpheus Enterprise
+- Monthly Price (Est.): The estimated monthly price of the Instance to be provisioned
+- Request Type: What is being requested, such as Instance approval
+- External Name: For ServiceNow integrations, the name of the approval in the ServiceNow console
+- Type: Internal or ServiceNow
+- Status
+- Date Created
+- Requested By: The HPE Morpheus Enterprise user making the request
+- Actions dropdown (for internal approval requests)
+  :   - Approve
+      - Deny
+      - Cancel
+- Actions dropdown (for ServiceNow requests)
+  :   - Cancel
+
+NOTE
+
+The Approvals list view can be sorted by NAME, REQUEST TYPE, EXTERNAL NAME, DATE CREATED, and REQUESTED BY
+
+### Internal approval requests
+
+#### About this task
+
+To Approve, Deny or Cancel an Internal approval request:
+
+#### Procedure
+
+1. Navigate to Operations  >  Approvals
+2. Select the Name of the Approval request
+3. Select Actions on the far right of the request
+4. Select Approve, Deny, or Cancel from the Actions dropdown
+5. Select OK on the confirmation modal
+
+#### Results
+
+- When an Internal request is approved, the related instance will begin to provision immediately and the request will show approved.
+- When an Internal request is denied, the related instances status will change to Denied and the request will show Rejected in the Approvals section.
+- When an Internal request is canceled, the related related instances status will change to Cancelled and the request will be canceled.
+
+### ServiceNow Approval requests
+
+ServiceNow approval request are managed in ServiceNow. The process of approving or rejecting requests is determined by the ServiceNow Workflow selected when configuring the SNOW Approval policy. These Workflows are configured in ServiceNow.
+
+IMPORTANT
+
+HPE Morpheus Enterprise syncs with ServiceNow every 5 minutes. Once an Approval Request is Approved or Rejected in Service Now, it will take up to 5 minutes for the instance to respond accordingly, and the status for the approval request in the Approvals section in HPE Morpheus Enterprise to update.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json b/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
new file mode 100644
index 0000000..98d1e73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+  "title": "Nutanix Prism Central",
+  "ordinal": 469,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Central",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB",
+        "clustering_title": "Nutanix Prism Central"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md b/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
new file mode 100644
index 0000000..17cb294
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F00D44F-F860-4D11-8C5F-7D93F1E4B9EB.md
@@ -0,0 +1,140 @@
+# Nutanix Prism Central
+
+HPE Morpheus Enterprise offers Nutanix Prism Central Cloud integration support through and official plugin. Adding the plugin to a HPE Morpheus Enterprise appliance adds a new Cloud integration type for Nutanix Prism Central. Download the plugin from the HPE Morpheus Enterprise [Plugin Exchange](https://share.morpheusdata.com/morpheus-nutanix-prism/about) and upload it to the appliance. Plugins are uploaded at Administration > Integrations > Plugins. See HPE Morpheus Enterprise [plugin documentation](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) for more details on adding plugins.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Project scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Creating a Minimal Service Account
+
+Integrating Nutanix Prism Central with HPE Morpheus Enterprise requires the use of a service account which has sufficient privileges to work with all Nutanix contructs that HPE Morpheus Enterprise touches. If possible, it’s recommended to use a service account with full administrator rights. This is because there is currently a bug on the Nutanix side that prevents limited roles from working with backups and snapshots. If you choose to use the minimal role permissions outlined in this section, those features will not work until the bug is resolved.
+
+### Recommended Minimal Service Account
+
+- The user belongs to the built-in “Prism Viewer” role
+- The user must be added to any Projects that need to be surfaced to the integration
+- The user must belong to a custom role with the permissions listed in the expandable section below
+
+#### Required Custom Role Permissions
+
+- Access Console VM
+- Allow Cross Cluster VM Migration
+- Allow VM Power Off
+- Allow VM Power On
+- Allow VM Reboot
+- Allow VM Reset
+- Allow VM Volume Group Connection
+- Clone VM
+- Copy Image Remote
+- Create External Subnet
+- Create Image
+- Create Layer2 Stretch
+- Create Overlay Subnet
+- Create Subnet
+- Create VM
+- Delete External Subnet
+- Delete Image
+- Delete Layer2 Stretch
+- Delete Subnet
+- Delete VM
+- Delete VM Recovery Point
+- Deploy VM Templates
+- Expand VM Disk Size
+- Export VM
+- Mount VM CDROM
+- Restore VM Recovery Point
+- Revert VM
+- Snapshot VM
+- Unmount VM CDROM
+- Update Cluster
+- Update Container Disks
+- Update External Subnet
+- Update Image
+- Update Layer2 Stretch
+- Update Overlay Subnet
+- Update Subnet
+- Update VM
+- Update VM Boot Config
+- Update VM Categories
+- Update VM CPU
+- Update VM Description
+- Update VM Disk List
+- Update VM GPU List
+- Update VM Memory
+- Update VM Memory Overcommit
+- Update VM Name
+- Update VM NGT Config
+- Update VM NIC List
+- Update VM Owner
+- Update VM Power State
+- Update VM Power State Mechanism
+- Update VM Project
+- Update VM Recovery Point
+- View Availability Zone
+- View Category
+- View Cluster
+- View Cluster Networking Capabilities
+- View Container
+- View Container Datastore
+- View Container Stats
+- View Dashboard
+- View External Subnet
+- View Host
+- View Image
+- View Layer2 Stretch
+- View Layer2 Stretch Related Entities
+- View Marketplace Item
+- View Name Category
+- View Network Gateway
+- View Overlay Subnet
+- View Project
+- View Storage Pool
+- View Subnet
+- View Value Category
+- View vCenter Cluster
+- View vCenter Container
+- View vCenter Node
+- View vCenter VM
+- View Virtual Switch
+- View VM
+- View VM Host Affinity Policy
+- View VM Recovery Point
+- View VM Templates
+- View VPC
+- View Vpn Connection
+
+IMPORTANT
+
+Due to a current Nutanix bug, non-administrator service accounts will not be able to utilize backup or snapshot features via HPE Morpheus Enterprise. Users who need these features should integrate using an administrator service account rather than the minimal user described here.
+
+## Adding a Nutanix Prism Central Cloud
+
+Adding Nutanix Prism Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the NPC appliance at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the Nutanix Prism Central plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), NUTANIX PRISM CENTRAL should be selectable as a Cloud type to add. Select it and click NEXT.
+
+![../../../_images/pickType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-75A6B1BB-774A-4E63-B8E7-70CF427BE53C-high.png)
+
+At minimum, it’s required to configure the following to add the new cloud:
+
+- **NAME:** A friendly name for the new NPC Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx:9440>)
+- **USERNAME:** Username for a Nutanix Prism Central service account (see the previous section for recommendations on service account user role configuration)
+- **PASSWORD:** The password for the service account
+- **VMM API VERSION:** Allows the user to select which VMM API versions their environment will support as HPE Morpheus Enterprise cannot auto-detect this and endpoint support differs between versions
+
+You’ll know the API URL and credentials have been entered correctly when the PROJECTS dropdown becomes populated. You may choose to scope Nutanix Prism Central Clouds to a specific project or scope the Cloud to all Projects. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+![../../../_images/configureCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B94510F8-00EB-4108-943D-8029EDB50DCD-high.png)
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json b/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
new file mode 100644
index 0000000..38e0519
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+  "title": "Creating Jobs",
+  "ordinal": 92,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24",
+        "clustering_title": "Creating Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md b/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
new file mode 100644
index 0000000..2f4ae05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F166B04-8BE6-4EF5-82A5-6C981695EC24.md
@@ -0,0 +1,63 @@
+# Creating Jobs
+
+## About this task
+
+NOTE
+
+Jobs require existing Tasks or Workflows. See the appropriate section of HPE Morpheus Enterprise docs for more on creating [Tasks](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#tasks) and [Workflows](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#workflows).
+
+To create a new Job:
+
+## Procedure
+
+1. Navigate to Provisioning > Jobs
+2. Select + ADD
+3. Enter the following 
+
+   - NAME: Name of the Job in HPE Morpheus Enterprise
+   - JOB TYPE: A Task Job will execute a selected Task, a Workflow Job will execute a selected Workflow
+   - ENABLED: When checked, the Job will run as scheduled
+4. Select NEXT
+5. Configure the Job 
+
+   Task Jobs
+   :   TASK: Select target Task. If relevant to the Task, Input fields will be presented
+
+       SCHEDULE:
+       :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions > ExecuteDate And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually) Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+           NOTE
+
+           HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+
+       Workflow Jobs
+       :   WORKFLOW: Select target Workflow. If relevant to the Workflow, Input fields will be presented
+
+           SCHEDULE:
+           :   Manual: Job is not scheduled but can be executed from Provisioning > Jobs and selecting Actions  >  Execute
+
+               Date And Time: Job will be executed at one specific point in time and not again (unless rescheduled or executed manually)
+
+               Schedule: Select a configured Execution Schedule. Execution Schedules are created in Library > Automation > Execute Scheduling
+
+               NOTE
+
+               HPE Morpheus Enterprise provides two default execution schedules, `Daily at Midnight` and `Weekly on Sunday at Midnight`. Any additional schedules were created by a User. Additional schedules can be added in Library > Automation > Execute Scheduling
+
+           INCLUDE POWER STATE: Select All, On, or Off. The default configuration is “All” and indicates the Job will run on all relevant Instances or servers at the proper schedule time. Selecting “On” or “Off” indicates the Job should only run against targets specifically having either an on or off power state
+
+           CONTEXT TYPE: Server or Instance
+
+           CONTEXT SERVER/INSTANCE: Select the Server or Instance you wish to target with the Job
+
+           RUN NOW: When checked, the Job will execute on save regardless of `SCHEDULE` setting.
+6. Select NEXT
+7. Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json b/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
new file mode 100644
index 0000000..8ad19ae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+  "title": "Building Catalog Instances",
+  "ordinal": 140,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C",
+        "clustering_title": "Building Catalog Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md b/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
new file mode 100644
index 0000000..4037309
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.md
@@ -0,0 +1,227 @@
+# Building Catalog Instances
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+An Instance in HPE Morpheus Enterprise is a set of one or more containers or virtual machines that correlate to a single, horizontally-scalable entity or service suite. From the Self Service section, we can pre-configure HPE Morpheus Enterprise Instances and present them to users viewing the Service Catalog Persona for one-click deployment.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Instance. The modal window will appear to configure and add a new catalog Instance.
+
+![../../_images/createInstance1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0D1DD7D2-5438-441D-9D5D-515401798FE8-high.png)
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **ENABLED:** When checked, this catalog item will be available for provisioning
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When marked, this Catalog Item will be available from the provisioning Catalog view
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **ALLOW QUANTITY:** When checked, an additional field is added to the order page allowing users to order multiple copies. If this option is enabled, ensure your configuration supports that flexibility (such as when IP or load balancer details are specified)
+- **MAX QUANTITY:** When the ALLOW QUANTITY configuration is used, an additional MAX QUANTITY configuration is available which sets an upper limit on the quantity that may be executed
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **CONFIG:** Enter, view, or edit Instance config here. Click CONFIGURE to build a base configuration through the HPE Morpheus Enterprise Instance wizard. After configuration through the Instance wizard, you may need to overwrite some static values in the Instance JSON body with calls to custom Input values. This allows your users to easily set the Instance Plan, Group, name, tags, or anything else they may need to control. Dynamic inputs are passed with the following syntax: “<%= customOptions.fieldName %>” where fieldName is the Field Name value set on the Input
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+## Using Forms with Catalog Items
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+Using Forms provides a number of advantages over using Inputs. Once the Form is selected, HPE Morpheus Enterprise helpfully provides a sidebar which contains all variables that can be consumed in the Instance config from the Form:
+
+![../../_images/catalogSidebar.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4820885E-F91A-4F9E-881B-4C5ECEC0F160-high.png)
+
+Many Form Inputs are designed to auto-inject themselves into the Instance config, you can see in the screenshot above that “AUTO INJECT” is checked. For variables that auto-inject, you do not need to override any static configuration with a variable call in order to consume that form value. In most cases, you should leave auto-inject turned on but the option is available to disable it for more advanced situations such as if you wanted to code custom logic into the variable call.
+
+Other types of Form Inputs do not auto-inject and, for these, you must override any static configuration in the Instance config with a variable call. For these situations, HPE Morpheus Enterprise helpfully provides the results of all variables so you can be sure you’re injecting the proper call. Click on the question mark (?) button immediately to the right of the “FORM VARIABLES” header to see a list of available variables and an example resolved variable. Variable tiles may be dragged from the sidebar into the CONFIG text area and a properly-formatted variable call will be inserted.
+
+![../../_images/optionTypeHelp.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF683E2D-8807-45D4-8E2B-B807A250D92B-high.png)
+
+As an example, see the configuration for an Ubuntu server in the expandable section below. You’ll notice in the configuration that a VMware Cloud, a specific Group, a specific Plan, and other static configurations are set. Since the Group, Cloud, Plan and other variables are able to be automatically injected, the user may select a different Group, Cloud, Plan, etc. from the form at provision time. The creator of the Catalog Item does not need to override those static configurations with variable calls.
+
+### Example Catalog Item Config
+
+```
+```
+{  
+  "hostName": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "metadata": "<%=customOptions.targetTags%>",  
+  "backup": {  
+    "backupRepository": 40,  
+    "veeamManagedServer": "",  
+    "jobSchedule": 2,  
+    "createBackup": true,  
+    "jobAction": "new",  
+    "jobRetentionCount": "3",  
+    "providerBackupType": 12,  
+    "target": 37006  
+  },  
+  "instance": {  
+    "userGroup": {  
+      "id": ""  
+    },  
+    "tags": "Forms,Test"  
+  },  
+  "defaultExpandAdvanced": false,  
+  "volumes": [  
+    {  
+      "maxIOPS": null,  
+      "displayOrder": 0,  
+      "unitNumber": "0",  
+      "minStorage": 5368709120,  
+      "configurableIOPS": false,  
+      "uuid": "a6781cc1-31ca-406b-aea0-e33ea1a18b7f",  
+      "controllerMountPoint": "2200223:0:4:0",  
+      "internalId": "[ESXi-DC2-QA-LUN01] Morpheus Ubuntu 22.04 20230307/Morpheus Ubuntu 22.04 20230307.vmdk",  
+      "id": 5255832,  
+      "datastoreId": "autoCluster",  
+      "maxStorage": 26843545600,  
+      "volumeCustomizable": true,  
+      "readonlyName": false,  
+      "controllerId": 2200223,  
+      "externalId": "2000",  
+      "virtualImageId": 1418543,  
+      "vId": 1418543,  
+      "size": 25,  
+      "name": "root",  
+      "planResizable": true,  
+      "rootVolume": true,  
+      "storageType": 1,  
+      "typeId": 1,  
+      "resizeable": true,  
+      "uniqueId": null  
+    }  
+  ],  
+  "type": "ubuntu",  
+  "ports": [  
+    {  
+      "code": "ubuntu.22",  
+      "visible": true,  
+      "internalPort": 22,  
+      "loadBalancePort": null,  
+      "loadBalanceProtocol": null,  
+      "sortOrder": 1,  
+      "name": "SSH",  
+      "id": 7,  
+      "shortName": "ssh",  
+      "externalPort": 22,  
+      "loadBalance": false  
+    }  
+  ],  
+  "version": "22.04",  
+  "hideLock": true,  
+  "cloud": {  
+    "name": "QA VMware",  
+    "id": 26324  
+  },  
+  "layout": {  
+    "code": "vmware-ubuntu-22.04-single",  
+    "id": 2608414  
+  },  
+  "showScale": false,  
+  "environment": "2",  
+  "networkInterfaces": [  
+    {  
+      "ipMode": "",  
+      "primaryInterface": true,  
+      "showNetworkPoolLabel": true,  
+      "showNetworkDhcpLabel": false,  
+      "network": {  
+        "idName": "VLAN0002 - Internal Server",  
+        "pool": {  
+          "name": "10.32.20.0 /22",  
+          "id": 18823  
+        },  
+        "id": "network-173431",  
+        "hasPool": false  
+      },  
+      "networkInterfaceTypeId": 4,  
+      "networkInterfaceTypeIdName": "VMXNET 3"  
+    }  
+  ],  
+  "copies": 1,  
+  "loadBalancer": [],  
+  "name": "${userInitials}-${cloudCode}-${type}-${sequence}",  
+  "storageControllers": [  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 0,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "IDE 0",  
+      "typeId": 2,  
+      "id": 1729031,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "IDE",  
+      "maxDevices": 2,  
+      "displayOrder": 1,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": -1,  
+      "busNumber": "1",  
+      "removable": false,  
+      "name": "IDE 1",  
+      "typeId": 2,  
+      "id": 1729032,  
+      "category": "ide"  
+    },  
+    {  
+      "editable": false,  
+      "typeName": "SCSI LSI Logic Parallel",  
+      "maxDevices": 15,  
+      "displayOrder": 2,  
+      "active": true,  
+      "unitNumber": null,  
+      "reservedUnitNumber": 7,  
+      "busNumber": "0",  
+      "removable": false,  
+      "name": "SCSI 0",  
+      "typeId": 4,  
+      "id": 1729030,  
+      "category": "scsi"  
+    }  
+  ],  
+  "config": {  
+    "poolProviderType": null,  
+    "isVpcSelectable": true,  
+    "smbiosAssetTag": null,  
+    "isEC2": false,  
+    "resourcePoolId": "pool-139625",  
+    "hostId": null,  
+    "createUser": true,  
+    "nestedVirtualization": null,  
+    "vmwareFolderId": "group-v80",  
+    "noAgent": false  
+  },  
+  "plan": {  
+    "code": "vm-8192",  
+    "id": 149  
+  },  
+  "group": {  
+    "name": "All Clouds",  
+    "id": "2"  
+  }  
+}
+```
+```
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json b/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
new file mode 100644
index 0000000..5f2a026
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+  "title": "Nesting Workflows",
+  "ordinal": 119,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html",
+  "topic_cluster": {
+    "clustering_title": "Nesting Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D",
+        "clustering_title": "Nesting Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md b/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
new file mode 100644
index 0000000..6c21ec8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.md
@@ -0,0 +1,9 @@
+# Nesting Workflows
+
+HPE Morpheus Enterprise allows Workflows to be nested for easier Workflow creation when many Workflows are used in an environment which have only slight differences or which are made up of common pieces. Nestable Workflows are created like any other Operational Workflow. Once the Workflow is saved, it can be embedded into a special Task type called “Nested Workflow.” A Nested Workflow-type Task simply references an Operational Workflow which may need to be used within other Workflows. Once Nested Workflow Tasks are created they can be used as part of any new Operational or Provisioning Workflows that are created thereafter (or may be added to existing Workflows too). For more on creating Tasks, see HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#tasks).
+
+NOTE
+
+Results from prior Tasks are still accessed using the same syntax even when a prior Task is embedded in a Nested Workflow. Additional syntax to reference the Nested Workflow Task or the Workflow itself are not needed. See HPE Morpheus Enterprise [Task documentation](https://docs.morpheusdata.com/en/latest/library/automation/automation.html#task-results) for more on chaining Task results.
+
+Nested Workflows Video Demo
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json b/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
new file mode 100644
index 0000000..ca73135
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+  "title": "Contacts",
+  "ordinal": 261,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.html",
+  "topic_cluster": {
+    "clustering_title": "Contacts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-1FE536B8-0BE2-4851-8801-174C49D984F3",
+        "clustering_title": "Contacts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md b/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
new file mode 100644
index 0000000..f313cc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-1FE536B8-0BE2-4851-8801-174C49D984F3.md
@@ -0,0 +1,10 @@
+# Contacts
+
+To configure user notifications, a contact must first be created in Monitoring  >  Contacts. These contacts can be one of a few types:
+
+- **Contact:** Used for either Email or SMS
+- **Web Hook:** Used for posting a notification to a web endpoint or Alert Ops
+- **Slack Hook:** Used for posting notifications to a Slack channel (ex. [https://slack.com/[Slack](https://slack.com/%5BSlack)])
+- **VictorOps:** Provides a web post format consistent with the required notification format for Victor Ops.
+
+Most of these options provide convenient examples and information when configuring the contact. Once they are configured, contacts can freely be used to build Alert Rules.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json b/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
new file mode 100644
index 0000000..d44fd62
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+  "title": "Uploading OS Images Using S3-Compatible Object Storage",
+  "ordinal": 409,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0",
+        "clustering_title": "Uploading OS Images Using S3-Compatible Object Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md b/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
new file mode 100644
index 0000000..57f63ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using S3-Compatible Object Storage
+
+## About this task
+
+S3-compatible object storage (such as MinIO) provides scalable and durable storage for OS images.
+
+## Procedure
+
+1. Configure an S3 storage bucket under Infrastructure > Storage > Buckets.
+2. Provide access credentials with read/write permissions.
+3. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+4. Confirm successful upload and activation.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json b/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
new file mode 100644
index 0000000..5a4e70e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+  "title": "Cloud Resource Tagging with Morpheus",
+  "ordinal": 371,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Resource Tagging with Morpheus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4",
+        "clustering_title": "Cloud Resource Tagging with Morpheus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md b/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
new file mode 100644
index 0000000..132d4d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.md
@@ -0,0 +1,91 @@
+# Cloud Resource Tagging with Morpheus
+
+## Introduction
+
+As organizations scale their cloud environments, they often need to devise methodologies for organizing those resources. Tags consist of key and optional value pairs which make it easier to search for or filter your cloud resources based on categories relevant to the organization. While each public or private cloud handles tagging slightly differently, Morpheus removes that complexity and differentiation by handling tags in a consistent way across clouds. In addition, the Morpheus policy engine gives administrators tools to set up guard rails and ensure cloud resource tagging is handled consistently with each provisioning.
+
+This guide will go through Morpheus tagging features and best practices, as well as include provisioning examples from some of the most commonly integrated clouds.
+
+NOTE
+
+Tag syncing is bi-directional in Morpheus for supported clouds. Tag syncing is currently supported in Amazon, Azure, Google, VMware, and Alibaba Clouds.
+
+## Tagging on Provisioning
+
+In the simplest use case, tags can be entered manually in most provisioning scenarios. For example, on the Configure tab of the Create Instance wizard, the user can expand the Tags section and enter as many Tags as he or she needs to comply with organization practices.
+
+![../../_images/1_manual_tag.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A9D53B5E-99C6-49D9-9F6E-8E1A18C1CFA7-high.png)
+
+Once the resource is deployed, Tags are synced and applied to the provisioned machine in the relevant cloud. Tags are shown on the Instance detail page in Morpheus and can also be confirmed in the cloud console if desired. Tag syncing is also a two-way street in that any tag updates applied within Morpheus or within the cloud console will be reflected everywhere.
+
+NOTE
+
+Tag updates made in the cloud console may take up to five minutes to be reflected in Morpheus UI following the next sync of cloud data.
+
+## Custom Instance Types and Tagging
+
+Manually tagging resources as described in the previous section will work in some cases but many administrators will likely need to pre-seed the provisioning wizards with tagging prompts or build dropdown lists for tag values. This is accomplished in Morpheus through the use of custom Instance Types, Inputs, and Option Lists.
+
+To get started, first create an Option List to hold dropdown or typeahead sets of available key values if needed based on organizational tagging policy. If the tag value field should be manually entered at provision time or if the value field is to be left blank, this step can be skipped. Option Lists are created and stored in the Morpheus Library (Library). They can be populated manually by entering CSV or JSON datasets as shown in the example below. They can also be dynamically populated through Morpheus API or REST calls.
+
+![../../_images/2_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5216C432-43A8-4C56-9D07-4C3D728D757A-high.png)
+
+With the set of possible values defined (if needed), we next create an Input to prompt the user for tag input when provisioning relevant Instance types. Inputs are also housed in the Morpheus Library (Library).
+
+It’s important to note the value entered for the FIELD NAME on the new Input will be set as the tag key. The EXPORT AS TAG box should also be marked. By default, the TYPE value is Text. This is appropriate when the user should be prompted with a free text field at provision time to enter a tag value. To tie this Input to the Option List that was just created (if needed), change the TYPE value to Select List or Typeahead. Typeahead works best for very long lists while Select List is often a better user experience for lists of a more manageable size. Set the Option List we created in the previous step in the OPTION LIST value (if needed).
+
+![../../_images/3_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FC1E55AE-02D8-40CB-9BE5-E0ED9106E1E7-high.png)
+
+At this point, we are ready to add this Input to any custom Instance Types or Layouts. When those Instance Types or Layouts are provisioned, the values input by the user become tags associated with the created cloud resources. By setting the Input on an Instance Type, the tag selection appears when provisioning all associated Layouts. Alternatively, if the Input is set on individual Layouts, it will only appear when those Layouts are provisioned.
+
+Instance Types and Layouts are also stored in the Morpheus Library (Library). By opening up any custom Instance Type, we can add the Input we just created when editing the Instance Type. Additionally, we can drill into associated Layouts and apply the Input to selected Layouts if that’s more appropriate.
+
+![../../_images/4_instance_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3F4F0DA9-5384-489B-AC6F-C33024D7F939-high.png)
+
+Going forward, each time the chosen Instance Type or Layout is provisioned, the user will be prompted to enter relevant tag selections. We can even require the user input these values or govern their inputs through tagging policies which will be discussed in the next section.
+
+## Instituting Tagging Policies
+
+If needed, Morpheus allows cloud resource tagging to be governed through its native policy engine. Like other policies, tag policies are added from Administration > Policies. By creating a new policy and setting the TYPE to Tags, the relevant fields are revealed.
+
+NOTE
+
+Tag policy scanning and enforcement is only currently supported for Azure, Amazon AWS, VMware, and Google Cloud Platform clouds. Additional Clouds may be supported in the future.
+
+With a tag policy, we can choose to enforce the policy on a strict or passive basis by marking or unmarking the STRICT ENFORCEMENT box. Strictly enforced tagging policies will not allow provisioning to proceed in supported clouds if the policy requirements are not met. If we opt to enforce the policy passively, a warning banner will appear on the detail page of any server that does not meet policy requirements. Additionally, existing servers in supported clouds will be scanned and those which do not meet policy requirements will also receive the warning banner.
+
+A tag policy must be given a KEY value. If we define only a KEY value, the policy will look for a tag with that key and any (or no) value. Alternatively, we can select any pre-existing Option List as the VALUE LIST to require the tag contain a value that exists in that list or even enter a specific VALUE.
+
+Finally, like other HPE Morpheus Enterprise policies, we can choose to scope it globally, by group, by cloud, or by user. Primary Tenant administrators can also choose to scope the policy to one or more Subtenants.
+
+![../../_images/5_tag_policy_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B7104343-4BFF-4072-808C-403A0182CD17-high.png)
+
+## Tagging in Action
+
+With the prep work complete, we can take a look at our Inputs in action at provision time. In this example case, several Inputs have been created and applied to one custom Instance Type. The example Instance Type has three associated CentOS Layouts, one for AWS, one for VMware, and one for Azure. Regardless of the selected Layout, users are prompted to fill the same tag fields and our tagging remains consistent regardless of the user who is provisioning a new resource at the time.
+
+## Tagging and AWS
+
+When provisioning my CentOS Instance Type with an Amazon Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/6_aws_provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-45A12345-D313-46FB-9806-C09FB33C0A9B-high.png)
+
+In the AWS web console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to the AWS web console. The opposite is also true.
+
+![../../_images/7_aws_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9164DCFD-602C-4B6B-ADA7-B389FB81215E-high.png)
+
+## Tagging and VMware
+
+When provisioning my CentOS Instance Type with a VMware Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/8_vmware_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-264EA4E8-7CD7-45D2-9CE1-CF46AC2E0598-high.png)
+
+In the VMware console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to VMware. The opposite is also true.
+
+## Tagging and Azure
+
+When provisioning my CentOS Instance Type with an Azure Layout, the tag prompts are shown in the provisioning wizard.
+
+![../../_images/9_azure_tags.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-62F1E8EF-C109-4E41-BAF8-C76B9E31E27F-high.png)
+
+In the Azure console, we can see the same tags are applied. We also have two-way tag sync going forward. When tags are updated in Morpheus, the changed is synced to Azure. The opposite is also true.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json b/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
new file mode 100644
index 0000000..5ea6a44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+  "title": "Resizing Volume",
+  "ordinal": 445,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.html",
+  "topic_cluster": {
+    "clustering_title": "Resizing Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010",
+        "clustering_title": "Resizing Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md b/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
new file mode 100644
index 0000000..a6760b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-21AB08DA-EAEF-46C2-8880-8CBC18BC8010.md
@@ -0,0 +1,12 @@
+# Resizing Volume
+
+## About this task
+
+This procedure allows the user to resize a volume. Volume size can only be increased. A rescan is required on the server OS to see the increased size.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Resize for the volume to be deleted.
+3. Specify the new size and click Resize.   
+   ![Resize volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9E3B3BDC-4EE0-491F-B1FC-BDFF31E19553-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json b/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
new file mode 100644
index 0000000..8cdd6f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+  "title": "Specifying Network Usage",
+  "ordinal": 436,
+  "parent_title": "Network Usage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html",
+  "topic_cluster": {
+    "clustering_title": "Specifying Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-21F2F208-7360-4468-B1FF-524CA30CB993",
+        "clustering_title": "Specifying Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md b/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
new file mode 100644
index 0000000..2feeaf3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-21F2F208-7360-4468-B1FF-524CA30CB993.md
@@ -0,0 +1,21 @@
+# Specifying Network Usage
+
+## About this task
+
+Perform the following to specify networks used during instance provisioning:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Provisioning > Instances.
+3. Select **HPE**Bare Metal (ILO) Server as the type.
+4. Click Next.
+5. Specify a Group, Cloud, and a Name for the Instance.
+6. Click Next.
+7. Select a Network.
+8. Select an interface type (Bond/Physical).
+9. Specify any required virtual interface.
+10. Click Next and complete. ![Instance Bond Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5359D1DC-7863-49EC-9F61-4C14BFC8F0F1-high.png)
+
+    For physical interfaces, the interfaces represent the physical ports in their display order. Virtual networks specify that tagged networks under the primary network specified are to be configured on the server OS with an IP interface. If any of those tagged networks are not required to be configured on the server OS as an IP interface, do not specify a virtual interface for those.   
+    ![InstancePhysicalNetwork](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CA592D7B-4562-4AA1-8A46-BF66F13DC305-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.json b/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.json
new file mode 100644
index 0000000..4a56364
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+  "title": "Dashboard",
+  "ordinal": 54,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2277183A-E315-4439-A885-C111A77C7154.html",
+  "topic_cluster": {
+    "clustering_title": "Dashboard",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2277183A-E315-4439-A885-C111A77C7154",
+        "clustering_title": "Dashboard"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.md b/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.md
new file mode 100644
index 0000000..3378349
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2277183A-E315-4439-A885-C111A77C7154.md
@@ -0,0 +1,80 @@
+# Dashboard
+
+The Dashboard is a single, high-level view into your environment which includes easy-to-read performance and configuration information. In many cases other areas within HPE Morpheus Enterprise UI will allow you to drill deeper into the information presented in the dashboard.
+
+![dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EED20D75-2987-4570-A0F2-5AD920F49D1D-high.png)
+
+NOTE
+
+Opensearch 7.16+ is required for the Log Trends Dashboard panel to work. When using versions below 7.16 you will see error messages in logs due to this panel missing needed dependencies to work correctly but these errors may be safely ignored.
+
+## Environment
+
+- **Groups:** Total number of Groups currently created
+- **Clouds:** Total number of Clouds currently integrated
+- **Clusters:** Total number of clusters currently provisioned
+- **Apps:** Total number of Apps currently provisioned
+- **Instances:** Total number of Instances currently provisioned
+- **Users:** Total number of HPE Morpheus Enterprise user accounts
+
+## System Status
+
+System status gives a high-level view of the health of the appliance. More detailed information can be viewed on the appliance health detail page (Administration > Health) and a more detailed breakdown of the meaning of each status indicator is in [HPE Morpheus Enterprise Health](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html#GUID-E6FCD7DB-6973-459F-9EBC-3088B211CF1C).
+
+## Favorites
+
+Any Instances you’ve “favorited” will appear here along with the Instance name, type, and IP address
+
+## Alarms
+
+The most recent five Alarms are displayed here and the user may link through to the resource which triggered the Alarm. For the complete list of Alarms and more information on each Alarm navigate to Operations > Activity > Alarms
+
+## Instance Status
+
+The total number of Instances is listed along with a pie chart showing the statuses of each. Hover over each section of the pie chart to see the total number and percentage of Instances in that state. States may include running, stopped, provisioning, and more
+
+## Instances By Cloud
+
+The total number of Clouds which currently have an Instance provisioned is shown. Hover over each section of the pie chart to see the total number and percentage of Instances provisioned to each Cloud
+
+## Daily Cloud Instances
+
+The number of Instances that have existed at any point in the day with additional breakdown to show the number provisioned to each Cloud. This number will include any pre-existing Instances which have carried over from previous days along with any new Instances that were provisioned and existed on that day even for a short time
+
+## Group Workloads
+
+The instantaneous count of host or container records broken down by Group association
+
+## Cloud Workloads
+
+The instantaneous count of host or container records broken down by Cloud association
+
+## Cluster Workloads
+
+The instantaneous count of managed containers broken down by Cluster association
+
+![../_images/dashboard2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1B7CFE86-1657-4EF7-B515-E3D104CDB5D2-high.png)
+
+## Log History
+
+Log History shows a snapshot of various time segments throughout the current day and the number of logs generated during each segment. Hover over any bar on the graph to see a breakdown in severity of the logs within each segment
+
+## Log Trends
+
+Log Trends identifies and lists repeated messages found in recent longs. If desired, this view can be filtered to show only Error or Warning-level log messages
+
+## Job Executions
+
+Displays the number of successful and unsuccessful Job executions over the last day, week or month
+
+## Backups
+
+Displays the number of successful and unsuccessful backups over the last day, week or month
+
+## Task Executions
+
+Displays the number of successful and unsuccessful Task executions over the last day, week or month
+
+## Activity
+
+The activity list displays the last few events that have taken place in HPE Morpheus Enterprise by any user. This could be new provisioned workloads, deleted workloads, backups, or a number of other things. A more complete list of recent activities can be viewed in Operations > Activity
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json b/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
new file mode 100644
index 0000000..2878fb1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+  "title": "SCVMM",
+  "ordinal": 470,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.html",
+  "topic_cluster": {
+    "clustering_title": "SCVMM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E",
+        "clustering_title": "SCVMM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md b/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
new file mode 100644
index 0000000..dd30a9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-22EEEC8A-E264-4D1B-9D76-E543DFD3096E.md
@@ -0,0 +1,240 @@
+# SCVMM
+
+NOTE
+
+HPE Morpheus Enterprise supports SCVMM cloud deployment as HA SCVMM failover cluster. You must follow the process to have a singular agent API key and only one agent online at a time.
+
+## Requirements
+
+- Access to SCVMM host on port 5985 for Agent installation
+- Access to Hyper-V host on port 2179 for hypervisor console access
+- HPE Morpheus Enterprise Agent installation (installed on the target SCVMM host via port 5985 and WinRM)
+- User with administrator privileges
+
+## Agent Requirement
+
+SCVMM and Hyper-V integrations utilize the HPE Morpheus Enterprise Agent for communication with the HPE Morpheus Enterprise appliance, making the HPE Morpheus Enterprise Agent required. This also means SCVMM and Hyper-V Clouds can only point to one HPE Morpheus Enterprise Appliance at any given time. If another HPE Morpheus Enterprise Appliance adds an SCVMM or Hyper-V Cloud thats is already managed by another HPE Morpheus Enterprise Appliance, the HPE Morpheus Enterprise Agent appliance\_url will be updated to point to the new HPE Morpheus Enterprise appliance\_url, and the previous HPE Morpheus Enterprise Appliance will no longer be able to communicate with the SCVMM Cloud or Hyper-V Cloud until the Agent configuration is updated to point to the previous appliance again. In HPE Morpheus Enterprise version 4.2.1 and higher, multiple HPE Morpheus Enterprise clouds can be created by integrating with the same SCVMM host. This allows users to create separate Clouds with are scoped to different SCVMM Cloud, Host and/or Cluster combinations.
+
+## Add a SCVMM Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select SCVMM, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   NOTE
+
+   You will need to open port 5985 in order for HPE Morpheus Enterprise to communicate to SCVMM. You will also want to make sure the SCVMM Controller has WinRM enabled.
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   SCVMM HOST
+   :   IP address or URL of SCVMM host server
+
+   USERNAME
+   :   SCVMM Username, for example: svc.scvmm
+
+   PASSWORD
+   :   SCVMM user Password
+
+   CLOUD
+   :   To scope the SCVMM Integration to a single Cloud, select it from the Cloud dropdown, which populates after establishing communication and authorization over port 5985 using the supplied username and password. To scope to all Clouds, leave the dropdown selection as `Select Cloud`
+
+   HOST GROUP
+   :   To scope the SCVMM Integration to a single host group, select a host group from the dropdown list. To scope to all host groups, select `All Hosts`
+
+   CLUSTER
+   :   To scope the SCVMM Integration to a single cluster, select a cluster from the dropdown list. To scope to all host groups, select `All`
+
+   LIBRARY SHARE
+   :   Select a Library Share to be used with the cloud integration
+
+   SHARED CONTROLLER
+   :   When creating additional HPE Morpheus Enterprise clouds that point to an SCVMM host already integrated with this appliance, select the appropriate shared controller value from the dropdown.
+
+       IMPORTANT
+
+       Only set `SHARED CONTROLLER` on additional HPE Morpheus Enterprise clouds and not on the Primary HPE Morpheus Enterprise SCVMM cloud. Failure to set the `SHARED CONTROLLER` on secondary HPE Morpheus Enterprise clouds pointed to the same SCVMM cluster will cause agent comm issues resulting in provisioning failures.
+
+       WORKING PATH
+       :   Path for HPE Morpheus Enterprise to write to, for example `c:\cloud`
+
+       DISK PATH
+       :   Path for Virtual Disks, for example `c:\virtualdisks`
+
+       HIDE HOST SELECTION FROM USERS
+       :   Prevents host selection from appearing in provisioning wizards
+
+       INVENTORY EXISTING INSTANCES
+       :   Enable for HPE Morpheus Enterprise to automatically discover existing VMs in the scoped resources
+
+       ENABLE HYPERVISOR CONSOLE
+       :   Enable to use VNC Hypervisor Console for HPE Morpheus Enterprise console connection as opposed to the default SSH and RDP console connection methods. Requires resolution of all Hyper-V host names and access over port 2179 from the HPE Morpheus Enterprise appliance to Hyper-V hosts.
+
+       SCVMM Specific Advanced Options
+
+       INSTALL AGENT
+       :   Enabled by default, INSTALL AGENT installs the HPE Morpheus Enterprise agent on the scvmm Controller when adding the cloud, which is required for full functionally unless using a shared controller in which scenario the agent would already be installed on the scvmm controller node. Disabling INSTALL AGENT on the cloud config when not using a shared controller will remove the ability to provision to the cloud.
+
+       Advanced Options
+
+       DOMAIN
+       :   Specify a default domain for instances provisioned to this Cloud.
+
+       SCALE PRIORITY
+       :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+       APPLIANCE URL
+       :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+       TIME ZONE
+       :   Configures the time zone on provisioned VM’s if necessary.
+
+       DATACENTER ID
+       :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+       NETWORK MODE
+       :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+       LOCAL FIREWALL
+       :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+       SECURITY SERVER
+       :   Security Server setting is for Security Service Integrations such as ACI
+
+       TRUST PROVIDER
+       :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+       STORAGE MODE
+       :   Single Disk, LVM or Clustered
+
+       BACKUP PROVIDER
+       :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+       REPLICATION PROVIDER
+       :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+       GUIDANCE
+       :   Enable Guidance recommendations on cloud resources.
+
+       COSTING
+       :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+       DNS INTEGRATION
+       :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+       SERVICE REGISTRY
+       :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+       CONFIG MANAGEMENT
+       :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+       CMDB
+       :   Select CMDB Integration to automatically update selected CMDB.
+
+       CMDB DISCOVERY
+       :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+       CHANGE MANAGEMENT
+       :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+       AGENT INSTALL MODE
+       :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+           - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+       VDI GATEWAY
+       :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+       CUSTOM LOGOS
+
+       When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+       INVENTORY OPTIONS
+
+       Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+       - Service Plans
+       - Resource Pools
+       - Networks
+       - Security Groups
+       - Datastores
+       - Folders
+
+       Provisioning Command
+
+       PROXY
+       :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+       Bypass Proxy for Appliance URL
+       :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+       NO PROXY
+       :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+       USER DATA (LINUX)
+       :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After clicking NEXT, the new Cloud can be added to a Group or configured with additional advanced options.
+
+### Create Ubuntu 22.04 image template
+
+Use the template creation steps detailed in the below article:
+
+https://support.hpe.com/hpesc/public/docDisplay?docId=sd00006774en\_us&page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD\_2.html#ariaid-title1
+
+with the exceptions as below:
+
+1. Enable required VM integration services before deploying the VM
+
+- Naviagate to "Hardware Configuration" -> "Advanced" -> "Integration Services". Check the checkbox "Guest services" under "Services".
+
+2. After the the step titled "Complete the installation process and reboot the machine. Update the package list and apply any upgrades", execute the below (to install a collection of utilities for hypervisor integration) :
+
+```
+```
+sudo apt install -y linux-cloud-tools-$(uname -r) linux-tools-$(uname -r)
+```
+```
+
+Follow the subsequent steps as in the article.
+
+**Create windows template**
+
+Create a new machine in SCVMM and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+**Procedure**
+
+- Apply any service packs / updates to the operating system.
+- Install .Net at least 4.5.2
+- Install SCVMM Agent
+- Ensure Windows Firewall will allow WinRM connections.
+- Shutdown the virtual machine and convert to a template.
+
+  Note : Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json b/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
new file mode 100644
index 0000000..fa412c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+  "title": "Repositories",
+  "ordinal": 97,
+  "parent_title": "Code",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html",
+  "topic_cluster": {
+    "clustering_title": "Repositories",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B",
+        "clustering_title": "Repositories"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md b/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
new file mode 100644
index 0000000..5816d96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.md
@@ -0,0 +1,128 @@
+# Repositories
+
+The Provisioning ‣ Code ‣ Repositories section contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repository folders and files, view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. This section also handles Import/Export functionality which allows users to backup HPE Morpheus Enterprise items (Tasks, Library Items, etc.) as code in a repository which can also be imported into another appliance, if desired.
+
+- Browse integrated repositories
+- View repo files
+- Switch branches
+- Trigger repo refreshes
+- Filter by Integration, Organization or Text search
+- Create Custom Views
+- Create Tasks from repo files
+- Create Spec Templates from repo files
+
+## Role Permissions
+
+Access and capabilities for the **Repositories** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Administration: Users`
+:   - None: Can view repo list but cannot browse repo folder and file names, select branch, refresh repositories or access/view file contents
+    - Read or Full: Can view repo list, browse repo folder and file names, select branch, refresh repositories. Cannot access/view file contents without Read or Full level permission on `Provisioning: Code Repositories`
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents
+
+Role: Feature Access: `Provisioning: Tasks`
+:   - None: Cannot create Tasks from repo files in repository browser
+    - Read or Full: Can create Tasks from repo files in repository browser
+
+Role: Feature Access: `Provisioning: Library`
+:   - None: Cannot create Spec Templates from files in repository browser
+    - Read or Full: Can create Spec Templates from files in repository browser
+
+## List Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Users with sufficient permissions will see a list view of all integrated code repositories
+4. Use the Search, Integrations or Organizations filter to filter listed repositories
+
+### Results
+
+TIP
+
+Select the gear icon ⚙ in the top right of the repos list view to create and save custom list views.
+
+## Refresh Repository
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ACTIONS ▿ > `Refresh`
+
+## Browse Repositories
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Users with sufficient permissions can browse repo folder and file names, select branches, and refresh repositories. Users can access/view file contents with Read or Full level permission on `Provisioning: Code Repositories`
+5. Select target folder icon to drill into the folder
+
+## View Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select ℹ icon to right of target file name
+
+### Results
+
+NOTE
+
+Users can access/view file contents only with Read or Full level permission on `Provisioning: Code Repositories`. File contents displayed is from last repo sync. Refresh repo to ensure current version for recent commits.
+
+## Create Task from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of compatible target file name
+5. Select target task type from available actions
+6. Complete the NEW TASK wizard to create a new Task. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Shell and Powershell Tasks types can be created from the code repo browser in v8.0.7. Ensure file compatibility with target Task type.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Tasks`.
+
+## Create Spec Template from Repository File
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar
+2. Select the `Code` link in the sub-navigation bar
+3. Select name of target repository
+4. Select gear icon to right of target file name
+5. Select target spec template type from available actions
+6. Complete the NEW SPEC TEMPLATE wizard to create a new Spec Template. The TYPE, SOURCE, REPOSITORY and FILE PATH fields will be automatically configured
+
+### Results
+
+NOTE
+
+Terraform spec template types can be created from the code repo browser in v8.0.7. Other spec template types can be created from repo files by changing the TYPE field in the NEW SPEC TEMPLATE wizard.
+
+NOTE
+
+Users can create tasks from Repositories only with Read or Full level permission on `Library: Templates`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json b/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
new file mode 100644
index 0000000..74b28dc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+  "title": "Cypher",
+  "ordinal": 264,
+  "parent_title": "Tools",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html",
+  "topic_cluster": {
+    "clustering_title": "Cypher",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A",
+        "clustering_title": "Cypher"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md b/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
new file mode 100644
index 0000000..7fbcf01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.md
@@ -0,0 +1,199 @@
+# Cypher
+
+## Overview
+
+Cypher at its core is a secure Key/Value store. But what makes cypher useful is the ability to securely store or generate credentials to connect to your instances. Not only are these credentials encrypted but by using a cypher you don’t have to burn in connection credentials between instances into your apps.
+
+Cypher keys can be revoked, either through lease timeouts or manually. So even if somebody were to gain access to your keys you could revoke access to the keys and generate new ones for your applications.
+
+Keys can have different behaviors depending on the specified mountpoint.
+
+## Mountpoints
+
+password
+:   Generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+tfvars
+:   This is a module to store a tfvars file for terraform app blueprints.
+
+secret
+:   This is the standard secret module that stores a key/value in encrypted form.
+
+uuid
+:   Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+key
+:   Generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key)
+
+vault
+:   Configures an integration between HPE Morpheus Enterprise and a Hashicorp Vault server. See below for additional configuration instructions.
+
+    - Key lease times are entered in seconds and default to 32 days (2764800 s).
+
+      - Quick Time Reference:
+      - Day: 86400
+      - Week: 604800
+      - Month (30 days): 2592000
+      - Year: 31536000
+
+## Creating Cypher Keys
+
+### Procedure
+
+1. Navigate to Tools > Cypher and select + ADD
+2. Configure one of the following types of Keys:
+
+## Password
+
+A Cypher password generates a secure password of specified character length in the key pattern (or 15) with symbols, numbers, upper case, and lower case letters (i.e. password/15/mypass generates a 15 character password).
+
+Key
+:   Pattern “password/character\_length/key”
+
+    Example: password/10/mypassword
+
+Value
+:   Leave the Value filed blank for a password, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the password will be generated and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generated password.
+
+To delete the password key, select Actions  >  Remove and confirm.
+
+## tfvars
+
+A mountpoint to store tfvars files for Terraform App Blueprints.
+
+Key
+:   Pattern “tfvars/key”
+
+    Example: tfvars/my-aws-account
+
+Value
+:   The values for your tfvars file to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES and the stored values will be available for use.
+
+NOTE
+
+You may also see Cloud profiles stored at the tfvars mountpoint. They will have a key pattern like: “tfvars/profile/cloud/$cloudCode/variables”. Terraform Cloud profiles are created on the Cloud detail page (Infrastructure > Clouds > selected Cloud) under the Profiles tab. They allow Terraform apps and specs to be provisioned across multiple Clouds that require differed tfvars. See the [Cloud profiles](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/profiles.html) page for more.
+
+## Secret
+
+A Cypher secret is the standard secret module that stores a key/value in encrypted form.
+
+Key
+:   Pattern “secret/key”
+
+    - EXAMPLE: secret/mysecret
+
+Value
+:   Add the secret value to be encrypted
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the secret will be encrypted and available for use.
+
+If your HPE Morpheus Enterprise user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the secret.
+
+To delete the secret, select Actions  >  Remove and confirm.
+
+## UUID
+
+A Cypher UUID Returns a new UUID by key name when requested and stores the generated UUID by key name for a given lease timeout period.
+
+Key
+:   Pattern “uuid/key”
+
+    - Example: uuid/myuuid
+
+Value
+:   Leave the Value filed blank for UUID, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the UUID will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate UUID.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Key
+
+A Cypher Key generates a Base 64 encoded AES Key of specified bit length in the key pattern (i.e. key/128/mykey generates a 128-bit key).
+
+Key
+:   Pattern “key/bit\_length/key”
+
+    - Example: key/256/mykey
+
+Value
+:   Leave the Value filed blank for key, as it will be generated.
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Save changes and the AES Key will be generate and available for use.
+
+If your user role has Cypher: Decrypt permissions, a “DECRYPT” button will be available in the Cypher section to view the generate AES Key.
+
+To delete the UUID, select Actions  >  Remove and confirm.
+
+## Vault
+
+Use this mountpoint to store Cypher secrets in a Hashicorp Vault server backend rather than HPE Morpheus Enterprise. Additionally, you can call secrets stored in Vault from this Cypher mountpoint even if they are only saved there and not listed in the HPE Morpheus Enterprise Cypher UI. This requires installation and configuration of the Hashicorp Vault plugin. See the YouTube video embedded in this section for more information on adding the plugin, configuration, and a demonstration of its capabilities.
+
+NOTE
+
+It’s recommended that you use a long-lived token as attempts to call Vault-stored values into Tasks will stop working if the token is no longer good. In such a case you’d have to obtain a new token, delete the Cypher entry with the old token, and create a new one to restore functionality once again. Using a long-lived token will prevent the need to do this often.
+
+Key
+:   Pattern “vault/<engineMount>/<secretPath>/data/<key>” (ex. vault/KV2/secret/data/morpheus/lab)
+
+Value
+:   Enter your key/value pair here in valid JSON (ex. {“hello”: “world”} )
+
+Lease
+:   Enter lease time in seconds (ex. 604800 for one week)
+
+Click SAVE CHANGES. The example BASH script below onboards the value stored in Vault from the secret/data/morpheus/lab mountpoint:
+
+```
+```
+from_vault="<%= cypher.read('vault/KV2/secret/data/morpheus/lab') %>"  
+echo $from_vault
+```
+```
+
+## Editing Cypher Keys
+
+Cypher key types which accept user-entered values (not generated values) are editable. To edit, click the “ACTIONS” button at the end of the row for the appropriate Cypher key and then click “Edit.” Edit the values and click SAVE CHANGES.
+
+## Using Cypher Keys in Scripts
+
+To use a Cypher key in a script, use the following syntax:
+
+`<%=cypher.read('var_name')%>`
+
+Example: `PASSWORD=<%=cypher.read('secret/myuserpassword')%>`
+
+Cypher also includes an option to read a value from the `password/*` mountpoint or create one if it doesn’t already exist. Use the following syntax:
+
+`<%=cypher.readPassword('var_name')%>`
+
+Example: `` PASSWORD=<%=cypher.readPassword('myuserpassword')%>` ``
+
+It should be noted that when Cypher keys are created using the `readPassword` function, the subsequent reads can only come from the same user. If another HPE Morpheus Enterprise user attempts to run the automation script containing the `readPassword` call, the secret value will not be read and it’s very likely the script will fail. For Tasks and Workflows that need to be run by multiple users, use a pre-existing Cypher key and reference it back in the script using `read` rather than `readPassword`.
+
+NOTE
+
+You can reference the original owner of a workflow so that keys can be used in a subtenant. Example `PASSWORD=<%=cypher.read('secret/myuserpassword')%>` could be changed to `PASSWORD=<%=cypher.read('secret/myuserpassword',true)%>` within a library or a workflow and the true means OWNER true. This will keep that key in the master tenants cypher store.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json b/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
new file mode 100644
index 0000000..423e699
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+  "title": "Add NSX advanced load balancer",
+  "ordinal": 503,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX advanced load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-269D2944-5080-4897-86F5-AC949F4B83F1",
+        "clustering_title": "Add NSX advanced load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md b/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
new file mode 100644
index 0000000..79eaa77
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-269D2944-5080-4897-86F5-AC949F4B83F1.md
@@ -0,0 +1,34 @@
+# Add NSX advanced load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX Advanced Load Balancer**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX adv LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0257709D-4A5C-441C-9E7B-C5793572100E-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   API HOST \*
+   :   Enter the API host name.
+
+   API PORT \*
+   :   Enter the PORT number.
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter NSX service account username.
+   :   **PASSWORD \***: Enter NSX service account password.
+
+   AVI CLOUD
+   :   From the drop-down list, select the AVI cloud (VMware Avi Load Balancer).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json b/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
new file mode 100644
index 0000000..3e42428
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+  "title": "Delete Workflow",
+  "ordinal": 121,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html",
+  "topic_cluster": {
+    "clustering_title": "Delete Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C",
+        "clustering_title": "Delete Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md b/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
new file mode 100644
index 0000000..2b5e366
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.md
@@ -0,0 +1,8 @@
+# Delete Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Delete icon on the row of the workflow you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json b/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
new file mode 100644
index 0000000..7f40568
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+  "title": "Canonical MAAS",
+  "ordinal": 461,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.html",
+  "topic_cluster": {
+    "clustering_title": "Canonical MAAS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8",
+        "clustering_title": "Canonical MAAS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md b/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
new file mode 100644
index 0000000..01ffa08
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-27706317-FA6C-49E6-8D44-FAE2E35217F8.md
@@ -0,0 +1,42 @@
+# Canonical MAAS
+
+MAAS from Canonical is an open-source server orchestration tool. It’s designed to allow administrators to build a datacenter from on-premises, bare-metal servers where large networks of individual units can be discovered, deployed, and reconfigured.
+
+## Integrating MAAS and HPE Morpheus Enterprise
+
+### About this task
+
+Integrating MAAS with HPE Morpheus Enterprise is a simple process requiring the MAAS API URL and API Key. We’ll start by gathering what we need from the MAAS UI, then move back into HPE Morpheus Enterprise to store the required details.
+
+We can gather the API key by clicking on the username in the upper-right corner of the MAAS UI window. From this preferences page, click on “API keys” as shown in the screenshot:
+
+![../../../_images/1prefPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2CE6F9DA-2A53-497D-B397-89CE446156D7-high.png)
+
+From the API keys page, select the displayed key and copy it. Alternatively, you can click the copy button in the UI to add the full key to your clipboard. Store this key in an accessible location for a later step.
+
+![../../../_images/2maasApi.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C7F62A15-E82D-479B-9D76-2A83365CD918-high.png)
+
+In addition to the API key, we need the MAAS API URL. As entered in HPE Morpheus Enterprise, the value will be like the following example: `http://<maas-hostname-or-ip>:5240`. We’ll enter the API URL into HPE Morpheus Enterprise duriong the next step.
+
+In HPE Morpheus Enterprise, navigate to the list of integrated Clouds and start a new MAAS Cloud integration:
+
+### Procedure
+
+1. Infrastructure > Clouds
+2. Click + ADD
+3. Select “MAAS”
+4. Click NEXT
+
+### Results
+
+On the “CREATE CLOUD” modal, you must at least give a friendly name for the Cloud in HPE Morpheus Enterprise, MAAS API URL and API KEY. An example is shown below:
+
+![../../../_images/3createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AA9E6041-8181-4D62-8EC4-516C7234E0FF-high.png)
+
+TIP
+
+You’ll know the credentials are entered correctly when your list of MAAS resource pools is synced in as you can see in the example screenshot.
+
+Click NEXT and add this new Cloud to an existing Group or create a new Group for it. Once you advanced past the end of the wizard, the Cloud is added and HPE Morpheus Enterprise begins to inventory (if you’ve opted to inventory when adding the Cloud).
+
+![../../../_images/4cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-598C2A66-38D0-4401-B1C5-14CF91A97474-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json b/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
new file mode 100644
index 0000000..0ba7d89
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+  "title": "Active Directory",
+  "ordinal": 282,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html",
+  "topic_cluster": {
+    "clustering_title": "Active Directory",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6",
+        "clustering_title": "Active Directory"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md b/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
new file mode 100644
index 0000000..a117d46
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.md
@@ -0,0 +1,130 @@
+# Active Directory
+
+## Overview
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+## How It Works
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+## Example Integration
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in-built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+## Adding an Active Directory Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following: 
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non-secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES. 
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Troubleshooting
+
+### About this task
+
+If you’re unable to get the Active Directory integration to work, the following troubleshooting steps may be useful to ensure your appliance can talk to the Active Directory server.
+
+### Procedure
+
+1. Open firewall ports 
+
+   Source: HPE Morpheus Enterprise appliance Destination: AD server’s FQDN or IP address Non-SSL AD integration: TCP-389 SSL AD integration: TCP-636
+2. Checking open LDAP connections from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following:
+
+   ```
+   ```
+   $ sudo lsof i- | grep :ldap
+   ```
+   ```
+3. Check LDAP connectivity from the HPE Morpheus Enterprise appliance 
+
+   Connect to a HPE Morpheus Enterprise appliance box and run the following. Be sure to replace the placeholder values in the command with the correct values for your environment:
+
+   ```
+   ```
+   $ ldapsearch   -x -h xx.xx.xx.xx -D "binding-user@acme.com" -W -b "cn=users,dc=acme,dc=com"
+   ```
+   ```
+4. Run tcpflow from the HPE Morpheus Enterprise appliance for non-SSL enabled AD identity Integrations 
+
+   Use tcpflow from the HPE Morpheus Enterprise appliance and then start the identity source configuration once again. Keep in mind this will only work for AD servers which are not SSL enabled:
+
+   ```
+   ```
+   $ sudo tcpflow -i any -c -v port 389
+   ```
+   ```
+5. Check the AD and domain controllers event logs 
+
+   Check the event logs for LDAP queries from the HPE Morpheus Enterprise appliance to ensure network connectivity.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json b/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
new file mode 100644
index 0000000..9d77a78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+  "title": "Tools",
+  "ordinal": 263,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html",
+  "topic_cluster": {
+    "clustering_title": "Tools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A",
+        "clustering_title": "Tools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md b/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
new file mode 100644
index 0000000..a0ccc3c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.md
@@ -0,0 +1,9 @@
+# Tools
+
+**Subtopics**  
+
+- **[Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html)**
+- **[Archives](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html)**
+- **[Image Builder](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html)**
+- **[Migrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html)**
+- **[VDI Pools](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json b/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
new file mode 100644
index 0000000..f42ff7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+  "title": "Email Templates",
+  "ordinal": 324,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.html",
+  "topic_cluster": {
+    "clustering_title": "Email Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-29661D5A-2426-4114-B839-1242C7A7D6A8",
+        "clustering_title": "Email Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md b/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
new file mode 100644
index 0000000..83f9087
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-29661D5A-2426-4114-B839-1242C7A7D6A8.md
@@ -0,0 +1,50 @@
+# Email Templates
+
+## Email Templates
+
+HPE Morpheus Enterprise sends out email to its users periodically to alert for various conditions such as an Instance provisioning success, warnings about upcoming Instance expiration, requests for password reset links, and more. HPE Morpheus Enterprise includes system-default email templates for all of these emailed conditions but allows users to create their own email templates to override the default template.
+
+On accessing the Email Templates tab, users will see a list of all email templates that currently exist. We can also see the owner which created the template as well as the associated Account (Tenant). System-default templates are shown as being owned by “System” and show no associated Account (Tenant). When a Master Tenant user creates a template, the option is given to tie the template to an Account or to make a global template. The Accounts column will show “Global” for global templates. Templates will apply in order of specificity: Tenant-specific templates apply first, then custom global templates, and finally system templates if no others exist for that email type.
+
+IMPORTANT
+
+Email templates apply in order of specificity. Tenant-specific templates apply over custom global templates which apply over system-default templates.
+
+![../../_images/emailTemplateList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-278D8A99-12B8-47EE-8FC8-F360DDA69C70-high.png)
+
+### Creating Templates
+
+Before creating the first template, it’s important to realize email from custom templates will still come wrapped in the standard HPE Morpheus Enterprise email headers and footers. It will also have included styling. This styling comes directly from your Tenant whitelabel configuration and will include HPE Morpheus Enterprise standard styling or your custom whitelabel styling depending on appliance configuration. The template itself should only include email body content which will be inserted within the styling wrapper.
+
+IMPORTANT
+
+It is possible to break the functionality of certain types of generated email by creating a custom template. For example, in a password reset email, you must ensure the password reset button is still included with the template. Other functionality-breaking scenarios may also be possible. Review the system-default template of any email type to copy syntax examples for such vital components.
+
+Some template types will have variables accessible, such as the logged in user’s name (to address the email) or an Instance name. To see the available variables, click on the info button for the system-default template of the type you wish to create. You’ll see the variables mentioned in a comment at the bottom of the template such as in this example Confirm Password Update Template:
+
+```
+```
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.greeting"}}}</p>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.message"}}}</p>  
+<a href={{{url}}}>{{{i18n "com.bertramlabs.plugins.accounts.password.email.linkLabel"}}}</a>  
+<p>{{{i18n "com.bertramlabs.plugins.accounts.password.email.signature"}}} </p>  
+<!-- available hbs variables are user.displayName and user.username -->
+```
+```
+
+To begin creating a new template, from the Email Templates tab of the global settings page (Administration > Settings), click + CREATE. The following configurations must be set:
+
+- **TYPE:** Select the email type for the new template
+- **TEMPLATE:** The HTML markdown for the new custom email template
+- **TENANTS:** This option is only available in the Master Tenant. Select a specific Tenant to tie the template to that Tenant or leave it empty to create a global template
+
+The following is an example of a Forgot Password Template. Note that it calls in the variable for the associated user display name and username.
+
+```
+```
+<p>Hello {{{user.displayName}}},</p>  
+<p>You have requested to reset the password for the account with username: {{{user.username}}}.</p>  
+<p>To reset the password, please click the button below. If you did not make this request, you can ignore this email but you should change your password.</p>  
+<a href='{{{forgotPasswordUrl}}}' class="btn-primary">Magical Password Reset Button</a>
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json b/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
new file mode 100644
index 0000000..aae2ab7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+  "title": "Hardware Requirements",
+  "ordinal": 179,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2",
+        "clustering_title": "Hardware Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md b/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
new file mode 100644
index 0000000..6d8ae13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.md
@@ -0,0 +1,36 @@
+# Hardware Requirements
+
+- **Operating System:** Ubuntu 22.04
+- **CPU:** One or more 64-bit x86 CPUs, 1.5 GHz minimum with Intel VT or AMD-V enabled
+- **Memory:** 4 GB minimum. For non-converged Layouts, configure HVM hosts to use shared external storage, such as an NFS share or iSCSI target. Converged Layouts utilize Ceph for clustered storage and require a **4 GB minimum memory per Ceph disk**
+- **Disk Space:** For converged storage, a data disk of at least 500 GB is required for testing. More storage will be needed for production clusters. An operating system disk of 15 GB is also required. Clusters utilizing non-converged Layouts can configure external storage (NFS, etc.) while HPE Morpheus Enterprise will configure Ceph for multi-node clusters
+- **Network Connectivity:** HVM hosts must be assigned static IP addresses. They also need DNS resolution of the HPE Morpheus Enterprise appliance and Internet access in order to download and install system packages for HVM dependencies, such as KVM, Open vSwitch (OVS), and more
+
+NOTE
+
+Ubuntu 22.04 uses `netplan` for networking and it is the responsibility of the customer to establish recommended networking configurations prior to provisioning an HVM cluster. To configure a static IP address, change into the directory holding the config files (`cd /etc/netplan`) and edit the existing configuration file (`/etc/netplan/50-cloud-init.yaml` or `/etc/netplan/00-installer-config.yaml` or `/etc/netplan/01-netcfg.yaml`). If desired, backup the existing configuration prior to editing it (`cp /etc/netplan/<file-name>.yaml /etc/netplan/<file-name>.yaml.bak`). For additional information on configuration file formatting, refer to `netplan` [documentation](https://netplan.readthedocs.io/en/stable/). Once the configuration is updated, validate and apply it (`netplan try`). The `try` command will validate the configuration and apply it if it’s valid. If invalid, it will automatically be rolled back.
+
+NOTE
+
+Clustered storage needs as much network bandwidth as possible. Network interfaces of at least 10 Gbps with jumbo frames enabled are required for clustered storage and for situations when all traffic is running through the management interface (when no compute or storage interface is configured). It’s highly likely that performance will be unacceptable with any lower configurations.
+
+Table 1. HVM Network Communication Ports
+
+       | Description | Source | Destination | Port | Protocol |
+| --- | --- | --- | --- | --- |
+| HPE Morpheus Enterprise Agent communication with the HPE Morpheus Enterprise appliance | HVM Host | HPE Morpheus Enterprise appliance server | 443 | TCP |
+| HPE Morpheus Enterprise Agent communication with the HVM Host for hypervisor console | HPE Morpheus Enterprise appliance server | HVM Host | 7443 | TCP |
+| HVM host configuration and management | HPE Morpheus Enterprise appliance server | HVM Host | 22 | TCP |
+| HVM interhost communication for clustered deployments | HVM Host | HVM Host | 22 | TCP |
+| HPE Morpheus Enterprise server SSH access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 22 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTP) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5985 | TCP |
+| HPE Morpheus Enterprise server WinRM (HTTPS) access for deployed virtual machines | HPE Morpheus Enterprise appliance server | HVM‐hosted virtual machines | 5986 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 3300 | TCP |
+| Ceph Storage | HVM Host | HVM Host | 6789 | TCP |
+| Ceph MDS/OSD | HVM Host | HVM Host | 6800‐7300 | TCP |
+| Corosync | HVM Host | HVM Host | 5404-5406 | UDP |
+| pcsd | HVM Host | HVM Host | 2224 | TCP |
+| dlmd | HVM Host | HVM Host | 21064 | TCP |
+|  | HVM Host | HVM Host | 9929 | TCP |
+|  | HVM Host | HVM Host | 9929 | UDP |
+|  | HVM Host | HVM Host | 3121 | TCP |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json b/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
new file mode 100644
index 0000000..f5fee6d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+  "title": "Morpheus UI war files",
+  "ordinal": 28,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus UI war files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03",
+        "clustering_title": "Morpheus UI war files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md b/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
new file mode 100644
index 0000000..b42926c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.md
@@ -0,0 +1,51 @@
+# Morpheus UI war files
+
+## About this task
+
+Pre-release or patched versions of the HPE Morpheus Enterprise UI are sometimes provided. To deploy the ui war on a HPE Morpheus Enterprise Appliance:
+
+## Procedure
+
+1. Download the war file to the target appliance 
+
+   ```
+   ```
+   wget https://url/war_file
+   ```
+   ```
+
+   NOTE
+
+   If the war file is provided via a droplr link, ensure a `+` is added to end of droplr url or the file will not download
+2. Backup current war file 
+
+   ```
+   ```
+   sudo mv /opt/morpheus/lib/morpheus/morpheus-ui.war /opt/morpheus/lib/morpheus/morpheus-ui.bak.`date +"%m-%d-%Y"`
+   ```
+   ```
+3. Move and rename new war file 
+
+   ```
+   ```
+   sudo mv <file> /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+4. Ensure war is owned by `morpheus-app` 
+
+   ```
+   ```
+   sudo chown morpheus-app:morpheus-app /opt/morpheus/lib/morpheus/morpheus-ui.war
+   ```
+   ```
+5. Restart the HPE Morpheus Enterprise UI 
+
+   ```
+   ```
+   sudo morpheus-ctl restart morpheus-ui
+   ```
+   ```
+
+## Results
+
+The new ui war will load on startup!
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json b/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
new file mode 100644
index 0000000..a65c3bf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 423,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md b/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
new file mode 100644
index 0000000..d3580aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.md
@@ -0,0 +1,28 @@
+# Firmware and Driver Lifecycle Management
+
+Starting with HPE BMaaS version 1.0.0, HPE Morpheus Enterprise supports firmware and driver updates for HPE ProLiant bare-metal servers using preloaded tasks and workflows. This capability enables administrators to centrally manage server firmware and driver compliance using HPE Service Pack for ProLiant (SPP) images, executed directly from the HPE Morpheus appliance.
+
+Firmware and driver updates are performed through **Jobs and Workflows** in HPE Morpheus and can be run in **Dry Run (inventory)** or **Deploy** modes. Updates can target firmware only, drivers only, or both, depending on operational requirements. The update process supports multiple servers per job and provides detailed execution logs for auditing and troubleshooting.
+
+## Prerequisites
+
+Before performing firmware and driver updates, ensure the following:
+
+- HPE BM Plugin version 1.0.0 or later is installed.
+- An appropriate HPESPP ISO is available for each server generation (for example, Gen10 and Gen11 require different SPP ISOs).
+- The HPE Morpheus appliance has access to the SPP ISO, either through:
+
+  - A locally downloaded ISO file, or
+  - A URL accessible without authentication.
+- For driver inventory and updates within a deployed operating system:
+
+  - iSUT (Integrated Smart Update Tools) and AMS (Agentless Management Service) must be installed and running on the target servers.
+  - ESXi hosts are expected to already have iSUT installed.
+
+**Subtopics**  
+
+- **[Adding HPE SPP to the Virtual Image Library](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-151B596B-EE69-4D4B-8C80-964A90D3523C.html)**
+- **[Installing iSUT on Deployed Instances (Optional)](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html)**
+- **[Creating and Running an SPP Update Job](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-10176AA6-4AAE-4480-98BE-D1E4FF3DBB2E.html)**
+- **[Monitoring and Completion](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html)**
+- **[Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json b/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
new file mode 100644
index 0000000..d3fd2af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+  "title": "API Access",
+  "ordinal": 339,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html",
+  "topic_cluster": {
+    "clustering_title": "API Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED",
+        "clustering_title": "API Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md b/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
new file mode 100644
index 0000000..047ba34
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.md
@@ -0,0 +1,20 @@
+# API Access
+
+Click the API Access button to expand the “API ACCESS” modal. In this modal you can generate or refresh access tokens that can be used with Morpheus API and Morpheus CLI.
+
+If no token yet exists for a particular “CLIENT ID”, click ACTIONS and then Generate. If a token has expired, we can also regenerate that token by clicking ACTIONS and then Regenerate. After regenerating a particular token, you would need to ensure any scripts using those tokens are updated.
+
+If needed, Primary Tenant administrators may configure the expiration periods for existing clients or create new clients from HPE Morpheus Enterprise global settings (Administration > Settings > Clients). See [client configuration documentation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-10BE13E9-1014-4162-97E7-A1056FED89B3.html) for more details.
+
+- **morph-api:** Used for HPE Morpheus Enterprise API access and should be the default token-type used
+- **morph-cli:** Used for HPE Morpheus Enterprise CLI access
+- **morph-automation:** Used by the internal Task engine and by jRuby-type Tasks to make API calls. It shouldn’t be used externally for other types of access or in external automation. It is surfaced in the UI so users can see if a token exists and can clear it when necessary
+- **morph-customer:** This token is available for legacy implementations and was previously recommended for custom API access (similar to the morph-api token). It’s not recommended for use but is still available to maintain support for legacy custom automation which may still be in use on customer sites
+
+After navigating away from the User Settings page, the complete access and refresh tokens will be masked from view. If these are lost or compromised, you can eliminate a token completely by clicking ACTIONS and then Clear. If you need to generate a new token for the same Client ID, click ACTIONS and then Regenerate.
+
+![../../_images/user-tokens.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-274AD26D-C940-4740-BBC7-7970107CCB4B-high.png)
+
+NOTE
+
+Access Tokens are only displayed/available after generation. Copy new Tokens and store appropriately before navigating from `/user-settings`, they will not be displayed again.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json b/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
new file mode 100644
index 0000000..d35f053
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+  "title": "Upgrading",
+  "ordinal": 20,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2",
+        "clustering_title": "Upgrading"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md b/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
new file mode 100644
index 0000000..c9e03bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.md
@@ -0,0 +1,8 @@
+# Upgrading
+
+**Subtopics**  
+
+- **[Upgrading Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html)**
+- **[Single Node/AIO Appliance Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html)**
+- **[3-Node HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html)**
+- **[Full HA Upgrade](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json b/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
new file mode 100644
index 0000000..3bfa4f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+  "title": "Okta",
+  "ordinal": 284,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html",
+  "topic_cluster": {
+    "clustering_title": "Okta",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997",
+        "clustering_title": "Okta"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md b/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
new file mode 100644
index 0000000..44ba4a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.md
@@ -0,0 +1,52 @@
+# Okta
+
+## Overview
+
+HPE Morpheus Enterprise allows users to integrate an Okta deployment for user management and authentication. In HPE Morpheus Enterprise, identity sources are added on a per-Tenant basis and Morpheus allows you to map Okta user groups to HPE Morpheus Enterprise user groups. User accounts are automatically created with matching metadata and role permissions when users are authenticated.
+
+## Adding an Okta Integration
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + IDENTITY SOURCE
+5. Choose TYPE: “Okta”
+6. Populate the following, then select SAVE CHANGES:
+
+### Results
+
+Name
+:   Unique name for authentication type
+
+Description
+:   A description for your new Okta Identity Source
+
+Okta URL
+:   Your Okta URL
+
+Administrator API Token
+:   Your Okta Administrator API Token
+
+Required Group
+:   The Okta group that users must be in to have access (optional)
+
+Default Role
+:   The default role a user is assigned if no group is listed under an Okta user that maps within the Morpheus Role Mappings section
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Now, allowed Okta users can log into HPE Morpheus Enterprise via their Okta credentials and a user will be automatically generated within HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+NOTE
+
+If you’ve created multi-tenant roles, these will also appear here and can be mapped to Okta user groups allowing you to map users to equivalent user groups in HPE Morpheus Enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json b/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
new file mode 100644
index 0000000..b98a43e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+  "title": "Edit Workflow",
+  "ordinal": 120,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html",
+  "topic_cluster": {
+    "clustering_title": "Edit Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9",
+        "clustering_title": "Edit Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md b/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
new file mode 100644
index 0000000..1318da7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.md
@@ -0,0 +1,10 @@
+# Edit Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar.
+2. Select Automation from the sub-navigation menu.
+3. Click the Workflows tab to show the workflows tab panel.
+4. Click the Edit icon on the row of the workflow you wish to edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json b/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
new file mode 100644
index 0000000..3323939
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+  "title": "Inputs",
+  "ordinal": 154,
+  "parent_title": "Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html",
+  "topic_cluster": {
+    "clustering_title": "Inputs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706",
+        "clustering_title": "Inputs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md b/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
new file mode 100644
index 0000000..cd7db19
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.md
@@ -0,0 +1,220 @@
+# Inputs
+
+Inputs are custom input fields that can be added to Instance Types and Layouts, then presented in Instance, App, and Cloning wizards. The resulting value is available in the Instance config map as <%=customOptions.fieldName%> or <%=customOptions[‘fieldName’], the latter syntax being required in certain situations such as when the field name contains a hyphen “-” (ex. <%=customOption[‘my-field-name’]). The fieldName and value can also be exported as Tags.
+
+![../../_images/new_option_type.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ADEB1679-C4C4-4345-B276-57B434C94563-high.png)
+
+## Create Input
+
+NOTE
+
+All possible fields listed. Displayed fields depend on `TYPE` selection
+
+NAME
+:   Name of the Input
+
+DESCRIPTION
+:   Description for reference in Input list view
+
+FIELD NAME
+:   This is the input fieldName property that the value gets assigned to
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+HIDDEN
+:   When marked, this Input will be hidden from the user but the value will still be accessible. This allows for alternate Input types to be used as hidden Inputs than what is possible with “Hidden” type Inputs (described further below). This is also different from Input “Visibility” settings as the values of non-visible Inputs is not accessible for consumption in automation routines
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value. It should also be noted that when an Input is not visible, its value is not available for consumption in automation routines. Use the “Hidden” flag (see above) to configure hidden yet accessible values
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+TYPE
+:   - **Text:** Text Input Field
+    - **Text Area:** A text area input, when selected an additional option appears to allow the user to configure the default number of visible rows in the text area
+    - **Select List:** Populated by Option Lists, presents a manual or REST-populated dropdown list
+    - **Checkbox:** Checkbox for `on` or `off` values
+    - **Number:** Input field allowing only numbers
+    - **Typeahead:** Populated by Option Lists: Rather than presenting a potentially-large dropdown menu, the user can begin typing a selection into a text field and choose the desired option. Multiple selections can be allowed with this type by marking the ‘ALLOW MULTIPLE SELECTIONS’ box
+    - **Hidden:** No field will be displayed, but the field name and default value will be added to the Instance config map for reference
+    - **Password:** An input field with suitable encryption for accepting passwords
+    - **Radio List:** Populated by Option Lists, presents a selection of radio buttons for the provisioning user
+
+LABEL
+:   This is the input label that typically shows to the left of a custom option
+
+ROWS
+:   For `Textarea` type Option Lists, determines how many text rows will be given when the Input is presented
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+REMOVE NO SELECTION
+:   For Select List-type Inputs. When marked, the Input will default to the first item in the list rather than to an empty selection. This is especially useful when only one choice is anticipated to be in the list as it saves the user from manually making a default selection
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+    **Verify Pattern Demo**
+
+DEFAULT CHECKED
+:   For `Checkbox` types, when marked the Checkbox will be checked by default
+
+OPTION LIST
+:   For `Select List` types, select a pre-existing Option List to set dropdown values
+
+    NOTE
+
+    `Select List` and `Typeahead` Inputs require creation and association of an Option List
+
+## Cascading Inputs
+
+One powerful facet of HPE Morpheus Enterprise Inputs is the ability to present users with different lists of input options based on their selections in other Inputs within the same wizard or modal. One common example, which is fully illustrated in this section, is to have a user select:
+
+- The Group they wish to provision into…
+- Then select the target Cloud from a list limited to Clouds which are in the selected Group…
+- Then select the target network from a list limited to networks which are available to the selected Cloud and Group
+
+To set this up, we will first configure our Inputs (custom option fields that can be applied to Instance Types and other HPE Morpheus Enterprise constructs) and Option Lists (dynamic lists of possible choices which can be associated with Inputs and presented in a dropdown or typeahead format). Once the custom options are configured, we will associate them with a new service catalog item and take a look at how the user would interact with them.
+
+### Group Custom Options
+
+To begin, we will create a new [Option List](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#option-lists) In this case, we will select type of “Morpheus Api” which will populate the list based on a call to the internal HPE Morpheus Enterprise API. Option Lists can also be populated by calls to external REST APIs or even from static lists that you enter manually. When dynamically populating Option Lists, whether via HPE Morpheus Enterprise API or an external API, translation and/or request scripts may be needed to prepare the request or translate the results. More on that as we build out the example.
+
+I have called my Option List “Groups” and selected “Groups” from the OPTION LIST menu. This simply indicates that Groups are the construct we want to call into our list from HPE Morpheus Enterprise API. In this case, we want to present a list of all Groups to the user by their name and pass the Group database ID in the background. Since it is common to create Option Lists from HPE Morpheus Enterprise API where the construct name is displayed to the user and the ID is passed, we actually do not need to input any translation scripts in this case. However, I will include a translation script here which does the same thing simply to provide more clarity to the example. HPE Morpheus Enterprise [Option List documentation](https://docs.morpheusdata.com/en/latest/library/options/option_lists.html) includes additional details on available translation script inputs and which are available without translation as a convenience feature.
+
+```
+```
+for (var x = 0; x < data.length; x++) {  
+  results.push({name: data[x].name, value:data[x].id});  
+}
+```
+```
+
+After saving the Option List, create the Input that presents the list we just created. I gave my Input the name of “Selected Group”, field name of “selectedGroup”, and label of “Group”. For type, choose “Select List” and a new field will appear at the bottom of the modal where we can select the Option List we just created. With this configuration, the Input will present as a dropdown list containing the options called from our Option List.
+
+### Cloud Custom Options
+
+Adding the Option List and Input for Clouds will be similar to the prior step with the exception that we will be including a request script which effectively filters the list of available Clouds to only those associated with the selected group. Follow the same process to start a new Option List, I have configured mine as follows:
+
+- **NAME:** Parsed Clouds
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Clouds
+
+We also need a request script that loads the `siteId` attribute of the `results` variable with the Group ID if the user has made a group selection. Essentially it appends this input as a query parameter to the API call, calling (for example) `./api/clouds?siteId=1` rather than `.../api/clouds`. It should be similar to the script below. Note that we are referencing the `selectedGroup` field name we created previously and that a “site” is the term for Groups in the HPE Morpheus Enterprise database.
+
+```
+```
+if (input.selectedGroup) {  
+  results.siteId = input.selectedGroup  
+}
+```
+```
+
+We also need a translation script which will be identical to the one used previously with the exception that if there is no input on the `selectedGroups` field, nothing will be displayed for the Clouds option.
+
+```
+```
+if (input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+We also need to create an Input to house this Option List. This process will be very similar to creating the previous Input except that we need to set selectedGroup as the Dependent Field. Setting a dependent field on an Input will trigger it to reload each time a selection is made in the indicated option. My configuration is as follows:
+
+- **NAME:** Parsed Cloud
+- **FIELD NAME:** parsedCloud
+- **DEPENDENT FIELD:** selectedGroup
+- **TYPE:** Select List
+- **LABEL:** Cloud
+- **OPTION LIST:** Parsed Clouds
+
+Save your changes once done.
+
+### Network Custom Option
+
+Finally, we will create an Option List/Input pair for network selection. In this case, it will be dependent on both the Group and Cloud selection. My Option List configuration is below:
+
+- **NAME:** Parsed Networks
+- **TYPE:** Morpheus Api
+- **OPTION LIST:** Networks
+
+### Request Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+  results.cloudId = input.parsedCloud  
+  results.groupId = input.selectedGroup  
+}
+```
+```
+
+### Translation Script:
+
+```
+```
+if (input.parsedCloud && input.selectedGroup) {  
+for (var x = 0; x < data.length; x++) {  
+    results.push({name:data[x].name, value:data[x].id});  
+  }  
+}
+```
+```
+
+The Input is configured as follows:
+
+- **NAME:** Parsed Networks
+- **FIELD NAME:** parsedNetwork
+- **DEPENDENT FIELD:** parsedCloud
+- **TYPE:** Select List
+- **LABEL:** Network
+- **OPTION LIST:** Parsed Networks
+
+### Setting Custom Options at Provision Time
+
+At this point, our dependent options are ready to be applied to custom Instance Types, Workflows or Service Catalog items as needed. When creating them, we can select an unlimited number of Inputs from a typeahead field on the create modal and they will be presented when a user goes to provision that element or run that Workflow. As an example, I have created a Service Catalog item that incorporates the three Inputs we have created. You can see how the dependent fields reload and present different options based on my selections.
+
+![../../_images/cascadingOptionList.gif](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-41F98D9A-033E-4560-8F99-824818F25590-high.gif)
+
+## Visibility Field
+
+The Input Visibility field allows users to set conditions under which the Input field is displayed. Visibility field accepts `fieldName:value` or `fieldName:(regex)`, where “fieldName” equals the fieldName of another Input which will determine the visibility of this Input, and “value” equals the target value of the other Input (or a regex pattern that matches to the values that meet your desired conditions). You can simply enter “fieldName” when visibility should be triggered when any value is entered. When the value of the target Input matches the “value” or “(regex)” set in the Visibility field, this Input will be displayed. When the value of the target Input does not match “value” or satisfy the “(regex)” set in the Visibility field, this Input will not be displayed.
+
+Expanding on the simplified example above, we could trigger visibility based on any one of multiple selections from the same Input by using a different regular expression, such as `color:(red|blue|yellow)`. Additionally, we are not restricted to the conditions of just one Input to determine visibility as the following would also be valid: `color:(red|blue|yellow),shape:(square)`. In the previous example, the Input “Color” would have to be set to red, blue, or yellow OR the Input “Shape” would have to be set to square in order to trigger visibility of the Input currently being configured. Prepend the previous example with `matchAll::` in order to require both conditions to be met rather than one or the other (ex. `matchAll::color:(red|blue|yellow),shape:(square)`).
+
+## Required Field
+
+The Required field allows for Inputs to be conditionally required. In this field, enter the Field Name value for another Input and, if that Input is filled by the user, the current Input will become required. This feature could also be used in conjunction with the Visibility field described above in that you may want a field to be required when visible but not required when hidden. Below is a simple abstract example showing how the second displayed Input becomes required when the first displayed Input is filled.
+
+![../../_images/required.gif](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E44477FD-45A4-44BD-A7CA-0587E51A09ED-high.gif)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json b/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
new file mode 100644
index 0000000..0b892d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+  "title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+  "ordinal": 367,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html",
+  "topic_cluster": {
+    "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF",
+        "clustering_title": "Creating XaaS Instance Types with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md b/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
new file mode 100644
index 0000000..90c296c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.md
@@ -0,0 +1,207 @@
+# Creating XaaS Instance Types with HPE Morpheus Enterprise
+
+HPE Morpheus Enterprise version 5.4.2 and higher includes the ability to build and provision XaaS Instance Types. These are non-VM backed Layouts which allow users to represent anything as an Instance. This includes the ability to utilize Provisioning Workflows to manage all phases of the Instance lifecycles consistently and automatically. XaaS Instance Types can also be tied into service plans to track costs or bill customers.
+
+In this specific example, we will create an XaaS Instance Type to manage the lifecycle of folders within a Dropbox account. Users will be able to visit the HPE Morpheus Enterprise Catalog and have the folder created by entering a name for the folder and clicking a single button. We’ll see how each folder is then represented as an Instance. With the Instance standing, users will be able to update the folder name by simply editing a custom value on the Instance. Finally, when the Instance is deleted, the folder is deleted from Dropbox as well.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Clouds
+- Inputs
+- Tasks
+- Workflows
+- Instance Types
+- Layouts
+- Catalog Items
+- Instances
+
+NOTE
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. In this guide we will go through the process of creating a HPE Morpheus Enterprise-type Cloud which can be used to hold your XaaS resources.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the Dropbox API token as a Cypher entry. Creating Dropbox developer accounts and obtaining API keys goes beyond the scope of this guide but Dropbox developer tools are well-documented if you want to try this out for yourself. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dropboxtoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/1cypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-865BCB56-4457-4DA6-A9A1-34CFCD22EEAE-high.png)
+
+One of my Tasks will also send a request to the HPE Morpheus Enterprise API so I’ll create a second Cypher entry to store a HPE Morpheus Enterprise API key:
+
+- **KEY:** secret/morphapitoken
+- **VALUE:** Enter Dropbox API token here
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+## Create Cloud
+
+XaaS Instances are associated with HPE Morpheus Enterprise-type Clouds. HPE Morpheus Enterprise Clouds are generic cloud wrappers that can be used to contain manually-managed servers, VMs, and (in this case) non-VM based resources. For this example, I’m creating a Cloud just to organize Dropbox folders. Navigate to Infrastructure > Clouds and click + ADD. The only required steps to create the Cloud are to give it a name and associate it with a Group. I’ve given mine a generic name but you could opt to be more targeted with your naming if you will use many HPE Morpheus Enterprise-type Clouds to manage other types of resources.
+
+- **NAME:** MorphCloud
+
+![../../_images/1cloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B1A71913-825C-4533-BBBD-AEF60F33F4F1-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create two Inputs in this case, one to allow the user to enter a name for their folder on provisioning and another which will be visible when editing the Instance to allow the user to rename their folder.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** DropBox Folder Name (The name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** dbfoldername (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **SHOW ON EDIT:** Checked (When checked, this Option is visible when editing an Instance)
+- **EDITABLE:** Checked (When checked, this Option is editable in addition to being visible while editing the Instance)
+- **LABEL:** DropBox Folder Name (The label the user sees next to the input field)
+
+Once done, click SAVE CHANGES
+
+![../../_images/2input.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-13B6ACC4-D949-465D-B229-1A7E9D065999-high.png)
+
+Next, configure a second Input with the following attributes:
+
+- **NAME:** DropBox Folder New Name
+- **FIELD NAME:** dbfoldernewname
+- **TYPE:** Text
+- **SHOW ON EDIT:** Checked
+- **EDITABLE:** Checked
+- **LABEL:**
+
+Click SAVE CHANGES
+
+## Create Tasks
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ll write the Task configuration directly into the HPE Morpheus Enterprise Tasks. However, Tasks can also be sourced directly from integrated version control repositories (like Github) so you never have to copy and paste code or make manual updates when your code changes.
+
+For this example, we need to create four Tasks. One to create the folder, one to rename the folder, one to rename the HPE Morpheus Enterprise Instance, and one to delete the folder. I’ve used Python Tasks to interact with the Dropbox Python SDK. I won’t go into how to write the individual Tasks here but the Python SDK is well-documented if you want to try things out for yourself. The same functions could be carried out using other Task types as well.
+
+![../../_images/3tasks.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BBDD2BA6-FF48-4A8B-903C-7F8C08E972A2-high.png)
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Dropbox - Create Folder
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Local (Select Repository to source your code from an integrated version control repository)
+- **CONTENT:** Enter Task content here
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the Dropbox API token from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US)
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES
+
+![../../_images/5createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-82B72BAF-618B-4F5A-B82F-8D4BE96BD27A-high.png)
+
+The process for creating the remaining three Tasks is very similar, expand the sections below to see screenshots of the Task config, if desired:
+
+### Dropbox - Delete Folder
+
+![../../_images/6deletetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-020E198F-49C6-4228-ABE8-C5580D223F15-high.png)
+
+### Dropbox - Rename Folder
+
+![../../_images/7renametask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-05551E97-6453-4079-A6D5-B0CF880BC840-high.png)
+
+### Dropbox - Reset Instance Name
+
+![../../_images/8resetinstancetask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BFB5EBC7-4C8A-4F58-AB33-90475BCB8B6E-high.png)
+
+## Create Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need the following to occurring during the Instance lifecycle:
+
+- At the provisioning phase, we want a folder to be created
+- At the reconfigure phase (when the Instance is edited), we want the folder to be renamed and the Instance name to be updated
+- At the teardown phase (when the Instance is deleted), we want the folder to be deleted
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **PLATFORM:** All
+- **TASKS - Provision:** Dropbox - Create Folder
+- **TASKS - Reconfigure:** Dropbox - Rename Folder; Dropbox - Reset Instance Name
+- **TASKS - Teardown:** Dropbox - Delete Folder
+
+Once done, click SAVE CHANGES
+
+![../../_images/9workflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4710C85B-97B8-4EFB-B607-8D8289BEE58C-high.png)
+
+## Create Instance Type
+
+With the Workflow and Inputs complete, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. From this, we’ll create a catalog item that our users can order in a later step.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** XaaS - Dropbox
+- **CODE:** xaas
+- **CATEGORY:** Utility
+- **ICON:** If desired, search the file system on your local computer for a Dropbox logo icon for easier identification of this Instance Type at provision time
+- **ENVIRONMENT PREFIX:** XAAS
+
+![../../_images/10instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-08F8C46C-E7EE-4E11-B0D2-D204B32405B6-high.png)
+
+Click SAVE CHANGES.
+
+## Create Layout
+
+After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case Workflow. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on (when dealing with VM-based Instance Types). Configure the Layout as follows:
+
+- **NAME:** XaaS - Dropbox
+- **VERSION:** Latest
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Workflow
+- **WORKFLOW:** Select the Workflow we’ve just created, “XaaS - Dropbox”. By selecting this, all Instances provisioned with this Layout will automatically have our chosen Tasks run during specific Instance lifecycle phases
+- **INPUTS:** Search and find the two custom Inputs we created earlier, “DropBox Folder Name” and “DropBox Folder New Name”
+
+![../../_images/11layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3C57ACEF-141F-4DED-929C-1724C2B1F81C-high.png)
+
+## Create Catalog Item
+
+Catalog Items offer a simplified provisioning process. Administrators can create Catalog Items using existing Instance Types, App Blueprints, or Workflows. Most or all of the provisioning options can be pre-selected leaving fewer decisions up to the user and allowing them to easily create what they need. In this case, we’ll create one based on the Instance Type that was made in the previous sections. Navigate to Library > Blueprints > Catalog Items and click + ADD, then Instance. Configure the following:
+
+- **NAME:** XaaS - Dropbox Folder
+- **ENABLED:** Checked (If unchecked, this Catalog Item will not be displayed in the provisioning catalog for users)
+- **LOGO:** If desired, browse your local disk for a Dropbox logo to make this Catalog Item easily recognizable
+
+Then, click CONFIGURATION WIZARD. On the “TYPE” tab, search for the Instance Type we created and click NEXT. On the “Group” tab, select the HPE Morpheus Enterprise-type Cloud and enter any name (we’ll override this name value later so it’s dynamic based on user input). Click NEXT. On the “CONFIGURE” tab, the Layout and Plan fields should default to acceptable values. Enter anything for the “Dropbox Folder Name”, we will also update this to be dynamic in the next step. Click through the final two tabs, there’s no need to attach our Workflow on the “AUTOMATION TAB” since we already have it on our Layout. Finally, click COMPLETE.
+
+Once finished, you’ll see the JSON configuration map for the Instance loaded into the “CONFIG” field. Update the “dbfoldername” Input value and the Instance name value to dynamically take on the user-entered value on the “Dropbox Folder Name” field as I’ve done in my screenshot below:
+
+![../../_images/12catitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F93420D1-2F2A-479B-9ACD-56A52256AD43-high.png)
+
+Near the bottom of the modal window, search for and attach the “DropBox Folder Name” Input. This will be the only input our users need to make to order their folder. Then, click SAVE CHANGES
+
+## Ordering Catalog Item
+
+At this point, the configuration steps are completed. As a test, we can order a folder from the provisioning Catalog. Navigate to Provisioning > Catalog and click “Order” on our “XaaS - Dropbox Folder” item. We need only provide a name for our folder and click “Order Now”.
+
+![../../_images/13orderitem.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-27E8619F-240F-43AE-A00F-70489E83CE32-high.png)
+
+If we now head to Provisioning > Instances, we can see a new Instance entry has been created for our Dropbox folder. Note that the Instance is named for our folder name exactly as we configured earlier.
+
+![../../_images/14inslist.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2FA0BA43-267B-4BFD-8C3A-46A8879844F4-high.png)
+
+Taking a look in the Dropbox web console, we can also see a folder has been created just as we’d expect.
+
+![../../_images/15dbcreate.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-38887B6A-8B2B-44AA-BDA0-91C557D414F8-high.png)
+
+## Managing and Deleting Instances
+
+Back in HPE Morpheus Enterprise, we can take a look at the Instance detail page (Provisioning > Instances > Specific Instance) and perform some Day 2 actions. By clicking EDIT, we can update Instance details. When Input values are updated, HPE Morpheus Enterprise will automatically trigger reconfigure actions on our Instance. In our case, we’ve configured it to update the folder name in Dropbox and update the Instance name in HPE Morpheus Enterprise for easier identification. As you can see in the screen shot, I’m providing a new folder name value:
+
+![../../_images/16editins.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4A83E6DE-B560-4FBC-A948-892DA9AFBBE2-high.png)
+
+As expected, our Instance name is updated and the folder is renamed on the Dropbox side:
+
+![../../_images/17insdetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9E516B64-6C3D-4577-B7C6-E67FC23ADBB2-high.png) ![../../_images/18dbupdate.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FB2B154B-85F7-4AA0-B77E-FB596CE9F7FE-high.png)
+
+Finally, I’ll delete the Instance. This has the effect of deleting the Instance object out of HPE Morpheus Enterprise and triggering our Teardown-phase action which deletes the folder from Dropbox:
+
+![../../_images/19dbdelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5D5388E9-5251-499E-ABE9-36A1342F356C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json b/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
new file mode 100644
index 0000000..b5c9dca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+  "title": "3 Node HA Install Example",
+  "ordinal": 18,
+  "parent_title": "Installation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html",
+  "topic_cluster": {
+    "clustering_title": "3 Node HA Install Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827",
+        "clustering_title": "3 Node HA Install Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md b/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
new file mode 100644
index 0000000..88a1e53
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.md
@@ -0,0 +1,489 @@
+# 3 Node HA Install Example
+
+Distributed App Nodes with Externalized MySQL Database
+
+A common and recommended HA Morpheus deployment consists of three app nodes using embedded services and an external MySQL DB cluster (minimum of 3 nodes).
+
+IMPORTANT
+
+HA environments installed without engagement from Morpheus are not eligible for support. The provided configuration serves as a sample only and requirements may vary. Please reach out to your account manager to discuss deploying a HA environment to meet the requirements for support.
+
+## Assumptions
+
+This guide assumes the following:
+
+- App nodes can resolve each others short names
+- All app nodes have access to shared storage mounted at `/var/opt/morpheus/morpheus-ui`.
+- This configuration is designed to tolerate the complete failure of a single node but not more. Specifically, the Elasticsearch tier requires MORE than 50% of the nodes to be up and clustered at all times. However, you can always add more nodes to increase resilience.
+- You have a load balancer available and configured to distribute traffic between the app nodes. [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
+
+![Morpheus 3-Node HA Architecture](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-627980F3-725B-4765-8CF0-89FD087667C8-high.png)
+
+## Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## MySQL requirements for Morpheus HA
+
+The requirements are as follows:
+
+- MySQL version v8.0.x (minimum of v8.0.72)
+- MySQL cluster with at least 3 nodes for redundancy.
+- Morpheus application nodes have connectivity to MySQL cluster.
+
+NOTE
+
+Morpheus does not create primary keys on all tables. If you use a clustering technology that requires primary keys, you will need to leverage the invisible primary key option in MySQL 8
+
+## Configure Morpheus Database and User
+
+### Procedure
+
+1. Create the Database you will be using with HPE Morpheus Enterprise. Login to mysql node: 
+
+   ```
+   ```
+   [root@node: ~]  mysql -u root -p  
+     # password: `enter root password`  
+   mysql> CREATE DATABASE morpheus CHARACTER SET utf8mb4 COLLATE utf8mb4_general_ci;  
+   mysql> show databases;
+   ```
+   ```
+2. Next create your HPE Morpheus Enterprise database user. This is the user the HPE Morpheus Enterprise app nodes will auth with mysql. 
+
+   ```
+   ```
+   mysql> CREATE USER 'morpheus'@'%' IDENTIFIED BY 'morpheusDbUserPassword';
+   ```
+   ```
+3. Next Grant your new HPE Morpheus Enterprise user permissions. 
+
+   ```
+   ```
+   mysql> GRANT ALL PRIVILEGES ON morpheus.* TO 'morpheus'@'%' with grant option;  
+   mysql> GRANT SELECT, PROCESS, SHOW DATABASES, RELOAD ON *.* TO 'morpheus'@'%';  
+   mysql> FLUSH PRIVILEGES;  
+   mysql> exit
+   ```
+   ```
+
+## App Node Installation
+
+### Requirements
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `outbound` access to the various backend services:
+
+- mySQL Port to External DB
+
+  - 3306/tcp
+
+Ensure the firewall (or security group) allows HPE Morpheus Enterprise `inbound` from agents and users:
+
+- HTTPS Port
+
+  - 443/tcp
+- RabbitMQ Ports
+
+  - 4369 (epmd - inter node cluster discovery)
+  - 5671 (TLS from nodes to RabbitMQ)
+  - 5672 (non-TLS from nodes to RabbitMQ)
+  - 15671 (HTTPS API)
+  - 15672 (HTTP API)
+  - 25672 (inter node cluster communication)
+  - 61613 (STOMP - non-TLS)
+  - 61614 (STOMP - TLS)
+- OpenSearch Ports
+
+  - 9200 (API access)
+  - 9300 (inter node cluster communication)
+
+### Installation
+
+#### Procedure
+
+1. First begin by downloading and installing the requisite HPE Morpheus Enterprise packages to ALL HPE Morpheus Enterprise app nodes. 
+
+   HPE Morpheus Enterprise packages can be found in the Downloads section of the [Morpheus Hub](https://morpheushub.com/download)
+
+   RHELL/CentOS
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance-ver-1.el8.x86_64.rpm  
+   [root@node: ~] rpm -ihv morpheus-appliance-appliance-ver-1.el8.x86_64.rpm
+   ```
+   ```
+
+   Ubuntu
+
+   ```
+   ```
+   [root@node: ~] wget https://example/path/morpheus-appliance_ver-1.amd64.deb  
+   [root@node: ~] dpkg -i morpheus-appliance-appliance_ver-1.amd64.deb
+   ```
+   ```
+2. Do NOT run reconfigure yet. The HPE Morpheus Enterprise configuration file must be edited prior to the initial reconfigure.
+3. Next you will need to edit the HPE Morpheus Enterprise configuration file `/etc/morpheus/morpheus.rb` on each node. 
+
+   NOTE
+
+   In the configuration below, the UID and GID for the users and groups are defined for services that will be embedded. This ensures they are consistent on all nodes. If they are not consistent, the shared storage permissions can become out of sync and errors will appear for plugins, images, etc. If not specified, Morpheus will automatically find available UIDs/GIDs starting at 999 and work down. Availability of UIDs and GIDs can be seen by inspecting `/etc/passwd` and `/etc/group` respectively. Change the UIDs and GIDs below based on what is available.
+
+   You can find additional configuration settings [here](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#advanced-morpheus-rb-settings)
+
+   Node 1
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.01'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node01'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.02'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node02'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   appliance_url 'https://morpheus.localdomain'  
+   opensearch['es_hosts'] = {'192.168.104.01' => 9200, '192.168.104.02' => 9200, '192.168.104.03' => 9200}  
+   opensearch['node_name'] = '192.168.104.03'  
+   opensearch['host'] = '0.0.0.0'  
+   rabbitmq['host'] = '0.0.0.0'  
+   rabbitmq['nodename'] = 'rabbit@node03'  
+   mysql['enable'] = false  
+   mysql['host'] = {'127.0.0.1' => 6446}  
+   mysql['morpheus_db'] = 'morpheus'  
+   mysql['morpheus_db_user'] = 'morpheus'  
+   mysql['morpheus_password'] = 'morpheusDbUserPassword'  
+   user['uid'] = 899  
+   user['gid'] = 899  
+   # at the time of this writing, local_user is not valid as an option so the full entry is needed  
+   node.default['morpheus_solo']['local_user']['uid'] = 898  
+   node.default['morpheus_solo']['local_user']['gid'] = 898  
+   opensearch['uid'] = 896  
+   opensearch['gid'] = 896  
+   rabbitmq['uid'] = 895  
+   rabbitmq['gid'] = 895  
+   guacd['uid'] = 894  
+   guacd['gid'] = 894
+   ```
+   ```
+
+   NOTE
+
+   The configurations above for `` `mysql['host'] `` shows a list of hosts, if the database has multiple endpoints. Like other options in the configuration, `mysql['host']` can be a single entry, if the database has a single endpoint: `mysql['host'] = 'myDbEndpoint.example.com` or `mysql['host'] = '10.100.10.111'`
+
+   IMPORTANT
+
+   The OpenSearch node names set in `opensearch['node_name']` must match the host entries in opensearch[‘es\_hosts’]. `node_name` is used for `node.name` and `es_hosts` is used for `cluster.initial_master_nodes` in the generated opensearch.yml config. Node names that do not match entries in cluster.initial\_master\_nodes will cause clustering issues.
+
+   IMPORTANT
+
+   The rabbitmq[‘node\_name’] in the Node 1 example above is rabbit@node01. The shortname for the server of node01 must be resolvable by DNS or /etc/hosts of all other hosts, same for node02 and node03. FQDNs cannot be used here
+4. Mount shared storage at `/var/opt/morpheus/morpheus-ui` on each App node if you have not already done so. Create the directory if it does not already exist.
+5. Reconfigure on all nodes 
+
+   All Nodes
+
+   ```
+   ```
+   [root@node: ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   HPE Morpheus Enterprise will come up on all nodes and OpenSearch will auto-cluster. RabbitMQ will need to be clustered manually after reconfigure completes on all nodes.
+
+## Clustering Embedded RabbitMQ
+
+### Procedure
+
+1. Select one of the nodes to be your Source Of Truth (SOT) for RabbitMQ clustering (Node 1 for this example). On the nodes that are NOT the SOT (Nodes 2 & 3 in this example), begin by stopping the UI and RabbitMQ. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop morpheus-ui  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   [root@node2 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop morpheus-ui  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   [root@node3 ~] morpheus-ctl stop rabbitmq
+   ```
+   ```
+2. Then on the SOT node, we need to copy the secrets for RabbitMQ. 
+
+   Begin by copying secrets from the SOT node to the other nodes.
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /etc/morpheus/morpheus-secrets.json  
+    "rabbitmq": {  
+      "morpheus_password": "***REDACTED***",  
+      "queue_user_password": "***REDACTED***",  
+      "cookie": "***REDACTED***"  
+    },
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /etc/morpheus/morpheus-secrets.json  
+     "rabbitmq": {  
+       "morpheus_password": "***node01_morpheus_password***",  
+       "queue_user_password": "***node01_queue_user_password***",  
+       "cookie": "***node01_cookie***"  
+     },
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] vi /etc/morpheus/morpheus-secrets.json  
+   "rabbitmq": {  
+     "morpheus_password": "***node01_morpheus_password***",  
+     "queue_user_password": "***node01_queue_user_password***",  
+     "cookie": "***node01_cookie***"  
+   },
+   ```
+   ```
+3. Then copy the erlang.cookie from the SOT node to the other nodes 
+
+   Node 1
+
+   ```
+   ```
+   root@node1: ~$ cat /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # 754363AD864649RD63D28
+   ```
+   ```
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+
+   Nodes 3
+
+   ```
+   ```
+   [root@node3 ~] vi /opt/morpheus/embedded/rabbitmq/.erlang.cookie  
+   # node01_erlang_cookie
+   ```
+   ```
+4. Once the secrets and cookie are copied from node01 to nodes 2 & 3, run a reconfigure on nodes 2 & 3. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+5. Next we will join nodes 2 & 3 to the cluster. 
+
+   IMPORTANT
+
+   The commands below must be run at root
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl stop rabbitmq  
+   [root@node2 ~] morpheus-ctl start rabbitmq  
+   [root@node2 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node2 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node02' ...  
+   [root@node2 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node02' with 'rabbit@node01' ...  
+   [root@node2 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node02' ...
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl stop rabbitmq  
+   [root@node3 ~] morpheus-ctl start rabbitmq  
+   [root@node3 ~] source /opt/morpheus/embedded/rabbitmq/.profile  
+   [root@node3 ~] rabbitmqctl stop_app  
+   # Stopping node 'rabbit@node03' ...  
+   [root@node3 ~] rabbitmqctl join_cluster rabbit@node01  
+   # Clustering node 'rabbit@node03' with 'rabbit@node01' ...  
+   [root@node3 ~] rabbitmqctl start_app  
+   # Starting node 'rabbit@node03' ...
+   ```
+   ```
+
+   NOTE
+
+   If you receive an error `unable to connect to epmd (port 4369) on node01: nxdomain (non-existing domain)` make sure to add all IPs and short (non-fqdn) hostnames to the `/etc/hosts` file to ensure each node can resolve the other hostnames.
+6. Next reconfigure Nodes 2 & 3 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl reconfigure
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl reconfigure
+   ```
+   ```
+7. The last thing to do is start the HPE Morpheus Enterprise UI on the two nodes that are NOT the SOT node. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl start morpheus-ui
+   ```
+   ```
+8. You will be able to verify that the UI services have restarted properly by inspecting the logfiles. A standard practice after running a restart is to tail the UI log file. 
+
+   Node 2
+
+   ```
+   ```
+   [root@node2 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Node 3
+
+   ```
+   ```
+   [root@node3 ~] morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   The UI should be available once the Morpheus logo is displayed in the logs. Look for the ascii logo accompanied by the install version and start time:
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2024  
+   timestamp: ****************************************
+   ```
+   ```
+
+## Embedded Elasticsearch
+
+Morpheus clusters OpenSearch automatically.
+
+## Load Balancer
+
+Configure your load balancer to distribute traffic between the app nodes.
+
+You can see some examples here: [Load Balancer Configuration](https://docs.morpheusdata.com/en/latest/getting_started/additional/additional_configuration.html#load-balancer-configuration)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json b/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
new file mode 100644
index 0000000..8de6d0a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+  "title": "Workloads: Apps Usage",
+  "ordinal": 70,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Apps Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DE45951-E56A-4651-AB77-F8C894E28788",
+        "clustering_title": "Workloads: Apps Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md b/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
new file mode 100644
index 0000000..ab7d4bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DE45951-E56A-4651-AB77-F8C894E28788.md
@@ -0,0 +1,32 @@
+# Workloads: Apps Usage
+
+![../_images/12appusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9916D4B0-7144-4088-98AC-2B2F2E780378-high.png)
+
+The Apps Usage dashboard lists all provisioned Apps that meet a set of filters and organizes them by Cloud. Totals for cost and resource usage of all relevant Apps can be viewed with a per-Cloud breakdown.
+
+## Filters
+
+Filter the Apps pulled into the dashboard by one or more of the following fields:
+
+- App name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for Apps that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among Apps meeting the dashboard filters
+- **APPS:** The total number of Apps represented in the dashboard
+- **INSTANCES:** The total number of Instances contained in all Apps meeting dashboard filters
+- **TOTAL COST:** The total cost of all selected Apps
+- **MEMORY:** The total memory allotted to selected Apps
+- **STORAGE:** The total storage allotted to selected Apps
+
+## Instance Usage List
+
+All Clouds with a currently-provisioned App which is selected in the dashboard filters are listed here. The name of the Cloud is listed along with its App count, the total memory, total storage, total CPU cores and price of the Apps provisioned in that Cloud are also listed.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json b/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
new file mode 100644
index 0000000..81afd0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+  "title": "Backups",
+  "ordinal": 326,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DEB33CC-132A-494C-B242-CA09B02E9333",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md b/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
new file mode 100644
index 0000000..7c4d145
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DEB33CC-132A-494C-B242-CA09B02E9333.md
@@ -0,0 +1,39 @@
+# Backups
+
+## Backup Settings
+
+The Backup settings page allows you enable or disable scheduled backups, select a default backup bucket, and administer global settings related to backups. Changes to global settings only affect new backups going forward and do not affect existing backups.
+
+NOTE
+
+Appliance backups are subject to a two-hour time limit to complete the backup. Automated backup attempts will be abandoned and will fail once this time limit is exceeded.
+
+IMPORTANT
+
+Appliances with an HA architecture containing multiple app nodes must ensure all nodes can access stored backups. By default, if no “Default Backup Bucket” configuration is made, backups are stored in `/var/opt/morpheus/bitcan`. If this path is local to the app nodes, all other app nodes would not be able to reach the backups. In such a case, one solution would be to create an NFS share for the `bitcan` directory for all app nodes. Another solution would be to make a “Default Backup Bucket” configuration selection, which all nodes would then use for backup storage and retrieval.
+
+### HPE Morpheus Enterprise Backup Settings
+
+Scheduled Backups
+:   Enable automatic scheduled backups for provisioned instances
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure instances for manual or scheduled backups
+
+Backup Appliance
+:   When enabled, a backup will be created for the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to view or edit settings related to the appliance backup
+
+Default Backup Bucket
+:   Select an existing bucket as the default for future backup runs. Click the `Infrastructure Storage` text link to add a new storage bucket to HPE Morpheus Enterprise if needed
+
+Default Backup Schedule
+:   Choose a default schedule interval for automated backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
+
+Default Backup Retention
+:   Choose the default number of backups to be retained for automated Instance and appliance backup jobs
+
+Default Synthetic Full Backup enabled
+:   When enabled, full synthetic backups will be on by default in addition to standard backups for supported workload types
+
+Default Synthetic Full Backup Schedule
+:   Choose a default schedule interval for full synthetic backups. The available selections in this dropdown menu are Execution Schedules defined in Library > Automation > Execute Scheduling
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json b/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
new file mode 100644
index 0000000..f471770
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+  "title": "Oracle Linux Virtualization Manager",
+  "ordinal": 464,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Linux Virtualization Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2DFC3858-043A-4053-AB10-F4534C7D7240",
+        "clustering_title": "Oracle Linux Virtualization Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md b/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
new file mode 100644
index 0000000..1846e94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2DFC3858-043A-4053-AB10-F4534C7D7240.md
@@ -0,0 +1,56 @@
+# Oracle Linux Virtualization Manager
+
+Oracle Linux Virtualization Manager (OLVM) allows administrators to manage and support a multi-host Oracle Linux KVM environment. HPE Morpheus Enterprise has developed and supports a plugin which allows an OLVM environment to be integrated and consumed as any other Cloud type within the HPE Morpheus Enterprise ecosystem. OLVM Clouds can be scoped to individual OLVM datacenters or scoped across all datacenters depending on configuration at the time of integration. Once integrated, HPE Morpheus Enterprise can automatically bring onboard OLVM resources including existing hosts, VMs (if desired), virtual images, networks and datastores.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Automatic Cloud sync
+- Datacenter scoping
+- Brownfield VM management
+- Clone VMs to images
+- Host monitoring
+- Datastore management
+- Hypervisor Remote Console
+- Lifecycle Management and Resize
+
+## Adding an OLVM Cloud
+
+Adding OLVM Clouds to HPE Morpheus Enterprise requires little more than the API URL and valid username and password credentials for a user with sufficient access to the resources that should be utilized by HPE Morpheus Enterprise. You’ll also need to ensure HPE Morpheus Enterprise can reach the OLVM at its API URL.
+
+Navigate to Infrastructure > Clouds and click + ADD. As long as the OLVM plugin has been added to the appliance and this Cloud type isn’t disabled in global settings (Administration > Settings), OLVM should be selectable as a Cloud type to add. Select it and click NEXT.
+
+At minimum, it’s required to configure the following to add the new Cloud:
+
+- **NAME:** A friendly name for the new OLVM Cloud in HPE Morpheus Enterprise
+- **API URL:** API access URL (ex. <https://xx.xx.xx.xx/ovirt-engine/api>)
+- **USERNAME:** Username for a OLVM service account, using an admin account will avoid any downstream permissions issues that could prevent features of the integration from working properly
+- **PASSWORD:** The password for the service account
+- **DATACENTER:** The Cloud may be scoped to a specific datacenter or to all datacenters
+
+You’ll know the API URL and credentials have been entered correctly when the DATACENTER dropdown becomes populated. Click NEXT and select a Group for the Cloud or create a new Group. Click NEXT to reach the review screen and then click COMPLETE.
+
+After completing the wizard, HPE Morpheus Enterprise will immediately begin to add the new Cloud and perform the first Cloud sync. Within a short time, existing workloads will be discovered and onboarded into HPE Morpheus Enterprise UI (if you’ve chosen to discover existing workloads). The Cloud is now ready to be used as a provisioning target or for day-two operations.
+
+## Monitoring the OLVM Cloud
+
+After integrating the Cloud, click into the Cloud detail page to see high level details about the OLVM environment including computed costs, number and health of hosts, resource utilization, and the number of running workloads.
+
+![../../../_images/cloudDetail1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-096B3009-F0C1-4217-9152-D59226017104-high.png)
+
+Additional tabs on the detail page allow administrators to view a list of hosts (and click into a host detail page, if desired), view a list of running VMs (and click into a VM detail page, if desired), view and manage networks and datastores, view or add Docker clusters, and view any containers running on Docker hosts.
+
+## Provisioning to the OLVM Cloud
+
+There are multiple ways to consume the new OLVM Cloud as a provisioning target. Adding an OLVM Cloud to HPE Morpheus Enterprise adds the OLVM Instance Type to the provisioning wizard. From the Instance list page (Provisioning > Instances), click + ADD and select “OLVM.”
+
+![../../../_images/olvmInsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6CDB3D9E-AFDF-45DC-830C-0356DCF91ABA-high.png)
+
+HPE Morpheus Enterprise syncs in all available Virtual Images from OLVM and presents them along with Datacenter and Cluster selections. Select the proper resource sizing and image template to provision a new VM into OLVM.
+
+![../../../_images/configIns.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E0A6E761-BCFB-4307-8E0F-76A9548B7230-high.png)
+
+In addition to using the built-in OLVM Instance Type, adding the OLVM Cloud allows administrators to add OLVM-type Layouts to new or existing Instance Types. Add new Layouts in the HPE Morpheus Enterprise Library (Library > Blueprints > Layouts). When adding a new Layout, select “OLVM” from the Technology dropdown to make this Layout available when an OLVM Cloud has been selected as the provisioning target. See the Library section of HPE Morpheus Enterprise UI documentation for more details on building out Library items.
+
+![../../../_images/layoutTech.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A46EF9A1-9EC9-416E-BB80-3B516BF4BB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json b/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
new file mode 100644
index 0000000..b242294
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+  "title": "Costing: Workload Costing",
+  "ordinal": 62,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Workload Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341",
+        "clustering_title": "Costing: Workload Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md b/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
new file mode 100644
index 0000000..fb8359e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.md
@@ -0,0 +1,26 @@
+# Costing: Workload Costing
+
+![../_images/5workloadcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-102FBE32-895E-4617-80D4-AA313E7BB572-high.png)
+
+The Workload Costing dashboard allows administrators to look at all or a subset of HPE Morpheus Enterprise-managed workloads to analyze their cost impact. Filters can be set to isolate a specific group of workloads and cost breakdowns are shown. Graphs are generated to reveal cost breakdowns of individual workloads or certain groups of workloads.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matched by search)
+- Group
+- Cloud
+- Tenant
+- Tag (Key). This is a required field and the top key in the list will be pre-selected by default
+- Value (tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all workloads that meet set filters:
+
+- **WORKLOADS:** The total number of workloads that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all workloads meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all workloads meeting dashboard filters
+- **TYPES:** The total number of workload types represented among workloads meeting set filters
+- **SIZES:** The total number of unique workload sizes represented among workloads meeting set filters
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json b/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
new file mode 100644
index 0000000..f5eaa90
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+  "title": "Communication Data",
+  "ordinal": 51,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md b/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
new file mode 100644
index 0000000..3aa1028
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.md
@@ -0,0 +1,156 @@
+# Communication Data
+
+The following page contains communication information between the HPE Morpheus Enterprise appliance, integrated technologies, managed machines, and services.
+
+## Communication Frequency and Configurability
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency and Configurability
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Elastic Search Check | Server Pull | Elastic Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | 5 minutes | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Push | ServiceNow | Sync HPE Morpheus Enterprise library items to ServiceNow catalog | Nightly | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
+
+## Ports and Protocols
+
+The following table contains communication port and protocol data between HPE Morpheus Enterprise appliance tiers, managed machines, and services. All communication to and from HPE Morpheus Enterprise goes thru the application tier with exception of inter-cluster communications for each of the HPE Morpheus Enterprise tiers when using a distributed architecture.
+
+Ports used to communicate with integrated technologies are those defined for the integration’s API. They are not represented in this table as many of these are configurable and may be different in each customer environment. Additionally, ports used to complete Morpheus checks are customizable and may vary for each check configured. They are also not represented in this table.
+
+Table 2. Ports and Protocols
+
+       | Source | Destination | Port | Protocol | Description |
+| --- | --- | --- | --- | --- |
+| User | Application Tier | 443 | TCP | User Access |
+| Morpheus Servers | DNS Servers | 53 | TCP | Domain Name Resolution |
+| Morpheus Servers | Time Source | 123 | TCP | Time Resolution |
+| Morpheus Servers | Web or Offline Installer | 80, 443 | TCP | Download repos and Morpheus packages (yum/apt repos) |
+| Managed Machine | Application Tier | 443 | TCP | Morpheus Agent Communications |
+| Managed Machine | Application Tier | 80, 443 | TCP | Agent Installation. (Requires port 80 only for Ubuntu 14.04) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Clout‐init (Linux) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation Cloudbase‐init (Windows) |
+| Managed Machine | Application Tier | N/A | N/A | Agent Installation VMtools |
+| Managed Machine | Application Tier | N/A | N/A | Static IP Assignment & IP Pools (Cloud‐init or VMware Tools) |
+| Managed Machine | Docker Image Repo | 443 | TCP | Applicable if using docker |
+| Managed Machine | Application Tier | 69 | TCP/UDP | PXE Boot (Forwarded to internal PXE port 6969) |
+| Application Tier | Managed Machine | 5985 | TCP | Agent Installation WinRM (Windows) |
+| Application Tier | Managed Machine | 22 | TCP | Agent Installation SSH (Linux) |
+| Application Tier | Managed Machine | 22, 3389, 443 | TCP | Remote Console (SSH, RDP, Hypervisor Console |
+| Application Tier | AWS S3 | 443 | TCP | Morpheus Catalog Image Download |
+| Application Tier | Hypervisor | 443 | TCP | Hypervisor hostname resolvable by Morpheus Application Tier |
+| Application Tier | Non‐ Transactional Database Tier | 443 | TCP | Applicable if using Amazon Elasticsearch Service |
+| Application Tier | Docker CE Repo | 443 | TCP | Applicable only when integrated with Docker |
+| Application Tier | Rubygems | 443 | TCP |  |
+| Application Tier | Morpheus Hub | 443 | TCP | (Optional) Telemetry data (Disabled only via license feature) |
+| Application Tier | Mail Server | 25 or 465 | SMTP | Send email from Morpheus |
+| Application Tier | postmarkapp | 2525 | TCP | Send email from Morpheus (such as alerts and password reset requests) when custom SMTP settings aren’t present |
+| Application Tier | Messaging Tier | 5672 | TCP | AMQP non‐TLS connections |
+| Application Tier | Messaging Tier | 5671 | TCP | AMQPS TLS enabled connections |
+| Application Tier | Messaging Tier | 61613 | TCP | STOMP Plugin connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Application Tier | Messaging Tier | 61614 | TCP | STOMP Plugin TLS enabled connections (Required only for Morpheus versions 4.2.1 or prior) |
+| Messaging Tier | Messaging Tier | 25672 | TCP | Inter‐node and CLI tool communication |
+| Administrator Web Browser | RabbitMQ Server Management | 15672 | TCP | Management plugin |
+| Administrator Web Browser | RabbitMQ Server Management | 15671 | TCP | Management plugin SSL |
+| Messaging Tier Cluster Node | Messaging Tier Cluster Node | 4369 | TCP | erlang (epmd) peer discovery service used by RabbitMQ nodes and CLI tools |
+| Application Tier | Non‐Transactional Database Tier | 9200 | TCP | Elasticsearch requests (Used in all cases except when utilizing AWS ES service) |
+| Application Tier | Non‐Transactional Database Tier | 443 | TCP | Elasticsearch requests (Used in all cases where ES is consumed as a PaaS service) |
+| Non‐Transactional Database Tier | Non‐Transactional Database Tier | 9300 | TCP | Elasticsearch Cluster |
+| Transactional Database Tier | Transactional Database Tier | 4567 | TCP/UDP | Write‐set replication traffic (over TCP) and multicast replication (over TCP and UDP). |
+| Transactional Database Tier | Transactional Database Tier | 4568 | TCP | Incremental State Transfer (IST) |
+| Application Tier | Transactional Database Tier | 3306 | TCP | MySQL client connections |
+| Backup Solution | Transactional Database Tier | 4444 | TCP | State Snapshot Transfer (SST) |
+| Application Tier | Integrated Technology | Varies | TCP | Integrations (Uses the port of the 3rd party systems API) |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json b/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
new file mode 100644
index 0000000..311f615
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+  "title": "Offline Installations and Upgrades",
+  "ordinal": 32,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html",
+  "topic_cluster": {
+    "clustering_title": "Offline Installations and Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B",
+        "clustering_title": "Offline Installations and Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md b/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
new file mode 100644
index 0000000..2af4ba1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.md
@@ -0,0 +1,104 @@
+# Offline Installations and Upgrades
+
+For customers that have an appliance behind a firewall/proxy that does not allow downloads from our Amazon download site, you can add the supplemental package to add the needed packages the standard Morpheus installer would have downloaded.
+
+## Offline Installation Requirements
+
+- NTP should be correctly configured and the server is able to connect to the NTP server in the ntp.conf file
+- The OS package repositories should be configured to use local LAN repository servers or the server should be able to receive packages from the configured repositories
+- The standard Morpheus and supplemental packages must be downloaded from another system and transferred to the Morpheus Appliance server
+- The supplemental package is additive, the full installer is also required
+
+NOTE
+
+The supplemental package is linked 1-to-1 to the appliance release. For example the supplemental package for 4.2.1-1 should be used with the appliance package 4.2.1-1
+
+## Offline Install
+
+## Ubuntu/Debian
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the Supplemental packages on to the appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_version_amd64.deb  
+   wget http://example_url/morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_version_amd64.deb  
+   sudo dpkg -i morpheus-appliance-supplemental_version_all.deb
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   # edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus log file located at /var/log/morpheus/morpheus-ui/current with the command `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
+
+## CentOS/RHEL
+
+### Procedure
+
+1. Download both the regular Morpheus Appliance package and the matching Supplemental package on to the Appliance server: 
+
+   ```
+   ```
+   wget http://example_url/morpheus-appliance_package_url.noarch.rpm  
+   wget http://example_url/morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+2. Install the both the Appliance package AND the Supplemental package. 
+
+   ```
+   ```
+   sudo rpm -i morpheus-appliance_package_url.noarch.rpm  
+   sudo rpm -i morpheus-appliance_package_supplemental_url.noarch.rpm
+   ```
+   ```
+3. Set the Morpheus UI appliance url (if needed, hostname will be automatically set). 
+
+   ```
+   ```
+   #Edit appliance_url to resolvable url (if not configured correctly by default)  
+   sudo vi /etc/morpheus/morpheus.rb
+   ```
+   ```
+4. Reconfigure the appliance to install required packages 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+### Results
+
+The Chef run should complete successfully. There is a small pause when Chef runs the resource remote\_file[package\_name] action create while Chef verifies the checksum. After the reconfigure is complete, the morpheus-ui will start and be up in a few minutes.
+
+NOTE
+
+Tail the morpheus-ui log file with `morpheus-ctl tail morpheus-ui` and look for the Morpheus ascii logo to know when the morpheus-ui is up.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json b/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
new file mode 100644
index 0000000..c2c62ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+  "title": "Default Unmanaged Network Support",
+  "ordinal": 403,
+  "parent_title": "Creating an HPE BMaaS Cloud",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html",
+  "topic_cluster": {
+    "clustering_title": "Default Unmanaged Network Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB",
+        "clustering_title": "Default Unmanaged Network Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md b/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
new file mode 100644
index 0000000..c937d76
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.md
@@ -0,0 +1,15 @@
+# Default Unmanaged Network Support
+
+HPE Morpheus Enterprise 8.0.13 and later automatically create a default unmanaged network during the **Bare Metal Cloud** creation process.
+
+When you select Unmanaged Network as the network mode, HPE Morpheus performs the following actions:
+
+- Creates a default unmanaged network automatically.
+- Configures the network to use DHCP for IP allocation.
+- Enables immediate selection of the network during instance provisioning.
+
+The below image shows the default unmanaged network automatically created during Bare-Metal cloud creation.   
+![Unmanaged Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9CB5E90B-9DED-4601-84AD-CA4E4538E297-high.png)
+
+The below image shows an untagged VLAN configuration with DHCP selected as the IP allocation method.   
+![Edit Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C186BB86-0721-493C-B4ED-10864ABF69F3-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json b/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
new file mode 100644
index 0000000..5a19d2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+  "title": "Storage Buckets",
+  "ordinal": 231,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Buckets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D",
+        "clustering_title": "Storage Buckets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md b/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
new file mode 100644
index 0000000..b4dc4e1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-30F59A1F-0573-4D88-A679-B5C5168BCE6D.md
@@ -0,0 +1,462 @@
+# Storage Buckets
+
+Storage Buckets are for Backup, Archives, Deployment and Virtual Images storage targets. Buckets can be browsed and files and folders can be uploaded, downloaded or deleted from the Bucket section. Retention Policies can be set on Storage Buckets for files to be deleted or backed up to another bucket after a set amount of time.
+
+## Supported Bucket Types
+
+- Alibaba
+- Amazon S3
+- Google Cloud Storage
+- Openstack Swift
+- Rackspace CDN
+
+## Alibaba Buckets
+
+### About this task
+
+To Add an Alibaba Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Alibaba from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   Alibaba Access Key
+
+   SECRET KEY
+   :   Alibaba Secret Key
+
+   REGION
+   :   Enter Alibaba Region for the Bucket
+
+   BUCKET NAME
+   :   Enter existing Alibaba Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   Create Bucket
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Amazon S3 Buckets
+
+### About this task
+
+To Add an Amazon S3 Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Amazon S3 from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   ACCESS KEY
+   :   AWS IAM Access Key
+
+   SECRET KEY
+   :   AWS IAM Secret Key
+
+   BUCKET NAME
+   :   Enter existing S3 Bucket name, or to add a new Bucket enter a new name and select Create Bucket.
+
+   CREATE BUCKET
+   :   Enable if the Bucket entered in BUCKET NAME does not exist and needs to be created. If enabled, select an AWS Region to create the Bucket in.
+
+   ENDPOINT URL
+   :   Optional endpoint URL if pointing to an object store other than amazon that mimics the Amazon S3 APIs.
+
+   Default Backup Target
+   :   Sets this Bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Google Cloud Storage Buckets
+
+### About this task
+
+NOTE
+
+Google Cloud Storage Buckets are associated with an existing GCP Cloud integration. Ensure the GCP Cloud integration is pre-existing before attempting to create a new Google Cloud Storage Bucket. On the initial integration and subsequent cloud syncs, Google Cloud Storage Buckets are automatically onboarded and updated.
+
+To add a Google Cloud Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Select the Storage link in the sub-navigation bar
+3. In the BUCKETS tab, Click the + ADD button
+4. Select Google Cloud Storage from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   A friendly name for the bucket in HPE Morpheus Enterprise
+
+   STORAGE SERVICE
+   :   Select the GCP cloud integration this bucket should be created in
+
+   PROJECT ID
+   :   Select the Project to create the group under, Projects are a GCP-specific concept and are logical grouping for your resources. Select any existing project associated with your selected GCP cloud integration
+
+   BUCKET NAME
+   :   The name for the bucket resource on the GCP side
+
+   LOCATION TYPE
+   :   Select Region, Dual-Region, or Multi-Region. Buckets with a Region location type will be stored in one GCP region, such as “us-east1 (South Carolina)”. Dual-Region and Multi-Region data is stored in two (or more, in the case of multi-region) GCP regions separated by a significant physical distance. Dual-Region and Multi-Region data is geo-redundant across the multiple selected regions
+
+   LOCATION
+   :   A selected GCP region (or regions, in the case of dual and multi-location data) where the data will be stored
+
+   STORAGE CLASS
+   :   Select Standard, Nearline, Coldline, or Archive. The appropriate storage class will depend on how frequently the bucket data is accessed and how long the type of data in the bucket is expected to be stored. More information on storage classes can be found in [GCP Documentation](https://cloud.google.com/storage/docs/storage-classes#descriptions)
+
+   ACTIVE
+   :   When marked, the bucket is available for use in HPE Morpheus Enterprise
+
+   DEFAULT BACKUP TARGET
+   :   Sets the bucket as the default storage option when creating backups at provision time or in the Backups section of HPE Morpheus Enterprise
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this Bucket as the default storage target when uploading deployment files in the Deployments section
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this bucket as the default storage target when uploading virtual images from the Virtual Images section, importing images from Instance actions, creating images with the Image Builder, and when creating new images from Migrations
+
+   RETENTION POLICY
+   :   Select None and the files in this bucket will never be deleted or backed up by HPE Morpheus Enterprise. When selecting ‘Backup Old Files’, HPE Morpheus Enterprise will backup files into another selected bucket once they reach a certain number of days old. When selecting ‘Delete Old Files’, HPE Morpheus Enterprise will delete any files that reach a certain number of days old
+
+## Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell EMC ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell EMC ECS Bucket.
+
+To Add a Dell EMC ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell EMC ECS bucket.
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Openstack Swift Buckets
+
+### About this task
+
+To Add an Azure Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Openstack Swift from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Openstack Swift Username
+
+   API KEY
+   :   Openstack Swift API Key
+
+   BUCKET NAME
+   :   Enter existing Openstack Swift Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   IDENTITY URL
+   :   Openstack Swift Identity URL
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Rackspace CDN Buckets
+
+### About this task
+
+To Add a Rackspace CDN Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Rackspace CDN from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   USERNAME
+   :   Rackspace CDN Username
+
+   API KEY
+   :   Rackspace CDN API Key
+
+   REGION
+   :   Enter Rackspace CDN Region
+
+   BUCKET NAME
+   :   Enter existing Rackspace CDN Bucket name, or to add a new Bucket enter a new name and select Create Bucket below.
+
+   Create Bucket
+   :   Enable if the name entered in BUCKET NAME does not exist and needs to be created.
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and then select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json b/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
new file mode 100644
index 0000000..92da0ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+  "title": "IPv6",
+  "ordinal": 38,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html",
+  "topic_cluster": {
+    "clustering_title": "IPv6",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D",
+        "clustering_title": "IPv6"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md b/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
new file mode 100644
index 0000000..0f69d4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.md
@@ -0,0 +1,43 @@
+# IPv6
+
+## Overview
+
+There may be situations where instances only have IPv6 routing available. HPE Morpheus Enterprise fully supports IPv6 for the appliance and agent comms.
+
+To enable IPv6 listener on the HPE Morpheus Enterprise appliance, you must modify the NGINX listeners.
+
+## Configuring NGINX Listeners
+
+### Procedure
+
+1. Confirm IPv6 is enabled and IP address is applied within the Morpheus underlying OS.
+2. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:80;
+   ```
+   ```
+3. Modify the `/opt/morpheus/embedded/nginx/conf/sites-available/morpheus-ssl.conf` file, and add the following listerning under the server block at the top: 
+
+   ```
+   ```
+   listen [::]:443 ssl;
+   ```
+   ```
+4. Restart the NGINX service: 
+
+   ```
+   ```
+   morpheus-ctl restart nginx  
+   ok: run: nginx: (pid 47868) 0s
+   ```
+   ```
+5. The site should now be resolvable via IPv6. To test you should be able to do the following: 
+
+   ```
+   ```
+   curl -k -6 https://[<IPv6 Address>]/ping  
+   MORPHEUS PING
+   ```
+   ```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json b/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
new file mode 100644
index 0000000..9992253
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+  "title": "Kubernetes Clusters",
+  "ordinal": 198,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3159C5BA-04D5-4035-9842-86197618F7D2",
+        "clustering_title": "Kubernetes Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md b/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
new file mode 100644
index 0000000..65a0c5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3159C5BA-04D5-4035-9842-86197618F7D2.md
@@ -0,0 +1,363 @@
+# Kubernetes Clusters
+
+## Requirements
+
+- Agent installation is required for Master and Worker Nodes. Refer to [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html) section for additional information.
+- Access to Cloud Front, Image copy access and permissions for System and Uploaded Images used in Cluster Layouts
+  :   Image(s) used in Cluster Layouts must either exist in destination cloud/resource or be able to be copied to destination by Morpheus, typically applicable for non-public clouds. For the initial provision, Morpheus System Images are streamed from Cloud Front through Morpheus to target destination. Subsequent provisions clone the local Image.
+- System Kubernetes Layouts require Master and Worker nodes to access to the following over 443 during K8s install and configuration:
+
+  - Morpheus Appliance url (443)
+  - <https://packages.cloud.google.com>
+  - <https://storage.googleapis.com>
+  - <https://docs.projectcalico.org>
+  - <https://openebs.github.io>
+  - <https://cloud.weave.works>
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
+
+## Creating Kubernetes Clusters
+
+### About this task
+
+Provisions a new Kubernetes Cluster in selected target Cloud using selected Layout.
+
+NOTE
+
+When deploying a highly-available Kubernetes cluster, it’s important to note that HPE Morpheus Enterprise does not currently auto-deploy a load balancer. Additionally, when HPE Morpheus Enterprise runs the `kubeadm init` command in the background during cluster provisioning, it also sets the `--control-plane-endpoint` flag to the first control plane node. This is a hard-coded behavior. To accomplish a highly-available cluster, users may wish to update the configured control plane endpoint, such as to a DNS name pointing to a load balancer. We are currently investigating updates to the product that would allow the user to specify such a DNS name prior to kicking off cluster provisioning. Additionally, users can circumvent this issue by configuring and deploying their own custom Cluster Layouts.
+
+HPE Morpheus Enterprise maintains a number of default Kubernetes Cluster Layouts which are updated frequently to offer support for current versions. AKS & GKE Kubernetes versions will dynamically update to the providers supported versions. HPE Morpheus Enterprise also supports creation of custom Kubernetes Cluster Layouts, a process which is described in detail in a later section.
+
+To create a new Kubernetes Cluster:
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clusters
+2. Select + ADD CLUSTER
+3. Select `Kubernetes Cluster`
+4. Select a Group for the Cluster
+5. Select NEXT
+6. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the Kubernetes Cluster
+
+   RESOURCE NAME
+   :   Name for Kubernetes Cluster resources
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+7. Select NEXT
+8. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   LAYOUT
+   :   Select from available layouts. System provided layouts include Single Master and Cluster Layouts.
+
+   PLAN
+   :   Select plan for Kubernetes Master
+
+   VOLUMES
+   :   Configure volumes for Kubernetes Master
+
+   NETWORKS
+   :   Select the network for Kubernetes Master & Worker VM’s
+
+   CUSTOM CONFIG
+   :   Add custom Kubernetes annotations and config hash
+
+   CLUSTER HOSTNAME
+   :   Cluster address Hostname (cluster layouts only)
+
+   POD CIDR
+   :   POD network range in CIDR format ie 192.168.0.0/24 (cluster layouts only)
+
+   WORKER PLAN
+   :   Plan for Worker Nodes (cluster layouts only)
+
+   NUMBER OF WORKERS
+   :   Specify the number of workers to provision
+
+   LOAD BALANCER
+   :   Select an available Load Balancer (cluster layouts only) }
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain override for DNS records
+
+       HOSTNAME
+       :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+
+   Autoscaler
+   :   The Cluster Autoscaler is a Kubernetes component that automatically adjusts the number of worker nodes in your cluster based on the resource requirements of your workloads. When application demand increases and existing nodes are unable to schedule new pods, the autoscaler adds additional nodes to the cluster. Conversely, when demand drops and nodes become underutilized, the autoscaler removes unnecessary nodes, helping to optimize resource usage and control costs.
+   :   NOTE
+
+       During scale down, the Cluster Autoscaler will skip nodes that have workloads which cannot be safely evicted, such as pods with persistent or local storage (e.g., Rook Ceph), or pods that are constrained by affinity or anti-affinity rules.
+   :   |  |  |
+       | --- | --- |
+       | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+       | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+       | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+9. Select NEXT
+10. Select optional Workflow to execute
+11. Select NEXT
+12. Review and select COMPLETE 
+
+    - The Master Node(s) will provision first.
+    - Upon successful completion of VM provision, Kubernetes scripts will be executed to install and configure Kubernetes on the Masters.
+      :   NOTE
+
+          Access to the sites listed in the [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892) section is required from Master and Worker nodes over 443
+    - After Master or Masters are successfully provisioned and Kubernetes is successfully installed and configured, the Worker Nodes will provision in parallel.
+    - Provision status can be viewed:
+      :   - From the Status next to the Cluster in Infrastructure  >  Clusters
+          - Status bar with eta and current step available on Cluster detail page, accessible by selecting the Cluster name from Infrastructure  >  Clusters
+    - All process status and history is available - From the Cluster detail page History tab, accessible by selecting the Cluster name from Infrastructure  >  Clusters and the History tab - From Operations - Activity - History - Individual process output available by clicking i on target process
+13. Once all Master and Worker Nodes are successfully provisioned and Kubernetes is installed and configured, the Cluster status will turn green. 
+
+    IMPORTANT
+
+    Cluster provisioning requires successful creation of VMs, Agent Installation, and execution of Kubernetes workflows. Consult process output from ``Infrastructure  >  Clusters - Details and morpheus-ui current logs at `Administration - Health - Morpheus Logs` for information on failed Clusters.
+
+### Intra-Kubernetes Cluster Port Requirements
+
+The table below includes port requirements for the machines within the cluster (not for the HPE Morpheus Enterprise appliance itself). Check that the following ports are open on Control-plane and Worker nodes:
+
+Table 1. Control‐plane node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 6443 | Kubernetes API Server | All |
+| TCP | Inbound | 6783 | Weaveworks |  |
+| TCP | Inbound | 2379‐2380 | etcd server client API | kube‐apiserver, etcd |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 10251 | kube‐scheduler | Self |
+| TCP | Inbound | 10252 | kube‐controller‐manager | Self |
+
+Table 2. Worker node(s)
+
+       | Protocol | Direction | Port Range | Purpose | Used By |
+| --- | --- | --- | --- | --- |
+| TCP | Inbound | 10250 | kubelet API | Self, Control plane |
+| TCP | Inbound | 30000‐32767 | NodePort Services | All |
+
+## Adding Worker Nodes
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `ADD (type) Kubernetes Worker` 
+
+   NAME
+   :   Name of the Worker Node. Auto=populated with `${cluster.resourceName}-worker-${seq}`
+
+   DESCRIPTION
+   :   Description of the Worker Node, displayed in Worker tab on Cluster Detail pages, and on Worker Host Detail page
+
+   CLOUD
+   :   Target Cloud for the Worker Node.
+4. Select NEXT
+5. Populate the following: 
+
+   NOTE
+
+   VMware sample fields provided. Actual options depend on Target Cloud
+
+   SERVICE PLAN
+   :   Service Plan for the new Worker Node
+
+   NETWORK
+   :   Configure network options for the Worker node.
+
+   HOST
+   :   If Host selection is enabled, optionally specify target host for new Worker node
+
+   FOLDER
+   :   Optionally specify target folder for new Worker node
+       :   Advanced Options
+           :   DOMAIN
+               :   Specify Domain override for DNS records
+
+               HOSTNAME
+               :   Set hostname override (defaults to Instance name unless an Active Hostname Policy applies)
+6. Select NEXT
+7. Select optional Workflow to execute
+8. Select NEXT
+9. Review and select COMPLETE
+
+### Results
+
+NOTE
+
+Ensure there is a default StorageClass available when using a Morpheus Kubernetes cluster with OpenEBS so that Kubernetes specs or HELM templates that use a default StorageClass for Persistent Volume Claims can be utilised.
+
+## Configure Autoscaler
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select `v MORE` for the target cluster
+3. Select `Configure Autoscaler`
+4. |  |  |
+   | --- | --- |
+   | ENABLE AUTOSCALER | Select this option to activate the Cluster Autoscaler functionality. When enabled, the autoscaler continuously monitors the cluster and automatically scales the number of worker nodes up or down as needed. |
+   | MINIMUM NODES | Specifies the minimum number of worker nodes that the autoscaler maintains in the cluster, even during periods of low workload. The cluster will not scale below this number of nodes. |
+   | MAXIMUM NODES | Specifies the maximum number of worker nodes that the autoscaler can add to the cluster. The cluster will not scale above this number, even if workload demand increases. This helps to control resource usage and costs. |
+5. Select `Apply`
+
+## Kubernetes Cluster Detail Pages
+
+The Kubernetes Cluster Detail page provides a high degree of monitoring and control over Kubernetes Clusters. This includes monitoring of all nodes in the Cluster, `kubectl` command line, account and role control, workload management, and more. The upper section of the page (which is persistent regardless of the currently-selected tab) provides high level costing and monitoring information, including a current aggregate metric for the CPU, memory and storage use.
+
+![../../_images/clusterDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-824D0DA3-5400-4EF0-BE66-A96F64902C89-high.png)
+
+The upper section also includes the ACTIONS menu which includes the following functions:
+
+- **REFRESH:** Forces a routine sync of the cluster status
+- **PERMISSIONS:** View and edit the Group, Service Plan, and Tenant access permissions for the cluster
+- **VIEW API TOKEN:** Displays the API token for the cluster
+- **VIEW KUBE CONFIG:** Displays the cluster configuration
+- **RUN WORKLOAD:** Run deployments, stateful sets, daemon sets, or jobs and target them to a specific namespace
+- **UPGRADE CLUSTER:** Upgrade the cluster to a higher version of Kubernetes
+
+  IMPORTANT
+
+  Kubelet configuration cleanup is required to upgrade clusters. The `--pod-infra-container-image` flag is deprecated from Kubernetes version 1.35.3. Upgrading clusters to v1.35.3 or later will fail if this deprecated flag is present in the Kubelet configuration. This flag must be manually removed from all nodes prior to initiating the upgrade process. See upgrade process below:
+  1. Edit the kubelet environment configuration file with `sudo vim /var/lib/kubelet/kubeadm-flags.env`
+  2. Locate the `KUBELET_KUBEADM_ARG`S entry and remove the following entry: `--pod-infra-container-image=registry.k8s.io/pause:3.10`
+  3. Save the file and exit the editor
+  4. Reload the configuration and restart the service with `sudo systemctl daemon-reload` and `sudo systemctl restart kubelet`
+  5. This process is repeated for all cluster nodes
+- **ADD KUBERNETES WORKER:** Launches a wizard which allows users to configure a new worker for the cluster
+
+Additional monitoring and control panes are located within tabs, some of which contain subtabs.
+
+- [Summary](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22330E1_D22331E1_D22332E1_D22333E1_D22334E1_D22335E1)
+- [Control](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22340E1_D22341E1_D22342E1_D22343E1_D22344E1_D22345E1)
+- [Access](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22350E1_D22351E1_D22352E1_D22353E1_D22354E1_D22355E1)
+- [Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22360E1_D22361E1_D22362E1_D22363E1_D22364E1_D22365E1)
+- [Workloads](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22370E1_D22371E1_D22372E1_D22373E1_D22374E1_D22375E1)
+- [Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22380E1_D22381E1_D22382E1_D22383E1_D22384E1_D22385E1)
+- [Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22390E1_D22391E1_D22392E1_D22393E1_D22394E1_D22395E1)
+- [Containers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22400E1_D22401E1_D22402E1_D22403E1_D22404E1_D22405E1)
+- [Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22410E1_D22411E1_D22412E1_D22413E1_D22414E1_D22415E1)
+- [History](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22420E1_D22421E1_D22422E1_D22423E1_D22424E1_D22425E1)
+- [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html#GUID-8FA4C005-9D2E-49AE-B13C-4AE07DA54275__DIV_D22430E1_D22431E1_D22432E1_D22433E1_D22434E1_D22435E1)
+
+### Summary
+
+The summary tab contains high-level details on health and makeup of the cluster. ![../../_images/clusterSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-42D2FAC8-D054-4AEC-8D10-59C6B15EE02A-high.png)
+
+### Control
+
+Contains the `kubectl` command line with ability to target commands to specific namespaces. The Control tab also contains the Packages subtab which displays the list of packages and their versions. ![../../_images/clusterControl.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-88388DAC-D1A7-4218-B17A-D605AB1D9095-high.png)
+
+### Access
+
+The Access Tab contains view and edit tools for Namespaces, accounts, roles, and role bindings. ![../../_images/clusterAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BC2EC859-76DA-4EC4-883C-DBA8BAD9DD52-high.png)
+
+### Nodes
+
+The nodes tab includes a list of master and worker nodes in the cluster, their statuses, and the current compute, memory, and storage pressure on each node. ![../../_images/clusterNodes.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-88E093F0-4EAB-4E6D-A023-F1C70F06812A-high.png)
+
+### Workloads
+
+View and edit existing Pods, Deployments, Replica Sets, Daemon Sets, Stateful Sets, and Jobs. Add new Deployments, Stateful Sets, Daemon Sets, and Jobs through the ACTIONS menu near the top of the Cluster Detail Page. ![../../_images/clusterWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5AA1E4AA-4AD5-4A7F-A274-2D7C01357494-high.png)
+
+### Network
+
+View, add, and edit Services, Endpoints, Ingress and Network Policies ![../../_images/clusterNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A94FC46E-8856-411E-8E6A-F2B6DBEAB45F-high.png)
+
+### Storage
+
+View, add, and edit Storage classes, Volume claims, Volumes, Config maps, and Secrets ![../../_images/clusterStorage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2A352500-C7FF-43CD-B91B-AD299208090B-high.png)
+
+### Containers
+
+View a list of containers running on the cluster and restart or delete them if needed. This list can be filtered by Namespace or a specific Worker if desired. ![../../_images/clusterContainers.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8D0ABC87-4D4D-4A4B-91A3-214698B516DD-high.png)
+
+### Monitoring
+
+View logs and events with filtering tools and search functionality available. ![../../_images/clusterMonitoring.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-02EEA1D6-F4BE-4060-AEBB-B6A2BD715EF6-high.png)
+
+### History
+
+View the Cluster lifecycle history. This includes lists of automation packages (Tasks and Workflows) run against the cluster or its nodes, the success of these scripts and the output. ![../../_images/clusterHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-394CC8A6-5257-4B4C-BF41-E10643BEEE8A-high.png)
+
+### Wiki
+
+View the HPE Morpheus Enterprise Wiki entry for this Cluster. This Wiki page may also be viewed in the Wiki section (Operations > Wiki). Edit the Wiki as desired, most standard Markdown syntax will be honored allowing the use of headings, links, embedded images, and more. ![../../_images/clusterWiki.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BAD395AC-5FAD-495D-B797-EEDA93C17B73-high.png)
+
+## Adding External Kubernetes Clusters
+
+HPE Morpheus Enterprise supports the management and consumption of Kubernetes clusters provisioned outside of HPE Morpheus Enterprise. These are referred to as External Kubernetes Clusters in HPE Morpheus Enterprise UI. This could be used, for example, to onboard and manage OpenShift clusters. In order to fully integrate the Kubernetes cluster with the HPE Morpheus Enterprise feature set, you may need to create a service account for HPE Morpheus Enterprise. Without first taking that step, some features may not work fully, such as listing all namespaces. The process for creating a service account and integrating the Cluster with HPE Morpheus Enterprise is described here.
+
+First, create the Service Account within the Kubernetes cluster:
+
+```
+```
+kubectl create serviceaccount morpheus
+```
+```
+
+Next, create the Role Binding:
+
+```
+```
+kubectl create clusterrolebinding morpheus-admin \  
+--clusterrole=cluster-admin --serviceaccount=default:morpheus \  
+--namespace=default
+```
+```
+
+With those items created, we can gather the API URL and the API token which will be used to add the existing cluster to HPE Morpheus Enterprise in the next step:
+
+```
+```
+kubectl config view --minify | grep server | cut -f 2- -d ":" | tr -d " "
+```
+```
+
+```
+```
+SECRET_NAME=$(kubectl get secrets | grep ^morpheus | cut -f1 -d ' ')  
+kubectl describe secret $SECRET_NAME | grep -E '^token' | cut -f2 -d':' | tr -d " "
+```
+```
+
+After finishing those steps, we can now create the external cluster in HPE Morpheus Enterprise. Navigate to Infrastructure > Clusters. Click + ADD CLUSTER and then select “External Kubernetes Cluster”. Set the following fields, you will have to advance through the pages of the wizard to see all fields indicated:
+
+- **GROUP:** A previously created HPE Morpheus Enterprise Group
+- **CLOUD:** A previously-integrated Cloud
+- **CLUSTER NAME:** A friendly name for the onboarded cluster in HPE Morpheus Enterprise UI
+- **RESOURCE NAME:** The resource name will be pre-pended to Kubernetes hosts associated with this cluster when shown in HPE Morpheus Enterprise UI
+- **LAYOUT:** Set an associated Layout
+- **API URL:** Enter the API URL gathered in the previous step
+- **API TOKEN:** Enter the API Token gathered in the previous step
+- **KUBE CONFIG:** Enter Kubeconfig YAML to authenticate the cluster
+
+The above are the required fields, others may be optionally configured depending on the situation. Complete the wizard and HPE Morpheus Enterprise will begin the process of onboarding the existing cluster into management within HPE Morpheus Enterprise UI. Once things are finalized and statuses are green, the cluster can be monitored and consumed as any other cluster provisioned from HPE Morpheus Enterprise.
+
+![../../_images/extKube.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E72E1043-FF51-4388-9D80-79CC7660C86A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json b/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
new file mode 100644
index 0000000..cbd2b27
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+  "title": "Tenant Roles",
+  "ordinal": 305,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2",
+        "clustering_title": "Tenant Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md b/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
new file mode 100644
index 0000000..d026ba8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3184BB84-FD3F-4A35-8D89-8EB3265CA3E2.md
@@ -0,0 +1,8 @@
+# Tenant Roles
+
+A Tenant Role sets the highest possible permissions for a Tenant. User Roles within that Tenant cannot exceed those of the Tenants assigned Tenant Role. Tenant Roles can be assigned to single or multiple Tenants, and do not apply to the Master Account.
+
+**Subtopics**  
+
+- **[To create a Tenant Role:](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-06D5442F-AE4E-4DD9-969E-34E1A20C80EC.html)**
+- **[Setting an Optional Landing URL](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json b/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
new file mode 100644
index 0000000..bd23360
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+  "title": "Nutanix Prism Element",
+  "ordinal": 463,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.html",
+  "topic_cluster": {
+    "clustering_title": "Nutanix Prism Element",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1",
+        "clustering_title": "Nutanix Prism Element"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md b/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
new file mode 100644
index 0000000..bd2d858
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-318C59CB-FC46-41E6-BC00-1AB2BAE9E2F1.md
@@ -0,0 +1,188 @@
+# Nutanix Prism Element
+
+## Overview
+
+Nutanix Prism Element simplifies datacenter infrastructure by integrating server and storage resources allowing applications to run at scale. HPE Morpheus Enterprise enhances Nutanix resources by allowing efficient and seamless deployment of virtualized or containerized applications, management of existing brownfield resources in Nutanix Clouds, pricing and cost tracking, and monitoring of running workloads.
+
+## Features
+
+- Virtual machine provisioning
+- Brownfield discovery
+- Containers
+- Backups / Snapshots
+- Datastores
+- Kubernetes
+- Resources Groups
+- Migrations
+- HPE Morpheus Enterprise costing and pricing
+- Auto Scaling
+- Load Balancing
+- Remote Console for hypervisor hosts and running workloads
+- Two-way Cloud sync
+- Lifecycle Management and Resize
+
+NOTE
+
+Prism Central is currently supported and is maintained as a separate, plugin-based Cloud integration. See the [Prism Central plugin page](https://share.morpheusdata.com/plugin/morpheus-nutanix-prism/about) on the HPE Morpheus Enterprise plugin share site for additional details and access to the plugin. There is also an [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/prismCentral/prismCentral.html) for that plugin here in HPE Morpheus Enterprise UI documentation.
+
+## Getting Started
+
+To get started, first confirm that a few prerequisite steps have been completed. The Nutanix cluster should be provisioned and available on the network. In a typical configuration, Nutanix will be available at the `https://fqdn:9440` URL. Have the credentials for an administrator service account available to integrate HPE Morpheus Enterprise with the Nutanix cluster. With those prerequisites already completed, you’re ready to add a Nutanix Cloud to HPE Morpheus Enterprise using the instructions in the next section.
+
+## Adding a Nutanix Cloud
+
+To start, navigate to the Cloud list page (Infrastructure > Clouds) and click + ADD. On the ADD CLOUD modal, you will at least need to provide a NAME for the Cloud in HPE Morpheus Enterprise along with the API URL and credentials. Other fields listed here are optional but may be needed for the Cloud to perform as desired in your environment.
+
+- **NAME:** A name for the Nutanix Cloud within HPE Morpheus Enterprise
+- **CODE:** A unique code for the cloud which is used in HPE Morpheus Enterprise API, CLI, and in automation scripts
+- **LABELS:** Select or create a new Label to apply to the Cloud. See [Labels documentation](https://docs.morpheusdata.com/en/latest/library/labels.html) for a complete description of the usefulness of Labels
+- **LOCATION:** An optional description field for the Cloud to hold location information
+- **VISIBILITY:** For multitenant environments, sets the visibility level for Tenants outside of the one the Cloud resources are assigned to
+- **TENANT:** If the visibility is set to private, this sets the Tenant the Cloud resources are assigned to
+- **ENABLED:** When checked, HPE Morpheus Enterprise will perform regular syncs with this Cloud and the Cloud will also be selectable as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** Indicates whether HPE Morpheus Enterprise should control the power state for provisioned VMs (not brownfield discovered VMs). If VMs are powered off for an unknown reason (that is, outside of HPE Morpheus Enterprise) they will be powered back on. Leave unchecked if you wish to manage workload power state outside of HPE Morpheus Enterprise
+- **API URL:** The URL for the Nutanix Prism API, typically in a format like `https://xx.xx.xx.xx:9440`
+- **CREDENTIALS:** Choose a pre-stored username/password credential set or enter a username/password set. If entering the credentials locally, you may also choose to securely store the credentials for later use. Depending on selection, additional fields will be added to facilitate that choice
+- **API VERSION:** Select the API version supported by your Nutanix environment to ensure HPE Morpheus Enterprise is not targeting endpoints which are incompatible with your environment
+- **INVENTORY EXISTING INSTANCES:** When checked, HPE Morpheus Enterprise will automatically onboard workloads which are already running in the Nutanix environment but which were provisioned outside of HPE Morpheus Enterprise. These may be brought under HPE Morpheus Enterprise management at a later time, if desired
+- **ENABLE HYPERVISOR CONSOLE:** When checked, enables remote console support directly to the hypervisor
+
+In addition to these basic settings, there are also some advanced options. These are similar but not identical for every Cloud type and some of them may not appear for Nutanix Clouds.
+
+### Advanced Cloud Options
+
+**Advanced Options**
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+**CUSTOM LOGOS**
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+**INVENTORY OPTIONS**
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+**Provisioning Command**
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+With the above configurations made, click NEXT. Choose to add the Cloud to an existing Group or to create a new Group and click NEXT once again. Finally, review the details of the new Cloud on the REVIEW tab and click COMPLETE if all looks good. At this point the new Cloud will be added to HPE Morpheus Enterprise and the initial Cloud sync will begin. On the Cloud list page (Infrastructure > Clouds), we will see the Cloud in an “OK” status once it is ready to be consumed in HPE Morpheus Enterprise as a provisioning target. Click into the Cloud detail page by clicking on the NAME of the Cloud from the list. Continue on to the next section for an overview of the details available on the Cloud detail.
+
+## Monitoring Nutanix Clouds
+
+On clicking into the Nutanix Cloud, you’ll land on the Summary tab. Here we can see high-level details including cost metrics for the month, general resource utilization information, and information on the number of hosts, workloads, and more that are currently running within the Cloud scope.
+
+![../../../_images/cloudDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1E122ED6-DF89-43B3-AB53-F645F37F8371-high.png)
+
+You’ll also notice the Clusters tab. Here you can see and click into any Docker or Kubernetes Clusters which are running on the Nutanix Cloud. HPE Morpheus Enterprise will see these clusters as provisioning targets themselves for containerized applications (as opposed to the Cloud itself for virtualized applications). You can also add new Kubernetes or Dockers clusters from this tab. HPE Morpheus Enterprise includes built-in Cluster Layouts but custom Cluster Layouts can also be created. There is a guide on creating your own custom Kubernetes Cluster Layouts in the Clusters section of HPE Morpheus Enterprise UI documentation.
+
+On the Hosts tab, you’ll see all Nutanix hypervisior hosts which are associated with the cluster. Host health metrics are viewable and we can click into individual hosts to see even greater detail on the individual host detail pages.
+
+The VM and Containers tabs show all current VM and container workloads across the cluster. When integrating the Cloud, if you opted to inventory existing workloads, discovered resources will appear here. If not (or if there simply are none), only HPE Morpheus Enterprise-provisioned workloads will appear here.
+
+## Provisioning New Workloads
+
+With the Cloud integrated, you’re already to provision new workloads. HPE Morpheus Enterprise comes pre-installed with a number of default library items designed to work with each supported Cloud integration type, including Nutanix. While this guide will not go through the process of using the provisioning wizard (see Provisioning > Instances page to start), you could provision a default workload to test functionality now if desired. Additionally, HPE Morpheus Enterprise will sync Virtual Images from Nutanix Clouds (Library > Virtual Images) and custom Library items may be built from these images. See the Library section of HPE Morpheus Enterprise documentation for more information on piecing together Instance Types, images, and automation scripts into cohesive and easily-consumed Library items.
+
+## Service Plans
+
+HPE Morpheus Enterprise includes a default set of Service Plans. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, and CPU cores. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Nutanix or create a new one. These all can be easily managed from the Administration > Plans & Pricing section.
+
+## Docker
+
+So far, this document has covered how to add the Nutanix cloud integration and has enabled users the ability to provision virtual machine-based Instances. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this, a Docker Host must first be provisioned into Nutanix (multiple are needed when dealing with horizontal scaling scenarios). As mentioned previously, these can be viewed or created from the Clusters tab of the Cloud detail page.
+
+To provision a Docker Host, simply navigate to the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a Nutanix Docker Host. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top. Just like with VMs, HPE Morpheus Enterprise includes default containerized items out of the box so provisioning to Docker hosts can be tested even before you’ve created your own container-based Library items.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, then the Agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a Nutanix Instance. From the Instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the Instance detail page. Snapshots taken outside HPE Morpheus Enterprise will be synced every five minutes (by default). To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json b/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
new file mode 100644
index 0000000..7973472
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+  "title": "Load Balancer Configuration",
+  "ordinal": 31,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancer Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83",
+        "clustering_title": "Load Balancer Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md b/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
new file mode 100644
index 0000000..4374b2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.md
@@ -0,0 +1,561 @@
+# Load Balancer Configuration
+
+For configurations with 2 or more Applications Nodes, a load balancer is recommended to ensure high availability (HA) from disruptions and upgrades. Below are the guidelines to configuring a load balancer for HPE Morpheus Enterprise but each configuration may differ based on the organization’s requirements.
+
+## Requirements
+
+- WebSockets enabled
+- Load Balance 443 (optionally redirect 80 to 443)
+
+  - SSL Termination (Offload), Bridging, and Passthrough are supported
+- Round-Robin or least connection distribution
+- HTTPS monitor `https://ip_address/ping` body for `MORPHEUS PING` or status of 200, for node operational health
+
+## Example configurations
+
+Below are a few examples of configuring load balancers to meet the needs of a HA configuration. The examples assume SSL bridging will be used, which means an SSL (TLS) certificate is presented by the load balancer to clients and the load balancer will communicate with the backend nodes via a different (possibly same) certificate. This configuration is recommended because the HPE Morpheus Enterprise application nodes will create self-signed certificates and the load balancer will present a valid certificate to end users. Additionally, all communication will be encrypted. This reduces the overhead of maintaining the certificates on the HPE Morpheus Enterprise application nodes, as the load balancer can ignore invaild certs on the application nodes. However, the certificates on the HPE Morpheus Enterprise application nodes are not required to be self-signed, they can be replaced with other trusted certificates following the [SSL Certificates](https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html) documentation.
+
+TIP
+
+The list below is not meant to be a complete list for all load balancers. The provided examples are common deployments that can be used for reference. The settings mentioned in the examples list the primary settings that may need to be configured, other settings are based on the organization’s needs requirements and own configuration.
+
+### F5 BIG-IP
+
+**Monitor**
+
+- **Type:** HTTPS
+- **Send String:** GET /ping
+- **Receive String:** MORPHEUS PING
+
+**Pool**
+
+- **Health Monitor:** Select monitor created in the **Monitor** section
+- **Load Balancing Method:** Least Connections (member) is recommended (alternatively Round Robin)
+- **Node Service Port:** 443/HTTPS
+
+**Virtual Server**
+
+- **Type:** Standard
+- **Service Port:** 443/HTTPS
+- **Protocol:** TCP
+- **Protocol Profile (Client):** tcp
+- **Protocol Profile (Server):** tcp
+- **HTTP Profile (Client):** http
+- **HTTP Profile (Server):** http
+- **SSL Profile (Client):** clientssl (or preferred profile with a trusted certificate)
+- **SSL Profile (Server):** serverssl
+- **Source Address Translation:** Auto Map
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### AWS Application Load Balancer (ALB)
+
+**Target Group**
+
+- **Target Type:** Instances
+- **Protocol/Port:** HTTPS/443
+- **Health Check Protocol:** HTTPS
+- **Health check path:** /ping
+- **Load balancing algorithm:** Least Outstanding Requests is recommended (alternatively Round Robin)
+
+**Load Balancer**
+
+- **Security Group:** Allow HTTPS/443 Inbound and Outbound
+- **Listener:** to the target group created in the **Target Group** section
+- **Security Policy:** ELBSecurityPolicy-2016-08
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### HAProxy
+
+**Example**`/etc/haproxy/haproxy.cfg`**configuration file**
+
+```
+```
+#---------------------------------------------------------------------  
+# Example configuration for a possible web application.  See the  
+# full configuration options online.  
+#  
+#   https://www.haproxy.org/download/1.8/doc/configuration.txt  
+#  
+#---------------------------------------------------------------------  
+#---------------------------------------------------------------------  
+# Global settings  
+#---------------------------------------------------------------------  
+global  
+    log         127.0.0.1:514 local2  
+    chroot      /var/lib/haproxy  
+    pidfile     /var/run/haproxy.pid  
+    maxconn     4000  
+    user        haproxy  
+    group       haproxy  
+    daemon  
+    # turn on stats unix socket  
+    stats socket /var/lib/haproxy/stats  
+    # utilize system-wide crypto-policies  
+    ssl-default-bind-ciphers PROFILE=SYSTEM  
+    ssl-default-server-ciphers PROFILE=SYSTEM  
+defaults  
+    mode                    http  
+    log                     global  
+    option                  httplog  
+    option                  dontlognull  
+    option http-server-close  
+    option forwardfor       except 127.0.0.0/8  
+    option                  redispatch  
+    retries                 3  
+    timeout http-request    10s  
+    timeout queue           1m  
+    timeout connect         10s  
+    timeout client          1m  
+    timeout server          1m  
+    timeout http-keep-alive 10s  
+    timeout check           10s  
+    maxconn                 3000  
+frontend main  
+    mode http  
+    bind *:443 ssl crt /etc/haproxy/ssl/combined_crt_key.pem  
+    default_backend             mybackend  
+backend mybackend  
+    mode http  
+    option      httpchk  
+    http-check  send meth GET uri /ping  
+    http-check  expect string MORPHEUS\ PING  
+    balance     leastconn  
+    server      app1 192.168.101.1:443 check ssl verify none  
+    server      app2 192.168.101.2:443 check ssl verify none  
+    server      app3 192.168.101.3:443 check ssl verify none
+```
+```
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
+
+### Azure Application Gateway
+
+In this example, it is assumed **End-To-End TLS Encryption** is being used, which means the Application Gateway will present a certificate to the clients and the backend nodes will present the **same** certificate.
+
+If a setting is not mentioned, it is assumed that the default can be maintained.
+
+**General Settings**
+
+- **Tier:** Standard V2
+- **Capacity type: Autoscale** or **Manual** are both supported
+- **HTTPS2:** Disabled
+
+**Frontend Configuration**
+
+- **Type:** Set **Public** if HPE Morpheus Enterprise should be accessilbe externally, otherwise choose **Private**
+- **Public IP Address:** Associate a previously create public IP or create a new one
+
+**Listener**
+
+- **Frontend IP:** Choose the IP created from the Frontend Configuration above
+- **Protocol:** HTTPS
+- **Port:** 443
+- **Certificate:**
+
+  - Upload the public certificate in **PFX** format
+  - This certificate should match the one presented by the backend nodes
+  - The certificate should include the entire chain, including the private key
+- **Listener type:** Basic
+- **Error page URL:** No
+
+**Backend Settings**
+
+- **Backend protocol:** HTTPS
+- **Backend port:** 443
+- **Use well known CA certificate:**
+
+  - If set to **Yes**, the certificate does not need to be uploaded in the settings. This must be a well known certificate provided by a well known certificate authority, not an internally generated certificate
+  - If set to **No**, ensure the certificate that is present on the backend nodes is uploaded to the Application Gateway. Note that the certificate should include the entire chain (CA, Intermediates, Certificate)
+- **Cookie-based affinity:** Disable
+- **Connection draining:** Enable
+- **Override with new host name:** No
+- **Use Custom probe:** No (one will be created next and will be assoicated during that configuration)
+
+**Health Probe**
+
+- **Protocol:** HTTPS
+- **Host:** Enter the host that is configured on the HPE Morpheus Enterprise application nodes. This same host that will be used on the Application Gateway Example: morpheus.mydomain.com
+- **Pick host name from backend settings:** No
+- **Pick port from backend settings:** Yes
+- **Path:** /ping
+- **Use probe matching conditions:** Yes
+- **HTTP response status code match:** 200-399
+- **Backend settings:** Choose the backend settings created above
+
+**Backend Pool**
+
+- The **Target Type** can either be **Virtual Machine** or **IP address or FQDN**
+
+  - If HPE Morpheus Enterprise is hosted in Azure, **Virtual Machine** will likely be the choice. The load balancer will need to able to communicate with the target
+  - If HPE Morpheus Enterprise is hosted on-premise, or outside of Azure, the **IP address or FQDN** can be used but the load balancer will need to able to communicate with the target
+
+**Important Items**
+
+- Ensure the backend virtual machines allow port 443 from the load balancer, otherwise a **502 error** may be seen
+- If using a wildcard certificate, you **must** use a custom health probe, as mentioned above, otherwise you may see the following error message:
+
+  `The Common Name (CN) of the backend server certificate does not match the host header entered in the health probe configuration (v2 SKU) or the FQDN in the backend pool (v1 SKU). Verify if the hostname matches with the CN of the backend server certificate.` More info: <https://techcommunity.microsoft.com/t5/fasttrack-for-azure/walkthrough-configuring-end-to-end-tls-with-application-gateway/ba-p/3269132>
+- As mentioned above, ensure the complete chain for the certificate is presented by HPE Morpheus Enterprise, otherwise you may see the following error message:
+
+  `The root certificate of the server certificate used by the backend does not match the trusted root certificate added to the application gateway. Ensure that you add the correct root certificate to whitelist the backend` More info: <https://learn.microsoft.com/en-us/answers/questions/150524/the-root-certificate-of-the-server-certificate-use>
+- Configuring the certificate on the HPE Morpheus Enterprise nodes
+
+  More info: <https://docs.morpheusdata.com/en/latest/getting_started/additional/morpheusSslCerts.html>
+- Additional reading:
+
+  <https://learn.microsoft.com/en-us/azure/application-gateway/certificates-for-backend-authentication> <https://learn.microsoft.com/en-us/azure/application-gateway/end-to-end-ssl-portal> <https://learn.microsoft.com/en-us/azure/application-gateway/ssl-overview>
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json b/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
new file mode 100644
index 0000000..06f4927
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+  "title": "Veeam",
+  "ordinal": 384,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.html",
+  "topic_cluster": {
+    "clustering_title": "Veeam",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA",
+        "clustering_title": "Veeam"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md b/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
new file mode 100644
index 0000000..d837ed7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-32ED3016-C3A4-405D-A275-AA3E782AC6EA.md
@@ -0,0 +1,102 @@
+# Veeam
+
+Veeam is a backup and replication platform designed to work with popular on-prem cloud providers, including VMware, Microsoft Hyper-V, and vCloud Director. HPE Morpheus Enterprise integrates with your existing Veeam appliance which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Veeam with HPE Morpheus Enterprise, sharing a Veeam integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from Veeam backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Veeam integration as the default backup target for compatible clouds
+- Select Veeam integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Veeam Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Integrations
+2. Select + ADD
+3. Select Veeam
+4. Fill in the following: 
+
+   Name
+   :   Friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, this integration will be active and available for use
+
+   API URL
+   :   IP or Hostname of the Veeam Enterprise Manager, must be HTTPS for VEEAM 10
+
+   Port
+   :   Port number configured to access the Veeam server, must be 9398 for VEEAM 10
+
+   Username
+   :   Username for an admin service account in Veeam
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise)
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that added the integration
+
+           Public
+           :   Available to Subtenants (primary tenant option only)
+5. Click SAVE
+
+### Results
+
+NOTE
+
+Veeam Backup Enterprise Manager must be installed in order to successfully integrate HPE Morpheus Enterprise with Veeam.
+
+IMPORTANT
+
+Once Veeam service has been integrated with HPE Morpheus Enterprise, Veeam server(s) will be available to select as the backup provider for VMware, Hyper-V, and vCloud Director cloud integrations (Infrastructure > Clouds > Edit a compatible Cloud). To enable Veeam backups, select the appropriate Veeam server as the “backup provider” for your cloud integrations as needed. Failure to do so will result in blank `Backup Repositories` and `Backup Job Templates` options when configuring Veeam Backups during provisioning.
+
+## Set Veeam as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Veeam integrations are supported as backup target for VMware, Hyper-V, and vCloud Director Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware, Hyper-V, or vCD Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Veeam integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-96E45BAD-D2AD-43F9-AE73-7AF6E41035F2-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Veeam is set as the backup provider, Veeam will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Veeam backup type
+- **Repository:** Select a repository synced from the Veeam backup provider associated with the Cloud
+- **Managed Server:** Select a managed server associated with the backup server selected in the previous step
+- **Backup Name:** A name for the backup in Morpheus, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A8EBDB01-089D-4518-B943-4DACE51F7528-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Veeam
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json b/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
new file mode 100644
index 0000000..b9d726a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+  "title": "Guides",
+  "ordinal": 359,
+  "parent_title": null,
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html",
+  "topic_cluster": {
+    "clustering_title": "Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010",
+        "clustering_title": "Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md b/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
new file mode 100644
index 0000000..8d37d5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.md
@@ -0,0 +1,6 @@
+# Guides
+
+**Subtopics**  
+
+- **[User Guides](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html)**
+- **[Integration Guides](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
new file mode 100644
index 0000000..f819976
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+  "title": "Boot Menus",
+  "ordinal": 251,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Menus",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3391053D-4F2A-49A4-8823-E63F708C55C4",
+        "clustering_title": "Boot Menus"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
new file mode 100644
index 0000000..d66dff7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.md
@@ -0,0 +1,21 @@
+# Boot Menus
+
+System-seeded Boot Menus are displayed and user-created Boot Menus can be edited and deleted. User-created Boot Menus are edited or deleted by clicking on the pencil or trash can icon in the appropriate row.
+
+## Adding a Boot Menu
+
+To begin, click + ADD. Available fields include:
+
+- NAME: Name of the Boot Menu
+- DESCRIPTION: Description of the Boot Menu
+- TYPE: Select between **bios, uefi, ipxe and grub**
+- ENABLED: Determines if the Boot Menu is active
+- DEFAULT MENU
+- ROOT MENU
+- MENU NAME
+- BOOT IMAGE
+- ANSWER FILE
+- MENU CONTENT
+- SUB MENUS
+
+Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json b/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
new file mode 100644
index 0000000..2c70bc0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+  "title": "Budgets",
+  "ordinal": 74,
+  "parent_title": "Costing",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html",
+  "topic_cluster": {
+    "clustering_title": "Budgets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157",
+        "clustering_title": "Budgets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md b/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
new file mode 100644
index 0000000..e8a4c71
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.md
@@ -0,0 +1,51 @@
+# Budgets
+
+Budgets provide insight into spending across their designated scope, allowing users to create and plan a budget targeted to their account, clouds, tenants, users, or groups.
+
+## Creating A Budget
+
+1. Navigate to Operations  >  Costing  >  Budgets
+2. Start a new budget by clicking + ADD
+
+   1. **Name**
+   2. **Description**
+   3. **Scope:** Here you can choose which construct this budget is tied to (Account, Tenant, Cloud, Group, or User)
+   4. **Period:** Currently “Year” is the only option
+   5. **Year:** Select a year to set budgets for future years. Alternatively, select “custom” to create a multi-year budget or input a custom fiscal year if required by your organization
+   6. **Forecast Model:** Optionally apply a forecast model to the Budget. When applied, forecasted amounts for each budget interval will be computed and graphical trend lines will be shown based on the model computation
+   7. **Interval:** Choose Month, Quarter, Year then fill in the budgeted amount for that interval (for quarter and year interval Budgets the entered amount is evenly split across the months in the given interval)
+3. Click SAVE CHANGES
+
+![../_images/createBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-18A42C5E-8C61-4ADA-AF78-23E743A230ED-high.png)
+
+## Multi-year Budgets
+
+Some organizations may need to create multi-year budgets or may need to set a fiscal year period. By default, annual budgets are tied to a calendar year (January - December) but HPE Morpheus Enterprise offers the flexibility of setting a fiscal year period when needed. When selecting a value from the YEAR dropdown in the add/edit budget modal, select “Custom” rather than one of the discreet years from the list. After selecting Custom, START DATE and END DATE fields allow the user to input any desired fiscal year period. Users can enter a period of up to three years using the start and end date bookends. The entered period must be one, two or three full years, partial years are not permitted.
+
+In the example below, I’ve created a three-year budget:
+
+![../_images/multiBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5E19B144-131B-4F0D-892B-9D10DB431658-high.png)
+
+## Budget Monitoring
+
+As the year (or years) goes on, existing Budgets can be reviewed to compare actual spend against the budgeted amount. To access the Budget detail, navigate to Operations > Costing > Budgets and select the desired Budget. The reported actual amount for a given month will be the same as the total cost reported for the month on the Invoice with the same scoping (for the current month, projected cost is used). Depending on the Cloud type, this figure can be pulled from a public clouds live costing API (such as with AWS, Azure, or GCP Clouds) or from the HPE Morpheus Enterprise in-built cost metering for private clouds (like VMware).
+
+Example Budget, Cloud-scoped:
+
+![../_images/budget.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4A12A8C3-AB86-4D4A-AF4E-432D5D9515BA-high.png)
+
+Example Cloud Invoice for the same month:
+
+![../_images/invoice.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-36CA0790-41CA-421C-9971-50062F8B82F4-high.png)
+
+## Cloud Budgets
+
+If you scope a budget to a Cloud, visit the Cloud summary tab in Infrastructure  >  Clouds  >  Select Cloud to see a cost-to-budget breakdown for that Cloud.
+
+![../_images/cloudBudget.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C731E3A8-F507-477B-93AB-71BC98DA37A0-high.png)
+
+## Budget Analytics
+
+In Operations  >  Analytics  >  Budget Analysis select scope (Account, Tenant, Cloud, Group, User) to view the budget analysis. If a budget exists for the selected scope, a cost breakdown against budgeted amounts will be shown.
+
+![../_images/budgetAnalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EA3645F4-5E49-4CFC-90CF-4A04880BF602-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json b/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
new file mode 100644
index 0000000..1ee5e1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+  "title": "Retrying Workflows",
+  "ordinal": 116,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html",
+  "topic_cluster": {
+    "clustering_title": "Retrying Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61",
+        "clustering_title": "Retrying Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md b/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
new file mode 100644
index 0000000..75d4931
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.md
@@ -0,0 +1,7 @@
+# Retrying Workflows
+
+When a Workflow fails, HPE Morpheus Enterprise allows users to retry from the failed Task. Access the Workflow execution from the executions list page (Provisioning > Executions), from the Executions tab of the Workflow detail page (Library > Automation > Workflows > Selected Workflow), or from the History tab on the Instance detail page (Provisioning > Instances > Selected Instance). From the execution, select the Retry button which looks like a clockwise circular arrow and is highlighted in the screenshot below. This can be very useful as it allows you to resume what could potentially be a very long running Workflow from a point of failure without needing to start from the beginning. Similarly, if a provisioned Instance is in a failed state due to a failure in an attached Workflow (such as a failed Task in the Provision phase of an attached Provisioning Workflow), the user can opt to resume the Tasks from the failure point after making a correction and restore the Instance to a successfully-provisioned state.
+
+Retry Workflow Tasks Video Demo
+
+![../../_images/retryTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-433AD4AB-C735-49B2-913B-302BF3209248-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json b/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
new file mode 100644
index 0000000..9dc4e52
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+  "title": "Prerequisites",
+  "ordinal": 399,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md b/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
new file mode 100644
index 0000000..c5bb6a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.md
@@ -0,0 +1,55 @@
+# Prerequisites
+
+Before integrating the HPE BMaaS with Morpheus Enterprise, verify that the following prerequisites are met to ensure successful deployment and operation.
+
+## Supported Hardware
+
+HPE BMaaS supports the following HPE ProLiant server platforms:
+
+- HPE ProLiant Gen10 Plus servers
+- HPE ProLiant Gen11 servers
+- HPE ProLiant Gen12 servers
+
+Ensure that servers are equiped with a supported HPE iLO version and are reachable over the network.
+
+## Network Connectivity
+
+The Morpheus Enterprise appliance must have:
+
+- Network connectivity to the iLO management interface of each ProLiant server
+- Network connectivity to the physical data network interfaces used for operating system provisioning
+- Proper routing and firewall rules allowing bidirectional communication between Morpheus and target servers
+- For environments using managed networking, additional connectivity to supported network switches (for example, HPE Aruba CX) is required.
+
+## Access Credentials
+
+Ensure the following credentials are available for each ProLiant server:
+
+- iLO IP address
+- iLO administrator username
+- iLO administrator password
+
+Credentials must have sufficient privileges to perform power operations, hardware inventory, and virtual media mounting.
+
+## Morpheus Platform Requirements
+
+- A supported version of Morpheus Enterprise is installed and operational
+- Administrative access to Morpheus for HPE BMaaS installation and configuration
+- Sufficient storage configured in Morpheus for OS images
+
+## Operating System Images
+
+OS ISO images available in the Morpheus Virtual Image Library
+
+## SSH Keys for Remote Login tothe Instance
+
+- Configure the SSH key access from an authorized host, for details see HPE Morpheus Enterprise documentation.
+- You can configure the SSH in HPE Morpheus under Infrastructure > Trust > Key Pairs
+
+## User Settings for OS (Linux and Windows)
+
+When provisioning a Linux- or Windows-based resource and opting to create users during the provisioning, the credentials entered in this section are used to create user during. For configuration, navigate to User Settings > Linux or User Settings > Windows Settings.
+
+## Proxy Configuration
+
+To configure proxy, navigate to Infrastructure > Network > Proxies.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json b/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
new file mode 100644
index 0000000..9539c9a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+  "title": "Trust",
+  "ordinal": 525,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3559161C-E53A-419A-B7E5-663F1440004F",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md b/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
new file mode 100644
index 0000000..2123e37
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3559161C-E53A-419A-B7E5-663F1440004F.md
@@ -0,0 +1,5 @@
+# Trust
+
+**Subtopics**  
+
+- **[CyberArk Conjur](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-030A6638-D9C6-492A-A021-8634B29738F7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json b/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
new file mode 100644
index 0000000..7ec93b3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+  "title": "Managing Instances",
+  "ordinal": 86,
+  "parent_title": "Instances",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76",
+        "clustering_title": "Managing Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md b/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
new file mode 100644
index 0000000..8dcc374
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.md
@@ -0,0 +1,92 @@
+# Managing Instances
+
+Instance actions allow you to perform numerous management tasks on instances. The actions available depend on the instance type, hypervisor, roles permissions, and instance state.
+
+Edit
+:   Edit the Name, Description, Environment, Group, Metadata, Tags, and Owner for the Instance.
+
+Delete
+:   Deletes the Instance.
+
+IMPORTANT
+
+Deleting an Instance will delete the actual VM’s or Containers and cannot be undone, unless a Delayed Removal policy has been applied prior to the Deletion. To delete Instances without deleting associated VM’s, delete the Instances VM record(s) from the Infrastructure section with “Remove Infrastructure” deselected and select “Remove Associated Instances” in the VM delete modal options. This will delete the records in HPE Morpheus Enterprise but leave the infrastructure in place.
+
+TIP
+
+You can change the owner of an instance easily by selecting the edit button and entering a new owner in the corresponding field.
+
+## Actions
+
+Available options in the Actions dropdown can include:
+
+Suspend
+:   Puts the VM in a suspended state without shutting down the OS.
+
+Stop/Start/Restart Service
+:   Stops, Starts or Restarts the service associated with the Instance Type.
+
+Stop/Start/Restart Server
+:   Stops, Starts or Restarts the Virtual Machine.
+
+Import as Image
+:   Clones and exports VM in its current state to target Storage provider and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Clone to Image
+:   Clones and converts VM in its current state to image in the source Cloud and adds Virtual Image Record with metadata matching the source Instance’s configuration.
+
+Lock/Unlock Instance
+:   A locked instance cannot be deleted until it is unlocked.
+
+Reconfigure
+:   The Reconfigure action allows service plan, disk, cpu, ram, networks and storage controller changes. Available options depend on the instance type and service plan configuration. Some resize actions require an instance restart.
+
+Clone
+:   Creates a new Instance from the Instance at its current state.
+
+Backup
+:   Immediately executes a backup of the Instance. Only available for Instances with backups enabled.
+
+Run Workflow
+:   Presents workflow options and then immediately runs selected Workflow on the Instance. Workflows can be created in the Library > Automationsection.
+
+Run Script
+:   Presents Script options and immediately executes selected Script on the Instance. Scripts can be created in the Library section.
+
+Apply Template
+:   Presents Template options and immediately applies selected Template to the Instance. Templates can be created in the Library section.
+
+Add Node
+:   Adds an additional node to the configuration. Additional options and configurations are required in the add node wizard depending on instance configuration and type.
+
+Eject Disk
+:   Ejects attached disk/iso.
+
+Add Slave
+:   Adds a database slave in the Instance.
+
+Change Master
+:   Changes the database Master node in an Instance.
+
+Clone to Template (VMware)
+:   Creates a new VMware Template from the Instance with corresponding HPE Morpheus Enterprise Virtual Image record.
+
+TIP
+
+Scrolling down in the Actions dropdown may be necessary to see all options.
+
+## Performing Instance Actions
+
+### Procedure
+
+1. Select the Provisioning link in the navigation bar.
+2. Click the Instance from the list of instances you wish to perform an action on.
+3. Click the Actions drop down button and select an Action.
+
+## Notes
+
+Every Instance has a Wiki section for adding useful information about the Instance. Wiki can be added by selecting the Wiki tab button on the bottom of Instance Detail pages. Instances with associated VMware VM’s will bi-directionally sync HPE Morpheus Enterprise Instance Wiki content and VMware VM Notes. See the [Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html) Section for more details.
+
+TIP
+
+Markdown Syntax is supported in Wikis.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json b/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
new file mode 100644
index 0000000..12b4d96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+  "title": "PowerDNS",
+  "ordinal": 486,
+  "parent_title": "DNS",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.html",
+  "topic_cluster": {
+    "clustering_title": "PowerDNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-367B7FE3-99E0-438C-87C0-43F9A179B552",
+        "clustering_title": "PowerDNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md b/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
new file mode 100644
index 0000000..44673f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-367B7FE3-99E0-438C-87C0-43F9A179B552.md
@@ -0,0 +1,78 @@
+# PowerDNS
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with PowerDNS to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in PowerDNS Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add PowerDNS Integration
+
+### About this task
+
+PowerDNS can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   PowerDNS
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   API HOST
+   :   URL of PowerDNS API. Example: `http://10.30.20.10:8081`
+
+   Token
+   :   PowerDNS API Token
+
+   Version
+   :   PowerDNS API Version
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, PowerDNS Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring PowerDNS with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json b/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
new file mode 100644
index 0000000..db8902f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+  "title": "Google Cloud Platform (GCP)",
+  "ordinal": 395,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-36BA3E37-26D3-488F-85C2-942C45119F02.html",
+  "topic_cluster": {
+    "clustering_title": "Google Cloud Platform (GCP)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-36BA3E37-26D3-488F-85C2-942C45119F02",
+        "clustering_title": "Google Cloud Platform (GCP)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md b/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
new file mode 100644
index 0000000..b1b5aed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-36BA3E37-26D3-488F-85C2-942C45119F02.md
@@ -0,0 +1,297 @@
+# Google Cloud Platform (GCP)
+
+## Integration Features
+
+- Provisioning Virtual Machines
+- Network tagging
+- Private and Local Images
+- Google VM Snapshots
+- Brownfield Inventory
+- Costing
+- Right-sizing
+- Shared Network Support
+
+## Requirements for Integration with HPE Morpheus Enterprise
+
+To integrate HPE Morpheus Enterprise with Google Cloud Platform, you will need the following. APIs are enabled in “APIs & Services” and must be enabled for all projects or the selected project (depending on your GCP Cloud integration settings). The next section contains more detailed steps for enabling API in the GCP web console.
+
+- The Compute Engine API enabled
+- The Cloud Resource Manager API enabled
+- The Cloud Billing API
+- The Identity and Access Management (IAM) API enabled
+- The BigQuery API enabled
+- The BigQuery Data Transfer API enabled
+- The Kubernetes Engine API enabled (required to provision GKE clusters)
+- Credentials for an IAM service account with Owner or Compute Admin role permissions
+- The private key and client email for the service account
+
+This integration guide goes through the process of configuring your account and obtaining the information necessary to integrate with HPE Morpheus Enterprise. Continue to the next section for a detailed look at enabling the APIs mentioned above.
+
+## Enabling the Required APIs
+
+In order to take full advantage of the HPE Morpheus Enterprise integration with Google Cloud, a number of APIs must be enabled within the GCP web console. It’s recommended that you enable all of the APIs listed in the preceding section regardless of the HPE Morpheus Enterprise feature set you intend to use. This will ensure you do not run into problems down the road stemming from a lack of access which may take time to diagnose.
+
+Log into the Google Cloud web console and navigate to the APIs and Services page. You may find this in the Quick access area of the welcome page or you can search for it as shown in the screenshot below.
+
+![../../../_images/apis.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C41DCEFF-896A-485D-B7F1-1097EF7E1E18-high.png)
+
+From the APIs and Services page, a list of enabled APIs and some details about your usage are shown. To enable new APIs, click + ENABLE APIS & SERVICES near the top of the window. Now on the API library page, search for the API you wish to enable. Here I’ve searched for the Kubernetes Engine API.
+
+![../../../_images/apisearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-11AC3447-F2D7-4C1D-B2FD-AF477146AB37-high.png)
+
+From the search results, click on the API you wish to enable to view its detail page. Click ENABLE. Once successfully enabled, the button will change to a MANAGE button. It may take a few moments for the API to be fully enabled. You may also be prompted to enable the Cloud Billing API or create an association with a Billing Account when enabling APIs. Go ahead and do so if prompted.
+
+![../../../_images/apienable.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-88E68260-6F46-43BB-8525-EF1D814408B5-high.png)
+
+Repeat this process until all required APIs (listed in the previous section) are enabled.
+
+## Creating a Service Account
+
+### Procedure
+
+1. From anywhere in the GCP web console, search for “service accounts” in the global search bar at the top of the window
+2. Click on the Service Accounts page (within the IAM & Admin stack)
+3. A list of existing service accounts within the selected Project is shown (if any)
+4. To create a new one, click + CREATE SERVICE ACCOUNT 
+
+   ![../../../_images/3create_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A3CD48CE-C19C-41EF-A6C2-286B2320673B-high.png)
+5. Enter at least a name for your new service and click CREATE AND CONTINUE 
+
+   ![../../../_images/4config_service_acct.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5E5FB1A4-AE19-4582-BF8A-CBDF18100628-high.png)
+6. After creating the service account, you’ll be prompted to set a role for the account. In order to fully integrate with HPE Morpheus Enterprise, you must use an account in the Owner role or the Compute Admin role
+7. Click CONTINUE 
+
+   ![../../../_images/5service_acct_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-172734F2-7D01-4F27-83CA-40CB948F05D2-high.png)
+8. Following creation of the service account, you’ll be taken back to the list of existing service accounts
+
+## Generating Keys and Integrating with HPE Morpheus Enterprise
+
+### Procedure
+
+1. From the list of service accounts, click the ellipsis button (…) to the right of a selected account
+2. Click “Manage Keys” 
+
+   ![../../../_images/6create_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-94F3D47B-1CE6-4C7C-A572-745199DE161D-high.png)
+3. On the Keys page, click “Add Key” and then “Create New Key”
+4. Select JSON format and click CREATE
+5. A JSON-formatted document will be downloaded, this document contains the Project ID, private key, and client email values needed to complete the integration process in the next step
+
+## Add a GCP Cloud
+
+### About this task
+
+NOTE
+
+The JSON-formatted document downloaded when creating a key for your service account contains all of the required values for completing the integration. Consult the above section on generating keys if needed.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select + CREATE CLOUD, select Google Cloud, and then click NEXT.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   PRIVATE KEY
+   :   The service account private key. Paste in the entire value between (but not including) the quotation marks in your downloaded JSON document, formatted like the following example: `-----BEGIN PRIVATE KEY-----(your_key)-----END PRIVATE KEY-----`
+
+   CLIENT EMAIL
+   :   The service account client email, ex: morpheus@morpheus.iam.gserviceaccount.com
+
+   PROJECT ID
+   :   Projects will auto-populate upon successful entry of the private key and client email. You can opt to scope the GCP integration to a single Project or select “All” to instead select the Project from the Resource Pool dropdown at provision time
+
+   REGION
+   :   Regions will auto-populate upon successful entry of the private key and client email. Select the appropriate region for this Cloud, if applicable. You can also opt to scope the GCP integration to all regions to allow users to select from any region at provision time
+
+   INVENTORY EXISTING INSTANCES
+   :   If checked, existing GCP resources will be inventoried and appear as unmanaged virtual machines in HPE Morpheus Enterprise.
+
+   If advanced options are not needed, click NEXT to advance to the Group selection page. Otherwise, continue on with this guide and review advanced or provisioning options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+4. After reviewing all options, click NEXT to advance to the Group selection page. Following Group selection, click COMPLETE to finish the integration process. If you’ve opted to inventory existing Instances, they will be viewable in HPE Morpheus Enterprise shortly. At this point, you are ready to provision new resources in Google Cloud Platform as needed!
+
+### Results
+
+IMPORTANT
+
+If you experience difficulties adding a GCP Cloud, review the above guide and ensure you’ve met all requirements for completing the integration. For example, if the Compute Engine API is not enabled, HPE Morpheus Enterprise will not accept credentials entered on the Create Cloud modal. If you repeatedly run into problems completing the integration process, review the above guide in its entirely and double check that each step is completed and your account meets all configuration requirements.
+
+## Create a GCP Project
+
+### About this task
+
+On initial integration, HPE Morpheus Enterprise will sync Projects and allow you to scope the integration to a specific Project or to scope the integration to all Projects. As time goes on, additional Projects are continually synced and can be managed from within the Resources tab on the Cloud detail page (Infrastructure > Clouds > Selected GCP Cloud). Within the Resources tab, users can edit some Project settings as well as delete Projects if needed.
+
+To create a new GCP Project:
+
+### Procedure
+
+1. Click + ADD RESOURCE POOL
+2. Enter a name value for the new Project
+3. Mark the “DEFAULT” box if you’d prefer newly provisioned Instances default to the new Project
+4. Enter a Project ID and ensure it meets the listed validation requirements
+5. Set a Parent value if the new Project should exist underneath a parent organization
+6. Finally, select a billing account
+7. Click SAVE CHANGES
+
+### Results
+
+After a few minutes, the new Project will be ready on the GCP side and HPE Morpheus Enterprise will be ready to provision new resources into it.
+
+## Enabling Live Costing for GCP
+
+GCP costing is done at the Billing Account level. Each Billing Account can be linked to one or more GCP Projects. All projects which are linked to the Billing Account will have their costing data available to HPE Morpheus Enterprise but if the GCP Cloud has been scoped to only one Project, HPE Morpheus Enterprise will ingest costing data only for that Project. Users can view the Billing Account linked to a particular project by clicking on the hamburger menu (main menu button in the far upper-left of the console window) and selecting billing. A pop-up window will give users the option to navigate to the Billing Account which is linked to the currently-selected Project.
+
+![../../../_images/costing1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9F511176-D2F9-4455-A1EB-7E9EA11219B3-high.png)
+
+Within the Billing Account, Standard Usage Cost must be enabled for HPE Morpheus Enterprise to access costing data. From the page for the appropriate Billing Account, click on Billing Export and then click “Edit Settings” under the “Standard usage cost heading”. Specify a project and create a dataset or specify an existing one. In doing this, you’re specifying a location for the dataset which will be for the entire billing account and not just for the Project the dataset resides in.
+
+![../../../_images/costing2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A3C3C708-1787-4F98-AA95-99BBBDDCEFAC-high.png)
+
+With configuration in the GCP console completed, we can now enable cost onboarding from the HPE Morpheus Enterprise side. Add or edit an existing GCP Cloud (Infrastructure > Clouds). Within the Advanced Options section, note the COSTING PROJECT and COSTING DATASET fields. When selecting a Project, associated datasets (if any) will automatically be loaded into the dropdown in the next field for selection. Additionally, the COSTING field should be set to “Sync Costing” rather than “Off”. Recall from the previous paragraph that this is merely pointing to the Project that houses the appropriate dataset. If your GCP Cloud in HPE Morpheus Enterprise is configured for all Projects, all costing data will be consumed for the Projects linked to the associated Billing Account (assuming those Projects have billing enabled). If the GCP Cloud in HPE Morpheus Enterprise is scoped to just one Project, only billing data for that Project will be onboarded. For this reason, the selected Costing Project can be (but is not necessarily) the Project to which the HPE Morpheus Enterprise Cloud is scoped.
+
+![../../../_images/costing3.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-15DC0856-A5ED-4CE5-8AFF-7C30A062DA86-high.png)
+
+## Windows Images
+
+HPE Morpheus Enterprise can add custom metatdata that will be injected into the unattend conf by GCP during provisioning. This is required for customizations including setting the Windows Administrator password during provisioning. GCP Windows Images must be syspreped using the `GCESysprep` command prior to image creation, and must have platform/os set on the Virtul Image record in HPE Morpheus Enterprise after image sync for successful customization and Agent Installation.
+
+### GCP Windows Requirements
+
+- GCP Windows Images must be syspreped using the `GCESysprep` command prior to Image creation in GCP. Refer to [Googles “creating-windows-os-image” doc](https://cloud.google.com/compute/docs/instances/windows/creating-windows-os-image).
+- Once the Image is synced into Morpheus, the Platform (Windows, Windows 2016 etc) must be set on the HPE Morpheus Enterprise Virtual Image record, otherwise linux is assumed and the metadata will not be generated correctly.
+- The Global Windows “Administrator” password must be set in HPE Morpheus Enterprise under `/admin/provisioning/settings` > Windows Settings > AdministratorPassword, or Administrator and password defined on the HPE Morpheus Enterprise Virtual Image record.
+- Be aware the unattend configuration during startup after sysprep delays causes a reboot and a prolonged finalization process during provisioning, and console/rdp may not be available during this time as windows is configuring.
+
+NOTE
+
+Some Google provided Windows Images have slow startups that cause the Morpheus Agent service to not start within the default 30 second service startup timeframe, including after initial reboot after sysprep/unattend configuration. This can be adjusted by running `New-ItemProperty -Path "HKLM:\SYSTEM\CurrentControlSet\Control\" -Name "ServicesPipeTimeout" -PropertyType DWORD -Value 180000` in powershell on the Windows Image.
+
+IMPORTANT
+
+Failure to use a GCP Windows Image that has not been sysprepped using `GCESysprep` will cause Agent Installation, Automation, and Console issues as HPE Morpheus Enterprise will not be able to set user credentials and authenticate.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json b/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
new file mode 100644
index 0000000..d8c0cc9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+  "title": "Adding hosts",
+  "ordinal": 185,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html",
+  "topic_cluster": {
+    "clustering_title": "Adding hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8",
+        "clustering_title": "Adding hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md b/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
new file mode 100644
index 0000000..408c347
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.md
@@ -0,0 +1,13 @@
+# Adding hosts
+
+The process of adding hosts to a pre-existing cluster is very similar to the process of provisioning the cluster initially. The requirements for the new worker node will be identical to the nodes initially added when the cluster was first provisioned. See the earlier sections in this guide for additional details on configuring the worker nodes.
+
+To add the host, begin from the HVM Cluster detail page (selected from the list at Infrastructure > Clusters). From the Cluster detail page, click ACTIONS and select “Add Worker”. Configurations required are the same as those given when the cluster was first created. Refer to the section above on “Provisioning the Cluster” for a detailed description of each configuration.
+
+Once HPE Morpheus Enterprise has completed its configuration scripts and joined the new worker node to the cluster, it will appear in a ready state within the Hosts tab of the Cluster detail page. When provisioning workloads to this Cluster in the future, the new node will be selectable as a target host for new Instances. It will also be an available target for managing placement of existing VMs running on the cluster.
+
+NOTE
+
+It’s useful to confirm all scripts related to creating the new host and joining the new host to the cluster completed successfully. To confirm, navigate to the detail page for the new host (Infrastructure > Clusters > Selected Cluster > HostsTab > SelectedHost) and click on the History tab. Confirm all scripts, even those run on the pre-existing hosts, completed successfully as it’s possible the new host was added successfully (green status) but failed in joining the cluster. When such a situation occurs it may appear adding the new host was successful though it will not be possible to provision workloads onto it due to not joining the cluster successfully.
+
+![../../_images/addHost.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-23D2DBDA-8840-4B60-A4B2-04DAD55E279E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json b/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
new file mode 100644
index 0000000..90d22b3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+  "title": "Attaching Logs to Case",
+  "ordinal": 347,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html",
+  "topic_cluster": {
+    "clustering_title": "Attaching Logs to Case",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6",
+        "clustering_title": "Attaching Logs to Case"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md b/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
new file mode 100644
index 0000000..0fe63aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.md
@@ -0,0 +1,11 @@
+# Attaching Logs to Case
+
+When submitting a case it is critical to attach the relevant logs. The logs can be found at `/var/log/morpheus/morpheus-ui/current`. Logs can be attached to the case at anytime.
+
+When submitting logs please reproduce the error right before capturing and sending the log file. This will ensure the activity that took place and resulted in an error is contained in the logs.
+
+Log rotation takes the current file each night or after it’s a certain size and compresses them. The `*.s` files in the current directory are rotated and zipped logs that can be sent as is.
+
+The logs can also be captured from the Morpheus UI. Under Administration > Health > Morpheus Logs. Please copy relevant logs and add to case as an attachment.
+
+![../_images/Morpheus-Health-Logs.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json b/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
new file mode 100644
index 0000000..9fe3a4c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+  "title": "Role Permissions",
+  "ordinal": 106,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md b/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
new file mode 100644
index 0000000..846b505
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.md
@@ -0,0 +1,5 @@
+# Role Permissions
+
+The User Role Permission ‘Provisioning: Tasks FULL’ is required to create, edit and delete tasks.
+
+Tasks Types that can execute locally against the HPE Morpheus Enterprise Appliance have an additional Role Permission: `Tasks - Script Engines`. Script Engine Task Types will be hidden for users without `Tasks - Script Engines` role permissions.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json b/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
new file mode 100644
index 0000000..a27d6ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+  "title": "Servers",
+  "ordinal": 235,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-37CA1665-B331-452A-AA3D-59608D85F006.html",
+  "topic_cluster": {
+    "clustering_title": "Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-37CA1665-B331-452A-AA3D-59608D85F006",
+        "clustering_title": "Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md b/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
new file mode 100644
index 0000000..11bccce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-37CA1665-B331-452A-AA3D-59608D85F006.md
@@ -0,0 +1,112 @@
+# Servers
+
+## Add Storage Server
+
+### Adding 3Par Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+#### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server
+       :   Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
+
+### Adding Dell EMC Isilon Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab. Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json b/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
new file mode 100644
index 0000000..8bfe116
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+  "title": "Creating Custom Cluster Layouts",
+  "ordinal": 145,
+  "parent_title": "Cluster Layouts",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Custom Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-382BFCD5-DE8D-4C54-B3D6-704970132153",
+        "clustering_title": "Creating Custom Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md b/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
new file mode 100644
index 0000000..f7e8cd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.md
@@ -0,0 +1,207 @@
+# Creating Custom Cluster Layouts
+
+Custer Layouts can be built for an infinite number of use cases and targeting a wide range of configurations or provisioning technologies. However, it still may help to see an example Cluster Layout created. In this section, we’ll create an example Cluster Layout which provisions a Kubernetes Cluster to a VMware vCenter Cloud containing a master node and three worker nodes. We’ll build out two Node Types to embed in the Cluster, one master and one worker. Within the Node Types, we will embed Script Templates needed to configure the nodes as they are provisioned and allow the workers to join the cluster. Script Templates can be configured to execute at various phases of the lifecycle of the node, similar to a Provisioning Workflow, so HPE Morpheus Enterprise can orchestrate the whole process.
+
+## Creating Script Templates
+
+We’ll first start by creating the necessary Script Templates. In this example, I’ll use a generic prep script that both the master and worker nodes will utilize and then I’ll create three additional scripts (two for the master node and one for the worker nodes) to accomplish various Kubernetes cluster setup tasks (`kubeadm init`, creating Role Bindings, joining workers to the cluster, etc.). I’ll briefly describe each here and step through the process of creating the Script Template objects in HPE Morpheus Enterprise.
+
+To begin a new Script Template, navigate to Library > Templates > Script Templates and click + ADD. All of the scripts used in this example will be “Bash” type, run as user “root” and with SUDO marked.
+
+The first script to add will be a prep script that both the master and worker nodes will use. This script turns swap off, installs `containerd`, runs updates, sets network config, and installs `kubelet`, `kubeadm`, and `kubectl`. Set this script to run in the PreProvision phase. The complete script, named “k8sprep” in my example can be viewed below:
+
+### k8sprep Script Template
+
+```
+```
+function wait_for_dpkg() {  
+  FRONT_END_LOCK_FILE=/var/lib/dpkg/lock-frontend  
+  DPKG_LOCK_FILE=/var/lib/apt/lists/lock  
+  echo "checking for dpkq lock existence..."  
+  if [ -e "$DPKG_LOCK_FILE" ]; then  
+    while fuser $DPKG_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $DPKG_LOCK_FILE..."  
+      sleep 1  
+    done  
+  fi  
+  echo "checking for dpkq lock-frontend existence..."  
+  if [ -e "$FRONT_END_LOCK_FILE" ]; then  
+    while fuser $FRONT_END_LOCK_FILE >/dev/null 2>&1 ; do  
+      echo "Waiting for lock $FRONT_END_LOCK_FILE..."  
+      sleep 1  
+    done  
+    echo "force removing lock $FRONT_END_LOCK_FILE"  
+    sudo rm $FRONT_END_LOCK_FILE  
+    sleep 5  
+  fi  
+}  
+  # Swap must be turned off see https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo swapoff -a ; sudo sed -i '/ swap / s/^/#/' /etc/fstab  
+  # Install containerd packages from Debian sse: https://docs.docker.com/engine/install/ubuntu/  
+wait_for_dpkg  
+sudo apt-get update  
+sudo apt-get install ca-certificates curl gnupg lsb-release -y  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg  
+sudo mkdir -m 0755 -p /etc/apt/keyrings  
+sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpgsudo  
+echo   "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu \  
+$(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null  
+sudo apt-get update  
+  # the Docker documentation advises to install the whole Docker runtime environment but containerd.io is sufficient  
+sudo apt-get install containerd.io -y  
+  # Prepare the necessary network config see: https://kubernetes.io/docs/setup/production-environment/container-runtimes/  
+sudo cat <<EOF | sudo tee /etc/modules-load.d/k8s.conf  
+overlay  
+br_netfilter  
+EOF  
+sudo modprobe overlay  
+sudo modprobe br_netfilter  
+sudo cat <<EOF | sudo tee /etc/sysctl.d/k8s.conf  
+net.bridge.bridge-nf-call-iptables  = 1  
+net.bridge.bridge-nf-call-ip6tables = 1  
+net.ipv4.ip_forward                 = 1  
+EOF  
+  # Apply sysctl params without reboot  
+sudo sysctl --system  
+  # Install kubeadm follwing the K8s documentation: https://kubernetes.io/docs/setup/production-environment/tools/kubeadm/install-kubeadm/  
+sudo apt-get install -y apt-transport-https ca-certificates curl  
+sudo curl -fsSL  https://packages.cloud.google.com/apt/doc/apt-key.gpg|sudo gpg --dearmor -o /etc/apt/trusted.gpg.d/k8s.gpg  
+sudo echo "deb https://apt.kubernetes.io/ kubernetes-xenial main" | sudo tee /etc/apt/sources.list.d/kubernetes.list  
+sudo apt-get update  
+sudo apt-get -y install -y kubelet=1.26.1-00 kubeadm=1.26.1-00 kubectl=1.26.1-00  
+sudo apt-mark hold kubelet kubeadm kubectl  
+  # see https://github.com/etcd-io/etcd/issues/13670  
+cat << EOF | sudo tee /etc/containerd/config.toml  
+version = 2  
+  [plugins]  
+  [plugins."io.containerd.grpc.v1.cri"]  
+   [plugins."io.containerd.grpc.v1.cri".containerd]  
+      [plugins."io.containerd.grpc.v1.cri".containerd.runtimes]  
+        [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc]  
+          runtime_type = "io.containerd.runc.v2"  
+          [plugins."io.containerd.grpc.v1.cri".containerd.runtimes.runc.options]  
+            SystemdCgroup = true  
+EOF  
+sudo systemctl restart containerd
+```
+```
+
+Next we’ll add a script called “kubeadm-init” in this example which will create and configure some working directories, set the `kubeadm` config yaml, and run `kubeadm init`. Set this script to run in the PreProvision phase as well. The complete script can be viewed below:
+
+### kubeadm-init Script Template
+
+```
+```
+mkdir -p <%=morpheus.morpheusHome%>/kube  
+mkdir -p <%=morpheus.morpheusHome%>/kube/working  
+mkdir -p <%=morpheus.morpheusHome%>/.kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/kube/working  
+cat <<EOF | sudo tee <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+# kubeadm-config.yaml  
+kind: ClusterConfiguration  
+apiVersion: kubeadm.k8s.io/v1beta3  
+kubernetesVersion: v1.26.1  
+networking:  
+  serviceSubnet: "10.96.0.0/16"  
+  podSubnet: "10.244.0.0/24"  
+  dnsDomain: "cluster.local"  
+apiServer:  
+  extraArgs:  
+    authorization-mode: "Node,RBAC"  
+clusterName: "example-cluster"  
+---  
+kind: KubeletConfiguration  
+apiVersion: kubelet.config.k8s.io/v1beta1  
+cgroupDriver: systemd  
+EOF  
+sudo kubeadm init --config <%=morpheus.morpheusHome%>/kube/working/kubeadm-config.yaml  
+sudo cp -i /etc/kubernetes/admin.conf <%=morpheus.morpheusHome%>/.kube/config &&  
+sudo chown <%=morpheus.morpheusUser%>:<%=morpheus.morpheusUser%> <%=morpheus.morpheusHome%>/.kube/config
+```
+```
+
+Lastly, we’ll add a setup script for the Kubernetes master node called “k8s-master-setup” for this example. This script creates the service account and role bindings. Set this script to run in the PostProvision phase and view the complete script below:
+
+### k8s-master-setup Script Template
+
+```
+```
+#create a service account  
+cd <%=morpheus.morpheusHome%>  
+#kubectl -n kube-system create sa morpheus  
+kubectl create sa morpheus  
+cat <<EOF | tee <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+apiVersion: v1  
+kind: Secret  
+metadata:  
+  name: morpheus-token  
+  annotations:  
+    kubernetes.io/service-account.name: morpheus  
+type: kubernetes.io/service-account-token  
+EOF  
+kubectl create clusterrolebinding serviceaccounts-cluster-admin --clusterrole=cluster-admin --group=system:serviceaccounts  
+kubectl create -f <%=morpheus.morpheusHome%>/kube/morpheus-sa.yaml  
+kubectl apply -f https://raw.githubusercontent.com/projectcalico/calico/v3.25.0/manifests/calico.yaml
+```
+```
+
+The three scripts we’ve just created will prepare the master node for our cluster. We now need an additional script that will prepare the worker nodes and join them to the cluster. The worker nodes will also use the “k8s-prep” script we added in the very first step which you’ll see in the next step when we create the node types.
+
+Add a fourth script which I’ve called “k8s-join” for this example. This script takes advantage of a special `joinCommand` variable as you’ll see when you view the full script. If you want to see exactly what this does later, you can create a new Bash script Task that echoes out that variable and run it against an existing Kubernetes worker node VM (`echo "<%=morpheus.kubernetes.joinCommand%>"`). Set this script to run in the PostProvision phase and view the full script below:
+
+### k8s-join Script Template
+
+```
+```
+sudo <%=morpheus.kubernetes.joinCommand%>
+```
+```
+
+This completes the needed Script Templates which we will set on two new Node Types in the next step. Continue on to the next section.
+
+## Creating Node Types
+
+With the Script Templates created we now need to make two new Node Types, one for the master node and one for the worker nodes. In this example case, we don’t need to add a new Virtual Image because we can use one of the preinstalled system images for Ubuntu on VMware vCenter which will work fine. Node Types are created in Library > Blueprints > Node Types. Once there, click + ADD. Within the modal for the new Node Type, configure the following:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the master node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep”, “kubeadm-init” and “k8s-master-setup” Script Templates (you may have called them something different)
+
+Finally, click SAVE CHANGES.
+
+Repeat the process to create a second Node Type. The second time around, use the following configurations:
+
+- **NAME:** Provide a name for the Node Type, can be anything to denote this is the worker node
+- **SHORT NAME:** A shortened version of the name without any spaces
+- **VERSION:** The version number you wish to apply for this particular Node Type which is useful if you iterate on your Node Types at any point
+- **TECHNOLOGY:** For this example case, VMware. Once set, additional options will appear
+- **VM IMAGE:** A pre-installed Ubuntu system image will work
+- **SCRIPTS:** Using the typeahead field, set the “k8sprep” and “k8s-join” Script Templates (you may have called them something different)
+
+Once done, click SAVE CHANGES to save the second Node Type. With the pieces in place, we are now ready to create the Cluster Layout object itself. Continue on to the next section.
+
+## Creating a Cluster Layout
+
+At this point we can create the Cluster Layout object in HPE Morpheus Enterprise and attach the Node Types we’ve just created (which themselves have our Script Templates applied). Cluster Layouts are created in Library > Blueprints > Cluster Layouts. Click + ADD and configure the following:
+
+- **NAME:** Provide a name for the Cluster Layout, can be anything to denote this is a Kubernetes cluster
+- **VERSION:** The version number you wish to apply to this Cluster Layout which is useful if you later iterate on this Cluster Layout
+- **CLUSTER TYPE:** Kubernetes Cluster
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4096 MB
+- **INPUTS:** Use the typeahead field to add configured Inputs to the Cluster Layout
+- **MASTER NODES:** Use the typeahead field to find the Kubernetes master Node Type we just created
+- **WORKER NODES:** Use the typeahead field to find the Kubernetes worker Node Type we just created. Set the “Count” value to three (3) since we wish to have three worker nodes in this cluster
+- **CLUSTER PACKAGES:** Use the typeahead field to add configued Cluster Packages to the Cluster Layout. Cluster Packages are created in the [Templates section](https://docs.morpheusdata.com/en/latest/library/templates/templates.html)
+- **SPEC TEMPLATES:** Use the typeahead field to add Spec Templates to the Cluster Layout
+
+Click SAVE CHANGES to save the Cluster Layout.
+
+## Testing and Wrap-Up
+
+At this point we are finished and we have a viable Kubernetes cluster that we can deploy with just one click. To add a new managed cluster to this HPE Morpheus Enterprise environment, navigate to Infrastructure > Clusters. To provision a cluster from the layout we just created, click + ADD CLUSTER and select “Kubernetes Cluster” from the dropdown menu. Make the appropriate selections to target the new cluster to an existing VMware vCenter Cloud and complete the wizard. Once complete, the new cluster will be visible on your clusters list page and from there you can drill into the detail page to view relevant details about the cluster including monitoring metrics, current workloads, and more.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json b/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
new file mode 100644
index 0000000..0d66782
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+  "title": "Dell ECS",
+  "ordinal": 521,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html",
+  "topic_cluster": {
+    "clustering_title": "Dell ECS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF",
+        "clustering_title": "Dell ECS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md b/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
new file mode 100644
index 0000000..8378aa5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.md
@@ -0,0 +1,246 @@
+# Dell ECS
+
+## Overview
+
+HPE Morpheus Enterprise integrates with DELL EMC ECS via the ECS api. This allows Morpheus to talk directly to the ECS services.
+
+When you add a ECS Server, HPE Morpheus Enterprise will sync in the following.
+
+- Storage Groups
+- Buckets
+- File shares
+
+Users will be able to create the following items within ECS without direct access to the ECS console.
+
+- Buckets
+- File shares
+
+## Storage Servers
+
+The first step in the Dell EMC ECS integration is to add a Dell EMC ECS Storage Server. Once added, Buckets, Files Shares and Storage Groups will be synced in and can be access and managed in HPE Morpheus Enterprise.
+
+### Adding Dell EMC ECS Storage Server
+
+#### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC ECS
+
+   URL
+   :   URL Of DELL EMC ECS Server Example : `https://192.168.190.200:4443`
+
+       TIP
+
+       The port 4443 is the api port for ECS api. This may be different depending on your configuration
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   S3 SERVICE URL (Optional)
+   :   Add your S3 service url Example: <http://192.168.190.220:9020>
+
+       NOTE
+
+       S3 SERVICE URL is not required if you are not planning on using ECS S3.
+5. Select SAVE CHANGES
+
+#### Results
+
+The Dell EMC ECS Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Buckets
+
+- **Buckets** will be listed in Infrastructure - Storage - Buckets
+
+  - Buckets can be created and deleted with Infrastructure - Storage Role Permissions
+  - Buckets can be browsed with Infrastructure: Storage Browser Role permissions
+  - File and folders can be uploaded, downloaded and deleted with Full Infrastructure: Storage Browser Role permissions.
+
+## Adding Dell EMC ECS Buckets
+
+### About this task
+
+NOTE
+
+A Dell ECS Storage Server must be configured in Infrastructure - Storage - Servers prior to adding a Dell ECS Bucket.
+
+To Add a Dell ECS Storage Bucket:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the BUCKETS tab, Click the + ADD button.
+4. Select Dell EMC ECS Bucket from the dropdown list
+5. From the NEW BUCKET Wizard input the following: 
+
+   NAME
+   :   Name of the Bucket in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   BUCKET NAME
+   :   Enter a name for the new Dell ECS bucket.
+
+   USER
+   :   Your Dell EMC ECS S3 user account
+
+   SECRET KEY
+   :   Your Dell EMC ECS S3 Secret
+       :   Example: jW+pFyAPtSS5FuEqKwt44xlpM/2
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace for the Bucket
+
+   STORAGE GROUP
+   :   Select a Dell EMC ECS Storage Group
+
+   Default Backup Target
+   :   Sets this bucket as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this Bucket will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this Bucket when creating VMware Backups, after which the snapshot will be removed from the target hypervisor.
+
+   Default Deployment Archive Target
+   :   Sets this Bucket as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this bucket as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the Bucket will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the bucket.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup Bucket.
+
+               BACKUP BUCKET
+               :   Search for and select the Bucket the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this bucket after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the Bucket.
+6. Select SAVE CHANGES
+
+### Results
+
+The Bucket will be created and displayed in the Buckets tab.
+
+- To browse, upload, download, or delete files from this Bucket, select the name of the Bucket.
+- To edit the Bucket, select the edit icon or select the name of the Bucket and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a bucket that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a Bucket, select the trash icon or select the name of the Bucket and select DELETE.
+
+  WARNING
+
+  When deleting a Bucket, all Deployment Versions and Backups associated with the Bucket will be deleted.
+
+## Add Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json b/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
new file mode 100644
index 0000000..b1ad81a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+  "title": "Hosts",
+  "ordinal": 211,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html",
+  "topic_cluster": {
+    "clustering_title": "Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B",
+        "clustering_title": "Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md b/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
new file mode 100644
index 0000000..b4c55c9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.md
@@ -0,0 +1,12 @@
+# Hosts
+
+![../../_images/infra_compute_header_hosts_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BC2FD43F-BD46-40FD-BA88-FA7789B6DE81-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Hosts in HPE Morpheus Enterprise are Hypervisors and Container hosts that VMs and Containers are hosted on, such as ESXi Hosts and Kubernetes Master and Workers. These hosts are populated from integrated clouds, hosts and clusters provisioned from Morpheus, or manually added hosts.
+
+Provisioning new hosts takes place in the Infrastructure > Clusters section of HPE Morpheus Enterprise. For example, provisioning a new Docker cluster in that section will begin the process of creating a HPE Morpheus Enterprise-managed Docker cluster with one host (by default). Additional hosts and custom layouts can also be created. See the [Clusters section](https://docs.morpheusdata.com/en/latest/infrastructure/clusters/clusters.html) of HPE Morpheus Enterprise docs for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json b/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
new file mode 100644
index 0000000..2536eff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+  "title": "Role Permissions",
+  "ordinal": 296,
+  "parent_title": "Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.html",
+  "topic_cluster": {
+    "clustering_title": "Role Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-397630C5-C2CE-4E35-A45D-0228C8F70867",
+        "clustering_title": "Role Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md b/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
new file mode 100644
index 0000000..cacb07e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-397630C5-C2CE-4E35-A45D-0228C8F70867.md
@@ -0,0 +1,12 @@
+# Role Permissions
+
+NOTE
+
+Permission options for sub-tenant user roles will only list options permitted by the Tenant role applied to the sub-tenant. Sub-Tenant user roles permissions cannot exceed permissions set by the overriding Tenant Role.
+
+**Subtopics**  
+
+- **[User Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html)**
+- **[Tenant Role Permission Sections](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html)**
+- **[Cloud Access Levels](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html)**
+- **[Feature Access Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json b/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
new file mode 100644
index 0000000..23eaf15
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+  "title": "Import and Export",
+  "ordinal": 98,
+  "parent_title": "Code",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html",
+  "topic_cluster": {
+    "clustering_title": "Import and Export",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-39D4284E-C733-48AD-94DE-CD929AEB0431",
+        "clustering_title": "Import and Export"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md b/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
new file mode 100644
index 0000000..9929cd7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.md
@@ -0,0 +1,128 @@
+# Import and Export
+
+Onboarded Git repositories can be configured as either import or export targets for a HPE Morpheus Enterprise appliance. This means that many created HPE Morpheus Enterprise constructs, such as Tasks, Library Items, and others, can be backed up to an integrated Git repository as code. This backup can take place on an automatic schedule (syncs every four hours) or can be triggered manually after changes are made. Users can back up all supported constructs within the appliance to a single repository or use Labels to back up only selected items. Exported constructs can also be imported into target appliances. This is useful for sharing items between two HPE Morpheus Enterprise environments, such as from a development appliance to a production appliance.
+
+NOTE
+
+The use of this feature requires an integrated Git repository. Please see our [integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for Github or other Git integrations if you’ve not yet integrated your code repositories. While Morpheus can onboard and work with both public and private code repositories, it is strongly recommended that you use private repositories for exporting your Morpheus constructs as code.
+
+Supported Constructs:
+
+- Tasks
+- Workflows
+- Spec Templates
+- Library Items
+- Forms
+
+NOTE
+
+When exporting all supported constructs HPE Morpheus Enterprise will export more than just the above types, however, only the above types are exportable as individual resources. This list may expand in the future as additional constructs become supported by future updates.
+
+## Role Permissions
+
+Access and capabilities for the Import/Export feature set is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Export/Import`
+:   - **None:** Cannot access the edit button on the Code List Page (Provisioning > Code) to set Import/Export settings or see Import/Export actions on the Code Repository Detail Page
+    - **Full:** Code repositories can be edited to set Import/Export configurations and Import/Export actions can be viewed and used on Code Repository Detail Pages
+
+## Import/Export Settings
+
+Code repositories are set to allow import, export or both from the Code Repositories List Page (Provisioning > Code). Click the edit button (✎) to the right of the selected repository to edit its import/export settings. When editing a code repository for import and export, set the following configurations:
+
+- **ENABLED:** When marked, routine syncs will take place between HPE Morpheus Enterprise and this repository. This includes all file syncs and not just actions related to import and export
+- **IMPORT/EXPORT:** Set “Auto export all” to automatically export once every four hours, “Manual export” to enable this repository for manual exports on demand, “Manual import” to enable this repository for manual imports on demand, “Import/Export” to enable both manual imports and exports on demand
+- **PATH:** The path within the repository where HPE Morpheus Enterprise should import from or export to
+- **EXPORT LABEL FILTER:** Enter a Label and HPE Morpheus Enterprise will export or import only constructs which include the Label into the repository. This must be a single Label, it cannot be a list of multiple Labels
+
+Once you’ve configured the code repository, click SAVE CHANGES
+
+NOTE
+
+Code repositories must have at least one file in them in order to export HPE Morpheus Enterprise constructs as code. This can be as simple as a README file, they just cannot be empty.
+
+![../../_images/editRepo.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1897DAD3-23E6-4D44-8331-93C40D4FD9FA-high.png)
+
+## Exporting
+
+After a repository is configured to allow export (see previous section), it may perform periodic automatic refreshes or the user may need to refresh the repository on demand (depending on settings). To manually initiate an export, drill into the Repository Detail page, click ACTIONS, and click “Export All Resources”.
+
+![../../_images/exportAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-01557155-5F51-4E18-9423-80740E675D88-high.png)
+
+Any new or updated constructs will be refreshed within the repository at the path your repository is configured to export into. Bear in mind that, even if you’ve configured HPE Morpheus Enterprise to export only constructs categorized with a specific Label, any required dependencies would also be exported. For example, if you’ve labeled a Workflow to be exported, HPE Morpheus Enterprise will also export the dependency Tasks so the Workflow will be functional. A similar behavior applies for exported Library Items which may have a number of dependencies. In the screenshot below, files can be seen populating the targeted Github repository.
+
+![../../_images/githubView.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-200CE557-64D2-4090-9C52-EE941972E411-high.png)
+
+HPE Morpheus Enterprise items are exported as scribe files. These are HCL-formatted representations of the construct as code. They include static attributes representative of the attributes set on the construct itself or they may use UUIDs to refer to other constructs or integrations. It shouldn’t be necessary to view or edit them unless you’re curious.
+
+![../../_images/viewScribe.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5C55D002-8AF1-4F8D-9EAE-D6839820B80F-high.png)
+
+## Importing
+
+After HPE Morpheus Enterprise constructs have been exported as code, they can be pulled down into other appliances which have the same repositories integrated. Items can be imported ad-hoc from the file browser within a Code Repository Detail page. Click on the gear (⚙) dropdown to the right of any scribe file that may exist in your repository. For example, in the screenshot below, an individual Task is being imported into the destination appliance.
+
+![../../_images/importFile.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E526F230-60CB-4FB1-ACCE-EA127DA5E7D2-high.png)
+
+In addition to importing one-off items, code repositories may also be configured for import so that many items can be imported at once. The same configurations can be made for import as export, including a specific path within the repository to import from and whether only specific Label groups should be targeted. Triggering a larger scale import for a whole repository is done from the Code Repository Detail Page. Click the ACTIONS button and then click “Import All Resources”.
+
+![../../_images/importAll.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-66220000-CC18-46E6-9B31-28E732091886-high.png)
+
+Once the import has been initiated, HPE Morpheus Enterprise will check to see if a new item will be created, if an existing item would be updated, if no action could be taken due to a conflict, or if no changes would result. This information is presented to the user who may then decide if the import action should go ahead.
+
+![../../_images/checkImport.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7E6E76A0-2B8D-49C7-ADBE-3D515134ED07-high.png)
+
+IMPORTANT
+
+Care has been taken with HPE Morpheus Enterprise Import/Export to ensure that existing work cannot be wiped out by an import action. For example, if a Task with a name identical to a pre-existing Task would try to be imported, HPE Morpheus Enterprise will require the naming conflict be resolved before the import can take place. In fact, HPE Morpheus Enterprise Import can only create new items or overwrite items created by import. It cannot overwrite anything user-created or anything pre-seeded with the system at install. Additionally, import cannot be scheduled automatically. Users must initiate all imports.
+
+IMPORTANT
+
+Importing resources which rely on existing integrations or sensitive values will require some additional configuration on the destination appliance. For example, importing a Task which references code in a separate repository which is not integrated on the target appliance will be imported with reference to the missing integration. This integration would need to be added before the Task could be used. Another example scenario would be a Task which references a secret value held in HPE Morpheus Enterprise Cypher. Once again, the Task would be imported and the required Cypher references would need to be made within the destination appliance before the Task could be used.
+
+## Checking Imported Items Prior to Use
+
+As mentioned in the previous section, not every imported item will immediately be available for use. This is primarily due to the target appliance lacking an integration (for example, an Ansible Tower integration required for an imported Task) or a securely stored secret string (for example, a Task that calls a secret string stored in HPE Morpheus Enterprise Cypher). HPE Morpheus Enterprise will still import these resources but this section discusses some manual changes that may have to be made to imported items in order for them to be usable. HPE Morpheus Enterprise will attempt to export all dependent resources (for example, the needed Tasks if a Workflow is exported) but imported items should still be checked and manually supplemented under certain conditions outlined below.
+
+When exporting, remember that HPE Morpheus Enterprise cannot export to a completely empty repository. Any file (such as a README) needs to exist first. Items deleted from HPE Morpheus Enterprise but previously exported to your repository will continue to exist in the repository. If you wish to delete them from any future imports, you must manually delete them from the repo. Finally, bear in mind that export functionality will only export items which are owned by the Tenant in which the export is created. HPE Morpheus Enterprise does not currently support exporting items which are shared to the tenant from the Master Tenant.
+
+### Protected Fields and User Credentials
+
+Protected information and secret values are not exported. When importing any resources which rely on protected information, the user will need to manually update the resource on the target appliance. Examples include anything authenticated using a stored credential set (from the Infrastructure > Trust > Credentials section), anything with a password field (such as HTTP Tasks or REST-based Option Lists accessing password-protected information), Chef Task Data Bag Keys, and more. Anything configured with a password or other protected field will need to be edited on the importing appliance and updated to have the protected information needed to function.
+
+### Integrations
+
+When an imported Task requires an integration that does not exist on the appliance, an integration will be created with the same name. The integration credentials will not be established, nor will any other configuration fields outside of the name. Users will need to update the integration configuration to make it functional in order for the imported Task to function.
+
+### SSH Keys
+
+SSH Keys are not set on imported resources, such as Tasks configured to be executed on a remote host. Users will need to add a valid key to the importing appliance and update the Task to use that SSH Key.
+
+### Ansible Tower Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on Ansible Tower Tasks.
+
+### vRealize Orchestrator Tasks
+
+Following import, “Inventory” and “Job Template” fields will need to be configured on vRO Tasks.
+
+### Option Lists
+
+Option lists need to be edited and saved prior to use in order to load any initial data sets that have been configured on the Option List.
+
+### Forms
+
+Input defaults that are ID-based will require manual correction after import. For example, if you have a Group Input which defaults to `GroupName:A(ID:2)`, when imported it will still be based off an ID value of 2. It’s highly likely that in the importing environment, a different Group will have an ID value of 2. A manual change to the correct ID value is required in the destination environment. Bear in mind that if you re-import a Form, you will also undo any manual changes you’ve made in the importing environment. Thus, if you update all defaults after importing, and then import once again, these manual default changes will be wiped out.
+
+Additionally, when Forms are using existing Inputs, those Inputs will be exported and imported for use in the destination environment. On import, HPE Morpheus Enterprise will add the needed Inputs unless the destination environment already has an Input with the same CODE value. This could give the appearance of creating duplicate Inputs if the destination environment happens to have an Input with the same name but a different code value. Users may wish to rename Inputs in the event they end up with more than one having the same name.
+
+### Tasks
+
+The user must ensure the presence of any dependency required by a Task. One example would be any Cypher keys being called by the Task. Add any required Cypher entries with identical keys or add compatible Cypher keys and update the Task configuration to utilize the updated Cypher mountpoints. Cypher is just one example, any other dependency required by the Task must be present. HPE Morpheus Enterprise does not parse the Task configuration to determine which dependencies are or are not present or required.
+
+### Icons and Images
+
+Icons which are set up on imported Instance Types will need to be manually uploaded to the appliance after import. They are not brought over as part of the import/export process.
+
+### Virtual Images
+
+When importing Node Types, the associated Virtual Image is mapped by its “Code” value. It is expected that a Virtual Image with the correct “Code” value already exists on the target appliance. If not, the Node Type will be imported without any Virtual Image attached. The user will then need to edit the Node Type and associate it with a compatible Virtual Image in order to become usable.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json b/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
new file mode 100644
index 0000000..0538d39
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+  "title": "HPE Bare Metal (BMaaS)",
+  "ordinal": 396,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Bare Metal (BMaaS)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3A38516A-B491-407B-AF69-9DF38E4266DF",
+        "clustering_title": "HPE Bare Metal (BMaaS)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md b/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
new file mode 100644
index 0000000..03651e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3A38516A-B491-407B-AF69-9DF38E4266DF.md
@@ -0,0 +1,29 @@
+# HPE Bare Metal (BMaaS)
+
+HPE Bare-Metal-as-a-Service (BMaaS) for Morpheus Enterprise extends Morpheus hybrid cloud management capabilities to HPE ProLiant physical servers. This integration allows the Morpheus platform to discover, provision, and manage these servers as first-class resources. Additionally, HPE BMaaS Cloud integrates HPE ProLiant bare-metal infrastructure into cloud environments to enable cloud-based provisioning and lifecycle management.
+
+HPE BMaaS manages the end-to-end server lifecycle, including hardware discovery, bare-metal provisioning, operating system deployment, monitoring, and metering. The Morpheus interface centrally orchestrates these tasks. This unified approach enables organizations to manage physical infrastructure, virtual machines, and cloud resources using consistent workflows, policies, and governance controls.
+
+HPE BMaaS Cloud provides the following key capabilities:
+
+- **Automated Server Discovery**: Automatically imports and discovers HPE ProLiant servers.
+- **Bare-Metal Provisioning**: Provisions hardware using custom or pre-configured OS images.
+- **Comprehensive OS Deployment**: Deploys Windows and Linux with unattended installations and customizable boot parameters.
+- **Lifecycle Management**: Manages firmware and drivers using the HPE Service Pack for ProLiant (SPP).
+- **Flexible Networking**: Supports both unmanaged and managed network integrations.
+- **Metering and Billing**: Maps discovered hardware to service plans to align metering with billing.
+- **Logical Organization**: Organizes resources into Bare Metal Clouds and Resource Pools to support multi-site environments and scalable infrastructure segmentation.
+
+HPE BMaaS improves operational visibility and server lifecycle control. It offers a scalable, automated approach to manage physical infrastructure across both greenfield (new) and brownfield (existing) environments.
+
+**Subtopics**  
+
+- **[Supported Software Versions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html)**
+- **[Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3535B779-7CDA-4288-A03A-02E0F9552B7B.html)**
+- **[Compute Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C06459C-26AA-4AB0-897C-F0EFA3F73923.html)**
+- **[Network Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html)**
+- **[Storage Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html)**
+- **[Troubleshooting and Diagnostics](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html)**
+- **[Known Limitations and Operational Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json b/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
new file mode 100644
index 0000000..06e749f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+  "title": "Migrations Plans",
+  "ordinal": 270,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3A627DBF-D797-42A2-A9AC-AAC321376068",
+        "clustering_title": "Migrations Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md b/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
new file mode 100644
index 0000000..c8082fb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.md
@@ -0,0 +1,25 @@
+# Migrations Plans
+
+Migration plans are created and run from the Migrations section of the Tools menu (Tools > Migrations). Migrations happen by creating and running Migration Plans. Plans are created in a pending state, meaning an additional action must be undertaken to set the plan in motion. Thus, Plans may be created which are intended to be run at a later time. Once finished, completed Plans remain on the Migrations list page for later review and, if desired, deletion.
+
+Creating Migration Plans
+
+Begin creating a Migration Plan from the Migrations list page (Tools > Migrations). This page contains a list of all Migrations already created, including those completed, currently running, and available to be run (pending). To start a new Migration, click + ADD.![A list of all currently-created Migrations.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-93D37CD4-FDF6-48AC-95C5-A5B7D7F30E35-high.png)
+
+From the SETUP tab of the CREATE MIGRATION PLAN modal, configure the following:
+
+- **NAME:** A name to identify the Migration
+- **SOURCE:** The source VMware vCenter Cloud
+- **TARGET:** The target Cloud containing the HVM Cluster
+- **RESOURCE POOL:** The selected destination HVM Cluster
+- **GROUP:** The Group which should own the migrated VMs
+
+When finished, click NEXT.![The SETUP tab of the CREATE MIGRATION PLAN modal.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D9CD7CB0-1B54-42D7-A75C-010C489E9E09-high.png)
+
+The next step is to choose VMs from the selected VMware source Cloud to migrate. Select as many as desired given current recommendations regarding the maximum size due to storage space and available bandwidth (see the previous section). Selected VMs will form a list at the bottom of the modal. When finished, click NEXT.![Selecting source VMs to migration from the source VMware Cloud.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EB548317-44C7-4C2C-B943-03241A92389D-high.png)
+
+The next tab establishes resource mapping. Listed, you will see the current networks and storage locations for the selected VMs. Choose destination networks and destination storage locations for each. Optionally, enter existing Linux or Windows user credentials and choose if prechecks or guest tools installation should be skipped. Click NEXT.![Mapping source networks and storage to destination networks and storage.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7B17FB9E-19D1-42B2-9696-7856C59EC92F-high.png)
+
+The final tab is a review tab where all current selections can be checked. Return to any previous tabs, if necessary, to update selections.
+
+At this point, the Migration is created but will not run without additional input. The Migration is in a "Pending" state. All selections made when configuring the Migration are shown here. To execute the Migration, click RUN. The length of time it will take for the Migration to run depends on many factors. Once run, the Migration detail page will provide status updates on VMs currently being migrated, which have completed successfully, and if any have failed. The History tab provides greater detail on current and past migration actions taken. The Destination tab includes details on VMware VMs which have successfully been migrated to the HVM Cluster. Migrations are run just once and may be kept indefinitely after for review. When a Migration is no longer needed, click DELETE.![The migration detail page showing a migration in a pending state.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7B7CB8A7-E91D-40E5-9B1B-E040BCFB2A0A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json b/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
new file mode 100644
index 0000000..66066f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+  "title": "Reports",
+  "ordinal": 55,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html",
+  "topic_cluster": {
+    "clustering_title": "Reports",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0",
+        "clustering_title": "Reports"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md b/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
new file mode 100644
index 0000000..6c18f50
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.md
@@ -0,0 +1,87 @@
+# Reports
+
+## Overview
+
+HPE Morpheus Enterprise offers 28 different report types which are designed to slice up costing and usage across Clouds, Tenants, and more. Reports can be run on-demand as needed or can be scheduled to run on certain intervals to be viewed at a later time. The list of available report types can be viewed at Operations > Reports.
+
+![../_images/1reportList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF328552-F0CB-4A16-89DE-DD5E534DDA21-high.png)
+
+## Report Types
+
+### ACCOUNT INVENTORY
+
+- Tenant Inventory Summary
+
+### CLOUD USAGE
+
+- Cloud Usage
+- Cloud Usage App Summary
+- Cloud Usage Instance Type Summary
+- [Tenant Usage](https://docs.morpheusdata.com/en/latest/operations/report_types/tenant_usage.html)
+
+### CLOUD COST
+
+- Amazon Reservation Coverage
+- Amazon Reservation Utilization
+- Amazon Savings Inventory Summary
+- Amazon Savings Plan Coverage
+- Amazon Savings Plan Utilization
+- Application Cost
+- Cloud Cost
+- Group Cost
+- Instance Cost
+- Tenant Cost
+- Time Series Cost
+
+### INFRASTRUCTURE INVENTORY
+
+- Cloud Inventory Summary
+- Container Host Inventory Summary
+- Group Inventory Summary
+- Guidance
+- Hypervisor Inventory Summary
+- Migration Planning
+- Tenant Resource Allocation
+
+### PROVISIONING INVENTORY
+
+- Instance Inventory Summary
+- Software Inventory
+- Software Inventory By Server
+- Tag Compliance
+- Virtual Machine Inventory Summary
+- Workload Summary
+
+By clicking into a report type, users can see any previous runs and active report schedules. New on-demand runs and new schedules of the selected report type can be created, edited, or deleted from here. The next few sections go into creating, editing, scheduling, viewing, and deleting reports in greater detail.
+
+## Create Reports
+
+To create a new report, navigate to the report type list page (Operations > Reports). Click RUN NOW to the right of the specific report type to bring up the wizard to run that particular report. The required and optional fields to run the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/2reportExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-39F2C925-F3CB-4E65-B5A6-B5B515D2A1F6-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Once the report is run, it will be visible in the list of Instance Cost reports and all reports until deleted.
+
+## Schedule Reports
+
+In addition to running on-demand reports, HPE Morpheus Enterprise also allows reports to be scheduled. This allows you to save report configuration and have access to refreshed information on the schedule you need.
+
+The process of scheduling a report is nearly identical to running on on-demand. From the report type list page (Operations > Reports) click SCHEDULE to the right of the report type you wish to schedule. The required and optional fields to schedule the selected report type will appear, for example, the configuration panel for the Instance Cost report is shown below:
+
+![../_images/3scheduleExample.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF0ECE3F-331E-4BDF-9CF3-8DA3BAF19EFA-high.png)
+
+In this case, we can choose to scope the report by start and end dates, Groups, Clouds, Tenants, and can specifically include or omit Instances based on tags. Additionally, we select the time schedule on which this report should automatically run. Finally, we can opt to add a comma-separated list of email addresses which should receive an emailed link to the report each time the report is run.
+
+NOTE
+
+HPE Morpheus Enterprise includes three schedules by default: Date and Time (run once at the specified time), Daily at Midnight, and Weekly on Sunday at Midnight. Any other listed scheduling periods are user-configured execution schedules (Library > Automation > Execute Scheduling). Create a new execution schedule if none of the existing schedules work for your reporting needs.
+
+## Viewing Results
+
+A list of all report runs is viewable on the Results tab of the report types list page (Operations > Reports). To view the report itself, click on the hyperlinked report filters. Only reports that are ready for viewing will have an active hyperlink on their filters. In addition to report filters, the run date, report type, creating user, and run status are shown. Click on any of these headers to filter the report list by that column in either ascending or descending order. Any report can be deleted by clicking on the trash can icon at the end of its row.
+
+![../_images/4resultsList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CDD94D4F-361B-4237-B8FD-B88CCFCB6118-high.png)
+
+## Viewing Schedules
+
+A list of all scheduled report runs can be viewed in the Scheduled tab of the report types list page (Operations > Reports). The friendly name of the report schedule is displayed along with the report type, last run time, next run time, and success status of the previous run. Schedules can be edited or deleted by clicking on the pencil or trash can icon, respectively. We can also view the most recent run of a given schedule (if it was successful) by clicking on the hyperlinked “last run” value.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json b/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
new file mode 100644
index 0000000..45f1ec8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+  "title": "Remote Storage",
+  "ordinal": 439,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3B6AC391-B993-47A2-8264-7389873C8D6D",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md b/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
new file mode 100644
index 0000000..c5f5f5c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.md
@@ -0,0 +1,16 @@
+# Remote Storage
+
+Remote storage enables lifecycle management of volumes on supported **HPE Alletra storage arrays** (including **Alletra MP** and **Alletra 9000**, where supported) and allows compute instances to attach to or detach from those volumes. These operations can be performed during instance provisioning or post-provisioning through the reconfigure workflow. The currently supported transport protocol is **Fibre Channel**.
+
+To get started with using remote storage, first, the storage plugin for Alletra needs to be loaded, and a storage server added. This allows the user to specify the URL where the management interface of the storage array is available, along with the user credentials to manage the storage array.
+
+There is also a concept of a datastore, which is used to represent a container for a set of volumes. A datastore is associated with a storage server and also a resource pool. The resource pool is used to represent a site or a location, which is useful when storage HA is being used with datastores associated with different sites.
+
+## Adding HPE AlletraStorage Integration
+
+You can add the Allertra Storage plugin JAR using the Upload plugin method.
+
+**Subtopics**  
+
+- **[Creating a Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html)**
+- **[Creating a Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json b/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
new file mode 100644
index 0000000..79b7eb6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+  "title": "Price Sets",
+  "ordinal": 290,
+  "parent_title": "Plans",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.html",
+  "topic_cluster": {
+    "clustering_title": "Price Sets",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911",
+        "clustering_title": "Price Sets"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md b/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
new file mode 100644
index 0000000..ea3c08b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3BBE7B0E-83BD-4EC1-B4E5-CE2261569911.md
@@ -0,0 +1,41 @@
+# Price Sets
+
+Price Sets combine Prices and then attach to Plans. Prices must be created prior to creating Price Sets, but it is recommended to review the Price Set Type options prior to creating Prices.
+
+Price Unit
+:   Select the Price Unit to use for the Price Set.
+
+    - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+    NOTE
+
+    Only Prices configured with matching Price Units can be used in a Price Set. “Month” is equivalent to 30 days by default. For AWS, month is 30.5 days. For Azure, month is 30.4 days.
+
+Type
+:   Price Set types determine which Prices are available to make up the set. This selection will filter the values returned in the Prices field at the bottom of the modal.
+
+    NOTE
+
+    It’s helpful to make note of the Prices options below before creating Price Sets.
+
+    - **Everything:** ‘Everything’ price sets require one or more ‘Everything’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Compute + Storage:** ‘Compute + Storage’ price sets require at least one of each ‘Memory’, CPU’, and ‘Disk Only’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Component:** ‘Component’ price sets require at least one of each ‘Memory’, ‘Cores’, ‘CPU’, and ‘Storage’ price types and may include ‘Platform’ or ‘Software’ price types
+    - **Load Balancer:** ‘Load Balancer’ price sets require at least one ‘Load Balancer’ price type and may include ‘Load Balancer Virtual Server’ price types. Load Balancer price sets are the only type which can be associated with Load Balancer Price Plans
+    - **Virtual Image:** ‘Virtual Image’ price sets require at least one ‘Storage’ price type. Virtual Image price sets are the only type which can be associated with Virtual Image Price plans
+    - **Snapshot:** ‘Snapshot’ price sets require at least one ‘Storage’ price type and may also include ‘Datastore’ price types. Snapshot price sets are the only type which can be associated with Snapshot Price plans
+    - **Software/Service:** ‘Software/Service’ Price Sets require at least one ‘Software/Service’ Price type
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
+
+Prices
+:   Search for and select Prices to be added to the Price Set. One of each Price Type required for the Price Set Type selected must be added for the Price Set to save.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json b/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
new file mode 100644
index 0000000..88bd0ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+  "title": "Openstack",
+  "ordinal": 465,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.html",
+  "topic_cluster": {
+    "clustering_title": "Openstack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85",
+        "clustering_title": "Openstack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md b/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
new file mode 100644
index 0000000..8dd84b9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3C7B42FA-5EBC-4035-BB8F-13B0BC366D85.md
@@ -0,0 +1,325 @@
+# Openstack
+
+## Overview
+
+Openstack is becoming a widely used on-premise infrastructure orchestration platform. It has a wide array of contributors and enterprise sponsorships. There are several variations on Openstack as well. HPE Morpheus Enterprise supports integration with all the various platform offerings and ranges in support all the way back to Openstack Juno. The complete list of compatible versions is listed in our [Integration Compatibility table](https://docs.morpheusdata.com/en/latest/release_notes/compatibility.html#integrations). It leverages the APIs and provides full functionality as a self service portal in front of Openstack.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups and Snapshots
+- Security Group Management
+- Disk Mode support Local/Image
+- Floating IP Assignment support
+- Brownfield VM management and Migration
+- Lifecycle Management and Resize
+- Docker Host management and configuration
+- Manila File Services (SFS)
+- Object Storage (OBS)
+- Network Lifecycle
+- LBaaS/Octavia Load Balancing Services
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to Openstack that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Image to QCOW2 Image Conversion
+- QCOW2 to RAW Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+- Instance Cloning
+- HPE Morpheus Enterprise Kubernetes Cluster Deployment
+
+TIP
+
+To allow Morpheus to list Hypervisor Hosts, ensure the Openstack user used for the Cloud Integration has sufficient privileges for `os_compute_api:os-hypervisors` in `/etc/nova/policy.json` in Openstack.
+
+NOTE
+
+CEPH is not supported in Morpheus 8.0.10 or higher.
+
+## Getting Started
+
+OpenStack Clouds are very easy to integrate with HPE Morpheus Enterprise. First, go to the Infrastructure  >  Clouds section and click + ADD. Select OpenStack to begin the integration process, most branded flavors of OpenStack will work with this Cloud selection as well.
+
+WARNING
+
+Support for OpenStack v2 Identity API has been removed in v5.3.3
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   v3 Identity endpoint.
+
+DOMAIN ID
+:   For Default domains, Default can be used. For other domain the Domain ID must be entered, not the Domain Name.
+
+PROJECT
+:   Enter the target project or leave this field blank to integrate all projects
+
+USERNAME
+:   Service Username
+
+PASSWORD
+:   Service user password
+
+OS VERSION
+:   Select Openstack Version. HPE Morpheus Enterprise supports the latest versions of OpenStack, select the latest version available if your current version is not shown.
+
+IMAGE FORMAT
+:   Select QCOW2, RAW or VMDK Image Type
+
+LB TYPE
+:   Select LB Type for Openstack LB syncing and creation
+
+Inventory Existing Instances
+:   Select for HPE Morpheus Enterprise to discover and sync existing VM’s
+
+Enable Hypervisor Console
+:   Hypervisor console support for openstack currently only supports novnc. Be sure the novnc proxy is configured properly in your openstack environment. When disabled HPE Morpheus Enterprise will use ssh and rdp for console conneciton (vm/host credentials required)
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+NOTE
+
+v5.3.3 adds openstack project management which requires additional permissions in openstack:
+
+```
+```
+identity:list_domain_roles  
+identity:list_role_assignments  
+identity:list_roles  
+identity:list_projects  
+identity:create_project  
+identity:update_project  
+identity:delete_project  
+identity:create_grant  
+identity:revoke_grant
+```
+```
+
+Most of the information in the dialog can be acquired from the Openstack dashboard. under Project  >  Access & Security  >  API Access. The API URL that is needed is the one tied to Identity. The Domain and Project inputs typically correlate to the multitenant domain setup within Openstack (sometimes just left at default) as well as the project name given to instances. HPE Morpheus Enterprise allows multiple integrations to the same Openstack cluster to be scoped to various domains and projects as needed.
+
+The remaining options help HPE Morpheus Enterprise determine which API capabilities exist in the selected Openstack environment. Hence the need for the Openstack version and image format. If a newer Openstack cluster is being used then exists in the dropdown, simply select the most recent version in the dropdown and this should function sufficiently until the new version is added.
+
+TIP
+
+Some Openstack environments do not support QCOW2 and force RAW image formats (like Metapod). This is due to some network overhead in Ceph created by using QCOW2. HPE Morpheus Enterprise keeps two copies of Openstack image templates for this exact purpose.
+
+Saving this cloud integration should perform a verification step and close upon successful completion.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure > Compute > Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+## Service Ports
+
+HPE Morpheus Enterprise consumes the following OpenStack service ports by default as part of its cloud integration. If your OpenStack implementation has been configured to use alternate service ports, these can be overwritten in the Cloud configuration under the Service Endpoints section when adding or editing the Cloud integration.
+
+![../../../_images/serviceEndpoints.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-533A8DF6-01D2-4189-A822-6565F7C5395D-high.png)
+
+### Default Service Ports
+
+- Identity: 5000
+- Compute: 8774
+- Image: 9292
+- Key Manager: 9311
+- Network: 9696
+- Volume API v3: 8776 v3
+- Manila: 8786
+
+## OpenStack Scalable File Service (SFS)
+
+The HPE Morpheus Enterprise integration with Openstack Cloud includes the capability to work with Openstack Scalable File Service (SFS). SFS is shared file storage hosted on Openstack Cloud. By integrating HPE Morpheus Enterprise with Openstack you can discover, create, manage, and delete SFS servers, as well as view and work with the file shares and files contained therein.
+
+### SFS Server Discovery and Management
+
+On integrating Openstack Cloud with HPE Morpheus Enterprise, SFS servers and file shares are discovered automatically after a short time. The server(s) can be viewed in Infrastructure > Storage > Servers. By viewing the server detail page and clicking EDIT, the storage server can be scoped as needed. Administrators can choose to scope to other Openstack Cloud integrations (if more than one relevant integration currently exists), select from synced availability zones, and scope the storage server to specific Tenants if desired.
+
+Additionally, Openstack SFS servers can be created from the storage server list page (Infrastructure > Storage > Servers) directly in HPE Morpheus Enterprise. Click +ADD to begin and set the storage server type value to “Openstack SFS”. Just like with existing synced SFS servers, those created from HPE Morpheus Enterprise can be scoped as needed.
+
+![../../../_images/addSfs.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-948FDB48-9D25-4116-8FAF-DF9669B6F3E1-high.png)
+
+### SFS File Share Discovery and Management
+
+Discovered file shares will appear among other file shares synced with HPE Morpheus Enterprise in Infrastructure > Storage > File Shares. Depending on the number of cloud integrations in your HPE Morpheus Enterprise appliance and the number of cloud integrations available to your user account, this list may be quite large. Using the search bar on this page, we can narrow down the list to only file shares whose names match the search terms.
+
+We can drill into individual file shares by clicking on the hyperlinked name in the list of all integrated file shares. From the file share detail page, a list of files will appear on the files tab. Begin the process of adding a new file by clicking +ADD. The Access tab on the file shares detail page allows users to view and manage ACL rules.
+
+NOTE
+
+“Failed to load files from storage provider” is present when the HPE Morpheus Enterprise appliance doesn’t have access to the file share.
+
+New Openstack SFS file shares can also be created directly in HPE Morpheus Enterprise. From the file shares list page, get started by clicking +ADD. Select the type “Openstack SFS Share”. Set the storage service field to a pre-existing Openstack SFS server. Setting a friendly name for the file share in HPE Morpheus Enterprise and selecting from synced availability zones is required.
+
+## Network and Router Creation
+
+Once an OpenStack Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “OpenStack Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select OpenStack Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select OpenStack Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OpenStack project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
+
+## Advanced
+
+There are a few advanced features when it comes to provisioning on top of Openstack. Most of these present themselves in the provisioning wizard. This includes OS Volume Type (Local or Volume) which dictates whether the main OS disk is copied and run off the hypervisor or remotely mounted as a volume via Glacier. Some Openstack setups only configure hypervisors with minimal local disks so volume type is needed.
+
+Another option during provisioning is “Assign Floating IP”. This option does exactly what it says and is similar to the feature on the Openstack instance dashboard itself. It should be noted that this will attempt to acquire a floating IP from the project and, if out of capacity, will attempt to increase capacity to the project if the cloud credentials provided have sufficient administrative privileges to do so.
+
+## Docker
+
+So far this document has covered how to add the Openstack cloud integration and has described how to provision virtual machine-based Instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to work with Docker containers and even support multiple containers per Docker host. To do this, a Docker host must first be provisioned into Openstack (multiple hosts are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host, navigate to Infrastructure > Clusters and click + ADD CLUSTER. Complete the provisioning wizard including selecting the appropriate Group and Cloud. Alternatively, you can navigate to the Clusters tab for a specific Cloud (Infrastructure > Clouds > Specific Cloud detail page > Clusterstab) and begin the process of provisioning a Docker host to that Cloud from there. Once completed, this host will show up in the Hosts sections (Infrastructure > HostsOR Infrastructure > Clouds > Specific Cloud detail page > Hoststab). HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones.
+
+Once a Docker Host is successfully provisioned, a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure, click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance URL which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance, the HPE Morpheus Enterprise Agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json b/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
new file mode 100644
index 0000000..33413ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+  "title": "Getting Started",
+  "ordinal": 2,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE",
+        "clustering_title": "Getting Started"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md b/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
new file mode 100644
index 0000000..f32c098
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.md
@@ -0,0 +1,11 @@
+# Getting Started
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html)**
+- **[Capacity and Planning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html)**
+- **[Installation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html)**
+- **[Upgrades & Maintenance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html)**
+- **[Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html)**
+- **[Initial Appliance Setup](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html)**
+- **[Core Functionality](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json b/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
new file mode 100644
index 0000000..082ef6f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+  "title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 365,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CA69B8E-D437-40EC-9755-668930BA21F4",
+        "clustering_title": "Automated Multi-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md b/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
new file mode 100644
index 0000000..e1fb2c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.md
@@ -0,0 +1,281 @@
+# Automated Multi-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. This is a companion guide to our [single-node application deployment guide](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.xml) and, in some cases, will refer directly to sections of that guide rather than duplicating information here.
+
+In this guide, we will create a custom App Blueprint for SuiteCRM consisting of a database node and an application node. Once configured, the provisioning process is completely automated (Provisioning > Apps) and results in the two-tiered app mentioned previously. We’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a multi-tiered application:
+
+- App Blueprints
+- Cypher
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. Additionally, while this could be done on many different Cloud types, I’m setting up this Instance Type for provisioning on a VMware vCenter Cloud. You would need to have a VMware Cloud already integrated with HPE Morpheus Enterprise in order to follow the guide exactly but I will not go through the process of creating new Clouds here. If you do not have a vCenter Cloud available to you, the concepts in the guide will translate to other Cloud types, including public clouds like Amazon AWS. You may have to make slight modifications in spots in order to make a fully working Instance Type for other Clouds.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. In this case, we need to store two Cypher secrets: The first is for the MySQL root password and the second is for the user which we will use to run SSH commands from the app server to the database server. Refer to the [single-node deployment guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-cypher) for details on setting up the first Cypher entry.
+
+Next we need to set up a Cypher for the SSH user so our application node can access the database. A handy trick here is to use the user specified in the HPE Morpheus Enterprise global Cloud-Init Setting as this will be automatically created on the Instances when they are provisioned by HPE Morpheus Enterprise. To check that the user is set up correctly, in the HPE Morpheus Enterprise UI go to Administration > Settings > Provisioning. Under the Cloud-Init Settings section, ensure that a username and password is set. After that, simply create a secret/cloudinit Cypher entry which stores the password for this user using the same process by which you set up the MySQL root password Cypher entry.
+
+## Create Inputs
+
+Inputs are custom input fields in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password. The steps to create these inputs have been detailed in the companion guide, if needed, you can reference them [here](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-inputs).
+
+## Create File Template and Library Template Task
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. We’ll also create a Task which we can use to automatically set our file template at the appropriate time during provisioning. The steps to create the [File Template](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-file-templates) and [Library Template Task](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks) are detailed in the companion guide so follow the links for walkthrough steps and return to this guide.
+
+## Create Database Install Task
+
+Since the database is installed on its own node, we need a Task which installs just database. In the prior section, we created a Library Template Task but this time we will create Bash Script Tasks to handle database node installation and application node installation. We’ll also need a simple third Task to restart the Apache service after setting the config file. We’ll go through the steps for creating all three of these Tasks in this section.
+
+Navigate to Library > Automation > Tasks and click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install db multi node
+- **Code:** suitecrminstalldbMN
+- **Type:** Shell Script (The proper fields will appear once the Type is set)
+- **Sudo:** Checked
+- **Source:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **Execute Target:** Resource
+
+### Database Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` != 0 ]  
+then  
+      sleep 120  
+fi  
+#Install MariaDB, start service and enable on boot  
+wget https://downloads.mariadb.com/MariaDB/mariadb_repo_setup  
+echo "fd3f41eefff54ce144c932100f9e0f9b1d181e0edd86a6f6b8f2a0212100c32c mariadb_repo_setup" | sha256sum -c -  
+chmod +x mariadb_repo_setup  
+./mariadb_repo_setup  --mariadb-server-version="mariadb-10.6"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enable mariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -u root -e "UPDATE mysql.user SET Password=PASSWORD('$RPass') WHERE User='root';"  
+mysql -u root -e "flush privileges"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.user WHERE User='root' AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass -e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass -e "DELETE FROM mysql.db WHERE Db='test' OR Db='test\_%';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Set bind-address parameter in my.cnf  
+sed -e '/^bind/s/^/#/g' -i /etc/mysql/mariadb.conf.d/50-server.cnf  
+systemctl restart mariadb.service
+```
+```
+
+## Create Application Install and Apache Restart Tasks
+
+We now need to create a Bash script task to install the application. However, before we do this, we need to consider how these Tasks will run. We need to have the database installed before the application. We can achieve this in our App Blueprint by configuring the boot order so that the database is provisioned before the application. However, as part of the database configuration, we also need to create a database user and set up remote access to the database for the application server IP. The challenge here is that we cannot create the database user as part of the database install Task as we will not know the application server IP address. To get around this, we will run the database configuration Tasks within the application install task using sshpass to remotely execute the MySQL commands on the database. This is where the cloud-init user and Cypher we created earlier come in.
+
+NOTE
+
+In the code section below, remember to set the correct username for your cloud-init user. In the code below it is set to pjonesci. You will also see in the Task below we are using environment variables to pull in the IP address of the database host (MYSQL\_HOST variable). We are able to do this because in the App Blueprint we will connect the tiers which means Instances in a tier can import the evars from Instances in connected tiers.
+
+Once again, click + ADD to start a new Task. Configure the new Task as follows:
+
+- **Name:** suitecrm install app multi node
+- **Code:** suitecrminstallappMN
+- **Type:** Shell Script
+- **Sudo:** Checked
+- **Source:** Local
+- **Execute Target:** Resource
+
+### Application Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/mysql_root')%>"  
+CIPass="<%=cypher.read('secret/cloudinit')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+MYSQL_HOST="<%=evars.SUITECRMDBMN_IP%>"  
+IP="<%=server.internalIp%>"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+        sleep 120  
+fi  
+#Install sshpass and apache, start service and enable on boot  
+apt-get install sshpass -y  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Use sshpass to remotely execute mysql commands on DB server to create database and database user  
+sshpass -p $CIPass ssh -o StrictHostKeyChecking=no -t pjonesci@$MYSQL_HOST <<REMOTE  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE USER '$SCRMUser'@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO $SCRMUser@'$IP' IDENTIFIED BY '$SCRMPass';"  
+sudo -S <<< "$CIPass" mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+REMOTE  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php7.3 libapache2-mod-php7.3 php7.3-common php7.3-mysql php7.3-gmp php7.3-curl php7.3-intl php7.3-mbstring php7.3-xmlrpc php7.3-gd php7.3-bcmath php7.3-imap php7.3-xml php7.3-cli php7.3-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+ sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" /etc/php/7.3/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+curl -sS https://getcomposer.org/installer | sudo php -- --version=1.10.9 --install-dir=/usr/local/bin --filename=composer  
+git clone https://github.com/salesagility/SuiteCRM.git /var/www/html/suitecrm  
+cd /var/www/html/suitecrm  
+composer install --no-dev  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+Finally, create the Apache restart Task mentioned earlier. The exact steps to create this Task are shown in the [companion single-node application guide](https://docs.morpheusdata.com/en/latest/getting_started/guides/autoinstall_instance.html#create-tasks).
+
+## Create Workflows
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provision phase. One Workflow will primarily handle database node installation and the other will primarily handle application node installation.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRMDB - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install db multi node” Task
+
+![../../_images/dbwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AE350F66-EE19-401B-A0C9-EB946194C3F2-high.png)
+
+Click SAVE CHANGES and then create the second Workflow:
+
+- **NAME:** SuiteCRMApp - Multi Node
+- **PLATFORM:** Linux
+- **TASKS:** In the provision phase, add our “suitecrm install app multi node”, “suitecrm file template”, and “suitecrm apache restart” Tasks
+
+Click SAVE CHANGES
+
+![../../_images/appwf.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B02FA612-F552-422C-B489-354AB4074DE4-high.png)
+
+## Create Instance Types for the Database and Application
+
+At this point we’re ready to put our pieces together into custom Instance Types for the database and application. Instance Types can be provisioned individually (Provisioning > Instances) but in this case we want to structure multiple Instance Types into logical tiers in an App Blueprint so they can be provisioned as a HPE Morpheus Enterprise App. Each Instance Type will contain a Layout and a Node Type, I’ll discuss each construct more fully as it’s time to create them.
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Set the following configurations:
+
+- **NAME:** SUITE\_CRM\_DB\_MN
+- **CODE:** suitecrmdbmn
+- **CATEGORY:** SQL
+- **ICON:** If desired, browse your local computer for a MariaDB icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMDBMN
+
+![../../_images/dbinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-992A3460-9FE9-4F5F-ABB2-FB8F13F0B3A9-high.png)
+
+Click SAVE CHANGES. With the Instance Type created, we’re ready to add a Layout. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** LO\_SUITE\_CRM\_DB\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **WORKFLOW:** Select the “SuiteCRM - Multi Node” Workflow that was previously created
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/dblo.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6BAE38A4-A27D-447A-86D1-01C6CF434D0E-high.png)
+
+Click SAVE CHANGES. With the Layout created, we’re ready to associated a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. In this case, we’re simply going to point to a default Ubuntu image which is supplied by HPE Morpheus Enterprise though you can associate Node Types with your own custom virtual images when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** NODE\_SUITE\_CRM\_DB\_MN
+- **SHORT NAME:** nodesuitecrmdbmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+Click SAVE CHANGES. This completes the database Library item needed to build out our App Blueprint in the next section. We now need to add a Library item representing the application node. Below I will list out the configurations for the Instance Type, Layout, and Node Type, you can refer back to the steps above if you need to see the click-by-click instructions once again for creating these objects.
+
+- **NAME:** SUITE\_CRM\_APP\_MN
+- **CODE:** suitecrmappmn
+- **CATEGORY:** Apps
+- **ICON:** If desired, browse your local computer for a SuiteCRM icon to make this Instance Type more recognizable when provisioning or creating App Blueprints
+- **ENVIRONMENT PREFIX:** SUITECRMAPPMN
+
+![../../_images/appinstype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D63BD45E-E0A9-4D0D-BAA2-2EFF77CC111B-high.png)
+
+- **NAME:** LO\_SUITE\_CRM\_APP\_MN
+- **VERSION:** Latest
+- **CREATABLE:** Checked
+- **TECHNOLOGY:** VMware
+- **MINIMUM MEMORY:** 4 GB (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **INPUTS:** Include the “SuiteCRM DB Name”, “SuiteCRM DB Password”, and “SuiteCRM DB User” Inputs that were previously created
+
+![../../_images/applo.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-29EF47D8-7883-4F20-8C82-6995D7CA784C-high.png)
+
+- **NAME:** NODE\_SUITE\_CRM\_APP\_MN
+- **SHORT NAME:** nodesuitecrmappmn
+- **VERSION:** Latest
+- **TECHNOLOGY:** VMware
+- **VM IMAGE:** Choose the HPE Morpheus Enterprise Ubuntu 18 image that is included with HPE Morpheus Enterprise out of the box
+
+![../../_images/appnode.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0BBD1C18-2B48-489F-959F-214CD44CED21-high.png)
+
+## Create the App Blueprint
+
+We are now ready create a HPE Morpheus Enterprise App Blueprint. HPE Morpheus Enterprise Blueprints allow pre-configured multi-tier application deployments for multiple environments. In this example we will use the custom Instance Types previously created to build out an App Blueprint for a two-tier SuiteCRM application with the database running on one VM and the application running on another VM.
+
+Go to Library > Blueprints > App Blueprints and click + ADD. Enter a name for the Blueprint (SuiteCRM Multi Node) and set type to HPE Morpheus Enterprise. Click NEXT.
+
+You will now be in the App Blueprint configuration screen where you can build out the structure of the App Blueprint. In the structure section on the left of the screen, click the + to add App Tier and then click it again to add a Database tier.
+
+![../../_images/namebp.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4B83AA01-4C21-4B94-B440-4E5E0BE1A81A-high.png)
+
+Now that we have the tiers created, we can create the configuration for each tier. Click the “+”” next to the App tier and in the window that pops up select the application Instance Type created previously (SUITE\_CRM\_APP\_MN).
+
+![../../_images/setappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-53BFEE5F-524C-498F-8000-E746C992C738-high.png) ![../../_images/nameappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D440051E-3817-4EFA-BEEF-AE37834507C5-high.png)
+
+Now click the “+” next to the Suite CRM Instance Type (under App). Select the Group and Cloud required (I’m selecting my VMware Cloud, in this case) and then click ADD CONFIG.
+
+![../../_images/setappcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-78CEFAB6-9636-4B0D-AC7A-913583BD97C9-high.png)
+
+You will now have a configuration under the Suite CRM icon. Click on the configuration and it will appear in the right-hand pane of the window. Fill in the configuration required to provision the Instance. The locks to the right of the fields allow you to lock down entries so that they cannot be changed when provisioning the App later. Do not click COMPLETE yet, we still need to configure the database tier.
+
+![../../_images/configappins.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-81561E16-36A7-44E7-AB89-4D944C4C34A4-high.png)
+
+Back in the left-hand pane, click the “+” next to Database and perform the same steps as before to add in the SUITE\_CRM\_DB\_MN Instance Type to the database tier. Add in the required configuration.
+
+![../../_images/configdbins.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0D8D8FF1-9617-4369-B1DF-B49DE4993A26-high.png)
+
+Once the configuration is set up for both tiers, we need to set the boot order and connect the tiers. The boot order is used to control the order in which the tiers are built. We want the database tier to build first, so we set the boot order to 0 on the database and 1 on the application. We also need to connect the tiers by checking the box under connected tiers.
+
+![../../_images/dbbootorder.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5C12EFCD-2D25-427F-AE41-752B282FF1C1-high.png)
+
+Save the App Blueprint by clicking COMPLETE.
+
+## Deploy the App Blueprint
+
+To deploy an App Blueprint, navigate to Provisioning > Apps and click + ADD. Select the App Blueprint we just created and work through the provisioning wizard, including naming the App and selecting the target Cloud.
+
+NOTE
+
+For the database hostname, specify the internal IP address of the database node
+
+![../../_images/app1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CA2843B6-3893-49B7-97B7-3236C92974E1-high.png) ![../../_images/app2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-11B85356-456E-453E-819A-E1848F22A86E-high.png) ![../../_images/app3.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-90155AD7-21F3-4243-BE6B-DE3205678495-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_APP\_NODE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json b/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
new file mode 100644
index 0000000..46ffdac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+  "title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+  "ordinal": 428,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.html",
+  "topic_cluster": {
+    "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C",
+        "clustering_title": "Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md b/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
new file mode 100644
index 0000000..cfb5f18
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CC5D68E-F244-4292-AD4C-A93A41C87F9C.md
@@ -0,0 +1,33 @@
+# Post-SPP Firmware Update - Mandatory Cold Power Cycle Procedure
+
+After applying an HPE Service Pack for ProLiant (SPP) on Gen11 and Gen12 servers, a full cold power cycle is required to ensure proper initialization of updated firmware components.
+
+An iLO reset or standard operating system reboot is not sufficient after an SPP update.
+
+Failure to perform a cold power cycle may result in:
+
+- Inconsistent Redfish storage inventory
+- Smart Array controller desynchronization
+- Missing or stale drive objects
+- Management platform initialization failures
+- Incomplete firmware activation
+
+Perform the following steps for cold power cycle:
+
+1. **Power OFF the server**:Shut down gracefully through the operating system or iLO interface. Confirm the server is completely powered off.
+2. **Disconnect AC Power**: Physically remove all power cables from the server power supplies.
+3. **Wait for 60 Seconds**: Allow sufficient time for residual power to drain. This clears controller cache and resets hardware state.
+4. **Reconnect Power**: Reattach all power cables securely.
+5. **Power ON the Server**: Boot the system normally.
+
+A full AC power removal forces:
+
+- Smart Array controller re-enumeration
+- PCI bus reinitialization
+- Storage firmware reload
+- Redfish object tree regeneration
+- Hardware state synchronization
+
+This process resolves the majority of post-SPP Redfish storage inconsistencies observed on Gen11 and Gen12 platforms.
+
+HPE strongly recommends performing a full cold power cycle after major firmware bundle updates to ensure all updated components are fully initialized.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json b/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
new file mode 100644
index 0000000..5396845
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+  "title": "Resource Center",
+  "ordinal": 528,
+  "parent_title": null,
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3CEB493A-1086-4AE2-8220-93B372329509.html",
+  "topic_cluster": {
+    "clustering_title": "Resource Center",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3CEB493A-1086-4AE2-8220-93B372329509",
+        "clustering_title": "Resource Center"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md b/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
new file mode 100644
index 0000000..df78ca3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3CEB493A-1086-4AE2-8220-93B372329509.md
@@ -0,0 +1,5 @@
+# Resource Center
+
+- [Developer Zone](https://developer.morpheusdata.com/)
+- [Support KnowledgeBase](https://support.morpheusdata.com/s/knowledge-base?language=en_US)
+- [White Papers](https://www.morpheusdata.com/resource-center)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json b/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
new file mode 100644
index 0000000..e71b7fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+  "title": "F5 Load Balancers",
+  "ordinal": 499,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html",
+  "topic_cluster": {
+    "clustering_title": "F5 Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3D3058F0-C2FE-4995-8D62-55A069D50709",
+        "clustering_title": "F5 Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md b/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
new file mode 100644
index 0000000..ec1af30
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.md
@@ -0,0 +1,139 @@
+# F5 Load Balancers
+
+## Virtual Servers
+
+Instances attached to an F5 will be listed in the Virtual servers tab. Virtual servers can also be manually added in this section.
+
+### Add Virtual Server
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers
+2. Select F5 Integration name to drill into the detail page
+3. Select + ADD in the VIRTUAL SERVERS tab
+4. Fill in the following: 
+
+   - NAME
+     :   Name of the Virtual Server in HPE Morpheus Enterprise
+   - DESCRIPTION
+     :   Description of the Virtual Server in HPE Morpheus Enterprise
+   - Enabled
+     :   Uncheck to keep the configuration but disable F5 availability in HPE Morpheus Enterprise
+   - VIP TYPE
+     :   - Standard
+         - Forwarding (Layer 2)
+         - Forwarding (IP)
+         - Performance (HTTP)
+         - Performance (Layer 4)
+         - Stateless
+         - Reject
+         - DHCP
+         - Internal
+         - Message Routing
+   - VIP HOSTNAME
+     :   Enter Hostname of the VIP (optional)
+   - VIP ADDRESS
+     :   Enter IP address for the VIP
+   - VIP PORT
+     :   Enter post used for the VIP
+   - SOURCE ADDRESS
+     :   Enter Virtual Server source address
+   - PROTOCOL
+     :   tcp, udp, or sctp
+   - PROFILES Search for and select from available PROFILES
+   - POLICIES
+     :   Search for and select from available POLICIES
+   - IRULES
+     :   Search for and select from available RUEL SCRIPTS
+   - PERSISTENCE
+     :   - cookie
+         - dest-addr
+         - global-settings
+         - hash
+         - msrdp
+         - sip
+         - source-addr
+         - ssl
+         - universal
+   - DEFAULT POOL
+     :   Select from available POOLS
+5. Select SAVE CHANGES
+
+## Policies
+
+Policies will be synced and listed in the Policies tab. These policies will be available options when creating Virtual Servers.
+
+## Pools
+
+### Create Pool
+
+NAME
+:   Name of the POOL in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the POOL in HPE Morpheus Enterprise
+
+BALANCE MODE
+:   - Round Robin
+    - Least Connections
+
+SERVICE PORT
+:   Specify SERVICE PORT for the POOL
+
+MEMBERS
+:   Search for and select from available NODES
+
+MONITORS
+:   Search for and select from available Monitors
+
+## Profiles
+
+SSL Profiles are synced and and will be created when an SSL Certificate is assigned in the Load balancer section when provisioning or editing a Load balancer on an Instance.
+
+## Monitors
+
+### Create Monitor
+
+NAME
+:   Name of the MONITOR in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the MONITOR in HPE Morpheus Enterprise
+
+PARENT MONITOR
+:   Select from available MONITORS
+
+DESTINATION
+:   Specify Destination, such a `*:443`. Default is `*:*`
+
+INTERVAL
+:   Specify Monitor Interval. Default is `5`
+
+TIMEOUT
+:   Specify Monitor Timeout. Default is `15`
+
+MONITOR CONFIG
+:   Enter monitor config.
+
+## Nodes
+
+### Create Node
+
+NAME
+:   Name of the NODE in HPE Morpheus Enterprise
+
+DESCRIPTION
+:   Description of the NODE in HPE Morpheus Enterprise
+
+ADDRESS
+:   Enter node address
+
+MONITOR
+:   Select from available MONITORS
+
+SERVICE PORT
+:   Specify SERVICE PORT for the NODE
+
+## Rule Scripts
+
+Rule Scripts will be synced and listed in the RULE SCRIPTS tab. These rules will be available options when creating Virtual Servers.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json b/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
new file mode 100644
index 0000000..863fd28
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+  "title": "Moving Workloads Between Hosts",
+  "ordinal": 184,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html",
+  "topic_cluster": {
+    "clustering_title": "Moving Workloads Between Hosts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF",
+        "clustering_title": "Moving Workloads Between Hosts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md b/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
new file mode 100644
index 0000000..d051508
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.md
@@ -0,0 +1,11 @@
+# Moving Workloads Between Hosts
+
+To manually move workloads between hosts, drill into the detail page for the VM (from the VMs tab of the cluster detail page). Click ACTIONS and select “Manage Placement”. Choose a different host and select from the following placement strategies:
+
+- **Auto:** Manages VM placement based on load
+- **Failover:** Moves VMs only when failover is necessary
+- **Pinned:** Will not move this workload from the selected host
+
+![../../_images/managePlacement.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-496FBC66-FFC3-4D76-B3D1-F0E4F31A838D-high.png)
+
+Within a short time, the workload is moved to the new host.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json b/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
new file mode 100644
index 0000000..d68c8b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+  "title": "Forms",
+  "ordinal": 153,
+  "parent_title": "Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html",
+  "topic_cluster": {
+    "clustering_title": "Forms",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3E6007AB-2F77-4783-8610-592F1BB9125B",
+        "clustering_title": "Forms"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md b/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
new file mode 100644
index 0000000..e75beea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.md
@@ -0,0 +1,163 @@
+# Forms
+
+Forms are designed to be used with [Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items). Using the provided tools, build forms to provide the appropriate customization fields for endusers in the Provisioning Catalog. Catalog Items can also be built using HPE Morpheus Enterprise Inputs but Forms provide unique capabilities that open up additional functionality and simplify the process. Once a Form is created it is then available to be associated with a Catalog Item. This section discusses the creation of Forms, the available options, and how they can be used effectively to create Catalog Items.
+
+## Creating a New Form
+
+To begin a new Form, navigate to Library > Options > Forms and click + ADD.
+
+![../../_images/newForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-79EB5F32-18B1-4437-9727-EA6FEC436A5C-high.png)
+
+## Adding Field Groups
+
+Field Groups are logical groupings of Input fields on your Form. Especially with larger forms, they make the Form easier to read and use. You can even collapse down sections of less commonly needed Inputs to keep your Forms clean. By default a new Form has no Field Groups but one can be added by clicking “+ ADD FIELD GROUP” in the center of the NEW FORM modal (which can be seen in the screenshot above). Field Groups can accept the following options:
+
+- **NAME:** The name and label for the Field Group
+- **DESCRIPTION:** And optional description for the Field Group
+- **COLLAPSIBLE:** When marked, the user can collapse (hide) or show the Field Group
+- **COLLAPSIBLE BY DEFAULT:** If the Field Group is marked collapsible, this option will appear to make the Field Group shown (unchecked) or hidden (checked) by default
+- **VISIBILITY FIELD:** Enter the fieldName of another Input and this Field Group will appear only when that Input has a value
+
+![../../_images/newFieldGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-07A59B83-A70F-407E-83F5-B6ABCB054D52-high.png)
+
+## Adding Inputs
+
+Inputs are the Form options themselves and can take various forms, such as text fields, checkboxes, select lists or other custom forms. Inputs can be added outside of any created Field Groups or they may be added within them. Click + ADD INPUT within the desired area (inside a Field Group or outside of them).
+
+When adding Inputs, you may add any Input (Library > Options > Inputs) that is pre-existing to your form. Set “USE EXISTING” to “Yes” and make the selection from the “EXISTING OPTION TYPE” typeahead field. Once selected, you’ll notice that all other settings cannot be edited. If needed, edit this Input within the Inputs section (Library > Options > Inputs).
+
+![../../_images/existingInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-25AEAFA2-3766-4411-9796-FCCD26396206-high.png)
+
+When adding Inputs, you may also create new Inputs within the Form builder. Some available types are no different than other Inputs you might make in the Input section (Library > Options > Inputs) but other types are unique to Forms. To create a new Input, set “USE EXISTING” to “No” and select the desired type.
+
+Input types are organized by categories. Inputs in the basic category are primarily the same types of Inputs that can be made in the Inputs section (Library > Options > Inputs). These include text fields, select lists, checkbox arrays, numerical inputs, and more. You can read more about the basic Input types in HPE Morpheus Enterprise [Input documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#inputs).
+
+Inputs in the Advanced and Provisioning categories are unique to Forms and require additional explanation. Advanced inputs are similar to basic but provide some sort of data manipulation capability or have a specific targeted function. See the list of advanced Input types below:
+
+- **Byte Size:** Allows numerical disk or storage size values to be given with selectable units (MB, GB, etc.). When a value is input and the unit is changed, the same value will be automatically computed into the new unit amount (1 GB > 1024MB, for example). Users may select which unit is initially loaded by default.
+- **Code Editor:** Gives the user a code editor field. Set a language or markdown format in the “HIGHLIGHTING” field to enable automatic syntax highlighting and spacing for the user. For example, the user could enter a provisioning shell script for their workload or provide a custom JSON payload at provision time (complete with syntax highlighting for easy entry).
+- **File Content:** Access file content either locally entered or sourced from an integrated repository or outside URL
+- **Icon Picker:** Allows the user to select an icon for their workload at provision time. The user may select from previously uploaded icons, upload their own, or use the built-in icon generator tool to create a unique icon right in the Form
+- **Key Value:** Allows the user to enter as many key/value pairs as they’d like which can be onboarded into the workload config at provision time
+- **Text Array:** Allows the user to enter multiple values separated by a delimiter of your choosing. HPE Morpheus Enterprise will parse out the entered values which can be individually deleted if desired before the form is submitted
+- **Typeahead:** Similar to Select List, especially for very long lists. Search for the desired value by typing the first few letters as a search parameter. Users may also browse the complete list by clicking the dropdown icon. This Input type can also support multiple selections, if needed. Associate this type of Input with a pre-defined Option List or create a new Option List right inside the Form builder
+
+![../../_images/forms1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E413A285-DAE5-4097-ABD7-5503BDA5B518-high.png)
+
+Inputs in the provisioning category are specifically tied to some provisioning construct in HPE Morpheus Enterprise (Groups, Clouds, etc.). They’re very useful for allowing users to select specific provisioning constructs, such as the Group, Cloud, Layout, or Network they wish to provision, and can automatically inject the user’s selection into the Catalog Item. This makes for much simpler Catalog Item development as compared to setting up the configuration using just the Input construct outside of Forms.
+
+Provisioning Inputs also include relevant reload and filtering behaviors by default. For example, your Cloud Input field will automatically reload after making a Group selection or your Layout Input field will automatically reload after setting a Group, Cloud, and Instance Type. This makes it very easy to create flexible Catalog Item forms that are useful across Clouds.
+
+The following provisioning Input types are supported, each with their own automatic filtering behavior and auto-inject capability into the Catalog Item spec:
+
+- Cloud
+- Disks
+- Exposed Ports
+- Group
+- Layout
+- Networks
+- Plan
+- Resource Pool
+- Security Groups
+- Tags
+- Vmw Folders
+
+![../../_images/forms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-186CA89B-1E7C-49B9-9C71-3CD0CE4E9A59-high.png)
+
+In order for provisioning Inputs to work properly, be sure to properly set the fields they should filter against. In the screenshot below you can see for a Resource Pool Input I’ve set the Group, Cloud, Layout, and Plan Inputs that it must be filtered against in order to work. Search for the Field Label of the target Input.
+
+![../../_images/poolFilters.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8E7A4B9B-FC72-4F3D-9EB8-6625130B3DA4-high.png)
+
+Once the type selected, the new Input will have many configuration options, most of which are the same options available when creating an Input from the Inputs section though some are new and some are presented in slightly different ways. The available options depend on the Input type selected but common options are shown in the expandable section below:
+
+### Common Input Configuration Options
+
+FIELD LABEL
+:   The name and label of the Input
+
+LOCALIZED LABEL
+:   If a localization code is selected, this field will have a translated label relative to the localization language selected for the appliance or user
+
+FIELD NAME
+:   This is the Input fieldName property used to resolve the field value into code or to refer to this field for creating dynamic relationships with other Input fields
+
+NOTE
+
+Field names should only contain letters, numbers, and hyphen (-), underscore (\_), or dot’.’ for separation.
+
+DEFAULT VALUE
+:   Pre-populates field with a default value
+
+PLACEHOLDER
+:   Background text that populates inside a field for adding example values, does not set a value
+
+HELP BLOCK
+:   Helpful text that will appear under your Input field to inform users about their selection
+
+LOCALIZED HELP BLOCK
+:   If a localization code is selected, this field will have a translated help block relative to the localization language selected for the appliance or user
+
+REQUIRED
+:   Prevents User from proceeding without setting value
+
+EXPORT AS TAG
+:   Creates Tags for fieldName/value (key/value) on Instances
+
+DISPLAY VALUE ON DETAILS
+:   When selected, the Input label and value (label: value) will be visible in a list of custom options on the Instance detail page
+
+LOCKED
+:   The Input field is visible but locked from being edited by the user. Any configured default values will be seen and set on the Instance but the user may not change the value
+
+HIDDEN
+:   Hides the field from view. The field is still active, however, and any configured default value would still be set
+
+EXCLUDE FROM SEARCH
+:   For Select List and Typeahead Inputs, check to exclude the form data from being stored as variables (which can be leveraged from an API call when needed)
+
+EDITABLE
+:   Allow the Input value to be updated when editing an Instance (This attribute is hidden if SHOW ON EDIT is not selected)
+
+SHOW ON EDIT
+:   Display the Input name and value when editing an Instance
+
+ALLOW MULTIPLE SELECTIONS
+:   For certain Input types which support multiple selections (Select List and Typeahead, for example), check to allow multiple items to be selected
+
+DEPENDENT FIELD
+:   The Field Name value for a field that will reload this Option List to present a different set of selections. Take a look at the section below on Cascading Inputs as well as the [associated article](https://support.morpheusdata.com/s/article/How-to-create-option-lists?language=en_US) in our KnowledgeBase for documented examples of this feature
+
+VISIBILITY FIELD
+:   A Field Name and selection value that will trigger this field to become visible. Currently, this only works when the Input is associated with a Service Catalog Item and viewed from the Service Catalog Persona perspective. See the section below on the Visibility Field for instructions on configuring this value
+
+VERIFY PATTERN
+:   For Text and Text Area-type Inputs. If desired, enter a regex pattern string and user entries must match the string to be accepted
+
+REQUIRE FIELD
+:   A fieldName that will trigger required attribute of this option
+
+A complete example form making use of provisioning Inputs and Field Groups is shown below:
+
+![../../_images/completeForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B953106A-64A3-4A8C-9BA9-428AE4A26C8A-high.png)
+
+## Using Localized Labels on Form Fields
+
+In creating a Form Input, you may enter a custom static text label by setting the FIELD LABEL attribute on the Input. Using this will set a label for your Form field which will appear the same for all users. Alternatively, you can set a dynamic text label by selecting an entry from the LOCALIZED LABEL typeahead field. By setting a Localized Label, the label will appear differently depending on the user’s web browser language localization setting, the HPE Morpheus Enterprise appliance localization setting (set in the [global settings area](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html)), or the user’s own localization setting from within the [User Settings section](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html). More specific localization settings (such as a user’s setting over the appliance-wide setting) override less specific settings.
+
+As an example, I’ll create a simple Form which has only a Group-type Input. Both the Field Label and Localized Label fields have been filled but the Localized Label takes precedence. Based on the localization settings for the user creating this Form, we see the label presented in US English as “GROUP.”
+
+![../../_images/buildForm.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2A54A030-6474-4ACB-B3A2-8E428EBF215E-high.png)
+
+If we then navigate to provision a Catalog Item based on this Form, we still see the US English “GROUP” field label as this specific user has a default localization of “English (United States)” in its User Settings menu.
+
+![../../_images/english.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F11BC817-1A85-4274-A47B-D401E36D4BDB-high.png)
+
+However, if we select a different user which has a default localization of “French,” and go to provision the same Catalog Item, the field label is shown in French.
+
+![../../_images/french.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-40BAFA08-1439-49F9-B642-C7C3FAED943F-high.png)
+
+HPE Morpheus Enterprise has several complete language packs and also allows users to contribute to new or in-progress language packs. If interested in creating or contributing to UI translations, take a look at [this YouTube video](https://www.youtube.com/watch?v=oX25kutg8vU).
+
+## Turning Forms into Catalog Items
+
+Once created, Forms can be associated with Catalog Items in the same way individual Inputs could before Forms were added. Add a new Catalog Items (or edit an existing one) in Library > Blueprints > Catalog Items. For complete details, refer to documentation on [creating Catalog Items](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#building-catalog-instances).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json b/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
new file mode 100644
index 0000000..9b6ad7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+  "title": "Variables",
+  "ordinal": 166,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html",
+  "topic_cluster": {
+    "clustering_title": "Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7",
+        "clustering_title": "Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md b/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
new file mode 100644
index 0000000..4c60a9a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.md
@@ -0,0 +1,1373 @@
+# Variables
+
+A vast number of variables are available for use in Tasks, Scripts, Templates, Resource Names, Cloud-Init User Data and Option List configs.
+
+IMPORTANT
+
+Variables are case sensitive
+
+## Pre-Provision Vars
+
+A subset of variables are available for Instance, Host Name and Hostnames. These can be passed inside `${ }` blocks during provisioning or in relevant policy configs. Groovy syntax can be resolved to allow for dynamic name generation as shown in some of the examples below.
+
+Instance Naming Policy example: `${userInitials}-${cloudCode}-${platform == 'windows' ? 'W' : 'L'}-${sequence}`
+
+Available variables for Naming Policy naming patterns include:
+
+```
+```
+${account}  
+${accountId}  
+${accountName}  
+${accountNumber}  
+${accountType}  
+${cloudCode}  
+${cloudName}  
+${customerNumber}  
+${customOptions.fieldName}  
+${groupCode}  
+${groupName}  
+${instance.instanceContext} # Environment Code  
+${platform == 'windows' ? 'w':'l'} # results in `w` for Windows platforms and `l` for Linux Platforms  
+${platform}  
+${provisionType}  
+${sequence} # results in 1  
+${sequence+100} # results in 101  
+${sequence.toString().padLeft(5,'0')} # results in 00001  
+${tenantId}  
+${tenant} # Tenant Name  
+${tenantSubdomain}  
+${type}  
+${userId}  
+${userInitials}  
+${username}
+```
+```
+
+An example Instance Name Policy using a naming pattern with User Initials, Cloud Code, Instance Type, and a sequential number starting at 3000 is `${userInitials}-${cloudCode}-${type}-${sequence+3000}`, resulting in an Instance Name of **md-vmwd3-centos-3001** for the first instance, followed by **md-vmwd3-centos-3002** and so on.
+
+NOTE
+
+It’s not recommended that users include “>”, “<”, “%”, “$”, or “=” in naming policies.
+
+## Syntax Examples
+
+PowerShell Example: `$app_id = "<%= instance.metadata.app_id %>"`
+
+Bash Example: `HOSTNAME="<%= container.server.hostname %>"`
+
+Python Example: `hostname = morpheus['server']['hostname']`
+
+HTTP Body Example: `{"name": "<%= instance.createdByUsername %>"}`
+
+![../_images/Metadata-Enviornment-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-14CAAF3E-4218-42AA-9D8B-8511E2C5E913-high.png) ![../_images/Tags-Variable-Spot](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B9FCD0BE-6651-4DA3-BC61-3AB7E704065C-high.png)
+
+NOTE
+
+customOptions values are defined from custom Inputs.
+
+## Common Examples
+
+```
+```
+                  container.configGroup: <%=container.configGroup%>  
+                  container.configId: <%=container.configId%>  
+                  container.configPath: <%=container.configPath%>  
+                  container.configRole: <%=container.configRole%>  
+                  container.containerTypeCode: <%=container.containerTypeCode%>  
+                  container.containerTypeName: <%=container.containerTypeName%>  
+                  container.containerTypeShortName: <%=container.containerTypeShortName%>  
+                  container.cores: <%=container.cores%>  
+                  container.dataPath: <%=container.dataPath%>  
+                  container.dateCreated: <%=container.dateCreated%>  
+                  container.domainName: <%=container.domainName%>  
+                  container.environmentPrefix: <%=container.environmentPrefix%>  
+                  container.externalIp: <%=container.externalIp%>  
+                  container.hostMountPoint: <%=container.hostMountPoint%>  
+                  container.hostname: <%=container.hostname%>  
+                  container.image: <%=container.image%>  
+                  container.internalHostname: <%=container.internalHostname%>  
+                  container.internalIp: <%=container.internalIp%>  
+                  container.logsPath: <%=container.logsPath%>  
+                  container.memory: <%=container.memory%>  
+                  container.planCode: <%=container.planCode%>  
+                  container.provisionType: <%=container.provisionType%>  
+                  container.server: <%=container.server.serverTypeName%>  
+                  container.serverId: <%=container.serverId%>  
+                  container.sshHost: <%=container.sshHost%>  
+                  container.status: <%=container.status%>  
+                  container.storage: <%=container.storage%>  
+                  container.version: <%=container.version%>  
+                  customOptions: <%=customOptions.fieldName%>  
+                  accountNumber: <%= accountNumber %> #resource tenant account number  
+                  customerNumber: <%= customerNumber %> #resource tenant customer number  
+                  accountName: <%= accountName %> # resource tenant account name  
+                  taskOwner.accountNumber: <%= taskOwner.accountNumber %> #task owner tenant account number  
+                  taskOwner.customerNumber: <%= taskOwner.customerNumber %>  
+                  taskOwner.accountName: <%= taskOwner.accountName %>  
+                  user.accountNumber: <%= user.accountNumber %> #user executing task tenant account number  
+                  user.customerNumber: <%= user.customerNumber %>  
+                  user.accountName: <%= user.accountName %>  
+                  evar: <%=evars.name%>  
+                  evars: <%=evars%>  
+                  group.code: <%=group.code%>  
+                  group.datacenterId: <%=group.datacenterId%>  
+                  group.location: <%=group.location%>  
+                  group.name: <%=group.name%>  
+                  instance.autoScale: <%=instance.autoScale%>  
+                  instance.configGroup: <%=instance.configGroup%>  
+                  instance.configId: <%=instance.configId%>  
+                  instance.configRole: <%=instance.configRole%>  
+                  instance.containers[0]: <%=instance.containers[0].containerTypeName%>  
+                  instance.cores: <%=instance.cores%>  
+                  instance.createdByEmail: <%=instance.createdByEmail%>  
+                  instance.createdByFirstName: <%=instance.createdByFirstName%>  
+                  instance.createdById: <%=instance.createdById%>  
+                  instance.createdByLastName: <%=instance.createdByLastName%>  
+                  instance.createdBYUsername: <%=instance.createdByUsername%>  
+                  instance.deployGroup: <%=instance.deployGroup%>  
+                  instance.description: <%=instance.description%>  
+                  instance.displayName: <%=instance.displayName%>  
+                  instance.domainName: <%=instance.domainName%>  
+                  instance.environmentPrefix: <%=instance.environmentPrefix%>  
+                  instance.expireDate: <%=instance.expireDate%>  
+                  instance.firewallEnabled: <%=instance.firewallEnabled%>  
+                  instance.hostname: <%=instance.hostname%>  
+                  instance.instanceContext: <%=instance.instanceContext%> (tip: instanceContext = Environment)  
+                  instance.instanceLevel: <%=instance.instanceLevel%>  
+                  instance.instanceTypeCode: <%=instance.instanceTypeCode%>  
+                  instance.instanceTypeName: <%=instance.instanceTypeName%>  
+                  instance.instanceVersion: <%=instance.instanceVersion%>  
+                  instance.memory: <%=instance.memory%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.name: <%=instance.name%>  
+                  instance.networkLevel: <%=instance.networkLevel%>  
+                  instance.plan: <%=instance.plan%>  
+                  instance.provisionType: <%=instance.provisionType%>  
+                  instance.status: <%=instance.status%>  
+                  instance.statusMessage: <%=instance.statusMessage%>  
+                  instance.storage: <%=instance.storage%>  
+                  instance.metadata: <%=instance.metadata%>  
+                  instance.userStatus: <%=instance.userStatus%>  
+                  server.agentInstalled: <%=server.agentInstalled%>  
+                  server.agentVersion: <%=server.agentVersion%>  
+                  server.apiKey: <%=server.apiKey%>  
+                  server.category: <%=server.category%>  
+                  server.commType: <%=server.commType%>  
+                  server.configGroup: <%=server.configGroup%>  
+                  server.configId: <%=server.configId%>  
+                  server.configRole: <%=server.configRole%>  
+                  server.consoleHost: <%=server.consoleHost%>  
+                  server.consolePort: <%=server.consolePort%>  
+                  server.consoleType: <%=server.consoleType%>  
+                  server.consoleUsername: <%=server.consoleUsername%>  
+                  server.dataDevice: <%=server.dataDevice%>  
+                  server.dateCreated: <%=server.dateCreated%>  
+                  server.description: <%=server.description%>  
+                  server.displayName: <%=server.displayName%>  
+                  server.domainName: <%=server.domainName%>  
+                  server.externalId: <%=server.externalId%>  
+                  server.externalIp: <%=server.externalIp%>  
+                  server.fqdn: <%=server.fqdn%>  
+                  server.hostname: <%=server.hostname%>  
+                  server.internalId: <%=server.internalId%>  
+                  server.internalIp: <%=server.internalIp%>  
+                  server.internalName: <%=server.internalName%>  
+                  server.internalSshUsername: <%=server.internalSshUsername%>  
+                  server.lastAgentUpdate: <%=server.lastAgentUpdate%>  
+                  server.lvmEnabled: <%=server.lvmEnabled%>  
+                  server.macAddress: <%=server.macAddress%>  
+                  server.managed: <%=server.managed%>  
+                  server.maxCores: <%=server.maxCores%>  
+                  server.maxMemory: <%=server.maxMemory%>  
+                  server.maxStorage: <%=server.maxStorage%>  
+                  server.name: <%=server.name%>  
+                  server.nodePackageVersion: <%=server.nodePackageVersion%>  
+                  server.osDevice: <%=server.osDevice%>  
+                  server.osType: <%=server.osType%>  
+                  server.osTypeCode: <%=server.osTypeCode%>  
+                  server.parentServerId: <%=server.parentServerId%>  
+                  server.plan: <%=server.plan%>  
+                  server.platform: <%=server.platform%>  
+                  server.platformVersion: <%=server.platformVersion%>  
+                  server.powerState: <%=server.powerState%>  
+                  server.serialNumber: <%=server.serialNumber%>  
+                  server.serverModel: <%=server.serverModel%>  
+                  server.serverType: <%=server.serverType%>  
+                  server.serverTypeCode: <%=server.serverTypeCode%>  
+                  server.serverTypeName: <%=server.serverTypeName%>  
+                  server.serverVendor: <%=server.serverVendor%>  
+                  server.softwareRaid: <%=server.softwareRaid%>  
+                  server.sourceImageId: <%=server.sourceImageId%>  
+                  server.sshHost: <%=server.sshHost%>  
+                  server.sshPort: <%=server.sshPort%>  
+                  server.sshUsername: <%=server.sshUsername%>  
+                  server.status: <%=server.status%>  
+                  server.statusMessage: <%=server.statusMessage%>  
+                  server.tags: <%=server.tags%>  
+                  server.toolsInstalled: <%=server.toolsInstalled%>  
+                  server.visibility: <%=server.visibility%>  
+                  task.results (using task code): <%=results.taskCode%>  
+                  task.results (using task name): <%=results["Task Name"]%>  
+                  task.results.value: <%=results.taskCode.key%>  
+                  zone.agentMode: <%=zone.agentMode%>  
+                  zone.cloudTypeCode: <%=zone.cloudTypeCode%>  
+                  zone.cloudTypeName: <%=zone.cloudTypeName%>  
+                  zone.code: <%=zone.code%>  
+                  zone.domainName: <%=zone.domainName%>  
+                  zone.firewallEnabled: <%=zone.firewallEnabled%>  
+                  zone.location: <%=zone.location%>  
+                  zone.name: <%=zone.name%>  
+                  zone.regionCode: <%=zone.regionCode%>  
+                  zone.scalePriority: <%=zone.scalePriority%>  
+                  cypher: <%=cypher.read('secret/hello')%>  
+cypher: <%=cypher.read('secret/' + zone.code)%> # Make variables more dynamic based off other variables
+```
+```
+
+## Instance
+
+```
+```
+instance {  
+        adminPassword,  
+        adminUsername,  
+        apps.[],  
+        assignedDomainName,  
+        autoScale,  
+        backup.{},  
+        configGroup,  
+        configId,  
+        configRole,  
+        container.{},  
+        containers.[],  
+        cores,  
+        createBackup,  true/false  
+        createdByEmail,  
+        createdByFirstName,  
+        createdById,  
+        createdByLastName,  
+        createdByUser.{  
+                 username,  
+                 displayName,  
+                 firstName,  
+                 lastName,  
+                 email,  
+                 linuxUsername,  
+                 windowsUsername  
+        },  
+        createdByUsername,  
+        createUser, # true/false  
+        customOptions,  
+        deployGroup,  
+        description,  
+        displayName,  
+        domainName,  
+        environmentPrefix,  
+        evars:{},  
+        expireDate, # YYYY-MM-DD-T00:00:00Z  
+        expireDays,  
+        expose.[],  
+        firewallEnabled:true/false,  
+        hostId,  
+        hostname,  
+        id,  
+        instanceContext,  
+        instanceLevel,  
+        instanceTypeCode,  
+        instanceTypeName,  
+        instanceVersion,  
+        isEC2:true/false,  
+        isVpcSelectable, # true/false  
+        layoutCode,  
+        layoutId,  
+        layoutName,  
+        layoutSize,  
+        lbInstances.[],  
+        memory(bytes),  
+        memoryDisplay, #MB/GB  
+        metadata.{},  
+        name,  
+        nestedVirtualization,  
+        networkLevel,  
+        noAgent,  
+        plan,  
+        poolProviderType,  
+        ports,  
+        provisionType,  
+        resourcePoolId,  
+        scheduleStatus,  
+        servicePassword,  
+        serviceUsername,  
+        smbiosAssetTag,  
+        sslCertId,  
+        sslEnabled, # true/false  
+        status,  
+        statusMessage,  
+        storage, # bytes  
+        tags,  
+        userStatus,  
+        vmwareFolderId,  
+}
+```
+```
+
+## Container
+
+```
+```
+container {  
+        configGroup,  
+        configId,  
+        configPath,  
+        configRole,  
+        containerTypeCode,  
+        containerTypeShortName,  
+        cores,  
+        dataPath,  
+        dateCreated,  
+        domainName,  
+        environmentPrefix,  
+        externalIp,  
+        hostMountPoint,  
+        hostname,  
+        image,  
+        internalHostname,  
+        internalIp,  
+        logsPath,  
+        memory,  
+        planCode,  
+        provisionType,  
+        server:{},  
+        serverId,  
+        sshHost,  
+        status,  
+        storage,  
+        version,  
+        containerTypeName  
+}
+```
+```
+
+## Server
+
+```
+```
+server {  
+        agentInstalled,  
+        agentVersion,  
+        apiKey,  
+        category,  
+        commType,  
+        configGroup,  
+        configId,  
+        configRole  
+        consoleHost,  
+        consolePort,  
+        consoleType,  
+        consoleUsername,  
+        dataDevice,  
+        dateCreated,  
+        description,  
+        displayName,  
+        domainName,  
+        externalId,  
+        externalIp,  
+        fqdn,  
+        hostname,  
+        internalId,  
+        internalIp,  
+        internalName,  
+        internalSshUsername,  
+        lastAgentUpdate,  
+        lvmEnabled,  
+        macAddress,  
+        managed,  
+        maxCores,  
+        maxMemory,  
+        maxStorage,  
+        name,  
+        nodePackageVersion,  
+        osDevice,  
+        osType,  
+        osTypeCode,  
+        parentServerId,  
+        plan,  
+        platform,  
+        platformVersion,  
+        powerState,  
+        serialNumber,  
+        serverModel,  
+        serverType,  
+        serverTypeCode,  
+        serverTypeName,  
+        serverVendor,  
+        softwareRaid,  
+        sourceImageId,  
+        sshHost,  
+        sshPort,  
+        sshUsername,  
+        status,  
+        statusMessage,  
+        tags,  
+        toolsInstalled,  
+        visibility,  
+        volumes {  
+                name  
+                id  
+                deviceName  
+                maxStorage  
+                unitNumber  
+                displayOrder  
+                rootVolume  
+        }  
+}
+```
+```
+
+## Zone (Cloud)
+
+```
+```
+zone {  
+        agentMode,  
+        cloudTypeCode,  
+        cloudTypeName,  
+        code,  
+        datacenterId,  
+        domainName,  
+        firewallEnabled,  
+        location,  
+        name,  
+        regionCode,  
+        scalePriority  
+}
+```
+```
+
+## networkConfig
+
+```
+```
+'networkConfig': {  
+  'primaryInterface': {  
+    'doDhcp': false,  
+    'dnsServers': [],  
+    'dnsDomain': "",  
+    'netmask': "",  
+    'gateway': "",  
+    'ipAddress': "",  
+    'doDhcp6': false,  
+    'gateway6': "",  
+    'ipv6Address': "",  
+    'cidr6Suffix': "",  
+    'dnsServers6': ""  
+  },  
+  'extraInterfaces': [  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    },  
+    {  
+      'doDhcp': false,  
+      'dnsServers': [],  
+      'dnsDomain': "",  
+      'netmask': "",  
+      'gateway': "",  
+      'ipAddress': "",  
+      'doDhcp6': false,  
+      'gateway6': "",  
+      'ipv6Address': "",  
+      'cidr6Suffix': "",  
+      'dnsServers6': ""  
+    }  
+  ]  
+}
+```
+```
+
+## Group (Site)
+
+```
+```
+group {  
+        code,  
+        location,  
+        datacenterId,  
+        name  
+}
+```
+```
+
+## Custom Options (Inputs)
+
+```
+```
+customOptions {  
+        customOptions.fieldName  
+}
+```
+```
+
+## Global
+
+ex: `<%= morpheus.user.id %>`
+
+```
+```
+"morpheus":{  
+   "user":{  
+      "id":value,  
+      "account":{  
+         "id":value  
+      },  
+      "username":"value",  
+      "displayName":"value",  
+      "email":"value",  
+      "firstName":"value",  
+      "lastName":"value",  
+      "dateCreated":0000-00-00T00:00:00Z,  
+      "lastUpdated":0000-00-00T00:00:00Z,  
+      "enabled":true/false,  
+      "accountExpired":true/false,  
+      "accountLocked":false,  
+      "passwordExpired":false,  
+      "defaultGroupId":value,  
+      "defaultZoneId":value,  
+      "hasLinuxUser":true/false,  
+      "hasWindowsUser":true/false,  
+      "role":{  
+         "id":value  
+      },  
+      "instanceLimits":value  
+   },  
+}
+```
+```
+
+## User
+
+```
+```
+'user': {'accountId': int,  
+        'accountName': 'string',  
+        'accountNumber': 'string',  
+        'attributes': {samlAttributes},  
+        'customerNumber': 'string',  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',
+```
+```
+
+## Script Variables Example
+
+Below is an example of the variables available to a script running against an Instance context.
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+```
+```
+'account': 'string',  
+'accountId': int,  
+'accountType': 'string',  
+'allowExisting': boolean,  
+'apps': [{'appContext': 'string',  
+          'description': 'string',  
+          'id': int,  
+          'name': 'string',  
+'cloud': 'string',  
+'cloudCode': 'string',  
+'cloudName': 'string',  
+'container': {'allowExisting': boolean,  
+              'certificatePath': string,  
+              'certificateStyle': string,  
+              'changeManagementExtId': int,  
+              'changeManagementServiceId': int,  
+              'cloud': 'string',  
+              'cloudConfig': {'agentInstall': agentInstallScript,  
+                              'finalizeServer': finalizeServerScript,  
+                              'meta': metaData,  
+                              'user': userData},  
+              'configGroup': int,  
+              'configId': int,  
+              'configPath': 'string',  
+              'configRole': int,  
+              'containerTypeCategory': 'string',  
+              'containerTypeCode': 'string',  
+              'containerTypeName': 'string',  
+              'containerTypeShortName': 'string',  
+              'cores': int,  
+              'coresPerSocket': int,  
+              'createUser': boolean,  
+              'customOptions': {'morph_ver': 'string',  
+              'dataPath': 'string',  
+              'dateCreated': 'string',  
+              'domainName': 'string',  
+              'environmentPrefix': 'string',  
+              'evars': {},  
+              'expireDays': 'string',  
+              'expose': ['string'],  
+              'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                                'name': 'string',  
+                                'port': int}],  
+              'externalIp': 'string',  
+              'externalPort': int,  
+              'hostMountPoint': 'string',  
+              'hostName': 'string',  
+              'hostname': 'string',  
+              'hosts': {'containerName': 'string',  
+                        'containerName': 'string',  
+                        'containerName': 'string',  
+              'id': int,  
+              'image': 'string',  
+              'instanceContext': 'string',  
+              'instanceType': {'code': 'string',  
+              'internalHostname': 'string',  
+              'internalIp': 'string',  
+              'internalPort': int,  
+              'layout': {'code': 'string',  
+                        'id': int},  
+              'logsPath': 'string',  
+              'maxCores': int,  
+              'maxCpu': int,  
+              'maxMemory': int,  
+              'maxStorage': int,  
+              'memory': int,  
+              'memoryDisplay': 'string',  
+              'mounts': [],  
+              'name': 'string',  
+              'networkId': int,  
+              'networkInterfaces': [{'id': 'string',  
+                                    'ipAddress': 'string',  
+                                    'ipMode': 'string',  
+                                    'network': {'dhcpServer': int,  
+                                                'group': int,  
+                                                'id': int,  
+                                                'name': 'string',  
+                                                'pool': int},  
+                                    'networkInterfaceTypeId': int}],  
+              'noAgent': boolean,  
+              'planCode': 'string',  
+              'portMap': {},  
+              'ports': [{'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean},  
+                        {'displayName': 'string',  
+                        'export': boolean,  
+                        'exportName': 'string',  
+                        'external': int,  
+                        'index': int,  
+                        'internal': int,  
+                        'link': boolean,  
+                        'loadBalance': boolean,  
+                        'loadBalanceProtocol': 'string',  
+                        'name': 'string',  
+                        'primaryPort': boolean,  
+                        'protocol': 'string',  
+                        'visible': boolean}],  
+              'provisionType': 'string',  
+              'publicKeyId': int,  
+              'server': {}  
+              'serverId': int,  
+              'shutdownDays': 'string',  
+              'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}],  
+              'sshHost': 'string',  
+              'status': 'string',  
+              'storage': int,  
+              'storageController': int,  
+              'type': 'string',  
+              'userGroup': {'id': '',  
+              'version': 'string',  
+              'vm': boolean,  
+              'volumes': [{'datastoreId': int,  
+                          'id': int,  
+                          'maxIOPS': int,  
+                          'maxStorage': int,  
+                          'name': 'string',  
+                          'rootVolume': boolean,  
+                          'size': int,  
+                          'storageType': int,  
+                          'vId': int}]},  
+'containerName': 'string',  
+'coresPerSocket': int,  
+'createUser': boolean,  
+'customOptions': {'morph_ver': 'string',  
+'deployOptions': {},  
+'evars': {},  
+'expireDays': 'string',  
+'expose': ['string'],  
+'exposedPorts': [{'loadBalanceProtocol': 'string',  
+                  'name': 'string',  
+                  'port': int}],  
+'externalIp': 'string',  
+'group': {'code': 'string',  
+          'configCmdbId': 'string',  
+          'configManagementId': 'string',  
+          'datacenterId': int,  
+          'dnsIntegrationId': 'string',  
+          'location': 'string',  
+          'name': 'string',  
+          'serviceRegistryId': 'string',  
+'groupCode': 'string',  
+'groupName': 'string',  
+'host': ,  
+'hostMountPoint': 'string',  
+'hostName': 'string',  
+'hosts': {},  
+'input': {'backup': ,  
+          'cloud': {},  
+          'computedHostName': 'string',  
+          'computedName': 'string',  
+          'copies': int,  
+          'domainOptions': {}},  
+          'environmentVariables': {},  
+          'executionId': int,  
+          'expireDays': int,  
+          'group': {},  
+          'hostName': 'string',  
+          'instanceContext': 'string',  
+          'layout': {},  
+          'metadata': {}},  
+          'name': 'string',  
+          'plan': {},  
+          'powerScheduleType': int,  
+          'securityGroups': {},  
+          'shutdownDays': int,  
+          'type': 'string',  
+          'version': 'string'},  
+'instance': {'adminPassword': 'maskedString',  
+            'adminUsername': 'string',  
+            'allowExisting': boolean,  
+            'apps': [{}],  
+            'assignedDomainName': 'string',  
+            'autoScale': boolean,  
+            'backup': {'backupRepository': int,  
+                        'createBackup': boolean,  
+                        'enabled': boolean,  
+                        'jobAction': 'string',  
+                        'jobRetentionCount': 'string',  
+                        'providerBackupType': int,  
+                        'showScheduledBackupWarning': boolean},  
+            'cloud': 'string',  
+            'cloudConfig': {'agentInstall': agentInstallScript,  
+                            'finalizeServer': finalizeServerScript,  
+                            'meta': metaData,  
+                            'user': userData  
+                                    },  
+            'configGroup': int,  
+            'configId': int,  
+            'configRole': int,  
+            'container': {},  
+            'containers': [{}],  
+            'cores': int,  
+            'createBackup': boolean,  
+            'createUser': boolean,  
+            'createdByEmail': 'string',  
+            'createdByFirstName': 'string',  
+            'createdById': int,  
+            'createdByLastName': 'string',  
+            'createdByUser': {'accountId': int,  
+                              'displayName': 'string',  
+                              'email': 'string',  
+                              'firstName': 'string',  
+                              'id': int,  
+                              'lastName': 'string',  
+                              'linuxUsername': 'string',  
+                              'username': 'string',  
+                              'windowsUsername': 'string',  
+            'createdByUsername': 'string',  
+            'customOptions': {'morph_ver': 'string',  
+            'deployGroup': ,  
+            'description': 'string',  
+            'displayName': 'string',  
+            'domainName': 'string',  
+            'environmentPrefix': 'string',  
+            'evars': {  
+            'expireDate': date,  
+            'expireDays': 'string',  
+            'expose': ['string'],  
+            'firewallEnabled': boolean,  
+            'hostName': 'string',  
+            'hostname': 'string',  
+            'id': int,  
+            'instanceContext': 'string',  
+            'instanceLevel': 'string',  
+            'instanceType': {'code': 'string',  
+            'instanceTypeCode': 'string',  
+            'instanceTypeName': 'string',  
+            'instanceVersion': 'string',  
+            'layout': {'code': 'string',  
+                        'id': int},  
+            'layoutCode': 'string',  
+            'layoutId': int,  
+            'layoutName': 'string',  
+            'lbInstances': [{'balanceMode': 'string',  
+                              'enabled': boolean,  
+                              'externalAddress': 'string',  
+                              'id': int,  
+                              'instanceId': int,  
+                              'loadBalancer': {'id': int},  
+                              'loadBalancerId': int,  
+                              'name': 'string',  
+                              'port': int,  
+                              'protocol': 'string',  
+                              'sslCert': 'string',  
+                              'sslRedirectMode': 'string',  
+                              'stickyMode': 'string',  
+                              'vipAddress': 'string',  
+                              'vipDirectAddress': 'string',  
+                              'vipHostname': 'string',  
+                              'vipName': 'string',  
+                              'vipPort': int,  
+                              'vipProtocol': 'string',  
+                              'vipScheme': 'string',  
+                              'vipShared': 'string',  
+            'loadBalancerId': int,  
+            'memory': int,  
+            'memoryDisplay': 'string',  
+            'metadata': {'ver': 'string',  
+            'name': 'string',  
+            'networkLevel': 'string',  
+            'plan': 'string',  
+            'ports': {},  
+            'powerScheduleType': ,  
+            'provisionType': 'string',  
+            'scheduleStatus': 'string',  
+            'servicePassword': 'maskedString',  
+            'serviceUsername': 'string',  
+            'shutdownDays': 'string',  
+            'site': {'accountId': int,  
+                      'active': boolean,  
+                      'id': int,  
+                      'integrations': [],  
+                      'location': 'string',  
+                      'name': 'string',  
+                      'visibility': 'string',  
+                      'zones': [{}]  
+            'sslCertId': int,  
+            'sslEnabled': boolean,  
+            'status': 'string',  
+            'statusMessage': 'string',  
+            'storage': int,  
+            'tags': 'string',  
+            'type': ,  
+            'userGroup': {'id': 'string',  
+            'userStatus': 'string',  
+'instanceContext': 'string',  
+'instanceType': {'code': 'string',  
+'internalIp': 'string',  
+'isDocker': boolean,  
+'layout': {'code': 'string',  
+'localScriptGitId': int,  
+'localScriptGitRef': 'string',  
+'logTag': 'string',  
+'maxCores': int,  
+'maxCpu': int,  
+'maxMemory': int,  
+'maxStorage': int,  
+'memoryDisplay': 'string',  
+'morpheus': {'apiAccessToken': 'string',  
+            'applianceHost': 'string',  
+            'appliancePort': 'string',  
+            'applianceScheme': 'string',  
+            'applianceSsl': boolean,  
+            'applianceUrl': 'string',  
+'morpheusUser': 'string',  
+'mounts': [],  
+'name': 'string',  
+'networkId': int,  
+'networkInterfaces': [{'id': 'string',  
+                      'ipAddress': 'string',  
+                      'ipMode': 'string',  
+                      'network': {'dhcpServer': ,  
+                                  'group': int,  
+                                  'Id': int,  
+                                  'name': 'string',  
+                                  'pool': int},  
+                      'networkInterfaceTypeId': int}],  
+'noAgent': boolean,  
+'platform': 'string',  
+'port': int,  
+'ports': [{'code': 'string',  
+          'displayName': 'string',  
+          'export': boolean,  
+          'exportName': 'string',  
+          'external': int,  
+          'index': int,  
+          'internal': int,  
+          'link': boolean,  
+          'loadBalance': boolean,  
+          'primaryPort': boolean,  
+          'protocol': 'string',  
+          'visible': boolean}],  
+'provisionType': 'string',  
+'publicKeyId': int,  
+'pythonAdditionalPackages': ,  
+'pythonArgs': ,  
+'pythonBinary': 'string',  
+'pythonScript': ,  
+'results': {},  
+'sequence': int,  
+'server': {'agentInstalled': boolean,  
+          'agentVersion': 'string',  
+          'apiKey': 'string',  
+          'category': ,  
+          'cloudConfig': {'agentInstall': agentInstallScript,  
+                          'finalizeServer': finalizeServerScript,  
+                          'meta': metaData,  
+                          'user': userData  
+                                  },  
+          'commType': 'string',  
+          'computeTypeCode': 'string',  
+          'computeTypeName': 'string',  
+          'configGroup': int,  
+          'configId': int,  
+          'configRole': 'string',  
+          'consoleHost': 'string',  
+          'consolePort': int,  
+          'consoleType': 'string',  
+          'consoleUsername': 'string',  
+          'createdByUser': {'accountId': int,  
+                            'displayName': 'string',  
+                            'email': 'string',  
+                            'firstName': 'string',  
+                            'id': int,  
+                            'lastName': 'string',  
+                            'linuxUsername': 'string',  
+                            'username': 'string',  
+                            'windowsUsername': 'string',  
+          'dataDevice': 'string',  
+          'dateCreated': 'string',  
+          'description': 'string',  
+          'displayName': 'string',  
+          'domainName': 'string',  
+          'externalId': 'string',  
+          'externalIp': 'string',  
+          'fqdn': 'string',  
+          'hostname': 'string',  
+          'id': int,  
+          'interfaces': [{'dhcp': boolean,  
+                          'domain': {'fqdn': 'string',  
+                                      'name': 'string',  
+                                      'ouPath': 'string'},  
+                          'interfaceId': int,  
+                          'ipAddress': 'string',  
+                          'ipMode': 'string',  
+                          'ipSubnet': 'string',  
+                          'ipv6Address': 'string',  
+                          'ipv6Subnet': 'string',  
+                          'macAddress': 'string',  
+                          'network': {'cidr': 'string',  
+                                      'cidrMask': 'string',  
+                                      'gateway': 'string',  
+                                      'name': 'string',  
+                                      'netmask': 'string',  
+                                      'vlanId': int},  
+                          'networkPosition': 'string',  
+                          'vlanId': int}],  
+          'internalId': int,  
+          'internalIp': 'string',  
+          'internalName': 'string',  
+          'internalSshUsername': 'string',  
+          'lastAgentUpdate': 'string',  
+          'lvmEnabled': boolean,  
+          'macAddress': 'string',  
+          'managed': boolean,  
+          'maxCores': int,  
+          'maxMemory': int,  
+          'maxStorage': int,  
+          'name': 'string',  
+          'nodePackageVersion': 'string',  
+          'osDevice': 'string',  
+          'osPassword': 'maskedString',  
+          'osType': 'string',  
+          'osTypeCode': 'string',  
+          'osUsername': 'string',  
+          'parentServerId': int,  
+          'plan': 'string',  
+          'platform': 'string',  
+          'platformVersion': 'string',  
+          'powerScheduleType': ,  
+          'powerState': 'string',  
+          'publicKeyId': int,  
+          'serialNumber': 'string',  
+          'serverModel': 'string',  
+          'serverType': 'string',  
+          'serverTypeCode': 'string',  
+          'serverTypeName': 'string',  
+          'serverVendor': 'string',  
+          'softwareRaid': boolean,  
+          'sourceImageId': int,  
+          'sshHost': 'string',  
+          'sshPort': int,  
+          'sshUsername': 'string',  
+          'status': 'string',  
+          'statusMessage': 'string',  
+          'tags': {},  
+          'toolsInstalled': boolean,  
+          'uniqueId': int,  
+          'uuid': 'string',  
+          'visibility': 'string',  
+          'volumes': [{'deviceName': 'string',  
+                        'displayOrder': int,  
+                        'id': int,  
+                        'maxStorage': int,  
+                        'name': 'string',  
+                        'rootVolume': boolean,  
+                        'unitNumber': 'string',  
+'serverId': 'string',  
+'serverName': 'string',  
+'shutdownDays': 'string',  
+'site': {'accountId': int,  
+        'active': boolean,  
+        'id': int,  
+        'integrations': [],  
+        'location': 'string',  
+        'name': 'string',  
+        'visibility': 'string',  
+        'zones': [{}],  
+'sshKey': 'string',  
+'state': {},  
+'storageController': int,  
+'tenant': 'string',  
+'tenantId': int,  
+'tenantSubdomain': 'string',  
+'type': 'string',  
+'user': {'accountId': int,  
+        'attributes': {samlAttributes},  
+        'displayName': 'string',  
+        'email': 'string',  
+        'firstName': 'string',  
+        'id': int,  
+        'lastName': 'string',  
+        'linuxUsername': 'string',  
+        'username': 'string',  
+        'windowsUsername': 'string',  
+'userGroup': {'id': 'string',  
+'userId': int,  
+'userInitials': 'string',  
+'username': 'string',  
+'vm': boolean,  
+'volumes': [{'datastoreId': int,  
+            'id': int,  
+            'maxIOPS': int,  
+            'maxStorage': int,  
+            'name': 'string',  
+            'rootVolume': boolean,  
+            'size': int,  
+            'storageType': int,  
+            'vId': int}],  
+'zone': {'agentMode': 'string',  
+        'cloudTypeCode': 'string',  
+        'cloudTypeName': 'string',  
+        'code': 'string',  
+        'datacenterId': int,  
+        'domainName': 'string',  
+        'firewallEnabled': boolean,  
+        'location': 'string',  
+        'name': 'string',  
+        'regionCode': 'string',  
+        'scalePriority': int}}
+```
+```
+
+NOTE
+
+Variable maps are determined by context, configurations and permissions, actual maps may contain additional or fewer options.
+
+## Spec Template Variables
+
+Spec Template Variables
+
+- **morpheus**
+  - getApiAccessToken()
+  - formatMemory(size, unit)
+  - applianceUrl
+  - applianceHost
+  - appliancePort
+  - applianceScheme
+  - applianceSsl
+  - morpheusHome
+  - morpheusUser
+  - publicKey
+  - privateKey
+  - cloudConfig
+- **cypher**
+  - read(key)
+  - write(key, value)
+  - delete(key)
+  - readUuid(key)
+  - readEncyptionKey(key)
+  - readPassword(key)
+- **archives**
+  - link(bucketName, filePath)
+- account
+- accountId
+- accountType
+- **apps - []**
+  - appContext
+  - description
+  - id
+  - name
+- **cloudConfig**
+  - agentInstall
+  - finalizeServer
+- **customOptions**
+  - key
+- **deployOptions**
+  - key
+- **evars**
+
+  - key
+- **group**
+  - code
+  - datacenterId
+  - location
+  - name
+- groupCode
+- groupName
+- **input**
+  - backup
+  - cloud
+  - computedHostName
+  - computedName
+  - copies
+  - domainOptions
+  - environmentVariables
+  - executionId
+  - expireDays
+  - group
+  - hostName
+  - instanceContext
+  - layout
+  - metadata
+  - name
+  - plan
+  - powerScheduleType
+  - securityGroups
+  - shutdownDays
+  - type
+  - version
+- **instance**
+  - adminPassword
+  - adminUsername
+  - apps - []
+    - appContext
+    - description
+    - id
+    - instances
+    - name
+  - assignedDomainName
+  - autoScale
+  - cloudConfig
+    - agentInstall
+    - finalizeServer
+  - configGroup
+  - configId
+  - configRole
+  - container
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - containers - []
+    - certificatePath
+    - certificateStyle
+    - changeManagementExtId
+    - changeManagementServiceId
+    - cloudConfig
+    - configGroup
+    - configId
+    - configPath
+    - configRole
+    - containerTypeCategory
+    - containerTypeCode
+    - containerTypeName
+    - containerTypeShortName
+    - cores
+    - dataPath
+    - dateCreated
+    - domainName
+    - environmentPrefix
+    - externalIp
+    - hostMountPoint
+    - hostname
+    - id
+    - image
+    - internalHostname
+    - internalIp
+    - logsPath
+    - memory
+    - name
+    - planCode
+    - portMap
+    - ports
+    - provisionType
+    - server
+    - serverId
+    - sshHost
+    - status
+    - storage
+    - version
+  - cores
+  - createdByEmail
+  - createdByFirstName
+  - createdById
+  - createdByLastName
+  - createdByUser
+    - accountId
+    - attributes
+    - displayName
+    - email
+    - firstName
+    - id
+    - lastName
+    - linuxUsername
+    - username
+    - windowsUsername
+  - createdByUsername
+  - customOptions
+    - key
+  - deployGroup
+  - description
+  - displayName
+  - domainName
+  - environmentPrefix
+  - evars
+    - key
+  - expireDate
+  - firewallEnabled
+  - hostname
+  - id
+  - instanceContext
+  - instanceLevel
+  - instanceTypeCode
+  - instanceTypeName
+  - instanceVersion
+  - layoutCode
+  - layoutId
+  - layoutName
+  - memory
+  - metadata
+  - name
+  - networkLevel
+  - plan
+  - ports
+  - provisionType
+  - scheduleStatus
+  - servicePassword
+  - serviceUsername
+  - sslCertId
+  - sslEnabled
+  - status
+  - statusMessage
+  - storage
+  - tags
+  - templateOutput
+  - userStatus
+- platform
+- provisionType
+- **results**
+- sequence
+- **state**
+  - iacDrift
+  - stateDate
+  - stateList - []
+    - category
+    - code
+    - contentPath
+    - errorMessage
+    - iacDrift
+    - id
+    - input
+    - name
+    - output
+    - planPath
+    - resourceVersion
+    - stateContext
+    - stateDate
+    - stateId
+    - statePath
+    - stateType
+    - status
+    - statusMessage
+    - tags
+    - workingPath
+  - stateType
+- tenant
+- tenantId
+- tenantSubdomain
+- type
+- userId
+- userInitials
+- username
+
+</</div>
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json b/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
new file mode 100644
index 0000000..32d3ccc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+  "title": "Cohesity",
+  "ordinal": 382,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.html",
+  "topic_cluster": {
+    "clustering_title": "Cohesity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8",
+        "clustering_title": "Cohesity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md b/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
new file mode 100644
index 0000000..8f7e3b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F21DAFF-8AA3-49EA-A0D9-64449F488BB8.md
@@ -0,0 +1,92 @@
+# Cohesity
+
+HPE Morpheus Enterprise integrates with Cohesity for selection as a Cloud backup target for compatible Cloud types and for adding Cohesity S3 storage servers and storage buckets. HPE Morpheus Enterprise integrates with your existing Cohesity appliance, which can then be set as the default backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. To utilize storage features, integrate a Cohesity S3 storage server and then create a Cohesity S3 storage bucket.
+
+This section discusses the process for integrating Cohesity with HPE Morpheus Enterprise, setting backup options during Instance provisioning, restoring Instances from Cohesity backup, and using Cohesity S3 storage.
+
+## Adding the integration
+
+Cohesity integrations are added in the backup integrations area of the UI (Backups > Integrations). If a Cohesity integration is not an option, you must download and add the Cohesity plugin to the HPE Morpheus Enterprise appliance. For additional information on adding a plugin, including how to access the Hewlett Packard Enterprise-maintained repository which includes the Cohesity plugin, see the [plugin section](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html) of this documentation.
+
+With the Cohesity plugin installed, navigate to Backups > Integrations to add a new Cohesity integration. Click + ADD and a modal appears for creating a new Cohesity backup provider.
+
+![../../_images/createBackupProvider.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F640EDCF-693E-49D1-8ABA-8AC090325603-high.png)
+
+Provide the following information:
+
+- **NAME:** A name for the Cohesity provider in HPE Morpheus Enterprise UI
+- **ENABLED:** When marked, the Cohesity provider will be available for use
+- **HOST:** Enter the host name
+- **CREDENTIALS:** An API key is required for authentication. Select “Local Credentials” to enter the API key directly into this modal. Select “api key” under the “New Credentials” heading to enter the API key directly into this modal and save it in a chosen secure secret store for later use. If an API key has already been stored in an integrated secret store, you may also choose it here rather than directly entering the key into this modal
+- **SECRET STORE:** Optional and only visible if you’ve opted in the CREDENTIALS field to securely store your entered API key
+- **API KEY:** Only visible if authenticating through local credentials (that is, you haven’t selected a saved API key from the CREDENTIALS field). Enter the API key
+- **VISIBILITY:** Cohesity integrations with private visibility are consumable only by the Tenant in which the integration is created
+
+When finished, click SAVE. The new Cohesity backup provider should be successfully created.
+
+## Setting the Cloud Backup Provider
+
+Now that the Cohesity backup provider is created, it can be set as the default backup provider for supported Cloud types. To set this configuration on a Cloud, navigate to the Clouds list page (Infrastructure > Clouds) and edit a compatible Cloud (✎ icon). Expand the “Advanced Options” section and locate the BACKUP PROVIDER configuration. Set the Cohesity provider as the backup provider for the Cloud and click SAVE CHANGES.
+
+![../../_images/editCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AF02E7F0-F125-4FF5-BA08-A35DEE94F1CC-high.png)
+
+## Backup Options at Provision Time
+
+With Cohesity set up as the backup provider for a Cloud (or Clouds), additional backup options are made available when provisioning to the Cloud. These configurations are made from the AUTOMATION tab of the provisioning wizard (launched by clicking + ADD from the Instance list page at Provisioning > Instances). From the AUTOMATION tab, expand the “Backups” section. The BACKUP TYPE of “Cohesity Protection Group” should be preselected. Then, make the next two configurations:
+
+- **BACKUP NAME:** A name for the backup (often named for the Instance associated with the backup)
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group.
+
+![../../_images/noPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-593744EF-D461-44D1-9839-26105B9AA42E-high.png)
+
+If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+![../../_images/yesPg.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0811D470-3CF2-43F5-8689-CA8820605919-high.png)
+
+Once these configurations are provided, complete the provisioning wizard and the configured backup options are applied to the new Instance.
+
+## Creating Backups for Existing Instances
+
+In addition to creating Backups at provision time, as discussed in the previous section, Cohesity backups can be configured for existing Instances. Start from the Backups list page (Backups > Backups) and click + ADD. When the CREATE BACKUP modal appears, select “Instance” from the SELECT SOURCE tab and click NEXT. From the NAME/TYPE tab use the INSTANCE field, which is a typeahead field, to search for a compatible Instance. In the NAME field, enter a name for the new Backup and click NEXT. From the INFO tab, the following configurations are made:
+
+- **BACKUP TYPE:** Cohesity Protection Group
+- **CLUSTER:** Select the correct Cohesity cluster from the dropdown
+
+As a final selection, choose whether or not to create a new Protection Group. If “No” is selected, a dropdown menu appears which allows selection of an existing Protection Group. If “Yes” is selected, additional configuration fields appear to facilitate creation of the Protection Group:
+
+- **PROTECTION GROUP NAME:** A name for the Protection Group
+- **POLICY ID:** Select the required Policy from the dropdown menu
+- **STORAGE DOMAIN:** Select the correct Storage Domain from the dropdown menu
+
+On clicking COMPLETE, the new Backup is successfully created.
+
+## Restoring from Cohesity Backups
+
+To restore an Instance from a Cohesity backup, begin at the Backups list page (Backups > Backups). From the list of Backups, click on the desired backup making sure to click the Backup name and not the name of a Backup Job. On the Backup detail page, note the BACKUP ARCHIVES section. Identify the correct restore point (if more than one are available) and click ACTIONS > Restore. The Instance will be successfully restored from backup.
+
+![../../_images/backupArchives.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6CF1441A-23C0-488D-B250-83D4CE2CAA76-high.png)
+
+## Using Cohesity S3
+
+To work with Cohesity S3, start by creating a Cohesity storage server object in HPE Morpheus Enterprise. To do so, navigate to Infrastructure > Storage > Servers and click + ADD. Make the following configurations:
+
+- **NAME:** A name for the storage server object in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description field
+- **ENABLED:** When marked, the storage server object is available for consumption in HPE Morpheus Enterprise
+- **TYPE:** Cohesity S3. When this type is selected, the required configuration fields appear
+- **ENDPOINT:** The endpoint of the cluster
+- **API KEY:** A valid API key for authentication
+
+Click SAVE CHANGES and the storage server object is created.
+
+![../../_images/createStorageServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F367EF34-C8AE-4D5E-83B2-6ECA4A797481-high.png)
+
+With the storage server created, Cohesity S3 buckets may be created. Buckets are created at Infrastructure > Storage > Buckers. Click + ADD and then Cohesity S3 Bucket. On the NEW BUCKET modal, first select a Cohesity S3 storage server from the STORAGE SERVICE dropdown menu. This will preload other configuration field dropdown menus, such as STORAGE DOMAIN and QOS. From this modal, the bucket can be set as a default backup target or as a default target for Virtual Images or deployment archives. Once finished, click SAVE CHANGES
+
+![../../_images/createBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FB2BEBEB-06B5-4F1A-BCD3-E72DF8E016AD-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json b/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
new file mode 100644
index 0000000..716ebd8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+  "title": "Cisco ACI",
+  "ordinal": 513,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html",
+  "topic_cluster": {
+    "clustering_title": "Cisco ACI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B",
+        "clustering_title": "Cisco ACI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md b/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
new file mode 100644
index 0000000..efdd147
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.md
@@ -0,0 +1,86 @@
+# Cisco ACI
+
+## Overview
+
+![ACI summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E24C5FDE-8C7F-44B1-B150-0FDDAB2B18CE-high.png)
+
+Add ACI as a network and security integration. Inventory your existing ACI configurations. Create networks, bridge domains, application profiles, tenants, endpoint groups, contexts, filters and contracts. Provision instances into new endpoint groups and define security groups that apply contracts on provision.
+
+From Morpheus below can be created:
+
+- Tenants
+- ANP’s
+- EPG’s
+- Contexts
+- Bridge Domains
+- Filters
+- Contracts
+
+NOTE
+
+Morpheus to ACI Sync Job Schedule: Every 5 minutes
+
+NOTE
+
+Morpheus connects to ACI APIC over port 443
+
+## Add Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Networks  >  Integrations
+2. Select +ADD > Networking > `Cisco ACI`
+3. Populate the following: 
+
+   NAME
+   :   ACI Integration Name/Label in HPE Morpheus Enterprise
+       :   This is unique to HPE Morpheus Enterprise and not part of authentication
+
+   URL
+   :   ACI fabric url, eg `https://apicdc.company.com`
+
+   USERNAME
+   :   ACI `aaaUser` name attribute
+
+   PASSWORD
+   :   ACI `aaaUser` pwd attribute
+
+   TENANT
+   :   Populates upon authentication, tenant selection not required
+4. Select ADD NETWORK INTEGRATION
+
+## Configure Cloud Network Mode
+
+### About this task
+
+For your ACI Integration to be available during provisioning, ACI needs to be defined on a Cloud or multiple Clouds `NETWORK MODE` advanced options.
+
+### Procedure
+
+1. Select an existing VMware vCenter Cloud
+2. Select EDIT
+3. Expand the Advanced Options section
+4. Select ACI Integration in `NETWORK MODE` dropdown
+5. Select SAVE
+
+## Instance Provisioning
+
+### About this task
+
+![ACI Instance provisioning options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+Once ACI is integration to a cloud, it can be used during instance provisioning:
+
+### Procedure
+
+1. From the EPG drop down, either an existing EPG can be selected or a new one can be created. It is the same for ANP, either create a new one or choose an existing.
+2. Under ACI security consumes and provides, contracts can be searched when you enter a name. When the provisioning wizard is completed, it will provision the instance and apply the ACI options and Security. This can be viewed under the instance page, or via REST API and CLI.
+
+## Blueprint Configuration
+
+![ACI Blueprint options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E69CABE7-1C08-4798-B0A1-4B9CB2373EF5-high.png)
+
+- In a Blueprint, you can define the ANP and EPG of each Tier
+- Variables can be used for EPG and ANP names.
+- This could be useful to create blueprints for dev testing to isolate from prod networks.
+- This can be hybrid based on the VMM domains in APIC.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json b/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
new file mode 100644
index 0000000..02c4561
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+  "title": "Scaling Morpheus Nodes",
+  "ordinal": 27,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html",
+  "topic_cluster": {
+    "clustering_title": "Scaling Morpheus Nodes",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B",
+        "clustering_title": "Scaling Morpheus Nodes"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md b/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
new file mode 100644
index 0000000..5558479
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.md
@@ -0,0 +1,40 @@
+# Scaling Morpheus Nodes
+
+Morpheus App nodes can be scaled to accommodate additional load. Appliance nodes can be scaled vertically in centralized architectures, and both vertically and horizontally in distributed architectures.
+
+## Vertical Scaling
+
+In all Appliance Architectures, Application nodes can be vertically scaled at any time, however a reconfigure must be performed for additional resources to be utilized by HPE Morpheus Enterprise on a node, which will result in the `morpheus-ui` restarting on the reconfiguring node.
+
+Morpheus configures memory/ram utilization for services during the `reconfigure` process. If additional memory/ram is added to a Host or VM running the Morpheus App, the additional memory/ram will not be utilized by the Morpheus Application until a `morpheus-ctl reconfigure` command is ran and the additional memory/ram is recognized.
+
+IMPORTANT
+
+When the `morpheus-ctl reconfigure` command detects changes on available memory/ram, it will restart the `morpheus-ui` service.
+
+The impact on Availability depends on the Morpheus Appliance Architecture.
+
+- Centralized Appliances
+  :   Morpheus will be unavailable while the `morpheus-ui` restarts.
+- Distributed Appliances
+  :   Zero-down time can be achieved by Reconfiguring one App Node at a time, with proper Front-End Load Balancer configuration.
+
+## Horizontal Scaling
+
+Additional Morpheus App Nodes can be added at any time to Fully Distributed Architectures.
+
+- Configure Shared Storage paths for the new App Node(s)
+- Install, but do not run the `morpheus-ctl reconfigure` command on the new App Node(s), using the same Morpheus version as the existing Appliance nodes.
+- Copy the `morpheus.rb` from an existing App Node to the new App Node(s)
+- Ensure permissions and network configuration for the new App Node(s) to access all MySQL and Elasticsearch nodes, and the RabbitMQ VIP.
+- Ensure permissions and network configuration for all required UI services and Integrations, such as network access to ESXi hosts over 443 for Hypervisor console and/or image transfers.
+- Add associated SSL files and configuration which is not on shared storage.
+- Reconfigure the new App Node(s) via `morpheus-ctl reconfigure`
+- Verify UI startup succeeded
+- Add New App Node(s) to Front End Morpheus UI Load Balancer pool.
+
+During `morpheus-ctl reconfigure`, the new App Node(s) will validate and be configured to use the existing tiers for the UI service. Upon successful reconfigure, the Morpheus service will be available on the App Node(s) with consistent data and capabilities.
+
+NOTE
+
+No services, including `morpheus-ui`, are required to be shut down on existing nodes when adding new App Nodes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json b/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
new file mode 100644
index 0000000..63dfbe9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+  "title": "Alibaba",
+  "ordinal": 388,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.html",
+  "topic_cluster": {
+    "clustering_title": "Alibaba",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B",
+        "clustering_title": "Alibaba"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md b/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
new file mode 100644
index 0000000..b90a2d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-3FCB42C2-A33A-45B0-90AC-8D5EC03A115B.md
@@ -0,0 +1,157 @@
+# Alibaba
+
+## Features
+
+- Brownfield discovery
+- Instance cloning
+- Security group creation and management
+- Docker and Kubernetes provisioning and management
+- Usage tracking
+- Two-way tag sync
+
+## Supported Regions
+
+- ap-northeast-1 (亚太东北 1 (东京)
+- ap-south-1 (亚太南部 1 (孟买)
+- ap-southeast-1 (亚太东南 1 (新加坡)
+- ap-southeast-2 (亚太东南 2 (悉尼)
+- ap-southeast-3 (亚太东南 3 (吉隆坡)
+- ap-southeast-5 (亚太东南 5 (雅加达)
+- cn-beijing (华北 2)
+- cn-chengdu (西南1（成都）)
+- cn-guangzhou (华南3（广州）)
+- cn-hangzhou (华东 1)
+- cn-heyuan (华南2（河源）)
+- cn-hongkong (香港)
+- cn-huhehaote (华北 5)
+- cn-qingdao (华北 1)
+- cn-shanghai (华东 2)
+- cn-shenzhen (华南 1)
+- cn-wulanchabu (华北6（乌兰察布）)
+- cn-zhangjiakou (华北 3)
+- eu-central-1 (欧洲中部 1 (法兰克福)
+- eu-west-1 (英国（伦敦）)
+- me-east-1 (中东东部 1 (迪拜)
+- us-east-1 (美国东部 1 (弗吉尼亚)
+
+## Integrate an Alibaba Cloud with HPE Morpheus Enterprise
+
+To add a new Cloud, navigate to Infrastructure > Clouds and click + ADD. Select “Alibaba Cloud” and click NEXT. Once the “ADD CLOUD” modal appears, configure the following:
+
+- **NAME:** A friendly name for the Cloud in HPE Morpheus Enterprise
+- **CODE:** A Cloud code used to reference this Cloud in HPE Morpheus Enterprise API
+- **LOCATION:** An optional field for tracking location data related to this Cloud
+- **VISIBILITY:** Public Clouds are available to all Tenants, Private Clouds are available to one selected Tenant
+- **TENANT:** If the Cloud visibility is set to “Private”, this field determines which Tenant the Cloud is exposed to
+- **ENABLED:** When marked, the Cloud is available as a provisioning target
+- **AUTOMATICALLY POWER ON VMS:** When marked, HPE Morpheus Enterprise is the source of truth for the expected power state of Instances. HPE Morpheus Enterprise tools should be used to control power state and HPE Morpheus Enterprise will override any unexpected power states (such as if an instance were powered on or off from the Alibaba web console)
+- **CREDENTIALS:** Select Local Credentials to enter authentication credentials on this modal, Existing Credentials to choose a pre-saved credential set, or New Credentials to enter authentication credentials on this modal and save them (in Infrastructure > Trust) for other uses later
+- **ACCESS KEY:** (When Local Credentials or New Credentials are selected) A valid Access Key for an Alibaba Cloud account
+- **SECRET KEY:** (When Local Credentials or New Credentials are selected) A valid Secret Key for an Alibaba Cloud account
+- **INVENTORY:** When marked, HPE Morpheus Enterprise will automatically onboard existing instances in the Alibaba Cloud account as unmanaged servers
+- **REGION:** Select the Alibaba Cloud region to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+- **VPC:** Select the Alibaba Cloud VPC to associate with the Cloud (if this list is empty, check your Access and Secret Key credentials)
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Following Integration
+
+After the integration has been created, HPE Morpheus Enterprise will sync existing workloads (if you’ve opted to inventory), security groups, tags, and more. Synced workloads can be viewed from Infrastructure > Compute. If Plans aren’t immediately available within a few minutes after the integration is created, navigate to the Cloud detail page (Infrastructure > Clouds > Your Integrated Alibaba Cloud), click REFRESH and click “Daily”. Shortly thereafter, the Plans should be synced and selectable at provision time. Without manually syncing the Plans, you may be unable to provision to this Cloud until it undertakes its next daily sync overnight as Plan selection is required.
+
+You’re now able to provision new Instances and Apps to the Alibaba Cloud. HPE Morpheus Enterprise includes a default catalog that includes Alibaba images which can be provisioned out of the box. Additionally, you can begin to create your own custom library of Alibaba workloads by adding Virtual Images and building out Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json b/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
new file mode 100644
index 0000000..20f10e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+  "title": "Creating Network Using the ArubaCX Integration",
+  "ordinal": 434,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Network Using the ArubaCX Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-421A3218-7033-4066-AF8E-AA2D46D4385C",
+        "clustering_title": "Creating Network Using the ArubaCX Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md b/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
new file mode 100644
index 0000000..c159cdf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.md
@@ -0,0 +1,26 @@
+# Creating Network Using the ArubaCX Integration
+
+## Prerequisites
+
+Before starting to create networks using integration, ensure that a Bare metal cloud is created with the ‘Network Mode’ set to the integration. If the Bare metal cloud already exists then ensure that ‘Network Mode’ is set to integration.
+
+## About this task
+
+Perform the following to create the network:
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network.
+3. Click the Add to add a new integration.
+4. Enter the following details for the network:
+   - **Group** for the network
+   - **Network Service** specifies the Network Integration to use
+   - **Name** for the network
+   - **Gateway, DNS** information if required
+   - **CIDR** for the subnet
+   - Primary **VLAN ID** for the network
+   - Check the **Private** checkbox if a private network
+   - **VLAN trunks** for the network (optional)
+   - Choose Network Pool to be one of the IP pools configured![Create network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-68DA56E3-0840-4CA8-B10F-718312751234-high.png)
+5. Click Save Changes to create the network.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json b/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
new file mode 100644
index 0000000..a1e72ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+  "title": "Code Integrations",
+  "ordinal": 100,
+  "parent_title": "Code",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html",
+  "topic_cluster": {
+    "clustering_title": "Code Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44272A47-8855-48A0-B475-E940CE97DD7A",
+        "clustering_title": "Code Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md b/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
new file mode 100644
index 0000000..595cc13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44272A47-8855-48A0-B475-E940CE97DD7A.md
@@ -0,0 +1,16 @@
+# Code Integrations
+
+The Provisioning ‣ Code ‣ Integrations section is where Code Integrations, such as Git and Github Repository Integrations, and Jenkins Build Service Integrations, can be created and managed.
+
+## Role Permissions
+
+Access and capabilities for the **Integrations** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json b/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
new file mode 100644
index 0000000..1d80b10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+  "title": "Backups",
+  "ordinal": 254,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html",
+  "topic_cluster": {
+    "clustering_title": "Backups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53",
+        "clustering_title": "Backups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md b/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
new file mode 100644
index 0000000..3af9fb8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.md
@@ -0,0 +1,191 @@
+# Backups
+
+The HPE Morpheus Enterprise built-in Backup solution provides VM, Container, Host, Database, File, Directory, Volume and Storage Provider Backup, Snapshot and Replication capabilities. Backups can be automatically configured during provisioning or manually created at any time. Backup Jobs with custom Execution Schedules and retention counts can be created and used across all environments in conjunction with configured Storage Providers. Backups can be restored over current Instances or as new Instances, and downloaded or deleted from HPE Morpheus Enterprise.
+
+HPE Morpheus Enterprise also integrates with external services to automate availability with other providers.
+
+## Initial Backups Setup
+
+Global Backup settings (Administration > Settings > Backups), Storage Providers (Infrastructure > Storage) and Execution Schedules (Library > Automation > Execute Scheduling) should be configured prior to creating backups. Global backup settings are where scheduled backups can be globally enabled or disabled and certain global backup default settings can be configured. Storage providers include local and remote configured storage locations that can be used as backup targets. Execution schedules are timed intervals at which individual automated backup jobs will run. See the next two sections for full details on global backup settings and configuring execution schedules. See HPE Morpheus Enterprise UI [Storage Documentation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html) for more information about configuring local and remote storage targets and/or integrating with third party storage providers.
+
+### Global Backups Settings
+
+HPE Morpheus Enterprise Backups can be enabled under Administration > Settings > Backups.
+
+Scheduled Backups
+:   When enabled, configured Backups will automatically run on their configured schedules. If disabled, backups need to be manually run.
+
+Create Backups
+:   When enabled, HPE Morpheus Enterprise will automatically configure backup jobs for Instances at provision time.
+
+Backup Appliance
+:   When enabled, a Backup will be created to backup the HPE Morpheus Enterprise appliance database. Select the `Backup` text link to edit the Appliance Backup Settings and view existing Appliance Backups.
+
+Default Backup Bucket
+:   From this dropdown, select the default storage bucket to be used for future created Backups. If needed, new storage providers can be configured and managed in the Infrastructure > Storage section.
+
+Default Backup Schedule
+:   From this dropdown, select a default execution schedule for future created Backups. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+Backup Retention Count
+:   The default maximum number of successful backups to retain.
+
+Default Synthetic Full Backup Enabled
+:   When enabled, supported workload types will have periodic full synthetic backups scheduled by default in addition to any typical backups (full backup followed by incremental backups) that may also be scheduled.
+
+Default Synthetic Full Backups Schedule
+:   From this dropdown, select a default execution schedule for future full synthetic backups. In general, this should be at a longer internal than incremental backups that are also scheduled. If needed, new schedules can be configured in Library > Automation > Execute Scheduling.
+
+### Execution Schedules
+
+Backup Execution Schedules can be configured and managed in Library > Automation > Execute Scheduling. An execution schedule stores only the interval at which some execution should be run and they can apply to both backups and automation scripts. To create a new backup job with this schedule, navigate to Backups  >  Backups and click “+ADD”. In the final step of creating the backup job we are able to select any of our created execution schedules. The Default Backup Schedule set in Administration > Settings > Backups will be selected when creating a backup job and not specifying an execution schedule.
+
+## Configuring Backups during Provisioning
+
+When Backups are enabled, Backup options are presented in the AUTOMATION tab of the provisioning wizard. Note that your default backup bucket and default backup schedule will be set according to your global backup settings as mentioned in the previous sections.
+
+NOTE
+
+The Backup options presented in the Automation tab can be disabled using a “Create Backup” Policy. See [`Policies`](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)
+
+BACKUP TYPE
+:   Select the type for the Backup. Backup Types displayed will be filtered by available options for the selected Instance Layout
+
+BACKUP NAME
+:   Defaults to the Instance name
+
+BACKUP TARGET
+:   Select the Storage Provider target for the Backup (when applicable)
+
+BACKUP JOB TYPE
+:   Create a new job, clone an existing job, or Add to existing job
+
+JOB NAME
+:   Defaults to the Instance name
+
+RETENTION COUNT
+:   Maximum number of successful backups to retain
+
+BACKUP SCHEDULE
+:   Select the schedule for the backup job from the list of existing execution schedules
+
+SYNTHETIC FULL (Currently only available for KVM VM Snapshot-type backups, such as those used with HVM Instances. More Layout types are expected to support synthetic full backups in the future)
+:   When checked, an additional schedule is configured for the backup job during which a synthetic full backup will be taken. In general, this should be on a longer time period than that at which standard backups (full backup followed by incremental backups) are configured
+
+SYNTHETIC FULL SCHEDULE
+:   Select the schedule for the backup job on which synthetic full backups should be taken
+
+Backup Types displayed will be filtered by available options per selected Instance Layout. Many backup job types are supported including (but not limited to):
+
+- File Backup
+- Directory Backup
+- MySQL
+- MongoDB
+- LVM Snapshot
+- LVM Image
+- LVM Migration
+- Windows Migration
+- Postgres
+- Tar Directory Backup
+- Amazon VM Snapshot
+- VMWare VM Snapshot
+- Fusion VM Snapshot
+- Xen VM Snapshot
+- Veeam VMWare VM Backup
+- Veeam Hyper-V VM Backup
+- Google VM Snapshot
+- Commvault File/Directory Backup
+- Azure VM Snapshot
+- Morpheus Appliance
+- Openstack VM Snapshot
+- DigitalOcean VM Snapshot
+- Nutanix VM Snapshot
+- Softlayer VM Snapshot
+- Hyper-V VM Snapshot
+- VMWare VM Snapshot
+- SCVMM VM Snapshot
+- UpCloud VM Snapshot
+- Bluemix VM Snapshot
+- Alibaba VM Snapshot
+- Oracle Cloud VM Snapshot
+- KVM VM Snapshot
+- Container Backup
+- VM Backup
+- Object Storage Backup
+
+## Summary
+
+The Backups Summary section shows the following metrics:
+
+- Number of Configured Backups trend
+- Backup Success Rate
+- Number of Completed Backups
+- Number of Failed Backups
+- Total Size of Backups (MB) trend
+- Upcoming and In Progress Backups
+
+If a User’s Role permission for Backups is set to User, the user will only see metrics for backups they own.
+
+![../_images/backupSummary.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A241F036-0867-4093-88ED-6F98CE2D6BD9-high.png)
+
+## Backups
+
+In the Backups > Backups section, currently-configured Backups can be viewed and managed, and new Instance, Host and Provider backups be configured. Backups must be tied to a Backup Job, which holds the retention count and the schedule on which the backup should automatically be run. You can create a new Job at the same time as the backup is created or you can create the job ahead of time and associate any new backups to the existing job.
+
+NOTE
+
+Role permissions for Backups determine which backups will be accessible to the individual user.
+
+### Create an Instance Backup
+
+#### About this task
+
+To create Instance backup:
+
+#### Procedure
+
+1. Navigate to Backups > Backups
+2. Click + ADD
+3. From the Create Backup Wizard select the radio button for Instance, then click NEXT
+4. Input the following: 
+
+   Instance
+   :   Select an Instance to backup from the typeahead menu
+
+   Name
+   :   Enter a name for the backup job being created
+5. Click NEXT
+6. Depending on the Instance Type selected in the previous step, enter additional details. These can include a specific container, backup type, database name, username and password, or a number of other things depending on the Instance Type
+7. Configure the storage bucket and retention details: 
+
+   Storage
+   :   Select a configured storage bucket as the backup target
+
+   Backup Job Type
+   :   Create a new backup job, add this backup to an existing job, or clone an existing job to handle this backup
+
+   Job Name
+   :   If creating a new job, enter a name for the job
+
+   Retention Count
+   :   If creating a new job, enter the number of backups which should be simultaneously retained
+
+   Schedule
+   :   If creating a new job, select an execution schedule of which to run the backup
+
+   Synthetic Full
+   :   When the backup is targeting an HVM Instance, check this box to schedule synthetic full backups in addition to the normal full and incremental backups
+
+   Synthetic Full Schedule
+   :   If synthetic full backups are enabled, select an execution schedule on which to run the synthetic full backups
+8. Click COMPLETE.
+
+#### Results
+
+NOTE
+
+On VMware Cloud types, HPE Morpheus Enterprise will merge and consolidate the snapshots held against a VM before exporting the OVF to the storage location or share. This is so HPE Morpheus Enterprise has a full and consistent copy of the VM state.
+
+TIP
+
+To edit an existing backup, click on the hyperlinked name of the backup job from the list of backups at Backups > Backups.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json b/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
new file mode 100644
index 0000000..a435585
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+  "title": "Unable to Delete Tenant",
+  "ordinal": 357,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Delete Tenant",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2",
+        "clustering_title": "Unable to Delete Tenant"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md b/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
new file mode 100644
index 0000000..5ba4195
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.md
@@ -0,0 +1,22 @@
+# Unable to Delete Tenant
+
+Problem
+:   When trying to delete a tenant, a message stating manage resources must be removed or other error occurs and the tenant is not deleted. The tenant may be stuck in a deleting status or return to OK status after delete attempt.
+
+Cause
+:   All managed resources must be removed from a tenant in order for that tenant to be deleted. This includes instances and their underlying managed vm’s
+
+Solution
+:   1. Login or impersonate that an Admin user inside the tenant
+    2. Navigate to Infrastructure > Hosts
+    3. Under Hosts and VM’s, delete any managed resources
+
+       - Uncheck `remove infrastructure` when deleting a VM to only remove it from HPE Morpheus Enterprise but not from the underlying hypervisor/cloud
+       - You must check `remove associated instances` if the VM has an associated instance
+       - If the VM no longer exists but there is still a record in HPE Morpheus Enterprise, uncheck `remove infrastructure` and check `force delete`
+    4. Once all managed resources are removed from the tenant, the tenant can then be deleted
+    5. In certain situations other components may prevent a tenant from being deleted. If you have removed all managed resources from a tenant and the tenant still cannot be deleted, please contact HPE Morpheus Enterprise support
+
+WARNING
+
+Managed resources can also be removed by deleting instances, but be aware this will delete VM’s associated with the instance from the underlying hypervisor/cloud
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.json b/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
new file mode 100644
index 0000000..b7a6727
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+  "title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+  "ordinal": 354,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44644079-BC85-448F-B542-23E18E9D5602",
+        "clustering_title": "HPE Morpheus Enterprise UI not loading after upgrade or reconfigure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.md b/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
new file mode 100644
index 0000000..7b1c1ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44644079-BC85-448F-B542-23E18E9D5602.md
@@ -0,0 +1,72 @@
+# HPE Morpheus Enterprise UI not loading after upgrade or reconfigure
+
+Problem:
+:   The HPE Morpheus Enterprise ui does not load after performing an upgrade.
+
+Common Causes:
+:   1. The morpheus-ui has not finished loading
+    2. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+    3. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+Solutions:
+:   1. The morpheus-ui has not finished loading.
+
+       An easy way to see when the ui is finished loading and running is to tail the ui current file and look for the morpheus logo with version and start time
+
+       ```
+       ```
+       morpheus-ctl tail morpheus-ui
+       ```
+       ```
+
+    NOTE
+
+    After running morpheus-ctl start morpheus-ui, the HPE Morpheus Enterprise ui takes around 3 minutes to run depending on hardware.
+
+    1. The morpheus-ui was not fully stopped before reconfigure, or not started after reconfigure
+
+       The morpheus ui must be stopped prior to running morpheus-ctl reconfigure when upgrading. Sometimes running morpheus-ctl stop morpheus-ui will timeout and the ui is not actually stopped. If stopping the ui does timeout, run morpheus-ctl kill morpheus-ui prior to reconfigure, and be sure to run morpheus-ctl start morpheus-ui after reconfigure is completed. If you ran a reconfigure before stopping the ui, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl reconfigure  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
+
+       Wait for the ui to come up.
+    2. HPE Morpheus Enterprise was forced to restart or shut down while the database schema was being migrated during an upgrade
+
+       If the ui fails to start and you see the error `Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by morpheus` it likely means morpheus was forced to restart or shut down while the database schema was being migrated during an upgrade, and the lock was not released. To release the lock, you will need to run a mysql query. You will need to install mysql-client on the morpheus appliance, and grab the password for morpheus mysql. The username and db name are both morpheus. The password to login to mysql can be found in the application.yml file located at `/opt/morpheus/conf/application.yml` Then run the following:
+
+       ```
+       ```
+       mysql -u morpheus -p -h 127.0.0.1 morpheus
+       ```
+       ```
+
+       At the prompt, enter the mysql password from the application.yml Then run:
+
+       ```
+       ```
+       DELETE FROM DATABASECHANGELOGLOCK;
+       ```
+       ```
+
+       Then restart morpheus-ui:
+
+       ```
+       ```
+       sudo morpheus-ctl restart morpheus-ui
+       ```
+       ```
+
+       If the restart timesout, run:
+
+       ```
+       ```
+       sudo morpheus-ctl kill morpheus-ui  
+       sudo morpheus-ctl start morpheus-ui
+       ```
+       ```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json b/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
new file mode 100644
index 0000000..897e644
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+  "title": "Images",
+  "ordinal": 253,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html",
+  "topic_cluster": {
+    "clustering_title": "Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53",
+        "clustering_title": "Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md b/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
new file mode 100644
index 0000000..25b9a1a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.md
@@ -0,0 +1,69 @@
+# Images
+
+Morpheus provides Images for ESXi, CentOS, Ubuntu and XenServer, and user can add their own Images.
+
+## Add Images
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab then click the Add Image button.
+4. From the Upload Virtual Image Wizard input the following information 
+
+   Name
+   :   Name of the Image.
+
+   Operating System
+   :   List of available operating systems.
+
+   Storage Provider
+   :   List of available storage providers.
+
+   Image Path
+   :   Path of the image.
+
+   Visibility
+   :   Private or Public
+
+   Account
+   :   List of accounts to allow permission to this image.
+5. Save Changes
+
+## Edit Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Images tab
+4. Click the actions drop down and select edit.
+5. Modify information as needed.
+6. Click the Save Changes button to save.
+
+## Convert Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Convert.
+
+## Download Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Images tab
+4. Click the Actions drop and select Download.
+
+## Remove Image
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar.
+3. Select the Image tab.
+4. Click the Actions drop and select Remove.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json b/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
new file mode 100644
index 0000000..0450c3a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+  "title": "Utilization: Utilization vs Cost",
+  "ordinal": 65,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html",
+  "topic_cluster": {
+    "clustering_title": "Utilization: Utilization vs Cost",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C",
+        "clustering_title": "Utilization: Utilization vs Cost"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md b/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
new file mode 100644
index 0000000..36b9800
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.md
@@ -0,0 +1,30 @@
+# Utilization: Utilization vs Cost
+
+![../_images/8utilization.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-98D09465-88F7-420B-AEF8-80393CC3A8B7-high.png)
+
+The Utilization vs Cost dashboard is designed to reveal workloads which are underutilized (expensive and seldom-used) and which are very cost-efficient (inexpensive and frequently-used). Administrators can filter the workloads considered by the dashboard through the use of filters and potentially identify areas of cost savings by decommissioning seldom-used machines.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Workload name (all matching search terms)
+- Time period (Current, one-day average, one-week average, one-month average, three-month average, six-month average, or one-year average)
+- Type (virtual machines, hosts, or bare metal)
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **COUNT:** The total number of workloads that meet dashboard filters
+- **CLOUD COUNT:** The total number of Clouds represented by the selected workloads
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **AVERAGE UTILIZATION:** The computed average utilization figure for all workloads selected by dashboard filters
+
+## Utilization List
+
+In addition to the totals and graph displayed, two workload lists are given showing the least utilized workloads by cost (lowest utilization per cost dollar) and the least utilized workloads overall (lowest utilization overall). These workloads are listed with links to the Instance or server detail pages, along with other details related to price and resource utilization.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json b/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
new file mode 100644
index 0000000..3aceb30
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+  "title": "HPE Alletra MP Storage",
+  "ordinal": 522,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Alletra MP Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD",
+        "clustering_title": "HPE Alletra MP Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md b/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
new file mode 100644
index 0000000..426f999
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.md
@@ -0,0 +1,316 @@
+# HPE Alletra MP Storage
+
+## Prerequisites
+
+- All HPE Alletra MP Storage iSCSI ports are reachable from each of the cluster hosts
+- The `multipath.conf` settings on each node should be configured as follows:
+
+```
+```
+defaults {  
+    find_multipaths yes  
+    user_friendly_names no  
+}
+```
+```
+
+Before you set up Active-Active Peer Persistence (AAPP) replication, ensure that the following requirements are met:
+
+**Supported configurations**
+
+- Remote Copy is configured using either Fibre Channel (RCFC) or IP (RCIP).
+- Replication targets are synchronous only.
+- HPE Alletra MP B10000 arrays are running OS version 10.5.0 or later.
+- AAPP replication supports only a 1:1 target mapping.
+
+**Array configuration (outside VM Essentials)**
+
+- Complete the AAPP Remote Copy configuration on both primary and secondary arrays.
+- Configure replication ports and define targets on both arrays.
+- Configure a Quorum Witness for the arrays.
+
+For more information about array configuration, see HPE GreenLake for Block Storage UI 2.5 User Guide.
+
+**VM Essentials setup**
+
+- Add both primary and secondary arrays as Storage Servers in Infrastructure > Storage > Server.
+- Create a datastore on both the primary and secondary Storage Servers.
+
+## Add HPE Alletra MP Storage
+
+### About this task
+
+The first step is to create a storage server in HPE Morpheus Enterprise. Once the storage server is added, you can create a datastore and provision Instances. Follow these steps to add a Storage Server:
+
+### Procedure
+
+1. Navigate to Infrastructure > Storage
+2. In the “Servers” tab, Click the + ADD button
+3. From the ADD STORAGE SERVER wizard, input the following: 
+
+   NAME:
+   :   Name of the storage server in HPE Morpheus Enterprise
+
+   TYPE:
+   :   Select “HPE Alletra MP”
+
+   URL:
+   :   URL of HPE Alletra MP Storage (ex. `https://storage-system.example.com` or `https://192.1.2.3:1234`)
+
+   USERNAME:
+   :   Add your administrative user account
+
+   PASSWORD:
+   :   Add your administrative user account password
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/add-storage-server.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-432FC4EC-3961-492E-9423-55CC7E6BCACA-high.png)
+
+The Storage Server will be added and displayed in the Datastore tab.
+
+## Create Datastore
+
+### About this task
+
+Add a Datastore to the Storage Server.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clusters.
+2. Click into the detail page for the cluster where the datastore is to be created.
+3. Select the Storage tab.
+4. Under the Data Stores sub tab, click + ADD.
+5. From the ADD DATASTORE wizard, input the following: 
+
+   NAME:
+   :   Name of the datastore in HPE Morpheus Enterprise.
+
+   TYPE:
+   :   Select the type of storage system.
+
+   STORAGE SERVER:
+   :   Select the storage server that is created using the ADD STORAGE SERVER wizard.
+
+   PROTOCOL TYPE:
+   :   Select the type of storage protocol.
+
+   RANSOMWARE DETECTION:
+   :   Select the check box to enable ransomware detection for all VMs created with this datastore.
+
+   NOTE
+
+   The datastore creation fails if storage servers other than HPE Alletra Storage MP B10000 are selected along with the Ransomware Detection option.
+
+   CPG
+   :   Use the drop-down list to select a Common Provisioning Group (CPG) for allocating storage to the new datastore.
+6. Click SAVE.
+
+### Results
+
+![Add data store](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6894A520-8797-40DF-9252-2F696167BA9F-high.png)
+
+The datastore is added and displayed in the Datastore tab. Confirm that its status is healthy.
+
+## Create Instance
+
+### About this task
+
+Create an Instance with the Datastore.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. In the Instances tab, Click the + ADD button
+3. From the ADD INSTANCE wizard input the following: 
+
+   - From the TYPE section: Select “HVM”
+   - Click NEXT
+
+     ![../../_images/create-instance-type.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-55F890E0-47C6-4621-9A97-C399B1AD1BB0-high.png)
+   - From the GROUP tab, input the following:
+
+     GROUP:
+     :   Select the Group for the Instance
+
+     CLOUD:
+     :   Select the Cloud for the Instance
+
+     NAME:
+     :   Name for the Instance in HPE Morpheus Enterprise
+   - Click NEXT
+
+     ![../../_images/create-instance-group.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4EEB766E-54E0-4C82-A60B-59AE6B75D705-high.png)
+   - From the CONFIGURE tab, input the following:
+
+     LAYOUT:
+     :   Select the Layout for the Instance
+
+     PLAN:
+     :   Select the Plan for the Instance
+
+     RESOURCE POOL:
+     :   Select the Resource Pool (Cluster) for the Instance
+
+     VOLUMES:
+     :   Add one or more Volumes to the Instance. Select the datastore created in the previous section
+
+     NETWORK:
+     :   Add Networks to the Instance
+
+     IMAGE:
+     :   Select the Image for the Instance
+
+     HOST:
+     :   Select the cluster host for the Instance
+
+     Other configurations may be added as needed.
+
+     ![../../_images/create-instance-configure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-358491C6-43F7-4197-9F53-94D50A1E99F1-high.png)
+   - Click NEXT
+   - Add Automation Tasks, if needed
+   - Click NEXT
+   - Review the Instance configuration
+   - Click COMPLETE![../../_images/create-instance-review.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-22C7AB89-6966-4E4D-8514-6A2FAD489B61-high.png)
+
+### Results
+
+The Instance is now provisioned to the new datastore and is viewable within the Instances (Provisioning > Instances) section.
+
+## Add a storage server
+
+The first step is to create a storage server in VM Essentials. After the storage server is added, you can view the storage summary and alerts, and view or edit volumes. For more information on adding a storage server, see [Add HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-9C460D6B-1616-47E0-9FF7-7AD7DD4ADDE3).
+
+### Viewing the Summary page
+
+The Summary tab displays system information, capacity utilization of the system, and the number of ransomware alerts detected
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server. The Summary tab displays the information for the selected server. ![Summary tab](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CADEC596-4D47-4B87-85E1-DC2756B5DAD8-high.png)
+
+   The Summary tab contains:
+
+   - **System**
+
+     The following information is displayed in the System tile:
+     - **Name**: Displays the system name of the selected server.
+     - **Model**: Displays the model name of the system.
+     - **Serial Number**: Displays the serial number of the system.
+     - **Health status**: Displays the system health status of the array depending on the highest severity type of the alerts listed in the Alerts tab for the storage system. The health status values can be Critical, Normal, or Warning.
+
+       | Highest Severity Type of Alerts | Health status |
+       | --- | --- |
+       | Critical or Fatal | Critical (The system has some major issues that will affect performance) |
+       | Major | Warning (The system is operational but with some non-critical issues) |
+       | Other types | Normal (The system is functioning as expected) |
+     - **Firmware version**: Displays the firmware version of the storage system.
+     - **WWN**: Displays a unique identifier name of the system.
+     - **Uptime**: Displays the total time the system has been operational.
+     - **IP Address**: Displays the IP address of the system.
+   - **Capacity Utilization**
+
+     The Capacity Utilization tile displays the total and used capacity percentage of the selected storage system.
+
+     - For models HPE Alletra MP B10000 and later, the Capacity Utilization tile populates the usable capacity.
+     - For models prior to HPE Alletra MP B10000, the Capacity Utilization tile populates the raw capacity information.
+
+     NOTE
+
+     You can get the latest system information by clicking the Summary tab.
+   - **Ransomware Detection**
+
+     The Ransomware Detection tile displays the number of ransomware alerts detected. A hyperlink is displayed when more than one ransomware alert is detected; otherwise, it is displayed as a plain text.
+
+     On clicking the hyperlink, you can view the details of alert by selecting Ransomware monitoring as the Filter by Type.
+
+     ![Alerts - ransomware monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0E521724-F9E5-4619-B9D9-BB943E488958-high.png)
+   - **Protection**
+
+     Using the Filter by drop-down list, you can view the protection status for a `VM` or an `Instance`.
+
+     This tile displays the snapshot protection and remote replication status of both virtual machines (VMs) and instances on the storage system. You can also view the total percentage of VMs or Instances that are protected. Protection is determined based on snapshot availability with or without remote replication. The protection data is auto-refreshed periodically.
+
+     NOTE
+
+     Hover over the information (i) icon beside each field to display the description.
+
+     For VMs, the following information is displayed:
+     - **Snapshot:** Count of VMs where each volume has a point-in-time snapshot.
+     - **Remote Replication:** Count of VMs that have replicated volumes.
+     - **Snapshot + Remote Replication:** Count of VMs that have replicated volumes, where each volume also has a point in time snapshot.
+     - **Unprotected:** Count of VMs that have neither replicated volumes nor point-in-time snapshot on any volume.
+
+     For Instances, the following information is displayed:
+     - **Snapshot:** Count of instances where every volume associated with each VM has a point-in-time snapshot.
+     - **Remote Replication:** Count of instances where every volume associated with each VM is replicated.
+     - **Snapshot + Remote Replication:** Count of instances where each associated VM has replicated volumes and every volume has a point-in-time snapshot.
+     - **Unprotected:** Count of instances where each associated VM neither has replicated volumes nor point-in-time snapshot on any volume.
+     - **Partially Protected:** Count of instances where some, but not all, of the instance's VMs have snapshots and can be in remote replication.
+
+### Viewing Alerts
+
+The Alerts tab displays system alerts with severity levels of Fatal, Critical, or Major.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server.
+3. Select the Alerts tab.
+4. Select the type of alert that you want to view from the Filter by Type drop-down list.
+5. The alerts displayed in the Alerts tab provide the following information:
+   - **Severity**: Displays the severity of the alert. The severity can be Fatal, Critical, or Major. The severity of the alert determines the health status of the system.
+   - **Type**: Displays the type of the alert message.
+   - **Message**: Displays the description of the alert message.
+   - **Time**: Displays the time when the alert was created. The UTC timezone is the standard timezone in HPE Morpheus Enterprise.![Alerts tab](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-46AEA56B-E951-48EC-8781-EEAF84D5ADB7-high.png)
+
+### Volumes tab
+
+#### Viewing Volumes
+
+The Volumes tab provides a list of all volumes, including their summary, capacity information, and ransomware monitoring status.
+
+1. Navigate to Infrastructure > Storage > Servers.
+2. In the Servers tab, select the server name.
+3. Select the Volumes tab. You can view the following information:
+   - **Name**: Displays the volume name for the VM.
+   - **Details**: Displays the CD Drive volume or data disk associated with the VM name.
+   - **Usage**: Displays a progress bar. The progress bar displays:
+     - Used capacity in percentage.
+     - Used capacity in either GiB or TiB, based on its value, in comparison to the total capacity.
+   - **Ransomware Monitoring**: Indicates whether ransomware monitoring is enabled or disabled for the volume. Ransomware monitoring is enabled or disabled while creating the datastore.
+
+     NOTE
+
+     Once ransomware monitoring is enabled for a datastore, the ransomware monitoring status cannot be edited​.
+   - **IOPS**: Displays the number of read and write operations performed by the volume each second.
+   - **Throughput**: Displays the amount of data transferred to or from the volume each second.
+
+   ![Volumes tab](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8E25EA50-EEC7-48EA-8FCF-973EB252A822-high.png)
+
+#### Editing volumes
+
+##### About this task
+
+You can edit the volumes individually for VMs created without selecting the Ransomware Detection check box in the ADD DATA STORE screen.
+
+##### Procedure
+
+1. Create a datastore without selecting the Ransomware Detection check box. 
+
+   To create a datastore, go to Infrastructure > Clusters, click the cluster name, then click Storage > Add. For more information on creating a datastore, see [Create Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-5332DFF1-C4D9-4CB9-9EB7-53E9A73719DE).
+2. Create a VM with the Ransomware Detection disabled datastore.
+
+   To begin provisioning a VM instance with the Ransomware Detection disabled datastore, go to Provisioning > Instances. For more information on creating a VM instance, see [Create Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html#GUID-C292527A-7464-4C79-9C27-A51681D8A157).
+3. Navigate to Infrastructure > Storage > Servers > Volumes tab.
+
+   The Actions drop-down menu is available for each volume that has the Ransomware Detection disabled.
+
+   NOTE
+
+   For VMs created with Ransomware Detection enabled datastore, the Actions drop-down is not displayed for such volumes.
+4. Click Actions > Edit.
+
+   The EDIT VOLUME message is displayed.
+
+   ![Edit volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-79282845-7740-4731-9DAF-BDAA8AC698BB-high.png)
+5. To change the status, select the Ransomware Detection check box if it is disabled or clear the check box if it is enabled.
+6. Click Save. The changes to the ransomware monitoring are saved.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json b/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
new file mode 100644
index 0000000..366c7c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+  "title": "Packages",
+  "ordinal": 312,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.html",
+  "topic_cluster": {
+    "clustering_title": "Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8",
+        "clustering_title": "Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md b/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
new file mode 100644
index 0000000..5b58eca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45D7E88A-1424-4577-BE72-AE5A9248EEC8.md
@@ -0,0 +1,130 @@
+# Packages
+
+## Overview
+
+Packages are code files used to define HPE Morpheus Enterprise resources, which can then be uploaded and used in any HPE Morpheus Enterprise appliance they may be needed in. HPE Morpheus Enterprise packages (.morpkg, .mpkg, or .mopkg) are added in the Administration > Integrations > Packages section of the UI. HPE Morpheus Enterprise packages contain Library and automation objects, such as Instance Types, Layouts, Node Types, Tasks, Spec Temples and Cluster Layouts. Following upload of a valid package, the defined HPE Morpheus Enterprise resources are immediately available for use in the appliance.
+
+The addition of `/administration/packages` is primarily targeted for uploading future HPE Morpheus Enterprise-provided packages, however users can create, distribute and/or import custom HPE Morpheus Enterprise packages too. This section goes over the process for writing and preparing packages for upload to a HPE Morpheus Enterprise appliance.
+
+## Role Permissions
+
+Access and capabilities for the **Packages** section is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Plugins`
+:   - None: Cannot access Admin: Plugins section
+    - Full: Access to Admin: Plugins and ability to upload HPE Morpheus Enterprise packages (`.morpkg`, `.mpkg`, or `.mopkg`)
+
+## Getting Started
+
+Packages consist of two primary parts, a `.json` manifest file (which sets some metadata about the package) and one or more `.scribe` files which define the resources to be added. These files are zipped and imported into HPE Morpheus Enterprise as one file (`.morpkg`, `.mpkg`, or `.mopkg`). Scribe files are written in HCL (Hashicorp Configuration Language) and follow referenced resource naming. In the next section, we will define the required attributes for both the `.json` manifest and the scribe files with examples.
+
+When uploading packages to HPE Morpheus Enterprise, keep in mind that the same packages can be reinstalled as many times as desired. When the same package is reinstalled, any local changes to those resources made in the HPE Morpheus Enterprise appliance will be overwritten. For example, if a Task has been created by package and changes are made locally to the Task config within HPE Morpheus Enterprise, subsequent uploads of the packages would overwrite those changes. A better method for making changes to package-sourced resources would be to update the package code, increase the version number, and upload the package once again. This ensures important local changes would not be overwritten by subsequent uploads. There is no warning given in the UI, changes are simply overwritten without notice.
+
+Additionally, it’s worth noting that while packages can be deleted (🗑 icon on the packages detail page), you will simply delete the package from the list. HPE Morpheus Enterprise will show a helpful list of resources added with the package if cleanup is desired but will not delete them.
+
+## Creating Packages
+
+As noted in the last section, a package consists of a `.json` manifest file and any number of `.scribe` files. We’ll first look at the manifest file, its purpose, and attributes that must be included in the JSON map.
+
+A typical package manifest looks like this:
+
+```
+```
+{  
+    "type": "scribe",  
+    "name": "morpheus-ubuntu-22.04-vmware",  
+    "code": "morpheus-ubuntu-22.04-vmware",  
+    "organization": "morpheus",  
+    "version": "20240415"  
+}
+```
+```
+
+The manifest includes each of the following attributes:
+
+- **TYPE:** Tells HPE Morpheus Enterprise to process all included files with the package as scribe files. Currently, this is the only supported type
+- **NAME:** This is the name for the package that will appear in HPE Morpheus Enterprise UI. The example manifest above came from a package that adds resources for an Ubuntu 22.04 library item to HPE Morpheus Enterprise, and is named to indicate that
+- **CODE:** Not visible in UI but exists for referencing the package via HPE Morpheus Enterprise API
+- **ORGANIZATION:** Appears only in the database but can be exposed via HPE Morpheus Enterprise API
+- **VERSION:** Listed in HPE Morpheus Enterprise UI and is useful for tracking changes over time to package-sourced resources
+
+Scribe files are quite a bit more complicated and have not yet been fully documented publicly. Nevertheless, we can show a couple examples here and give strategies for extracting additional examples from your own environment. Certain resources will require reference to other resources included with the scribe file. Here’s a simple scribe file creating a shell script-type “Hello World” Task:
+
+```
+```
+resource "task" "HelloWorld" {  
+  name = "HelloWorld"  
+  uuid = "2c2306e0-3b30-4886-b8a3-d1362c9b9490"  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  executeTarget = "resource"  
+  labels = [ "export" ]  
+  lastUpdated = "2024-04-19T19:18:40.000Z"  
+  options = [  
+    { optionType = { code = "shell.sudo" }, value = "on" },  
+    {  
+      content = { uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0" }  
+      optionType = { code = "script" }  
+    }  
+  ]  
+  taskType = { code = "script" }  
+}  
+resource "file-content" "ff5de589-75da-48ec-ba66-5fe5905397b0" {  
+  uuid = "ff5de589-75da-48ec-ba66-5fe5905397b0"  
+  content = "echo \"Hello World\""  
+  dateCreated = "2024-04-19T19:15:47.000Z"  
+  lastUpdated = "2024-04-19T19:15:47.000Z"  
+}
+```
+```
+
+In this case, the Task config was written locally in the Add/Edit Task modal within HPE Morpheus Enterprise rather than sourced from elsewhere (such as a Github repository). The Task content itself is a distinct resource and is referenced in the Task resource by UUID. Outside resources can also be referenced by HCL referenced resource naming such as in the following example where a `workload-type` resource references a `virtual-image` resource:
+
+```
+```
+resource "virtual-image" "vmware_vsphere_image_morpheus_almalinux_9_20240324" {  
+  code = "vmware_vsphere_image_morpheus_almalinux_9_20240324"  
+  category = "vmware.vsphere.image.morpheus.almalinux"  
+  name = "Morpheus AlmaLinux 9 XX-DATE-XX"  
+  imageType = "vmdk"  
+  remotePath = "https://s3-us-west-1.amazonaws.com/morpheus-images/vmware/20240324/almalinux-9/morpheus-almalinux-9-x86_64-20240324.ovf"  
+  imagePath = "vmware/20240324/almalinux-9"  
+  isCloudInit = true  
+  systemImage = true  
+  installAgent = true  
+  osType {  
+    code = "almalinux.9.64"  
+  }  
+  zoneType = "vmware"  
+}  
+resource "workload-type" "vmware_almalinux_9" {  
+  code = "vmware-almalinux-9"  
+  shortName = "almalinux"  
+  name = "AlmaLinux 9"  
+  ports = [22]  
+  containerVersion = "9"  
+  entryPoint = ""  
+  mountLogs = "/var/log"  
+  statTypeCode = "vm"  
+  logTypeCode = "vm"  
+  showServerLogs = true  
+  category = "almalinux"  
+  cloneType = "almalinux"  
+  priorityOrder = 0  
+  serverType = "vm"  
+  providerType = "vmware"  
+  containerPorts = [{code = "almalinux.22"}]  
+  actions = [{code = "generic-remove-node"}]  
+  checkTypeCode = "containerCheck"  
+  virtualImage = virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324  
+  provisionType = "vmware"  
+  backupType = "vmwareSnapshot"
+```
+```
+
+The specific virtual image is referenced as `virtual-image.vmware_vsphere_image_morpheus_almalinux_9_20240324`.
+
+To go further, you can generate additional examples from your own environments. Use the [Import/Export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html#import-and-export) feature built into HPE Morpheus Enterprise and export your created resources into integrated Git repositories. When viewing the results in your repositories, you’ll see the resources are exported as scribe files.
+
+## Preparing and Uploading Packages
+
+To prepare the package, ensure the manifest and scribe files are gathered into one directory. You’ll then need to zip the contents of that directory with a valid extension (`.morpkg`, `.mpkg`, or `.mopkg`). In Linux, from outside the directory, you can use: `zip -j <package-name>.mpkg <directory-name>/*`. The package is now ready to be uploaded. Navigate to Administration > Integrations > Packages on any appliance and use the file picker tool to upload your new package file.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json b/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
new file mode 100644
index 0000000..833336a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+  "title": "Storage Considerations",
+  "ordinal": 5,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539",
+        "clustering_title": "Storage Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md b/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
new file mode 100644
index 0000000..f5cb6e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.md
@@ -0,0 +1,47 @@
+# Storage Considerations
+
+Upon initial installation HPE Morpheus Enterprise takes up less than 10 GB of space, however HPE Morpheus Enterprise Services, Virtual Images, Backups, Logs, stats, and user-uploaded and imported data require adequate space on the HPE Morpheus Enterprise Appliance(s) based on appliance configuration and activity. HPE Morpheus Enterprise recommends at least 200 GB as a general figure to start from but storage needs will vary dramatically based on each specific use case. In some cases, significantly more space will be needed.
+
+IMPORTANT
+
+It is the customer’s responsibility to ensure adequate storage space per configuration and use case. The appliance should be properly monitored to ensure it does not run low on disk space.
+
+## Default Paths
+
+`/opt/morpheus`
+:   Morpheus Application and Services Files
+
+`/var/opt/morpheus`
+:   User, Application and Services Data, including default config Opensearch, RabbitMQ and Database data, default Virtual Image path, and working directory for Backups
+
+`/var/opt/morpheus/morpheus-ui` (HA Installations Only)
+:   In an HA Installation, a NFS share is required and mounted to this location. Virtual Images, Plugins, and other shared files are stored at this path to be accessible for all nodes
+
+`/home`
+:   Morpheus service account home data, such as configuration files
+
+`/var/log`
+:   Morpheus Service logs
+
+`/tmp`
+:   Storage for any temp files created by Morpheus or the operating system
+
+## Images
+
+Virtual Images can be uploaded to HPE Morpheus Enterprise Storage Providers for use across Clouds. By default when no Storage Provider has been added, images will write to `/var/opt/morpheus/morpheus-ui/vms`. Please ensure adequate space when uploading Images using local file paths.
+
+## Backups
+
+HPE Morpheus Enterprise can offload snapshots when performing backups to local or other Storage Providers. By default when no Storage Provider has been added, backups will write to `/var/opt/morpheus/bitcan/backups/`. When using none NFS Storage providers, the backup file(s) must be written to `/var/opt/morpheus/bitcan/working/` before they can be zipped, sent to the destination Storage provider such as S3, and removed from `/var/opt/morpheus/bitcan/working/`. Please ensure adequate space in `/var/opt/morpheus/bitcan/` when offloading Backups.
+
+NOTE
+
+The backup /working and /backups paths are configurable in morpheus.rb with bitcan[‘working\_directory’] = ‘$path’ and bitcan[‘backup\_directory’] = ‘/tmp’
+
+## VM Logs and Stats
+
+When using HPE Morpheus Enterprise with a locally-installed Elasticsearch configuration, VM, Container, Host and Appliance logs and stats are are stored in Elasticsearch. Please ensure adequate space in `/var`, specifically `/var/opt/morpheus/elasticsearch` in relation to the number of Instances reporting logs, log frequency, and log retention count. With partition space at 85% filled or higher (by default), Elasticsearch will enter an unhealthy state and the HPE Morpheus Enterprise appliance will not function properly.
+
+## HPE Morpheus Enterprise Services Logs
+
+Logs for services local to the HPE Morpheus Enterprise Appliance, such as the Morpheus UI, elasticsearch, rabbitmq, mysql, nginx and guacd are written to `/var/log/morpheus/`. Current logs are rotated nightly, zipped, and files older than 30 days are automatically removed. Misconfigured services, ports and permissions can cause excessive log file sizes.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json b/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
new file mode 100644
index 0000000..d255f1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+  "title": "Terraform Blueprints",
+  "ordinal": 137,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-46A53E20-D2A8-4233-8829-7865C7A434B7",
+        "clustering_title": "Terraform Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md b/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
new file mode 100644
index 0000000..73963fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-46A53E20-D2A8-4233-8829-7865C7A434B7.md
@@ -0,0 +1,42 @@
+# Terraform Blueprints
+
+Terraform Blueprints are one way that Terraform can be integrated and leveraged with HPE Morpheus Enterprise, with the other being the HPE Morpheus Enterprise Terraform provider which is not discussed in this section. HPE Morpheus Enterprise and Terraform are complimentary technologies which together can increase efficiency and simplify automation across cloud environments. For more on this relationship, see our [whitepaper](https://www2.morpheusdata.com/Morpheus-and-Terraform) on how HPE Morpheus Enterprise and Terraform are better together.
+
+Currently, HPE Morpheus Enterprise supports provisioning Apps based on Terraform Blueprints to VMware, Amazon, Azure, and Oracle Clouds with additional Cloud support coming in future releases. On first attempt to provision a Terraform App, HPE Morpheus Enterprise will automatically install Terraform. It is possible in some operating system configurations for this automated installation process to fail, requiring you to install Terraform manually. If needed, manual installation instructions and guidance are provided [here](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-installation).
+
+To create a new Terraform Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Terraform. NEXT
+
+![../../../_images/new_blueprint.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-65A40826-21ED-4A71-83F9-0951FA0B62B7-high.png)
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+The Terraform Configuration section is where the Terraform template file (.tf) is added or linked to the Blueprint. Using a Config Type of “Terraform (.tf)” or “Terraform JSON (.tf.json)”, you can write or paste your configuration directly into the new Blueprint. Alternatively, you can pull in config files from an integrated Git repository using the “Git Repository” Config type.
+
+In the Terraform Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “Terraform (.tf)” or “Terraform JSON (.tf.json)” to create or paste configuration directly into the new Blueprint
+- **CONFIG:** Enter your configuration here
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section or HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+In the Terraform Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+- **TFVAR SECRET:** Select an existing TFVar-formatted Cypher. See the Cyphers section of HPE Morpheus Enterprise docs for more information on Cyphers
+- **OPTIONS:** Enter any additional options, such as a variable definition
+
+Once finished, click COMPLETE.
+
+Your new Terraform Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json b/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
new file mode 100644
index 0000000..8e772f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+  "title": "Cancelling Workflow Tasks",
+  "ordinal": 117,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html",
+  "topic_cluster": {
+    "clustering_title": "Cancelling Workflow Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE",
+        "clustering_title": "Cancelling Workflow Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md b/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
new file mode 100644
index 0000000..d1b8f5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.md
@@ -0,0 +1,11 @@
+# Cancelling Workflow Tasks
+
+When a Workflow is running, HPE Morpheus Enterprise offers the capability of cancelling a Task and stopping any subsequent Tasks from starting. When viewed later in History or Executions, this leaves the Task and Workflow in a cancelled state. This is useful if you have a very long-running Task that you know will fail and wish to cancel or if you want to prevent a “retryable” Task from running again.
+
+To cancel a Workflow, open the execution. Within the running Task will be a cancel button, click the button to interrupt the Workflow. Once cancelled, see that the Workflow and Task are now considered to be in a cancelled state which is shown in the UI. At this point the cancel button becomes a retry button and the Task could be resumed if desired.
+
+NOTE
+
+Cancelling a Task doesn’t actually interrupt the process already running on the workloads themselves. It simply interrupts the Workflow and stops it from continuing. Behind the scenes, HPE Morpheus Enterprise allows the running process to complete or time out rather than risk corrupting data with a non-graceful interrupt.
+
+![../../_images/cancelTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-47300BA8-9B05-428D-835A-1975B04DE84E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json b/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
new file mode 100644
index 0000000..84b3a4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+  "title": "Provisioning Workflow Execution Phases",
+  "ordinal": 113,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Workflow Execution Phases",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50",
+        "clustering_title": "Provisioning Workflow Execution Phases"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md b/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
new file mode 100644
index 0000000..f1ee446
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.md
@@ -0,0 +1,18 @@
+# Provisioning Workflow Execution Phases
+
+| Phase | Description | Usage Example | Notes |
+| --- | --- | --- | --- |
+| Configuration | Tasks are run prior to initial calls to the specified cloud API to initiate provisioning | Call to an external platform to dynamically generate a hostname prior to kicking off provisioning or dynamically altering configuration of a Catalog Item prior to provisioning |  |
+| Price | Price Phase Tasks are only invoked when the Workflow is tied to a Layout. Like the Configuration Phase, these Tasks are run prior to any calls made to the target Cloud API and allow pricing data to be overridden for the Workload being provisioned. A “spec” variable containing Instance config is passed into the Task and a specific return payload is expected in order to work properly. Any other pricing (such as on the Service Plan) is overridden. See the section below for a detailed example of this Phase being used. | An MSP customer calling out to a custom pricing API to deliver Instance pricing to their own customers. | See the section below on Price Phase implementation for a detailed setup example. |
+| Pre Provision | For VMs, Tasks are run after the VM is running and prior to any Tasks in the Provision phase. For containers, Tasks in this phase are run on the Docker host and prior to `docker run` | Prepare a Docker host to run containers | Pre Provision can be used for a Blueprint so it is added before a script which is set at the Provision phase executes. Pre Provision for scripts is mainly for Docker as you can execute on the host before the container is running. |
+| Provision | Like pre‐provision, Tasks for VMs are run after the VM is running. For containers, these Tasks are run on the containers once they are running on the host. For many users, this is the most commonly‐used phase. | Join the server to a domain | Tasks included with in the Provision phase are considered to be vital to the health of the Instance. If a Task in the Provision phase fails, the Workflow will fail and the Instance provisioning will also fail. Tasks not considered to be vital to the existence of the Instance should go in the Post Provision phase where their failure will not constitute failure of the Instance. |
+| Post Provision | Tasks are run after the entire provisioning process has completed | Disable UAC or Windows Firewall on a Windows box or join Active Directory | When adding a node to an Instance, Tasks in this phase will be run on all nodes in the Instance after the new node is provisioned. This is because Post Provision operations may need to affect all nodes, such as when joining a new node to a cluster. Tasks in Pre Provision and Provision phases would only be run on the new node in this scenario. |
+| Start Service | Tasks in this phase are intended to start the service associated with the Instance type. | Include a script to start the service associated with the Instance (such as MySQL) which will execute when the Start Service action is selected from the Instance detail page | Start services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Stop Service | Tasks in this phase intended to stop the service associated with the Instance type. | Include a script to stop the service associated with the Instance (such as MySQL) which will execute when the Stop Service action is selected from the Instance detail page | Stop services is manually run from the Instance detail page and is designed to refer to the service the Instance provides. |
+| Pre Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, prior to the deploy taking place. | Extract files from a deploy folder and move them to their final positions prior to deploy | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Deploy | Tasks in this phase are run when a new deploy is triggered from the Deploy tab of the Instance detail page, after the deploy has completed | Update configuration files or inject connection details from the environment at completion of the deploy process | Deployments are manually triggered from the Instance detail page and are designed to refer to deployment of services, like a website or database. |
+| Reconfigure | Tasks in this phase are run when the reconfigure action is made against an Instance or host | Rescan or restart the Instance after a disk is added |  |
+| Teardown | Tasks are run during VM or container destroy | Remove Active Directory objects prior to tearing down the Instance |  |
+| Scale Down | Tasks are run when a node is removed from an Instance. This does not apply to Clusters when a worker node is removed. |  |  |
+| Shutdown | Tasks are run immediately before the target is shutdown | Send an update on Instance power state to a CMDB |  |
+| Startup | Tasks are run immediately before the target is started | Send an update on Instance power state to a CMDB |  |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json b/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
new file mode 100644
index 0000000..eecf60b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+  "title": "VDI Pools",
+  "ordinal": 272,
+  "parent_title": "Tools",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.html",
+  "topic_cluster": {
+    "clustering_title": "VDI Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2",
+        "clustering_title": "VDI Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md b/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
new file mode 100644
index 0000000..e97990b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-47FFBF50-97FD-460E-AB64-F8FE49F6CFF2.md
@@ -0,0 +1,383 @@
+# VDI Pools
+
+The VDI Pools section of HPE Morpheus Enterprise Tools provides a management area for defining VDI Pools and VDI Apps that a user can consume within the [Virtual Desktop Persona](https://docs.morpheusdata.com/en/latest/personas/personas.html#morpheus-virtual-desktop-environments-beta).
+
+Pools can be either persistent or non-persistent and have various controls pertaining to idle pools and minimum or maximum sizes. The idea here is to make sure a server is always quickly available to accommodate user demand.
+
+HPE Morpheus Enterprise leverages its Instance Types concept for provisioning servers within the VDI Pool. All the options available during Instance provisioning is available for setting the base server configuration. This includes Workflows, domain joins, tagging, image selection and more.
+
+A timeout setting can also be applied to release pool allocations from a user once they have disconnected their session. For non-persistent pools, a good recommendation is ten minutes whereas, for a persistent pool, a sensible recommendation would be around one hour.
+
+Pool behavior changes depending on the pool type. In a non-persistent pool, when a timeout period expires, the VM is destroyed and a new one is allocated for use. This functionality will change based on the cloud technology in a future update allowing for potential recycling of the VMs. In a Persistent pool, when the lease timeout expires, the Instance will shutdown until the user requests it again in the future. It is important to note that lease timeouts auto-extend for as long as the user is logged into or browsing any area of the HPE Morpheus Enterprise application. Once the user closes their browser or logs out of their session, the timeouts will no longer auto-extend.
+
+## Configuring Access to VDI Pools
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None” (controls access to the Virtual Desktop Persona view)
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection (controls access to launch virtual desktop instances from configured pools)
+6. Access the Features tab and expand the Provisioning section
+7. Set “Remote Console” permission to Full and “Remote Console Auto Login” permission to Yes (allows user access to VDI sessions)
+8. Role changes are saved automatically, there is no need to manually save
+
+### Results
+
+Additionally, users should have a Linux and/or Windows username and password configured in their user profiles in order for virtual desktop login to be as seamless as possible. User profiles are accessed by clicking on the user’s name in the upper-right corner of the application windows and clicking USER SETTINGS. The section to enter Windows and Linux account credentials is in the right column of the page.
+
+## Creating VDI Templates
+
+### About this task
+
+NOTE
+
+The following guide focuses on VMware and Windows but is applicable to most cloud environments. HPE Morpheus Enterprise also supports Linux virtual desktops.
+
+### Procedure
+
+1. Create a thin-provisioned VM in the VMware vCenter console. It’s recommended you allocate at least 50 GB of storage, at least 2 vCPU and at least 8 GB RAM on the template. Smaller VMs can be deployed from this template later.
+2. Install a Windows operating system, there is no need to supply a license during deployment.
+3. Supply the initial username and password
+4. Install any updates, applications or optimizations. See the next section for recommended optimizations for the most performant virtual desktop experience
+5. Shutdown the VM and convert to a template. Optionally, you can also use the Linked Clones (VMware) process which is described in a later section
+
+### Suggested Optimizations
+
+Reducing display and input delays is key to providing the best virtual desktop experience for the user. Consider the following optimizations for VDI desktops and servers:
+
+- Disable desktop wallpapers
+- Implement Roaming Profiles
+- Enforce WDDM remote display driver
+- Re-enable local Administrator
+- Delete the initial created user profile
+- Clean up any unneeded installer packages
+
+Additionally, there are a number of OS optimization tools available on the Internet which are specific to VDI use cases.
+
+### Linked Clones
+
+#### About this task
+
+Linked Clones are a feature of VMware which references snapshots of a VM to deploy from. This adds the advantage of quicker clone times and the ability to more easily share small modifications to a file system. HPE Morpheus Enterprise supports Linked Clones but recommends them for VDI workloads only.
+
+NOTE
+
+Linked Clones are not templates but rather powered down VMs.
+
+#### Procedure
+
+1. Locate the VM you desire to have the Linked Clone in HPE Morpheus Enterprise. If it’s not currently managed by HPE Morpheus Enterprise, navigate to the appropriate Cloud (Infrastructure > Clouds), find the VM on the “VMs” tab, and click “Convert to Managed” from the ACTIONS menu
+2. In the CONVERT TO INSTANCE modal, select “No Agent Install” in the AGENT field
+3. If snapshots are already on the VM, these will now be synced by HPE Morpheus Enterprise. If you have not yet created a snapshot, do so in the vCenter console (and refresh the Cloud integration in HPE Morpheus Enterprise afterward) or from the ACTIONS menu in HPE Morpheus Enterprise itself. Be sure to take a snapshot of a powered-off VM and give the snapshot a name that will be identifiable for administrators
+4. From the Instance detail page in HPE Morpheus Enterprise, navigate to the Backups tab to find the snapshot
+5. Select “More” and create the Linked Clone
+6. The Linked Clone will now appear in the HPE Morpheus Enterprise Virtual Image repository (Library > Virtual Images), ready to use with your custom Layouts
+
+#### Results
+
+NOTE
+
+You should modify the Virtual Image to “Force Guest Customization” unless you `sysprep` your VM at shutdown time
+
+## Creating or Editing a VDI Pool
+
+VDI pools are configured from the Tools menu (VDI Pools selection). The following information is displayed in the VDI pools list view, bear in mind some fields may be hidden depending on how you’ve configured your VDI pools list view (gear icon):
+
+- **TYPE:** An icon indicating the machine type associated with the pool. HPE Morpheus Enterprise includes many logos out of the box and also allows users to set their own custom icons
+- **NAME:** The friendly name given to the VDI pool
+- **PERSISTENT:** A check mark will appear when the VDI pool is configured for persistent virtual desktops
+- **ENABLED:** A check mark will appear when the VDI pool is enabled and visible to users whose Role permissions allow them access
+- **POOL USAGE:** A graph representing the usage of the VDI pool. The total length of the bar represents the maximum pool size based on the configuration. Green segments represent available virtual desktops, blue segments represent reserved virtual desktops, yellow segments represent virtual desktops which are being prepared, and gray segments represent additional pool capacity which could be made available depending on how many virtual desktops are currently reserved and how many idle machines you’ve configured the pool to keep available
+- **DESCRIPTION:** A description of the virtual desktop type, if provided
+
+![../../_images/vdiPools.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-03AD0B76-424F-40CE-BF86-0D1D4C81A991-high.png)
+
+Create a VDI pool by selecting + ADD from the VDI Pools tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI pool in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual desktop type
+- **MIN IDLE:** The minimum number of virtual desktops that should remain idle and ready
+- **INITIAL POOL SIZE:** The number of virtual desktops that will be prepared when the pool is created or enabled
+- **MAX IDLE:** The maximum number of virtual desktops that remain idle and ready. Machines will be shut down as necessary when this number is exceeded due to users vacating their machines
+- **MAX SIZE:** The total number of virtual desktops this pool can have. Additional users will not be able to access machines once this number is reached
+- **LEASE TIMEOUT (MINUTES):** The user lease time on a virtual desktop they’ve reserved. The lease will continue to auto-renew itself as long as the user is logged into HPE Morpheus Enterprise. Once the user has logged out and the lease timeout period has expired, the machine will be released as appropriate based on your configuration
+- **PERSISTENT:** Pools with persistent virtual desktops will reserve a machine for each user in order to preserve settings, installed applications, work files and more. Machines in persistent pools will be shut down rather than destroyed when they are no longer in use
+- **RECYCLABLE:** When enabled, the VDI Instance will revert back to a snapshot and become available once again after the user has logged out and the VDI session has expired. This behavior will not apply to VDI pools which are also configured to be persistent because in that configuration the Instance is merely stopped and saved for the user’s next session. This feature is currently only available for Cloud types which support snapshot management (VMware, Nutanix, and vCD)
+- **ALLOW COPY** Enables or disables the ability for the VDI user to copy contents from the VDI instance to the local clipboard
+- **ALLOW PRINTER** When enabled, users local system printers can be targeted from the VDI Instance
+- **ALLOW HYPERVISOR CONSOLE:** When checked, native cloud console will be enabled (if available) rather than using HPE Morpheus Enterprise-native RDP/SSH capability
+- **AUTO CREATE LOCAL USER UPON RESERVATION:** When marked, the user configured in HPE Morpheus Enterprise user settings will be created when the machine is initially accessed. If unchecked or if there is no user configured in HPE Morpheus Enterprise user settings, ensure the machine is joining a domain or there is a known user on the machine image in order to allow access
+- **ENABLED:** When marked, the initial pool size will begin to deploy once the VDI pool is saved. The icon for this desktop environment will also be presented to Virtual Desktop Persona users
+- **CONFIGURE:** Click this button to configure the deployment configuration each system will use. The wizard is identical to the Instance provisioning wizard meaning all available Instance Types, Workflows, and more are available to virtual desktop machine creation. Consult the steps above to see an example VDI image prep walkthrough
+- **LOGO:** Upload or select a logo to represent the virtual desktop type to users
+- **VDI APPS:** Optionally select one or more frequently-used applications the user can launch directly. Users will also have the option to launch into the desktop
+- **VDI GATEWAY** Select a configure VDI Gateway for VDI sessions to be redirected to. VDI sessions will be redirected to the gateway when a gateway is specified.
+
+**Guest Console SSH Tunnel** (optional)
+:   A Jump Host can be configured for VDI session connections. HPE Morpheus Enterprise will tunnel through the Jump Host when connecting Guest Console sessions for VDI. This is not applicable for Hypervisor Console connections.
+
+- **GUEST CONSOLE JUMP HOST** Jump Host IP address or hostname used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP USERNAME** Jump Host Username used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PORT** Jump Host Port used to connect to the Jump Host for Guest Console sessions to VDI Instances
+- **GUEST CONSOLE JUMP PASSWORD** Jump Host Password used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if key specified)
+- **GUEST CONSOLE KEYPAIR** Jump Host SSH Key used to connect to the Jump Host for Guest Console sessions to VDI Instances (optional if password specified)
+
+NOTE
+
+A Guest Console Keypair included here must be a local keypair, not a synced keypair.
+
+![../../_images/createVdiPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B80B0A34-FE78-4289-A475-03068127D897-high.png)
+
+## Creating or Editing a VDI Apps
+
+### About this task
+
+VDI Apps allow users to launch directly into commonly-used apps rather than the OS desktop. Currently, VDI Apps only work with RDP Windows Instances, taking advantage of native Windows Remote Application functionality. Natively-hosted remote desktop applications can only be presented from Windows 10 Enterprise and Education. Other versions of Windows 10 can present remote applications using the procedure below:
+
+### Procedure
+
+1. Open the Windows Registry Editor
+2. Locate the following entry: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Terminal Server\TSAppAllowList`
+3. Navigate to `fDisabledAllowList` and set its value to “1” in the right-hand pane
+4. Add a new key under `TSAppAllowList` and name it “Applications”
+5. Add a new key under “Applications” using any name you’d like
+6. Within this new key, create two new string values, one called “Name” and one called “Path”
+7. The string value for “Name” should describe the application (ex. “Notepad”)
+8. The string value for “Path” should be the absolute path to the executable for that application (ex. “C:WindowsSystem32notepad.exe”)
+
+### Results
+
+VDI Apps are created by selecting + ADD from the VDI Apps tab or edit an existing one by clicking on the pencil icon from the appropriate row. Configure the following, fields containing a vertical blue bar along the left edge are required:
+
+- **NAME:** A friendly name for the VDI App in HPE Morpheus Enterprise
+- **DESCRIPTION:** A description of the virtual app type
+- **LAUNCH PREFIX:** A reference to the remote app registry prepended with two pipes ( `||` ). For example, we might create a registry “Chrome” for a Chrome browser VDI App and the associated launch prefix would be “||Chrome”
+- **LOGO:** Upload or select a logo to represent the virtual app type to users
+
+## VDI Gateways
+
+The HPE Morpheus Enterprise Worker is a light weight distributed worker daemon as well as a scalable VDI Gateway. Currently, the features center around VDI Gateway but will expand to support full plugin workloads as well as agent relay capabilities.
+
+### Adding VDI Gateways to HPE Morpheus Enterprise
+
+VDI Gateways can be linked to a HPE Morpheus Enterprise appliance and then used in VDI Pool configurations. VDI sessions will be redirected to configured gateways instead of the HPE Morpheus Enterprise appliance when a VDI Gateway is specified for a VDI Pool.
+
+NOTE
+
+A VDI Gateway is a separate VM or container Instance used to route users to VDI Instances. The HPE Morpheus Enterprise VDI Gateway section is for configuring a connection to a VDI Gateway, not creating the gateway Instance itself.
+
+- **NAME** Specify a name for the VDI Gateway in HPE Morpheus Enterprise. Note that the VDI Gateway Name is not used when connecting to the gateway
+- **DESCRIPTION** Specify a description for the VDI Gateway in HPE Morpheus Enterprise. (optional)
+- **GATEWAY URL** The url of the VDI Gateway. This url is used to connect to the gateway, and should match the the worker url of the VDI Gateway.
+
+Upon creation, the VDI Gateway record will produce an `API KEY`. This `API KEY` needs to be specified in the `morpheus-worker.rb` file on the API Gateway itself under `worker['apikey'] = '$API_KEY'`. Once the gateway object is created you will need to configure it as the default gateway in HPE Morpheus Enterprise global settings (Administration > Settings > Appliance). Scroll down to the “Default Console Gateway” setting and select the gateway object you’ve just created. Continue on to the next section to actually install the gateway and configure it with your API key.
+
+### VDI Gateway VM Install
+
+A VDI Gateway VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+VDI Gateway Package URLs are available at <https://app.morpheushub.com> in the downloads section.
+
+#### Requirements
+
+##### About this task
+
+Table 1. Supported VDI Gateway Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 9, 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE, SLES | 12 |
+| Ubuntu | 16.04, 18.04, 20.04 |
+
+- **Memory:** 4 GB RAM minimum recommended for default installations supporting up to 20 concurrent sessions. Add 50 MB RAM per additional concurrent session
+- **Storage:** 10 GB storage minimum recommended. Storage is required for VDI Gateway Packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity to and from HPE Morpheus Enterprise appliance and from users to the VDI Gateway over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise VDI Gateway package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+##### Procedure
+
+1. Download the target distro & version package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+   ```
+   ```
+2. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-worker-$version.distro
+   ```
+   ```
+3. Next install the package using your selected distribution’s package installation command and your preferred opts. Example, for RPM: 
+
+   rpm:
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-worker-$version.$distro  
+   Preparing...                          ################################# [100%]  
+   Updating / installing...  
+      1:morpheus-worker-5.3.1-1.$distro    ################################# [100%]  
+   Thank you for installing Morpheus Worker!  
+   Configure and start the Worker by running the following command:  
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+4. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following: 
+
+   ```
+   ```
+   worker_url 'https://gateway_worker_url' # This is the gateway URL the |morpheus| appliance can resolve and reach on 443  
+   worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of |morpheus| appliance which the gateway can reach on port 443  
+   worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from |morpheus| Appliance VDI Pools > VDI Gateways configuraiton
+   ```
+   ```
+
+   NOTE
+
+   By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+5. After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services: 
+
+   ```
+   ```
+   sudo morpheus-worker-ctl reconfigure
+   ```
+   ```
+
+   The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+6. Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+### VDI Gateway Docker Install
+
+To Use VDI Gateway within a Docker container, a few pieces of information are needed.
+
+Firstly, in HPE Morpheus Enterprise, go to **Tools > VDI Pools > VDI Gateways** and create a new VDI Gateway Record. Be sure to set the HTTPS URL as HPE Morpheus Enterprise will need to be able to redirect the user’s browser to that page. An API Key will be generated. Make note of this as you will need it later.
+
+Now Simply run with:
+
+```
+```
+docker run -d -p 8443:8443  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheusAppliance.url morpheusdata/morpheus-worker:latest``
+```
+```
+
+This will setup an HTTPS self-signed exposed port on 8443 for the vdi gateway. It is highly recommended to use valid certificates on your VDI Gateways. It could be terminated at the VIP or a p12 SSL File can be used and configured for the container.
+
+If the docker entrypoint detects a file at `/etc/certs/cert.p12`, SSL Will be enabled on port 8443 instead. be sure to set environment variables `MORPHEUS_SSL_ALIAS` and `MORPHEUS_SSL_PASSWORD` when using p12 files.
+
+If you wish to run in HTTP mode and SSL terminate at the VIP, you can run the container like so:
+
+```
+```
+docker run -d -p 8080:8080  -e MORPHEUS_SELF_SIGNED=true -e MORPHEUS_KEY=[apiKey] -e MORPHEUS_URL=https://my.morpheus.url morpheusdata/morpheus-worker:latest
+```
+```
+
+### VDI Gateway Helm Chart Installation
+
+First, configure the Helm repository:
+
+```
+```
+helm repo add morpheusdata https://gomorpheus.github.io/helm-charts-morpheus/
+```
+```
+
+Next, install the HPE Morpheus Enterprise worker using `helm install`. You can specify each parameter using `--set key=value[,key=value]` arguments as in the following example:
+
+```
+```
+helm install morpheus-worker --set replicaCount="1" morpheusdata/morpheus-worker
+```
+```
+
+Alternatively, you can create a values YAML file and pass an argument as in the following example:
+
+```
+```
+helm install -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+Upgrading the workers node(s) is as simple as refreshing the repo and using `helm upgrade`:
+
+```
+```
+helm repo update  
+helm upgrade -f values.yaml morpheus-worker morpheusdata/morpheus-worker
+```
+```
+
+To uninstall, use one of the following:
+
+```
+```
+helm uninstall morpheus-worker
+```
+```
+
+or
+
+```
+```
+helm delete morpheus-worker --purge
+```
+```
+
+NOTE
+
+`helm delete` removes all the Kubernetes components associated with the chart and deletes the release.
+
+The following table lists the configurable parameters of the Sentry chart and their default values:
+
+Table 2.
+
+     | Parameter | Description | Default |
+| --- | --- | --- |
+| image.repository | Image repository | morpheusdata/morpheus‐worker |
+| image.tag | Image tag. Possible values listed here. | 5.3.1‐4 |
+| image.pullPolicy | Image pull policy | IfNotPresent |
+| env.MORPHEUS\_KEY | API Key for Morpheus Worker |  |
+| env.MORPHEUS\_URL | Morpheus FQDN with protocol |  |
+| env.MORPHEUS\_SELF\_SIGNED | Is Morpheus using a Self Signed Certificate | false |
+| service.type | Kubernetes service type for the GUI | ClusterIP |
+| service.port | Kubernetes port where the GUI is exposed | 8989 |
+| livenessProbe.initialDelaySeconds | Initial delay (seconds) for liveness monitoring | 5 |
+| livenessProbe.timeoutSeconds | Timeout (seconds) before health check considered unhealthy | 5 |
+| livenessProbe.periodSeconds | Poll interval (seconds) between health checks | 10 |
+| livenessProbe.failureThreshold | Number of failed polls before restarting service | 3 |
+| replicaCount | Number of Replicas if AutoScaling False | 1 |
+| autoscaling.enabled | Enable AutoScaling | false |
+| autoscaling.minReplicas | Minimum number of Replicas | 1 |
+| autoscaling.maxReplicas | Maximum number of Replicas | 100 |
+| autoscaling.targetCPUUtilizationPercentage | CPU Threshold for AutoScaling | 80 |
+| autoscaling.targetMemoryUtilizationPercentage | Memory Threshold for AutoScaling |  |
+| ingress.enabled | Enables Ingress | false |
+| ingress.annotations | Ingress annotations | {} |
+| ingress.path | Ingress path | / |
+| ingress.hosts | Ingress accepted hostnames | chart‐example.local |
+| ingress.tls | Ingress TLS configuration | [] |
+| resources | CPU/Memory resource requests/limits | {} |
+| nodeSelector | Node labels for pod assignment | {} |
+| tolerations | Toleration labels for pod assignment | [] |
+| affinity | Affinity settings for pod assignment | {} |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json b/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
new file mode 100644
index 0000000..5d1c849
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+  "title": "Workflows",
+  "ordinal": 112,
+  "parent_title": "Automation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html",
+  "topic_cluster": {
+    "clustering_title": "Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284",
+        "clustering_title": "Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md b/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
new file mode 100644
index 0000000..509a6ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.md
@@ -0,0 +1,17 @@
+# Workflows
+
+Workflows are groups of Tasks, which are described in detail in the preceding section. Operational Workflows can be run on-demand against an existing Instance or server from the Actions menu on the Instance or server detail page. Additionally, they can be scheduled to run on a recurring basis through Morpheus Jobs (Provisioning > Jobs).
+
+Provisioning Workflows are associated with Instances at provision time (in the Automation tab of the Add Instance wizard) or after provisioning through the Actions menu on the Instance detail page. Provisioning Workflows assign Tasks to various stages of the Instance lifecycle, such as Provision, Post Provision, and Teardown. When the Instance reaches a given stage, the appropriate Tasks are run. Task results and output can be viewed from the History tab of the Instance or server detail page.
+
+**Subtopics**  
+
+- **[Provisioning Workflow Execution Phases](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-47CD21B9-0818-4B47-9CFA-27C19F3E8B50.html)**
+- **[Add Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html)**
+- **[Allow Custom Config](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html)**
+- **[Retrying Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-34DE6BFF-C4CD-4C78-A963-62798D548E61.html)**
+- **[Cancelling Workflow Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-46EF85AB-AF8A-4C1A-988D-F8E5F81367DE.html)**
+- **[Price Phase Task Utilization](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html)**
+- **[Nesting Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1F488507-3D6B-4EC3-9D55-E542F2978E2D.html)**
+- **[Edit Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2CABEED6-A0AB-4473-B2C1-A50B30A5C3F9.html)**
+- **[Delete Workflow](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-272497A0-8AE1-4C3F-99D8-3F60B52DA17C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json b/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
new file mode 100644
index 0000000..9a652eb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+  "title": "Library Integrations",
+  "ordinal": 164,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.html",
+  "topic_cluster": {
+    "clustering_title": "Library Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2",
+        "clustering_title": "Library Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md b/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
new file mode 100644
index 0000000..e4d1bc8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49022137-A78E-4863-B1CF-D455EDD1A7D2.md
@@ -0,0 +1,3 @@
+# Library Integrations
+
+The integrations section within HPE Morpheus Enterprise Library lists existing integrations and allows for the creation of new integrations which are related to automation technologies. A complete list of integrated third party technologies is available in the Administration section (Administration > Integrations). More detailed information about each HPE Morpheus Enterprise integration with third party technologies is included in our [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) section.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json b/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
new file mode 100644
index 0000000..bd5f1f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+  "title": "Roles",
+  "ordinal": 276,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html",
+  "topic_cluster": {
+    "clustering_title": "Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA",
+        "clustering_title": "Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md b/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
new file mode 100644
index 0000000..4d42246
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.md
@@ -0,0 +1,28 @@
+# Roles
+
+There are two Role types in HPE Morpheus Enterprise, Tenant Roles and User Roles. Understanding these Role types is key to effectively administering Role permissions in HPE Morpheus Enterprise. These two Role types are discussed in greater detail in this section.
+
+## Tenant Roles
+
+Tenant Roles set the maximum permission levels for Users in the Tenant. User Role permissions will not exceed the permissions of the Tenant Role.
+
+- Tenant Roles set the maximum permissions for a Tenant
+- User Roles in a Tenant cannot exceed the permissions of the Tenant Role
+- A Tenant Role can be assigned to one or multiple Tenants
+- Tenant Roles determine Cloud access for the child Tenant such that all Clouds in the parent Tenant which have visibility set to Public will show as options in the Tenant Role Cloud Access tab
+- Only parent Tenant Clouds given access in the Tenant Role will be accessible in the Subtenant
+
+IMPORTANT
+
+Tenant Roles cap permissions on all Subtenant User Roles. User Roles can be created in the Subtenant with lesser permissions than the Tenant Role allows. Tenant Roles are designed for a parent Tenant Admin to set max permissions for the Subtenant, and a child Tenant Admin to configure User Roles inside the Tenant.
+
+## User Roles
+
+User Roles determine feature, Group, and Instance Type access for all Users. In a multi-Tenant environment, there are two types of User Roles: Single-Tenant User Roles and Multi-Tenant User Roles.
+
+- **Single-Tenant User Roles:** These exist solely in the Tenant they are created in
+- **Multi-Tenant User Roles:** Parent Tenants can create Multi-Tenant User Roles. These Roles are automatically seeded into child Tenants and can be assigned to Users within that Tenant. Changes to Multi-Tenant User Roles made in the parent Tenant are propagated to all children. However, once a Multi-Tenant User Role is edited inside the child Tenant, it is no longer linked to the Multi-Tenant User Role and becomes its own unique single-Tenant Role. It will no longer receive propagated changes.
+
+NOTE
+
+Multi-Tenant User Roles are intended to make Subtenant User Role creation easier, so parent Tenant administrators do not have to re-create the same base Subtenant Users Roles for every Subtenant. Multi-Tenant User Roles are not a single Role across Tenants, but more like a template that creates new Subtenant User Roles that can then be managed in the Sub Tenant.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json b/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
new file mode 100644
index 0000000..a12d487
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+  "title": "Software Licenses",
+  "ordinal": 329,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.html",
+  "topic_cluster": {
+    "clustering_title": "Software Licenses",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C",
+        "clustering_title": "Software Licenses"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md b/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
new file mode 100644
index 0000000..3bb018e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49494E3A-BB6A-4C0C-95A9-A1BA3989393C.md
@@ -0,0 +1,53 @@
+# Software Licenses
+
+## Overview
+
+The License section is for automating the application of Licenses to Instances while provisioning. Licenses can be added to HPE Morpheus Enterprise and then attached to images. HPE Morpheus Enterprise will then apply the license to Instances provisioned using the images with license attached. Licenses can be configured for single or multiple Tenants.
+
+### Creating Licenses
+
+#### Procedure
+
+1. Select + Create License
+2. In the New License modal, enter the following: 
+
+   - License Type
+     :   Windows
+   - Name
+     :   Name of the License in HPE Morpheus Enterprise
+   - License Key
+     :   Enter the License Key
+   - Org Name
+     :   The Organization Name (if applicable) related to the license key
+   - Full Name
+     :   The Full Name (if applicable) related to the license key
+   - Version
+     :   The License Version
+   - Copies
+     :   The Number of copies available on the License
+   - Description
+     :   License description displayed in the Licenses list in HPE Morpheus Enterprise, helpful for identifying the License after creation
+   - Virtual Images
+     :   Search for existing Virtual Images by name and select to attach the image to the license.
+         :   NOTE
+
+             Virtual Images are synced from Clouds or added in the Library > Virtual Images section.
+   - Tenant Permissions
+     :   Search for and select the Tenant(s) the License will be available for. Multiple Tenants can be added.
+3. Save Changes
+
+### Provisioning with Licenses
+
+When a Virtual Image is added to a license, HPE Morpheus Enterprise will automatically apply the License to Instances configured with the Virtual Image during provisioning, including Instance Types with a Node Type that is configured with the Virtual Image, or if the image is selected when using generic Cloud Instances types (VMware, AWS, Nutanix, Openstack etc). Virtual Images can be removed from a License by editing the License.
+
+### Managing Licenses
+
+Created Licenses details are displayed in the License page, including the number of copies applied per License, the Tenants added to the License, and the Virtual Images attached to the License.
+
+The Name, Version, Copies, Description, Virtual Images and Tenant Permissions are editable but selecting the Actions dropdown on a License.
+
+NOTE
+
+License Types, Keys, Org Names and Full Names are not editable after a license has been created.
+
+License can also be removed using the Actions dropdown on a License.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json b/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
new file mode 100644
index 0000000..75d1d6b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+  "title": "Add Amazon ALB load balancer",
+  "ordinal": 492,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ALB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4983900F-0A3F-4F61-BB06-8270BE27C886",
+        "clustering_title": "Add Amazon ALB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md b/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
new file mode 100644
index 0000000..9962c9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.md
@@ -0,0 +1,33 @@
+# Add Amazon ALB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ALB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-81281149-FB28-4485-B1B1-957E0FCE24AE-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json b/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
new file mode 100644
index 0000000..cbab32b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+  "title": "Load Balancers",
+  "ordinal": 225,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md b/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
new file mode 100644
index 0000000..32bbe05
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.md
@@ -0,0 +1,9 @@
+# Load Balancers
+
+Infrastructure  >  Load Balancers
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-14A50EED-E11C-47E2-9C35-28B1F09CF6A7.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-00E2C383-D602-4EAD-BE7F-64E69F5DD5C1.html)**
+- **[Orchestrating Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-151C50C5-5883-4137-A9B0-EAF5F8087117.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json b/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
new file mode 100644
index 0000000..12fbedc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+  "title": "Infrastructure",
+  "ordinal": 167,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html",
+  "topic_cluster": {
+    "clustering_title": "Infrastructure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4A13998A-C40E-4505-B1A1-16B21926D177",
+        "clustering_title": "Infrastructure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md b/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
new file mode 100644
index 0000000..b5d7ba1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4A13998A-C40E-4505-B1A1-16B21926D177.md
@@ -0,0 +1,15 @@
+# Infrastructure
+
+The heart of HPE Morpheus Enterprise is the ability to manage provisioning across any infrastructure, from bare metal to virtualized clouds and all the way to public infrastructure.
+
+**Subtopics**  
+
+- **[Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html)**
+- **[Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html)**
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html)**
+- **[Network](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-49F13E32-7912-4F28-8C78-5DF3AB06E690.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-034C870E-F6DE-4D0B-950B-23A627D33C65.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html)**
+- **[Boot](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json b/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
new file mode 100644
index 0000000..44b4c26
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+  "title": "Prerequisites",
+  "ordinal": 248,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md b/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
new file mode 100644
index 0000000..a78c45a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.md
@@ -0,0 +1,39 @@
+# Prerequisites
+
+In order to work with HPE Morpheus Enterprise bare metal PXE boot capabilities, some initial setup configuration is required. First, on the HPE Morpheus Enterprise server, if you have a firewall enabled, make sure port 69 is open for TFTP. HPE Morpheus Enterprise actually uses port 6969 and during installation a redirect should have been set. To check this, SSH onto the Morpheus server and run the following:
+
+```
+```
+iptables -t nat -L -n -v
+```
+```
+
+If the redirect is still properly, the response should include the following:
+
+```
+```
+Chain PREROUTING (policy ACCEPT 69 packets, 9767 bytes)  
+pkts bytes target   prot opt in out source     destination  
+0     0 REDIRECT udp  --  *  *   0.0.0.0/0  0.0.0.0/0        udp dpt:69 redir ports 6969  
+0     0 DNAT     tcp  --  *  *   0.0.0.0/0  169.254.169.254  tcp dpt:80 to:192.168.1.156
+```
+```
+
+Next, in HPE Morpheus Enterprise, set a default PXE root password. This password is set in Administration > Settings > Provisioning. With the default root password set, set up the redirect on the DHCP server. In addition to the DNS and Gateway settings, add Boot Server Host Name which will be the name of the HPE Morpheus Enterprise Server and Bootfile Name which should be set to `pxelinux.0`. If you are using a Linux-based DHCP server, for example on CentOS, the dhcpd.conf configuration will look something like the following:
+
+```
+```
+allow booting;  
+allow bootp;  
+option option-128 code 128 = string;  
+option option-129 code 129 = text;  
+next-server xx.xx.xx.xx;  
+filename "pxelinux.0";
+```
+```
+
+NOTE
+
+Replace the dummy IP address in the example dhcpd.conf file above with your HPE Morpheus Enterprise appliance IP address.
+
+Once you have done this, when you boot a PXE-enabled machine on the network, it will be told to access the HPE Morpheus Enterprise server and request the `pxelinux.0` file. It will do this on port 69, the default for TFTP and will be redirected to 6969 once it hits the HPE Morpheus Enterprise server. If successful you will see the “HPE Morpheus Enterprise PXE Server” menu when you boot a server. This is the default menu defined in HPE Morpheus Enterprise and supports the shipped PXE images supplied with the product. By selecting any of the choices from the “HPE Morpheus Enterprise PXE Server menu”, the install files should be downloaded and the server configured as per the supplied kickstart files. At this point, back on the HPE Morpheus Enterprise appliance, you should see the MAC address for the new server appear in the “Discovered MAC Addresses” tab of the Infrastructure > Boot page.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json b/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
new file mode 100644
index 0000000..eae9931
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+  "title": "Overview",
+  "ordinal": 268,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4CCF6004-31A7-4B35-996D-5E12877CB443",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md b/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
new file mode 100644
index 0000000..387ec01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.md
@@ -0,0 +1,3 @@
+# Overview
+
+The bulk migration tool is designed to migrate existing VMs running on integrated VMware vCenter Clouds to HVM Clusters. Thus, creating a migration requires existing vCenter Cloud integration(s) and at least one functional HVM Cluster. See the VMware vCenter integration guide and the HVM Clusters guide elsewhere in this documentation stack for more details on getting started with and using those integrations. Migrations may include multiple VMs and may include both Linux and Windows workloads.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json b/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
new file mode 100644
index 0000000..f53ab81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+  "title": "Create a Single Tenant User Role",
+  "ordinal": 303,
+  "parent_title": "User Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html",
+  "topic_cluster": {
+    "clustering_title": "Create a Single Tenant User Role",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47",
+        "clustering_title": "Create a Single Tenant User Role"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md b/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
new file mode 100644
index 0000000..0359ccd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.md
@@ -0,0 +1,15 @@
+# Create a Single Tenant User Role
+
+## Procedure
+
+1. In the Master Account, navigate to Administration > Roles
+2. Select + CREATE ROLE
+3. Enter a name for the Role and optional Description
+4. For TYPE, select “User Role”
+5. Leave the “Multi-tenant Role” checkbox blank.
+6. Optionally select an existing Role to copy in the COPY FROM ROLE dropdown. \* This will configure the new Role with the same configuration as the selected role to copy. A new role that is not copied from another role will be generated with all permissions set to NONE.
+7. Select SAVE CHANGES
+
+## Results
+
+After saving the Role will be created, and you will be redirected to the Roles Permissions settings.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json b/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
new file mode 100644
index 0000000..5acb43b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+  "title": "Network",
+  "ordinal": 216,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.html",
+  "topic_cluster": {
+    "clustering_title": "Network",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799",
+        "clustering_title": "Network"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md b/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
new file mode 100644
index 0000000..262fc8c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4D7A7C25-BB0F-4212-AEB4-8C7177DEC799.md
@@ -0,0 +1,13 @@
+# Network
+
+**Subtopics**  
+
+- **[Networks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html)**
+- **[Network Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html)**
+- **[Routers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html)**
+- **[IP Pools](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html)**
+- **[Floating IPs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html)**
+- **[Domains](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E_2.html)**
+- **[Security Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1A14AD6E-BC3E-4E87-A794-00BE2915D6C1.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json b/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
new file mode 100644
index 0000000..ca19071
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+  "title": "ITSM",
+  "ordinal": 488,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html",
+  "topic_cluster": {
+    "clustering_title": "ITSM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-4F4F8735-4673-4408-BDA3-C295F2A88174",
+        "clustering_title": "ITSM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md b/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
new file mode 100644
index 0000000..fff2647
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.md
@@ -0,0 +1,7 @@
+# ITSM
+
+**Subtopics**  
+
+- **[Service Now](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html)**
+- **[Cherwell](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html)**
+- **[Remedy](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json b/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
new file mode 100644
index 0000000..f7fa76b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+  "title": "Image Types",
+  "ordinal": 148,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html",
+  "topic_cluster": {
+    "clustering_title": "Image Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9",
+        "clustering_title": "Image Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md b/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
new file mode 100644
index 0000000..b8e2b6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.md
@@ -0,0 +1,7 @@
+# Image Types
+
+HPE Morpheus Enterprise provides a vast System Image repo with pre-configured images for every Cloud. All other images are User Images. User images can be added directly to HPE Morpheus Enterprise, or automatically synced from integrated clouds. It is important to configure synced User Images for metadata, including specifying the Platform and User Credentials, prior to provisioning. Provisioning a User Image that has not been configured may result in failed provisioning.
+
+IMPORTANT
+
+Synced User Images need to be configured prior to provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json b/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
new file mode 100644
index 0000000..bcab5d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+  "title": "Feature Access Permissions",
+  "ordinal": 300,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.html",
+  "topic_cluster": {
+    "clustering_title": "Feature Access Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA",
+        "clustering_title": "Feature Access Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md b/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
new file mode 100644
index 0000000..f6065b6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-50C87C86-5EA7-4910-A164-BEEA1E33A0AA.md
@@ -0,0 +1,257 @@
+# Feature Access Permissions
+
+Feature Access settings control permissions for sections and objects in HPE Morpheus Enterprise. Permission options include:
+
+None
+:   Hidden or inaccessible for user
+
+Read
+:   User can view but cannot edit or create
+
+Full
+:   User has full access
+
+User
+:   User can access Objects they have created or own
+
+Group
+:   User can access Objects assigned to or shared with Groups the User has access to
+
+Remote Console: Provisioned
+:   Remote Console tab will only appear after instance is successfully provisioned.
+
+Remote Console: Auto Login
+:   RDP and SSH only, controls if user is auto-logged in to Remote Console or presented with login prompt.
+
+Role Mappings
+:   Gives User Access to Role Mappings config in `/admin/roles` for configuring Identity Source Role Mappings without providing Access to other Identity Source configuration settings.
+
+## Admin Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Admin: Ansible | None, Full | Allows or disallows the ability to edit existing Ansible integrations | Ansible integrations are shown on the Integrations list page (Administration > Integrations). Users with access may view and edit them here. | This permission is recommended for those responsible for administering HPE Morpheus Enterprise, including creating integrations with third‐party technologies, specifically Ansible |  |
+| Admin: Appliance Settings | None, Full | Allows or disallows access to the Appliance and License tabs in Administration > Settings | The Appliance tab in Administration > Settings is where HPE Morpheus Enterprise administrators would configure the appliance URL, Tenant and User management, email, proxy, and currency settings. Additionally, defining which Clouds are available for integration within HPE Morpheus Enterprise is done on this page. On the License tab information about the current HPE Morpheus Enterprise license may be viewed and a new license may be applied when needed. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant. Those responsible for configuring currency, email, and proxy settings for Cloud API access will need this permission. | This permission is recommended to be set to None on the Tenant Role to restrict this access for all Subtenant Users. |
+| Admin: Backup Settings | None, Full | Allows or disallows access to Administration > Settings > Backups. Master Tenant administrators have additional settings for appliance backups and defaults on this page. | The Backup Settings page is where users define the default HPE Morpheus Enterprise backup bucket, backup schedule, and retention count. Additionally, if given to a Master Tenant user they will have the ability to enable scheduled backups, create backups, and backup appliance. | This permission is recommended for those responsible for enabling backups and setting default backup buckets within HPE Morpheus Enterprise. |  |
+| Admin: Clients | None, Full | Allows or disallows access to the Clients tab in global settings (Administration > Settings) | The Clients settings section is where API clients are created and edited. Default clients may have their validity and refresh periods edited but cannot be deleted. User‐created API clients may be edited or deleted | This permission is recommended for those responsible for administering API access. |  |
+| Admin: Distributed Workers | None, Full | Allows or disallows access to Administration > Integrations > Distributed Workers Tab |  |  |  |
+| Admin: Environment Settings | None, Full | Allows or disallows access to the Environments tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define the visibility of the environment to either private or public. When given to a Subtenant user the environments are only visible to the subtenant (private). | The Environments tab is where named environments such as development or production are created and given a description as well as a code for use within the API. A display order and visibility is also set. | This permission is recommended for those responsible for defining environments that will be available to select at provision time whether they are the Master Tenant or Subtenant users. |  |
+| Admin: Export/Import | None, Full | Allows access to the Export/Import functionality which is part of the Code Repositories section of HPE Morpheus Enterprise UI (Provisioning > Code) | Export/Import tools allow users to configure integrated Git repositories as either export or import targets (or both) and execute exports or imports | This permission is recommended for administrators as it allows wholesale export of HPE Morpheus Enterprise constructs (Tasks, Library Items, and more) as code into Git repositories as well as import of new items from repositories into the appliance |  |
+| Admin: Guidance Settings | None, Full | Allows or disallows access to the Guidance tab in Administration > Settings | The Guidance tab controls global thresholds for HPE Morpheus Enterprise guidance recommendations | This permission is recommended for those responsible for cost and resource management |  |
+| Admin: Health | None, Read | Determines access to the Administration > Health page, including the HPE Morpheus Enterprise Health and HPE Morpheus Enterprise Logs tabs. | The Health pages provide an overview of HPE Morpheus Enterprise health, notifications from integrations, and the current HPE Morpheus Enterprise‐ui log. | This permission is recommended for those responsible for administering and troubleshooting HPE Morpheus Enterprise. | This permission is recommended to be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Identity Source | None, Role Mappings, Full | Allows or disallows access to create, edit, or delete integrated Identity Sources associated with subtenants. The “Role Mappings” option allows the user to edit role mappings without seeing higher level details about the integration itself (such as server IP addresses and admin usernames). | The Identity Sources page associated with the selected Tenant allows for creating, editing, and removing of identity sources in addition to configuring role mapping between HPE Morpheus Enterprise and the identity provider. | Full permission is recommended for those responsible for integrating HPE Morpheus Enterprise with Identity Providers. Role Mapping permission is recommended for those responsible for Role Based Access Control (RBAC). | This permission is recommended to be set to None for any subtenant user roles via use of a Tenant Role unless they manage their own RBAC. |
+| Admin: Integrations | None, Read, Full | This allows or disallows full or read access to Administration > Integrations. | The Administration Integrations tab is where many new or existing integration types can be configured. These include Chef, Puppet, Ansible, Ansible Tower, vRealize Orchestrator, Microsoft DNS, PowerDNS, Route 53, Git, GitHub, Docker, Jenkins, ServiceNow, Cherwell, Remedy, and ACI. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated technologies. |  |
+| Admin: License Settings | None, Full | Allows or disallows access to the Licenses tab in Administration > Settings > Provisioning. When given to a Master Tenant user they may define specific subtenants in which the licenses may be used. | The Licenses tab is where software licenses may be added for tracking in HPE Morpheus Enterprise. HPE Morpheus Enterprise may then be configured to apply these licenses on provision. Currently, only Windows license types are available. | This permission is recommended for those responsible for managing Windows licenses. |  |
+| Admin: Log Settings | None, Full | Allows or disallows access to the Administration > Settings > Logs. | The Logs page is where logs are enabled. Syslog forwarding rules are also configured here. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise log settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access to Subtenant Users. |
+| Admin: Message of the day | None, Full | Allows or disallows access to create and edit Message of the Day policies in Administration > Policies | The Policies page is where policies are defined. When creating a policy, users can select “Message of the Day” from the TYPE dropdown with this permission set to Full. | This permission is recommended for those responsible for publishing the Message of the Day. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Monitoring Settings | None, Full | Allows or disallows access to Administration > Settings > Monitoring | The monitoring settings page is where HPE Morpheus Enterprise monitoring and monitoring integrations are configured. Monitoring checks can be turned on or off, and availability time frame, check interval period, and reported availability precision are also configured on this page. | This permission is recommended for those responsible for configuring HPE Morpheus Enterprise monitoring settings and integrations. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Packages | None, Full | Allows or disallows access to the Packages tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom library packages (mpg) are added. | This permission is recommended for those responsible for managing the Library. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Plugins | None, Full | Allows or disallows access to the Plugins tab on the Integrations page (Administration > Integrations) | The Plugins tab is where custom plugins are added to extend HPE Morpheus Enterprise functionality. | This permission is recommended for those responsible for extending HPE Morpheus Enterprise functionality through custom plugins. | This permission is recommended to be set to None in the Tenant Role to restrict this access from Subtenant Users. |
+| Admin: Policies | None, Read, Full | This setting determines the level of access to Administration > Policies. When given to a Master Tenant user the ability to define Global policies and associate them with one or many Subtenants is granted. When given to a Subtenant user, a global policy applies only to their subtenant. | The Policies page is where policies are defined. On create, the type of policy is selected, a name, description, and scope are defined. | This permission is recommended for those responsible for configuring and managing policies either at the Master Tenant or Subtenant. |  |
+| Admin: Profiles | none,read,full | Allows or disallows access to Profiles (Clouds) | Profiles are where Terraform, Key/Value profiles are created and managed. | This permission is recommended for those responsible for managing secrets and other metadata that needs to be accessed by provisioning and automation processes. |  |
+| Admin: Provisioning Settings | None, Full | Allows or disallows access to the Settings tab of the Administration > Settings > Provisioning page. | The Settings tab is where global provisioning settings are configured. For Master Tenant users, these include allowing Cloud selection, allowing host selection, requiring environment selection, showing pricing, hiding datastore stats on selection, cross‐Tenant naming policies, and reusing naming sequence numbers. For both Master Tenant and Subtenant users, defining the deploy archive store, cloud‐init setting, the PXE boot root password, and default App Blueprint types are available. | This permission is recommended to only be assigned to roles utilized within the Master Tenant. |  |
+| Admin: Roles | None, Read, Full | This setting determines access to the Administration > Roles page. When given to a Subtenant user, the ability to create user roles is granted. When given to a Master Tenant user, the ability to create and manage Tenant and Multi‐Tenant Users roles is also granted. | The Roles page is where roles are defined. On create, a name and description are defined. Once created, the Role is accessed and feature access, Group access, Instance Type access and Blueprint access may be configured. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC) either globally or within their Subtenant. |  |
+| Admin: Service Plans | None, Read, Full | This setting determines access to Administration > Plans & Pricing. When given to a Subtenant user, access to the Plans tab is granted. When given to a user in the Master Tenant, the Price Sets and Prices tabs are also available. | The Plans tab is where service plans are defined. On create, a name and code (for API) are defined, display order, provisioning type, storage, memory, core count and the price may be configured. Additionally, the actions menu will allow group access to be scoped. | This permission is recommended for those responsible for defining and managing pricing and applying plans. |  |
+| Admin: Tenant | None, Read, Full | This setting determines access to the Administration > Tenants page. With this permission, local users may be created or deleted within each Tenant. Critical Note: Granting this permission to Subtenant users will expose all Tenants and Tenant users to the Subtenant. | The Tenant page is where all Tenants may be viewed, edited, created, or even deleted. | This permission is recommended to only be assigned to Roles utilized within the Master Tenant who are responsible for the creation, configuration, and/or deletion of Subtenants. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Tenant ‐ Impersonate Users | None, Full | This setting allows or disallows access to impersonate users. This selection is located on the Administration > Users page in the Actions menu. When set to Full, Impersonate selection is available. | This permission allows for users in the Master Tenant to impersonate users of the Master Tenant and Subtenants. | This permission is recommended to be assigned only to Roles utilized within the Master Tenant who are responsible for configuring RBAC or for supporting users. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| Admin: Users | None, Read, Full | This setting determines access to the Administration > Users page (both Users and User Groups tabs). User Roles can also be set or edited when creating or editing a User on this page. Note: A Master Tenant user with the Admin: Tenants (Full) permission may also access and perform user management from the associated Tenant page. | The User tab is where all users may be viewed, edited, created, or even deleted. The User Groups tab is where User Groups may be viewed, edited, created, or even deleted. Within HPE Morpheus Enterprise, a User Group may be selected during provisioning in order to add each group member’s credentials to an Instance. When creating a User Group a name, description, server group (in Linux, name of the group to assign members), sudo access toggle, and a list of users are defined. | This permission is recommended for those responsible for managing users and RBAC. |  |
+| Admin: Whitelabel Settings | None, Full | Allows or disallows access to the Whitelabel tab in Administration > Settings. | The Whitelabel tab is where custom Tenant logos, colors, and security banners may be configured. | This permission is recommended for those responsible for branding tenants, whether they are Master Tenant users or individual Subtenant users. |  |
+
+## API Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| API: Billing | None, Read, Full | Allows or disallows access to invoices and projects via HPE Morpheus Enterprise API/CLI. | The invoices API/CLI is used to generate bills and gather highly‐granular costing data for supported Clouds. Read access allows list and get functions and Full allows access to post (refresh). | This permission is recommended for those responsible for generating invoices or projects. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+| API: Execution Request | None, Full | Allows or disallows access to an API endpoint. | This endpoint allows users to execute scripts on Instances, containers, or hosts and then polls for a response. | This permission is recommended for those responsible for arbitrary API script execution. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Backups Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Backups | None, View, Read, User, Full | Determines access to the Backups secton of HPE Morpheus Enterprise UI, including the Summary, Jobs, Backups, and History subpages. The “User” permission allows access only to backup objects the user owns. | The Summary subpage allows the user to see the number of configured backups, the success rate, recent failures, and the size of the backups, as well as, the upcoming and in‐progress backups. The Jobs subpage is where backup jobs may be created, cloned, edited or deleted. On create, a name, code (for use within the API), retention count, and schedule are selected (Note: Selectable schedules are defined Execution Schedules which are created in the Library > Automation). On the backups subpage, a list of configured backups is provided and new backups may be created or on‐demand backups may be executed. On create, the place where the target exists is selected (Instance, Host, or Provider), the source is selected and a name is defined as well as the selected execution schedule. On the History subpage both the backups and restores tabs are available. Names, statuses, start times, durations and size may be viewed. | This permission is recommended for those responsible for performing the backup and restoration of workloads. |  |
+| Backups: Integrations | None, Read, Full | Determines access to the Backups > Integrations page. | From this page, backup integrations may be created, edited, or deleted. The page also provides the status of existing integrations. On create the integration product is selected and all associated connection and authentication information must be provided. Additionally, visibility is set to either public or private. Integrations available include Avamar, Commvault, Rubrik, Veeam, and Zerto. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and backup technologies. | It is recommended this setting be set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Catalog Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Catalog (Formerly Service Catalog: Catalog) | None, Full | Determines access to Provisioning > Catalog and Catalog in the Service Catalog Persona view | The Catalog page displays the complete list of Catalog Items that can be ordered from the Service Catalog | This permission is recommended for users who will order items from the Service Catalog |  |
+| Catalog: Dashboard (Formerly Service Catalog: Dashboard) | None, Read | Determines access to and Dashboard in Service Catalog Persona view | The Catalog Dashboard contains featured Catalog Items, recently‐ordered Catalog items and Inventory items. The Catalog Dashboard is the default landing page for the Service Catalog Persona view | This permission is recommended for users who will use the Service Catalog |  |
+| Catalog: Inventory (Formerly Service Catalog: Inventory) | None, Full | Determines access to and Dashboard in Service Catalog Persona view | The Inventory is the complete list of user‐owned items provisioned from the Service Catalog | This permission is recommended for users who will use the Service Catalog and need to be able to view details on the items they’ve provisioned from the Catalog |  |
+
+## Infrastructure Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Infrastructure: Boot | None, Read, Full | Determines access to the Integrations > Bootpage, including the Mapping, Boot Menus, Answer Files, Images, and Discovered MAC Addresses tabs. | HPE Morpheus Enterprise includes a PXE Server to provide for rapid bare metal provisioning. The Boot page is where users may add, edit, or delete answer files, as well as, manage their own images or use existing ones. Boot menus and mappings are also managed here and discovered MAC addresses are displayed. | This permission is recommend for those responsible for bare metal provisioning. |  |
+| Infrastructure: Certificates | None, Read, Full | Determines access to the SSL Certificates tab on the Infrastructure > Keys& Certs page. | The SSL Certificates page is where certificates may be uploaded and managed. These certificates may then be used within HPE Morpheus Enterprise when orchestrating load balancers. | This permission is recommended for personnel who will be orchestrating and provisioning load balancers. |  |
+| Infrastructure: Clouds | None, Read, Group, Full | Determines access to the Infrastructure > Clouds page. The “Group” permission limits the Cloud list page (Infrastructure > Clouds) to show only Clouds in their assigned Groups. | The Cloud page is where new Clouds are integrated with HPE Morpheus Enterprise and existing Cloud integrations are managed. This includes creating a code for use within the API, the location, visibility, tenant, whether or not it should be enabled, and if VMs should be automatically powered on. Additionally, Clouds may be integrated from the Clouds tab of a Group detail page. | This permission is recommended for those responsible for configuring RBAC as well as those responsible for HPE Morpheus Enterprise Cloud Integrations. |  |
+| Infrastructure: Clusters | None, Read, Group, Full | Determines access to the Infrastructure > Clusters page. | The Clusters page allows you to create and manage Kubernetes, Docker, and KVM Clusters, as well as Cloud‐specific Kubernetes services such as EKS. | This permission is recommend for those creating and managing containers or container services. |  |
+| Infrastructure: Compute | None, Read, Full | Determines access to the Infrastructure > Hostspage, including the Hosts, Virtual Machines, and Bare Metal tabs. | The Hosts page provides for viewing and managing hosts, virtual machines, and bare metal hosts. On the bare metal hosts page, hosts may come from PXE boot or may be manually added. On the Hosts page hypervisors and Docker hosts are displayed. The Virtual Machines page lists all VMs. On all three pages actions may be performed against machines. Additionally, views may be refined by altering the columns displayed and CSV/JSON exporting of lists is available. | This permission is recommend for those whom need to take action on machines and those responsible for bare metal provisioning. |  |
+| Infrastructure: Credentials | None, Read, Full | Determines access to the Credentials tab in Infrastructure > Trust | The credentials tab allows you to create and manage credential sets stored internally and in external Cypher server integrations | This permission is recommended for those responsible for maintaining credentials |  |
+| Infrastructure: Groups | None, Read, Full | Determines access to the Infrastructure > Groups page. | The Groups page is where HPE Morpheus Enterprise Groups are created and given a code for use within the API. Additionally, the DNS service, CMDB, service registry, and config management may be selected. Existing Clouds/Hosts or new Clouds/Hosts are added to the Group and virtual or bare metal machines may be viewed. | This permission is recommended for those responsible for configuring Role Based Access Control (RBAC). |  |
+| Infrastructure: Keypairs | None, Read, Full | Determines access to the Key Pairs tab on the Infrastructure > Keys& Certs page. | The Keypairs page allows for ease in accessing instances via SSH. On create a name, public key, private key, and passphrase are entered. | This permission is recommended for those whom utilize HPE Morpheus Enterprise deployment and management of Linux Instances. |  |
+| Infrastructure: Kubernetes Control | None, Full | Determines access to the Control tab on Kubernetes Cluster detail pages (Infrastructure > Clusters > Selected Kubernetes Cluster > ControlTab) | Run `kubectl` commands, apply templates, and run workloads on the Kubernetes Cluster | This permission is recommended for Kubernetes Cluster administrators |  |
+| Infrastructure: Load Balancers | None, Read, Full | Determines access to the Infrastructure > Load Balancers page, including both the Load Balancers and Virtual Servers tabs. The "Group" permission level allows Users to see only the Load Balancers tied to Groups they can access. | The Load Balancers page is where new load balancer integrations may be configured. Additionally, existing integrations may be managed. The Virtual Servers page is where virtual servers are managed to include policies, pools, profiles, monitors, nodes, and rule scripts may be managed. | This permission is recommended for those responsible for integrating HPE Morpheus Enterprise with load balancers as well as those responsible for managing virtual servers. |  |
+| Infrastructure: Move Servers | None, Full | Determines access to the “Change Cloud” action on server detail pages (Infrastructure > Compute > Virtual Machines tab > SelectedVM > Actions > Change Cloud) | Change Cloud allows server records to be migrated from one Cloud to another. Note that this is not a migration tool but simply allows for upkeep of records in HPE Morpheus Enterprise. | This permission is recommended for appliance administrators. See other sections of HPE Morpheus Enterprise documentation for more information on the use of this feature. |  |
+| Infrastructure: Networks | None, Read, Group, Full | Determines access to the Infrastructure > Networks page, including the Networks, network groups, and integrations tabs. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Networks page is where networks are configured for DHCP or static IP assignment and existing networks are displayed. The Network Groups page is where networks are grouped to allow round robin provisioning among the group. The Integrations page is where IPAM, DNS, security, service registry, and virtual network tools are integrated. These include Cisco ACI, VMware NSX T and V, Infoblox, Bluecat, phpIPAM, SolarWinds, Stealth, EfficientIP SolidServer, Microsoft DNS, PowerDNS, Route 53, and more. | This permission is recommended for those responsible for integration with network technologies and the configuration and management of networks to be used during provisioning. |  |
+| Infrastructure: Policies | None, Read, Full | Determines access to the Policies tabs on the Group and Cloud detail pages (Infrastructure > Groups > selected Group OR Infrastructure > Cloud > selected Cloud). | Policies can be created from this tab which are scoped to the Cloud or Group being viewed. | This permission is recommended for users who will need to set quotas which pertain specifically to Groups or Clouds the user has access to. |  |
+| Infrastructure: Security Groups | None, Read, Full | Determines access to the Security Groups tab on the Infrastructure > Networks page. | The Security Groups page is where Security Groups (aka virtual firewalls) are defined. | This permission is recommended for those responsible for firewall configuration and management. |  |
+| Infrastructure: Server Software | None, Read, Full | Determines access to the Software tab on server detail pages. The ‘Full’ permission level surfaces a SYNC button on the Software tab, users with ‘Read’ permission do not see the SYNC button. | The Software Tab of a server detail page is where the list of installed software packages for the server are shown. |  |  |
+| Infrastructure: State | None, Read, Full | Determines access to the power state toggle on the Infrastructure > Hostspage. | This toggle moves Hosts between a started and stopped state. | This permission is recommended for those responsible for managing Hosts. |  |
+| Infrastructure: Storage | None, Read, Full | Determines access to the Infrastructure > Storage page, including the Buckets, File Shares, Volumes, Data Stores, and Servers tabs. | The Servers page is where storage integrations are configured. Integrations available include 3Par, AWS S3, Dell EMC ECS and Isilon, Huawei or Open Telekom OBS and Huawei, Open Telekom, OpenStack SFS. The Volumes page is where storage volumes may be created or viewed. The File Shares page is where File Shares of types CIFS, Dell EMC ECS or Isilon, local storage, and NFSv3 may be configured. The Buckets page is where storage buckets of type AWS S3, Alibaba, Azure, Open Telekom OBS, OpenStack Swift, Racspace CDN may be created. Storage buckets are used for Backup, Archives, and Virtual Images. The Data Store page is where permissions to data stores may be managed and new data stores are added. | This permission is recommended for those responsible for storage integrations and configurations. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+| Infrastructure: Storage Browser | None, Read, Full | Determines file browsing access to buckets and file shares on the Buckets and File Shares tabs of the Infrastructure > Storage page. | The Storage Browser permission allows users who also have appropriate Infrastructure: Storage permission to browse, add files and folders, download, and delete from the buckets and file shares. | This permission is recommended for those who need to browse storage. |  |
+| Infrastructure: Trust Integrations | None, Read, Full | Determines access to the Integrations tab of the Infrastructure > Keys& Certs page. | The Integrations tab is where new trust integrations can be configured. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and trust providers. | This permission is recommended to be set to None on the Tenant Role to restrict access to Subtentant users. |
+
+## Library Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Library: App Blueprints (Formerly Provisioning: Blueprints) | None, Read, Full | Determines access to the Library > Blueprints > App Blueprints page. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of HPE Morpheus Enterprise is available. | This permission is recommended for those responsible for defining HPE Morpheus Enterprise‐type Blueprints. |  |
+| Library: Blueprints ‐ ARM (Formerly Provisioning: Blueprints ‐ ARM) | None, Provision, Full | Determines access to ARM‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from ARM Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of ARM is available. | This permission is recommended for those responsible for defining ARM blueprints. |  |
+| Library: Blueprints ‐ CloudFormation (Formerly Provisioning: Blueprints ‐ CloudFormation) | None, Provision, Full | Determines access to CloudFormation‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from CloudFormation Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of CloudFormation is available. | This permission is recommended for those responsible for defining CloudFormation blueprints. |  |
+| Library: Blueprints ‐ Helm (Formerly Provisioning: Blueprints ‐ Helm) | None, Provision, Full | Determines access to Helm‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Helm Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Helm is available. | This permission is recommended for those responsible for defining Helm blueprints. |  |
+| Library: Blueprints ‐ Kubernetes (Formerly Provisioning: Blueprints ‐ Kubernetes) | None, Provision, Full | Determines access to Kubernetes‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Kubernetes Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Kubernetes is available. | This permission is recommended for those responsible for defining Kubernetes blueprints. |  |
+| Library: Blueprint ‐ Terraform (Formerly Provisioning: Blueprints ‐ Terraform) | None, Provision, Full | Determines access to Terraform‐type Blueprints on the Library > Blueprints > App Blueprints page. The “Provision” permission allows for provisioning Apps from Terraform Blueprints without the ability to create or edit them. | The Blueprints page allows for the creation of pre‐configured, multi‐tier application definitions which can be deployed via the Apps page. With this permission the blueprint type of Terraform is available. | This permission is recommended for those responsible for defining Terraform blueprints. |  |
+| Library: Catalog Items (Formerly Tools: Self Service) | None, Read, Full | Determines access to Library > Blueprints > Catalog Items | Library > Blueprints > Catalog Items allows administrators to configure Catalog Items for the Library Catalog and Self Service Persona users | This permission is recommended for those responsible for creating and managing Library Catalog Items. |  |
+| Library: Instance Types (Formerly Provisioning: Library) | None, Read, Full | Determines access to the Library > Blueprints > Instance Types | Library > Blueprints > Instance Types is where Instance Types are created and maintained. | This permission is recommended for those responsible for managing the Instance Types. |  |
+| Library: Integrations (Formerly Provisioning: Automation Integrations) | None, Read, Full | Determines access to Library > Integrations. | Library > Integrationsis where Library Automation created and maintained.. These include Chef, Puppet, Ansible, Ansible Tower and vRealize Orchestrator. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and integrated automation technologies. |  |
+| Library: Packages | None, Read, Full | Determines access to Library > Templates > Cluster Packages. | Library > Templates > Cluster Packages is where Cluster Packages are created or edited. Cluster Packages are associated with Cluster Layouts | This permission is recommended for those responsible for Cluster Layout templating |  |
+| Library: Options | None, Read, Full | Determines access to Library > Options ‐ Inputs (Option Types) and Option Lists. |  | This permission is recommended for those responsible for creating and managing Library Inputs (Option Types) and Option Lists. |  |
+| Library: Scheduling ‐ Execute (Formerly Provisioning: Scheduling ‐ Execute) | None, Read, Full | Determines access to Library > Automation > Execute Scheduling. | The Execute Scheduling is where time schedules for Jobs, including Task, Workflow, and Backup Jobs are created and managed. | This permission is recommended for those responsible to create and manage schedules to be selected when scheduling jobs. |  |
+| Library: Scheduling ‐ Power (Formerly Provisioning: Scheduling ‐ Power) | None, Read, Full | Determines access to Library > Automation > Power Scheduling. | Power Scheduling is where startup and shutdown times are created, these schedules can be applied via policy or manaully. | This permission is recommended for those responsible to create and manage power schedules. |  |
+| Library: Tasks (Formerly Provisioning: Tasks) | None, Read, Full | Determines access to Library > Automation > Tasks and Library > Automation > Workflows. | Library > Automation > Tasks is where Tasks are created and managed. Library > Automation > Workflows is where Workflows are created and managed. Workflows are used to execute one or many tasks during specified phases. | This permission is recommended for those responsible for creating provisioning and operational scripts. |  |
+| Library: Tasks ‐ Script Engines (Formerly Provisioning: Tasks ‐ Script Engines) | None, Full | Determines access to **Execute Target** of **Local** for Tasks. | This permission limits Tasks from being able to run on the Morpheus appliance(s). Additionally, Task Types that only contain the **Execute Target** of **Local** will be removed, such as: Groovy, Javascript, and Python Task Types. | This permission is recommended for those responsible for Tasks that may need to execute on the appliance(s). |  |
+| Library: Templates | None, Read, Full | Determines access to Library > Templates | Library > Templates is where Spec Templates, File Templates, Script Templates and Security Packages are created and managed. | This permission is recommended for those responsible for creating and managing Spec Templates, File Templates, Script Templates and Security Packages. |  |
+| Library: Thresholds (Formerly Provisioning: Thresholds) | None, Read, Full | Determines access to Library > Automation > Scale Thresholds. | Scale Thresholds is where preconfigured settings for auto‐scaling Instances are configured. When adding auto‐scaling to an Instance, existing Scale Thresholds can be selected to define auto‐scaling rules. | This permission is recommended for those responsible for defining auto‐scaling for Instances. | This permission is recommended to be set to None or Read on the Tenant Role to restrict access for Subtenant users. |
+| Library: Virtual Images (Formerly Provisioning: Virtual Images) | None, Read, Full | Determines access to the Library > Virtual Images page. | Library > Virtual Images is where user and system Virtual Images are managed. | This permission is recommended for those who are responsible for image management. |  |
+
+## Lifecycle Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Environment Variables | None, User, Read, Full | Allows access to the Environments tab of the Instance detail page | Allows Instance environment variables to be edited. If set to “User” level only environment variables of Instances owned by the currently logged in user may be edited. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Extend Expirations | None, User, Full | Determines if the user can extend an expiration or shutdown Policy | Allows the user to extend automated shutdown or expiration policies set against any workload (“full” permission) or against the user’s own workloads (“user” permission) | This permission is recommended for administrators or those who need to be able to extend Policies set against their own workloads (“user” level permission) |  |
+| Power Control | None, User, Full | Allows access to power state controls for Instances and servers, including stopping, starting, restarting and suspending. | Allows the user to change the current power state of Instances and servers | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure | None, User, Full | Allows general access to Instance and server reconfigure (resize) feature. See additional reconfigure permissions below for more granular control over specific reconfigure functionality. | Allows general access to reconfigure features for Instances and servers. “User” level permission allows only Instances and servers owned by the currently logged in user to be reconfigured. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Change Plan | None, User, Full | Allows the user to change the Instance service plan | When reconfiguring, the user may change the service plan associated with the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their plans changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Add | None, User, Full | Allows the user to add disks to an Instance or server during reconfigure. | When reconfiguring, the user may add disks to the selected Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Change Type | None, User, Full | Allows the user to change the datastore or volume type during reconfigure. | When reconfiguring, the user may update datastore or volume types. “User” level permission allows only Instances owned by the currently logged in user to have their disk types changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Modify | None, User, Full | Allows the user to modify an attached disk during reconfigure. | When reconfiguring, the user may modify disks attached to the Instance. “User” level permission allows only Instances owned by the currently logged in user to have their disks changed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Disk Remove | None, User, Full | Allows the user to remove disks or volumes during reconfigure. | When reconfiguring, the user may remove disks attached to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have their disks removed. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Add | None, User, Full | Allows the user to add a network adapter during reconfigure. | When reconfiguring, the user may add a network interface to the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces added. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Modify | None, User, Full | Allows the user to edit network adapters during reconfigure. | When reconfiguring, the user may edit network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces modified. | This permission is recommended for those needing management control over Instances |  |
+| Reconfigure: Network Remove | None, User, Full | Allows the user to remove network adapters during reconfigure. | When reconfiguring, the user may remove network interfaces on the Instance or server. “User” level permission allows only Instances owned by the currently logged in user to have network interfaces removed. | This permission is recommended for those needing management control over Instances |  |
+| Lifecycle: Retry/Cancel | None, Full | Determines access to retry and cancel buttons for Tasks (for example, in the History tab of an Instance detail page) | Retry and cancel functionality allows failed automation Tasks to be retried or stuck Tasks to be stopped from various places within HPE Morpheus Enterprise UI (such as in the History tab of an Instance detail page) |  |  |
+
+## Monitoring Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Monitoring | None, Read, User, Full | Determines level of access to the Monitoring section of HPE Morpheus Enterprise UI, including the Status, Apps, Checks, Groups, Incidents, Contacts, and Alert Rules subpages. The “User” permission will allow access only to objects the user owns. | The Checks page is where automatically‐created checks are customized or new checks are created. The Groups and Apps pages are where checks may be grouped. The Incidents page is where incidents are created upon Check failure. The Contacts page is where contacts may be added for notifications. The Alert Rules page is where notification are configured. | This permission is recommended for those responsible for monitoring applications, incidents, or configuring notifications. |  |
+| Monitoring: Logs (Formerly Logs) | None, Read, User, Full | Determines level of access to the Logs section of HPE Morpheus Enterprise UI. The “User” permission will allow access only to objects the user owns. | Monitoring > Logs is where Instance and Server logs may be viewed (also must be enabled in order to view Appliance logs from Administration > Health > Morpheus Logs Logs when health permission is also enabled). | This permission is recommended for those who should have access to Instance and Server logs. | Setting permission to Full on the Tenant Role will give Subtenant users full access to all logs appliance‐wide, including to workloads living in other Tenants, for any Subtenant users who also have Full permission on their User Role. It’s recommended that you set this permission to User on the Tenant Role so that Subtenant users are not able to see logs for workloads other than their own. |
+
+## Networks Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Networks: DHCP Relays | None, Read, Full | Determines access to the DHCP Relays in applicable network integrations | Allows DHCP Relays to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: DHCP Servers | None, Read, Full | Determines access to the DHCP Servers in applicable network integrations | Allows DHCP Servers to be viewed, created and managed | This permission is recommended for those tasked with network management |  |
+| Networks: Domains | None, Read, Group, Full | Determines access to the Domains tab on the Infrastructure > Network page. Domains may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into Domains scoped to Groups they can access. | The Domains page is where network domains are managed. Domains are used for setting FQDNs, joining Windows Instances to domains, and creating A‐Records with DNS integrations. On create the domain controller and credentials for domain join must be provided. | This permission is recommended for those responsible for HPE Morpheus Enterprise DNS and domain‐join integrations. |  |
+| Networks: Firewalls | None, Read, Manage Rules, Full | Determines access to the Firewall tab on applicable network integrations detail pages. When the “Manage Rules” permission is given, users have read‐only access to firewall groups and the ability to create and manage firewall rules on those groups | The Firewall tab is where network firewall groups and rules are viewed, created and managed | This permission is recommended for those tasked with network security management |  |
+| Networks: Floating IPs | None, Read, Full | Determines access to the Floating IPs tab on the Network list page (Infrastructure > Network) | The Floating IPs tab is where Floating IPs from supported Clouds are listed once synced into HPE Morpheus Enterprise Users may also release unattached Floating IPs from this page and link through to any workloads which have Floating IPs attached | This permission is recommended for those tasked with network management |  |
+| Networks: IP Pools | None, Read, Group, Full | Determines access to the IP Pools tab on the Network list page (Infrastructure > Network). IP Pools may be scoped for specific Group access. If the Group‐level permission is selected here, users will only have visibility into IP Pools scoped to Groups they can access. | The IP Pools tab is where IP pools from various networks are displayed. Detail pages for IP pools can also be accessed here | This permission is recommended for those tasked with IP address management |  |
+| Networks: Integration | None, Read, Full | Determines access to the Integrations tab on the Network list page (Infrastructure > Network) | The integrations tab is where network integrations can be viewed, added and managed. Additionally, the detail pages for network integrations are accessed here | This permission is recommended for those tasked with handling network integrations and their use within HPE Morpheus Enterprise |  |
+| Networks: Proxies | None, Read, Full | Determines access to the Proxies tab on the Infrastructure > Networks page. | The Infrastructure Networks Proxies page is where Proxy configurations are stored, which are available for use by the provisioning engines. | This permission is recommended for those responsible for configuring proxies to be used when provisioning. |  |
+| Networks: Router Firewalls | None, Read, Full | Determines access to Firewall tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Firewall tab is where firewall rules are viewed, created, and managed | This permission is recommended for those responsible for managing firewall rules |  |
+| Networks: Router Interfaces | None, Read, Full | Determines access to Interfaces tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Interface tab is where router interfaces can be viewed, created and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router NAT | None, Read, Full | Determines access to the NAT tab on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The NAT tab is where NAT rules are viewed, created, and managed | This permission is recommended for those responsible for network traffic flow |  |
+| Networks: Router Redistribution | None, Read, Full | Determines access to Route Redistribution tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Route Redistribution tab is where redistribution rules are viewed, created, and managed | This permission is recommended for those responsible for redistribution rules |  |
+| Networks: Router Routes | None, Read, Full | Determines access to Routing tabs on Router Detail pages (Infrastructure > Network > Routers tab > SelectedRouter) | The Routing tab is where routes are viewed, created, and managed | This permission is recommended for those responsible for network route management |  |
+| Networks: Routers | None, Read, Group, Full | Determines access to the Routers tab on the Infrastructure > Networks page. The “Group” permission setting allows access to objects shared to Groups associated with the user. | The Routers page is where virtual routers are created and managed from Cloud and Network integrations. | This permission is recommended for those responsible for network management. |  |
+| Networks: Server Groups | None, Read, Full | Determines access to |  |  |  |
+| Networks: Static Routes | None, Read, Full | Determines access to the routing tab on a router detail page (/infrastructure/networks/routes) | The routers tab is where routes are created and managed | This permission is recommended for those responsible for network management |  |
+
+## Operations Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Operations: Activity | None, Read | Determines access to the Activity and History tabs on the Operations > Activity page. | The Activity page displays four types of recent activities: Provisioning, Alerts, Backups, and Permissions. | This permission is recommended for those responsible to monitor or view activities and their statuses within HPE Morpheus Enterprise. |  |
+| Operations: Alarms | None, Read, Full | Determines access to the Alarms tab in the Activity section (Operations > Health) | The Alarms tab is where alarms are listed and acknowledgement actions can be taken against them | This permission is recommended for those responsible for monitoring |  |
+| Operations: Analytics | None, Read, Full | Determines access to the Operations > Analytics page. | The Analytics page gives administrators the ability to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. | This permission is recommended for those responsible for understanding utilization and costs. |  |
+| Operations: Approvals | None, Read, Full | Determines access to the Operations > Approvals page. | When a Provision Approval‐type Policy is enabled for a Group or Cloud, an approval request will be created on each relevant provision attempt. These approvals can be handled directly in HPE Morpheus Enterprise or dealt with in ServiceNow with a properly‐configured integration. | This permission is recommended for those responsible for approving, denying, or canceling approval requests. |  |
+| Operations: Budgets | None, Read, Full | Determines access to the Operations > Budgetspage. | The Budgets page is where budgets are created and applied to clouds, tenants, users, or groups. | This permission is recommended for those responsible for managing budgets. |  |
+| Operations: Dashboard | None, Read | Determines access to the Operations > Dashboard page (default HPE Morpheus Enterprise landing page). | The Dashboard page is a single pane of glass showing quick, easy‐to‐read performance and configuration information about the HPE Morpheus Enterprise environment. | “Read” permission is recommended for all users. When set to None, Operations > Reports becomes the default landing page and attempts to go to the Dashboard will redirect users to their User Settings page. |  |
+| Operations: Guidance | None, Read, Full | Determines access to the Operations > Guidance page. | The Guidance page shows recommendations for resource and cost‐utilization optimization. | This permission is recommended for those responsible to optimize utilization and costs of Cloud‐based resources. |  |
+| Operations: Invoices | None, Read, Full | Determines access to the Invoices tab in Operations > Costing | The Invoices tab allows access to highly‐granular historical costing data | This permission is recommended for those responsible for generating invoices and analyzing spend |  |
+| Operations: Reports | None, Read, Full | Determines access to the Operations > Reports page. | The Reports page is where reports may be generated and exported into JSON or CSV format. | This permission is recommended for those responsible for account, infrastructure, provisioning, usage, and cost reports. |  |
+| Operations: Usage | None, Read, Full | Determines access to the Usage tab on the Operations > Activity page. | The Usage tab shows billing information for Instances and hosts that have pricing configured on their Service Plans. | This permissions is recommended for those responsible for cost accounting. |  |
+| Operations: Wiki | None, Read, Full | Determines access to the Operations > Wiki page. | The Wiki page allows easy UI, API and CLI access to information to be referenced or shared with others. Wiki pages encompass individual Clouds, Groups, Servers, Instances, Clusters, and other pages can be manually created. Wiki pages from resources are accessible from the Operations > Wiki page or within individual resource detail pages on their respective Wiki tabs. | This permission is recommend for those responsible for documentation and knowledge management. |  |
+
+## Projects Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Projects | None, Read, Full | Determines access to Projects through HPE Morpheus Enterprise API | Projects are used to associate resources together and apply common tags to their invoices | This permission is recommended for those responsible for cost analysis and invoice reporting |  |
+
+## Provisioning Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Provisioning: Administrator | None, Full | When editing an Instance (Provisioning > Instances > selected Instance > EDITbutton), this permission determines access to changing the owner of an Instance. | Allows you to change the owning user of an Instance. | This permission is recommended for those responsible to ensure all instances are owned by appropriate personnel. |  |
+| Provisioning: Advanced Node Type Options | None, Full | This allows or disallows access to the “Extra Options” field of the Node Types tab on the Library page when the Node Type Technology value is set to “VMware”. | When VMware technology type is selected for a new or existing Node Type (Library > Blueprints > Node Types), the “Extra Options” field will be available in the VMware VM Options section. These allow defining advanced vmx‐file parameters during provisioning. | This permission is recommended for those responsible for managing VMware Node Types (images). |  |
+| Provisioning: Apps | None, Read, User, Full | Determines access to the Provisioning > Apps page. The “User” permission will allow access to only object the user owns. | The Apps page allows Instances to be grouped and tiered logically into Apps. From this page, Apps can be deployed from existing Blueprints and Instances can be added to existing Apps. Security groups and environmental variables (Linux Only) may be added and edited. The App log, history, and monitoring tabs may be viewed. | This permission is recommended for those responsible for provisioning. |  |
+| Provisioning: Code Deployments | None, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Deployments page provides the ability to use git, fetch from a url, or upload a file to be utilized during the provisioning of an Instance or pushed to an existing Instance. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Code Integrations | None, Read, Full | Determines access to the Integrations tab on the Provisioning > Code page. | From this page code integrations may be created, edited, or deleted. Integrations available include Git, Github, and Jenkins. | This permission is recommended for those responsible for the integration between HPE Morpheus Enterprise and code repositories and services. |  |
+| Provisioning: Code Repositories | None, List Files, Read, Full | Determines access to the Deployments tab on the Provisioning > Code page. | The Code Repositories contains the repositories integrated with HPE Morpheus Enterprise allowing users to browse repositories folders and files and view file contents from any branch, trigger a refresh, and create tasks, scripts and templates directly from the repos. | This permission is recommended for those responsible for providing and managing software. |  |
+| Provisioning: Execute Script | None, Full | Determines access to the Run Script and Apply Template selections from the Actions menu on an Instance detail page | These selections bring up a menu allowing the user to select a script and run it against the viewed Instance or select a template to write to the Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Task | None, Full | Determines access to the Run Task selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Task and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Execute Workflow | None, Full | Determines access to the Run Workflow selection from the Actions menu on an Instance detail page | This selection brings up a menu allowing the user to select a Workflow and run it against the viewed Instance | This permission is recommended for those running day two automations against existing Instances |  |
+| Provisioning: Executions | None, Read, User | Determines access Provisioning > Executions. When the permission level is set to “User” only the executions owned by the current user are shown | Provisioning > Executions is where Task, Workflow, and Security Scan execution output can be viewed | This permission is recommended for those who are responsible for managing or troubleshooting Task, Workflow, and Security Scan executions. |  |
+| Provisioning: Import Image | None, Full | Determines access to the Import as Image and Clone to Image selections from the Actions menu on an Instance detail page | These selections allow users to create an image from an existing Instance or import the Instance as an image to a selected bucket | This permission is recommended for those responsible for managing the library of provisionable items |  |
+| Provisioning: Instances: Add | None, Full | Gives access to create Instances. Without this permission the user cannot directly add Instances. | The “+ ADD” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance create API actions as well | This permission is recommended for any user who needs to be able to provision Instances |  |
+| Provisioning: Instances: Clone | None, User, Full | Determines the presence of the “Clone” selection under the Actions menu on the Instance detail page and Instance clone API functionality | The “Clone” selection will not be available under the “Actions” menu on the Instance detail page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be cloned. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Delete | None, User, Full | Determines the presence of the “Delete” button on the Instance detail page, delete bulk action on the Instances list page, and Instance delete API functionality | The “Delete” button will not be available on the Instance detail page and the delete action will not be available from the Instances list page if permission is set to “None” and the user will not have access to similar API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be deleted. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Edit | None, User, Full | Gives access to the Edit Instances modal for existing Instances (and corresponding API functionality). This allows the user to edit an Instance display name, tags, or Input (custom option) values | The “EDIT” button will not be visible on the Instances List Page if permission is set to “None” and the user will not have access to Instance edit API actions. If permission is set to “User”, only Instances owned by the currently logged in user may be edited. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Force Delete | None, Full | Determines access to the force delete option when deleting Instances | The force delete option (checkbox) will not be available when deleting Instances if this permission is not given. Force deleting allows HPE Morpheus Enterprise to delete an Instance object even when it is unable to confirm the delete happened in the target cloud. Occasionally, this may be necessary but improper use can cause orphaned objects. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: List | None, User, Full | Controls which Instances are listed on the Instances list page (Provisioning > Instances). When set to “User”, only Instances owned by the currently logged in user will be displayed. |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Lock/Unlock | None, User, Full | Gives access to the lock/unlock actions on Instance detail pages (and corresponding API functionality). This allows the user to lock or unlock Instances which reduces the chances of accidental removal of important workloads. | The Lock/Unlock selections will not be visible in the Actions menu on the Instances List Page if permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be locked or unlocked. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Remove From Control | None, User, Full | Gives access to deleting an Instance in HPE Morpheus Enterprise only. The instance remains in the target cloud. This may only be done for brownfield workloads which were converted to managed HPE Morpheus Enterprise Instances |  | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Scale | None, User, Full | Gives access to the scale tab on Instance detail pages which allow configuration of automated scaling thresholds (and corresponding API functionality). This allows the user to control scaling thresholds and add/remove nodes from an Instance. | The Scale tab on the Instance detail pages will not be visible and the user will not be able to add/remove nodes from Instances if the permission is set to “None”. If permission is set to “User”, only Instances owned by the currently logged in user may be scaled. | This permission is recommended for any user who needs to be able to manage Instances |  |
+| Provisioning: Instances: Settings | None, User, Read, Full | Gives access to configuration changes if the Instance supports dynamic settings templates |  |  |  |
+| Provisioning: Job Executions | None, Read | Determines access to the Job Executions tab on the Provisioning > Jobs page. | The Job Executions page contains execution history of completed jobs, including any process outputs and error messages. | This permission is recommended for those who are responsible for managing or troubleshooting jobs. |  |
+| Provisioning: Jobs | None, Read, Full | Determines access to the Jobs tab on the Provisioning > Jobs page. | The Jobs page is where jobs are scheduled for the execution of automation Tasks and Workflows against Instances or servers. | This permission is recommended for those responsible to schedule the exectution of Tasks or Workflows. |  |
+| Provisioning: Remote Console | None, User, Full | Determines access to the console on a Host detail page (Infrastructure > Hosts > selected Host, VM, or Bare Metal resource > Consoletab). The “User” permission gives access to the console only for resources the logged in user owns. | Remote console access for Instances, hosts, virtual machines, and bare metal. | This permission is recommended for those who need console access for provisioned Cloud resources. |  |
+| Provisioning: Remote Console Auto Login | No, Yes | This allows or disallows the ability to automatically log into the remote console. | HPE Morpheus Enterprise will automatically log into the machine using the credentials defined on the VM or Host. The credentials are defined either from the virtual image used, added via cloud‐init or VMware Tools using the global cloud‐init settings (Administration > Settings > Provisioning), or the Linux or Windows settings defined in User Settings. | This permission is recommended when an organization utilizes HPE Morpheus Enterprise to create user accounts on provisioned or managed machines, as well as, allow remote console access. |  |
+| Provisioning: Service Mesh | None, Read, User, Full | Determines access to the Provisioning > ServiceMesh page, including the Services and DNS tabs. The “User” permission will allow access only to objects the user owns. | The Service Mesh page displays container services and DNS information. A service mesh ensures fast and reliable communication between containerized application services. | This permission is recommended for those responsible for container management. |  |
+| Provisioning: State | None, Read, Full | Determines access to the State tab for a Terraform Instance or App | The State tab is where [Terraform state management](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html#terraform-app-state-management) is handled for Terraform Instances or Apps | This permission is recommended for those responsible for any Terraform‐based workloads |  |
+
+## Security Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Security: Scanning | None, Read, Full | Determines access to the Security Packages tab on the Jobs list page (Provisioning > Jobs), Security Scanning type Jobs, and Security Subtab inside the Software tab on a server detail page where the results of security scans are viewed | Allows access to view, create, and run security scans on existing systems, as well as view the results of previously‐run scans | This permission is recommended for those responsible for security compliance of existing systems |  |
+
+## Snapshots Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Snapshots | None, Read, Full | Determines access to the “Create Snapshot” function in the Actions menu on an Instance detail page (Provisoning > Instances > selected Instance). | If utilizing a VMware Cloud, the ability to create snapshots is available on the Instance detail page (Provisoning > Instances > selected Instance). | This permission is recommended for Instance owners who should be allowed to take snapshots. |  |
+| Snapshots: Linked Clone | None, Full | For VMware Cloud Instances, this controls access to the ability to create linked clone snapshots on the Instance detail page |  |  |  |
+
+## Tools Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Tools: Archives | None, Read, Full | Determines access to the Tools > Archives page. | Archives provides a way to store files and make them available for download by scripts and users. Archives are organized by buckets. Each bucket has a unique name that is used to identify it in URLs and Scripts. | This permission is recommended for those responsible for storage or scripts which will use the Archive. |  |
+| Tools: Cypher | None, List, Read, User, Full, Full Decrypt | Determines access to the Tools > Cypher page. The “List” permission allows only listing Cypher entries in HPE Morpheus Enterprise UI and API. The “Read” permission allows listing in addition to decrypting them via automation for used in scripts and Tasks. The “User” permission will allow access similar to “Read” though only for Cypher objects the user owns, in addition to allowing for creation of Cypher entries. The “Full” permission allows creation and “Read” access to all Cypher entries regardless of who created them. The “Full Decrypt” permission gives the same rights as “Full” with the added privilege of decrypting the secret values for plaintext viewing. | Secure key/value store. Cypher keys can be used in scripts. | Recommended for those who need to store or use security key value pairs. |  |
+| Tools: Image Builder | None, Read, Full | Determines access to the Tools > Image Builder page, Image Builds, Boot Scripts, and Preseed Scripts tabs. | The HPE Morpheus Enterprise Image Builder tool creates vmdk, qcow2, vhd and raw images. The Image Builder creates a blank VM in VMware, attaches an OS ISO, executes a boot script on the VM at startup via VNC, which calls a preseed script that runs the unattended OS installation and configuration. HPE Morpheus Enterprise then executes an OVA export of the completed vmdk to the target storage provider and converts the image to all other specified formats. | Recommended for those who are responsible for image creation. |  |
+| Tools: Kubernetes | None, Read, User, Full | Allows for the management of Kubernetes clusters via the API (may be deprecated in the near future). | Allows for the management of Kubernetes clusters via the API | This permission is recommended for those who need to manage Kubernetes clusters via the API. | It is recommended this permission is set to None on the Tenant Role to restrict access for Subtenant users. |
+
+## Virtual Desktop Permission Options
+
+| Permission Name | Permission Options | Feature Access | Description | Recommendations | Tenant Role Recommendations |
+| --- | --- | --- | --- | --- | --- |
+| Virtual Desktop: Copy/Paste | None, Full | Allows copy and paste access from the virtual desktop terminal | Enables the user to copy and paste values from a virtual desktop session into the paste buffer of their local computer |  |  |
+| Virtual Desktop: Local Printer | None, Full | Enables printing from a virtual desktop session to a locally installed printer |  |  |  |
+| Tools: VDI Pools | None, Read, Full | Allows for the management of virtual desktop (VDI) pools. | Enables the user to access the VDI Pools section (Tools > VDI Pools) and view existing pools (with “read” permission) or create and edit pools (with “full” permission). Related API functions are also granted with this feature permission. | This permission is recommended for those needing to manage VDI pools |  |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json b/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
new file mode 100644
index 0000000..a8e4bc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+  "title": "Infoblox",
+  "ordinal": 507,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html",
+  "topic_cluster": {
+    "clustering_title": "Infoblox",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25",
+        "clustering_title": "Infoblox"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md b/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
new file mode 100644
index 0000000..3b3cb4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.md
@@ -0,0 +1,153 @@
+# Infoblox
+
+## Features
+
+- Network Pools synchronization
+- DNS Zone & Zone record synchronization
+- Host Record synchronization
+- Total & Free IP status bar for networks
+- Network Grid and List view with IP Status and records, date and user tracking
+- Automatic and manual IP Reservations, DNS A/PTR record creation and deletion
+- Use script variables like <%= variableX %> for evaluation of the key data in extended attributes
+
+## Adding Infoblox Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise Infoblox integration requires credentials for an Infoblox user account with API access granted, access to list the pools and zones you wish to work with, and rights to create and destroy records. See Infoblox documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network - Integrations`
+2. Select + ADD > IPAM > Infoblox
+3. Enter the following: 
+
+   ![../../_images/infoblox_settings_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-98F9FF7B-AC47-4C2E-B21B-FAE2E4D79468-high.png)
+
+   NAME
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable the Integration
+
+   URL
+   :   Infoblox wapi url. Example: <https://yourInfobloxHost/wapi/v2.10.5>
+
+       TIP
+
+       The target Infoblox host wapi version can be referenced at <https://yourInfobloxHost/wapidoc/>
+
+   USERNAME
+   :   Infoblox user username
+
+   PASSWORD
+   :   Infoblox user password
+
+   THROTTLE RATE
+   :   In milliseconds (ms)
+
+   DISABLE SSL SNI VERIFICATION
+   :   Leave selected to disable SSL SNI Verification
+
+   INVENTORY EXISTING
+   :   Mark this option to inventory existing network pools from Infoblox
+
+   NETWORK FILTER
+   :   Filter which networks are synced into HPE Morpheus Enterprise. Example: Network Filter: `network_view=default&*Building=work`
+
+   ZONE FILTER
+   :   Filter terms for Zone Records
+
+   TENANT MATCH ATTRIBUTE
+   :   This can be set to the name of the extended attribute in Infoblox where HPE Morpheus Enterprise will check for the id of a morpheus tenant. This allows for setting the tenant’s HPE Morpheus Enterprise id to an extended attribute field on a network view or network in Infoblox, and when the network or view is discovered by morpheus, it will be auto assigned to the right tenant.
+
+   IP MODE
+   :   Static IPs or DHCP Reservations
+
+   EXTRA ATTRIBUTES
+   :   Accepts a JSON input of custom attributes that can be saved on host records in Infoblox. These Must be first defined as extra attributes in Infoblox and values can be injected for the user creating the record and the date of assignment. The available injectable attributes are: userId, username, and dateCreated.
+
+       ```
+       ```
+       {  
+         "Date Assigned":"<%=dateCreated%>",  
+         "Requestor":"<%=username%>",  
+         "Request Number":"<%=userId%>"  
+       }
+       ```
+       ```
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the Infoblox IPAM integration will be created and the following will sync:
+
+- Infoblox networks will be synced in and populate in the Infrastructure - Network - IP Pools tab and in the Infoblox detail page under the NETWORK POOLS tab
+- Host Records will sync and populate in the Network Pool detail view (select an IP Pool name to view)
+- DNS Zones will sync and populate under Infrastructure - Network - Domains and in the Infoblox detail page under the HOSTS tab
+- DNS Zone Records will sync and populate
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Infoblox IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Infoblox IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time (if desired)
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP Pools or Infrastructure  >  Network  >  Services  >  Infoblox
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addhostrecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-06C4001C-7079-484B-93C0-F78B6A6000CE-high.png)
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+
+   DOMAIN
+   :   Select an Infoblox Zone
+
+   Create DNS Records
+   :   Select to create DNS A and PTR Records in Infoblox
+4. Select SAVE CHANGES
+
+## Creating Zone Records
+
+### Procedure
+
+1. Select a Domain from Infrastructure  >  Network  >  Domains or Infrastructure  >  Network  >  Services  >  Infoblox  >  Zones
+2. Select + ADD
+3. Enter the following 
+
+   ![../../_images/infoblox_addzonerecord.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9A893000-4821-4C0D-8205-5F43B0CBF5F3-high.png)
+
+   NAME
+   :   Name for the record, such as Hostname
+
+   Type
+   :   A, AAAA, CNAME, MX, NS, PTR, SOA, or TXT
+
+   CONTENT
+   :   Content of the record, such as IP or A Record
+
+   TTL
+   :   Time To Live value
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json b/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
new file mode 100644
index 0000000..ffeedeb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+  "title": "3-Node HA Upgrade",
+  "ordinal": 23,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.html",
+  "topic_cluster": {
+    "clustering_title": "3-Node HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC",
+        "clustering_title": "3-Node HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md b/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
new file mode 100644
index 0000000..345953f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5205CDAA-81D9-412F-9DF2-6A2A6CA9D1EC.md
@@ -0,0 +1,301 @@
+# 3-Node HA Upgrade
+
+3-Node HA Appliances represent 3 App nodes with local RabbitMQ and Opensearch services clustered across the app nodes, and an external MySQL cluster.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be obtained from My HPE Software Center. Reach out to your account manager with any questions regarding access.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for any 3-node variations using externalized MySQL, Opensearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+WARNING
+
+Upgrades can add additional storage load on database nodes. Please refer to database storage requirements within 3nodeinstall before upgrading.
+
+### 3-Node HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3-Node HA configurations to v8.1.2.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. With the upgrade package downloaded and transferred to each application node, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once the Node 1 upgrade has completed and the UI is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+NOTE
+
+Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps. If simply appending a port to your `appliance_url` value doesn’t work, consult the related article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/Configure-Morpheus-to-utilize-and-alternate-port-for-SSL?language=en_US).
+
+#### 3-Node Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the ui is available, upgrade the deb package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once Node 2 upgrade has completed and the ui is available, upgrade the deb package on Node 3, and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### 3-Node HA CentOS / RHEL Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in 3 Node HA configurations to v8.1.2.
+
+WARNING
+
+As a best practice, always backup your database prior to any upgrade.
+
+IMPORTANT
+
+The following is only for “3 Node HA” Architecture configurations.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### 3-Node Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once Node 1 upgrade has completed and the UI is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then, upgrade the RPM package on Node 3 and run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### 3-Node Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the RPM package on Node 1, then run a Reconfigure on Node 1. 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+2. Once Node 1 upgrade has completed and the u is available, upgrade the RPM package on Node 2, then run a Reconfigure on Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Then upgrade the RPM package on Node 3, then run a Reconfigure on Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Opensearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a service (mysql, rabbitmq, elasticsearch …) it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json b/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
new file mode 100644
index 0000000..0cef70e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+  "title": "Installing and Integrating an External Cypher Appliance",
+  "ordinal": 240,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html",
+  "topic_cluster": {
+    "clustering_title": "Installing and Integrating an External Cypher Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D",
+        "clustering_title": "Installing and Integrating an External Cypher Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md b/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
new file mode 100644
index 0000000..903d6c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.md
@@ -0,0 +1,55 @@
+# Installing and Integrating an External Cypher Appliance
+
+The external Cypher appliance runs on a small separate VM and supports a variety of base OS distributions. Credentials are securely passed to the external appliance and can be retrieved and consumed in specific places within HPE Morpheus Enterprise UI. The download URL for the installer can be retrieved from HPE Morpheus Enterprise [Hub](https://app.morpheushub.com/), replace the placeholder URL in the instructions below with the correct URL for the latest version of the Cypher appliance.
+
+Begin by provisioning and updating the VM for the Cypher appliance. Then, download the installer. The following steps go through the installation process on Ubuntu but, as mentioned in the previous paragraph, many popular distributions are supported.
+
+```
+```
+# An example URL is shown below, find the URL for the latest version and for the correct distro at |morpheus| Hub  
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-cypher_$version_amd64.deb
+```
+```
+
+Next, install and reconfigure the package.
+
+```
+```
+sudo dpkg -i morpheus-cypher_$version_amd64.deb  
+sudo morpheus-cypher-ctl reconfigure
+```
+```
+
+After the installation and reconfigure is complete, we need to record the generated API key so we can integrate the external Cypher store with HPE Morpheus Enterprise in a later step. We can get this from the logs with the following command:
+
+```
+```
+sudo morpheus-cypher-ctl tail  
+==> /var/log/morpheus-cypher/cypher/current <==  
+2022-02-02_15:22:27.84848 |  \/  (_) ___ _ __ ___  _ __   __ _ _   _| |_  
+2022-02-02_15:22:27.84848 | |\/| | |/ __| '__/ _ \| '_ \ / _` | | | | __|  
+2022-02-02_15:22:27.84848 | |  | | | (__| | | (_) | | | | (_| | |_| | |_  
+2022-02-02_15:22:27.84848 |_|  |_|_|\___|_|  \___/|_| |_|\__,_|\__,_|\__|  
+2022-02-02_15:22:27.84849   Micronaut (v3.2.2)  
+2022-02-02_15:22:27.84849  
+2022-02-02_15:22:28.09130 15:22:28.087 [main] INFO  i.m.context.env.DefaultEnvironment - Established active environments: [ec2, cloud]  
+2022-02-02_15:22:30.15129 15:22:30.151 [main] INFO  c.m.cypher.service.CypherService - Root Data: null  
+2022-02-02_15:22:30.83499 15:22:30.834 [main] INFO  c.m.cypher.service.CypherService - Initialized Root Token: c90xxxx00000xxxxxx000000xxxxx000 ... Write this down as it will only display once  
+2022-02-02_15:22:32.01282 15:22:32.012 [main] INFO  io.micronaut.runtime.Micronaut - Startup completed in 4749ms. Server Running: http://localhost:8080
+```
+```
+
+IMPORTANT
+
+The API key is only shown once when the appliance is first installed. Securely store this API key for later reference or you will be unable to integrate this Cypher appliance with any other HPE Morpheus Enterprise appliances.
+
+This completes the installation process, move to HPE Morpheus Enterprise UI to integrate the remote Cypher store with HPE Morpheus Enterprise. Cypher integrations are added in Infrastructure > Trust > Integrations. Click + ADD and then click Cypher. Configure the following:
+
+- **NAME:** A name for the Cypher integration in HPE Morpheus Enterprise
+- **ENABLED:** When checked, this Cypher integration is available for storing and retriving credentials
+- **API HOST:** The URL where your Cypher appliance can be reached (ex. <https://x.x.x.x/>)
+- **API KEY:** The API Key we retrieved and saved in the previous step
+
+![../../_images/addCypherInt.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37B0DB77-147F-4EA0-BD49-CB4DA1253ED4-high.png)
+
+Click SAVE CHANGES to save the new integration. Refer to the “Credentials” section above for details on storing new credential sets using the external appliance and how they can be called back in various places throughout the UI.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json b/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
new file mode 100644
index 0000000..bc111f1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+  "title": "Migrations",
+  "ordinal": 267,
+  "parent_title": "Tools",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF",
+        "clustering_title": "Migrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md b/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
new file mode 100644
index 0000000..8309072
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5451A5D2-E2B9-4654-B082-E0D17F6279FF.md
@@ -0,0 +1,8 @@
+# Migrations
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4CCF6004-31A7-4B35-996D-5E12877CB443.html)**
+- **[Migrations Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html)**
+- **[Migrations Plans](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3A627DBF-D797-42A2-A9AC-AAC321376068.html)**
+- **[Configuring Windows Workloads (Windows 2022 or later) for Migration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json b/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
new file mode 100644
index 0000000..80775b5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+  "title": "Add F5BigIP load balancer",
+  "ordinal": 496,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html",
+  "topic_cluster": {
+    "clustering_title": "Add F5BigIP load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5473844F-B09C-4F23-AC2F-A305A384136B",
+        "clustering_title": "Add F5BigIP load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md b/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
new file mode 100644
index 0000000..ee0192b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5473844F-B09C-4F23-AC2F-A305A384136B.md
@@ -0,0 +1,61 @@
+# Add F5BigIP load balancer
+
+## About this task
+
+NOTE
+
+- The HPE Morpheus Enterprise integration with F5 only supports basic authorization. Token-based authorization is not currently supported.
+- The F5 API handles SSL certificate installation by downloading the certificate from a URL the user provides. HPE Morpheus Enterprise provides the “Appliance URL” configured in global settings (Administration > Settings > Appliance) to satisfy that requirement. Make sure you have configured a valid URL in this field and that F5 can reach it.
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. Select **F5 BigP** from the drop-down list. 
+
+   The NEW LOAD BALANCER panel opens.   
+   ![F5 LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FBE17C69-EA72-449A-9EAC-9529F57EFA38-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   Select the load balancer group.
+
+   CLOUD
+   :   Select the load balancer cloud.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions
+
+   API HOST
+   :   Enter IP or resolvable host name url.
+
+   API PORT
+   :   Enter the API port number. Typically it will be `8443`.
+
+   USERNAME
+   :   Enter the API user name.
+
+   PASSWORD
+   :   Enter the API user password.
+
+   MANAGEMENT URL
+   :   Enter the management URL. For example, <https://10.30.20.31:8443/xui/>
+
+   Advanced Options (optional)
+   :   - ALLOW VIP ENTRY: Select this parameter to list the VIP pools.
+       - VIP POOL: Select from the drop-down list.
+       - VIRTUAL NAME: Enter a virtual name.
+       - POOL NAME: Enter a virtual name.
+       - SERVER NAME: Enter a server name.
+5. Click **Save Changes**.
+
+**Subtopics**  
+
+- **[Add Load Balancer to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html)**
+- **[F5 Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
new file mode 100644
index 0000000..754ce8f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+  "title": "Catalog",
+  "ordinal": 82,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4",
+        "clustering_title": "Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
new file mode 100644
index 0000000..ae75d6c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.md
@@ -0,0 +1,41 @@
+# Catalog
+
+The Catalog presents a simplified self-service view where users can select and deploy Instances, Blueprints or Workflows with pre-defined configuration in just a few clicks and without presenting an overwhelming list of options. Selections are presented as tiles and users can add items to a cart as if shopping on an eCommerce website. For users who tend to provision regularly from a small selection of Instance Types and configurations, the catalog is an easier option compared with the much more detailed and option-rich Instance provisioning wizard.
+
+## Configuring Catalog Item Access
+
+Within the Catalog, users are presented with selections based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items. Thus, administrators will need to enable access to some Catalog Items in order for users to make use of this view.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Catalog
+
+The catalog shows the complete list of predefined items available to the user for provisioning. Catalog items are not created here, however. For more on creating catalog items, see the Catalog Items tab in the HPE Morpheus Enterprise [Library section](https://docs.morpheusdata.com/en/latest/library/blueprints/blueprints.html#catalog-items) (Library > Blueprints > Catalog Items).
+
+![../../_images/catalog.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ED6FCF79-BB81-4C2B-B4A6-4DCB7357CFB5-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning. The catalog shows a complete list of items but the list can be filtered by entering search terms or by selecting a category. When adding or editing catalog items, an optional category may be set which aids in filtering for environments which have a lot of catalog items to select from.
+
+![../../_images/orderPage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3AE2F03E-DBC7-4FC1-BED0-DB5F6B096D9F-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![../../_images/cart.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CE0F030E-A45D-4412-92D9-38608B669FC9-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can now be viewed from their respective list pages. Depending on whether you’ve ordered an Instance, App, or Workflow execution, navigate to the appropriate list page for your item to view it.
+
+## Order Detail
+
+![../../_images/orderHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D954DA2F-C2AD-4BD7-B7C3-02CE5AEF0719-high.png)
+
+The Order Detail page includes a complete list of orders and some basic details about them. If the item still exists, you can link through to the detail page for the item (whether that be Instance detail, App detail, or Execution detail). When the item name is not hyperlinked, the item has been deleted but the record of the order remains in the history.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json b/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
new file mode 100644
index 0000000..cf717f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+  "title": "Boot",
+  "ordinal": 246,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.html",
+  "topic_cluster": {
+    "clustering_title": "Boot",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F",
+        "clustering_title": "Boot"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md b/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
new file mode 100644
index 0000000..56bb2f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-54ED92EC-A60B-4CBD-B409-D6B5F48EF81F.md
@@ -0,0 +1,11 @@
+# Boot
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4C10568E-58B7-4D0B-A76E-4144CAA0BE7E.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html)**
+- **[Mapping](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html)**
+- **[Boot Menus](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3391053D-4F2A-49A4-8823-E63F708C55C4.html)**
+- **[Answer Files](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html)**
+- **[Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-44A7BA66-FC27-40C3-8A12-2704D2043B53.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json b/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
new file mode 100644
index 0000000..cd680cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+  "title": "Virtual Images",
+  "ordinal": 146,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-55E760C3-2167-4A03-88ED-D9078C196D74.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-55E760C3-2167-4A03-88ED-D9078C196D74",
+        "clustering_title": "Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md b/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
new file mode 100644
index 0000000..1f80e32
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-55E760C3-2167-4A03-88ED-D9078C196D74.md
@@ -0,0 +1,9 @@
+# Virtual Images
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html)**
+- **[Image Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-505834BA-E280-4CA0-A4B5-FD8AC3C32AC9.html)**
+- **[Configuring Virtual Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html)**
+- **[Provisioning Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html)**
+- **[Add Virtual Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1CF5D90B-ABF3-4151-A9CE-275EB6C32BE4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json b/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
new file mode 100644
index 0000000..3f9dba5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+  "title": "Load Balancers",
+  "ordinal": 491,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html",
+  "topic_cluster": {
+    "clustering_title": "Load Balancers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-563347AC-C86B-4AC7-BF58-B80A3201662F",
+        "clustering_title": "Load Balancers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md b/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
new file mode 100644
index 0000000..a6dba66
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.md
@@ -0,0 +1,13 @@
+# Load Balancers
+
+**Subtopics**  
+
+- **[Add Amazon ALB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4983900F-0A3F-4F61-BB06-8270BE27C886.html)**
+- **[Add Amazon ELB load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html)**
+- **[Add Azure load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html)**
+- **[Add Citrix NetScaler Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1CC88F1D-21D7-4715-95BB-47F52C0AED42.html)**
+- **[Add F5BigIP load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5473844F-B09C-4F23-AC2F-A305A384136B.html)**
+- **[Add FortiADC load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html)**
+- **[Add HaProxy container load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html)**
+- **[Add NSX load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html)**
+- **[Add NSX advanced load balancer](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-269D2944-5080-4897-86F5-AC949F4B83F1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json b/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
new file mode 100644
index 0000000..94a14da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+  "title": "Proxies",
+  "ordinal": 33,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html",
+  "topic_cluster": {
+    "clustering_title": "Proxies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E",
+        "clustering_title": "Proxies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md b/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
new file mode 100644
index 0000000..f2596c4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.md
@@ -0,0 +1,27 @@
+# Proxies
+
+## Overview
+
+In many situations,companies deploy virtual machines in proxy restricted environments for things such as PCI Compliance, or just general security. As a result of this HPE Morpheus Enterprise provides out of the box support for proxy connectivity. Proxy authentication support is also provided with both Basic Authentication capabilities as well as NTLM for Windows Proxy environments. HPE Morpheus Enterprise is even able to configure virtual machines it provisions to utilize these proxies by setting up the operating systems proxy settings directly (restricted to cloud-init based Linux platforms for now, but can also be done on windows based platforms in a different manner).
+
+To get started with Proxies, it may first be important to configure the HPE Morpheus Enterprise appliance itself to have access to proxy communication for downloading service catalog images. To configure this, visit the Administration > Settings page where a section labeled “Proxy Settings” is located. Fill in the relevant connection info needed to utilize the proxy. It may also be advised to ensure that the Linux environment’s `http_proxy`, `https_proxy`, and `no_proxy` are set appropriately.
+
+## Defining Proxies
+
+Proxies can be used in a few different contexts and optionally scoped to specific networks with which one may be provisioning into or on a cloud integration as a whole. To configure a Proxy for use by the provisioning engines within HPE Morpheus Enterprise we must go to Infrastructure  >  Networks  >  Proxies. Here we can create records representing connection information for various proxies. This includes the host ip address, proxy port, and any credentials (if necessary) needed to utilize the proxy. Now that these proxies are defined we can use them in various contexts.
+
+## Cloud Communication
+
+When morpheus needs to connect to various cloud APIs to issue provisioning commands or to sync in existing environments, we need to ensure that those api endpoints are accessible by the appliance. In some cases the appliance may be behind a proxy when it comes to public cloud access like Azure and AWS. To configure the cloud integration to utilize a proxy, when adding or editing a cloud there is a setting called “API Proxy” under “Advanced Options”. This is where the proxy of choice can be selected to instruct the Provisioning engine how to communicate with the public cloud. Simply adjust this setting and the cloud should start being able to receive/issue instructions.
+
+## Provisioning with Proxies
+
+Proxy configurations can vary from operating system to operating system and in some cases it is necessary for these to be configured in the blueprints as a prerequisite. In other cases it can also be configured automatically. Mostly with the use of cloud-init (which all of our out of the box service catalog utilizes on all clouds). When editing/creating a cloud there is a setting for “Provisioning Proxy” in “Provisioning Options”. If this proxy is set, HPE Morpheus Enterprise will automatically apply these proxy settings to the guest operating system.
+
+Overriding proxy settings can also be done on the Network record. Networks (or subnets) can be configured in Infrastructure  >  Networks or on the Networks tab of the relevant Cloud detail page. Here, a proxy can also be assigned as well as additional options like the `No Proxy` rules for proxy exceptions.
+
+## Docker
+
+When provisioning Docker based hosts within a Proxy environment it is up to the user to configure the docker host proxy configuration manually. There are workflows that can be configured via the Automation engine to make this automatic when creating docker based hosts. Please see documentation on Docker and proxies for specific information.
+
+Proxy setups can vary widely from company to company, and it may be advised to contact support for help configuring morpheus to work in the proxy environment.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json b/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
new file mode 100644
index 0000000..801156d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+  "title": "Monitoring and Completion",
+  "ordinal": 427,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring and Completion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-56F6E993-6289-4BC0-AFD6-938516823FC8",
+        "clustering_title": "Monitoring and Completion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md b/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
new file mode 100644
index 0000000..ce5774c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-56F6E993-6289-4BC0-AFD6-938516823FC8.md
@@ -0,0 +1,15 @@
+# Monitoring and Completion
+
+## Procedure
+
+1. Monitor job progress from the Job Executions tab.
+2. Execution time may range from 15 minutes to over one hour, depending on:
+   1. Number of servers
+   2. Deploy mode
+   3. Selected content
+   4. Firmware and driver versions on the target servers
+3. Upon completion, detailed logs are available in the Job Executions tab.
+
+   - Do not enter any values in Custom Config.
+   - Servers are not automatically rebooted as part of the update process.
+     - If a reboot is required to complete updates, it must be performed manually at a time appropriate for the hosted services.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json b/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
new file mode 100644
index 0000000..c492393
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+  "title": "Ansible Tower",
+  "ordinal": 377,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible Tower",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9",
+        "clustering_title": "Ansible Tower"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md b/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
new file mode 100644
index 0000000..d56144e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.md
@@ -0,0 +1,184 @@
+# Ansible Tower
+
+## Overview
+
+HPE Morpheus Enterprise supports Ansible Tower for configuration management. HPE Morpheus Enterprise accomplishes this by integrating with an existing instance running Ansible Tower (AT) 3.3.0-1 and earlier. The username and password required for integration can be a user with admin access or a user with project admin access
+
+HPE Morpheus Enterprise will import the current Inventory, Templates, Hosts, Groups and Projects. In the integration view it will add a Job tab which will have information of all the jobs executed from HPE Morpheus Enterprise.
+
+NOTE
+
+This integration will not import data of the jobs which are not executed from HPE Morpheus Enterprise.
+
+## Add Ansible Tower Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Ansible Tower”
+3. Populate the following fields: 
+
+   - Name: Name of the Ansible Tower Integration in HPE Morpheus Enterprise
+   - Enabled: To disable the integration, uncheck this option
+   - Ansible Tower URL: An HTTPS or HTTP Ansible Tower URL
+   - Username: The user HPE Morpheus Enterprise would use to communicate with Ansible Tower
+   - Password: Enter the password. Password is encrypted and saved in DB
+   - API Version: This drop down has one option (`v2`) for now but may have others in future
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Scope Ansible Tower Integration to a Cloud
+
+### About this task
+
+All instances provisioned in this cloud will have the Ansible Tower config option during provisioning. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Scope Ansible Tower Integration to a Group
+
+### About this task
+
+All instances provisioned in this Group will have the Ansible Tower config option during provisioning in any cloud part of the Group. See below the Provisioning Options for more details about the options.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Tower Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Tower Integration added, an Ansible Tower section will appear in the Config section of the provisioning wizard. By default, Ansible Tower is enabled, but can be disabled by expanding the Ansible Tower section and unchecking Enable Ansible Tower.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible Tower
+:   Select to bootstrap
+
+Inventory
+:   A list of Inventory available in Ansible Tower will appear in the drop down. Select an existing inventory. The instance will be added to the inventory selected.
+
+Ansible Group
+:   Enter the name of a new or an existing Group in the inventory selected above.
+
+Template
+:   Select an existing template or select the option ‘Create New Template’. If ‘Create New Template’ is selected below fields will appear and are mandatory
+    :   Template Name
+        :   Enter the template name
+
+        Project
+        :   Select an existing project from the drop down options
+
+        Playbook
+        :   Select a playbook from the dropdown to be associated with the template. Note: HPE Morpheus Enterprise doesn’t store a local copy of the playbooks visible in Ansible Tower. SCM or local path for playbooks should be maintained in Ansible Tower.
+
+Execute Mode
+:   Select one of the options from the dropdown
+    :   Limit to instance
+        :   This will execute the template on the instance provisioned.
+
+        Limit to Group
+        :   This will execute the template on all hosts attached to the group entered in the ‘Ansible Group’ field.
+
+        Run for all
+        :   This will execute the template on all hosts in the inventory
+
+        Skip execution
+        :   This will skip the execution of the template on the instance provisioned.
+
+## Scoping Ansible Tower Jobs to Tenant-Default Inventories
+
+Users in the Primary Tenant have an additional Inventory execution option when creating Ansible Tower Job-type Tasks. When making a selection in the Inventory field, “Use Tenant Default” may be selected rather than a specific Inventory. This is because Ansible Tower Jobs created in the Primary Tenant may be shared publicly to other Tenants through public Workflows or when associated with public Library items.
+
+![../../_images/ansibleTowerInventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-628F3A54-3E8C-4986-8502-5ADA96A0ACC6-high.png)
+
+When this option is selected and the Task is run in a Subtenant, it will automatically be run against the default Inventory which is configured for the Subtenant. The next section includes steps for associating Tenants and default Inventories.
+
+IMPORTANT
+
+An Ansible Tower Job configured to run against a Tenant-default Inventory will fail when run by a user whose Tenant does not have a default Inventory set.
+
+### Setting Default Inventories for Tenants
+
+When creating or editing Ansible Tower integrations, navigate to the Inventory tab to view all Inventories synced from the selected integration. Click “Permissions” inside the “MORE” action menu at the end of a row for the selected Invetory. Within the PERMISSIONS modal, there is a single typeahead field where a Tenant can be selected. Once the Tenant is selected, click SAVE CHANGES. Now back on the Inventory list view, you’ll see the default Tenant which is associated with each Inventory.
+
+NOTE
+
+Tenants may only be associated with one Inventory, though an Inventory can have multiple Tenant associations. If a Tenant is selected to be associated with a new Inventory, its association with a previous Inventory will automatically be removed.
+
+![../../_images/inventoryList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8724DEA8-C761-416C-81CA-D3F82E6177B8-high.png)
+
+## Ansible Tower Configuration
+
+When using an Ansible Tower task type or associating the Ansible Tower integration with a cloud/group, there are a few options that can be configured:
+
+- Inventory
+- Group
+- Job Template
+- Execute Mode
+
+### Prompt at Launch
+
+Some options used to configure your deployments have the related option of **Prompt at Launch** in Ansible Tower, which should be enabled on the template to be chosen in the **Job Template** field. If **Prompt at Launch** is not enabled, the values configured on the template in Ansible Tower will be used instead. **Prompt at Launch** can be seen below on the **Inventory** and **Limit** fields:
+
+![../../_images/ansibleTowerPromptAtLaunch.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4731D3C6-EE0D-46A5-A78C-DD7235B7A582-high.png)
+
+### Group
+
+The **Group** field is optional but a group can be entered into the field to associate the host to, in the target inventory. If the group is existing, then the instance will be associated as a host to that group. If the group does not exist, the group will be created and the instance will be associated as a host to that group.
+
+![../../_images/ansibleTowerGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-048E8C28-2E88-4711-B75F-2E8EEB9FA747-high.png)
+
+### Inventory
+
+When provisioning on a cloud with a configured Ansible Tower integration or using an Ansible Tower task type against an instance, the instance will be added as a host to the inventory chosen in the **Inventory** field. As mentioned, if specified, these instance will be associated with groups in the inventory as well. When using an inventory that syncs from a project, the instance will still be added as a host in the inventory, in addition to the sync’d inventory. This means that Ansible Tower will aggregate the manually added hosts from HPE Morpheus Enterprise with the sync’d project inventory. However, if the **Overwrite** option is enabled on the source for the project that contains the inventory, any hosts added by HPE Morpheus Enterprise **will be overwritten**. In some cases, a separate HPE Morpheus Enterprise inventory may be desired, if **Overwrite** is required on your sources.
+
+![../../_images/ansibleTowerOverwrite.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ECAFBE4F-9B9C-42E0-86EE-30B3860FFEBF-high.png)
+
+## Passing extra\_vars to Ansible Tower Job
+
+When provisioning or when running Ansible Tower Jobs as HPE Morpheus Enterprise Tasks, you may pass the `extra_vars` stack to the Tower Job. First, ensure the Job Template has extra variables “Prompt on Launch” enabled as shown below:
+
+![../../_images/towerExtraVars.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4C836374-5A94-4045-AE04-99B90A2F4F9F-high.png)
+
+The sample Playbook below is associated with the Tower Job Template.
+
+```
+```
+---  
+- hosts: all  
+vars:  
+  Opensource_Team: "Customer"  
+tasks:  
+- name: Print Hello World  
+  debug:  
+    msg:  
+    - "Hello World {{ Opensource_Team }}. Here are Morpheus extra_vars: {{ morpheus }}"
+```
+```
+
+After executing the Tower Job, we can see the variable stack surfaced into the results as defined in the Playbook:
+
+![../../_images/towerResults.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-47CAE600-317C-468B-B98F-69522E132DE4-high.png)
+
+## Use Case
+
+You have Job template(s) in Ansible Tower to do post build config after the OS is deployed. The playbook with roles and tasks to do post build will add specific users and groups, install required packages, remove packages, disable services, change config for ntp, resolv, hosts etc. You want to add the instance to an existing Group/Inventory in Tower.
+
+You can achieve this by adding the Ansible Tower Integration and then scope it to a Cloud or Group. While provisioning an instance, in the config stage you have the Ansible Tower section with option to select the post build job template, select the Inventory and provide an existing Group Name or if the Group doesn’t exist Morpheus will create it and submit for provisioning.
+
+Morpheus will provision the instance, once it is in the finalize state where the instance has an ip and has completed domain join if required, added user(s) or User Groups if specified then HPE Morpheus Enterprise will add the instance to the inventory and Group and run the Template which will do all the post build of the server.
+
+The output of the post build template execution can be see under Instance history.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json b/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
new file mode 100644
index 0000000..ae9afc7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+  "title": "IP Pools",
+  "ordinal": 220,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.html",
+  "topic_cluster": {
+    "clustering_title": "IP Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E",
+        "clustering_title": "IP Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md b/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
new file mode 100644
index 0000000..e5c75db
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-57B7AEAF-921C-43D2-8A65-2BEA1310EE1E.md
@@ -0,0 +1,34 @@
+# IP Pools
+
+Infrastructure  >  Network  >  IP Pools
+
+## Overview
+
+The IP Pools tab in the Networks section allows you to create HPE Morpheus Enterprise-type IP Pools (which is an IP address range HPE Morpheus Enterprise can use to assign available static IP addresses to Instances) and NSX IP Pools. The IP Pool section also displays pools synced from IPAM integrations like Infoblox, Bluecat and others.
+
+## To add a HPE Morpheus Enterprise Network Pool
+
+### Procedure
+
+1. Click + ADD in Infrastructure  >  Network  >  IP Pools
+2. Enter the following:
+   :   Name
+       :   A friendly name for the IP Pool in HPE Morpheus Enterprise.
+
+       Pool Type
+       :   Currently HPE Morpheus Enterprise-type IP Pools and NSX IP Pools (with a configured integration) can be created directly from HPE Morpheus Enterprise
+
+       Starting Address
+       :   The starting IP address of the IP Pool address range. ex: 192.168.0.2
+
+       Ending Address:
+       :   The ending IP address of the IP Pool address range. ex: 192.168.0.255
+3. Save Changes
+
+### Results
+
+NOTE
+
+Multiple Address Ranges can be added to a pool by selecting the + icon next to the address range.
+
+After saving the IP pool will be available for assignment to networks in the NETWORK POOL dropdown when adding or editing a network.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json b/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
new file mode 100644
index 0000000..43c8767
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+  "title": "Executions",
+  "ordinal": 95,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html",
+  "topic_cluster": {
+    "clustering_title": "Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9",
+        "clustering_title": "Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md b/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
new file mode 100644
index 0000000..d2b4d49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.md
@@ -0,0 +1,31 @@
+# Executions
+
+Executions contains the execution status and history from Task and Operational Workflow Executions run from Library > Automation > Tasks and Library > Automation > Workflows. Executions for Tasks and Workflows are split out to their own labeled tabs.
+
+NOTE
+
+Tasks and Workflows executed from a Job or from Instance or Host `Actions` do not populate in the Executions Section, and can be referenced from the History tab on the target resource. All task and Workflow executions can be referenced in Operations  >  Activity  >  History
+
+Execution results in the ui display:
+
+NAME
+:   Name of the Task or Workflow Executed
+
+TYPE
+:   Type of execution (Task or Workflow)
+
+START DATE
+:   Date and time of execution
+
+ETA/DURATION
+:   Estimate time of completion for executions in progress, or the total execution time for completed executions.
+
+RESULTS
+:   Result status of execution (Succeeded, Failed, In-Progress or Pending)
+
+Execution Detail (i)
+:   Click on the `i` to view process output results
+
+    NOTE
+
+    Job and automation executions can be expanded to show process details by clicking on the arrow icon immediately to the right of the NAME column.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json b/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
new file mode 100644
index 0000000..b565847
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+  "title": "GPU Passthrough Example",
+  "ordinal": 196,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html",
+  "topic_cluster": {
+    "clustering_title": "GPU Passthrough Example",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-580E4107-827A-43F6-888D-5CDD41EB42E0",
+        "clustering_title": "GPU Passthrough Example"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md b/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
new file mode 100644
index 0000000..11b39e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.md
@@ -0,0 +1,25 @@
+# GPU Passthrough Example
+
+In a previous section, a Service Plan was created which consumes a GPU when a VM is provisioned using that Plan. This section shows an example provisioning a workload using that Plan and a GPU-accelerated workload running on the VM. In this example, there is an Nvidia GeForce RTX 3050 connected to one of the HVM Hosts. By passing the GPU hardware through to a provisioned VM, hardware-accelerated AI workloads can be run on the VM.
+
+Begin by navigating to Provisioning > Instances. The list of all currently-managed Instances is here along with high level information (power state, etc). To begin a new Instance, click + ADD. Choose type HVM and click NEXT. On the next pane, choose the Group and Cloud in which your desired HVM Cluster resides, name the Instance, and click NEXT.
+
+On the CONFIGURE tab, the main thing to note for this example is the PLAN configuration. This dropdown contains some default Plans that are included with HPE Morpheus VM Essentials and compatible with the HVM provisioning technology (named “1 CPU, 1GB Memory”, etc). This dropdown also includes user-created Plans, such as those you’ve created to consume GPU hardware. In the screenshot below, you can see the “GPU Plan” was selected.
+
+![../../_images/showPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1FD71B7E-138D-4F35-B57F-AA2C3AA2E357-high.png)
+
+From here, complete the Instance provisioning wizard selecting any automation or lifecycle configurations and wait for the Instance provisioning to complete.
+
+With provisioning complete, check the attached device(s) from the HPE Morpheus VM Essentials UI. This is done from the VM level rather than the Instance level. From the Instance detail page, click on the Resources tab. Click on the name of the desired VM to access the VM detail page. Click on the Devices tab. As in the screenshot below, the attached GPU should be shown.
+
+![../../_images/attachedGpu.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5AC07D64-3534-439B-925D-858854858310-high.png)
+
+To go further, open a console session to the new VM either through HPE Morpheus VM Essentials UI or by connecting to the VM over SSH from a local terminal session. Use the `lspci` command to view all devices connected to PCI buses. The attached GPU should be shown here as it is in the UI.
+
+At this point, the VM is ready to run GPU-accelerated workloads normally. To test this, I’ll run Ollama which is an open-source tool designed to make it easy to run large language models (LLMs) locally. In the screenshot below, see the AI chatbot response to an input. This result took only a few seconds thanks to GPU hardware acceleration.
+
+![../../_images/ollamaOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FEED6AA7-831F-4630-93F2-BD77DAB2EF2C-high.png)
+
+With the request completed, we can run the `ollama ps` command which confirms the model was running under GPU acceleration.
+
+![../../_images/gpuUsed.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-15D2AC03-19A9-47B0-8D16-7EA83603BDF2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json b/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
new file mode 100644
index 0000000..9c6274f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+  "title": "User Groups",
+  "ordinal": 310,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html",
+  "topic_cluster": {
+    "clustering_title": "User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-589A7663-2242-4FBE-9214-FE0F91A29972",
+        "clustering_title": "User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md b/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
new file mode 100644
index 0000000..3542af6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-589A7663-2242-4FBE-9214-FE0F91A29972.md
@@ -0,0 +1,49 @@
+# User Groups
+
+## Overview
+
+User Groups can be selected during provisioning to add each group members credentials to the Instance. User Groups can be configured for sudo access and in Linux will assign Group members to a groupId in linux.
+
+## Creating User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select + CREATE USER GROUP.
+4. Enter the following: 
+
+   NAME
+   :   Name of the User Group
+
+   DESCRIPTION
+   :   Optional User Group Description
+
+   SERVER GROUP
+   :   Name of the groupId to assign Group members to in linux.
+
+   SUDO ACCESS
+   :   Enable to give Group members sudo access
+
+   USERS
+   :   Search for and select existing Users to add to the User Group.
+5. Select SAVE CHANGES.
+
+## Editing User Groups
+
+### Procedure
+
+1. Navigate to Administration > Users
+2. Select the USER GROUPS tab.
+3. Select the ACTIONS dropdown next to the target User Group.
+4. Select EDIT
+5. Make changes, add or remove users from the group.
+6. Select SAVE CHANGES.
+
+## Adding a User Group when Provisioning
+
+### Procedure
+
+1. When provisioning, in the CONFIG section expand the USER section.
+2. Select an existing Group from the USER GROUP dropdown.
+3. Users will be created for members in the selected User Group on the provisioned Instance(s).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json b/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
new file mode 100644
index 0000000..349b301
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+  "title": "Local Storage - Boot Volume Selection During Instance Creation",
+  "ordinal": 455,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html",
+  "topic_cluster": {
+    "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251",
+        "clustering_title": "Local Storage - Boot Volume Selection During Instance Creation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md b/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
new file mode 100644
index 0000000..a41e474
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.md
@@ -0,0 +1,9 @@
+# Local Storage - Boot Volume Selection During Instance Creation
+
+Table 1. Boot Volume Selection During Instance Creation
+
+        | S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Boot volume not found | Device UID mismatch or not yet discovered | - Confirm device discovery is complete - Verify the UID in the storage controller | - | Wait for discovery to complete and retry. |
+| 2 | `ResourceMissingAtURI` errors | Redfish device discovery is not complete | - Verify Redfish discovery status - Confirm the device is visible in Redfish inventory | - | Retry after a short wait. |
+| 3 | Script cannot find the device | UID format mismatch or missing disk link | - Verify `/dev/disk/by-id/` entries  - Confirm correct disk UID format | - | Ensure disk links are correctly mapped and retry. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
new file mode 100644
index 0000000..b2cc655
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+  "title": "Clusters",
+  "ordinal": 170,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.html",
+  "topic_cluster": {
+    "clustering_title": "Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC",
+        "clustering_title": "Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
new file mode 100644
index 0000000..b878c02
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-592C33A6-7AC6-457A-B490-ABB2DA7E68DC.md
@@ -0,0 +1,13 @@
+# Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1621A716-2765-4655-B4D0-C95B8416F4D3.html)**
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html)**
+- **[Cluster Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html)**
+- **[HVM Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html)**
+- **[Kubernetes Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3159C5BA-04D5-4035-9842-86197618F7D2.html)**
+- **[Docker Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-07A9C046-F9C9-4C39-BB10-1F2E9D96C2C2.html)**
+- **[EKS Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html)**
+- **[GKE Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html)**
+- **[OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json b/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
new file mode 100644
index 0000000..0b76e8d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+  "title": "Deployments",
+  "ordinal": 99,
+  "parent_title": "Code",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html",
+  "topic_cluster": {
+    "clustering_title": "Deployments",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA",
+        "clustering_title": "Deployments"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md b/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
new file mode 100644
index 0000000..27f1af5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.md
@@ -0,0 +1,110 @@
+# Deployments
+
+NOTE
+
+In v5.3.2+, Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+
+The deployments section provides very useful PaaS like capabilities when it comes to deploying applications into the newly provisioned environment. These can be uploaded directly from the UI, pulled from a build server, pulled from a public or private Git repository or even via the API and the various plugins created, such as Jenkins, and Gradle to support continuous build / integration workflows.
+
+A deployment can be considered a set of versions that relate to a particular project or application being deployed. This allows one to keep track of a history of versions and easily reuse these deployment versions across Instances that may exist in different environments. An example might be to deploy a version from a deployment to a staging Instance and (once approved) also deployed into production.
+
+## Role Permissions
+
+Access and capabilities for the **Deployments** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+## Getting Started
+
+Getting started with deployments is easy. They can vary slightly for the application stack being deployed but the simplest phase of a deployment is adding a version and adding the appropriate files to the deployment archive that are needed for the application to run. This could be a single file like a WAR file for Tomcat, or it could be hundreds of files for stacks like Ruby on Rails.
+
+There are a few ways to create a deployment. The first is to use the Provisioning ‣ Code ‣ Deployments section of the application to create them. Simply add a new deployment and give it a name representing the application that is being deployed. Once a deployment is created select the deployment to view its versions (which will be empty to start). Next, it is time to add a version.
+
+When adding a version there are several options. There are 3 types represented by the UI. These include File, Fetch, and Git respectively. A File deployment allows the user to simply drag their files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees (If files exist in subfolders then only the Chrome browser is supported due to browser limitations at the time of this writing). This is also the common type that is represented when files are uploaded via the CLI, or available build tool integration plugins. Once the files have completed their upload simply save the version for use.
+
+### Git
+
+For performing git based deploys HPE Morpheus Enterprise supports both public and private repositories. To utilize a private git repository the add version dialog will display a public keypair that can be added to the git service for authentication purposes. Currently this keypair is shared across the account and not specifically scoped to the user so it may be advisable to connect this integration to a deployment account in git. From here either a ssh or `https` git url can be entered along with a git branch or tag name. Once the version is saved, this repository will be copied down into the deployment archive for use.
+
+### Fetch
+
+Fetch based deployments are pretty straightforward. Simply enter a url to a file representing the deployment. This can be a single file (in which case it will just be added to the deployment archive singularly) or it can be a zip file (which will automatically be expanded into the archive). HTTP Authentication options can also be entered if the url requires some form of basic authentication scheme for access by the appliance.
+
+## Configuring Library Items for Deployments
+
+In order to have the UI tools available to utilize Deployments with a provisioned Instance, the Library items must have certain configurations set. Once configured correctly, any Instance provisioned from the Library item would then have access to any of your Deployments.
+
+First, within the **Instance Type** (Library > Blueprints > Instance Types), ensure the SUPPORT DEPLOYMENTS attribute is marked. This is off by default so it will need to be manually enabled on all relevant Instance Types. Next, you’ll want to ensure you have the correct DEPLOY FOLDER configured on **Node Types** (Library > Blueprints > Node Types). This is the mount point which will be replaced by the contents of your Deployments. Finally, you will want the **Provisioning Workflows** associated with the Library item to have the proper Tasks configured within its Pre-Deploy and/or Deploy phases. Tasks in the Pre-Deploy phase are run as soon as the Deployment is triggered from the UI prior to any other Deploy actions taking place. This could be used, for example, to extract files from the deploy folder and move them to their final destinations before the primary deploy actions take place. Tasks in the Deploy phase are run after the deployment is completed, such as if you wanted to update configuration files or inject connection details from the environment after the completion of the deploy process.
+
+## Deploying to an Instance
+
+Now that the Deployment object and Library items are configured, it is easy to push that deployment out to any Instance provisioned within HPE Morpheus Enterprise by navigating to the specific Instance that it needs deployed to. On the Instance detail page there is a tab called Runtime and within it another tab labeled Deploy. From here simply add a deploy. The dialog will ask firstly from which deployment the deploy is from (or allow you to create a new one on the spot), and secondly which version to deploy (also with the option to add one on the fly). The next step of the wizard will display any configuration options that might be specific to the Instance type being deployed to (i.e. CATALINA\_OPTS for Tomcat or Java Command for java) as well as the file explorer and deployment type selections for review (or use when creating a new version on the fly). Fill in the required items then simply hit complete. The deploy will now be asynchronously sent off to all of the virtual machines or containers within the Instance in a rolling restart and the deployment status will be represented.
+
+TIP
+
+When deploying to an Instance, the custom configuration options that were entered during the previous deployment are automatically carried forward allowing one to edit them or leave them as is.
+
+## Rolling Backwards and Forwards
+
+Because of the tracked history of deployments kept within HPE Morpheus Enterprise, the deploy tab of Instance detail makes it easy to choose a previously run deployment and jump back to it in the event of a failed deployment. The history will automatically be updated and the configuration, as well as data from the previous deployment state of the Instance will be restored.
+
+## Offloading Storage
+
+Since a full history of the backup builds are kept in HPE Morpheus Enterprise, as the appliance grows it becomes necessary to change where these are stored. On a fresh install these are stored on the local appliance in `/var/opt/morpheus` or wherever the master account may have changed the configuration to point to. It is also possible to adjust the deployment archive store by creating a Storage Provider tied to an S3 compatible object store, Openstack Swift object store, or any other type of mountpoint provided. This option can be adjusted in Administration > Settings > Provisioning once a storage provider is created within the account.
+
+## Add Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the + Add button.
+5. Enter a Name for the deployment and a description (optional)
+6. Click the Save Changes button to save.
+
+## Add Version
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the Name of the deployment you would like to add a version to.
+5. Click the Add Version button.
+6. From the Add Version Wizard select the deployment type.
+7. Input the Version of the deployment.
+8. Depending on the type of deployment selected perform one of the following: 
+
+   Files
+   :   Drag files into the file explorer presented by the dialog. This file explorer can take single files or entire file trees.
+
+   Fetch
+   :   Enter a url to a file representing the deployment.
+
+   Git
+   :   The add version dialog will display a public key pair that can be added to the git service for authentication purposes. Either a ssh or https git url can be entered along with a git branch or tag name.
+9. Click the Save Changes button to save.
+
+## Edit Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the ✎ icon on the row of the deployment you wish to edit, or click the Name of the deployment and then the Edit button from the deployment detail page.
+5. Modify information as needed
+6. Click the Save Changes button to save.
+
+## Delete Deployment
+
+### Procedure
+
+1. Select the `Provisioning` link in the navigation bar.
+2. Select the `Code` link in the sub-navigation bar.
+3. Select the `Deployments` tab.
+4. Click the 🗑 icon on the row of the deployment you wish to delete, or click the Name of the deployment and then the DELETE button.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json b/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
new file mode 100644
index 0000000..71fdef1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+  "title": "Costing: Tag Costing",
+  "ordinal": 64,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tag Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5AE10D03-5E33-4437-8477-059B0390B662",
+        "clustering_title": "Costing: Tag Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md b/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
new file mode 100644
index 0000000..8ac65dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5AE10D03-5E33-4437-8477-059B0390B662.md
@@ -0,0 +1,28 @@
+# Costing: Tag Costing
+
+![../_images/7tagcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3B425176-5841-4C03-B67D-F6B86603E1CD-high.png)
+
+The Tag Analysis dashboard creates groups of workloads based on the presence of specific tags and meeting other filters. This workload group can be analyzed for total cost and projected costs.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Tag key (all matched by search)
+- Metric (apply to see the top tag values by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+
+## Data Displayed
+
+The following aggregate totals (by tag) are compiled for workloads that meet set filters:
+
+- **TAGS:** The total number of unique tag keys for workloads meeting dashboard filters
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+
+## Tags List
+
+A list of each tag (key) represented on selected workloads is displayed in a list below the dashboard graphs. We also see the total number of workloads associated with the tag, the total memory, total storage, total CPU cores, and total price. If we click the “MORE” link at the end of each row, we can see a list of all tag values associated with the key.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json b/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
new file mode 100644
index 0000000..dc18635
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+  "title": "Storage",
+  "ordinal": 454,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5B7DB753-B382-4E98-BF3A-599C15334A69",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md b/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
new file mode 100644
index 0000000..7f80239
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.md
@@ -0,0 +1,8 @@
+# Storage
+
+The topic describes troubleshooting procedures for storage.
+
+**Subtopics**  
+
+- **[Local Storage - Boot Volume Selection During Instance Creation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-58D8BDA8-9485-4D86-AB25-3DDC8F738251.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json b/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
new file mode 100644
index 0000000..3bb14cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+  "title": "Groups",
+  "ordinal": 168,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.html",
+  "topic_cluster": {
+    "clustering_title": "Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56",
+        "clustering_title": "Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md b/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
new file mode 100644
index 0000000..f4e5605
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5CAFD8A5-00B4-47E1-983D-422EFEE26E56.md
@@ -0,0 +1,119 @@
+# Groups
+
+## Overview
+
+### About this task
+
+Groups in HPE Morpheus Enterprise define what resources a user has access to. Group access is defined by User Roles. Clouds are added to groups, and a User can only access the Clouds that are in the Groups their Role(s) gives them access to. Resources such as Networks, Datastores, Resources Pools, and Folders have additional Group access settings.
+
+Policies applied to a Group will be enforced on all Instances provisioned or moved into that Group.
+
+NOTE
+
+Groups are not multi-tenant. A group only exists in the tenant is it is created in.
+
+The Groups view displays all current groups, includes search feature, and also enables the addition of new groups.
+
+To View Groups:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## UI
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+
+## CLI
+
+View all groups: `groups list` To use the group: `groups use <id>` or `groups use "group name"` Json output of a specific group: `groups get <id> -j` or `groups get "group name" -j`
+
+## API
+
+View all groups: `curl https://api.gomorpheus.com/api/groups -H "Authorization: BEARER access_token"` View a specific group: `curl https://api.gomorpheus.com/api/groups/:id -H "Authorization: BEARER access_token"`
+
+## Adding Groups
+
+### About this task
+
+![../../_images/add_group.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-314860C2-E6E2-4F71-9AC0-AEE0E9E53A08-high.png)
+
+To add a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Create Group button
+4. Input out the Name and Location (optional) fields
+5. Click the Save Changes button to save
+
+## Managing Groups
+
+### About this task
+
+![../../_images/group_view.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4D1622A4-0DFF-47E7-AFF2-B9CBC2298957-high.png)
+
+To view a Group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar
+2. Click the Groups link
+3. Click the Group name to view/modify
+
+### Results
+
+Available tabs in group view
+
+Hosts
+:   Lists available hosts in the group and displays power, os, name, type, cloud, ip address, nodes, disc space, memory, and status. You can add a host from this tab panel by clicking Add Host.
+
+Virtual Machines
+:   List all Virtual Machines in the Group.
+
+Bare Metal
+:   List all Bare Metal Hosts added to the Group
+
+Clouds
+:   Lists Clouds added to the Group. Existing Clouds or new Clouds can be added from the Group by clicking Add Cloud.
+
+Policies
+:   Lists and allows creation or management of Policies applied to the Group.
+
+## Edit Group
+
+### About this task
+
+To edit a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to edit.
+4. Click the Edit button.
+5. From the Edit Group Wizard modify information as needed.
+6. Click the Save Changes button to save.
+
+## Delete Group
+
+### About this task
+
+To delete a group:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Click the Groups link.
+3. Click the name of the group you wish to delete.
+4. Click the Delete button.
+5. Confirm
+
+## User Access
+
+IMPORTANT
+
+User access to Groups is determined by their user Role(s). Group access for Roles can be configured in the Group Access section of a Roles Settings.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json b/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
new file mode 100644
index 0000000..e1e1540
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+  "title": "Example Cluster Deployment",
+  "ordinal": 180,
+  "parent_title": "Base Cluster Details",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html",
+  "topic_cluster": {
+    "clustering_title": "Example Cluster Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D",
+        "clustering_title": "Example Cluster Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md b/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
new file mode 100644
index 0000000..d260807
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.md
@@ -0,0 +1,15 @@
+# Example Cluster Deployment
+
+In this example cluster, each host box consists of:
+
+- 4 vCPU
+- 16 GB memory
+- 20 GB OS boot disk
+- 250 GB data disk (deployed to `/dev/sdb`)
+- 3 network interfaces for management, storage, and compute traffic (set to `eth0`, `eth1`, and `eth2`, respectively, in this example. Your environment may differ.)
+
+NOTE
+
+250 GB data disks used in this example are simply for demonstration purposes. A typical test cluster should consist of at least 500 GB storage and more will be required for production. Do not raid disks on physical servers. Multiple disks may be specified per host by giving a comma-separated list (ex. /dev/sda,/dev/sdb,/dev/sdc,etc.) in the DATA DEVICE field during cluster setup. These along with disks from all other nodes will be added to the total CEPH storage, which is presented as one large volume.
+
+HVM clusters must also live in HPE Morpheus Enterprise-type Clouds (See Infrastructure > Clouds). A pre-existing HPE Morpheus Enterprise Cloud may be used or a new Cloud could be created to handle HVM management.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json b/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
new file mode 100644
index 0000000..7b7da01
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+  "title": "Network Groups",
+  "ordinal": 218,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.html",
+  "topic_cluster": {
+    "clustering_title": "Network Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E",
+        "clustering_title": "Network Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md b/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
new file mode 100644
index 0000000..7312abd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D0A7A5B-88E9-46E9-97E8-513DBDD06B0E.md
@@ -0,0 +1,26 @@
+# Network Groups
+
+Network Groups are useful for grouping networks during provisioning and scaling or grouping availability subnets together such that during provisioning vm’s within an instance can be round robin provisioned across availability zones.
+
+## Adding Network Groups
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks Groups
+2. Select ADD
+3. Enter the following: 
+
+   Group info:
+   :   - Name: Name of the Network Group in HPE Morpheus Enterprise
+       - Description: Details of the Network Group in HPE Morpheus Enterprise
+
+   Networks
+   :   - Search for and select target Networks for the Network Group
+       - Search for and select target Subnets for the Network Group
+
+   Group Access
+   :   - Set Group Access for the Network Group. Group access controls which Groups at provision time will have access to this resource. Select “all” (default) to give workloads provisioned to any Group access to this resource. If this resource should be restricted only to workloads provisioned to specific Groups, select all that apply.
+
+   Tenant Permissions
+   :   - Resources with Public visibility will be available to users in any Tenant (subject to other RBAC controls). Resources with Private visibility are given only to individually selected Tenants. Select all that apply.
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json b/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
new file mode 100644
index 0000000..6c1c69a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+  "title": "Remedy",
+  "ordinal": 490,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.html",
+  "topic_cluster": {
+    "clustering_title": "Remedy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287",
+        "clustering_title": "Remedy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md b/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
new file mode 100644
index 0000000..a86d3d2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D52CEDB-FB3B-48D5-A9D3-3E85F3095287.md
@@ -0,0 +1,80 @@
+# Remedy
+
+## PreRequisites
+
+The user used for this integration need to be an Administrator in Remedy or have all the permissions to the form that is outlined in the table below.
+
+Table 1.
+
+      | API Endpoint | Action | BMC Form | Existing BMC Role |
+| --- | --- | --- | --- |
+| /api/arsys/v1/entry/CTM:People | GET | CTM:People | Contact People Admin |
+| /api/arsys/v1/entry/COM:Company?q=%27Status%27=%22Enabled%22&fields=values(Company) | GET | COM:Company | Atrium Foundation Admin |
+| /api/arsys/v1/entry/User | GET | User | User Administrator |
+| /api/arsys/v1/entry/Group | GET | Group | User Administrator |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | POST | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | PUT | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/arsys/v1/entry/CHG:Infrastructure%20Change | GET | CHG:Infrastructure Change | Infrastructure Change Master |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | POST | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | PATCH | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | GET | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_DiskDrive | DELETE | BMC.CORE:BMC\_DiskDrive | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | POST | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | PATCH | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | GET | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_IPEndpoint | DELETE | BMC.CORE:BMC\_IPEndpoint | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | POST | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | PATCH | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | GET | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Memory | DELETE | BMC.CORE:BMC\_Memory | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | POST | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | PATCH | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | GET | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/cmdb/v1.0/instances/BMC.ASSET/BMC.CORE/BMC\_Processor | DELETE | BMC.CORE:BMC\_Processor | CMDB Data Change All |
+| /api/arsys/v1/entry/AST:ComputerSystem | GET | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | PUT | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:ComputerSystem | POST | AST:ComputeSystem | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | GET | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | PUT | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:IPEndpoint | POST | AST:IPEndpoint | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | GET | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | PUT | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:DiskDrive | POST | AST:DiskDrive | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | GET | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | PUT | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Processor | POST | AST:Processor | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | GET | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | PUT | AST:Memory | Asset Admin |
+| /api/arsys/v1/entry/AST:Memory | POST | AST:Memory | Asset Admin |
+| /api/jwt/login | POST |  |  |
+
+## Add Remedy Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Remedy` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   REMEDY HOST
+   :   Url of the Remedy Instance. e.g: <http://xx.xx.xx.xx:8008>
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Remedy user’s password
+
+   COMPANY
+   :   The dropdown will populate with values as soon as the auth using the above creds are successful
+
+   APPROVAL USER
+   :   Full name of the user as it appear in Remedy. E.g: userid ‘anish’ would have full name as “Anish Abraham”
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json b/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
new file mode 100644
index 0000000..66bfbef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+  "title": "Image Catalog",
+  "ordinal": 406,
+  "parent_title": "Image Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html",
+  "topic_cluster": {
+    "clustering_title": "Image Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D659229-2AFA-4A63-9194-D128E673AA02",
+        "clustering_title": "Image Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md b/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
new file mode 100644
index 0000000..0e2cf4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D659229-2AFA-4A63-9194-D128E673AA02.md
@@ -0,0 +1,22 @@
+# Image Catalog
+
+This section describes how to upload Bare Metal (BM) operating system images into Morpheus using a configurable image repository. HPE Morpheus supports multiple backend storage options, allowing administrators to centrally manage OS images and reuse them across bare metal provisioning workflows.
+
+Uploaded images are registered under Library > Virtual Images and are made available for bare metal instance provisioning.
+
+## Supported OS Image Sources
+
+HPE Morpheus supports uploading Bare Metal OS images from the following storage backends:
+
+- Local storage on the HPE Morpheus appliance
+- S3-compatible object storage
+- CIFS (Samba) file shares
+- NFS (v3) file shares
+
+Each backend option is configured as a File Share or Storage Bucket and referenced during image upload.
+
+**Subtopics**  
+
+- **[Uploading OS Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html)**
+- **[Windows OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E55D4270-ED77-4161-8712-45824C891713.html)**
+- **[Linux OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json b/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
new file mode 100644
index 0000000..b2a28fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+  "title": "Getting started with HPE Morpheus Enterprise and Azure",
+  "ordinal": 363,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and Azure"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md b/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
new file mode 100644
index 0000000..85a2bfc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.md
@@ -0,0 +1,363 @@
+# Getting started with HPE Morpheus Enterprise and Azure
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with Microsoft Azure public cloud. By the end, you will integrate your first cloud with HPE Morpheus Enterprise, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our [Reddit user community forum](https://www.reddit.com/r/morpheusdata/).
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/latest/getting_started/requirements/requirements.html). In order to provision any new Instances, hosts, or applications (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a community edition license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License. For more, take a look at our community edition [welcome package](https://www.morpheusdata.com/community-welcome).
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to Groups and a user can only access Clouds that are in the Groups to which their roles give them access. More information on HPE Morpheus Enterprise Groups is [here](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html#groups). A deep dive into Groups goes beyond the scope of this guide but it’s often useful to create a Group that contains all Clouds for testing purposes. We will create that group now so that we can add our first Cloud into this Group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+Click SAVE CHANGES. Your Group is now ready to accept Clouds.
+
+![../../_images/1newGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-542A0791-5B19-4A90-A597-CF88E9A0B7F9-high.png)
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be on-prem, public clouds, or even bare metal. In this guide, we will focus on integrating and working with Microsoft Azure public cloud.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the Cloud list page which lists all configured Clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated Azure cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AZURE (PUBLIC)” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, we’re asked to provide Azure-specific details to connect to the cloud. HPE Morpheus Enterprise Azure integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET
+
+![../../_images/2createCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-31D2E874-AE3E-4F65-B514-72258B2A437B-high.png)
+
+### Create App Registration
+
+#### About this task
+
+HPE Morpheus Enterprise authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with HPE Morpheus Enterprise has Owner or Contributor permissions on the specified Subscription.
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one using the steps below. If you already have one you wish to use, continue to the next section.
+
+#### Procedure
+
+1. Log into the Azure portal
+2. Select “Azure Active Directory”
+3. Select “App Registrations”
+4. Select “New Registration” 
+
+   ![../../_images/Default_Directory_App_registrations_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A57114C7-68E3-4BBA-B11D-51BC35609D3C-high.png)
+5. Next, give the app a name, specify Web app / API for the type (default) and enter any URL for the Sign-on URL:
+6. Click Create and your new App Registration will be created. 
+
+   ![../../_images/Register_an_application_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-55330F72-25B5-4408-8A33-43884CBF6D26-high.png)
+
+#### Results
+
+Now that we have our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration in the next section.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+![../../_images/morpheusAppReg_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3DD99466-18E6-40A5-A2C4-63B8D766487E-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select “Certificates & secrets” in the Manage section
+2. Select `+ New client secret` 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FEF1F839-2F89-43AA-A5F8-744B625725F0-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select an expiration duration
+6. Click Add 
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-201809CC-7FE8-42EF-87DE-2FDE9015C0E9-high.png)
+7. Copy the newly-generated client secret value. 
+
+   IMPORTANT
+
+   Copy the client secret value before continuing as it will not be viewable again later.
+
+   ![../../_images/morpheusAppReg_Certificates_secrets_Copy.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-276863D1-39D2-4F67-8A52-511B32010C1B-high.png)
+8. Store/Paste client secret for use later when adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have three of the four credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID which we will gather in the next section.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the Subscriptions section. The search function can help to locate these sections if they aren’t immediately apparent in the UI menu 
+
+   ![../../_images/azuresubscriptionssearch.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AE54CAA0-CE46-424A-ADB0-5F5C2E2521AF-high.png)
+2. In the Subscriptions section, copy the Subscription ID 
+
+   ![../../_images/Subscriptions_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2DA76817-C462-4B49-BCA8-DCBF83CA8860-high.png)
+3. Store/Paste for use as the Subscription ID when adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory existing cloud resources, create resources or remove them.
+
+#### Procedure
+
+1. In the Subscriptions section in Azure, select the Subscription
+2. In the Subscription pane, select “Access Control (IAM)”
+3. Either Click :guilabel`+ Add`, and then “Add Role Assignment” OR simply select “Add a role assignment” 
+
+   ![../../_images/Azure_subscription_1_Access_control_IAM_Microsoft_Azure.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-68F85CA0-5206-4738-8FA9-11A40E6B4277-high.png)
+4. In the right pane, select “Owner” or “Contributor” Role type
+5. Search for the name of the App Registration used for the HPE Morpheus Enterprise integration
+6. Select the App Registration in the search results
+7. Select “Save” 
+
+   ![../../_images/Add_role_assignment_save.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-374258C1-E537-4439-BCE9-9F8918C369E4-high.png)
+
+#### Results
+
+You now have the required credentials and permissions to add an Azure Cloud integration into HPE Morpheus Enterprise. Continue on with the next sections of this guide to complete the integration from the HPE Morpheus Enterprise side.
+
+### Complete the Add Cloud Process in HPE Morpheus Enterprise
+
+If you’ve followed this guide from the start, you will already have a Cloud integration modal open in HPE Morpheus Enterprise UI. If you still need to open that wizard, navigate to Infrastructure > Clouds > + ADD > Azure (Public) and click NEXT. Fill in the following fields with the information gathered in the steps above:
+
+- Subscription ID
+- Tenant ID
+- Client ID
+- Client Secret
+- Location
+- Resource Group
+- Inventory Existing Instances
+- Inventory Level
+- Account Type
+
+Once valid credentials are populated in the appropriate fields, the LOCATION dropdown menu will be populated. Select an available region, this is also a helpful check to ensure you’ve correctly provided working credentials. In addition, we can scope the cloud integration to all resource groups in the region (All) or can select a specific resource group to limit HPE Morpheus Enterprise resource inventorying and creation to just that resource group.
+
+By checking INVENTORY EXISTING INSTANCES, HPE Morpheus Enterprise will automatically onboard existing cloud resources which are scoped to the region and resource group indicated. If this box is checked, we will also need to select either basic inventorying, which syncs name, IP addresses, platform types, power status, and sizing data (storage, CPU, and RAM) OR full (API heavy) inventorying which syncs resource utilization metrics (storage, CPU, and RAM) when available in addition to what we get with basic inventorying.
+
+To move on, expand the “Advanced Options” section.
+
+NOTE
+
+CSP accounts will also need to enter CSP TENANT ID, CSP CLIENT ID, and CSP CLIENT SECRET in the Advanced Options section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first Cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), **COSTING**, **DNS INTEGRATION**, **CMDB**, and **AGENT INSTALL MODE**.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” Groups if you wish to use the Group we configured earlier. Alternatively, you can create a new one here.
+
+![../../_images/3cloudGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0908B711-2897-4E7C-8C95-07D3BE88990B-high.png)
+
+Once you’ve selected or created the Group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new Cloud is now listed on the Cloud list page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the Cloud.
+
+#### Viewing Cloud Inventory
+
+Now that we’ve integrated our first Azure cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the Cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+#### Configuring Resource Pools
+
+With our Azure Cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  Resources tab. In here, we are able to see and control access to the various resource pools that have been configured in Azure. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise if it is not configured as active.
+
+![../../_images/4resourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7380FEF7-F20E-43FE-B217-9597FD1569DE-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any Group we’d like. We can also choose to make some or all of our resource pools available to every Group. Specific resource pools can also be defined as the default for each Group when needed.
+
+![../../_images/5resourcePoolGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BDAD86D8-81F9-4622-BB7D-FE2E1FCEFC1E-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+#### Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “Resources” tab to the “Data Stores” tab on our Cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![../../_images/6dataStore.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-971BB5E6-79F2-4447-9227-2000EAB24BEF-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific Groups. This ensures that the members of each Group are only able to consume the data stores they should have access to.
+
+#### Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all Clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific Cloud detail page so that networks from other Clouds are not shown.
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+Since this guide is focused on working within an Azure cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your Azure cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain Groups or Tenants.
+
+![../../_images/7cloudNetworks.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EB96C871-9B00-4B7B-9BBD-6800427665D5-high.png)
+
+#### Provisioning Your First Instance
+
+At this point, the groundwork is laid and we are ready to attempt our first new provisioning. As a first Instance, we’ll provision an Apache web server to our Azure cloud. HPE Morpheus Enterprise includes a very robust catalog of pre-configured Instance types. We’ll use one of these included catalog items for this guide but you’ll likely also need to prep your own custom images and Instance types to make available to your users. Much more on this can be found elsewhere in HPE Morpheus Enterprise documentation.
+
+Navigate to |ProIns|. If any Instances are currently provisioned, we will see them listed here. To start a new Instance we click + ADD to open the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/8createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-82D93BA5-71D0-4A63-9DBA-C13AE6E3C395-high.png)
+
+First, we’ll specify the Group to provision into which determines the Clouds available. If you’ve followed this guide to this point, you should at least have a Group that houses all of your Clouds which you can select here. This will allow us to select the Azure cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating Instances and available options is [here](https://docs.morpheusdata.com/en/latest/provisioning/instances/instances.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+![../../_images/9configureInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E9D875CD-D6C4-4D20-AD60-767C3A47671E-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your HPE Morpheus Enterprise user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click NEXT to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the Instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the Instance in the list to move to the Instance detail page. For now we will see a progress bar indicating that the Instance is being created and is starting up. The exact amount of time this process will take depends on selections made when provisioning the Instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the Instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+#### Creating Your First Library Item
+
+In the prior section, we manually provisioned our first Instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick Instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a HPE Morpheus Enterprise-provided image, you’ll want to ensure it’s configured. You will not be able to complete this section without selecting an available image. In this example we will use a CentOS image that was previously configured in the HPE Morpheus Enterprise library. If you need to configure your own images prior to starting this section, navigate to Library > Virtual Images and click + ADD. A deeper dive into image prep and virtual image configuration goes beyond the scope of this guide.
+
+Provisionable elements in HPE Morpheus Enterprise combine a Node Type(s), Layout(s), and an Instance Type. The [Overview section](https://docs.morpheusdata.com/en/latest/provisioning/library/library.html#overview) of HPE Morpheus Enterprise docs discusses these objects and how they work together in greater detail. Our first step here will be to create a Node Type which wrap the image itself with additional configuration, templates, and scripts. While not strictly required, creating the Node Type, Instance Type, and then the Layout is often a good workflow for creating Library items. That is the order we will follow in this guide.
+
+Navigate to Library > Blueprints > Node Types and click + ADD
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**: Example Azure CentOS 7
+- **SHORT NAME**: eac7 (Identifies the Node Type in HPE Morpheus Enterprise API/CLI)
+- **VERSION**: 7 (Ensures the correct Node Types are used when tying Layouts with multiple images to the same Instance Type)
+- **TECHNOLOGY**: Azure
+- **VM IMAGE**: Azure-Centos-7
+
+Click SAVE CHANGES
+
+![../../_images/10addNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A92C3DF6-A4AF-4C9E-8DFD-0ADC4CCEDC48-high.png)
+
+With the new Node Type created, we’ll now add a new Instance type which will be accessible from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click + ADD.
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click SAVE CHANGES. You could also provide a description, icon, and category for easier identification from the provisioning wizard later.
+
+![../../_images/11addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E5B46F39-E1FE-4EDF-9C6B-348A60C37A00-high.png)
+
+Now that we’ve created a new Instance type, access it by clicking on the name in the list of custom Instances you’ve created. In my case, I’ve given the name “Example Azure CentOS 7”.
+
+Once we’ve opened the new Instance type, by default, we should be on the “LAYOUTS” tab. Click + ADD LAYOUT. I’ve set the following fields on my example layout:
+
+- **NAME**: Example Azure CentOS 7
+- **VERSION**: 7 (This is the version number of the layout itself, which is labeled 7 in the example)
+- **TECHNOLOGY**: Azure
+- **Nodes**: Select the Node Type we created earlier, if desired you can specify multiple nodes
+
+Click SAVE CHANGES.
+
+![../../_images/12addLayout.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D60CF065-8C8D-4F3F-8068-61523120D1FE-high.png)
+
+At this point we’ve completed the setup work and can now provision the Instance we’ve created to our specifications. Navigate to |ProIns| and click + ADD. From the search bar we can search for the new Instance type we’ve created.
+
+![../../_images/13createCustomInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C1C05D91-5824-4DAD-8132-CF4EF2D46BD6-high.png)
+
+As before, we can select a Group and Cloud to provision this new Instance. Click NEXT. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new Instance type. Select a network and click NEXT. Once again we will also click NEXT through the “AUTOMATION” tab. Finally, click COMPLETE.
+
+As before when we provisioned a pre-existing Instance from the default catalog, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on the configuration and environmental factors but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the provisioning process has completed, open the Instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available, assuming the image and your custom catalog item were configured to seed user accounts and connect back to the HPE Morpheus Enterprise appliance.
+
+#### Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A Task could be a script added directly, scripts or Blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of Task types can be found in the [Automation section](https://docs.morpheusdata.com/en/latest/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a Task, add the Task to a Workflow, and run the Workflow against a new and existing Instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click +NEW INTEGRATION and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus/-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE HPE Morpheus Enterprise AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus/-ansible-example.git.
+
+Click SAVE CHANGES. You’ll now see our new Ansible integration listed among any other configured integrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click + ADD. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+Now that we have a Workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring an instance to your needs. There are a number of other automation types that can be built into your Workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/latest/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+#### Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume Azure public cloud. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/latest/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json b/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
new file mode 100644
index 0000000..33be73f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+  "title": "Requirements",
+  "ordinal": 172,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md b/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
new file mode 100644
index 0000000..3cc440c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-5F72EBA5-E780-4511-8EA0-4ABA11628663.md
@@ -0,0 +1,4 @@
+# Requirements
+
+- Morpheus Role permission Infrastructure: Clusters  >  Full required for Viewing, Creating, Editing and Deleting Clusters.
+- Morpheus Role permission Infrastructure: Clusters  >  Read required for Viewing Cluster list and detail pages.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json b/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
new file mode 100644
index 0000000..25f3627
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+  "title": "Overview",
+  "ordinal": 43,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-607895C8-5308-4A68-9219-1EA342DB9C6C",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md b/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
new file mode 100644
index 0000000..5bd67fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.md
@@ -0,0 +1,9 @@
+# Overview
+
+The HPE Morpheus Enterprise Agent is an important and powerful facet of HPE Morpheus Enterprise as an orchestration tool. Though it is not required, which is one unique capability of our platform versus some of our competitors, it is recommended for use as it brings many benefits. Not only does it provide statistics for the guest operating system and resource utilization, it also brings along with it monitoring and log aggregation capabilities. After an initial brownfield discovery, Users can decide to convert unmanaged VMs to managed.
+
+NOTE
+
+**Agent installation is not required to manage an Instance.** If you don’t have the Agent installed, we make every effort to aggregate stats. These will vary based on the Cloud and can be more limited or less accurate without utilizing HPE Morpheus Enterprise Agent.
+
+The HPE Morpheus Enterprise Agent is very lightweight and secure. It does not open any inbound network ports but rather only opens an outbound connection back to the HPE Morpheus Enterprise appliance over port 443 (HTTPS or WSS protocol). This allows for a bidirectional command bus where instructions can be sent to orchestrate a workload without needing access to things like SSH or WinRM. The tool can even be installed at provision time via technologies like Cloud-Init, such that the HPE Morpheus Enterprise appliance itself doesn’t even need direct network access to the VLAN under which the workload resides. By doing this we address many of the network security concerns that come with the use of an agent while demonstrating its security and analytics benefits. We can even use this statistical data at the guest OS level rather than the hypervisor level to provide extremely precise right-sizing recommendations.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json b/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
new file mode 100644
index 0000000..684357f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+  "title": "Operating Systems",
+  "ordinal": 165,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.html",
+  "topic_cluster": {
+    "clustering_title": "Operating Systems",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-60BD671A-C620-49C7-81EB-56C5197E61C2",
+        "clustering_title": "Operating Systems"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md b/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
new file mode 100644
index 0000000..091835b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-60BD671A-C620-49C7-81EB-56C5197E61C2.md
@@ -0,0 +1,45 @@
+# Operating Systems
+
+Out of the box, many Operating Systems (also referred to as OS types) are seeded into HPE Morpheus Enterprise by default. OS types can be set on Virtual Images when they are created. If you don’t use any other features of OS types described here, they are still useful to set on Virtual Images to ensure only Workflows designed for the platform can be run against workloads provisioned from the image. It can also help ensure certain types of reporting and dashboard metrics are correct.
+
+IMPORTANT
+
+It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration. Read this section in full for complete detail on the use cases for the Operating System construct.
+
+## Permissions
+
+Access to Operating Systems is controlled by the `Library: Operating Systems` feature permission. Access levels are as follows:
+
+- **FULL:** Access to view, create, and edit Operating Systems
+- **READ:** Access to view Operating Systems only
+- **NONE:** No access to the Operating Systems section of the UI
+
+## Use Cases
+
+OS types can primarily be used in one of two use cases. The first is adding your own images to existing OS types. The upshot of doing this is to use built-in Instance Types (for example, the “UBUNTU” Instance Type) while replacing the included default images with your own gold master images for some or all provisioning technologies.
+
+View the existing OS types by navigating to Library > OperatingSystems. Here, a list of all OS types is shown. If this is a brand new appliance or if you’ve never added new Operating Systems, all shown here will be system default OS types. By clicking into any of the OS types for which HPE Morpheus Enterprise currently provides default images, you will see all of the Virtual Images for that OS type and the provisioning technology each image is compatible with.
+
+![../../_images/listOsImages.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-47C7B1DB-2DE5-4A66-B1A9-EAFC3B87601B-high.png)
+
+To add an existing Virtual Image to the currently-selected OS type, click + ADD. Select the image and optionally identify a provisioning technology or even a specific Cloud. When finished, click SAVE.
+
+NOTE
+
+When adding a Virtual Image to an OS type, only Virtual Images that have been saved with the same OS type (Operating System) configuration will be shown in the typeahead list.
+
+![../../_images/addOsImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-84DB6665-2DF9-46C0-9DB1-623644B30196-high.png)
+
+Once images are associated with a built-in OS type, they will be used when the situation warrants (a compatible provisioning target is selected or the correct Cloud is chosen, depending on how the OS type image was configured). It’s important to note that user images are always selected over system images with the same configuration (same associated technology and/or Cloud). Additionally, more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Only one user image can be added per Operating System with an identical technology and/or Cloud configuration and this image would supersede the system image with the same technology and/or Cloud configuration.
+
+The second use case is to add your own Operating System. New Operating Systems can be added by navigating to Library > OperatingSystems and clicking + ADD. OS types can be configured with highly granular detail allowing environments with similar Os types to distinguish them.
+
+![../../_images/createOsType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-436A53AF-DF69-439A-83EE-7F9AB7045072-high.png)
+
+After creating the OS type, any new or existing Virtual Images can be associated to the newly created Operating System (Library > Virtual Images). Once Virtual Images have the Operating System association, you can return to the OS type and complete the association with the Operating System by clicking into the OS type and clicking + ADD.
+
+Once you have a custom Operating System loaded with your own gold master images, the OS type can be used with new Node Types going forward. To see how this works, navigate to Library > Blueprints > Node Types and click + ADD. Change the default technology for a new Node Type from the default “Docker” value to another technology, such as “VMware”. Notice that the option is given to associate the Node Type with either a specific image or with an OS type. By selecting an OS type, the Node Type will select the appropriate image at provision time based on technology and/or Cloud filters.
+
+![../../_images/createNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D7231A7E-44FC-46F2-BF5A-99020D46CF48-high.png)
+
+It’s important to note that more specifically configured images (for example, one with both a technology and a Cloud configured) will be selected over those less specifically configured. Additionally, only one user image can be added per Operating System with an identical technology and/or Cloud configuration.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json b/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
new file mode 100644
index 0000000..58ce7d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+  "title": "Importing HPE ProLiant Bare Metal Servers",
+  "ordinal": 416,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.html",
+  "topic_cluster": {
+    "clustering_title": "Importing HPE ProLiant Bare Metal Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED",
+        "clustering_title": "Importing HPE ProLiant Bare Metal Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md b/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
new file mode 100644
index 0000000..62a9c52
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-61034B56-5E87-4A7F-A15C-79F82D5BC2ED.md
@@ -0,0 +1,31 @@
+# Importing HPE ProLiant Bare Metal Servers
+
+## About this task
+
+Perform the following procedure to import HPE ProLiant Bare Metal Servers:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute, then select the Bare Metal tab.
+2. Click the + Bare Metal button, then select HPE Server.
+3. Select the Group you created earlier from the drop-down list and click Next.   
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-64D4C0D9-B1A4-4257-A316-81069FC4EF3A-high.png)
+4. Enter a Name for the server and click Next.   
+   ![Name](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B361D956-0808-4F91-9D2F-87F840898005-high.png)
+5. Enter the following iLO (Integrated Lights Out) details for the server:
+
+   - iLO IP Address
+   - iLO Username (typically "Administrator")
+   - iLO Administrator Password  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C4D9169E-91C8-4F6D-841A-B8DE6DAB8824-high.png)
+6. Leave the Pre-Provisioned Server option unselected, then click Next.
+7. Click Next to review your host configuration details.
+8. Click Complete to finalize the host creation.   
+   ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DB572274-C1F6-4461-9594-5436E0CBE9AB-high.png)  
+
+   The below image shows list of clouds available.   
+   ![clouds](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8F3FE3ED-1AEB-4AD5-808A-D9C7C54B1308-high.png)
+
+## Results
+
+the HPE ProLiant Bare Metal plugin automatically discovers and records all hardware details from the server using its Integrated Lights Out (iLO) management interface. This discovery process may take a few minutes, depending on the server and network conditions. After completion, the server becomes available (STATUS = `available`) in Morpheus for further provisioning and lifecycle operations.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json b/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
new file mode 100644
index 0000000..17d5810
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+  "title": "Single Node/AIO Appliance Upgrades",
+  "ordinal": 22,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node/AIO Appliance Upgrades",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38",
+        "clustering_title": "Single Node/AIO Appliance Upgrades"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md b/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
new file mode 100644
index 0000000..e36c9cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-616AB588-38EB-4E59-A3F3-BEE8CB610D38.md
@@ -0,0 +1,55 @@
+# Single Node/AIO Appliance Upgrades
+
+IMPORTANT
+
+Only appliances running Morpheus v6.0.0 or higher can upgrade to v8.1.2. Always backup your database before running any upgrade.
+
+The following covers upgrading Single Node or AIO (All-In-One) Appliance configurations.
+
+## Debian / Ubuntu
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on Ubuntu/Debian, download new deb package from My HPE Software Center and transfer it to your application node, stop the morpheus-ui, install the new deb package, then reconfigure.
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
+
+## CentOS / RHEL / Amazon / SLES
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+To upgrade Morpheus running on CentOS, RHEL, Amazon or SLES, download the upgrade package from My HPE Software Center, transfer it to your application node, install the new rpm package, stop the morpheus-ui, reconfigure and then start the morpheus-ui:
+
+```
+```
+sudo morpheus-ctl stop morpheus-ui  
+sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+All services will automatically start during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+
+NOTE
+
+Services will be stopped during package installation and started during the reconfigure process, including the morpheus-ui service. If the reconfigure process is interrupted or fails, the morpheus-ui service may need to be manually started or restarted. In certain situations if another service hangs on starting during reconfigure, run `systemctl restart morpheus-runsvdir` then reconfigure and restart `morpheus-ui` if successful.
+
+After the morpheus-ui service finishes loading, the upgrade is complete.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json b/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
new file mode 100644
index 0000000..b2b2ded
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+  "title": "Script Templates",
+  "ordinal": 161,
+  "parent_title": "Templates",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html",
+  "topic_cluster": {
+    "clustering_title": "Script Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C",
+        "clustering_title": "Script Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md b/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
new file mode 100644
index 0000000..46032ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.md
@@ -0,0 +1,75 @@
+# Script Templates
+
+Scripts are bash and Powershell scripts that can be attached to Node Types to always execute at the selected phase when that Node Type is provisioned, added to Workflows as Library Script Tasks, and/or executed ad-hoc on Instances.
+
+## Creating Scripts
+
+### Procedure
+
+1. Navigate to Library > Templates > Script Templates
+2. Select + ADD
+3. Enter the Following: 
+
+   NAME
+   :   Name of the Script in HPE Morpheus Enterprise
+
+   SCRIPT TYPE
+   :   - Bash
+       - Powershell
+
+   PHASE
+   :   Select which phase the Script will execute when attached to a Node Type. When a script is attached to a Node Type, it will execute according to the selcted phase:
+
+       Start Service
+       :   Any time the Instance action `Start Service` is executed
+
+       Stop Service
+       :   Any time the Instance action `Stop Service` is executed
+
+       Pre-Provision
+       :   - Containers: Script will execute against the container host before the container is provisioned
+           - Virtual Machines: Script will execute before any provision phase Scripts or Tasks
+
+       Provision
+       :   Script will execute once per new Instance node during the provision Phase. Provisioning will not be considered complete until all scripts and tasks in the provisioning phase are completed
+
+           NOTE
+
+           Any Script or Task set to the provision phase will be included in the total provision time and impact success/warn/failure provisioning status messages. As an example, your VM could be up and running but if your Script is in the provision phase and fails, provisioning will be marked as a failure.
+
+           Post-Provision
+           :   Script will execute once per new Instance node after the provision phase is completed. Scripts and Tasks in the Post-Provision phase will show execution status and history, but are not considered part of the provision and do not impact provisioning status.
+
+           Pre-Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The Script will run prior to the deployment file(s) being written
+
+           Deploy
+           :   Script will execute on target Instance any time a deployment is run against the Instance. The script will run after the deployment file(s) are written
+
+           Reconfigure
+           :   Script will execute on target Instance any time a reconfigure is executed against the Instance.
+
+           Teardown
+           :   Script will execute on target Instance upon Instance deletion. Script will execute against target Instance prior to the deletion/removal of resources.
+
+   SCRIPT
+   :   Enter Bash or Powershell script.
+
+       NOTE
+
+       HPE Morpheus Enterprise variables are supported in Library Scripts using `<%= variable.var %>` format
+
+   RUN AS USER
+   :   By default Scripts are execute as `morpheus-node`. To execute as another User, populate `RUN AS USER` and ensure proper user permissions & group access
+
+   SUDO
+   :   Flag `SUDO` if sudo is required to execute the Script
+
+### Results
+
+To attach Scripts and templates that have been added to the Library to a Node Type, start typing the name and then select the script(s) and/or template(s).
+
+- Multiple scripts and templates can be added to a Node Type
+- Scripts and Templates can be added/shared among multiple Node Types
+- The execution phase can be set for Scripts in the Scripts section
+- Search will populate Scripts or Templates containing the characters entered anywhere in their name, not just the first letter(s) of the name
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json b/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
new file mode 100644
index 0000000..478ba6a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+  "title": "Git",
+  "ordinal": 481,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html",
+  "topic_cluster": {
+    "clustering_title": "Git",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A",
+        "clustering_title": "Git"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md b/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
new file mode 100644
index 0000000..9547d74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.md
@@ -0,0 +1,26 @@
+# Git
+
+Git Repository integrations allow integration of public or private Git repositories in Github, GitLab or other services. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Each time code from your repositories is invoked, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Creating an Integration
+
+### About this task
+
+New Git integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need an access code for authentication with private repositories, public repositories can be integrated simply with a URL.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Git repository
+4. Configure the following: 
+
+   - NAME: A friendly name for the Git repository integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, code in this repository will be available for creating automation or other HPE Morpheus Enterprise constructs
+   - DEFAULT BRANCH: The default repository branch from which code should be sourced
+   - USERNAME: For private repositories, enter an account name (such as a Github username)
+   - PASSWORD: For Github and GitLab, password authentication is no longer supported but access tokens should go in this field.
+   - ACCESS TOKEN: Currently an unused field, access tokens should go in the Password field
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json b/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
new file mode 100644
index 0000000..4bd9b4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+  "title": "EKS Clusters",
+  "ordinal": 200,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.html",
+  "topic_cluster": {
+    "clustering_title": "EKS Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6",
+        "clustering_title": "EKS Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md b/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
new file mode 100644
index 0000000..25c485a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63057943-01D8-4FD5-B8CE-CE49A73A93E6.md
@@ -0,0 +1,64 @@
+# EKS Clusters
+
+Provisions a new Elastic Kubernetes Service (EKS) Cluster in target AWS Cloud.
+
+NOTE
+
+EKS Cluster provisioning is different than creating a Kubernetes Cluster type in AWS EC2, which creates EC2 instances and configures Kubernetes, outside of EKS.
+
+HPE Morpheus Enterprise currently supports EKS in the following regions: `us-east-2`, `us-east-1`, `us-west-1`, `us-west-2`, `af-south-1`, `ap-east-1`, `ap-south-1`, `ap-northeast-3`, `ap-northeast-2`, `ap-southeast-1`, `ap-southeast-2`, `ap-northeast-1`, `ca-central-1`, `eu-central-1`, `eu-west-1`, `eu-west-2`, `eu-south-1`, `eu-west-3`, `eu-north-1`, `me-south-1`, `sa-east-1`, `us-gov-east-1`, `us-gov-west-1`
+
+## Create an EKS Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `EKS Cluster`
+4. Populate the following: 
+
+   LAYOUT
+   :   Select server layout for EKS Cluster
+
+   PUBLIC IP
+   :   Subnet Default
+       :   Use AWS configured Subnet setting for Public IP assignment
+
+       Assigned EIP
+       :   Assigned Elastic IP to Controller and Worker Nodes. Requires available EIP’s
+
+   CONTROLLER ROLE
+   :   Select Role for EKS Controller from synced role list
+
+   CONTROLLER SUBNET
+   :   Select subnet placement for EKS Controller
+
+   CONTROLLER SECURITY GROUP
+   :   Select Security Group assignment for EKS Controller
+
+   WORKER SUBNET
+   :   Select Subnet placement for Worker Nodes
+
+   WORKER SECURITY GROUP
+   :   Select Security Group assignment for Worker Nodes
+
+   WORKER PLAN
+   :   Select Service Plan (EC2 Instance Type) for Worker Nodes
+
+   User Config
+   :   CREATE YOUR USER
+       :   Select to create your user on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile)
+
+       USER GROUP
+       :   Select User group to create users for all User Group members on provisioned hosts (requires Linux user config in HPE Morpheus Enterprise User Profile for all members of User Group)
+
+   Advanced Options
+   :   DOMAIN
+       :   Specify Domain for DNS records
+
+       HOSTNAME
+       :   Set hostname (defaults to Instance name)
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json b/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
new file mode 100644
index 0000000..399f8c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+  "title": "User Role Permission Sections",
+  "ordinal": 297,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-633B871A-14AC-42B5-9BDA-8F907433F700.html",
+  "topic_cluster": {
+    "clustering_title": "User Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-633B871A-14AC-42B5-9BDA-8F907433F700",
+        "clustering_title": "User Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md b/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
new file mode 100644
index 0000000..ab36200
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-633B871A-14AC-42B5-9BDA-8F907433F700.md
@@ -0,0 +1,34 @@
+# User Role Permission Sections
+
+Features
+:   Controls User access level for UI sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Groups
+:   Controls User access level for Groups. Groups are not a Multi-Tenant construct, only Groups created in the current Tenant will be visible.
+
+Instance Types
+:   Controls User access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls User access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls User access for each report type in the Reports section (Operations > Reports). The user must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls User access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls user access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters (assuming the Role also has feature access to applicable permissions related to adding Clusters)
+
+VDI Pools
+:   Controls User access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls User access to configured Workflows, including the ability to view, edit, execute, or apply to Library item configurations
+
+Tasks
+:   Controls User access to configured Tasks, including the ability to view, edit, execute, or apply to Workflows
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json b/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
new file mode 100644
index 0000000..a01b87e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+  "title": "Image Builder",
+  "ordinal": 266,
+  "parent_title": "Tools",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html",
+  "topic_cluster": {
+    "clustering_title": "Image Builder",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064",
+        "clustering_title": "Image Builder"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md b/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
new file mode 100644
index 0000000..8c767f9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.md
@@ -0,0 +1,130 @@
+# Image Builder
+
+The Morpheus Image Builder tool creates vmdk, qcow2, vhd and raw Images from scratch. The Image Builder creates a blank VM in VMware, attaches an os iso, executes a boot script on the VM at startup via VNC which calls a preseed script which runs the unattended os installation and configuration. Morpheus then executes an ova export of the completed vmdk to target Storage provider, and converts the image to all other specified formats. The new Virtual Image records are automatically added to Morpheus and the Images are then available for use.
+
+## Requirements
+
+- DHCP must be enabled on the network specified for the VM in Morpheus, and network settings configured for DHCP in Morpheus
+  :   The blank VM must get network configuration via DHCP upon boot. Static IP assignment is not possible.
+- Hypervisor Console must be enabled on the Target Cloud
+  :   Morpheus utilizes VNC to pass the boot script to the VM.
+- VM must be able to reach and resolve the Morpheus appliance url over 443
+  :   The boot script calls to the Morpheus appliance to get the preseed script.
+- Valid Linux iso set for the Virtual Image. Windows is not supported.
+  :   The iso can exist in the target cloud or uploaded to Morpheus
+
+      NOTE
+
+      `cloud-init enabled` must be disabled on the iso Virtual Image settings.
+- Access to target ESXi host(s) over 443 and ESXi hostname dns resolution
+  :   - Same requirement as Hypervisor Console and Image upload/download to/from vCenter.
+- Valid Boot Script
+- Valid Pre-seed script
+- Valid Storage Provider configure for ova export of generated image.
+
+## Sample Scripts
+
+### Sample Boot Script
+
+```
+```
+<wait5><tab> text ks=<%=preseedUrl%><enter>
+```
+```
+
+NOTE
+
+`<%=preseedUrl%>` is a Morpheus variable that will populate with the Morpheus appliance url.
+
+### Sample Preseed Script
+
+```
+```
+# CentOS 7.x kickstart file - ks.cfg  
+#  
+# For more information on kickstart syntax and commands, refer to the  
+# CentOS Installation Guide:  
+# https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/Installation_Guide/sect-kickstart-syntax.html  
+#  
+# For testing, you can fire up a local http server temporarily.  
+# cd to the directory where this ks.cfg file resides and run the following:  
+#    $ python -m SimpleHTTPServer  
+# You don't have to restart the server every time you make changes.  Python  
+# will reload the file from disk every time.  As long as you save your changes  
+# they will be reflected in the next HTTP download.  Then to test with  
+# a PXE boot server, enter the following on the PXE boot prompt:  
+#    > linux text ks=http://<your_ip>:8000/ks.cfg  
+# Required settings  
+lang en_US.UTF-8  
+keyboard us  
+rootpw password  
+authconfig --enableshadow --enablemd5  
+timezone UTC  
+# Optional settings  
+install  
+cdrom  
+user --name=cloud-user --plaintext --password password  
+unsupported_hardware  
+network --bootproto=dhcp  
+firewall --disabled  
+selinux --permissive  
+bootloader --location=mbr --append="biosdevname=0 net.ifnames=0"  
+text  
+skipx  
+zerombr  
+clearpart --all --initlabel  
+autopart --type=plain  
+firstboot --disabled  
+reboot  
+%packages --nobase --ignoremissing --excludedocs  
+openssh-clients  
+# Prerequisites for installing VMware Tools guest additions.  
+# Put in kickstart to ensure first version installed is from install disk,  
+# not latest from a mirror.  
+kernel-headers  
+kernel-devel  
+gcc  
+make  
+perl  
+curl  
+wget  
+bzip2  
+dkms  
+patch  
+net-tools  
+git  
+# Core selinux dependencies installed on 7.x, no need to specify  
+# Other stuff  
+sudo  
+nfs-utils  
+open-vm-tools  
+-fprintd-pam  
+-intltool  
+-biosdevname  
+# unnecessary firmware  
+-aic94xx-firmware  
+-atmel-firmware  
+-b43-openfwwf  
+-bfa-firmware  
+-ipw*-firmware  
+-irqbalance  
+-ivtv-firmware  
+-iwl*-firmware  
+-libertas-usb8388-firmware  
+-ql*-firmware  
+-rt61pci-firmware  
+-rt73usb-firmware  
+-xorg-x11-drv-ati-firmware  
+-zd1211-firmware  
+%end  
+%post  
+# configure vagrant user in sudoers  
+echo "%cloud-user ALL=(ALL) NOPASSWD: ALL" >> /etc/sudoers.d/cloud-user  
+chmod 0440 /etc/sudoers.d/cloud-user  
+cp /etc/sudoers /etc/sudoers.orig  
+sed -i "s/^\(.*requiretty\)$/#\1/" /etc/sudoers  
+# keep proxy settings through sudo  
+echo 'Defaults env_keep += "HTTP_PROXY HTTPS_PROXY FTP_PROXY RSYNC_PROXY NO_PROXY"' >> /etc/sudoers  
+%end
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json b/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
new file mode 100644
index 0000000..4317495
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+  "title": "AzureStorage",
+  "ordinal": 520,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html",
+  "topic_cluster": {
+    "clustering_title": "AzureStorage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C",
+        "clustering_title": "AzureStorage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md b/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
new file mode 100644
index 0000000..5fa5a13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.md
@@ -0,0 +1,30 @@
+# AzureStorage
+
+## To Add Azure Storage
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Storage
+2. Select + ADD
+3. From the New Storage Provider Wizard input the following: 
+
+   Name
+   :   Name of the storage provider.
+
+   Provider Type
+   :   Azure
+
+   Storage Account
+   :   Add Storage Account
+
+   Storage Key
+   :   Add Storage Key
+
+   Share Name
+   :   Add Share Name
+
+   Targets
+   :   - Default Backup Target
+       - Default Deployment Archive Target
+       - Default Virtual Image Store
+4. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json b/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
new file mode 100644
index 0000000..d03dccb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+  "title": "Network Management",
+  "ordinal": 429,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF",
+        "clustering_title": "Network Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md b/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
new file mode 100644
index 0000000..89722a1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-63E00C75-EF17-4EB1-9569-78FE6A0AADDF.md
@@ -0,0 +1,16 @@
+# Network Management
+
+At a high level, there are two network modes in which a cloud can be configured to operate:
+
+- Unmanaged network mode (`Unmanaged`).
+- Managed network mode (`ArubaCX-Int`).
+
+Network modes are created during cloud creation.
+
+![Network Mode](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-876273B4-9A6A-4398-B541-2C7FEE1F1A25-high.png)
+
+**Subtopics**  
+
+- **[Unmanaged Networks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1741A126-636E-4A96-812C-48A8B7A25E88.html)**
+- **[Managed Networks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html)**
+- **[Networks Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json b/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
new file mode 100644
index 0000000..0e6e13a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+  "title": "Uninstall HPE Morpheus Enterprise Agent",
+  "ordinal": 49,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html",
+  "topic_cluster": {
+    "clustering_title": "Uninstall HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D",
+        "clustering_title": "Uninstall HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md b/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
new file mode 100644
index 0000000..fb06012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.md
@@ -0,0 +1,37 @@
+# Uninstall HPE Morpheus Enterprise Agent
+
+## Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+## Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json b/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
new file mode 100644
index 0000000..74bd9c5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+  "title": "Add NSX load balancer",
+  "ordinal": 502,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.html",
+  "topic_cluster": {
+    "clustering_title": "Add NSX load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A",
+        "clustering_title": "Add NSX load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md b/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
new file mode 100644
index 0000000..03134d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6427BABA-5ECA-4316-905D-0DC0C8FB0D8A.md
@@ -0,0 +1,34 @@
+# Add NSX load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **NSX**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![NSX lb](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D2AD8017-CB76-4284-91AE-2514167985CA-high.png)
+4. Configure the following parameters: 
+
+   NSX
+   :   From the drop-down list, select the configured NSX load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   OPTIONS
+   :   **ENABLED**: Select this option to enable the NSX for the integration.
+   :   **ADMIN STATE**: Select this option to switch to admin state.
+
+   SIZE
+   :   From the drop-down list, select the size of the NSX to be provisioned.
+
+   TIER-1 GATEWAYS
+   :   From the drop-down list, select the Tier-1 gateway.
+
+   LOG LEVEL
+   :   From the drop-down list, select the log level for the logs.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json b/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
new file mode 100644
index 0000000..9775c2f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+  "title": "Managing Apps",
+  "ordinal": 89,
+  "parent_title": "Apps",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html",
+  "topic_cluster": {
+    "clustering_title": "Managing Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1",
+        "clustering_title": "Managing Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md b/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
new file mode 100644
index 0000000..dc7be67
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.md
@@ -0,0 +1,85 @@
+# Managing Apps
+
+## App Status
+
+App Status is determined by the status of the Instances within the App or by the DELETE action. All Instances in an App must be in ‘Running’ status for the App status to equal ‘Running’.
+
+Table 1. App Statuses
+
+     | Status Icon | App Status | Status Reason |
+| --- | --- | --- |
+| ../../_images/running_icon.svg | Running | All Instance Statuses = Running |
+| ../../_images/failed_icon.svg | Failed | Any Instance Status = Failed |
+| ../../_images/pending_icon.svg | Pending | Any Instance Status = Pending |
+| ../../_images/pendingRemoval_icon.svg | Pending Removal | Any Instance Status = Pending Removal |
+| ../../_images/deploying_icon.svg | Provisioning | Any Instance Status = Provisioning |
+| ../../_images/removing_icon.svg | Removing | The DELETE action was trigger on the App |
+| ../../_images/unknown_icon.svg | Unknown | Any Instance Status = Unknown, or the App is empty |
+
+## Editing an App
+
+### About this task
+
+The EDIT action allows permissioned users to update an Apps metadata, Environment, Group and Owner.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select EDIT
+4. Update the following 
+
+   NAME
+   :   App Name
+
+   DESCRIPTION
+   :   App Description
+
+   ENVIRONMENT
+   :   App Environment
+
+   GROUP
+   :   App Group assignment
+
+   OWNER
+   :   User assigned as Owner of the App
+5. Select SAVE CHANGES
+
+## Deleting an App
+
+### About this task
+
+The DELETE action allows permissioned users to delete an App and, by default, all Instances within the App.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select DELETE
+4. The DELETE APP? confirmation modal will be displayed: 
+
+   Remove Instances
+   :   Deletes all Instances associated with the App - Enabled by Default
+
+   Preserve Backups
+   :   Preserves Backups of the Instances associated with the App - Disabled by Default
+
+   Preserve Volumes
+   :   Preserves Storage Volumes of the Instances associated with the App - Disabled by Default
+
+   Force Delete
+   :   Forces deletion of the App - Required when any Instances associated with the App are in “provisioning” state - WARNING Force deleting may cause orphaned infrastructure or resources. - Disabled by Default
+5. Select DELETE to proceed with deleting the App, or CANCEL to abort the delete action.
+
+## Exporting Configuration JSON
+
+### About this task
+
+To export an App Blueprint as JSON:
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select an App from the list to view the App detail page
+3. Select ACTIONS > Export
+4. The App export file will be downloaded to your computer as `{app_name}.json`
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json b/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
new file mode 100644
index 0000000..52583a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+  "title": "Compute Management",
+  "ordinal": 400,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.html",
+  "topic_cluster": {
+    "clustering_title": "Compute Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3",
+        "clustering_title": "Compute Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md b/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
new file mode 100644
index 0000000..c667508
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-65714C62-EFBC-4119-B8C6-1724D2B89FC3.md
@@ -0,0 +1,22 @@
+# Compute Management
+
+The topic section describes how HPE Morpheus Enterprise orchestrates on-premises and HPE BMaaS Cloud resources. It covers the end-to-end lifecycle for physical servers, including installation, cloud configuration, on-boarding, and workload migration.
+
+Administrators perform the following tasks:
+
+- Define a Bare Metal Cloud
+- Configure unmanaged networks and resource pools
+- Import HPE ProLiant servers for centralized visibility
+- Manage greenfield (new) and brownfield (existing) server deployment
+- Convert Pre-Provisioned servers into managed HPE Morpheus instances
+
+Administrators use these procedures to enable consistent provisioning, lifecycle management, and governance for HPE ProLiant infrastructure within HPE Morpheus.
+
+**Subtopics**  
+
+- **[Adding HPE BMaaS Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0F66BE6C-8428-458C-BF0B-CD7C075ACC50.html)**
+- **[Creating an HPE BMaaS Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html)**
+- **[Creating Resource Pools](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html)**
+- **[Image Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html)**
+- **[Provisioning a New Server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-016909A4-5AF9-4DE7-8088-DB62BBC6B00C.html)**
+- **[Importing Pre-Provisioned Server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json b/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
new file mode 100644
index 0000000..ab2e976
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+  "title": "Morpheus Agent OS Support",
+  "ordinal": 45,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent OS Support",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184",
+        "clustering_title": "Morpheus Agent OS Support"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md b/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
new file mode 100644
index 0000000..f922ab4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.md
@@ -0,0 +1,119 @@
+# Morpheus Agent OS Support
+
+Table 1.
+
+           | Name | Bit Count | Category | Code | OS Family | OS Version | Platform | Vendor | Install Agent? |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Almalinux Linux 8 64‐bit | 64 | almalinux | almalinux.8.64 | almalinux | 8 | linux | almalinux | Yes |
+| Almalinux Linux 9 64‐bit | 64 | almalinux | almalinux.9.64 | almalinux | 9 | linux | almalinux | Yes |
+| amazon linux 2 64‐bit | 64 | amazonlinux | amazonlinux.2.64 | centos | 2 | linux | amazon | Yes |
+| centOS | 32 | centos | cent | rhel | all | linux | centos | Yes |
+| centOS 6 | 32 | centos | cent.6 | rhel | 6 | linux | centos | Yes |
+| centOS 6 64‐bit | 64 | centos | cent.6.64 | rhel | 6 | linux | centos | Yes |
+| centOS 64‐bit | 64 | centos | cent.64 | rhel | all | linux | centos | Yes |
+| centOS 7 | 32 | centos | cent.7 | rhel | 7 | linux | centos | Yes |
+| centOS 7 64‐bit | 64 | centos | cent.7.64 | rhel | 7 | linux | centos | Yes |
+| centOS 8 | 32 | centos | cent.8 | rhel | 8 | linux | centos | Yes |
+| centOS 8 64‐bit | 64 | centos | cent.8.64 | rhel | 8 | linux | centos | Yes |
+| centOS 8 Stream 64‐bit | 64 | centos | cent.8.stream.64 | rhel | 8 | linux | centos | Yes |
+| centOS 9 64‐bit | 64 | centos | cent.9.64 | rhel | 9 | linux | centos | Yes |
+| debian | 32 | debian | debian | debian | all | linux | debian | Yes |
+| debian 10 64‐bit | 64 | debian | debian.10.64 | debian | 10 | linux | debian | Yes |
+| debian 10.9 64‐bit | 64 | debian | debian.10.9.64 | debian | 10 | linux | debian | Yes |
+| debian 11 64‐bit | 64 | debian | debian.11.64 | debian | 11 | linux | debian | Yes |
+| debian 6 | 32 | debian | debian.6 | debian | 6 | linux | debian | Yes |
+| debian 6 64‐bit | 64 | debian | debian.6.64 | debian | 6 | linux | debian | Yes |
+| debian 64‐bit | 64 | debian | debian.64 | debian | all | linux | debian | Yes |
+| debian 7 | 32 | debian | debian.7 | debian | 7 | linux | debian | Yes |
+| debian 7 64‐bit | 64 | debian | debian.7.64 | debian | 7 | linux | debian | Yes |
+| debian 8 | 32 | debian | debian.8 | debian | 8 | linux | debian | Yes |
+| debian 8 64‐bit | 64 | debian | debian.8.64 | debian | 8 | linux | debian | Yes |
+| debian 9.13 64‐bit | 64 | debian | debian.9.13.64 | debian | 9 | linux | debian | Yes |
+| debian 9.4 64‐bit | 64 | debian | debian.9.4.64 | debian | 9 | linux | debian | Yes |
+| ESXi | 64 | esxi | esxi | NULL |  | ESXi | vmware | No |
+| ESXi 4 | 64 | esxi | esxi.4 | NULL | 4 | ESXi | vmware | No |
+| ESXi 5 | 64 | esxi | esxi.5 | NULL | 5 | ESXi | vmware | No |
+| ESXi 6 | 64 | esxi | esxi.6 | NULL | 6 | ESXi | vmware | No |
+| ESXi 7 | 64 | esxi | esxi.7 | NULL | 7 | ESXi | vmware | No |
+| ESXi 8 | 64 | esxi | esxi.8 | NULL | 8 | ESXi | vmware | No |
+| fedora | 32 | fedora | fedora | NULL | all | linux | fedora | Yes |
+| fedora 64‐bit | 64 | fedora | fedora.64 | NULL | all | linux | fedora | Yes |
+| linux | 64 | linux | linux | NULL | all | linux | linux | Yes |
+| linux 32‐bit | 32 | linux | linux.32 | NULL | all | linux | linux | No |
+| linux 64‐bit | 64 | linux | linux.64 | NULL | all | linux | linux | No |
+| mac os | 64 | mac | mac | darwin | all | osx | apple | Yes |
+| opensuse | 32 | opensuse | opensuse.32 | suse | all | linux | opensuse | Yes |
+| opensuse 15 64‐bit | 64 | opensuse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| opensuse 64‐bit | 64 | opensuse | opensuse.64 | suse | all | linux | opensuse | Yes |
+| oracle enterprise | 32 | oracle | oracle.32 | NULL | all | linux | oracle | Yes |
+| oracle enterprise 64‐bit | 64 | oracle | oracle.64 | NULL | all | linux | oracle | Yes |
+| oracle linux 64‐bit | 64 | oracle | oracle.linux.64 | NULL | all | linux | oracle | Yes |
+| oracle vm server | 64 | oracle | ovs | NULL | all | linux | oracle | No |
+| other 32‐bit | 32 | other | other.32 | NULL | all | other | other | No |
+| other 64‐bit | 64 | other | other.64 | NULL | all | other | other | No |
+| redhat | 32 | redhat | redhat | rhel | all | linux | redhat | Yes |
+| redhat 6 | 32 | redhat | redhat.6 | rhel | 6 | linux | redhat | Yes |
+| redhat 6 64‐bit | 64 | redhat | redhat.6.64 | rhel | 6 | linux | redhat | Yes |
+| redhat 64‐bit | 64 | redhat | redhat.64 | rhel | all | linux | redhat | Yes |
+| redhat 7 | 32 | redhat | redhat.7 | rhel | 7 | linux | redhat | Yes |
+| redhat 7 64‐bit | 64 | redhat | redhat.7.64 | rhel | 7 | linux | redhat | Yes |
+| redhat 8 | 32 | redhat | redhat.8 | rhel | 8 | linux | redhat | Yes |
+| redhat 8 64‐bit | 64 | redhat | redhat.8.64 | rhel | 8 | linux | redhat | Yes |
+| redhat 9 64‐bit | 64 | redhat | redhat.9.64 | rhel | 9 | linux | redhat | Yes |
+| Rocky Linux 8 | 32 | rocky | rocky.8 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 8 64‐bit | 64 | rocky | rocky.8.64 | rocky | 8 | linux | rocky | Yes |
+| Rocky Linux 9 64‐bit | 64 | rocky | rocky.9.64 | rocky | 9 | linux | rocky | Yes |
+| solaris | 32 | solaris | solaris.32 | NULL | all | solaris | solaris | No |
+| solaris 64‐bit | 64 | solaris | solaris.64 | NULL | all | solaris | solaris | No |
+| suse enterprise | 32 | suse | suse | suse | all | linux | suse | Yes |
+| suse enterprise 11 | 32 | suse | suse.11 | suse | 11 | linux | suse | Yes |
+| suse enterprise 11 64‐bit | 64 | suse | suse.11.64 | suse | 11 | linux | suse | Yes |
+| suse enterprise 12 | 32 | suse | suse.12 | suse | 12 | linux | suse | Yes |
+| suse enterprise 12 64‐bit | 64 | suse | suse.12.64 | suse | 12 | linux | suse | Yes |
+| suse enterprise 15 | 32 | suse | suse.15 | suse | 15 | linux | suse | Yes |
+| suse enterprise 15 64‐bit | 64 | suse | suse.15.64 | suse | 15 | linux | suse | Yes |
+| suse enterprise 64‐bit | 64 | suse | suse.64 | suse | all | linux | suse | Yes |
+| ubuntu | 32 | ubuntu | ubuntu | debian | all | linux | canonical | Yes |
+| ubuntu 12 | 32 | ubuntu | ubuntu.12.04 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 12 64‐bit | 64 | ubuntu | ubuntu.12.04.64 | debian | 12.04 | linux | canonical | Yes |
+| ubuntu 13 | 32 | ubuntu | ubuntu.13.10 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 13 64‐bit | 64 | ubuntu | ubuntu.13.10.64 | debian | 13.10 | linux | canonical | Yes |
+| ubuntu 14 | 32 | ubuntu | ubuntu.14.04 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 14 64‐bit | 64 | ubuntu | ubuntu.14.04.64 | debian | 14.04 | linux | canonical | Yes |
+| ubuntu 15 | 32 | ubuntu | ubuntu.15.10 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 15 64‐bit | 64 | ubuntu | ubuntu.15.10.64 | debian | 15.10 | linux | canonical | Yes |
+| ubuntu 16 | 32 | ubuntu | ubuntu.16.04 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 16 64‐bit | 64 | ubuntu | ubuntu.16.04.64 | debian | 16.04 | linux | canonical | Yes |
+| ubuntu 18.04 | 32 | ubuntu | ubuntu.18.04 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 18.04 64‐bit | 64 | ubuntu | ubuntu.18.04.64 | debian | 18.04 | linux | canonical | Yes |
+| ubuntu 20.04 | 32 | ubuntu | ubuntu.20.04 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 20.04 64‐bit | 64 | ubuntu | ubuntu.20.04.64 | debian | 20.04 | linux | canonical | Yes |
+| ubuntu 22.04 64‐bit | 64 | ubuntu | ubuntu.22.04.64 | debian | 22.04 | linux | canonical | Yes |
+| ubuntu 24.04 64‐bit | 64 | ubuntu | ubuntu.24.04.64 | debian | 24.04 | linux | canonical | Yes |
+| ubuntu 64‐bit | 64 | ubuntu | ubuntu.64 | debian | all | linux | canonical | Yes |
+| unknown | 64 | other | unknown | NULL | all | unknown | unknown | No |
+| windows | 64 | windows | windows | windows | all | windows | microsoft | Yes |
+| windows 10 | 32 | windows | windows.10 | windows | 10 | windows | microsoft | Yes |
+| windows 10 64‐bit | 64 | windows | windows.10.64 | windows | 10 | windows | microsoft | Yes |
+| windows 11 | 32 | windows | windows.11 | windows | 11 | windows | microsoft | Yes |
+| windows 11 64‐bit | 64 | windows | windows.11.64 | windows | 11 | windows | microsoft | Yes |
+| windows 7 | 32 | windows | windows.7 | windows | 7 | windows | microsoft | Yes |
+| windows 7 64‐bit | 64 | windows | windows.7.64 | windows | 7 | windows | microsoft | Yes |
+| windows 8 | 32 | windows | windows.8 | windows | 8 | windows | microsoft | No |
+| windows 8 64‐bit | 64 | windows | windows.8.64 | windows | 8 | windows | microsoft | Yes |
+| windows server 2003 | 64 | windows | windows.server.2003 | windows | 2003 | windows | microsoft | No |
+| windows server 2008 | 64 | windows | windows.server.2008 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2008 R2 | 64 | windows | windows.server.2008.r2 | windows | 2008 | windows | microsoft | Yes |
+| windows server 2012 | 64 | windows | windows.server.2012 | windows | 2012 | windows | microsoft | Yes |
+| windows server 2016 | 64 | windows | windows.server.2016 | windows | 2016 | windows | microsoft | Yes |
+| windows server 2019 | 64 | windows | windows.server.2019 | windows | 2019 | windows | microsoft | Yes |
+| windows server 2022 | 64 | windows | windows.server.2022 | windows | 2022 | windows | microsoft | Yes |
+| windows server 2025 | 64 | windows | windows.server.2025 | windows | 2025 | windows | microsoft | Yes |
+| xen server 6.1 | 64 | xen | xenserver.6.1 | xen | 6.1 | linux | xen | No |
+| xen server 6.2 | 64 | xen | xenserver.6.2 | xen | 6.2 | linux | xen | No |
+| xen server 6.5 | 64 | xen | xenserver.6.5 | xen | 6.5 | linux | xen | No |
+| xen server 7.0 | 64 | xen | xenserver.7.0 | xen | 7.0 | linux | xen | No |
+
+NOTE
+
+Other Operating System types may be supported but are not tested.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json b/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
new file mode 100644
index 0000000..486fb5a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+  "title": "Known Limitations and Operational Considerations",
+  "ordinal": 457,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.html",
+  "topic_cluster": {
+    "clustering_title": "Known Limitations and Operational Considerations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-663434D4-E8EB-4468-992C-107B9FD4AC30",
+        "clustering_title": "Known Limitations and Operational Considerations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md b/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
new file mode 100644
index 0000000..ae31592
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-663434D4-E8EB-4468-992C-107B9FD4AC30.md
@@ -0,0 +1,7 @@
+# Known Limitations and Operational Considerations
+
+Table 1. Known Limitations and Operational Considerations
+
+        | S.No | Topic | Description | Impact | Applicability | Operational Guidance |
+| --- | --- | --- | --- | --- | --- |
+| 1 | SATA Controller Initialization Delay During Importing HPE ProLiant Bare Metal Servers | During the bare-metal server import and hardware discovery process, if a server has one or more SATA controllers with no attached SATA disks, the system waits a minimum of **5 minutes per SATA controller** before continuing.  The wait time is cumulative and applies to each SATA controller detected without attached disks.  This behavior occurs during the initial hardware probing phase, before the server becomes available for provisioning in Morpheus. | 1. Increased time to complete bare-metal server discovery, import, and provisioning. 2. Delay proportional to the number of SATA controllers present without disks. 3. No impact once the server import process has completed. 4. No impact when SATA controllers have SATA disks attached. | This condition is typically observed in **lab** or **evaluation** environments where SATA controllers may be present but not populated with disks.  Standard **production** deployments are not expected to include unused SATA controllers. | Disabling an Embedded SATA Controller (HPE ProLiant)   1. Reboot the server. 2. Press **F9** to enter **System Utilities**. 3. Navigate to:  **System Configuration** → **BIOS/Platform Configuration (RBSU)** → **PCIe Device Configuration**. 4. For **each** embedded SATA controller that is not in use:     - Select the controller (for example, Embedded SATA Controller #1).    - Change the **SATA Device Disable** from **Auto** to **Disabled**. 5. Press F12 to save the changes and exit, followed by reboot. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json b/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
new file mode 100644
index 0000000..14b4db4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+  "title": "Zerto",
+  "ordinal": 386,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-66740846-A143-48D1-80FF-7314D86BE61A.html",
+  "topic_cluster": {
+    "clustering_title": "Zerto",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-66740846-A143-48D1-80FF-7314D86BE61A",
+        "clustering_title": "Zerto"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md b/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
new file mode 100644
index 0000000..eaceddf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-66740846-A143-48D1-80FF-7314D86BE61A.md
@@ -0,0 +1,56 @@
+# Zerto
+
+![Morpheus and Zerto Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6A463450-FFCB-4806-BD66-0A0EE909F08D-high.png)
+
+## Overview
+
+By integrating HPE Morpheus Enterprise and Zerto, HPE Morpheus Enterprise will automatically bring in your pre-existing Zerto replication groups as well as allow you to create and edit replication groups from within HPE Morpheus Enterprise UI. Additionally, the Zerto integration can be set as the replication provider to existing compatible Clouds (such as VMware vCenter Clouds) to allow new workloads to be added to replication groups. If needed, new replication groups can also be created at provision time with the newly provisioned VMs added to them. The Zerto integration detail page also provides summary details for the integration as well as listing out replications and replication sites which are available to use with replication groups.
+
+## Adding a Zerto Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Zerto
+4. Fill in the following: 
+
+   Name
+   :   A friendly name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled and made available for consumption in HPE Morpheus Enterprise
+
+   API URL
+   :   API URL for the Zerto Virtual Manager (ex. `API URL: https://xx.xx.xx.xx:9669`)
+
+   Username
+   :   Username for an admin Zerto service account
+
+   Password
+   :   Password for the provided user (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Restricts integration access to users in the current Tenant (subject to additional RBAC settings)
+
+           Public
+           :   The integration is accessible to all Tenants (option available to Master Tenant users only)
+5. Once complete, click SAVE
+
+### Results
+
+NOTE
+
+In addition to manually entering username and password credentials in this modal, users also have the option to use a stored username/password credential set, or manually enter credentials and have them stored for later use in the HPE Morpheus Enterprise secure credential store. See the CREDENTIALS configuration in the add/edit integration modal for all of these options.
+
+Once the integration is created, you can click into the integration detail page to see existing replication groups, summary data, and other information about replications and replication sites.
+
+## Setting a Replication Provider
+
+With the integration created, Zerto can be added as the replication provider for compatible Clouds. Edit an existing Cloud (click the EDIT button from the Cloud detail page) and expand the Advanced Options section. In the dropdown for Replication Provider, select the Zerto integration. Finally, save the Cloud to commit the changes.
+
+With the Cloud and the Zerto integration associated, you will now see additional replication options at provision time. When provisioning to the associated Cloud in the future, expand the Replication section from within the AUTOMATION tab of the provisioning wizard. Here you have the option of adding newly provisioned VMs to an existing replication group. Additionally, you may also create a brand new replication group from within the provisioning wizard itself if a new group is needed.
+
+![../../_images/zertoProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DC7C1357-FBBB-469E-A3EC-D2EFAA786192-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json b/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
new file mode 100644
index 0000000..b9ad933
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+  "title": "Building Catalog Workflows",
+  "ordinal": 142,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html",
+  "topic_cluster": {
+    "clustering_title": "Building Catalog Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135",
+        "clustering_title": "Building Catalog Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md b/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
new file mode 100644
index 0000000..7fd0896
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.md
@@ -0,0 +1,34 @@
+# Building Catalog Workflows
+
+NOTE
+
+API usage for Catalog Items with Forms is not yet supported. If planning to use the API or CLI to order Catalog Items you should not use Forms on Catalog Items until it is supported.
+
+From the Catalog Items List Page (Library > Blueprints > Catalog Items), click ADD. From the dropdown menu, select Workflow. The modal window will appear to configure and add a new catalog Workflow.
+
+Configure the following:
+
+- **NAME:** A friendly name for the catalog item in HPE Morpheus Enterprise
+- **CODE:** An optional shortcode for coded naming schemes or programmatic reference
+- **DESCRIPTION:** An optional description identifying the catalog item
+- **CATEGORY:** Select an existing category or enter a new one. When provisioning from the catelog, items can be filtered by category
+- **LABELS:** A comma-separated list of descriptive strings which can be used to categorize the Catalog Item. The Catalog Items list view page can be filtered by labels to make them easier to find
+- **ENABLED:** When checked, this Workflow item will be available for selection in the Service Catalog
+- **DISABLE AUTO PRICE:** When marked, price estimates are no longer refreshed with every field change at the time this Catalog Item is ordered. For some workloads with heavy Configuration-phase Tasks this may improve performance of the order page
+- **FEATURED:** When checked, this catalog item will be given special visibility in the Service Catalog Persona view
+- **VISIBILITY:** Set to private to keep the catalog item available only to users in the current Tenant. Master Tenant administrators may set catalog items to public to make them viewable and usable by Subtenant users
+- **LOGO:** Select or upload a logo to be associated with this catalog item
+- **DARK LOGO:** If desired, set an alternate logo for use when the dark theme is applied to the HPE Morpheus Enterprise appliance
+- **WORKFLOW:** Select an existing Workflow to be associated with this Catalog Item, new Workflows are created in Library > Automation
+- **CONTEXT:** Optionally restrict users to a specific target context, Instance, Server, or None
+- **CONFIG:** Enter an optional custom config JSON body. See [Workflows documentation](https://docs.morpheusdata.com/en/latest/library/automation/workflows.html#allow-custom-config) for a formatting example
+- **CONTENT:** Optionally include documentation content for this Catalog Item. Markdown-formatted text is accepted and displayed appropriately when the item is ordered from the Service Catalog. A new Catalog Item-type Wiki entry will also be added containing this information.
+- **FORM TYPE:** Choose whether a Form or individual Inputs should be used to set the user options at provisioning time. See [Forms documentation](https://docs.morpheusdata.com/en/latest/library/options/options.html#forms) for complete details on creating Forms.
+- **FORM:** If the Form Type of “Form” is selected, choose the pre-existing Form which should be associated with the Catalog Item
+- **INPUTS:** If the Form Type of “Inputs” is selected, choose the pre-existing Inputs which should be associated with the Catalog Item
+
+TIP
+
+There are a number of advantages to using Forms over Inputs. See the section above on using Forms with Catalog Items for a complete description on how they are used and the advantages to using them.
+
+Once done, click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json b/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
new file mode 100644
index 0000000..cadcd2b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+  "title": "Automation",
+  "ordinal": 103,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html",
+  "topic_cluster": {
+    "clustering_title": "Automation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6779EFD7-BD52-4678-AC19-30AE09F26217",
+        "clustering_title": "Automation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md b/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
new file mode 100644
index 0000000..4d06f4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.md
@@ -0,0 +1,13 @@
+# Automation
+
+Library  >  Automation
+
+The Automation section is composed of Tasks and Workflows. Tasks can be scripts added directly, scripts and blueprints from the Library section, recipes, playbooks, puppet agent installs, or http (api) calls. These Tasks are are combined into workflows, which can be selected to run at provision time or executed on existing instances via Actions  >  Run Workflow.
+
+**Subtopics**  
+
+- **[Tasks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html)**
+- **[Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-48ED6B2F-2E0B-491F-A497-139DD9B91284.html)**
+- **[Scale Thresholds](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html)**
+- **[Power Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html)**
+- **[Execute Scheduling](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json b/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
new file mode 100644
index 0000000..e52a30b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+  "title": "User Settings",
+  "ordinal": 334,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md b/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
new file mode 100644
index 0000000..faef8a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.md
@@ -0,0 +1,14 @@
+# User Settings
+
+The fields included in this section are described below. By entering any new values in these fields and clicking SAVE, the existing value will be overwritten.
+
+- **Theme:** Choose from a selection of themes including default and dark mode themes. The Theme setting is not available when Whitelabeling is enabled on the current Tenant
+- **Username:** Your HPE Morpheus Enterprise username
+- **First Name:** Your first name (together with Last Name makes up your display name)
+- **Last Name:** Your last name (together with First Name makes up your display name)
+- **Email:** Your email address
+- **Password:** Enter a value and save changes to update your password. The value in the Confirm field below must match
+- **Confirm:** Confirm the new password you’ve entered
+- **RECEIEVE NOTIFICATIONS** Determines if provisioning notifications are emailed to this User
+
+![../../_images/user_settings500.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1A22C9CD-F310-4AEF-A818-55C0954C9C55-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json b/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
new file mode 100644
index 0000000..e8d4b62
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+  "title": "Cluster Permissions",
+  "ordinal": 173,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Permissions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733",
+        "clustering_title": "Cluster Permissions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md b/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
new file mode 100644
index 0000000..160cd6b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-690DD9D4-9114-4EE1-97F1-254D7B67B733.md
@@ -0,0 +1,6 @@
+# Cluster Permissions
+
+- Cluster Permissions
+  :   Each Cluster has Group, Tenant and Service Plan access permissions settings (“MORE” > Permissions on the Clusters list page).
+- Namespace Permissions
+  :   Individual Namespaces also have Group, Tenant and Service Plan access permissions settings
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json b/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
new file mode 100644
index 0000000..6640526
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+  "title": "Convert to Provisioned Node",
+  "ordinal": 421,
+  "parent_title": "Import Pre-Provisioned Servers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html",
+  "topic_cluster": {
+    "clustering_title": "Convert to Provisioned Node",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF",
+        "clustering_title": "Convert to Provisioned Node"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md b/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
new file mode 100644
index 0000000..a7ab110
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.md
@@ -0,0 +1,20 @@
+# Convert to Provisioned Node
+
+## About this task
+
+Perform the following to convert to Managed or create a new instance:
+
+## Procedure
+
+1. After the server is imported, go to Infrastructure > Compute > Bare Metal.
+2. Select the imported server.
+3. Click Convert to Managed. ![Convert to Managed](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3462CBDA-30E9-451B-9EDE-E68FA70DDA5F-high.png)
+4. Confirm the server details and click Execute. ![Convert to Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8CCF2394-D2E1-4815-AEC2-8E706E61732D-high.png)
+
+   NOTE
+
+   Use the same OS credentials that were provided during the import step.
+
+## Results
+
+The Convert to Managed action creates a new instance, makes the selected server a fully provisioned node, and adds it to the new instance. It creates the association of this server with networks and volumes in HPE Morpheus, as present in the network switches and the storage array, respectively. In addition, it creates the association of the VLAN interfaces with the IP addresses on the host OS on the server.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json b/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
new file mode 100644
index 0000000..aa8e719
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+  "title": "Instance Types",
+  "ordinal": 128,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C",
+        "clustering_title": "Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md b/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
new file mode 100644
index 0000000..8d58e4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B0F9AE1-F0B9-4E4A-A444-833E9A4BA49C.md
@@ -0,0 +1,60 @@
+# Instance Types
+
+Adding an Instance Type creates a new Library item category. Multiple Layouts can be added to an Instance Type and these Layouts can have different Nodes attached. The Instance provisioning wizard will present the Layout options compatible with the selected Cloud. If Cloud selection is turned off, all Layouts will be presented for all Cloud types accessible by the User.
+
+![../../_images/instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C56262F7-FB82-4802-A8D8-DEE2D9FE3DB1-high.png)
+
+Name
+:   Name of the Instance Type in the provisioning Library
+
+Code
+:   A useful shortcode for provisioning naming schemes and export reference
+
+Description
+:   The description of the Instance Type shown in the Provisioning Library. (255 characters max)
+
+Category
+:   For filtering in Instance sections and provisioning wizard
+
+    - Web
+    - SQL
+    - NoSQL
+    - Apps
+    - Network
+    - Messaging
+    - Cache
+    - OS
+    - Cloud
+    - Utility
+
+Icon
+:   An identifiable icon to display in-line with your Instance Type in the provisioning wizard (Suggested dimensions: 150 x 51)
+
+Visibility
+:   - Private: Only accessible by assigned Accounts/Tenants
+    - Public: Accessible by all Accounts/Tenants
+
+Inputs
+:   Custom options presented to the user at provision time, Inputs are also created and stored in Morpheus Library
+
+Price Sets
+:   Associate a Price Set with the Instance Type, Price sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Instance Types become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Instance Type. If this Instance Type is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Instance Type Price Sets Demo**
+
+Environment Prefix
+:   Used for exportable environment variables when tying Instance Types together in App contexts. If not specified, a name will be generated
+
+Environment Variables
+:   Name and value pairs for environment variables to be loaded on initialization
+
+Enable Settings
+:   Allows for attachment of modifiable file templates to Node Types in a settings tab of the Instance after deployment
+
+Enable Scaling (Horizontal)
+:   Enables load balancer assignment and auto-scaling features
+
+Support Deployments
+:   Enables deployment features (Requires a data volume be configured on each version. Files will be copied into this location)
+
+Upon saving, this Instance Type will be available in the provisioning catalog, per User Role access. However, we still need to add Layouts to the Instance Type, and prior to creating a Layout, we will add a Node Type.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json b/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
new file mode 100644
index 0000000..cae403d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+  "title": "Open Telekom Cloud",
+  "ordinal": 468,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6B3D18B4-5885-4318-848F-DE294F57057B.html",
+  "topic_cluster": {
+    "clustering_title": "Open Telekom Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B3D18B4-5885-4318-848F-DE294F57057B",
+        "clustering_title": "Open Telekom Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md b/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
new file mode 100644
index 0000000..553a400
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B3D18B4-5885-4318-848F-DE294F57057B.md
@@ -0,0 +1,222 @@
+# Open Telekom Cloud
+
+Open Telekom Cloud is an Openstack-based public cloud offering. HPE Morpheus Enterprise offers a robust integration into OTC and supports many of its features, including those listed in the next section.
+
+## Features
+
+- Virtual machine provisioning
+- Backups
+- Brownfield VM management and migration
+- Hypervisor remote console
+- Cloud sync
+- Lifecycle management and resizing
+- Network security group creation
+- Network security group management
+- Router and network creation
+- Load balancer services
+- Docker host management and configuration
+- Floating IP assignment
+- OBS buckets (create, manage, delete, and discovery)
+
+## Add an Open Telekom Cloud
+
+Navigate to Infrastructure > Clouds and click + ADD. Scroll to Open Telekom Cloud and click NEXT. Complete the ADD CLOUD modal, the remainder of this guide includes descriptions of the fields presented on this modal with advice on formatting needed values and where certain data can be located.
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+IDENTITY API URL
+:   The v3 identity API URL, such as `https://iam.eu-de.otc.t-systems.com/v3`
+
+DOMAIN ID
+:   Note that this is the Domain ID and not the Domain Name. The Domain ID can be found via the CLI by typing `openstack domain list`. For default domains, “Default” can be used
+
+PROJECT
+:   OTC projects are groupings of resources and can include compute resources, storage or networking. Multiple projects may be nested under your account. Select the project to which HPE Morpheus Enterprise should onboard from (if desired) and provision
+
+REGION
+:   OTC Region
+
+USERNAME
+:   The username for the OTC service account that HPE Morpheus Enterprise will use. Ensure this account has sufficient cloud privileges to avoid interruption of work in HPE Morpheus Enterprise
+
+PASSWORD
+:   The password for the above service account
+
+IMAGE FORMAT
+:   Select QCOW, RAW or VMDK
+
+IMAGE STORE
+:   Set an OBS bucket as a permanent store location for HPE Morpheus Enterprise virtual images. Users are limited to uploading images of 2GB or less in size if an OBS bucket is not specified here
+
+INVENTORY EXISTING IMAGES
+:   When selected, HPE Morpheus Enterprise will automatically onboard existing cloud resources which can be converted to managed Instance if desired. View onboarded cloud resources in the Compute Section (Infrastructure > Compute)
+
+ENABLE HYPERVISOR CONSOLE
+:   Hypervisor console support for Openstack currently only supports `novnc`. Be sure the novnc proxy is configured properly in your Openstack environment
+
+### Service Endpoints
+
+If needed, update the following service endpoints. A complete listing of OTC API endpoints is [here](https://docs.otc.t-systems.com/endpoint/index.html).
+
+- COMPUTE SERVICE
+- IMAGE SERVICE
+- STORAGE SERVICE
+- NETWORK SERVICE
+- LOAD BALANCER SERVICE
+- OBJECT STORAGE SERVICE
+- SHARED FILE SYSTEM SERVICE
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Network and Router Creation
+
+Once an Open Telekom Cloud is integrated into HPE Morpheus Enterprise, new network creation options become available. When adding a new network (Infrastructure > Networks > NetworksTab), a new type labeled “Open Telekom Private Network” is available when clicking +ADD. When the user creates this network construct in HPE Morpheus Enterprise, a layer two subnet is created but it’s not connected to a Virtual Private Cloud (VPC). This is by design as an Internet-routable network is not always desired. Continue on with this section after creating the network to also create a VPC (router).
+
+### Create a network
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Networks tab
+3. Click +ADD
+4. Select Open Telekom Private Network
+5. Complete the modal based on requirements for the new network
+6. Click SAVE CHANGES
+
+### Create a router
+
+#### Procedure
+
+1. Navigate to Infrastructure > Networks
+2. Click on the Routers tab
+3. Click +ADD
+4. Select Open Telekom Router
+5. Complete the modal based on requirements for the new router
+6. Click SAVE CHANGES
+
+#### Results
+
+When creating a router, it’s helpful to note that the External Network is the floating IP network that has been assigned to the OTC project. This network will grant your Instances their routes out to the Internet. The Internal Subnet can be a layer two subnet that you may have created in the previous step. In addition, multiple subnets can be added to the router (VPC) and the IP address on the subnet would be the router’s internal IP address.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json b/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
new file mode 100644
index 0000000..c6a3804
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+  "title": "Host Features",
+  "ordinal": 176,
+  "parent_title": "Features",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html",
+  "topic_cluster": {
+    "clustering_title": "Host Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0",
+        "clustering_title": "Host Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md b/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
new file mode 100644
index 0000000..0384378
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.md
@@ -0,0 +1,21 @@
+# Host Features
+
+- Automated HVM cluster provisioning
+- CEPH storage configuration for multi-node clusters
+- CEPH summary, a high-level dashboard of CEPH components and status
+- DRS, automatic rebalancing of clusters based on resource consumption
+- Intelligent vCPU placement to lock vCPU cores to the same NUMA node and L3 cache
+- Host hardware sensor data collection
+- Compatibility validation of network and storage devices at time of cluster provisioning
+- Hypervisor console
+- Configuration and deployment of OVS networks (VLANs)
+- Cluster and individual host monitoring
+- Add hosts to existing clusters
+- Console support for cluster hosts
+- Add, edit and remove networks and data stores from clusters
+- Gracefully take hosts out of service with maintenance mode
+- Migration of workloads across hosts
+- Configurable automatic failover of running workloads when a host is lost
+- Ability to add and provision to fibre channel storage resources or iSCSI storage resources via GFS2 filesystem
+- Integration with HPE Morpheus Enterprise costing
+- Governance through HPE Morpheus Enterprise RBAC, Tenancy, and Policies
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json b/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
new file mode 100644
index 0000000..5b406a7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+  "title": "Prices",
+  "ordinal": 291,
+  "parent_title": "Plans",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.html",
+  "topic_cluster": {
+    "clustering_title": "Prices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775",
+        "clustering_title": "Prices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md b/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
new file mode 100644
index 0000000..dbc85b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B922BFB-DFAC-4617-8642-DDFDCEB5A775.md
@@ -0,0 +1,85 @@
+# Prices
+
+Details on various price configurations are given here. When creating prices, it’s also necessary to understand how they will be applied. Specifically, this relates to the **INCUR CHARGES** configuration. Charges can be incurred “While Running”, “While Stopped”, or “Always”. It typically makes the most sense to have running and stopped prices for a given type (Cores, for example) OR to have an “Always” price (but not both). This is because the prices do not stack and the higher of a competing “Always” or running/stopped price will take precedence. This can lead to confusion over which price was applied and how a final cost total was computed. You should decide in advance for a given price type for a price set whether you wish to charge an “Always” rate or charge separately for running/stopped states.
+
+Price Types
+:   - Everything: One price for all resources Storage, CPU, Memory, and Disks
+    - Memory + CPU
+    - Memory Only (per MB)
+    - Cores Only (per core)
+    - Disk Only (per GB)
+    - Platform: Select from Windows, Linux (generic), or one of several specific Linux distributions
+    - Software/Service: Add prices for software licenses which may be included with your price sets
+    - Datastore (per GB)
+    - Load Balancer
+    - Load Balancer Virtual Server
+
+Price Units
+:   - Minute
+    - Hour
+    - Day
+    - Month
+    - Year
+    - Two Year
+    - Three Year
+    - Four Year
+    - Five Year
+
+Currency
+:   - AED
+    - ARS
+    - AUD
+    - BRL
+    - BWP
+    - CAD
+    - CHF
+    - CLF
+    - CLP
+    - COP
+    - DKK
+    - EUR
+    - GBP
+    - IDR
+    - ILS
+    - INR
+    - JOD
+    - JPY
+    - KRW
+    - MAD
+    - MNT
+    - MYR
+    - MXN
+    - NGN
+    - NOK
+    - NZD
+    - PLN
+    - ROL
+    - RUB
+    - SAR
+    - SEK
+    - SGD
+    - THB
+    - TRL
+    - USD
+    - USN
+    - VND
+    - XAF
+    - XCD
+    - XOF
+    - XPF
+    - ZAR (South African Rand)
+
+Cost
+:   The base cost of the resource(s). The Price will match the Cost unless a Price Adjustment is added.
+
+Price Adjustment
+:   - **None:** Default, no markup added and Price will match Cost
+    - **Fixed Markup:** A fixed amount added to the Cost. Price will equal Cost + Markup.
+    - **Percentage Markup:** Adds a percentage markup to Cost. Price equals Cost + (Cost x Markup %)
+    - **Custom Price:** Sets a Price independent from the Cost. If the Cost changes, a Custom Price will not.
+
+Price
+:   A computed value of the final price including the cost plus any applicable markup.
+
+Apply Price Changes to Usage
+:   If marked, when saving a Price Set (new Price Set or saving changes to an existing one), usage records will be restarted for servers affected by the pricing change.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json b/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
new file mode 100644
index 0000000..8e02c9d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+  "title": "Additional Configuration Options",
+  "ordinal": 29,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html",
+  "topic_cluster": {
+    "clustering_title": "Additional Configuration Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5",
+        "clustering_title": "Additional Configuration Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md b/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
new file mode 100644
index 0000000..7e233ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.md
@@ -0,0 +1,13 @@
+# Additional Configuration Options
+
+**Subtopics**  
+
+- **[Advanced morpheus.rb Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-13B77F8D-BA84-4649-A4C1-D137357E7A78.html)**
+- **[Load Balancer Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-32D8CBBE-0375-48BC-8038-E6618F94BE83.html)**
+- **[Offline Installations and Upgrades](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2F18C295-175A-4F00-BA7A-5DB2A068BA2B.html)**
+- **[Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-56ECA7C7-DCE4-423D-B8E1-A429E9132E3E.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html)**
+- **[Import Trusted Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0BBD18FA-91D0-406A-B004-3F068114DE70.html)**
+- **[Data Encryption](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html)**
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html)**
+- **[IPv6](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3148715A-05C1-4793-9B2B-6DB66D7C101D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json b/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
new file mode 100644
index 0000000..e1d161a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+  "title": "Softlayer",
+  "ordinal": 471,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6C22C389-3D06-4DF0-B997-1CA161175182.html",
+  "topic_cluster": {
+    "clustering_title": "Softlayer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6C22C389-3D06-4DF0-B997-1CA161175182",
+        "clustering_title": "Softlayer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md b/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
new file mode 100644
index 0000000..63df293
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6C22C389-3D06-4DF0-B997-1CA161175182.md
@@ -0,0 +1,147 @@
+# Softlayer
+
+## Add a Softlayer Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   Softlayer Username
+
+API Key
+:   Softlayer User API Key, accessible in the Softlayer Portal under `Account  >  Users  >  View API Key
+
+Datacenter
+:   Datacenters will auto-populate upon successful authentication with the above credentials. Select appropriate Datacenter for this Cloud.
+
+Object Store
+:   Select the destination Object Store
+
+Inventory Existing Instances
+:   If enabled, existing Softlayer Instances will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json b/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
new file mode 100644
index 0000000..84c070f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+  "title": "Allow Custom Config",
+  "ordinal": 115,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.html",
+  "topic_cluster": {
+    "clustering_title": "Allow Custom Config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C",
+        "clustering_title": "Allow Custom Config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md b/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
new file mode 100644
index 0000000..6c5266b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6C33948D-4A43-4CBB-B112-DAB194C1AC5C.md
@@ -0,0 +1,32 @@
+# Allow Custom Config
+
+When “Allow Custom Config” is marked on Operational Workflows, the user is shown a text area for custom configuration at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Workflow is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json b/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
new file mode 100644
index 0000000..b1341a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+  "title": "Supported Integration Versions",
+  "ordinal": 524,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Integration Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8",
+        "clustering_title": "Supported Integration Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md b/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
new file mode 100644
index 0000000..ddefe44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.md
@@ -0,0 +1,56 @@
+# Supported Integration Versions
+
+Morpheus supports an extensive range of software integrations and versions past and present. Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+In addition, HPE Morpheus Enterprise is verified to work with, but not limited to:
+
+## Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 1. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
+
+If you have any specific requirements please contact [support@morpheusdata.com](mailto:support%40morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json b/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
new file mode 100644
index 0000000..a3c04bf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+  "title": "VM Features",
+  "ordinal": 177,
+  "parent_title": "Features",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html",
+  "topic_cluster": {
+    "clustering_title": "VM Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3",
+        "clustering_title": "VM Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md b/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
new file mode 100644
index 0000000..4533659
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.md
@@ -0,0 +1,17 @@
+# VM Features
+
+- Workload provisioning and monitoring (Linux or Windows workloads)
+- Guest and hypervisor console support for running workloads with selectable hypervisor console keyboard layouts
+- Affinity placement, pin VMs to hosts
+- Brownfield discovery of existing VMs
+- Reconfigure VM sizing
+- Disk migration across datastores
+- UEFI support
+- Migration of VMs across hosts
+- Configure automatic failover for individual VMs in the event a host is lost
+- Reconfigure running workloads to resize plan, add/remove disks, and add/remove network interfaces
+- Backup and restore HVM workloads, with optional synthetic full backups
+- Clone VMs
+- Take snapshots and revert to snapshots
+- HPE Morpheus Enterprise library and automation support
+- Integration with HPE Morpheus Enterprise costing features
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json b/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
new file mode 100644
index 0000000..340bd72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+  "title": "Uploading OS Images Using Local Storage",
+  "ordinal": 408,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF",
+        "clustering_title": "Uploading OS Images Using Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md b/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
new file mode 100644
index 0000000..24fbb35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.md
@@ -0,0 +1,16 @@
+# Uploading OS Images Using Local Storage
+
+## Prerequisites
+
+- Ensure that Morpheus-app user owns the storage directory.
+- Ensure that Morpheus-app user has access to the storage path.
+
+## About this task
+
+Local storage allows OS images to be uploaded directly to the Morpheus appliance filesystem and is suitable for smaller environments or evaluation use cases.
+
+## Procedure
+
+1. Configure a Local Storage file share under Infrastructure > Storage > File Shares.
+2. Upload the OS ISO using Library > Virtual Images > Add > ISO.
+3. Verify the image status is **Active**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json b/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
new file mode 100644
index 0000000..f006dac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+  "title": "Option Lists",
+  "ordinal": 155,
+  "parent_title": "Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html",
+  "topic_cluster": {
+    "clustering_title": "Option Lists",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299",
+        "clustering_title": "Option Lists"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md b/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
new file mode 100644
index 0000000..855bfaa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.md
@@ -0,0 +1,468 @@
+# Option Lists
+
+Option Lists allow you to give the user more choices during provisioning to then be passed to scripts and/or automation. Option Lists, however, are pre-defined insofar as they are not free-form. They can be manually entered CSV or JSON, they can be dynamically compiled from REST calls via GET or POST requests, or populated by LDAP queries.
+
+![../../_images/newOptionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-90142EEF-2840-4A18-9295-9DFD5C795BC8-high.png)
+
+## Generic Option List Fields
+
+The displayed fields in the create/edit Option List modal depend on the TYPE value selected.
+
+NAME
+:   Name of the Option List
+
+DESCRIPTION
+:   Description of the Option List for reference in Option List list view
+
+TYPE
+:   - **REST:** REST API call to populate Option List
+    - **Manual:** Manually entered dataset, CSV or JSON
+    - **Morpheus API:** Call to internal HPE Morpheus Enterprise API to populate the Option List
+    - **LDAP:** Searches and returns a list of Active Directory objects
+    - **Plugin:** Sourced by custom-coded `DataSetProvider` plugins. See [developer documentation](https://developer.morpheusdata.com/docs#dataset-providers) for additional details
+
+VISIBILITY
+:   If the account currently signed in is not in the master tenant, visibility will automatically change to private
+
+## Manual Option List Fields
+
+DATASET
+:   Appears only for manual Option Lists. Add your CSV or JSON list to this field
+
+    NOTE
+
+    JSON entries must be formatted like the following example: `[{"name":"Test","value":1},{"name":"Testing","value":2}]`
+
+## Plugin Option List Fields
+
+OPTION LIST
+:   Select an Option List made available by a currently-integrated plugins
+
+## REST Option List Fields
+
+SOURCE URL
+:   A REST URL used to fetch list data which is cached in the appliance database
+
+REAL TIME
+:   When checked, a REST call will be made to update the Option List at the time its presented to the User
+
+IGNORE SSL ERRORS
+:   Do not fail API query for self-signed or invalid certs on REST call target
+
+INJECT SYSTEM AUTHORIZATION HEADER
+:   Select when calling back into the HPE Morpheus Enterprise API to automatically inject authorization headers
+
+USE OWNER AUTHORIZATION
+:   Select when calling back into the HPE Morpheus Enterprise API. When enabled, the Option List will be populated using the Option List owner's Role permissions rather than the logged in User's at execution time to ensure complete list population
+
+SOURCE METHOD
+:   GET or POST
+
+SOURCE HEADERS
+:   Custom HTTP Headers to include in the source request
+
+CREDENTIALS
+:   Use a stored credential set or manually enter credentials to access data requiring authentication. Currently, only basic auth is supported
+
+INITIAL DATASET
+:   Create an initial JSON or CSV dataset to be used as the collection for this option list. It should be a list containing objects with properties ‘name’ and ‘value’
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    for(var x=0;x < data.length; x++) {  
+      results.push({name: data[x].name,value:data[x].id});  
+    }
+    ```
+    ```
+
+REQUEST SCRIPT
+:   Create a JS script to prepare the request. Return a data object as the body for a POST request, and return an array containing properties ‘name’ and ‘value’ for a GET request. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’
+
+    **Example:**
+
+    ```
+    ```
+    results.push({name: 'userId', value : data.users})
+    ```
+    ```
+
+    In a GET request (SOURCE METHOD = GET), the value of the results variable is used to build out the request parameters. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1",value: "value1"}]
+    ```
+    ```
+
+    The request would be made to: `https://<someURL>?name1=value1`.
+
+    In a POST request (SOURCE METHOD = POST), the value of the results variable is used to build the body of the POST request. Thus, in the example `results` value:
+
+    ```
+    ```
+    results=[{name:"name1", value:"value1"}, {name:"name2", value:"value2"}]
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    {name:"name1", value:"value1"}, {name:"name2", value:"value2"}
+    ```
+    ```
+
+    An alternative method to building the POST request (SOURCE METHOD = POST), can be seen below. As well, we can access other **Inputs** that are available on the same form, when provisioning an Instance or Catalog Item. As seen below, the other Inputs can be accessed using the `data` variable. We can access another Input by calling its **Field Name**, which can be configured when editing the Input in Library > Options > Inputs. This allows using data from other Inputs to be used in this Input’s request.
+
+    In the example below the Input Field Name we’ll access is `myinputfieldname`, which we can get either the name (visible value for lists) or value from the item:
+
+    Name variable: `data.myinputfieldname` Value variable: `data.myinputfieldname_value`
+
+    ```
+    ```
+    var postBody = {};  
+    postBody["number"] = data.myinputfieldname_value;  
+    postBody["env"] = "all";  
+    results = postBody;
+    ```
+    ```
+
+    The following JSON body would be posted to the target URL:
+
+    ```
+    ```
+    { "number": "123456", "env": "all" }
+    ```
+    ```
+
+## Morpheus API Option List Fields
+
+OPTION LIST
+:   A list of available object types to return
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+    **Example:**
+
+    ```
+    ```
+    var i=0;  
+    results = [];  
+    for(i; i<data.length; i++) {  
+      results.push({name: data[i].name, value: data[i].value});  
+    }
+    ```
+    ```
+
+    Translation script inputs:
+
+    **Clouds**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `code: <String>`
+    - `description: <String>`
+    - `regionCode: <String>`
+    - `location: <String>`
+    - `zoneType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `cloud: <String>` // “public” or “private” value
+      - `code: <String>`
+
+    **Environments**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `code: <String>`
+    - `name: <String>`
+
+    **Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience attribute to avoid requiring translation
+    - `name: <String>`
+    - `code: <String>`
+    - `uuid: <String>`
+    - `location: <String>`
+    - `datacenterId: <Number>`
+
+    **Instances**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `category: <String>`
+    - `description: <String>`
+    - `apiKey: <String>`
+    - `status: <String>`
+    - `hourlyPrice: <Number>`
+    - `hourlyCost: <Number>`
+    - `instanceType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `plan: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `site: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+
+    **Instances Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `instanceId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+    **Networks**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `category: <String>`
+    - `name: <String>`
+    - `status: <String>`
+    - `cloudId: <Number>`
+    - `groupId: <Number>`
+    - `networkType:<Object>`
+
+      - `id: <Number>`
+      - `code: <String>`
+      - `name: <String>`
+    - `externalId: <String>`
+    - `externalNetworkType: <String>`
+    - `networkDomain: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `networkPool: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `createdBy: <String>`
+
+    **Plans**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `storage: <Integer, bytes>`
+    - `memory: <Integer, bytes>`
+    - `cores: <Number>`
+
+    **Resource Pools**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `externalId: <String>`
+    - `name: <String>`
+    - `serverGroupId: <Number>`
+    - `status: <String>`
+    - `regionCode: <String>`
+    - `parentPoolId: <Number>`
+    - `type: <String>`
+
+    **Security Groups**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `code: <String>`
+    - `name: <String>`
+    - `externalType: <String>`
+    - `externalId: <String>`
+    - `cloudId: <Number>`
+    - `scopeMode: <String>`
+    - `scopeId: <Number>`
+
+    **Servers**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `displayName: <String>`
+    - `description: <String>`
+    - `category: <String>`
+    - `osType: <String>`
+    - `powerState: <String>`
+    - `lastStats: <String>`
+    - `zone: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+    - `capacityInfo: <Object>`
+
+      - `maxStorage: <Integer, bytes>`
+      - `maxMemory: <Integer, bytes>`
+      - `maxCores: <Number>`
+      - `usedMemory: <Integer, bytes>`
+      - `usedStorage: <Integer, bytes>`
+    - `computeServerType: <Object>`
+
+      - `id: <Number>`
+      - `name: <String>`
+      - `nodeType: <String>`
+      - `vmHypervisor: <String>`
+      - `containerHypervisor: <String>`
+
+    **Servers Wiki**
+
+    - `id: <Number>`
+    - `value: <Number>` // id, convenience
+    - `name: <String>`
+    - `urlName: <String>`
+    - `category: <String>`
+    - `serverId: <String>`
+    - `content: <String>`
+    - `contentFormatted: <String>`
+    - `format: <String>`
+    - `createdByUsername: <String>`
+    - `updatedByUsername: <String>`
+
+REQUEST SCRIPT
+:   The request script is used differently for Morpheus API Option List types. A Morpheus API option list type will use an internal API to return a list of objects instead of performing HTTP(S) requests to the Morpheus API. Due to this approach, the results object will not be used to generate query parameters or a JSON body. The results object will instead be used to contain a map of accepted key:value pairs that can be used to filter, sort and order the list of objects that get returned.
+
+    Below is a list of accepted `key:value` pairs for each object type:
+
+    **Generic options available for all object types**
+
+    - `max: <integer>` // Maximum number of results to return. Default: 25
+    - `offset: <integer>` // Offset for returned results. Default: 0
+    - `sort: <string>` // Field to sort on. Default: ‘name’
+    - `order: <string>` // Order of returned values. Accepted values: ‘asc’, ‘desc’. Default: ‘asc’
+
+      **Example:**`results = {max: 5, order : 'desc'}`
+
+    **Networks**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only networks associated with this provision type
+    - `layoutId: <Number>` // Id of an Instance Layout, ignored if provisionTypeId is supplied, otherwise used to look up the provision type
+    - `poolId: <Number>` // Id of a network pool, filters to only networks within the specified network pool
+
+    **Instance Networks**
+
+    Contains same options for Networks Morpheus API but pre-filtered for Networks applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Plans**
+
+    - `zoneId` // Required. In order for plans to be returned and properly filtered, you must provide a `zoneId` and `siteId` as well as either a `layoutId` or `provisionTypeId`
+    - `siteId`
+    - `layoutId`
+    - `provisionTypeId: <Number>` // Id of the provision type (technology), filters to only plans associated with this provision type
+
+    **Resource Pools**
+
+    - `zoneId`
+    - `siteId`
+    - `planId`
+    - `layoutId: <Number>` // Id of an Instance Layout, used to get the associated provision type and filter to that provision type
+
+    **Security Groups**
+
+    - `zoneId` // required
+    - `poolId`
+
+    **Clouds**
+
+    - `zoneId : <integer>` // Database ID of cloud to return
+    - `tenantId : <integer>` // Database ID of tenant where clouds are added. Filters to only clouds added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` // Database ID of cloud type. Filters to only clouds with the specified cloud type
+    - `siteId : <integer>` // Database ID of group. Filters to only clouds within the specified group
+    - `tagName : <string>` // Filters to clouds with servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to clouds with servers that have tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on cloud name and description
+
+      **Example:**`results = {tenantId: 1, siteId: 1, tagName: "morpheus"}`
+
+    **Instance Types Clouds**
+
+    Contains same options for Clouds Morpheus API type but pre-filtered for Clouds applicable to a selected Instance Type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Instances**
+
+    - `appsId : <integer>` // Database ID of app to filter by. Returns instances linked to the app
+    - `tenantId : <integer>` // Database ID of tenant where instances are located. Filters to only instances within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the instance that contains the specified server
+    - `tagName : <string>` // Filters to instances with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to instances with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on instance name and description
+
+      **Example:**`results = {tenantId:1, phrase: "ha"}`
+
+    **Groups**
+
+    - `tenantId : <integer>` // Database ID of tenant where groups are located. Filters to only groups added within the specified tenant. Only available in Master Tenant
+    - `zoneTypeId : <integer>` Database ID of cloud type. Filters to only groups that contain clouds with the specified cloud type
+    - `zoneId : <integer>` // Database ID of cloud. Filters to only groups that contain the cloud with the specified ID
+    - `siteId : <integer>` // Database ID of group to return
+    - `phrase : <string>` // Fuzzy matches phrase on group name and location.
+
+    **Servers**
+
+    - `tenantId : <integer>` // Database ID of tenant where servers are located. Filters to only servers within the specified tenant. Only available in Master Tenant
+    - `serverId : <integer>` // Database ID of server. Filters to the server specified by the ID
+    - `siteZoneId : <integer>` // Database ID of cloud. Filters to servers contained within the specified cloud
+    - `serverType : <string>` // Type of server. Accepted values: ‘host’, ‘baremetal’, ‘vm’
+    - `siteId : <integer>` // Database ID of group. Filters to only servers contained within clouds that are added in the specified group
+    - `tagName : <string>` // Filters to servers with tags containing the tagName
+    - `tagValue : <mixed>` // Requires tagName. Filters to servers with tags containing the tagName and specified tagValue
+    - `phrase : <string>` // Fuzzy matches phrase on server name and description.
+
+      **Example:**`results = {max: 50, siteZoneId : 3}`
+
+    **Instances Wiki**
+
+    Contains same options for Instances Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+    **Servers Wiki**
+
+    Contains same options for Servers Morpheus API type.
+    :   - `phrase : <string>` // Fuzzy matches phrase on wiki name, urlName and content
+
+## LDAP Option List Fields
+
+LDAP URL
+:   The URL pointing to the LDAP server
+
+USERNAME
+:   The fully qualified username (with @ suffix syntax) for the binding account
+
+PASSWORD
+:   The password for the above account
+
+LDAP Query
+:   The LDAP query to pull the appropriate objects. See the next section for an example use case
+
+TRANSLATION SCRIPT
+:   Create a JS script to translate the result data object into an array containing objects with properties ‘name’ and ‘value’. The input data is provided as ‘data’ and the result should be put on the global variable ‘results’.
+
+NOTE
+
+Option Lists are set on one or multiple `Select List` or `Typeahead` Inputs. The Input is then set on an Instance Type, Layout, Cluster Layout, and/or Operational Workflow for input during provisioning or execution.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
new file mode 100644
index 0000000..4af5897
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+  "title": "Supported Locales",
+  "ordinal": 12,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Locales",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4",
+        "clustering_title": "Supported Locales"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
new file mode 100644
index 0000000..2ad0ee4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.md
@@ -0,0 +1,28 @@
+# Supported Locales
+
+Morpheus supports a number of different UI locales, including:
+
+- English
+- French
+- German
+- Spanish
+- Chinese (Simplified)
+- Portuguese (Brazil)
+- Korean
+- Italian
+
+The full list of supported locales can be viewed within the Morpheus UI via the “Default Appliance Locale” select list within Administration Settings.
+
+## Switching Locales
+
+The language of text in the Morpheus UI can be changed by telling the Morpheus server which locale to use. A Locale is made up of a language code and a country code. For example “en\_US” is the code for US English, whilst “en\_GB” is the code for British English. When using the Morpheus UI software through a client, the Morpheus UI software server will send the UI text back to the client using the appropriate static Language Pack. All translations returned via Morpheus Internationalization have been made and approved prior to the Morpheus UI version release.
+
+**Via Locale Settings in the Morpheus UI:** An application wide default locale can be configured within the Master Tenant under Administration -> Settings -> Default Appliance Locale. An individual Morpheus user can configure a preferred locale within their user settings. Using a locale setting is the preferred method for switching the Morpheus UI language.
+
+**Via the Accept-Language HTTP header:** The Accept-Language request HTTP header advertises which languages the client is able to understand, and which locale variant is preferred. Most browsers will by default send a “Accept-Language” HTTP header when visiting websites. The value of Accept-Language will match the configured preference of the browser’s user language/locale settings. The Morpheus UI will automatically detect the Accept-Language header and return the UI text from the corresponding Language Pack where possible. If there is no matching Language Pack the English US language pack is displayed in the UI. If an application locale or user locale setting has been configured in the Morpheus UI, then this will override the user’s browser preferences.
+
+**Via the “lang” query parameter:** Morpheus has the capability to switch locales by passing a parameter called “lang” to the Morpheus UI request. For example, “operations/dashboard?lang=de” will switch the locale preference to German. Morpheus will automatically switch the user’s locale and store it in a cookie so subsequent requests will have the new header. If a user is unauthenticated then the user’s locale will be reset. To switch a locale back to English pass “?lang=en” as a query parameterin the Morpheus UI request.
+
+NOTE
+
+Many of Morpheus’ language packs are generated by our clients. For that reason, we cannot guarantee accuracy and completeness of the translation. As new UI elements are added, existing language sets may not have immediate updates to keep pace with application changes. If you would like to contribute to a new or existing language pack, contact your account team or Morpheus support. Contributed content will be included within the next application version.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json b/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
new file mode 100644
index 0000000..ca6b778
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+  "title": "Checks",
+  "ordinal": 258,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.html",
+  "topic_cluster": {
+    "clustering_title": "Checks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8",
+        "clustering_title": "Checks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md b/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
new file mode 100644
index 0000000..20de295
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-6FFCD815-6AC5-46F9-AB71-F293570366A8.md
@@ -0,0 +1,87 @@
+# Checks
+
+The Monitoring system is composed of individual checks. A check is created for every container or vm that is provisioned through HPE Morpheus Enterprise . One interesting thing about these checks is they are type aware. There are several different built in check types that are selected based on the service or instance type that is being provisioned. These range from database type checks to web checks and message checks. They are highly configurable and also feature fallback check types for those more generic use cases.
+
+Checks can be customized to run custom queries, check queue sizes, or even adjust severity levels and check intervals. All of these things can be controlled from the Checks sub tab within Monitoring.
+
+## Health
+
+A Check can have one of four primary health states, which are Error, Healthy, Warning, and Unknown. Checks can also be muted, in which case they are effectively disabled and are not actively run to gather an updated health state. While Checks are muted, the availability percentage does not change regardless of the health of the workload being checked. The default view shows Checks in all health states but this view can be filtered to show just one health state. Change the view filter to “Happy” to see only Checks in a Healthy state, “Sad” to see only Checks in an Error state, “Warning” to see Checks in both a “Warning” and “Unknown” state, and “Muted” to see only muted Checks.
+
+When a Check test fails, the system automatically reattempts the Check after 30 seconds to eliminate false negatives. This will convert the Check into an error state and raise the appropriate severity incident depending on the grouping of the Check. When a Check recovers, it automatically goes into a Warning state. The Warning state will remain until 10 successful Check runs have completed.
+
+## Options
+
+All check types have several core options and some of these default options can be configured in Admin  >  Monitoring. This includes the default check interval time. By default a check is run every 5 minutes. This can however be changed to run as frequently as once every minute.
+
+- Max Severity: The maximum severity level impact for a created incident that can occur if the check fails (defaults to Critical).
+- Check Interval: The frequency with which a check is run (default 5 minutes).
+- Affects Availability: Whether or not this check impacts overall system availability calculations.
+
+## SSH Tunneling
+
+In many cases when it comes to monitoring databases, and services they may not be fronted on the public ip’s for external monitoring. To reach these safely, and securely HPE Morpheus Enterprise provides an SSH Tunneling mechanism for its check servers. This allows the check to be confirmed via an ssh port tunnel securely using a keypair.
+
+## Check Servers
+
+On a base installation of HPE Morpheus Enterprise a single check server is installed on the appliance. This is used for running any custom user checks. This service connects to the provided rabbitmq services and can be moved off or even scaled horizontally onto sets of check servers. All other checks that are related to provisioned containers or VMs are executed by the installed agent on the guest OS or Docker host.
+
+## Check types
+
+### Web Check
+
+A web check is useful to identify if a url is reachable and the text to match check criteria confirms if the website is loading with the expected values. The text to match character should be within the first few lines of the page source.
+
+Use case:
+:   Adding a check to make sure morpheus demo environment is functioning. The below check will login to the morpheus UI and look for a text Morpheus on the dashboard page.
+    :   Values to be added in Check:
+        :   - Name: “<enter name>”
+            - Type: Web Check
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Web Url: <https://demo.morpheusdata.com/operations/dashboard> (Note: this page will load only if my login is successful. Enter the login details in Username and password fields)
+            - Request Method: GET
+            - Basic Authentication: \* User: <username> \* Password: <password>
+            - Text to Match: “Morpheus” (Login to the url and on the page of dashboard, right click and select view page source. In the forst few lines, look for a text that you want this check to verify)
+            - Save Changes
+
+### Push API Check
+
+This check can be used to send an API call to morpheus from a platform to check if the push api is working. A push Check is not polled regularly by the standard monitoring system. Instead it is expected that an external API push updates as to the status of the check timed closely with the configured check interval setting. This is used to throttle the push from performing too many status updates.
+
+NOTE
+
+If a check is not heard from within the check intervals, It’s status will be updated to error and an incident will be raised as if it failed.
+
+Use Case:
+:   Send an API call from an app to make sure the API is not cluttered and can send checks in a 2 mins interval.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “Push API Check”
+            - Interval: 5 mins (Select an interval)
+            - Max severity: Critical
+            - Check the box for affects availability
+            - Copy the curl command are schedule to send this via your API. For testing we used postman to send the api call at an interval of 4 mins.
+            - Save Changes
+
+### MySQL Check
+
+This check is used to run a query on a host running mysql.
+
+Use Case:
+:   Query localhost running mysql to query a table to check if there is any status as requested. If the status has a count of 1 then the check would pass else mark it as critical.
+    :   Values to be added to the check:
+        :   - Name: “<enter name>”
+            - Type: “MySQL Check”
+            - Interval: 5 mins (Select an interval)
+            - Check the box for affects availability
+            - Host: 127.0.0.1
+            - Port: 3306
+            - DB Name: morpheus
+            - User: <db user name>
+            - Password: <password>
+            - Query: “select count(\*) as count from request\_reference where status = ‘requested’;”
+            - Operator: Equal
+            - Check results: 1
+            - Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json b/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
new file mode 100644
index 0000000..828650a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+  "title": "Tenants",
+  "ordinal": 277,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md b/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
new file mode 100644
index 0000000..2c2c325
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.md
@@ -0,0 +1,71 @@
+# Tenants
+
+The Tenants page displays a list of all Tenants. This page enables users to Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, and the Created Date.
+
+Click the Tenant Name to drill into the Tenant View where you can again Edit or Delete the Tenant, as well as Create Users, Edit Users, and Delete Users users belonging to the Tenant.
+
+## Create Tenants
+
+### About this task
+
+To Create Tenants:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Create Tenant button.
+4. From the New Tenant wizard input: 
+
+   - Name
+   - Description (optional)
+   - Subdomain
+   - Base Role
+   - Currency
+5. Within the Advanced Options section, track customer data related to the Tenant if needed: 
+
+   - Account Number
+   - Account Name
+   - Customer Number
+6. Click the Save Changes
+
+## Edit Tenant
+
+### About this task
+
+To edit a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Edit the Edit Tenant settings.
+
+## Disabling Tenant
+
+### About this task
+
+When disabling a tenant, they are not able to login and cannot be impersonated by another tenant. However all of their information will still remain in HPE Morpheus Enterprise and they may still receive notifications and alerts.
+
+To disable a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Edit pencil icon on the row of the Tenant to edit.
+4. Uncheck the `Enabled` box.
+
+## Delete Tenant
+
+### About this task
+
+To delete a Tenant:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Delete trashcan icon on the row of the Tenant to delete.
+4. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.json b/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
new file mode 100644
index 0000000..d1710bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+  "title": "SSL Certificates",
+  "ordinal": 34,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7056841F-C280-4C83-8065-017EF45643F9.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7056841F-C280-4C83-8065-017EF45643F9",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.md b/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
new file mode 100644
index 0000000..39d265b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7056841F-C280-4C83-8065-017EF45643F9.md
@@ -0,0 +1,75 @@
+# SSL Certificates
+
+By default HPE Morpheus Enterprise generates a Self-Signed SSL Certificate. The Self-Signed SSL Certificate can be replaced with a Trusted CA Signed SSL Certificate.
+
+## Trusted CA Signed SSL Certificate Implementation
+
+### Procedure
+
+1. If you don’t already have your certificate, run an OpenSSL command to generate an SSL certificate request (.csr) and private key (.key). If you need help formatting the command, [DigiCert provides a helpful tool](https://www.digicert.com/easy-csr/openssl.htm)
+2. Submit your certificate request (.csr) and await approval of the request and return of the certificate (.crt)
+3. Copy the private key and certificate to `/etc/morpheus/ssl/your_fqdn_name.key` and `/etc/morpheus/ssl/your_fqdn_name.crt` respectively 
+
+   Extracting Certificates in PFX Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl pkcs12 -in example.pfx -nocerts -nodes -out priv.key  
+   # Extract the public key  
+   openssl pkcs12 -in example.pfx -clcerts -nokeys -out pub.crt  
+   # Extract the CA cert chain  
+   openssl pkcs12 -in example.pfx -cacerts -nokeys -chain -out ca.crt
+   ```
+   ```
+
+   Extracting Certificates in PEM Format
+
+   ```
+   ```
+   # Extract the private key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key  
+   # Extract the public key  
+   openssl x509 -outform der -in your-cert.pem -out your-cert.key
+   ```
+   ```
+4. Edit the configuration file `/etc/morpheus/morpheus.rb` and add the following entries: 
+
+   ```
+   ```
+   nginx['ssl_certificate'] = 'path to the certificate file'  
+   nginx['ssl_server_key'] = 'path to the server key file'
+   ```
+   ```
+
+   NOTE
+
+   Both files should be owned by root and only readable by root, also if the server certificate is signed by an intermediate then you should include the signing chain inside the certificate file. The key file needs to be decrypted for Morpheus to install it properly.
+5. Next simply reconfigure the appliance and restart nginx: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl restart nginx
+   ```
+   ```
+
+## Self-Signed SSL Certificate Regeneration
+
+When Morpheus is deployed it generates a 10 year Self-Signed SSL Certificate. Below details the process to regenerate the Certificate and Key files.
+
+### Regenerate both the Certificate and Key
+
+#### Procedure
+
+1. Delete the certificate and key files in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
+
+### Regenerate only the Certificate
+
+#### Procedure
+
+1. Delete the certificate file in `/etc/morpheus/ssl/`.
+2. Run Reconfigure `morpheus-ctl reconfigure`.
+3. Restart NGINX `morpheus-ctl restart nginx`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json b/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
new file mode 100644
index 0000000..515c8a4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+  "title": "HPE Morpheus Enterprise",
+  "ordinal": 1,
+  "parent_title": null,
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312",
+        "clustering_title": "HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md b/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
new file mode 100644
index 0000000..9482b3b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-709AAADB-A9C1-40B6-AD22-958EE7E6F312.md
@@ -0,0 +1,20 @@
+# HPE Morpheus Enterprise
+
+IMPORTANT
+
+This user manual pertains to HPE Morpheus Enterprise Software. [Click here](https://www.hpe.com/support/morpheus-vm-essentials-documentation-latest) for the HPE Morpheus VM Essentials Software user manual.
+
+**Subtopics**  
+
+- **[Getting Started](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3CA39221-7A9A-4C51-B56D-D5D1A69876FE.html)**
+- **[Operations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html)**
+- **[Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html)**
+- **[Library](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-17B067B3-32C3-4DE7-82DE-B6033C235495.html)**
+- **[Infrastructure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4A13998A-C40E-4505-B1A1-16B21926D177.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-443DA867-07E9-416F-ABFB-2C4BF2312D53.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_2.html)**
+- **[Tools](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2914AB3A-354A-4E42-BCFF-3B3F19867E9A.html)**
+- **[Administration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html)**
+- **[Personas](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html)**
+- **[Diagrams](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-173469C2-D5C6-47F6-8A01-41C3D73B679B.html)**
+- **[Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json b/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
new file mode 100644
index 0000000..1d8bcca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+  "title": "Floating IPs",
+  "ordinal": 221,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.html",
+  "topic_cluster": {
+    "clustering_title": "Floating IPs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-719570B7-BE8A-49B2-87D7-336A9703ED88",
+        "clustering_title": "Floating IPs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md b/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
new file mode 100644
index 0000000..6c932a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-719570B7-BE8A-49B2-87D7-336A9703ED88.md
@@ -0,0 +1,32 @@
+# Floating IPs
+
+## Overview
+
+HPE Morpheus Enterprise supports sync and management of floating IP addresses for OpenStack, Huawei, and OTC Clouds. When these Clouds are integrated and floating IPs are present, HPE Morpheus Enterprise will automatically sync them in. Once synced, floating IPs are viewable from their own list page (Infrastructure > Network > Floating IPs) and related options are presented during provisioning, teardown, and from Instance detail pages.
+
+NOTE
+
+The Floating IPs tab is present only when supported Clouds are integrated and floating IPs are available. Additional Cloud support is planned for the future.
+
+## Floating IPs List Page
+
+All Floating IPs known to HPE Morpheus Enterprise can be viewed on the Floating IPs List Page (Infrastructure > Network > Floating IPs). From the Floating IPs list page we can see the following:
+
+- **IP ADDRESS**: The address for the floating IP synced from a supported Cloud
+- **CLOUD**: The Cloud integration the floating IP was synced from
+- **STATUS**: “Free” when the floating IP is available and “Assigned” when the floating IP is currently assigned to a workload
+- **VM**: For assigned floating IPs, the VM which currently has the floating IP attached
+
+Free floating IPs will have a gear icon (⚙) at the end of the row. Click the gear icon and select “Release Floating IP” to release from within the source cloud and remove the entry from the Floating IPs list.
+
+![../../_images/floatIpList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-65C72DC3-8755-45A9-978E-2E3F840D4F91-high.png)
+
+## Working with Floating IPs
+
+When provisioning to supported Clouds, HPE Morpheus Enterprise will give the option to attach a floating IP at provision time. From the CONFIGURE tab of the provisioning wizard for supported Clouds, select the desired floating IP.
+
+![../../_images/floatIpSet.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9514094E-8567-4571-ACFD-C334FA3A166C-high.png)
+
+During Instance teardown, HPE Morpheus Enterprise gives the option to release the floating IP.
+
+![../../_images/floatIpDelete.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5B05E0B0-B6AA-440E-947C-C9683D20BF9C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json b/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
new file mode 100644
index 0000000..dffbbb0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+  "title": "Uploading OS Images Using CIFS (Samba)",
+  "ordinal": 410,
+  "parent_title": "Uploading OS Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images Using CIFS (Samba)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD",
+        "clustering_title": "Uploading OS Images Using CIFS (Samba)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md b/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
new file mode 100644
index 0000000..e2d57ac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.md
@@ -0,0 +1,12 @@
+# Uploading OS Images Using CIFS (Samba)
+
+## About this task
+
+CIFS (Samba) allows OS images to be stored on a shared Windows or Linux file server.
+
+## Procedure
+
+1. Configure a CIFS file share under Infrastructure > Storage > File Shares.
+2. Provide valid credentials for the Samba share.
+3. Upload the OS ISO through Library > Virtual Images > Add > ISO.
+4. Verify the image is accessible for provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json b/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
new file mode 100644
index 0000000..c2874c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+  "title": "Communication Data",
+  "ordinal": 9,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html",
+  "topic_cluster": {
+    "clustering_title": "Communication Data",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9",
+        "clustering_title": "Communication Data"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md b/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
new file mode 100644
index 0000000..c547e36
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.md
@@ -0,0 +1,101 @@
+# Communication Data
+
+The following table contains communication information, including frequency and configurability between HPE Morpheus Enterprise and its supported technology integrations.
+
+Table 1. Communication Frequency, Ports, and Protocols
+
+        | Source | Push/Pull | Destination | Description | Default Interval | Configurable Internal |
+| --- | --- | --- | --- | --- | --- |
+| Cloud Foundry App Check | Server Pull | Cloud Foundry Applications that exist within Morpheus | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Docker Container Check | Server Pull | Docker containers that exist within Morpheus | If no other check types apply, automatically created during provisioning if using the related system container type, in order to inspect the running state. May be manually created but must be a machine that exists in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Open Search Check | Server Pull | Open Search application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Microsoft SQL Server Check | Server Pull | Microsoft SQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Mongo Check | Server Pull | Mongo DB application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| MySQL Check | Server Pull | MySQL application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Postgres Check | Server Pull | Postgres application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Push API Check | Client Push | Morpheus API | External system push notifications to Morpheus for the purpose of ensuring the notifications are received. | 5 Minutes | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. This is dependent on the external source and triggers an error after two missed intervals. |
+| Rabbit MQ Check | Server Pull | Rabbit MQ application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Redis Check | Server Pull | Redis application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Riak Check | Server Pull | Riak application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| SNMP Check | Server Pull | SNMP | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Socket Check | Server Pull | Web Socket | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Virtual Machine Check | Server Pull | Virtual Machine that exists within Morpheus | If no other check types apply, automatically created during provisioning if using the related system node type, in order to inspect the running state. May be manually created. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Web Check | Server Pull (GET) or Server Push (POST) | Web application | Automatically created during provisioning if using the related system node/container type in order to inspect the running state. May be manually created but does not need to exist in Morpheus. | 5 Minutes with 30 second recheck on failure. | Range of 1 minute to 3 hours of selectable intervals. Additionally, the default interval may be globally altered. |
+| Public Cloud Integration | Server Pull | Alibaba Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Amazon AWS GovCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | DigitalOcean | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Google Cloud Platform | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Huawei Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | IBM Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Microsoft Azure | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Open Telekom Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | Oracle Public Cloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | UpCloud | Data synchronization | 5 Minutes | No |
+| Public Cloud Integration | Server Pull | VMware on AWS | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Cisco UCS Manager | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Dell EMC | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | HPE OneView | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | KVM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | MacStadium | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Azure Stack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft Hyper‐V | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Microsoft SCVMM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Nutanix Acropolis | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Openstack | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Oracle VM | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Pivotal Cloud Foundry | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Supermicro | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware vCloud Director | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Vmware ESXi | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware Fusion | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | VMware vCenter | Data synchronization | 5 Minutes | No |
+| Private Cloud Integration | Server Pull | Xen Server | Data synchronization | 5 Minutes | No |
+| Automation Integration |  | Ansible |  | N/A | No |
+| Automation Integration | Server Pull | Ansible Tower | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Chef | Data synchronization | 10 Minutes | No |
+| Automation Integration | Server Pull | Puppet | Data synchronization | 10 Minutes | No |
+| Automation Integration |  | Terraform |  | N/A | No |
+| Automation Integration | Server Pull | vRealize Orchestrator | Data synchronization | 10 Minutes | No |
+| Backup Integration | Server Pull | Commvault | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Veeam | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Rubrik | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Zerto | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Backup Integration | Server Pull | Avamar | Scheduled backup execution (1 Minute), Backup provider refresh (1 hour) | 1 Minute; 1 Hour | No |
+| Build Integration | Server Pull | Jenkins | Data synchronization | 10 minutes | No |
+| Container Integration | Server Pull | Docker | Data synchronization | 5 Minutes | No |
+| Container Integration |  | Docker Registry | On‐demand | N/A | No |
+| Container Integration | Server Pull | Kubernetes | Data synchronization | 5 Minutes | No |
+| Deployment Integration | Server Pull | Git/Github | Syncing latest version of Git‐tracked repos | On‐demand when using a file or repository for Morpheus functions | No |
+| DNS Integration | Server Pull | AWS Route53 | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | Microsoft DNS | Data synchronization | 10 minute | No |
+| DNS Integration | Server Pull | PowerDNS | Data synchronization | 10 minute | No |
+| Identity Management Integration | Server Pull | Microsoft AD | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | OneLogin | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Okta | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | Jump Cloud | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | LDAP | User Role and Group Sync | N/A, On login | No |
+| Identity Management Integration | Server Pull | SAML | User Role and Group Sync | N/A, On login | No |
+| IPAM Integration | Server Pull | Infoblox | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | phpIPAM | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| IPAM Integration | Server Pull | Bluecat | Refresh network pool servers (1 Hour) | 1 Hour | Yes (Variable Throttle Rate) |
+| IPAM Integration | Server Pull | SolarWinds | Refresh network pool servers (1 Hour) | 1 Hour | No |
+| ITSM Integration | Server Pull | ServiceNow | Approval sync | 5 Minutes | No |
+| ITSM Integration | Server Pull | Cherwell | Data synchronization | 10 Minutes | No |
+| ITSM Integration | Server Pull | Remedy | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | AzureLB | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | F5 BigIP | Data synchronization | 10 Minutes | No |
+| Load Balancer Integration | Server Pull | Citrix NetScaler | Data synchronization | 10 Minutes | No |
+| Logging Integration |  | Syslog | On‐demand | N/A | No |
+| Monitoring Integration | Server Pull | ServiceNow | Data synchronization | Depends on check configuration | Yes (part of check configuration) |
+| Monitoring Integration |  | AppDynamics | On‐demand | N/A | No |
+| Monitoring Integration |  | NewRelic | On‐demand | N/A | No |
+| Network Integration | Server Pull | NSX | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Cisco ACI | Data synchronization | 10 Minutes | No |
+| Network Integration | Server Pull | Unisys Stealth | Data synchronization | 10 Minutes | No |
+| Storage Integration | Server Pull | 3Par | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Azure Storage | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Dell ECS | Updating storage metadata | 10 Minutes | No |
+| Storage Integration | Server Pull | Isilon | Updating storage metadata | 10 Minutes | No |
+| Morpheus Agent | Agent Pull | Application Tier | Secure Web Socket | Persistent | No |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json b/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
new file mode 100644
index 0000000..11107ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+  "title": "Cloud Foundry",
+  "ordinal": 392,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Foundry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C",
+        "clustering_title": "Cloud Foundry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md b/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
new file mode 100644
index 0000000..a616c69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-735C5C8D-CE99-4261-B0D1-0B3F4D34382C.md
@@ -0,0 +1,441 @@
+# Cloud Foundry
+
+## Configuration
+
+### Adding PCF Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select CLOUD FOUNDRY from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   Cloud Foundry API Url
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+### Adding PCF Cloud From Infrastructure > Groups
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group
+3. Select the CLOUDS tab
+4. Scroll down to CLOUD FOUNDRY and select + ADD
+5. Populate the following: 
+
+   Name
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   Location
+   :   Description field for adding notes on the cloud, such as location.
+
+   Visibility
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   Select a Tenant if Visibility is set to Private to assign to Cloud to that Tenant. Multiple Tenants can be added by editing the cloud after creation.
+
+   API URL
+   :   Cloud Foundry API Url. Example `https://api.cf.morpheusdata.com`
+
+   CLIENT ID
+   :   Typically `cf`
+
+   CLIENT SECRET
+   :   Typically blank
+
+   USERNAME
+   :   Enter Username. If using an API Key, enter `apikey` for username, and the API Key as the password.
+
+   PASSWORD
+   :   Enter Password. If using an API Key, the API Key as the password.
+
+   ORGANIZATION
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Review and then Select COMPLETE
+
+## Adding Spaces
+
+### About this task
+
+Cloud Foundry Spaces are referred to as Resource Pools in Morpheus. You can add a new Space by:
+
+### Procedure
+
+1. Navigating to the Cloud and selecting the Resources tab.
+2. Then, click :guilabel:‘+ Add Resource’.
+3. Give the Resource a Name
+4. Expand the Managers, Developers, and Auditors section to add specific Cloud Foundry users to the roles. When adding a user to these sections, use their Cloud Foundry email addresses.
+
+## Provisioning
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, as well as a generic Cloud Foundry Instance Type that will create a shell app used in conjunction with deployments. PCF Marketplace items can also be added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+## Deployments
+
+The Cloud Foundry App Instance Type is used in conjunction with deployments. Users do not have to pick deployment when creating a Cloud Foundry App Instance Type, but then Instance will only be a shell of a Cloud Foundry Application.
+
+A deployment in Morpheus can either point to a git hub repository or contain the actual manifest.yml and associated artifacts required for a Cloud Foundry deployment. During the deployment, Morpheus will gather up the files required. Therefore, if the deployment points to a git hub repository, Morpheus will fetch the files from git hub. Once the files are obtained, Morpheus will deploy the artifacts in a similar fashion to the Cloud Foundry cli. This includes parsing the manifest to obtain the parameters to create or update the Cloud Foundry application. Morpheus will ignore certain fields such as memory and disk size because they are dictated by the selected plan. Other fields are utilized such as routes. After parsing the manifest.yml file (including overwriting certain fields), Morpheus is ready to update or create the App in Cloud Foundry.
+
+After the App is configured, the artifacts references in the Morpheus deployment are uploaded to Cloud Foundry for the App. Note that when paths are referenced in the manifest.yml file, the paths continue to be relative to the manifest. So, a jar file under build/libs would need to be found under the build/libs directory.
+
+If Cloud Foundry services are specified in the manifest, they must already exist within Cloud Foundry. Morpheus App templates can be utilized to wire up Cloud Foundry services created by Morpheus. In this case, Morpheus will add all of the included service names defined in the App template to the manifest.yml services section. Therefore, multiple services can be used and wired up by Morpheus.”
+
+## Example
+
+To better understand how Morpheus parses the manifest.yml file, lets take a closer look at the Cloud Foundry ‘spring-music’ project. The project can be found here (<https://github.com/cloudfoundry-samples/spring-music>).
+
+The project contains the required manifest.yml file as well as the source code and build.gradle file to define how the project is to be built. After downloading the project to your local machine, build the project to generate the jar.
+
+Now, let’s take a look at the manifest.yml file:
+
+```
+```
+---  
+applications:  
+- name: spring-music  
+  memory: 1G  
+  random-route: true  
+  path: build/libs/spring-music.jar
+```
+```
+
+Using the Cloud Foundry docs (<https://docs.cloudfoundry.org/devguide/deploy-apps/manifest.html>), we can gain a better understanding of how this file is utilized by Cloud Foundry.
+
+- The `-name` parameter defines the name that will be given to the application in Cloud Foundry. Morpheus will overwrite this value with the name given to the Instance being created in Morpheus.
+- The `-memory` parameter (as well as the disk\_quota parameter if specified) will be overwritten by Morpheus based on the plan specified for the Instance.
+- The `-path` parameter defines, where relative to the manifest.yml file, your Cloud Foundry application can be found.
+- The `-random-route parameter`, as well as all other parameters described in the Cloud Foundry documentation will simply be passed through to Cloud Foundry.
+
+## Adding Marketplace Items
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds and select your Cloud Foundry Cloud
+2. Select the MARKETPLACE tab
+3. Select + ADD MARKETPLACE ITEM
+4. Select the HPE Morpheus Enterprise Instance Type to add the Marketplace Item to.
+5. Enter version
+6. Search for and select Marketplace Item
+7. Select SAVE CHANGES
+
+### Results
+
+A Node Type and layout will be created in the Library section and the layout will be automatically added to the Instance Type selected when adding the Marketplace Item.
+
+## Provisioning Instances
+
+### Seeded and Marketplace Items
+
+#### About this task
+
+HPE Morpheus Enterprise automatically seeds MySQL, Redis and RabbitMQ PCF Instance Types, and PCF Marketplace items can also be easily added to the Provisioning Library in the Cloud detail view Marketplace tab. The Marketplace item will be added to the selected Instance Type and available when selecting the Cloud Foundry Cloud during Instance or App Template creation.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select an Instance Type with a Cloud Foundry layout (MySQL, Redis and RabbitMQ plus Marketplace additions)
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select Version and Instance Configuration for a Cloud Foundry layout, ex: Cloud Foundry MySQL
+8. Select a Plan and available options for the Plan, or use the custom Plan
+9. Select a Space to add the Instance to
+10. Optionally configure advanced options
+11. Select NEXT
+12. Optionally configure Automation options
+13. Select NEXT
+14. Select COMPLETE
+
+#### Results
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
+
+### Cloud Foundry App Instance Type
+
+#### About this task
+
+IMPORTANT
+
+Add Deployments in Provisioning > Code > Deployments to be used when provisioning a Cloud Foundry App Instance Type.
+
+NOTE
+
+Minimal options are outlined below.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances and select the Cloud Foundry App Instance Type
+2. Select NEXT
+3. Select a Group and PCF Cloud
+4. Add an Instance Name
+5. Optionally select and Environment Tag and/or add a custom Tag
+6. Select NEXT
+7. Select a Plan and available options for the Plan, or use the custom Plan
+8. Select a Space to add the Instance to
+9. Select NEXT
+10. In the Deployments section, select a Deployment and Version to be deployed. These can be git repos or files added in Provisioning > Code > Deployments 
+
+    IMPORTANT
+
+    If services are specified in a git repo manifest, HPE Morpheus Enterprise assumes they are already exist in the PCF cloud with matching names.
+11. Select NEXT
+12. Select COMPLETE
+
+#### Results
+
+This will quickly create the Cloud Foundry Application, and then the deployment will follow which may take longer depending on the app configuration. The location will be updated with the route once it is configured.
+
+NOTE
+
+Compute, Memory, and CPU stats will be pulled, and a Cloud Foundry monitoring health check will be automatically configured for the instance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json b/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
new file mode 100644
index 0000000..37b66ed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+  "title": "HPE Morpheus Enterprise Agent Key Features",
+  "ordinal": 44,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38",
+        "clustering_title": "HPE Morpheus Enterprise Agent Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md b/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
new file mode 100644
index 0000000..de12eab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.md
@@ -0,0 +1,64 @@
+# HPE Morpheus Enterprise Agent Key Features
+
+While optional, HPE Morpheus Enterprise Agent provides many benefits and features in areas of log aggregation, security, automation, monitoring, and more. This page contains the complete summary of its key features and benefits.
+
+## Logging
+
+The installed HPE Morpheus Enterprise Agent captures application logs and sends them back to the HPE Morpheus Enterprise appliance. The Agent buffers and compresses logs, sending them in chunks to minimize packet transfers. If desired, users may set up forwarding to an external syslog platform though for most users HPE Morpheus Enterprise internal logging functionality is sufficient. Agent logs can be viewed in the UI at Monitoring > Logs. Filtering and search tools are available, even supporting [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html). Logs may also be exported.
+
+## Monitoring and Guidance
+
+HPE Morpheus Enterprise provides robust monitoring into the workloads it manages. For example, from Instance detail pages, usage metrics are tracked on the Summary and Monitoring tabs. The available metrics are significantly improved when HPE Morpheus Enterprise Agent is installed on the workload. HPE Morpheus Enterprise will make a best effort to gather this information in the absence of an installed Agent but for some Cloud types this is not possible. The table below shows the usage metrics HPE Morpheus Enterprise can gather with and without the Agent (though the exact metric available without the Agent will vary by Cloud).
+
+Table 1.
+
+      |  |  |  |  |
+| --- | --- | --- | --- |
+| **Category** | **Statistic** | **With Agent** | **Without Agent** |
+| Memory | Max Memory | Yes | Yes |
+| Memory | Used Memory | Yes | No |
+| Memory | Cache Memory | Yes | No |
+| Storage | Max Storage | Yes | Yes |
+| Storage | Used Memory | Yes | No |
+| Processing | System CPU % | Yes | No |
+| Processing | User CPU % | Yes | Yes |
+| IOPS | Total IOPS | Yes | No |
+| IOPS | IOPS Read | Yes | No |
+| IOPS | IOPS Write | Yes | No |
+| Networking | Net TX Rate | Yes | No |
+| Networking | Net RX Rate | Yes | No |
+| Other | Agent Command Bus | Yes | No |
+| Other | Log Aggregation | Yes | No |
+| Other | Health & Monitoring | Yes | No |
+
+In addition to usage and monitoring, HPE Morpheus Enterprise also provides a useful guidance feature (Operations > Guidance). Guidance analyzes your managed workloads and makes cost-saving or performance recommendations. The effectiveness of this feature is greatly enhanced when HPE Morpheus Enterprise Agent is installed on your workloads.
+
+## Script Execution
+
+The HPE Morpheus Enterprise Agent initiates an outbound connection from the managed workload to the appliance over TCP port 443. This establishes a bidirectional command bus which allows HPE Morpheus Enterprise to orchestrate automation on managed machines without stored credentials. Many different [Task types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html) are supported and Tasks can be stacked into Operational or Provisioning Workflows to create logical automation routines. SSH or WinRM connectivity, as well as credentials, are required for Task execution when HPE Morpheus Enterprise Agent is not installed.
+
+## Setting File Templates
+
+File Templates are stored templated text files, primarily config files (for example, `my.cnf` or `morpheus.rb`). Users have access to the full map of HPE Morpheus Enterprise variables for injecting values custom to the specific workload at provision time. HPE Morpheus Enterprise Agent can transfer files generated from templates to managed nodes.
+
+## Firewall Management
+
+When “Local Firewall” is enabled for a Cloud (see the Advanced Options section on the Add/Edit Cloud modal), the HPE Morpheus Enterprise Agent can manage host or VM IP Table (firewall) rules for Linux workloads.
+
+## Summary and Additional benefits:
+
+- Installation is optional for provisioned and managed VMs
+- The Linux agent can be shrunk and should be less then 0.2% peak
+- Provides a command bus such that HPE Morpheus Enterprise doesn’t need credentials to access a box
+- Can still manage workflows if credentials are changed
+- SSH agent can be disabled and still get access to the box
+- Agent can be installed over Cloud-init, Windows unattend.xml, VMware Tools, SSH, WinRM, Cloudbase-Init, or manually
+- Makes a single, persistent connection over HTTPS websocket and runs as a service
+- Buffers and compresses logs, then sends them in chunks to minimize packets
+- Supports syslog forwarding
+- Accepts commands, executes commands, writes files, and manipulates firewalls
+- Significantly enhances Guidance recommendations through enhanced statistics
+
+NOTE
+
+The HPE Morpheus Enterprise Agent is required for managed Docker, Kubernetes, SCVMM, Hyper-V, KVM, and ESXi Hosts (for ESXi-only Cloud, not vCenter Clouds).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json b/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
new file mode 100644
index 0000000..b950910
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+  "title": "Maintenance Mode",
+  "ordinal": 186,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html",
+  "topic_cluster": {
+    "clustering_title": "Maintenance Mode",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7",
+        "clustering_title": "Maintenance Mode"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md b/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
new file mode 100644
index 0000000..5b3c302
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.md
@@ -0,0 +1,5 @@
+# Maintenance Mode
+
+HVM cluster hosts can be easily taken out of service for maintenance when needed. From the host detail page, click ACTIONS and then click “Enter Maintenance.” When entering maintenance mode, the host will be removed from the pool. Live VMs that can be migrated will be moved to new hosts. VMs that are powered off will also be moved when possible. When a live VM cannot be moved (such as if it’s “pinned” to the host), the host will not go into maintenance mode until that situation is cleared. You could manually move a VM to a new host or you could power it down if it’s non-essential. After taking that action, attempt to put the host into maintenance mode once again. HPE Morpheus Enterprise UI provides a helpful dialog which shows you which VMs live on the host are to be moved as the host goes into maintenance mode. When maintenance has finished, go back to the ACTIONS menu and select “Leave Maintenance.”
+
+![../../_images/enterMaintenance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-18F5E0CD-4DD0-4720-8DA0-E81B1048013B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json b/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
new file mode 100644
index 0000000..f0049f3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+  "title": "User Settings",
+  "ordinal": 332,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html",
+  "topic_cluster": {
+    "clustering_title": "User Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84",
+        "clustering_title": "User Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md b/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
new file mode 100644
index 0000000..1e2c84c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.md
@@ -0,0 +1,13 @@
+# User Settings
+
+User settings are accessed by clicking on your display name in the far upper-right corner of the application window. In this dropdown menu, click on the “USER SETTINGS” link.
+
+**Subtopics**  
+
+- **[User Photo](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-68E5CB99-152C-463C-9E41-5B2C67C659CD.html)**
+- **[2 Factor Authentication](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html)**
+- **[Preferences](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html)**
+- **[Linux Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-12450828-47CC-4F83-9E94-AF80242C2E3A.html)**
+- **[Windows Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html)**
+- **[API Access](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C366D1B-0426-4F6D-9A1B-CDF97B468FED.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.json b/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
new file mode 100644
index 0000000..244fb35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+  "title": "Node Types",
+  "ordinal": 130,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-75D89535-68AE-4507-A961-26CE8914F074.html",
+  "topic_cluster": {
+    "clustering_title": "Node Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-75D89535-68AE-4507-A961-26CE8914F074",
+        "clustering_title": "Node Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.md b/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
new file mode 100644
index 0000000..b1630e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-75D89535-68AE-4507-A961-26CE8914F074.md
@@ -0,0 +1,96 @@
+# Node Types
+
+Node Types are the link between Images and Layouts.
+
+## Node Type Configuration Options
+
+The following fields are for all Technology types:
+
+Name
+:   Name of the Node Type in HPE Morpheus Enterprise
+
+Short Name
+:   The short name is a lowercase name with no spaces used for display in your container list
+
+Version
+:   Version for the Node Type. Examples: 7.5, 2012 R2, latest
+
+Technology
+:   Select associated Technology. This will filter the available configuration options, images and which Layouts the Node Type can be added to
+
+Environment Variables
+:   Add pre-set environment variables to the Node Type
+
+Category
+:   Node Types of differing categories within the same Layout can have differing sizing
+
+## Technology-Specific Options
+
+The Options fields will change depending on the Technology option selected. For VM provisioning technology options, select an image from the VM Image dropdown. This list is populated from the HPE Morpheus Enterprise Virtual Images section and will include images uploaded into HPE Morpheus Enterprise as well as synced images from added clouds.
+
+NOTE
+
+Amazon and Azure Marketplace Images can be added in the Virtual Images section for use as Node Types in custom library items.
+
+### Docker Options
+
+For Docker, type in the name and version of the Docker Image, then select the integrated registry.
+
+Service Ports
+:   To open ports on the node, enter the name and port to expose. The Load Balancer HTTP, HTTPS, or TCP setting is required when attaching to Load Balancers.
+
+    Defining an Exposed port will also create a hyperlink(s) on the container location (IP) in the VM or Container section of the associated Instance detail page.
+
+Scripts
+:   Search for and select one or multiple scripts to be executed when the Node Type is provisioned
+
+File Templates
+:   Search for and select one or multiple File Templates to be written when the Node Type is provisioned
+
+Example port configuration:
+
+![../../_images/node_ports.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EAA33A7C-4570-4FBD-857C-F9C400D588C2-high.png)
+
+### VMware Options
+
+HPE Morpheus Enterprise supports VMware-specific configurations related to Node Types targeted for VMware vCenter Clouds. Setting the TECHNOLOGY field on the Node Type to “VMware” reveals these fields.
+
+### vApp Properties
+
+Some VMware images may expect the user to provide values for vApp properties related to server configuration. HPE Morpheus Enterprise allows the user to set values for vApp properties on the Node Type, which can be static values or even HPE Morpheus Enterprise variables such as if we wanted to provide the next available IP address from a HPE Morpheus Enterprise IP pool or source a password from HPE Morpheus Enterprise Cypher. Consider the following example workflow for examining an OVA image, uploading it to HPE Morpheus Enterprise as a Virtual Image, and setting vApp properties on the Node Type.
+
+If you have an OVA that doesn’t have the properties laid out in a visible format, you can unzip it and inspect the OVF file to help set the vApp properties in HPE Morpheus Enterprise. For example, take a look at the screenshot below from an OVF file associated with an F5 image. There are four vApp properties I wish to set related to network and user configuration. The `userConfigurable` property should be toggled to `true` for any that may be set to `false`. The key is identified by the `key` property and, if desired, default values can be set via the `value` property. Save any changes to the OVF file.
+
+![../../_images/vappOvf.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-97074F85-A232-4095-9625-CEAF93C468A2-high.png)
+
+With changes saved, the image can be uploaded to HPE Morpheus Enterprise as a Virtual Image from which we can create and configure a Node Type. Below you can see the Virtual Image uploaded and revealed on the Virtual Images list page.
+
+![../../_images/vappVirtualImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-583CAD5E-6A57-49DB-AEAB-704F815F73D7-high.png)
+
+Next, create a new Node Type. After setting the TECHNOLOGY value to “VMware” the fields related to vApp Property configuration will be revealed. Select the uploaded Virtual Image as the “VM IMAGE” and set the key/value pairs in VAPP PROPERTIES. In this case, I’ve dynamically loaded the values using HPE Morpheus Enterprise variables.
+
+![../../_images/vappNodeType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-871C2818-8DD3-478D-ADC4-613602524004-high.png)
+
+The rest of the process is the same as building out any other HPE Morpheus Enterprise library item. House the Node Type within a Layout and the Layout within an Instance Type. It should then be provisionable as any other Instance Type.
+
+### Extra Options
+
+When VMware Technology Type is selected, EXTRA OPTIONS will be available in the VMware VM Options section. These allow defining Advance vmx-file parameters during provisioning.
+
+Some Example include:
+
+```
+```
+tools.setinfo.sizeLimit : 1048576  
+vmci0.unrestricted : FALSE  
+isolation.tools.diskWiper.disable : TRUE
+```
+```
+
+NOTE
+
+Not all parameters can be set using extra config parameters. A sample reference list can be found at <http://www.sanbarrow.com/vmx/vmx-advanced.html#vmx>
+
+IMPORTANT
+
+Use caution when setting Extra Options. Malformed config files can break provisioning. Troubleshooting issues related to Extra Options defined are beyond the scope of HPE Morpheus Enterprise product support.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json b/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
new file mode 100644
index 0000000..5205fd1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+  "title": "Integrations",
+  "ordinal": 531,
+  "parent_title": "See Also",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-768B1CD6-73F8-4CBC-9675-E03000B36147",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md b/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
new file mode 100644
index 0000000..2f7bb06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.md
@@ -0,0 +1,9 @@
+# Integrations
+
+The Integrations section in Library > Integrationsis for adding and managing Automation Integrations. Existing Automation Integrations from Administration > Integrations are also populated and accessible from Library > Integrationsand vice-versa.
+
+`Provisioning: Automation Integrations` and `Admin: Integrations` are separate Role permissions, so Automations Integration access can be separated from the Administration Integrations section.
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json b/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
new file mode 100644
index 0000000..d47ce77
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+  "title": "Azure (Public)",
+  "ordinal": 390,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html",
+  "topic_cluster": {
+    "clustering_title": "Azure (Public)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB",
+        "clustering_title": "Azure (Public)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md b/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
new file mode 100644
index 0000000..aa6455d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.md
@@ -0,0 +1,411 @@
+# Azure (Public)
+
+## Overview
+
+Morpheus offers a complete Integration with Microsoft Azure including the following:
+
+- Virtual Machine Sync, Create, Delete, Manage, RBAC, Tenant Permissions, Policies
+- Resource Group Sync, Create, Delete, RBAC, Tenant Permissions
+- Network Sync, Create, Delete, RBAC, Tenant Permissions
+- Subnet Sync, Create, Delete, RBAC, Tenant Permissions
+- Security Group Sync, Create, Delete, Tenant Permissions
+- Security Group Rule Sync, Create, Delete, Tenant Permissions
+- ARM Blueprints, Spec Templates, Deployment Logs Sync, Git/GitHub Integration
+- MSSQL Service Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- AKS Sync, Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Backup Create, Delete, Manage, RBAC, Policies
+- Storage Sync, Create, Delete, Manage, Browse, RBAC, Tenant Permissions, Policies
+- Marketplace Sync
+- Private Image Sync & Upload
+- Azure Marketplace Custom Library Item Support
+- Remote Console (SSH & RDP)
+- Lifecycle Management
+- Availability Set Support
+- Scale Set Sync, Create, Assign, Manage, Delete
+- Azure Load Balancer Create, Assign, Manage, Delete, RBAC, Tenant Permissions
+- Docker (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Kubernetes (VM) Cluster Sync, Create, Delete, Manage, RBAC, Tenant Permissions
+- Service Plan Sync, Tenant Permissions, RBAC
+- Pricing Sync RBAC, Tenant Permissions, Markup
+- Costing Sync, Reporting, Invoicing
+- Reservations Sync, Guidance Recommendations
+- Azure Stack Support
+- Tag Bi-Directional Sync, Creation, Deletion Policy Enforcement
+- Cost Estimator
+- Azure US Gov Support
+- Azure China Support
+- Azure Germany Support
+- CSP Account Support
+
+## Requirements
+
+Morpheus Azure Integration requires Owner or Contributor access to subscription via App Registration. Adding an Azure Cloud or Clouds to HPE Morpheus Enterprise will require the following:
+
+- Azure Subscription ID
+- Directory (tenant) ID
+- Application (client) ID
+- Application (client) Secret
+- Application (client) must be Owner or Contributor of Subscription
+
+CSP Accounts require the additional following input:
+
+- CSP Directory (tenant) ID
+- CSP Application (client) ID
+- CSP Application (client) SECRET (Web App Key)
+
+The HPE Morpheus Enterprise appliance requires outbound HTTPS (443) access to the Azure endpoints. Depending on the type of cloud you choose when adding Azure, ensure the proper endpoints are allowed:
+
+**Global Azure Cloud**
+:   - <https://management.core.windows.net> (ServiceManagementUrl)
+    - <https://management.azure.com> (ResourceManagerUrl)
+    - <https://login.microsoftonline.com> (ActiveDirectoryAuthority)
+
+**US Gov Cloud**
+:   - <https://management.core.usgovcloudapi.net> (ServiceManagementUrl)
+    - <https://management.usgovcloudapi.net> (ResourceManagerUrl)
+    - <https://login.microsoftonline.us> (ActiveDirectoryAuthority)
+
+**Germany Cloud**
+:   - <https://management.core.cloudapi.de> (ServiceManagementUrl)
+    - <https://management.microsoftazure.de> (ResourceManagerUrl)
+    - <https://login.microsoftonline.de> (ActiveDirectoryAuthority)
+
+**China Cloud**
+:   - <https://management.core.chinacloudapi.cn> (ServiceManagementUrl)
+    - <https://management.chinacloudapi.cn> (ResourceManagerUrl)
+    - <https://login.chinacloudapi.cn> (ActiveDirectoryAuthority)
+
+## Credentials & Permissions
+
+Morpheus authenticates with Azure via an App Registration with an Owner or Contributor Role on a Subscription. Use the steps below to create and collect the required credentials and assign the required permissions to integrate Azure with HPE Morpheus Enterprise.
+
+WARNING
+
+Using an App Registration (service principal) that has selective resource permissions and is not an Owner or Contributor of the Subscription is not supported and will cause failures/issues. Please confirm the App Registration you use to integrate Azure with Morpheus has Owner or Contributor permissions on the specified Subscription before contacting support.
+
+### Create an App Registration
+
+#### About this task
+
+If you do not have an existing Azure Active Directory App Registration, or you wish to use an new one for HPE Morpheus Enterprise, you will need to create one.
+
+TIP
+
+If you can’t find sections of the Azure portal discussed in this integration guide, such as App Registrations or Subscriptions, you may be able to find them under the “Favorites” section within the main hamburger menu, at the “All Resources” page from within the main hamburger menu, or by using the global search bar.
+
+#### Procedure
+
+1. Log into the Azure web console
+2. Select “App Registrations”, you may have to go to the “All Services” page to find it 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E7EF3195-082B-46D5-BE32-590BA7644633-high.png)
+3. Click “+ New registration” 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B7FEBDD8-32CB-479A-B49C-82A8F817992B-high.png)
+4. Next, give app a name, specify which accounts may access this API, specify Web for the Redirect URI type and enter any url for the Sign-on URL:
+5. Click Register and your new App Registration will be created. 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F16A233F-1112-4341-A19D-97F5B91E2A10-high.png)
+
+#### Results
+
+Now that we have (or already had) our App Registration, we will gather the credentials required for the HPE Morpheus Enterprise Azure integration.
+
+### Copy Directory (tenant) and Application (client) IDs
+
+#### About this task
+
+The App Registration Directory (tenant) and Application (client) ID are required for the HPE Morpheus Enterprise Azure integration. Both can be found in the overview section of the App Registration.
+
+#### Procedure
+
+1. Go to the Overview section of your App Registration
+2. Copy the Directory (tenant) ID
+3. Store/Paste for use as the Tenant ID when Adding your Azure cloud in HPE Morpheus Enterprise
+4. Copy the Application (client) ID
+5. Store/Paste for use as the Client ID when Adding your Azure cloud in HPE Morpheus Enterprise 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-663FA392-839D-43E5-8C32-C50055985BCD-high.png)
+
+### Generate a Client Secret
+
+#### About this task
+
+While still in your App Registration:
+
+#### Procedure
+
+1. Select Certificates & secrets in the Manage Section
+2. Select `+ New client secret` 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B699A18D-B220-488B-989E-B67C83E2AA67-high.png)
+3. The “Add a client secret” modal will come up
+4. Add a description to help identify the secret in the future
+5. Select a duration
+6. Select Add 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-20277A74-BFD7-42BA-87B7-B249CAC4E4DD-high.png)
+7. Copy the newly generated Client Secret Value. It is important to copy the Client Secret Value now as it will not be displayed/available 
+
+   IMPORTANT
+
+   Copy the key value before continuing as it will not be displayed/available again.
+8. Store/Paste for use as the Client Secret when Adding your Azure cloud in HPE Morpheus Enterprise
+
+#### Results
+
+You now have 3 of the 4 credentials required for HPE Morpheus Enterprise Azure cloud integration. The last credential required is the Azure Subscription ID.
+
+### Subscription ID
+
+#### About this task
+
+To get the Azure Subscription ID:
+
+#### Procedure
+
+1. Navigate to the main Subscriptions section. One way is to search for “Subscriptions” and select Subscriptions in the search results
+2. In the main “Subscriptions” section, copy the Subscription ID 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4B40A8B2-3C59-4AE4-8980-1DA3A3786918-high.png)
+3. Store/Paste for use as the Subscription ID when Adding your Azure cloud in HPE Morpheus Enterprise
+
+### Make App Registration owner or contributor of Subscription
+
+#### About this task
+
+The App Registration created/used needs to be an owner of the Azure Subscription used for the HPE Morpheus Enterprise cloud integration. If lesser permissions are given or permissions are assigned at individual resource levels, HPE Morpheus Enterprise will not be able to properly inventory/sync, create and/or remove resources.
+
+#### Procedure
+
+1. In the main Subscriptions section, click on the name of the Subscription
+2. With the Subscription detail open, select “Access Control (IAM)”
+3. Click “+ ADD” and then click “Add role assignment” from the pop-out menu 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8812BC0F-33DB-4F3D-8399-7EC297A6DC2E-high.png)
+4. Click on the tab for “Privileged administrator roles”
+5. Select Owner or Contributor and click “Next”
+6. Add Members to the Role Assignment by clicking “+ Select members”
+7. Select the App Registration from the search results and click Select 
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-24AA7305-E9B5-428A-8FAE-ABC8F17CAE2E-high.png)
+8. Click “Review + Assign”
+
+## Add an Azure Cloud Integration
+
+### About this task
+
+To add a new Azure Cloud integration into HPE Morpheus Enterprise using the credentials created/collected from the previous section, perform the following:
+
+### Procedure
+
+1. In HPE Morpheus Enterprise, navigate to Infrastructure > Clouds and select + ADD 
+
+   ![../../../_images/Clouds_Morpheus_Add.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DC3EC6CE-40F3-4AFA-9B6E-5CCAFE1DC9DE-high.png)
+2. Select “AZURE (PUBLIC)” from the Cloud Types list and click NEXT 
+
+   ![../../../_images/Clouds_Morpheus1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4F7C2657-7339-46B0-82DB-A517DB5B0D73-high.png)
+3. Populate the Following 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   CLOUD TYPE
+   :   - Global (Azure Cloud)
+       - US Gov (Azure US Government)
+       - German (Azure German Cloud)
+       - China (Azure China Cloud)
+
+   SUBSCRIPTION ID
+   :   The target Azure Subscription ID obtained from the previous section
+
+   TENANT ID
+   :   The Directory (tenant) ID obtained from the previous section
+
+   CREDENTIALS
+   :   If available, select a pre-stored Client ID and Client Secret set. Alternatively, select “Local Credentials” to enter the Client ID and Client Secret without storing them for later access. “client id and secret” under the “New Credentials” heading can also be selected so your Client ID and Client Secret will stored for later use in either the HPE Morpheus Enterprise credential store or in an integrated third party secret store
+
+   CLIENT ID
+   :   The Application (client) ID obtained from the previous section
+
+   CLIENT SECRET
+   :   The Application (client) Secret obtained from the previous section
+
+   LOCATION
+   :   Once valid credentials are populate above and HPE Morpheus Enterprise is able to successfully authenticate with Azure, the available locations/regions will populate.
+
+   REGION
+   :   Scope the Cloud to either “All” regions or a selected Azure region
+
+   RESOURCE GROUP
+   :   - Select “All” to scope the Cloud to all available Resource Groups in the specified location/region.
+       - Select a single Resource Group to limit HPE Morpheus Enterprise resource creation, selection and discovery to just this Resource Group.
+
+   INVENTORY EXISTING INSTANCES
+   :   Check to enable discovery/inventory of existing VM’s in the scoped Region and Resource Group(s)
+
+   ACCOUNT TYPE
+   :   Standard, EA or CSP
+
+       NOTE
+
+       For CSP Accounts, also enter CSP TENANT ID, CSP CLIENT ID and CSP CLIENT SECRET in the Advanced Options section. In order to enable cost sync for CSP accounts, the “CSP CUSTOMER” checkbox must be marked and “COSTING” should be set to “Costing” rather than “Costing and Reservations”.
+
+       For the CSP Client Secret, enter the Web App Key rather than the Native App Key. This should be accessed from the Microsoft Partner Center rather than the Azure web console. If this is not, Plans may sync but Price Sets and Prices would not.
+
+       ![../../../_images/addAzureCloudMorpheusS1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B917D3E3-342A-4DB9-9377-A0F20BB69D1F-high.png)
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+   AZURE COSTING MODE
+   :   Standard, CSP, or Azure Plan
+
+       Example configurations but choose what is applicable to the tenant:
+
+       Table 1. Example Azure Costing Configurations
+
+            | Account Type | Azure Costing Mode | Notes |
+       | --- | --- | --- |
+       | Standard (Pay as you go) | Standard |  |
+       | EA (Enterprise Agreement) | Standard |  |
+       | CSP (Cloud Solution Provider) | CSP | CSP Tenant, ID, Client ID, and Client Secret required |
+       | CSP (Cloud Solution Provider) | Azure Plan (Microsoft Customer Agreement) | CSP Tenant, ID, Client ID, and Client Secret required on the primary cloud |
+4. Once done configuring the Cloud, select NEXT. NOTE all specified values except the Subscription ID can be changes after the Cloud is created.
+5. Next select an existing Group to add the Azure Cloud to, or create a new Group, then select NEXT 
+
+   ![../../../_images/Clouds_MorpheusAddGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6C5E021D-A3B6-4AE2-9A7E-A7E1FD6A001C-high.png)
+6. Review the configuration and then select COMPLETE 
+
+   ![../../../_images/Clouds_MorpheusComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-57620E9D-45F0-4D5E-AEAB-F5496EDF994F-high.png)
+
+### Results
+
+Your new Azure Cloud integration will be created and begin to sync.
+
+NOTE
+
+The initial sync of an Azure Cloud can take some time due to Marketplace data sync.
+
+![../../../_images/Clouds_MorpheusNewCloudAdded.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E14BF630-7826-4A29-A728-7EE6BCEA365F-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json b/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
new file mode 100644
index 0000000..9d58aca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+  "title": "HVM Clusters",
+  "ordinal": 174,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.html",
+  "topic_cluster": {
+    "clustering_title": "HVM Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF",
+        "clustering_title": "HVM Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md b/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
new file mode 100644
index 0000000..d8c1377
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-76D7FB26-B201-4FB1-ABEF-B8BE590904CF.md
@@ -0,0 +1,14 @@
+# HVM Clusters
+
+An HVM cluster is a hypervisor clustering technology utilizing KVM. Beginning with just a few basic Ubuntu boxes, HPE Morpheus Enterprise can create a cluster of hypervisor hosts complete with monitoring, failover, easy migration of workloads across the cluster, and zero-downtime maintenance access to hypervisor host nodes. All of this is backed by HPE Morpheus Enterprise Tenant capabilities, a highly-granular RBAC and policy engine, and Instance Type library with automation workflows.
+
+**Subtopics**  
+
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html)**
+- **[Base Cluster Details](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html)**
+- **[Provisioning the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html)**
+- **[Provisioning a Workload](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html)**
+- **[Image Prep (Windows)](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html)**
+- **[Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html)**
+- **[Hypervisor Console Keyboards](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.json b/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
new file mode 100644
index 0000000..71078b7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+  "title": "GKE Clusters",
+  "ordinal": 201,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-77287C89-E688-49C4-869F-652DE15478FB.html",
+  "topic_cluster": {
+    "clustering_title": "GKE Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-77287C89-E688-49C4-869F-652DE15478FB",
+        "clustering_title": "GKE Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.md b/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
new file mode 100644
index 0000000..f7ba949
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-77287C89-E688-49C4-869F-652DE15478FB.md
@@ -0,0 +1,69 @@
+# GKE Clusters
+
+Provisions a new Google Kubernetes Engine (GKE) Cluster in target Google Cloud.
+
+NOTE
+
+Ensure proper permissions exist for the Google Clouds service account to create, inventory and manage GKE clusters.
+
+## Create an GKE Cluster
+
+### Procedure
+
+1. Navigate to `Infrastructure - Clusters`
+2. Select + ADD CLUSTER
+3. Select `GKE Cluster`
+4. Populate the following: 
+
+   CLOUD
+   :   Select target Cloud
+
+   CLUSTER NAME
+   :   Name for the GKE Cluster
+
+   RESOURCE NAME
+   :   Name for GKE Cluster resources/hosts
+
+   DESCRIPTION
+   :   Description of the Cluster
+
+   VISIBILITY
+   :   Public
+       :   Available to all Tenants
+
+       Private
+       :   Available to Master Tenant
+
+   LABELS
+   :   Internal label(s)
+
+   LAYOUT
+   :   Select cluster layout for GKE Cluster
+
+   RESOURCE POOL
+   :   Specify an available Resource Pool from the selected Cloud
+
+   GOOGLE ZONE
+   :   Specify Region for the cluster
+
+   VOLUMES
+   :   Cluster hosts volume size and type
+
+   NETWORKS
+   :   Select GCP subnet(s) and config
+
+   WORKER PLAN
+   :   Service Plan for GKE worker nodes
+
+   RELEASE CHANNEL
+   :   Regular, Rapid, Stable or Static
+
+   CONTROL PLANE VERSION
+   :   Select from available synced GKE k8’s versions
+
+   NUMBER OF WORKERS
+   :   Number of worker nodes to be provisioned
+5. Select NEXT
+6. Select optional Workflow to execute
+7. Select NEXT
+8. Review and select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json b/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
new file mode 100644
index 0000000..38abbc1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+  "title": "Costing: Group Costing",
+  "ordinal": 59,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Group Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA",
+        "clustering_title": "Costing: Group Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md b/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
new file mode 100644
index 0000000..3254eb7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.md
@@ -0,0 +1,32 @@
+# Costing: Group Costing
+
+![../_images/2groupcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BC2102C2-6D1A-4EC2-8F51-173EAE0CE091-high.png)
+
+The Group Costing dashboard aggregates cost totals for all Groups that meet filters set on the dashboard. This allows administrators to sort Groups by their total costs and anticipate monthly total costs by Group.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- Group (all matched by search)
+- Group (selected from dropdown)
+- Cloud
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Groups that meet set filters:
+
+- **GROUPS:** The total number of Groups that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Groups meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Groups meeting dashboard filters
+
+## Group List
+
+Each Group that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Group:
+
+- **NAME:** The name given to the Group in HPE Morpheus Enterprise at the time of creation
+- **LOCATION:** The Group location (if available)
+- **DATACENTER:** The Group datacenter (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Group listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Group listed
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.json b/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
new file mode 100644
index 0000000..4fd5355
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+  "title": "Provisioning into OpenShift",
+  "ordinal": 209,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning into OpenShift",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-786D5554-1448-4001-A39C-647F22CA9278",
+        "clustering_title": "Provisioning into OpenShift"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.md b/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
new file mode 100644
index 0000000..d42cbf0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-786D5554-1448-4001-A39C-647F22CA9278.md
@@ -0,0 +1,31 @@
+# Provisioning into OpenShift
+
+In addition to adding a new cluster type (as covered in the previous sections), the HPE Morpheus Enterprise OpenShift plugin also adds the "OpenShift" Instance Type to the provisioning wizard. Through this, new virtualized Instances can be provisioned to the OpenShift cluster. Use the following steps to provision a new virtual machine into the cluster.
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select OPENSHIFT and click NEXT
+4. On the Group tab, select a Group and Cloud. These selections will be filtered to include only Groups which can access Clouds that contain OpenShift clusters
+5. Still on the Group tab, provide a Name for the new Instance and click NEXT
+6. On the Configure tab, set the following configurations:
+
+   - Layout: The "Openshift VM" Layout is included by default. Additional Layouts can be created within the Blueprints section (Library > Blueprints > Layouts) by selecting the "Openshift" Layout technology and associating the Layout with the "Openshift" Instance Type. See the Blueprints section of this user manual for more information on building Library items
+   - Plan: Plans of various sizes and levels of customizability can be created in Administration > Plans & Pricing. By default, a single Plan specifying 2 CPU cores and 4 GB memory is seeded when adding the plugin
+   - Resource Pool: Select the desired OpenShift cluster
+   - Volumes: Select the proper number and size volumes
+   - Networks: Networks correspond to NetworkAttachedDefinitions (NADs) in OpenShift. This list includes all NADs and names them by "<namespace>/<NAD name>" to make it easier to select a network within the intended namespace (Project). Users may select multiple NADs while provisioning but they must be from the same namespace
+
+     IMPORTANT
+
+     The first network interface chosen as part of Instance deployment will be treated as the primary interface and is expected to be reachable from the HPE Morpheus Enterprise appliance.
+   - Image: Select from all synced virtual images. Note that only custom user images are synced from OpenShift, we do not sync from the large library of default images that ship with OpenShift
+   - Project: Select the proper namespace. Bear in mind it's currently up to the user to select a valid namespace based on the network selected. If you choose an invalid namespace for the chosen network, provisioning will fail. In the future, this select list may provide automatic filtering to prevent invalid configuration but, for now, the user must make a valid selection
+7. Still on the Configure tab, other configurations common to many Instance Types can also be made. When finished, click NEXT
+8. On the Automation tab, choose to run automation Tasks or associate Workflows with the new Instance. Other common automation configurations can also be made, such as scale or backup configurations. Click NEXT
+9. On the Review tab, click COMPLETE
+
+The new OpenShift VM will soon be running based on the configurations given. Its status can be monitored from the OpenShift cluster detail page discussed in the previous section or from the Instances list page.
+
+NOTE
+
+Instance/VM console access is only supported if the VM is available on the network and reachable by HPE Morpheus Enterprise over the SSH port for Linux or the RDP port for Windows.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json b/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
new file mode 100644
index 0000000..b4d3ad6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+  "title": "OneLogin",
+  "ordinal": 285,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html",
+  "topic_cluster": {
+    "clustering_title": "OneLogin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-78DC62BA-524C-456D-827F-465C10A1AA6F",
+        "clustering_title": "OneLogin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md b/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
new file mode 100644
index 0000000..99e67fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.md
@@ -0,0 +1,43 @@
+# OneLogin
+
+By integrating OneLogin with HPE Morpheus Enterprise, users can access HPE Morpheus Enterprise with their existing credentials set up within the OneLogin platform. Additionally, administrators can manage user access including Role assignment and enabling or disabling users from within the OneLogin platform. As employees are onboarded, change positions, or leave the company, additional user management within the HPE Morpheus Enterprise platform is not necessary.
+
+## Adding OneLogin Identity Source Integration
+
+To begin, log into OneLogin with an administrator account to gather some needed pieces of information. From the top menu bar, select Administration. From the admin panel, click Developers > APICredentials. Click the button labeled “New Credential”. Provide a name for the new API credentials and select “Manage Users” as the permissions type. Store the credentials somewhere they can be retrieved in the next step.
+
+![../../_images/oneLoginKey.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3244CCDD-7F2B-4DF3-B4E6-4BA4B0686C60-high.png)
+
+Back in HPE Morpheus Enterprise, navigate to the Tenant which will integrate with OneLogin. Identity providers are integrated on a per-Tenant basis in HPE Morpheus Enterprise. From the selected Tenant, click IDENTITY SOURCES. The list of currently-integrated identity providers is here. Click + ADD IDENTITY SOURCE to start a new integration for OneLogin. Fill in the fields below:
+
+- **TYPE:** OneLogin
+- **NAME:** A name for the identity source integration in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the identity source
+- **ONELOGIN SUBDOMAIN:** The subdomain from your OneLogin portal URL. For example, “morpheus-dev” if your portal is accessed at morpheus-dev.onelogin.com. Incorrect subdomains will cause login attempts to HPE Morpheus Enterprise to fail
+- **ONELOGIN REGION:** Specify US or EU region
+- **API CLIENT SECRET:** OneLogin API client secret which was gathered earlier in this walkthrough
+- **API CLIENT ID:** OneLogin API client ID which was gathered earlier in this walkthrough
+- **REQUIRED ROLE:** Enter a role which OneLogin users logging into HPE Morpheus Enterprise must have to gain access to HPE Morpheus Enterprise
+- **DEFAULT ROLE:** The default HPE Morpheus Enterprise Role applied to users created from the OneLogin integration if no other role mapping is specified in other Role Mappings fields
+- **ROLE MAPPINGS:** All existing HPE Morpheus Enterprise Roles will be listed with fields to enter OneLogin Roles to create a mapping. Users with OneLogin roles matching the role mappings will be assigned the appropriate Role(s) in HPE Morpheus Enterprise when signing in
+- **ENABLE ROLE MAPPING PERMISSION:** When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the core integration fields (such as the API keys)
+- **MANUAL ROLE ASSIGNMENT:** When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+Select SAVE CHANGES and the OneLogin Integration will be added.
+
+Users can now login to HPE Morpheus Enterprise with OneLogin credentials. The first login will create a user in HPE Morpheus Enterprise matching the username, email and password from OneLogin. If a REQUIRED ROLE is specified in the Identity Source settings, only users with that Role in OneLogin will be able to login to HPE Morpheus Enterprise.
+
+IMPORTANT
+
+OneLogin users will not authenticate in HPE Morpheus Enterprise if there is an existing HPE Morpheus Enterprise User with matching username or email address.
+
+You can now test the integration by logging in with user credentials which have been configured in OneLogin. On the first login, a new user will be created with the same username, email address, and password as contained in OneLogin. On subsequent logins, HPE Morpheus Enterprise will sync with OneLogin to make sure the user hasn’t been disabled or if its Role(s) have changed in OneLogin which would affect its corresponding Roles in HPE Morpheus Enterprise.
+
+The HPE Morpheus Enterprise identity source integration is interacting with the OneLogin APIs in the list below. This reference may be needed to ensure HPE Morpheus Enterprise is integrating using an API key with sufficient privileges. In a situation where troubleshooting is needed, first confirm these APIs can be accessed using the provided key.
+
+- `/auth/oauth2/token` - Generate Token
+- `/api/1/users/$user_id/roles` - Get Roles
+- `/api/1/login/auth` - Create Session
+- `/api/1/users/$user_id` - Get User
+- `/api/1/roles/$role_id` - Get Role
+- `/api/1/roles?name=$role_name` - Find Role
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json b/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
new file mode 100644
index 0000000..09d801d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+  "title": "Capacity: Capacity Planning",
+  "ordinal": 66,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity: Capacity Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F",
+        "clustering_title": "Capacity: Capacity Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md b/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
new file mode 100644
index 0000000..0cb85a6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.md
@@ -0,0 +1,9 @@
+# Capacity: Capacity Planning
+
+![../_images/capacityPlanning.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-54937FF3-952A-40DE-8C06-8E193416776A-high.png)
+
+The capacity planning dashboard shows both realtime use and predicted future use in key metrics of memory, storage and CPU use over a pre-defined period. Choose to show this across the entire appliance (all Tenants and Clouds) or scoped to just a single Tenant or a single Cloud. This can help to plan for future hardware needs, plan for changing public Cloud spend, or identify over/under utilization of certain resources.
+
+## Filters
+
+Leave unfiltered to show data across all Tenants and Clouds. Optionally choose to filter down to all Clouds in one specific Tenant or a single Cloud. The trend line predicts future use of resources based on recent past utilization.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json b/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
new file mode 100644
index 0000000..d1d24ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+  "title": "Agent Install Methods",
+  "ordinal": 47,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Install Methods",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE",
+        "clustering_title": "Agent Install Methods"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md b/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
new file mode 100644
index 0000000..0c4dcc4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.md
@@ -0,0 +1,100 @@
+# Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+## For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+## SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+## WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+## VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+## Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+## Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+## Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+## Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json b/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
new file mode 100644
index 0000000..4171538
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+  "title": "Key Features",
+  "ordinal": 398,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.html",
+  "topic_cluster": {
+    "clustering_title": "Key Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099",
+        "clustering_title": "Key Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md b/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
new file mode 100644
index 0000000..6bd9df8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A6944E8-6B89-48A1-8C76-4D9E21EB5099.md
@@ -0,0 +1,106 @@
+# Key Features
+
+HPE BMaaS for Morpheus Enterprise provides centralized discovery, provisioning, lifecycle management, and monitoring for HPE ProLiant bare-metal infrastructure. The key features of HPE BMaaS are as follows:
+
+- Automated Server Discovery and Inventory
+
+  - Server Import: Imports HPE ProLiant servers into Morpheus using iLO IP addresses and credentials.
+  - Hardware Inventory Discovery: Automatically collects detailed hardware data, including:
+
+    - Server model and generation
+    - CPU, memory, and storage configurations
+    - Network interfaces and adapters
+    - Firmware and driver versions
+  - Service Plan Mapping: Maps discovered hardware to Morpheus Service Plans to align metering, consumption tracking, and billing.
+  - Metadata Management: Maintains updated server metadata to ensure operational visibility and support capacity planning.
+- Resource Pool and Bare Metal Cloud Management
+
+  - Create a Bare Metal Cloud per tenant to represent dedicated HPE ProLiant infrastructure.
+  - Organize servers within the cloud into Resource Pools for multi-site deployments and infrastructure segmentation.
+  - Allocate servers to specific groups, environments, or use cases.
+  - Apply policies, access control, and governance at the cloud or resource pool level.
+- Bare Metal Instance Provisioning
+
+  - Provision bare metal instances directly from available HPE ProLiant servers.
+  - Support for:
+
+    - Local disk RAID configuration during deployment
+    - Automated OS installation
+    - Post-install configuration and customization
+  - Associate instances with user-defined groups, clouds, and resource pools.
+- Operating System Deployment
+
+  - Deploy Windows Server and Linux operating systems using ISO images stored in the Morpheus Virtual Image Library.
+  - Supported unattended installation mechanisms:
+
+    - Windows Setup (AutoUnattend)
+    - RHEL / Oracle Linux Kickstart
+    - Ubuntu Autoinstall (cloud-init)
+  - Consistent and repeatable OS deployments across environments.
+- Image Management
+
+  - Centralized catalog of bootable OS images.
+  - Support for multiple image storage backends:
+
+    - Storage > File Shares
+
+      - CIFS (Samba Windows File Sharing): Windows-compatible network file sharing
+      - Local Storage: Direct storage on the server
+      - Network File System version 3 (NFSv3): Linux network file sharing
+    - Storage > Buckets
+
+      - S3-compatible object storage (for example, using MinIO): Object storage through S3 API
+    - Images can be reused across multiple provisioning workflows.
+- Greenfield (New Server) Provisioning
+
+  - Provision brand-new, unconfigured HPE ProLiant servers into Morpheus-managed bare metal instances.
+  - Perform full end-to-end lifecycle automation, including:
+
+    - Server discovery
+    - Power control and boot orchestration
+    - RAID and storage configuration
+    - Network configuration
+    - Operating system deployment
+  - Enable zero-touch deployment from factory-fresh hardware to production-ready servers.
+  - Ensure consistent, repeatable provisioning aligned with organizational standards.
+- Brownfield (Pre-Provisioned Server) Import
+
+  - Import existing physical servers into Morpheus as Pre-Provisioned resources
+  - Convert imported servers into fully managed Morpheus instances.
+  - Add additional imported servers as nodes to an existing instance.
+- Firmware and Driver Lifecycle Management
+
+  - Execute firmware and driver inventory and updates using HPE Service Pack for ProLiant (SPP).
+  - Run updates through Morpheus Jobs and Workflows.
+  - Target firmware only, drivers only, or both.
+  - Support for:
+
+    - Dry Run (inventory only)
+    - Deploy (apply updates)
+- Monitoring and Metering
+
+  - Monitor real-time hardware health and operational status through iLO integration.
+  - Surface system alerts and hardware events inside HPE Morpheus Enterprise.
+  - Meter resource consumption for reporting and charge-back or show-back.
+- Networking Integration
+
+  - Automated VLAN and switch port configuration in managed mode.
+  - Flexible network attachment to physical or bonded interfaces.
+  - Support for:
+
+    - Unmanaged networks
+    - Managed networks using HPE Aruba CX switches
+- Storage Integration
+
+  - Use local server storage for OS installation.
+  - Integrate with HPE Alletra MP storage arrays for remote SAN volumes.
+  - Create, attach, detach, resize, and delete volumes from HPE Morpheus Enterprise.
+- Integration with Morpheus Core Platform Capabilities
+
+  Bare metal instances benefit from native Morpheus platform features, including:
+  - SSH and RDP access
+  - Morpheus agent (morphd) deployment
+  - Workflow automation and lifecycle scripts
+  - Policy-based governance
+  - Role-based access control
+  - Multi-group and multi-cloud support
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json b/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
new file mode 100644
index 0000000..5924fcd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+  "title": "Single Node Installation",
+  "ordinal": 16,
+  "parent_title": "Installation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html",
+  "topic_cluster": {
+    "clustering_title": "Single Node Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1",
+        "clustering_title": "Single Node Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md b/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
new file mode 100644
index 0000000..33d9721
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.md
@@ -0,0 +1,439 @@
+# Single Node Installation
+
+## Single Node Install Overview
+
+In a Single Host/All-in-one configuration, all components required for Morpheus are automatically installed and configured during the Morpheus `reconfigure` command.
+
+![../../../_images/morpharchSingleV3.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37BE6AA0-10E5-4D0D-BCC1-0834A578B1EC-high.png)
+
+Appliance Host
+:   - Application
+      :   - Morpheus App
+    - Web Server/Proxy
+      :   - NGINX
+    - Database
+      :   - MySQL
+    - Messaging
+      :   - RabbitMQ
+    - Search
+      :   - Opensearch
+    - Console
+      :   - Guacamole
+    - Monitoring
+      :   - Check Server
+
+### Default Paths
+
+HPE Morpheus Enterprise follows several install location conventions. Below is a list of the system paths.
+
+IMPORTANT
+
+Altering the default system paths is not supported and may break functionality.
+
+- Installation Location: `/opt/morpheus`
+- Log Location: `/var/log/morpheus`
+
+  - Morpheus-UI: `/var/log/morpheus/morpheus-ui`
+  - MySQL: `/var/log/morpheus/mysql`
+  - NginX: `/var/log/morpheus/nginx`
+  - Check Server: `/var/log/morpheus/check-server`
+  - OpenSearch: `/var/log/morpheus/opensearch`
+  - RabbitMQ: `/var/log/morpheus/rabbitmq`
+- User-defined install/config: `/etc/morpheus/morpheus.rb`
+
+## Single Node Install on CentOS
+
+NOTE
+
+Appliance Package links are available at <https://app.morpheushub.com> in the downloads section.
+
+### Quick Install
+
+#### Procedure
+
+Install the Appliance package and run `sudo morpheus-ctl reconfigure`.
+
+#### Results
+
+That is it. After the reconfigure completes, HPE Morpheus Enterprise will start and be available at `https://your_machine_name` in a minute or few.
+
+### Step-by-step Install Instructions
+
+#### Procedure
+
+1. Ensure the HPE Morpheus Enterprise Appliance host meets the minimum [requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)
+2. Download the target version `.rpm` package for installation in a directory of your choosing. The package can be removed after successful installation. 
+
+   ```
+   ```
+   wget https://www.hpe.com/support/hpesc/path/to/morpheus-appliance-$version.rpm
+   ```
+   ```
+3. Validate the package checksum matches source checksums. For example: 
+
+   ```
+   ```
+   sha256sum morpheus-appliance-$version.rpm
+   ```
+   ```
+4. Next install the rpm package 
+
+   ```
+   ```
+   sudo rpm -ihv morpheus-appliance-x.x.x-1.x86_64.rpm
+   ```
+   ```
+5. By default the appliance\_url uses the machines hostname, ie `https://your_machine_name`. The default url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. Additional Appliance configuration options are available below. 
+
+   Appliance Configuration Options
+
+   Morpheus allows for additional advanced customizations for system managed services within the morpheus.rb file located in `/etc/morpheus/morpheus.rb`. Below is a list of the supported items available in the `morpheus.rb` file.
+
+   NOTE
+
+   Service configuration settings are not applicable for externalized services such as external MySQL, Opensearch or RabbitMQ clusters. Only connection settings are applicable for external services. Additionally, to configure HPE Morpheus Enterprise to utilize alternate ports for SSL, you may have to take additional configuration steps if simply appending a port to your `appliance_url` value doesn’t work.
+
+   ```
+   ```
+   app['encryption_key_suffix'] = '$suffix'  
+     # Replace $suffix with the suffix string of your choice. See `https://docs.morpheusdata.com/en/latest/getting_started/additional/encryption.html` for important details and warnings.  
+   appliance_url 'https://morpheus.appliance-url.com'  
+     # Appending alternate port to appliance_url is supported. ie 'https://morpheus.appliance-url.com:8443'  
+     # The appliance_url cannot exceed 64 characters  
+     # The appliance_url must not contain a trailing `/`.  
+   bitcan['backup_directory'] = '/var/opt/morpheus/bitcan/backups'  
+   bitcan['working_directory'] = '/var/opt/morpheus/bitcan/working'  
+   opensearch['auth_password'] = 'xxxxxxxxxxxxxxxx'  
+   opensearch['auth_user'] = 'morpheus-es-user'  
+   opensearch['enable'] = true  
+   opensearch['es_hosts'] = {'127.0.0.1' => 9200}  
+   opensearch['host'] = "127.0.0.1"  
+   opensearch['port'] = "9200"  
+   opensearch['tmp_dir'] = '/var/tmp/opensearch'  
+   opensearch['use_tls'] = false  
+   ↓ The following opensearch settings are only valid for Internal/Embedded opensearch services  
+   opensearch['log_dir'] = '/var/log/morpheus/opensearch'  
+   opensearch['memory_alloc_arena_max'] = 2  
+   opensearch['memory_map_max'] = 65536  
+   opensearch['memory_map_threshold'] = 131072  
+   opensearch['memory_top_pad'] = 131072  
+   opensearch['memory_trim_threshold'] = 131072  
+   opensearch['open_files'] = 204800  
+   opensearch['secure_mode'] = false  
+   opensearch['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   opensearch['xmx'] = 0.25  
+   guacd['guacamole_enabled'] = false  
+   guacd['host'] = localhost #### The host guacd is listening on, if not configured 'localhost' is the default value  
+   logging['svlogd_num'] = 30 #### keep 30 rotated log files  
+   logging['svlogd_size'] = 209715200 #### 200 MB in bytes  
+   logging['svlogd_timeout'] = 86400 #### rotate after 24 hours in seconds  
+   mysql['enable'] = true  
+   mysql['host'] = {'127.0.0.1' => 3306}  
+   mysql['use_tls'] = false  
+   mysql['morpheus_db_user'] = 'morpheus-db-user'  
+   mysql['morpheus_password'] = 'morpheus-db-password'  
+   mysql['morpheus_db'] = 'xxxxxxxxxxxxxxxx'  
+   mysql['mysql_url_overide'] = 'jdbc:mysql://10.30.20.10:3306,10.30.20.11:3306,10.30.20.12:3306/morpheusdb?autoReconnect=true&useUnicode=true&characterEncoding=utf8&failOverReadOnly=false&useSSL=false'  
+   ↓ The following mysql settings are only valid for Internal/Embedded mysql services  
+   mysql['tmp_dir'] = '/tmp/mysql'  
+   mysql['log_dir'] = '/var/log/morpheus/mysql'  
+   mysql['max_active'] = 150 # The combined value off all app node max_active values must be lower than max_connections setting in mysql  
+   mysql['max_connections'] = 151  
+   mysql['max_allowed_packet'] = 67108864  
+   mysql['mysql_connect_timeout'] = 60000  
+   mysql['mysql_max_reconnects'] = 2  
+   mysql['mysql_queries_before_retry_source'] = 0  
+   mysql['mysql_seconds_before_retry_source'] = 300  
+   nginx['cache_max_size'] = '5000m'  
+   nginx['enable'] = true  
+   nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'  
+   nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+   nginx['loading_pages']['iteration_time'] = 10000 # milliseconds  
+   nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+   nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+   nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+   nginx['loading_pages']['max_loops'] = 60 # seconds  
+   nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+   nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+   nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+   nginx['log_format_name'] = 'custom'  
+   nginx['log_format'] = '\'$remote_addr - $remote_user [$time_local] "$request" \' \'$status $body_bytes_sent "$http_referer" \' \'"$http_user_agent" "$http_x_forwarded_for" \' \'rt=$request_time uct="$upstream_connect_time" uht="$upstream_header_time" urt="$upstream_response_time"\';'  
+   nginx['listen_ipv6'] = nil #### IPv6 will be added to ``morpheus.conf`` and ``morpheus-ssl.conf`` listeners if any value is set in morpheus.rb other than ``nil``, including "off" or false  
+   nginx['ssl_ciphers'] = "ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-SHA384:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA:DHE-RSA-AES256-SHA256:DHE-RSA-AES128-SHA256:DHE-RSA-AES256-SHA:DHE-RSA-AES128-SHA:ECDHE-RSA-DES-CBC3-SHA:EDH-RSA-DES-CBC3-SHA:AES256-GCM-SHA384:AES128-GCM-SHA256:AES256-SHA256:AES128-SHA256:AES256-SHA:AES128-SHA:DES-CBC3-SHA:HIGH:!aNULL:!eNULL:!EXPORT:!DES:!MD5:!PSK:!RC4"  
+   nginx['ssl_company_name'] = "Morpheus, LLC"  
+   nginx['ssl_country_name'] = "US"  
+   nginx['ssl_email_address'] = "personal@email.com"  
+   nginx['ssl_locality_name'] = "San Mateo"  
+   nginx['ssl_organizational_unit_name'] = "DevOps"  
+   nginx['ssl_protocols'] = "TLSv1 TLSv1.1 TLSv1.2"  
+   nginx['ssl_session_cache'] = "builtin:1000  shared:SSL:10m"  
+   nginx['ssl_session_timeout'] = "5m"  
+   nginx['ssl_state_name'] = "CA"  
+   nginx['worker_connections'] = 10240  
+   nginx['workers'] = integer calculated from number of cpus  
+   nginx['ssl_access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   nginx['access_ping_log'] = false #### false by default, when true GET requests to the ``/ping`` endpoint are logged in the ``/var/log/morpheus/nginx/morpheus-ssl-access.log`` file on the appliance  
+   rabbitmq['enable'] = true  
+   rabbitmq['host'] = '127.0.0.1'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['queue_user_password'] = 'xxxxxxxxxxxxxxxx'  
+   rabbitmq['queue_user'] = 'morpheus-rmq-user'  
+   rabbitmq['vhost'] = 'morpheus'  
+   ↓ The following rabbitmq settings are only valid for Internal/Embedded rabbitmq services  
+   rabbitmq['heartbeat'] = nil  
+   rabbitmq['log_dir'] = '/var/log/morpheus/rabbitmq'  
+   rabbitmq['nodename'] = 'rabbit@localhost'  
+   rabbitmq['port'] = '5672'  
+   rabbitmq['use_tls'] = false  
+   repo['repo_host_url'] = 'https://www.hpe.com/support/hpesc'  
+   ui['http_client_connect_timeout'] = 10000  #### milliseconds  
+   ui['jobs_enabled'] = true #### This option disables the appliance jobs service on the appliance node when set to false. This should be disabled only when configuring jobs to run on specific app nodes in HA environments.  
+   ui['kerberos_config'] = nil  
+   ui['kerberos_login_config'] = nil  
+   ui['log_dir'] = '/var/log/morpheus/morpheus-ui'  
+   ui['max_memory_mb'] = nil  
+   ui['memory_alloc_arena_max'] = 2  
+   ui['memory_map_max'] = 65536  
+   ui['memory_map_threshold'] = 131072  
+   ui['memory_top_pad'] = 131072  
+   ui['memory_trim_threshold'] = 131072  
+   ui['pxe_boot_enabled'] = false #### This option disables the PXE service within the app  
+   ui['support_links'] = {  
+     'name' => ['url', 'i18n'],  
+     'name1' => ['url1', i18n1'],  
+     'name2' => ['url2', i18n2']  
+   } #### The internationalization configuration is optional. The result of this configuration are entries in the support dropdown menu in the upper bar of the application window which override the default entries.  
+   ui['vm_images_cdn_url'] = 'https://morpheus-images.morpheusdata.com'  
+   ui['xms'] = 0.25 #### Configurable for customers running into high memory issues, values are the percentage of total RAM. Both ui and es xms/xmx config only apply if Opensearch is enabled.  
+   ui['xmx'] = 0.25
+   ```
+   ```
+6. After all configuration options have been set, run: 
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus.rb` and running `sudo morpheus-ctl reconfigure` again. Appliance and other services may need to be restarted depending on configuration changes.
+7. Once the installation is complete the morpheus-ui service will automatically start up and be available shortly. To monitor the UI startup process, run `morpheus-ctl tail morpheus-ui` and look for the ascii logo accompanied by the install version and start time: 
+
+   ```
+   ```
+   timestamp:    __  ___              __  
+   timestamp:   /  |/  /__  _______  / /  ___ __ _____  
+   timestamp:  / /|_/ / _ \/ __/ _ \/ _ \/ -_) // (_-<  
+   timestamp: /_/  /_/\___/_/ / .__/_//_/\__/\_,_/___/  
+   timestamp: ****************************************  
+   timestamp:   Version: |morphver|  
+   timestamp:   Start Time: xxx xxx xxx 00:00:00 UTC 2021  
+   timestamp: ****************************************
+   ```
+   ```
+
+#### Results
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on Debian/Ubuntu
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on Ubuntu or Debian a few preparatory items should be addressed first.
+
+### Procedure
+
+First make sure the apt repository is up to date by running `sudo apt-get update`. It is advisable to verify the assigned hostname of the machine is self-resolvable. 
+
+IMPORTANT
+
+If the machine is unable to resolve its own hostname `nslookup hostname` some installation commands will be unable to verify service health during installation and fail.
+
+### Results
+
+1. Next simply download the relevant `.deb` package for installation. This package can be acquired from <https://app.morpheushub.com> downloads section.
+
+   TIP
+
+   Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package/morpheus-appliance_x.x.x-1_amd64.deb`
+
+1. Next we must install the package onto the machine and configure the morpheus services:
+
+   ```
+   ```
+   sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   sudo morpheus-ctl reconfigure
+   ```
+   ```
+2. Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+   ```
+   ```
+   sudo morpheus-ctl reconfigure  
+   sudo morpheus-ctl stop morpheus-ui  
+   sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   The morpheus-ui can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
+
+## Single Node Install on RHEL
+
+### About this task
+
+To get started installing HPE Morpheus Enterprise on RHEL/RedHat a few prerequisite items are required.
+
+### Procedure
+
+1. Configure firewalld to allow access from users on 443 (Or remove firewall if not required).
+2. Make sure the machine is self resolvable to its own hostname.
+3. For RHEL 7.x, the Optional RPMs repo needs to be added for Reconfigure to succeed. It does not need to be added For RHEL 8.x, as the Optional RPMs repo is now part of the appstream repo that is enabled by default in RHEL 8.x. 
+
+   - RHEL 7.x Amazon:`yum-config-manager --enable rhel-7-server-rhui-optional-rpms`
+   - RHEL 7.x:`yum-config-manager --enable rhel-7-server-optional-rpms`
+
+### Results
+
+NOTE
+
+For Amazon users a Redhat subscription is not required if the appropriate yum REGION repository is added instead as demonstrated above.
+
+The RedHat Enterprise Linux server needs to be registered and activated with Redhat subscription. The server optional rpms repo needs to be enabled as well.
+
+To check if the server has been activated please run the subscription-manager version. Subscription manager will return the version plus the python dependency version.
+
+If the server has not been registered and activated then the subscription manager version will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: This system is currently not registered  
+subscription management server: 0.9.51.24.-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+When a server has been registered and activated with Redhat the subscription manager will return the below message.
+
+```
+```
+sudo subscription-manager version  
+server type: Red Hat Subscription Management  
+subscription management server: 0.9.51.24-1  
+subscription-manager: 1.10.14-7.el7 python-rhsm: 1.10.12-2.el7
+```
+```
+
+If the subscription manager re-turns the message `This system is currently not registered` please follow the below steps to register the server.
+
+TIP
+
+To register the server you will need to have sudo permissions [Member of the Wheel group] or root access to the server. You will also need your Redhat registered email address and password.
+
+subscription-manager register
+
+```
+```
+sudo subscription-manager register  
+Username: redhat@example.com  
+Password: . subscription-manager auto --attach
+```
+```
+
+NOTE
+
+This can take a minute to complete
+
+```
+```
+sudo subscription-manager attach --auto  
+Installed Product Current Status: Product Name: Red Hat Enterprise Linux  
+Server Status: Subscribed
+```
+```
+
+To check to see if the RHEL server has the Red Hat Enterprise Linux 7 Server - Optional (RPMs) repo enabled please run the following command to return the repo status.
+
+TIP
+
+To check the server repos you will need to have sudo permissions [Member of the Wheel group] or root access to the server.
+
+```
+```
+sudo yum repolist all | grep "rhel-7-server-optional-rpms" rhel-7-server-optional-rpms/7Server/x86_64 disabled
+```
+```
+
+If the repo status was returned as disabled then you will need to enable the repo using the subscription manager like below.
+
+```
+```
+sudo subscription-manager repos --enable rhel-7-server-optional-rpms  
+Repository 'rhel-7-server-optional-rpms' is enabled for this system.
+```
+```
+
+The message `Repo 'rhel-7-server-optional-rpms' is enabled for this system.` will appear after enabling the repo. This will confirm that the repo has been enabled.
+
+Next simply download the relevant `.rpm` package for installation. This package can be acquired from morpheushub.com.
+
+TIP
+
+Use the `wget` command to directly download the package to your appliance server. i.e. `wget https://www.hpe.com/support/hpesc/path/to/package.rpm`
+
+Next we must install the package onto the machine and configure the morpheus services:
+
+```
+```
+sudo rpm -i morpheus-appliance_x.x.x-1_amd64.rpm  
+sudo morpheus-ctl reconfigure
+```
+```
+
+Once the installation is complete the web interface will automatically start up. By default it will be resolvable at `https://your_machine_name` and in many cases this may not be resolvable from your browser. The url can be changed by editing `/etc/morpheus/morpheus.rb` and changing the value of `appliance_url`. After this has been changed simply run:
+
+```
+```
+sudo morpheus-ctl reconfigure  
+sudo morpheus-ctl stop morpheus-ui  
+sudo morpheus-ctl start morpheus-ui
+```
+```
+
+NOTE
+
+The `morpheus-ui` can take 2-3 minutes to startup before it becomes available.
+
+There are additional install settings that can be viewed in the [Additional Configuration Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B95E888-6B01-47E2-AB6C-5357324DBAB5.html) section.
+
+Once the browser is pointed to the appliance a first time setup wizard will be presented. Please follow the on screen instructions by creating the master account. From there you will be presented with the license settings page where a license can be applied for use (if a license is required you may request one or purchase one by contacting your sales representative).
+
+More details on setting up infrastructure can be found throughout this guide.
+
+TIP
+
+If any issues occur it may be prudent to check the morpheus log for details at `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json b/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
new file mode 100644
index 0000000..cf88880
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+  "title": "Installation",
+  "ordinal": 14,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.html",
+  "topic_cluster": {
+    "clustering_title": "Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8",
+        "clustering_title": "Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md b/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
new file mode 100644
index 0000000..aa1dab6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7ABFAE27-1B01-4630-A46F-86ADE40672F8.md
@@ -0,0 +1,8 @@
+# Installation
+
+**Subtopics**  
+
+- **[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html)**
+- **[Single Node Installation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7A7CF662-8990-4A6D-A6BF-A99759FA11E1.html)**
+- **[HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)**
+- **[3 Node HA Install Example](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2D8A0A86-2231-4239-AB44-5475B4AE0827.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json b/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
new file mode 100644
index 0000000..0ed7787
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+  "title": "Rubrik",
+  "ordinal": 385,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.html",
+  "topic_cluster": {
+    "clustering_title": "Rubrik",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4",
+        "clustering_title": "Rubrik"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md b/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
new file mode 100644
index 0000000..18dd225
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7AFDEE86-434B-4DFB-BE40-1D7D185F8FD4.md
@@ -0,0 +1,80 @@
+# Rubrik
+
+The embedded HPE Morpheus Enterprise Rubrik Backup integration allows syncing, creation, and management of Rubrik Backups for vCenter Clouds. New Rubrik integrations are created in Backups > Integrations and, once created, can be set as the backup provider for existing vCenter Clouds. The latest versions of the Rubrik plugin support Rubrik CDM as well as Rubrik RSC (Rubrik Cloud Security). From a HPE Morpheus Enterprise standpoint, the primary difference between the two is in how they are authenticated. CDM-based integrations are created with API key authentication whereas RSC-based integrations are created with a client ID and client secret. Once the integration is created, the feature set as used through HPE Morpheus Enterprise is identical.
+
+## Features
+
+- Backup sync & association
+- SLA Domain sync & selection
+- Backup creation, deletion & restore
+- Restore Backups over existing VMs
+- Restore Backups as new Instances
+
+## Adding Rubrik Integration
+
+### About this task
+
+NOTE
+
+The Rubrik backup service is currently only supported on the VMware Cloud type.
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Rubrik
+4. Fill in the following: 
+
+   Rubrik CDM Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (api key), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   API Token
+   :   If manually entering credentials, this field will be visible. Enter the API key
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+
+   Rubrik RSC Integration
+
+   Name
+   :   A name for the integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When marked, the integration is enabled for use as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Rubrik API server. Each Rubrik customer will have a unique host URL (for example: `https://morpheusdata.my.rubrik.com`)
+
+   Credentials
+   :   Choose to manually enter authentication credentials and save them to a secure credential store for later use (client id and secret), manually enter and not save them for later use (Local Credentials), or apply a previously-saved API key (select from list of existing credentials)
+
+   Client ID
+   :   If manually entering credentials, this field will be visible. Enter the client ID for authentication. If needed, add a service account to obtain credentials (for example: `https://morpheusdata.my.rubrik.com/service_accounts`). Keep in mind the service account will need to have sufficient privileges to interface with the Rubrik API to execute all HPE Morpheus Enterprise functionality listed in the “Features” section above
+
+   Client Secret
+   :   If manually entering credentials, this field will be visible. Enter the client secret for authentication
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json b/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
new file mode 100644
index 0000000..6611b63
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+  "title": "Incidents",
+  "ordinal": 260,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.html",
+  "topic_cluster": {
+    "clustering_title": "Incidents",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17",
+        "clustering_title": "Incidents"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md b/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
new file mode 100644
index 0000000..c665596
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BBB877B-68DE-4FC1-88AC-1EE083765E17.md
@@ -0,0 +1,9 @@
+# Incidents
+
+Incident management is very important in any IT Operations environment. The ability to notify the appropriate people of an outage that requires immediate attention is critical to reducing recovery time and even preventing potential customer facing impacts. Because of this, HPE Morpheus Enterprise provides incident management features as well as external integrations out of the box.
+
+Incidents can be found in the Monitoring- > Incidents section. When a check fails, an incident is automatically raised. These can vary in severity based on the user configured check severities as well as the group hierarchy (representative of redundancy).
+
+Incidents are also grouped. If an application is impacted and multiple checks fail for that application they automatically get grouped together in one Incident that can fluctuate or escalate in severity as time progresses. These incidents can be muted so as not to affect availability and they can also be resolved manually with an option to detail resolution information.
+
+There are also integrations and API’s for integrating with existing corporate workflows when it comes to incident management.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json b/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
new file mode 100644
index 0000000..d4df620
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+  "title": "Cluster Packages",
+  "ordinal": 163,
+  "parent_title": "Templates",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BD87211-4E8A-480C-A7B6-E502808743EC",
+        "clustering_title": "Cluster Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md b/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
new file mode 100644
index 0000000..c7f13bd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.md
@@ -0,0 +1,21 @@
+# Cluster Packages
+
+Cluster Packages are created and can then be associated with Cluster Layouts. Cluster Packages themselves are created from Spec Templates. The Spec Templates and Cluster Layouts sections of HPE Morpheus Enterprise docs include more information on creating those constucts and show the steps to deploy sample builds.
+
+## Creating a Cluster Package
+
+Navigate to the Cluster Packages List page (Library > Templates > Cluster Packages). System Cluster Packages are listed here. These are included as part of HPE Morpheus Enterprise pre-built Cluster Layouts and cannot be edited or viewed. User-created Cluster Layouts are also listed here and these may be edited. To begin creating a new Cluster Package, click + ADD and configure the following:
+
+- **NAME:** A friendly name for the Cluster Package in HPE Morpheus Enterprise
+- **CODE:** An identifying code for the Cluster Package for use with HPE Morpheus Enterprise API and CLI
+- **DESCRIPTION:** An optional description for the Cluster Package
+- **PACKAGE VERSION:** A version designation for the Cluster Package
+- **ICON:** An identifying icon for the Cluster Package, this will appear in a list with other packages associated with a Cluster Layout
+- **DARK MODE IMAGE:** An alternate icon for the Cluster Package used when the dark theme is enabled on the HPE Morpheus Enterprise appliance
+- **TYPE:** A type selection for the package, see dropdown for options
+- **PACKAGE TYPE:** A one-word descriptor for the package such as “calico”, “prometheus”, etc.
+- **ENABLED:** When marked, this Cluster Package is available to be set on Cluster Layouts
+- **REPEAT INSTALL:** When marked, if the package install initially fails, the installation will be attempted again
+- **SPEC TEMPLATES:** Use the Typeahead field to select relevant Spec Templates to build the Cluster Package
+
+![../../_images/cluster-packages.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D5D3548C-0254-4864-A53B-0147E5742FBC-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json b/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
new file mode 100644
index 0000000..22469f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+  "title": "Import Pre-Provisioned Servers",
+  "ordinal": 420,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html",
+  "topic_cluster": {
+    "clustering_title": "Import Pre-Provisioned Servers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E",
+        "clustering_title": "Import Pre-Provisioned Servers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md b/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
new file mode 100644
index 0000000..8f69cbd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.md
@@ -0,0 +1,29 @@
+# Import Pre-Provisioned Servers
+
+## About this task
+
+Perform the following to add a bare metal server:
+
+## Procedure
+
+1. Navigate to Infrastructure > Compute > Bare Metal.
+2. Click Add Bare Metal Server.
+3. Select the Pre-Provisioned server.
+4. Complete the remaining server details and click Save.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-961F7EE2-166C-4B30-A63A-5C6CF0D638BC-high.png)  
+
+   NOTE
+
+   **For Windows**: When importing a Pre-Provisioned Windows server, select Windows OS. This is required because some import operations are specific to Windows.
+
+   During import, the HPE BMaaS validates the association between the provided iLO IP and OS IP by executing commands on the host OS. The supplied OS credentials must have elevated privileges:
+   - **Linux OS**: The user must have sudo privileges.
+   - **Windows OS**: The user must be in the Administrators group.
+
+## Results
+
+Once the server is imported, it should be ready to be converted into a fully provisioned node.
+
+**Subtopics**  
+
+- **[Convert to Provisioned Node](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6A02D571-9949-4EA4-B43C-C2CED90210EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json b/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
new file mode 100644
index 0000000..2d76fe8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+  "title": "logback config",
+  "ordinal": 37,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.html",
+  "topic_cluster": {
+    "clustering_title": "logback config",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7",
+        "clustering_title": "logback config"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md b/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
new file mode 100644
index 0000000..0612f8b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7.md
@@ -0,0 +1,888 @@
+# logback config
+
+NOTE
+
+This doc is for 5.4.4+ versions that use `logback.xml`. 5.4.3 and earlier versions use `logback.groovy` with a different syntax that is not compatible with this doc. Please refer to 5.4.3 and earlier documentation for `logback.groovy` configuration details.
+
+The log output for the morpheus-ui service is configured in the logback.xml file. Log output levels can be updated when more or less log output is desired.
+
+## Setting Log Levels
+
+To change a log level, edit the logback configuration file in /opt/morpheus/conf/logback.xml and save. The changes will be reflected within the configured `scanPeriod`, 30 seconds by default.
+
+Levels:
+:   - **OFF** (no log output)
+    - **ERROR** (includes error logs)
+    - **WARN** (includes warn and error logs)
+    - **INFO** (includes info, warn and error logs)
+    - **DEBUG** (includes info, warn, error and debug logs)
+    - **TRACE** (includes info, warn, error, debug and trace logs)
+
+WARNING
+
+Use DEBUG and/or TRACE levels with caution. DEBUG & TRACE levels can produce many logs that can consume disk space quickly. Only use DEBUG and/or TRACE levels when needed and target them for specific services.
+
+## Example Logback Settings
+
+Below are sample log configuration settings. This is not a complete list. Additional log names/paths can typically be determined from the standard INFO, WARN and ERROR logs.
+
+ACI
+:   ```
+    ```
+    <logger name="com.morpheus.integration.NetworkServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciNetworkService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.AciUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>
+    ```
+    ```
+
+Amazon
+:   ```
+    ```
+    <logger name="com.morpheus.compute.amazon.AmazonComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AmazonComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.costing.AmazonCostingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AmazonProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Azure
+:   ```
+    ```
+    <logger name="com.morpheus.Azure.ServersController" level="DEBUG"/>  
+    <logger name="com.morpheus.AzureSqlServerProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.azure.AzureComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AzureCostingService" level="DEBUG"/>
+    ```
+    ```
+
+Chef
+:   ```
+    ```
+    <logger name="com.morpheus.automation.ChefClientService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefService" level="DEBUG"/>  
+    <logger name="com.morpheus.automation.ChefTaskService" level="DEBUG"/>
+    ```
+    ```
+
+DNS
+:   ```
+    ```
+    <logger name="com.morpheus.dns.MicrosoftDnsService" level="DEBUG"/>
+    ```
+    ```
+
+General
+:   ```
+    ```
+    <logger name="com.morpheus.InstanceService" level="DEBUG"/>  
+    <logger name="com.morpheus.util.ApiUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.AppService" level="DEBUG"/>  
+    <logger name="com.morpheus.MorpheusComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.RpcService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.AbstractBoxProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ProgressUpdater" level="DEBUG"/>
+    ```
+    ```
+
+Google
+:   ```
+    ```
+    <logger name="com.morpheus.compute.google.GoogleComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.GoogleComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.GoogleProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Hyper-V
+:   ```
+    ```
+    <logger name="com.morpheus.compute.hyperv.HypervComputeService" level="DEBUG" />  
+    <logger name="com.morpheus.compute.HypervComputeUtility" level="DEBUG" />
+    ```
+    ```
+
+IBM Cloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.softlayer.SoftlayerComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.SoftlayerComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Kubernetes
+:   ```
+    ```
+    <logger name="com.morpheus.app.KubernetesAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.KubernetesResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.KubernetesComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.host.KubernetesHostService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.KubernetesProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.KubernetesStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Monitoring
+:   ```
+    ```
+    <logger name="com.morpheus.monitoring.MonitorCheckService" level="DEBUG"/>
+    ```
+    ```
+
+Network
+:   ```
+    ```
+    <logger name="com.morpheusdata.infoblox.InfobloxProvider" level="DEBUG"/>  
+    <logger name="com.morpheus.network.InfobloxNetworkPoolService" level="DEBUG"/>  
+    <logger name="com.morpheus.network.NetworkService " level="DEBUG"/>  
+    <logger name="com.morpheus.network.PluginNetworkPoolService" level="DEBUG"/>
+    ```
+    ```
+
+Nutanix
+:   ```
+    ```
+    <logger name="com.morpheus.compute.nutanix.NutanixComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.NutanixComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.NutanixProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Openstack
+:   ```
+    ```
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.AbstractOpenStackComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.OpenStackProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.storage.OpenStackSFSStorageService" level="DEBUG"/>
+    ```
+    ```
+
+Option Types
+:   ```
+    ```
+    <logger name="com.morpheus.OptionSourceService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeListService" level="DEBUG"/>  
+    <logger name="com.morpheus.OptionTypeService" level="DEBUG"/>
+    ```
+    ```
+
+Remote Console
+:   ```
+    ```
+    <logger name="com.morpheus.remote.MorpheusGuacamoleWebsocketHandler" level="DEBUG"/>
+    ```
+    ```
+
+SCVMM
+:   ```
+    ```
+    <logger name="com.morpheus.compute.scvmm.ScvmmComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.ScvmmComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.ScvmmProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+ServiceNow
+:   ```
+    ```
+    <logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="DEBUG"/>  
+    <logger name="com.morpheus.integrations.ServiceNowUtility" level="DEBUG"/>
+    ```
+    ```
+
+Tasks
+:   ```
+    ```
+    <logger name="com.morpheus.task.AnsibleTowerTaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.TaskService" level="DEBUG"/>  
+    <logger name="com.morpheus.task.WinrmTaskService" level="DEBUG"/>
+    ```
+    ```
+
+Terraform
+:   ```
+    ```
+    <logger name="com.morpheus.app.AbstractResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAppTemplateService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.app.TerraformResourceMappingService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.TerraformProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+Usage
+:   ```
+    ```
+    <logger name="com.morpheus.AccountPriceService" level="DEBUG"/>
+    ```
+    ```
+
+vCloud
+:   ```
+    ```
+    <logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VcloudDirectorProvisionService" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.VcdComputeUtility" level="DEBUG"/>
+    ```
+    ```
+
+Veeam
+:   ```
+    ```
+    <logger name="com.morpheus.backup.VeeamBackupService" level="DEBUG"/>
+    ```
+    ```
+
+Vmware
+:   ```
+    ```
+    <logger name="com.morpheus.compute.VmwareComputeUtility" level="DEBUG"/>  
+    <logger name="com.morpheus.compute.vmware.VmwareComputeService" level="DEBUG"/>  
+    <logger name="com.morpheus.provision.VmwareProvisionService" level="DEBUG"/>
+    ```
+    ```
+
+vRO
+:   ```
+    ```
+    <logger name="com.morpheus.automation.VroService" level="DEBUG"/>
+    ```
+    ```
+
+## All core logger paths
+
+Expand below to see all core HPE Morpheus Enterprise logger paths set to INFO level.
+
+### All core logger paths
+
+```
+```
+<logger name="com.bertramlabs.plugins.AccountsAuthService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AccountsService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.ActiveDirectoryUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.AzureSamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomApiUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.CustomExternalUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.DefaultUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.JumpCloudUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.LdapUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OktaUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.OneLoginUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.PingUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.SamlUserService" level="INFO"/>  
+<logger name="com.bertramlabs.plugins.UserSourceAuthenticationProvider" level="INFO"/>  
+<logger name="com.morpheus.AbstractComputeService" level="INFO"/>  
+<logger name="com.morpheus.AbstractPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.AccountBudgetService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationObjectService" level="INFO"/>  
+<logger name="com.morpheus.AccountIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.AccountInvoiceService" level="INFO"/>  
+<logger name="com.morpheus.AccountPriceService" level="INFO"/>  
+<logger name="com.morpheus.AccountResourceService" level="INFO"/>  
+<logger name="com.morpheus.AccountUsageService" level="INFO"/>  
+<logger name="com.morpheus.ActivityService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AbstractAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.AmazonConvertibleRiAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.CostAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.UtilizationAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.analytics.WorkloadAnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.AnalyticsService" level="INFO"/>  
+<logger name="com.morpheus.api.AbstractApiService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.CommandService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.DownloadService" level="INFO"/>  
+<logger name="com.morpheus.api.agent.UploadService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.AbstractResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.AppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.HelmAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.KubernetesResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.MorpheusAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.ScribeResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAppTemplateService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAwsResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformAzurermResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformGoogleResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.app.TerraformVsphereResourceMappingService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceClientService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceDelayedJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceHealthService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceJobService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceLicenseService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceService" level="INFO"/>  
+<logger name="com.morpheus.ApplianceStorageService" level="INFO"/>  
+<logger name="com.morpheus.approval.ApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.RemedyApprovalService" level="INFO"/>  
+<logger name="com.morpheus.approval.ServiceNowApprovalService" level="INFO"/>  
+<logger name="com.morpheus.AppService" level="INFO"/>  
+<logger name="com.morpheus.ArchiveService" level="INFO"/>  
+<logger name="com.morpheus.AsyncService" level="INFO"/>  
+<logger name="com.morpheus.AuditLogService" level="INFO"/>  
+<logger name="com.morpheus.automation.AbstractConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleService" level="INFO"/>  
+<logger name="com.morpheus.automation.AnsibleTowerService" level="INFO"/>  
+<logger name="com.morpheus.automation.ChefService" level="INFO"/>  
+<logger name="com.morpheus.automation.ConfigManagementService" level="INFO"/>  
+<logger name="com.morpheus.automation.HelmService" level="INFO"/>  
+<logger name="com.morpheus.automation.PuppetService" level="INFO"/>  
+<logger name="com.morpheus.automation.SaltStackService" level="INFO"/>  
+<logger name="com.morpheus.automation.VroService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.AbstractReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupExecutionInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStatus" level="INFO"/>  
+<logger name="com.morpheus.backup.BackupStorageService" level="INFO"/>  
+<logger name="com.morpheus.backup.DirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.FileBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.KarmanStorageProviderBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmImageBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.LvmSnapshotBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusApplianceBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MorpheusContainerBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.MysqlBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupExecutionService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupJobService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupProviderService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginBackupRestoreService" level="INFO"/>  
+<logger name="com.morpheus.backup.PluginReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationInterface" level="INFO"/>  
+<logger name="com.morpheus.backup.ReplicationService" level="INFO"/>  
+<logger name="com.morpheus.backup.SqlserverBackupService" level="INFO"/>  
+<logger name="com.morpheus.backup.TarDirectoryBackupService" level="INFO"/>  
+<logger name="com.morpheus.BootMacService" level="INFO"/>  
+<logger name="com.morpheus.builds.AbstractBuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.BuildsService" level="INFO"/>  
+<logger name="com.morpheus.builds.JenkinsBuildsService" level="INFO"/>  
+<logger name="com.morpheus.CapacityService" level="INFO"/>  
+<logger name="com.morpheus.CatalogCartService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemService" level="INFO"/>  
+<logger name="com.morpheus.CatalogItemTypeService" level="INFO"/>  
+<logger name="com.morpheus.certificate.AbstractCertificateService" level="INFO"/>  
+<logger name="com.morpheus.certificate.MorpheusCertificateService" level="INFO"/>  
+<logger name="com.morpheus.CertificateService" level="INFO"/>  
+<logger name="com.morpheus.ChefClientService" level="INFO"/>  
+<logger name="com.morpheus.cm.ChangeManagementService" level="INFO"/>  
+<logger name="com.morpheus.cm.CherwellCmService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.AbstractCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.CmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.RemedyCmdbService" level="INFO"/>  
+<logger name="com.morpheus.cmdb.ServiceNowCmdbService" level="INFO"/>  
+<logger name="com.morpheus.code.AbstractCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.CodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GitCodeService" level="INFO"/>  
+<logger name="com.morpheus.code.GithubCodeService" level="INFO"/>  
+<logger name="com.morpheus.compliance.NVDSyncService" level="INFO"/>  
+<logger name="com.morpheus.compliance.PackageManagementService" level="INFO"/>  
+<logger name="com.morpheus.compute.cisco.UcsComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.CloudPluginComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeApiService" level="INFO"/>  
+<logger name="com.morpheus.compute.ComputeServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.compute.IpmiService" level="INFO"/>  
+<logger name="com.morpheus.compute.KubernetesComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.MaasComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.ManualComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.OneviewComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.SelfManagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.standard.StandardComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.unmanaged.UnmanagedComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VcloudDirectorComputeService" level="INFO"/>  
+<logger name="com.morpheus.compute.vmware.VmwareComputeService" level="INFO"/>  
+<logger name="com.morpheus.ComputeService" level="INFO"/>  
+<logger name="com.morpheus.container.ActivemqContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.DockerContainerUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.container.ElasticsearchContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.JavaContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.MysqlContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.NodeContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.PostgresContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.RedisContainerService" level="INFO"/>  
+<logger name="com.morpheus.container.SqlserverContainerService" level="INFO"/>  
+<logger name="com.morpheus.ContainerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ContainerService" level="INFO"/>  
+<logger name="com.morpheus.costing.AbstractCostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingInterface" level="INFO"/>  
+<logger name="com.morpheus.costing.CostingService" level="INFO"/>  
+<logger name="com.morpheus.costing.StandardCostingService" level="INFO"/>  
+<logger name="com.morpheus.CurrencyConversionService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherGORMDatastoreService" level="INFO"/>  
+<logger name="com.morpheus.cypher.CypherService" level="INFO"/>  
+<logger name="com.morpheus.DashboardService" level="INFO"/>  
+<logger name="com.morpheus.DatastoreService" level="INFO"/>  
+<logger name="com.morpheus.DataViewService" level="INFO"/>  
+<logger name="com.morpheus.DbSchedulerService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.AbstractDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.CloudFoundryAppDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DefaultDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.DockerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.GrailsDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.IisDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.JbossDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.KubernetesDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.NodeDeployService" level="INFO"/>  
+<logger name="com.morpheus.deploy.ServerDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.deploy.VmDeployTargetService" level="INFO"/>  
+<logger name="com.morpheus.DeploymentService" level="INFO"/>  
+<logger name="com.morpheus.discovery.AbstractDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DatastoreCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.DiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostBalancingDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.HostCapacityDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ReservationRecommendationDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.ShutdownDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.discovery.SizeDiscoveryService" level="INFO"/>  
+<logger name="com.morpheus.dns.AbstractDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.BindDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.ConsulDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.DNSProvider" level="INFO"/>  
+<logger name="com.morpheus.dns.DnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.MicrosoftDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PluginDnsService" level="INFO"/>  
+<logger name="com.morpheus.dns.PowerDnsService" level="INFO"/>  
+<logger name="com.morpheus.ElasticCleanupService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentService" level="INFO"/>  
+<logger name="com.morpheus.EnvironmentVariableService" level="INFO"/>  
+<logger name="com.morpheus.ExecuteScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.ExecutionRequestService" level="INFO"/>  
+<logger name="com.morpheus.export.AccountInvoiceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.CodeRepositoryExportService" level="INFO"/>  
+<logger name="com.morpheus.export.DeploymentExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExecuteScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ExportService" level="INFO"/>  
+<logger name="com.morpheus.export.InstanceExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AdminIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.AutomationIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.BackupIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.CertificateIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.DeployIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.integrations.NetworkIntegrationExportService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerExpertService" level="INFO"/>  
+<logger name="com.morpheus.export.LoadBalancerInstancesExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkDomainExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkPoolExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkRouterExportService" level="INFO"/>  
+<logger name="com.morpheus.export.NetworkSecurityGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.PowerScheduleTypeExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServerGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ServicePlanExportService" level="INFO"/>  
+<logger name="com.morpheus.export.TaskExportService" level="INFO"/>  
+<logger name="com.morpheus.export.ThresholdExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserExportService" level="INFO"/>  
+<logger name="com.morpheus.export.UserGroupExportService" level="INFO"/>  
+<logger name="com.morpheus.export.WorkflowExportService" level="INFO"/>  
+<logger name="com.morpheus.FileCopyRequestService" level="INFO"/>  
+<logger name="com.morpheus.GlobalSearchService" level="INFO"/>  
+<logger name="com.morpheus.host.AbstractHostService" level="INFO"/>  
+<logger name="com.morpheus.host.DockerHostService" level="INFO"/>  
+<logger name="com.morpheus.host.ExternalKubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.KubernetesHostService" level="INFO"/>  
+<logger name="com.morpheus.host.SwarmHostService" level="INFO"/>  
+<logger name="com.morpheus.HttpClientService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubQueueService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubService" level="INFO"/>  
+<logger name="com.morpheus.hub.MorpheusHubSyncService" level="INFO"/>  
+<logger name="com.morpheus.imagebuild.ImageBuildService" level="INFO"/>  
+<logger name="com.morpheus.ImageCacheService" level="INFO"/>  
+<logger name="com.morpheus.instance.InstanceUpgradeService" level="INFO"/>  
+<logger name="com.morpheus.InstanceService" level="INFO"/>  
+<logger name="com.morpheus.InstanceTypeService" level="INFO"/>  
+<logger name="com.morpheus.integration.AbstractIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.CherwellIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.GitRepoService" level="INFO"/>  
+<logger name="com.morpheus.integration.RemedyIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.RunDeckIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.SalesForceIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.ScribeService" level="INFO"/>  
+<logger name="com.morpheus.integration.ServiceNowIntegrationService" level="INFO"/>  
+<logger name="com.morpheus.integration.TerraformService" level="INFO"/>  
+<logger name="com.morpheus.jobs.AbstractJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.JobExecutor" level="INFO"/>  
+<logger name="com.morpheus.jobs.KubernetesJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.SecurityScanExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.TaskJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.jobs.WorkflowJobExecutorService" level="INFO"/>  
+<logger name="com.morpheus.JobService" level="INFO"/>  
+<logger name="com.morpheus.KeyPairService" level="INFO"/>  
+<logger name="com.morpheus.library.LayoutService" level="INFO"/>  
+<logger name="com.morpheus.LicenseService" level="INFO"/>  
+<logger name="com.morpheus.LoadBalancerPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.LocalizationService" level="INFO"/>  
+<logger name="com.morpheus.LocalRepoService" level="INFO"/>  
+<logger name="com.morpheus.log.AbstractLogService" level="INFO"/>  
+<logger name="com.morpheus.log.LogRhythmLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SplunkLogService" level="INFO"/>  
+<logger name="com.morpheus.log.SyslogLogService" level="INFO"/>  
+<logger name="com.morpheus.LogService" level="INFO"/>  
+<logger name="com.morpheus.maint.UpdateService" level="INFO"/>  
+<logger name="com.morpheus.MarketplaceClientService" level="INFO"/>  
+<logger name="com.morpheus.MarshallService" level="INFO"/>  
+<logger name="com.morpheus.MetadataTagService" level="INFO"/>  
+<logger name="com.morpheus.migration.AbstractMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.HypervisorMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.LvmMigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.MigrationService" level="INFO"/>  
+<logger name="com.morpheus.migration.WindowsMigrationService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlerterService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AlertRuleService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.AvailabilityService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.CheckAgentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.IncidentService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorAppService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorChartingService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckManagementService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorCheckService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitoringService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.MorpheusMonitorService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.NewRelicService" level="INFO"/>  
+<logger name="com.morpheus.monitoring.ServiceNowService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusComputeService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusPackageService" level="INFO"/>  
+<logger name="com.morpheus.MorpheusSecurityService" level="INFO"/>  
+<logger name="com.morpheus.MotdService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AbstractNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.AciNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.AviLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.BluecatNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.BootService" level="INFO"/>  
+<logger name="com.morpheus.network.CitrixNetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.CloudPluginNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.ConsulService" level="INFO"/>  
+<logger name="com.morpheus.network.F5BigIpLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.F5LineRateLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.FirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.FortiADCLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.HaproxyLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InfobloxNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.InternalNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.IPAMProvider" level="INFO"/>  
+<logger name="com.morpheus.network.KubernetesRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.LoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.LocalFirewallService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.MorpheusRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetScalerLoadBalancerService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkConfigService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkRegistryService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.NetworkServicesService" level="INFO"/>  
+<logger name="com.morpheus.network.NutanixNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PaloAltoNetworkService" level="INFO"/>  
+<logger name="com.morpheus.network.PhpipamNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PluginNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.PxeService" level="INFO"/>  
+<logger name="com.morpheus.network.SolarWindsNetworkPoolService" level="INFO"/>  
+<logger name="com.morpheus.network.StealthNetworkSecurityService" level="INFO"/>  
+<logger name="com.morpheus.NetworkDomainService" level="INFO"/>  
+<logger name="com.morpheus.OauthProviderService" level="INFO"/>  
+<logger name="com.morpheus.OperationEventService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourcePluginService" level="INFO"/>  
+<logger name="com.morpheus.OptionSourceService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeListService" level="INFO"/>  
+<logger name="com.morpheus.OptionTypeService" level="INFO"/>  
+<logger name="com.morpheus.os.LinuxOsService" level="INFO"/>  
+<logger name="com.morpheus.os.WindowsOsService" level="INFO"/>  
+<logger name="com.morpheus.PermissionService" level="INFO"/>  
+<logger name="com.morpheus.plugin.AbstractPluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.BackupProviderPluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupJobImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupRestoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupResultImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusBackupTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationGroupImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationSiteImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.backup.MorpheusReplicationTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeServerInterfaceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusComputeZoneFolderImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.compute.MorpheusDatastoreImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusAccountInvoiceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.costing.MorpheusCostingImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.cypher.MorpheusCypherImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusAccountInventoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.integration.MorpheusIntegrationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusAccountCredentialTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusCloudImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputePortImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeServerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeLayoutFactoryImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeTypeSetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusComputeZonePoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContainerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusContextImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusInstanceImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusMetadataTagTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOperationNotificationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusOsTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusPermissionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusProcessImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusReportImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusServicePlanImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusSnapshotImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStatsImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageControllerTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusStorageVolumeTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusTaskImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusUsageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusVirtualImageLocationImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.MorpheusWikiPageImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkDomainRecordImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolIpImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkPoolRangeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkSubnetImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.network.MorpheusNetworkTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.PluginProviderManagerService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.policy.MorpheusPolicyTypeImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.provisioning.MorpheusProvisionImplService" level="INFO"/>  
+<logger name="com.morpheus.plugin.web.MorpheusWebRequestImplService" level="INFO"/>  
+<logger name="com.morpheus.policy.AbstractPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.BackupStoragePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.MotdPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.NetworkPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.PolicyServiceInterface" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageBucketQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageServerQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.StorageShareQuotaPolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.TagCompliancePolicyService" level="INFO"/>  
+<logger name="com.morpheus.policy.WorkflowPolicyService" level="INFO"/>  
+<logger name="com.morpheus.PolicyService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleService" level="INFO"/>  
+<logger name="com.morpheus.PowerScheduleTypeService" level="INFO"/>  
+<logger name="com.morpheus.PriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.PricePlanService" level="INFO"/>  
+<logger name="com.morpheus.ProcessService" level="INFO"/>  
+<logger name="com.morpheus.ProfileService" level="INFO"/>  
+<logger name="com.morpheus.project.ProjectService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractBoxProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.AbstractProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.CloudPluginProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerEngineProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.DockerProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ExternalProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.HelmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.IProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.KubernetesProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.MaasProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ManualProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.OneviewProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.ScribeProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SelfManagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.StandardProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.SwarmProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.TerraformProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UcsProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.UnmanagedProvisionService" level="INFO"/>  
+<logger name="com.morpheus.provision.WorkflowProvisionService" level="INFO"/>  
+<logger name="com.morpheus.ProvisioningService" level="INFO"/>  
+<logger name="com.morpheus.ProxyService" level="INFO"/>  
+<logger name="com.morpheus.ReferenceService" level="INFO"/>  
+<logger name="com.morpheus.report.AbstractReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonCoverageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonSavingsReportService" level="INFO"/>  
+<logger name="com.morpheus.report.AmazonUtilizationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudAppUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeCapacityReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInstanceTypeUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudInventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CloudUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.CostReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InventoryReportService" level="INFO"/>  
+<logger name="com.morpheus.report.InvoiceReportService" level="INFO"/>  
+<logger name="com.morpheus.report.MigrationReportService" level="INFO"/>  
+<logger name="com.morpheus.report.PluginReportService" level="INFO"/>  
+<logger name="com.morpheus.report.ReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TenantUsageReportService" level="INFO"/>  
+<logger name="com.morpheus.report.TimeSeriesCostReportService" level="INFO"/>  
+<logger name="com.morpheus.RoleService" level="INFO"/>  
+<logger name="com.morpheus.RpcService" level="INFO"/>  
+<logger name="com.morpheus.scale.AbstractScaleService" level="INFO"/>  
+<logger name="com.morpheus.scale.MorpheusScaleService" level="INFO"/>  
+<logger name="com.morpheus.ScaleService" level="INFO"/>  
+<logger name="com.morpheus.scribe.ScribeLibraryService" level="INFO"/>  
+<logger name="com.morpheus.ScriptConfigService" level="INFO"/>  
+<logger name="com.morpheus.sdn.AbstractSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.MorpheusSdnService" level="INFO"/>  
+<logger name="com.morpheus.sdn.OvsService" level="INFO"/>  
+<logger name="com.morpheus.sdn.VethSdnService" level="INFO"/>  
+<logger name="com.morpheus.security.AbstractSecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.security.ScapScanService" level="INFO"/>  
+<logger name="com.morpheus.security.SecurityScanService" level="INFO"/>  
+<logger name="com.morpheus.SecurityGroupService" level="INFO"/>  
+<logger name="com.morpheus.SequenceService" level="INFO"/>  
+<logger name="com.morpheus.ServerScriptService" level="INFO"/>  
+<logger name="com.morpheus.ServerService" level="INFO"/>  
+<logger name="com.morpheus.ServicePlanService" level="INFO"/>  
+<logger name="com.morpheus.SettingsService" level="INFO"/>  
+<logger name="com.morpheus.SetupService" level="INFO"/>  
+<logger name="com.morpheus.SiteService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotPriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.SnapshotService" level="INFO"/>  
+<logger name="com.morpheus.StatsService" level="INFO"/>  
+<logger name="com.morpheus.StatusService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.AbstractStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.BasicStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.CephStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.EcsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.IsilonStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.KubernetesStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.NfsStorageService" level="INFO"/>  
+<logger name="com.morpheus.storage.QnapFileStationService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageServerService" level="INFO"/>  
+<logger name="com.morpheus.storage.StorageVolumeService" level="INFO"/>  
+<logger name="com.morpheus.storage.ThreeParStorageService" level="INFO"/>  
+<logger name="com.morpheus.StorageProviderService" level="INFO"/>  
+<logger name="com.morpheus.SubAccountService" level="INFO"/>  
+<logger name="com.morpheus.task.AbstractTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.AnsibleTowerTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ChefTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ContainerTemplateTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.EmailTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ExecutableTaskInterface" level="INFO"/>  
+<logger name="com.morpheus.task.GroovyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.HttpTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JavascriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.JRubyTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.LocalScriptTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PuppetTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.PythonTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.RestartTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.ShellTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskConfigService" level="INFO"/>  
+<logger name="com.morpheus.task.TaskService" level="INFO"/>  
+<logger name="com.morpheus.task.VroTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WinrmTaskService" level="INFO"/>  
+<logger name="com.morpheus.task.WriteAttributesTaskService" level="INFO"/>  
+<logger name="com.morpheus.trust.AbstractCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialProvider" level="INFO"/>  
+<logger name="com.morpheus.trust.CredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.CypherCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.InternalCredentialService" level="INFO"/>  
+<logger name="com.morpheus.trust.PluginCredentialService" level="INFO"/>  
+<logger name="com.morpheus.UsageLimitService" level="INFO"/>  
+<logger name="com.morpheus.UserGroupService" level="INFO"/>  
+<logger name="com.morpheus.UserManagementService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiAppService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiGatewayService" level="INFO"/>  
+<logger name="com.morpheus.vdi.VdiPoolService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImagePriceManagerService" level="INFO"/>  
+<logger name="com.morpheus.VirtualImageService" level="INFO"/>  
+<logger name="com.morpheus.WikiPageService" level="INFO"/>  
+<logger name="com.morpheus.worker.DistributedWorkerService" level="INFO"/>  
+<logger name="com.morpheus.ZoneFolderService" level="INFO"/>  
+<logger name="com.morpheus.ZoneMarketplaceService" level="INFO"/>  
+<logger name="com.morpheus.ZonePoolService" level="INFO"/>  
+<logger name="com.morpheus.ZoneRegionService" level="INFO"/>  
+<logger name="com.morpheus.ZoneService" level="INFO"/>
+```
+```
+
+## Audit logs
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+2. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+3. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+4. Once the service has stopped enter the following at the xml prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+5. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json b/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
new file mode 100644
index 0000000..5f89e2e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+  "title": "Identity Sources",
+  "ordinal": 280,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440",
+        "clustering_title": "Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md b/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
new file mode 100644
index 0000000..e79c97c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.md
@@ -0,0 +1,12 @@
+# Identity Sources
+
+Administration > Tenants > (Selected Tenant) > Identity Sources Administration > Users > Identity Sources
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html)**
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json b/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
new file mode 100644
index 0000000..fba738a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+  "title": "Virtual Machines",
+  "ordinal": 212,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Machines",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7CA53A6D-026B-4977-8247-349750CE4EB9",
+        "clustering_title": "Virtual Machines"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md b/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
new file mode 100644
index 0000000..897d908
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.md
@@ -0,0 +1,22 @@
+# Virtual Machines
+
+![../../_images/infra_compute_header_vms_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-354FC170-C67F-4589-B0CA-75A62F884A32-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+The Virtual Machines tab lists all managed and unmanaged VMs across HPE Morpheus Enterprise. Managed VMs are either provisioned by HPE Morpheus Enterprise, or are inventoried/discovered VMs that have been converted to managed. Unmanaged VMs are typically inventoried/discovered VMs from Cloud integrations.
+
+## Virtual Machine Change Cloud
+
+Change Cloud functionality allows a server to be reassociated to a new Cloud, which may be necessary at times for easier record keeping in HPE Morpheus Enterprise. In order to use this feature, the user must have “Infrastructure: Move Servers” permission set to “Full.”
+
+Changing Clouds might be necessary, for example, when moving a VM from one vCenter datacenter to another. We can use this tool to update the Cloud association in HPE Morpheus Enterprise as well. Other scenarios may include migrating workloads from private Cloud to public Cloud or even creating a brand new VM in a new Cloud which represents an identical workload to something pre-existing but which will be retired.
+
+NOTE
+
+For VMware Clouds, Cloud reassignment occurs automatically when a server is migrated from one cluster to another or from one resource pool to another within the same cluster. Following the next Cloud sync, HPE Morpheus Enterprise will reflect the migration made in vCenter. In this scenario, you should not try to use the manual change Cloud tools. In fact, you will receive a warning in HPE Morpheus Enterprise logs if you attempt to do so.
+
+To change Clouds, navigate to the VM detail page (Infrastructure > Compute > Virtual Machines > selected VM), click on the ACTIONS menu, and click Change Cloud. You can select the new target Cloud here and optionally select a new VM which the current one should be merged into. The important thing to keep in mind is that this tool is for HPE Morpheus Enterprise record keeping only. **It is not a tool which does migration work for you.** See the embedded video below for a demonstration of this feature.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json b/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
new file mode 100644
index 0000000..4e5d8ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+  "title": "SSL Certificates",
+  "ordinal": 242,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html",
+  "topic_cluster": {
+    "clustering_title": "SSL Certificates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF",
+        "clustering_title": "SSL Certificates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md b/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
new file mode 100644
index 0000000..70d0220
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.md
@@ -0,0 +1,3 @@
+# SSL Certificates
+
+SSL certificates authenticate the identity of web servers and encrypt the data being transmitted. HPE Morpheus Enterprise stores SSL certificates to simplify administration and application of SSL certificates to HPE Morpheus Enterprise-managed resources.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json b/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
new file mode 100644
index 0000000..7f3f580
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+  "title": "Unable to Provision a Custom Image",
+  "ordinal": 358,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html",
+  "topic_cluster": {
+    "clustering_title": "Unable to Provision a Custom Image",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7",
+        "clustering_title": "Unable to Provision a Custom Image"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md b/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
new file mode 100644
index 0000000..69d4a98
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.md
@@ -0,0 +1,22 @@
+# Unable to Provision a Custom Image
+
+## About this task
+
+Prior to provisioning an custom image, the image must be configured in the Library > Virtual Images section by selecting Edit on the Actions dropdown of the Virtual Image.
+
+In the Edit Virtual Image pane:
+
+## Procedure
+
+1. Select “Cloud Init Enabled?” only if the Virtual Image is a linux image with cloud init installed.
+2. Enter the username and password that are set on the Virtual Image.
+
+## Results
+
+NOTE
+
+When using Static IP’s or IP Pools in VMware, VMware tools must also be installed on the template in order for HPE Morpheus Enterprise to set the static IP address when provisioning.
+
+NOTE
+
+HPE Morpheus Enterprise agents only support 64-bit vm’s prior to versions 2.12.3 and 3.0.2
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json b/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
new file mode 100644
index 0000000..6ef8d45
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+  "title": "ArubaCX Network Integration",
+  "ordinal": 510,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html",
+  "topic_cluster": {
+    "clustering_title": "ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A",
+        "clustering_title": "ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md b/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
new file mode 100644
index 0000000..e9b7f56
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.md
@@ -0,0 +1,177 @@
+# ArubaCX Network Integration
+
+## Overview
+
+The ArubaCX network plugin is implemented as a HPE Morpheus Enterprise `GenericIntegrationProvider` in Groovy. The plugin handles network and cluster events generated by HPE Morpheus Enterprise and modifies the configuration of ArubaCX switches based on the cable connections between the affected servers and switches. HPE Morpheus Enterprise integrates directly with ArubaCX to create or delete networks for OVS Port Groups that are added or deleted within a configured Cluster.
+
+## Features
+
+- Network - Create or Delete OVS Port Group.
+
+## Prerequisites
+
+- A pair of ArubaCX 8325 series switches
+- All the hosts in the Cluster are connected to these pair of switches
+- REST API access to the ArubaCX switches with administrative rights
+- User credentials for the ArubaCX switch pair with API access granted and read/write access to the switch configuration
+
+### Server Network Configuration (Netplan)
+
+#### Procedure
+
+1. On each host, configure a `bond0` interface on the management interfaces
+2. The management interfaces should be connected to the ArubaCX switch pair Sample configuration: 
+
+   ```
+   ```
+   {  
+       bonds:  
+         bond0:  
+           interfaces:  
+             - ens2f0np0  
+             - ens1f0np0  
+           parameters:  
+             mode: "active-backup"  
+       ...  
+   }
+   ```
+   ```
+
+### Switch Configuration
+
+#### Procedure
+
+1. Configure the management interface and IP address on both switches in the pair
+2. The switch pair must be configured with `vsx-sync` enabled for high availability and redundancy 
+
+   Sample configuration:
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role primary  
+       keepalive peer 192.168.0.1 source 192.168.0.0  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+
+   ```
+   ```
+   vsx  
+       inter-switch-link lag 256  
+       role secondary  
+       keepalive peer 192.168.0.0 source 192.168.0.1  
+       vsx-sync loop-protect-global mclag-interfaces vsx-global
+   ```
+   ```
+3. Create a Multi-Chassis Link Aggregation Group (MC-LAG) between the ArubaCX switch and the upstream network, referred to as `lag1`
+4. Configure the `lag1` interface on both switches in the pair Sample configuration: 
+
+   ```
+   ```
+   interface lag 1 multi-chassis  
+       no shutdown  
+       no routing  
+       vlan trunk native 1  
+       vlan trunk allowed 1,175  
+       lacp mode active  
+       loop-protect
+   ```
+   ```
+5. The switch ports connected to the server’s management interfaces should be set to “Trunk mode” with a “Native VLAN” Sample configuration: 
+
+   ```
+   ```
+   interface 1/1/1  
+   no shutdown  
+   no routing  
+   vlan trunk native 175  
+   vlan trunk allowed 175
+   ```
+   ```
+
+## Adding ArubaCX Integration
+
+### About this task
+
+NOTE
+
+Making full use of the HPE Morpheus Enterprise ArubaCX integration requires credentials for Aruba CX switch pair with API access granted and read/write access to switch configuration. See ArubaCX 8325 documentation for more information on user rights administration in that product.
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select + New Integration > Other > ArubaCX 
+
+   ![../../_images/arubacx_new_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D9808197-A648-4D9C-864F-4A60FC8C7A35-high.png)
+3. Enter the following: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   ENABLED
+   :   Deselect to disable the integration
+
+   USERNAME
+   :   User username for all switches
+
+   PASSWORD
+   :   User password for all switches
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 1
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 2
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 3
+
+   IPV4 ADDRESS
+   :   Primary switch IP address for switch pair 4
+
+   IPV4 ADDRESS
+   :   Secondary switch IP address for switch pair 4
+
+   UPLINK LAG INTERFACE
+   :   Name of the uplink LAG interface (default is 'lag1')
+4. Select SAVE CHANGES
+
+### Results
+
+Upon save the ArubaCX Network integration will be created. See example screenshots created with and without leaf-spine enabled:
+
+![../../_images/arubacx_settings.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5D534A49-DDA0-4E90-856C-F6244B48C327-high.png)![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-74EB5EDA-F973-4471-B1D1-74DBF6F4AAA4-high.png)
+
+NOTE
+
+All fields can be edited after saving.
+
+Sample Reference Architecture for EVPN Configuration
+
+1. Minimum four leaf switches, two spine switches, and one core switch
+2. At least two servers in separate racks
+3. Configure switches to encapsulate L2 traffic via VXLAN overlay across racks
+4. VMs on servers in different racks communicate through the EVPN switch configuration
+5. Route traffic between racks through spine switches
+
+## Add ArubaCX Integration to a Cluster
+
+### Procedure
+
+1. In Infrastructure > Clusters select the target Cluster
+2. Select the Edit icon for the Cluster
+3. In the “Integrations” dropdown, select an available ArubaCX Integration
+4. Save Changes 
+
+   ![../../_images/arubacx_edit_cluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6978CDB6-74D2-492A-B461-2F0EC476F018-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json b/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
new file mode 100644
index 0000000..cb380ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+  "title": "Task Types",
+  "ordinal": 108,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html",
+  "topic_cluster": {
+    "clustering_title": "Task Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6",
+        "clustering_title": "Task Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md b/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
new file mode 100644
index 0000000..fe77622
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.md
@@ -0,0 +1,25 @@
+# Task Types
+
+Available Task Types
+
+         |  | Task Type | Task Description | Source Options | Execute Target Options | Configuration Requirements | Role Permissions Requirements |
+| --- | --- | --- | --- | --- | --- | --- |
+| ansible | Ansible | Runs an Ansible playbook. Ansible Integration required | Ansible Repo (Git) | Local, Resource | Existing Ansible Integration | Library: Tasks |
+| ansibletower | Ansible Tower | Relays Ansible calls to Ansible Tower | Tower Integration | Local, Remote, Resource | Existing Ansible Tower Integration | Library: Tasks |
+| chef | Chef bootstrap | Executes Chef bootstrap and run list. Chef Integration required | Chef Server | Resource | Existing Chef Integration | Library: Tasks |
+| conditional | Conditional Workflow | Allows the user to set JavaScript logic. If it resolves to `true`, HPE Morpheus Enterprise will run the Operational Workflow set as the “IF OPERATIONAL WORKFLOW” and if it resolves to `false`, HPE Morpheus Enterprise will run the “ELSE OPERATIONAL WORKFLOW” | N/A (JavaScript logic must be locally sourced, Tasks housed within the associated Workflows may have different sourcing options depending on their types.) | Local | Existing Operational Workflows | Library: Tasks |
+| email | Email | Send an email from a Workflow | Task Content | Local | SMTP Configured | Library: Tasks |
+| groovy | Groovy script | Executes Groovy Script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| http | HTTP | Executes REST call for targeting external API’s. | Local | Local | None | Library: Tasks |
+| javascript | Javascript | Executes Javascript locally (on HPE Morpheus Enterprise app node) | Local | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| jruby | jRuby Scirpt | Executes Ruby script locally (on HPE Morpheus Enterprise app node) | Local, Repository, Url | Local | None | Library: Tasks, Tasks ‐ Script Engines |
+| libraryscript | Library Script | Creates a Task from an existing Library Script (Library > Templates > Script Templates) | Library Script | Resource | Existing Library Script | Library: Tasks |
+| template | Library Template | Creates a Task from an existing Library Template (Library > Templates > Spec Templates) | Library Template | Resource | Existing Library Templates | Library: Tasks |
+| nestedworkflow | Nested Workflow | Embeds a Workflow into a Task which allows the Workflow to be nested within other Workflows for situations when common Task sets are frequently used in Workflows | N/A | Local | N/A | Library: Tasks |
+| powershell | PowerShell Script | Execute PowerShell Script on the Target Resource | Local, Repository, Url | Remote, Resource, Local | None | Library: Tasks |
+| puppet | Puppet Agent Install | Executes Puppet Agent bootstrap, writes `puppet.conf` and triggers agent checkin. Puppet Integration required | Puppet Master | Resource | Existing Puppet Integration | Library: Tasks |
+| python | Python Script | Executes Python Script locally | Local, Repository, Url | Local | `virtualenv` installed on Appliance Nodes | Library: Tasks, Tasks ‐ Script Engines |
+| restart | Restart | Restarts target VM/Host/Container and confirms startup status before executing next task in Workflow | System | Resource | None | Library: Tasks |
+| shellscript | Shell Script | Executes Bash script on the target resource | Local, Repository, Url | Local, Remote, Resource | None | Library: Tasks |
+| vro | vRealize Orchestrator Workflow | Executes vRO Workflow on the Target Resource | vRO Integration | Local, Resource | Existing vRO Integration | Library: Tasks |
+| wa | Write Attributes | Add arbitrary values to the Attributes map of the target resource | N/A | Local | Provide map of values as valid JSON | Library: Tasks |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json b/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
new file mode 100644
index 0000000..32e3bca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+  "title": "Uploading OS Images",
+  "ordinal": 407,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.html",
+  "topic_cluster": {
+    "clustering_title": "Uploading OS Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E",
+        "clustering_title": "Uploading OS Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md b/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
new file mode 100644
index 0000000..e2012b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-80911C58-F6AB-4001-B50E-EC0F43773A5E.md
@@ -0,0 +1,15 @@
+# Uploading OS Images
+
+## Prerequisites
+
+- Image upload and deployment performance depend on network bandwidth and storage backend performance.
+- File permissions on shared storage must allow Morpheus read access.
+- OS images must be bootable and compatible with the target bare metal hardware.
+- Server reboots and virtual media behavior depend on hardware management interfaces (for example, iLO).
+
+**Subtopics**  
+
+- **[Uploading OS Images Using Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6E67B963-98E5-4F99-B239-C0A83E75DBDF.html)**
+- **[Uploading OS Images Using S3-Compatible Object Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-20AF9B68-EDEE-400D-B351-F0A8B19853E0.html)**
+- **[Uploading OS Images Using CIFS (Samba)](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-724CB591-93AE-41D8-8CA4-8410DD6C1DAD.html)**
+- **[Uploading OS Images Using NFS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0BAF2FE9-97B1-4D4A-9525-ED355C24F870.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json b/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
new file mode 100644
index 0000000..b28bb44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+  "title": "How to un-manage an Instance/VM/Host",
+  "ordinal": 351,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html",
+  "topic_cluster": {
+    "clustering_title": "How to un-manage an Instance/VM/Host",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8143252C-EC38-43B2-B2E0-443A60C01768",
+        "clustering_title": "How to un-manage an Instance/VM/Host"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md b/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
new file mode 100644
index 0000000..64c6dfb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8143252C-EC38-43B2-B2E0-443A60C01768.md
@@ -0,0 +1,63 @@
+# How to un-manage an Instance/VM/Host
+
+## Description
+
+A managed VM (and associated Instance) needs to be unmanaged and returned to Discovered type.
+
+## Solution
+
+### About this task
+
+Delete the record from the Infrastructure  >  Compute (! not from Provisioning - Instances) selection with the following configuration in the Delete modal:
+
+- `Remove Infrastructure` UNCHECKED
+- `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+- `Force Delete` UNCHECKED
+
+The most important items to be aware of when “un-managing” an Instance/VM/Host are:
+
+### Procedure
+
+1. The “Remove from Infrastructure” flag when deleting a VM or Host in HPE Morpheus Enterprise determines if the actual VM is deleted from the target Infrastructure. 
+
+   - Checking “Remove Infrastructure” means you WANT TO DELETE THE ACTUAL VM. Typing “DELETE” in the confirmation field is required when “Remove From Infrastructure” is enabled.
+   - Unchecking “Remove Infrastructure” means you only want to delete the record in HPE Morpheus Enterprise but leave the actual VM untouched.
+2. Deleting an Instance will always remove Infrastructure. 
+
+   IMPORTANT
+
+   REPEAT: Deleting an Instance from the `Provisioning` section will always remove the VM aka Infrastructure.
+3. After removing the record from HPE Morpheus Enterprise, the VM must be in a Cloud with Inventory enabled to automatically be re-discovered.
+
+## Process
+
+### About this task
+
+Steps to delete a managed VM from HPE Morpheus Enterprise and, when necessary, remove the associated Instance:
+
+### Procedure
+
+1. Navigate to the VM (not Instance) detail page at Infrastructure  >  Compute - VMs 
+
+   NOTE
+
+   VM’s inside an Instance can be navigated to inside the Instance Details page by selecting the VM in the `VM's` seciton on the Instance Details page.
+2. Select DELETE
+3. Configure the DELETE HOST modal with the following settings: 
+
+   ![../_images/delete_host_modal.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7627FF0E-DEA9-4A41-8E6B-E1E752BA731F-high.png)
+   - `Remove Infrastructure` UNCHECKED
+   - `Remove Associated Instances` Must be checked if the server has an associated Instance, as deleting the VM but not the Instance would result in an abandoned Instance thus not allowed.
+   - `Force Delete` UNCHECKED
+
+   IMPORTANT
+
+   If you have to type DELETE that means the `Remove Infrastructure` flag is selected and you are confirming deletion of the actual VM. Ensure `Remove Infrastructure` is UNCHECKED when you want to leave the VM intact!
+4. Select DELETE
+5. The VM and associated Insatnce will be removed from HPE Morpheus Enterprise but the actual VM will remain.
+6. Wait up to 5 min or click REFRESH on the associated Clouds details page to force a cloud sync. 
+
+   NOTE
+
+   `Inventory` must be enabled on the associated cloud for the VM to automatically be re-discovered by HPE Morpheus Enterprise.
+7. The VM is now back in HPE Morpheus Enterprise as discovered/unmanaged. To managed and create a new Instance from the VM, select ACTIONS : Convert To Managed.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json b/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
new file mode 100644
index 0000000..6e31430
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+  "title": "Overview",
+  "ordinal": 147,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8168FFDF-77DD-42E0-B747-95099C7852AB",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md b/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
new file mode 100644
index 0000000..872bf07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8168FFDF-77DD-42E0-B747-95099C7852AB.md
@@ -0,0 +1,17 @@
+# Overview
+
+The Virtual Image section displays a list of all images, local and synced, that are available to deploy. HPE Morpheus Enterprise includes a rich catalog of pre-configured System Images available for every cloud type. User Images are automatically synced from Cloud Integrations and added to the Virtual Images section. Images can also be uploaded directly into HPE Morpheus Enterprise via local file or url. Amazon and Azure Marketplace images can also be added to the Virtual Images Section.
+
+Understanding the process of prepping images for consumption in HPE Morpheus Enterprise is a very important step toward building an effective HPE Morpheus Enterprise environment. In addition to the information contained in this section on Virtual Images, it may be helpful to see a complete image prep example walkthrough. Our getting started guide for HPE Morpheus Enterprise and VMware includes [a section on preparing images](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html#prepping-an-image) that may provide a helpful example.
+
+TIP
+
+HPE Morpheus Enterprise includes a wide catalog of system image types as examples to show how the product can be used and to give users a starting point for implementing their own library. The included images are not intended to be production-ready images. HPE Morpheus Enterprise always recommends its users create their own gold images which meet their required specifications.
+
+IMPORTANT
+
+Invalid Image Settings cause provisioning failures. HPE Morpheus Enterprise syncs in as much meta-data as possible for synced images, but additional configuration may be needed to ensure successful provisioning.
+
+WARNING
+
+Cloud-init is enabled by default for all Linux images. If your Linux image does not have Cloud-init installed, Cloud-init Enabled must be unchecked before provisioning the image or it will fail immediately.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json b/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
new file mode 100644
index 0000000..1df624c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+  "title": "Configuring Tenants and Resources for Multi-Tenancy",
+  "ordinal": 279,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063",
+        "clustering_title": "Configuring Tenants and Resources for Multi-Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md b/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
new file mode 100644
index 0000000..e13b1d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.md
@@ -0,0 +1,264 @@
+# Configuring Tenants and Resources for Multi-Tenancy
+
+A very common scenario for Managed Service Providers (MSPs) is the need to provide access to resources on a customer-by-customer basis. Several administrative features are available in HPE Morpheus Enterprise to ensure customer resources are properly scoped and isolated. With its built-in multi-tenancy capabilities and white label support, managed service providers have a wide range of capabilities when it comes to managing customer Tenants and users.
+
+## Tenants
+
+There are essentially two types of Tenants in HPE Morpheus Enterprise
+
+- Master Tenant
+- Sub Tenants
+
+During the initial setup of a HPE Morpheus Enterprise Appliance, the Master Tenant is created. All Tenants created in addition to this Master Tenant are Subtenants. There is only one Master Tenant, though its child Tenants can create child Tenants of their own. The Master Tenant may scope resources to all other Tenants while any Subtenants which have children of their own may only scope resources to their immediate children Tenants.
+
+### Creating Tenants
+
+#### About this task
+
+The Master Tenant is created during the initial appliance setup. Additional sub-Tenants can be created in the Administration > Tenants section.
+
+The Tenants page displays a list of all Tenants. This page enables users to: Create, Edit, and Delete Tenants. The list of Tenants displays the Tenant Name, Role, Total Instances, Total Users, Status (active or inactive) and the Created Date. Click the Tenant Name to drill into the Tenant View where you can edit or delete the Tenant, as well as create, edit and delete users belonging to the Tenant.
+
+NOTE
+
+At least one Tenant in addition to the Master Tenant is required to scope resources across Tenants.
+
+To create a new sub-Tenant
+
+#### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the +Create Tenant button.
+4. From the New Tenant wizard input \* Name (Required) \* Description \* Base Role \* Currency (for pricing)
+
+#### Results
+
+The Base Role defines a role set from which all roles created within the Tenant will inherit.
+
+NOTE
+
+In prior versions, we could set Limits when creating a Subtenant. These could restrict the amount of storage, memory, and CPUs that can be collectively provisioned by all users in the Tenant. In more recent versions, this functionality has been rolled into Policies (Administration > Policies). When creating a Policy, we are able to specify a Tenant to which the Policy should apply.
+
+Click the Save Changes button.
+
+![The Create Tenant dialog box is shown](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-16DD7A70-0CA9-44E3-8361-DBA158D96416-high.png)
+
+### Viewing Tenants
+
+To View an individual Tenant page, select the Tenant name from the main Tenants section.
+
+![../../_images/viewtenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-39DE1887-6BEA-45F1-B234-9F2921BD663A-high.png)
+
+From inside the Tenant view, we can edit or delete the Tenant, as well as click into any of the Tenant’s users.
+
+### Tenant Users
+
+To create a new user within the Tenant:
+
+Click the CREATE USER button, then from the New User wizard input the fields below:
+
+- First Name
+- Last Name
+- Username
+- Email
+- Role
+- Password
+- Confirm Password
+
+Click Save Changes.
+
+NOTE
+
+Users are specific to each Tenant. Users created in the Master Tenant or other sub-Tenants will only have access to the Tenant they are created in.
+
+### Impersonate Tenant User
+
+HPE Morpheus Enterprise allows admin users in parent Tenants to impersonate any user in their child Tenants to see HPE Morpheus Enterprise as if they are that user. To impersonate a user, you must be logged in as a user with the “Impersonate User” feature enabled in the assigned role.
+
+From inside a Tenant detail page (containing the list of that Tenant’s users), and in the specific user’s ACTIONS drop down, select “Impersonate”.
+
+![../../_images/configuring_multi_tenancy-9583a.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-071C08CB-F499-4A7F-BFCA-87B4C6B6D08F-high.png)
+
+This will log you in as that user in their respective Tenant. To log out of the impersonate users Tenant, select the username in the header, and then select “Quit Impersonating”
+
+![../../_images/configuring_multi_tenancy-d229b.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C13E674E-CE80-485D-B60E-0F33BD0BE2F7-high.png)
+
+## Resources
+
+In the Master Tenant, resources can be configured with private or public visibility:
+
+- Private Visibility: Only available to the assigned Tenant.
+- Public Visibility (option available in Master Tenant only): Available across all Tenants
+
+Resources in the Master Tenant can also be assigned directly to Subtenants. When a resource is assigned to a Subtenant, it is only available for that Subtenant, and its visibility is automatically set to private. Public visibility is not an option for any resource assigned to or created in a Subtenant.
+
+From the Master Tenant, the following resources can be configured for public visibility across all Tenants, or assigned to individual sub-Tenants
+
+- Clouds
+- Hosts
+- Virtual Machines
+- Networks
+- Datastores
+- Resource Pools
+- Folders
+- Virtual Images
+- Library Instance Types
+- Pricing
+- Policies
+- Workflows
+- Roles
+
+NOTE
+
+Virtual Image Blueprints can be made available to multiple select Tenants when set to private.
+
+### Cloud Visibility & Assignment
+
+#### About this task
+
+To set the visibility of a Cloud to Public (shared across all Tenants) or Private (only available to the assigned Tenant):
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-349e2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF8023AD-C31F-4FF1-A51C-AE47C55EA399-high.png)
+
+When a cloud is set to Public visibility, it is available to be added to Subtenants. All Subtenants created after a Master Tenant cloud is set to public will automatically have clouds with public visibility added, and a group will be created for each available cloud matching the cloud name in the new Subtenant(s).
+
+For Tenants created prior to a Master Tenant cloud being set to public visibility, the Subtenant will have the option to add that cloud but it will not automatically be added.
+
+While the cloud will be available for Subtenants, the resources available in that cloud to the Subtenant(s) depends on the visibility or assignment of the individual resources.
+
+NOTE
+
+A Subtenant user must have sufficient role permissions and cloud access to add publicly available clouds. Master Tenant clouds settings cannot be edited from Subtenants.
+
+### Assign a Cloud to an Tenant
+
+IMPORTANT
+
+When assigning a Cloud to a Tenant, all resources for that Cloud will only be available to the assigned Tenant. If a cloud is created in the Master Tenant and assigned to a sub-Tenant, it will no longer be available for use by the Master Tenant or any other sub-Tenants, although it can be assigned back to the Master Tenant, or to another sub-Tenant.
+
+It may be preferable for service providers to share or assign their cloud resources, such as specific hosts, networks, resources pools and datastores, across sub-Tenants, rather than an entire cloud.
+
+### To assign a cloud from the Master Tenant to a Sub-Tenant
+
+#### Procedure
+
+1. Navigate to Infrastructure, Clouds
+2. Select either the pencil/edit icon on the end of the cloud row, or click the name of the cloud and select “Edit” in the cloud page.
+3. From the “Tenant” drop down, select the Tenant to assign the cloud to. The visibility will automatically be set to “Private” when a cloud is assigned to a sub-Tenant.
+4. Select Save Changes in the footer of the Edit Cloud modal.
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-c907d.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1741E74F-481B-4D67-A2B0-B338A4958C9E-high.png)
+
+When a cloud is assigned to a sub-Tenant, or assigned to the Master Tenant with private visibility, that cloud and all of its resources are only available to the assigned Tenant. The Master Tenant still maintains control and visibility, and can edit the cloud settings or re-assign the cloud.
+
+### Individual Resource Visibility & Assignment
+
+Similar to clouds, individual resources from the Master Tenant can be set to public and available to sub-Tenants, or assigned to sub-Tenants.
+
+By default, any host, virtual machine, bare metal server, network, resource pool, datastore or blueprint added, created or inventoried by an Tenant is assigned to that Tenant. If these resources are in the Master Tenant, they can be assigned to sub Tenants. Assigning one of these resources will make it unavailable to the Master Tenant, but it will still be visible and editable by the Master Tenant. This allows Master Tenant resources to be isolated for use by sub-Tenants while still under the control of the Master Tenant.
+
+Resources assigned to sub-Tenants from the Master Tenant will be visible and available for use by that sub-Tenant, however they cannot be edited or re-assigned by the sub-tenant.
+
+### Set the Visibility of a Host, Virtual Machine or Bare metal Server to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. Select Edit in the resource page to bring up the config modal
+5. From the “Visibility” drop down, select either “Public” or “Private”
+6. Select Save Changes
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-d738d.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A6C1B836-5DF2-47CE-A78A-0A94A1A777C0-high.png)
+
+Assigning a Host, Virtual Machine, or Bare Metal server to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Hosts
+2. Select either the Hosts, Virtual Machines or Bare Metal tab
+3. Click the name of the resource
+4. From the “Actions” dropdown in the the resource page, select Assign Tenant
+5. In the Assign Tenant modal, select the Tenant to assign the resource to.
+6. Select Execute in the modal
+
+![../../_images/configuring_multi_tenancy-3c39f.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0DC2CDEE-E498-4EF1-B0B5-B54260A82FF7-high.png)
+
+The resource will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+### Set the Visibility of a Network to Public or Private
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Visibility” drop down, select either “Public” or “Private”
+4. Select Save Changes in the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-bc333.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9AB26FDA-4C5C-4F4C-ACD5-1013B6D3F162-high.png)
+
+### Assign a Network to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Infrastructure, Network
+2. Select either the pencil/edit icon in the network row, or click the name of the network and select “Edit” in the network page.
+3. From the “Tenant” drop down, select an Tenant to assign the network to.
+4. Select Save Changes in the lower the modal
+
+#### Results
+
+![../../_images/configuring_multi_tenancy-9f15c.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FC41C95A-2672-476A-B22E-2C2541407BB8-high.png)
+
+The Network will now be assigned and available for use by the assigned Tenant. If assigned to a sub-Tenant, the Master Tenant will maintain visibility and control.
+
+Set the Visibility or assign a datastore to an Tenant
+
+1. From the Master Tenant, navigate to Infrastructure, Storage
+2. Select the “Data Stores” tab
+3. Select Edit from the “Actions” dropdown in the datastores row
+4. From the “Visibility” drop down, select either “Public” or “Private”
+5. From the “Tenant” drop down, select the Tenant to assign the datastore to.
+
+   NOTE
+
+   If assigned to a sub-tenant, the visibility will be automatically set to private.
+6. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-1e978.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-77B5C886-86F4-40C1-A0D1-DE6EDDA1EBBB-high.png)
+
+### Set the Visibility or assign a Virtual Image to an Tenant
+
+#### Procedure
+
+1. From the Master Tenant, navigate to Provisioning, Virtual Images
+2. Select Edit from the “Actions” dropdown in the Virtual Images row
+3. From the “Visibility” drop down, select either “Public” or “Private”. Public will share the
+4. From the “Tenant” field, start typing the name of the Tenant to assign the Virtual Image to. Matching Tenants will populate, then select the Tenant to add. 
+
+   NOTE
+
+   Virtual Images can be set to Private, but accessible to more that one Tenant
+
+#### Results
+
+#. Repeat step 4 for all Tenants requiring access to the virtual image. .. To remove access for an Tenant, click the “x” next to the Tenant name #. Select Save Changes in the modal
+
+![../../_images/configuring_multi_tenancy-d9abe.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-453CA12C-D7A9-4CFE-83D3-B133334EE8C4-high.png)
+
+The Virtual Image will now be available for use by the assigned Tenants.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json b/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
new file mode 100644
index 0000000..fb421e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+  "title": "Chef",
+  "ordinal": 378,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html",
+  "topic_cluster": {
+    "clustering_title": "Chef",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-826F09D8-C40B-483D-9CB5-CE504BD18810",
+        "clustering_title": "Chef"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md b/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
new file mode 100644
index 0000000..00b0a69
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.md
@@ -0,0 +1,74 @@
+# Chef
+
+## Overview
+
+HPE Morpheus Enterprise integrates with one or multiple Chef servers to be used for bootstrapping while provisioning or as tasks in workflows in the Automation section. These workflows can then be run during provisioning in the provisioning wizard Automation pane, or on an existing Instance by selecting Run Workflows from the Actions menu on the Instance detail page. Workflows can also be added to Instances in the blueprint and app sections.
+
+## Add Chef Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations and select + New Integration
+2. Select Integration Type “Chef”
+3. Populate the following fields: 
+
+   - Name: Name of the Chef Integration in HPE Morpheus Enterprise
+   - Chef Endpoint: url of chef server api endpoint in <https://api.example.com> format. Do not add /organization/xxxx here, which is populated in the Chef Organization field
+   - Chef Version: 12.3.0 by default, can be changed to use a different/more recent version of chef
+   - Chef Organization: Chef Server Organization
+   - Chef User: Chef Server User
+   - User Private Key: The private key of the user with access to this chef server
+   - Organization Validator: Validator key for the organization
+4. Save Changes
+
+### Results
+
+The added Chef Integration is now available for use in HPE Morpheus Enterprise. The Chef Integration can be added to Clouds or Groups to auto-bootstrap nodes and specify Environment, Node ID, Runlist, Attributes and Tags when creating instances. The Chef integration can also be selected in the Chef Server dropdown when creating a Chef Bootstrap-type Task.
+
+NOTE
+
+Integrating Chef with HPE Morpheus Enterprise enables a user to bootstrap a node using Chef Bootstrap-type Tasks or Chef associations with Clouds or infrastructure Groups. It does not enable users to update run-lists on the Chef server for nodes which have already been bootstrapped.
+
+## Scope Chef Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Scope Chef Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Chef Integration.
+5. Save Changes
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Chef Integration added, a Chef section will appear in the Config section of the provisioning wizard. By default, Chef is enabled, but can be disabled by expanding the Chef section and unchecking Enable Chef.
+
+Chef Integration Provisioning options:
+
+Enable Chef
+:   Select to bootstrap
+
+Chef Environment
+:   Populate Chef environment, or leave as \_default
+
+Chef Node ID
+:   Defaults to instance name, configurable.
+
+Chef Runlist
+:   Add Runlist
+
+CHEF ATTRIBUTES
+:   Add Chef Attributes
+
+CHEF TAGS
+:   Add Chef tags
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json b/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
new file mode 100644
index 0000000..368dee3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+  "title": "Activity",
+  "ordinal": 78,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html",
+  "topic_cluster": {
+    "clustering_title": "Activity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-82C53DF1-4293-41E2-A90A-740C1814DD12",
+        "clustering_title": "Activity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md b/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
new file mode 100644
index 0000000..aa44b12
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.md
@@ -0,0 +1,61 @@
+# Activity
+
+The Activity section displays a recent activity report for Auditing. HPE Morpheus Enterprise defines an activity as any major action performed on an instance or server, such as, but not limited to adding a server, deleting a server, provisioning an instance, deleting an instance, creating a backup, and so on. This view can be searched and filtered by type, user, and date range.
+
+![Activity page](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-01147D13-F369-4441-B97D-9354DA79DF93-high.png)
+
+## Activity
+
+There are three types of activities that are displayed in the Activity Reports:
+
+- Backup
+- Provisioning
+- Alert
+
+### To View a Recent Activity report:
+
+#### Procedure
+
+1. Select the `Operations` link in the navigation bar.
+2. Select `Activity` in the sub navigation bar.
+
+#### Results
+
+Recent activity is displayed in order from recent to oldest. This view can be searched and filtered by type, user, and date range.
+
+### Review
+
+To review the item the activity occurred on, click the name of the activity and it will go to a new page and display that item.
+
+NOTE
+
+Deleted activities are displayed as an alert and do not contain a link to the event item. If the activity is not a deletion event we provide a link on the activity name to go to the item the activity occurred on. Delete activity alerts are shown for Instances, servers, Clouds, Groups, and Monitoring Checks.
+
+### To Filter:
+
+#### Procedure
+
+1. Click the filter drop down of type of filter you want to apply.
+2. Select the appropriate filter.
+
+## Alarms
+
+The ALARMS section shows Operation notifications from Cloud and other Service Integrations. Cloud and other Service Integration Alarms are not generated by HPE Morpheus Enterprise but synced and displayed for visibility in HPE Morpheus Enterprise.
+
+![Alarms](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-444E2530-12E2-439A-A1C7-EED4D7F91D38-high.png)
+
+## History
+
+The HISTORY section shows Process History from Instances and Apps processes. This is an aggregate view of the `History` tab in Instance and App details pages.
+
+![History](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DE8D2A86-CAB3-4D94-9D4C-83C5FA49585A-high.png)
+
+Processes can be expanded to view all process steps and process history detail including output and errors.
+
+Access to HISTORY is given by the `Operations:Activity` Role permission.
+
+The Logs displayed in Administration > Health > Morpheus Logs are from `/var/log/morpheus/morpheus-ui/current`. These logs show all ui activity and are useful for troubleshooting and auditing.
+
+NOTE
+
+Stack traces in Administration > Health > Morpheus Logs are filtered for HPE Morpheus Enterprise services. Complete stack traces can be found in `/var/log/morpheus/morpheus-ui/current`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json b/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
new file mode 100644
index 0000000..db3b6a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+  "title": "Task Results",
+  "ordinal": 111,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html",
+  "topic_cluster": {
+    "clustering_title": "Task Results",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-84B6C16D-5601-4CFB-9C53-47AE75271884",
+        "clustering_title": "Task Results"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md b/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
new file mode 100644
index 0000000..c00a3b3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.md
@@ -0,0 +1,161 @@
+# Task Results
+
+## Overview
+
+Using Task results, the output from any preceding Tasks within the same Workflow phase is available to be called into additional Tasks. The results are stored on the `results` variable. Since results are available to all Tasks, we can use results from any or all prior Tasks so long as they are executed within the same provision phase.
+
+In script type tasks, if a RESULT TYPE is set, HPE Morpheus Enterprise will store the output on the `results` variable. It’s important to understand that the result type indicates the format of the Task output HPE Morpheus Enterprise should expect. HPE Morpheus Enterprise will parse that output into a Groovy map which can be retrieved and further parsed by resolving the `results` variable. If the RESULT TYPE is incorrectly set, HPE Morpheus Enterprise may not be able to store the Task results correctly. Jump to the section on [Script Config Examples](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1AAB6E42-CAE7-456C-85D2-FC3E917F731C.xml) to see how script results are processed in various example cases.
+
+## Results Types
+
+- Single Value
+  :   Entire task output is stored in `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable.
+- Key/Value pairs
+  :   Expects `key=value,key=value` output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+- JSON
+  :   Expects `key:value,key:value` json formatted output. Entire task output is available with `<%=results.taskCode%>` or `<%=results["Task Name"]%>` variable (output inside `[]`). Individual Values are available with `<%=results.taskCode.key%>` variables.
+
+IMPORTANT
+
+The entire output of a script is treated as results, not just the last line. Ensure formatting is correct for the appropriate result type. For example, if Results Type is `json` and the output is not fully json compatible, the result would not return properly.
+
+IMPORTANT
+
+Task results are not supported for Library Script task types
+
+## Script Config Examples
+
+Single Value using Task Code
+:   Source Task Config
+    :   - NAME: Var Code (single)
+        - CODE: singleExample
+        - RESULT TYPE: Single Value
+        - SCRIPT: `echo "string value"`
+
+    Source Task Output: `string value`
+
+    Results Task Config (using task code in variable)
+    :   - NAME: N/A
+        - CODE: N/A
+        - RESULT TYPE: N/A
+        - SCRIPT: `echo "single: <%=results.singleExample%>"`
+
+    Results Task Output: `single: string value`
+
+Single Value using Task Name
+:   Source Task Config
+    :   NAME
+        :   Var Code
+
+        CODE
+        :   none
+
+        RESULT TYPE
+        :   Single Value
+
+        SCRIPT
+        :   `echo "string value"`
+
+    Source Task Output
+    :   `string value`
+
+    Results Task using task name in variable
+    :   Results Task Script
+        :   `echo "task name: <%=results["Var Code"]%>"`
+
+        Results Task Output
+        :   `task name: test value`
+
+Key/Value Pairs
+:   Source Task Config
+    :   NAME
+        :   Var Code (keyval)
+
+        CODE
+        :   keyvalExample
+
+        RESULT TYPE
+        :   Key/Value pairs
+
+        SCRIPT
+        :   `echo "flash=bang,ping=pong"`
+
+    Source Task Output
+    :   `flash=bang,ping=pong`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "keyval: <%=results.keyvalExample%>"`
+
+        Results Task Output
+        :   `keyval: [flash:bang, ping:pong]`
+
+    Results Task for a single value)
+    :   Results Task Script
+        :   `echo "keyval value: <%=results.keyvalExample.flash%>"`
+
+        Results Task Output
+        :   `keyval value: bang`
+
+JSON
+:   Source Task Config
+    :   NAME
+        :   Var Code (json)
+
+        CODE
+        :   jsonExample
+
+        RESULT TYPE
+        :   JSON
+
+        SCRIPT
+        :   `echo "{\"ping\":\"pong\",\"flash\":\"bang\"}"`
+
+    Source Task Output
+    :   `{"ping":"pong","flash":"bang"}`
+
+    Results Task for all results
+    :   Results Task Script
+        :   `echo "json: <%=results.jsonExample%>"`
+
+        Results Task Output
+        :   `json: [ping:pong, flash:bang]`
+
+    Results Task for a single value
+    :   Results Task Script
+        :   `echo "json value: <%=results.jsonExample.ping%>"`
+
+        Results Task Output
+        :   `json value: pong`
+
+    Multiple Task Results
+    :   Results Task Script
+        :   ```
+            ```
+            echo "single: <%=results.singleExample%>"  
+            echo "task name: <%=results["Var Code"]%>"  
+            echo "keyval: <%=results.keyvalExample%>"  
+            echo "keyval value: <%=results.keyval.flash%>"  
+            echo "json: <%=results.jsonExample%>"  
+            echo "json value: <%=results.jsonExample.ping%>"
+            ```
+            ```
+
+        Results Task Output
+        :   ```
+            ```
+            single: string value  
+            task name: string value  
+            keyval: [flash:bang, ping:pong]  
+            keyval value: bang  
+            json: [ping:pong, flash:bang]  
+            json value: pong
+            ```
+            ```
+
+## Workflow Config
+
+Add one or multiple tasks with Results Type configured to a workflow, and the results will be available to all tasks in the same phase of the workflow via the `<%=results.variables%>` during the workflow execution.
+
+- Task Results are only available to tasks in the same workflow phase
+- Task Results are only available during workflow execution
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json b/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
new file mode 100644
index 0000000..60aa3a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+  "title": "Answer Files",
+  "ordinal": 252,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.html",
+  "topic_cluster": {
+    "clustering_title": "Answer Files",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2",
+        "clustering_title": "Answer Files"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md b/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
new file mode 100644
index 0000000..2ab924e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-85336EA6-ECB0-48EF-8646-6BDC4FBEDFE2.md
@@ -0,0 +1,51 @@
+# Answer Files
+
+Answer files are like lists of answers for questions that you know the setup program is going to ask but the user is not prepared to answer. They contain one or more sections, and each section contains one or more properties in the form name=value. Morpheus provides Answer Files for ESXi, CentOS, Ubuntu and XenServer, and user can add their own.
+
+## Add Answer Files
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab then click the Add Answer File button.
+4. From the New Answer File Wizard input the following information 
+
+   Name
+   :   Name of the answer file.
+
+   Description(optional)
+   :   Description of the new answer file.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Script Name
+   :   Name of the new answer file.
+
+   Script Version
+   :   Version of the new answer file.
+
+   Script
+   :   The script for the new answer file.
+5. Save
+
+## Edit Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab
+4. Click the edit icon on the row of the answer file you wish to edit.
+5. Modify information as needed.
+6. Save Changes
+
+## Delete Answer File
+
+### Procedure
+
+1. Click the Infrastructure link in the navigation bar.
+2. Click the Boot link in the sub navigation bar
+3. Select the Answer Files tab.
+4. Click the delete icon on the row of the answer file you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json b/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
new file mode 100644
index 0000000..14c02af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+  "title": "Overview",
+  "ordinal": 316,
+  "parent_title": "Policies",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md b/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
new file mode 100644
index 0000000..1a8b36e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.md
@@ -0,0 +1,3 @@
+# Overview
+
+Policies add governance, ease of use, cost-savings, and auditing features to HPE Morpheus Enterprise. HPE Morpheus Enterprise enables end users to create Policies scoped to Users, Roles, Groups, Clouds, Tenants, Networks, Plans, and Global scoping to give Admins full control and governance over their environments. The available scoping will vary from one Policy type to another. See the section below for information on each Policy type and guides for more complex Policy implementation.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json b/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
new file mode 100644
index 0000000..e98ce11
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+  "title": "Costing",
+  "ordinal": 73,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html",
+  "topic_cluster": {
+    "clustering_title": "Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1",
+        "clustering_title": "Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md b/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
new file mode 100644
index 0000000..2a657c1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.md
@@ -0,0 +1,7 @@
+# Costing
+
+**Subtopics**  
+
+- **[Budgets](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-33E060CF-9C8E-4AA3-971B-7C5E06954157.html)**
+- **[Invoices](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html)**
+- **[Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json b/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
new file mode 100644
index 0000000..51e30fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+  "title": "Task Configuration",
+  "ordinal": 109,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html",
+  "topic_cluster": {
+    "clustering_title": "Task Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D",
+        "clustering_title": "Task Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md b/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
new file mode 100644
index 0000000..925979f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.md
@@ -0,0 +1,322 @@
+# Task Configuration
+
+## Ansible Playbook
+
+![ansible](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FCAE649B-4E95-4F5B-A897-78C6A01F895D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ANSIBLE REPO:** Select existing Ansible Integration
+- **GIT REF:** Specify tag or branch (Option, blank assumes default)
+- **PLAYBOOK:** Name of playbook to execute, both `playbook` and `playbook.yml` format supported
+- **TAGS:** Enter comma separated tags to filter executed tasks by (ie `--tags`)
+- **SKIP TAGS:** Enter comma separated tags to run the playbook without matching tagged tasks (ie `--skip-tags`)
+
+IMPORTANT
+
+Using different Git Refs for multiple Ansible Tasks in same Workflow is not supported. Git Refs can vary between Workflows, but Tasks in each Workflow must use the same Git Ref.
+
+## Ansible Tower Job
+
+![ansibletower](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AF431C26-FA58-4140-8DAA-09CCA119F769-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TOWER INTEGRATION:** Select an existing Ansible Tower integration
+- **INVENTORY:** Select an existing Inventory, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Inventory
+- **GROUP:** Enter a group name, when bootstrapping an Instance, HPE Morpheus Enterprise will add the Instance to the Group if it exists. If it does not exist, HPE Morpheus Enterprise will create the Group
+- **JOB TEMPLATE:** Select an existing job template to associate with the Task
+- **SCM OVERRIDE:** If needed, specify an SCM branch other than that specified on the template
+- **EXECUTE MODE:** Select Limit to Instance (template is executed only on Instance provisioned), Limit to Group (template is executed on all hosts in the Group), Run for all (template is executed on all hosts in the Inventory), or Skip Execution (to skip execution of the template on the Instance provisioned)
+
+## Chef bootstrap
+
+![chef](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-531590A7-AFBE-40A7-BBBF-D4E7EB32974A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **CHEF SERVER:** Select existing Chef integration
+- **ENVIRONMENT:** Populate Chef environment, or leave as `_default`
+- **RUN LIST:** Enter Run List, eg `role[web]`
+- **DATA BAG KEY:** Enter data bag key (will be masked upon save)
+- **DATA BAG KEY PATH:** Enter data bag key path, eg `/etc/chef/databag_secret`
+- **NODE NAME:** Defaults to Instance name, configurable
+- **NODE ATTRIBUTES:** Specify attributes inside the `{}`
+
+## Conditional Workflow
+
+![../../_images/conditional.svg](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C6A92829-120A-43A5-AAFA-221E3A1C89EF-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **LABELS:** A comma separated list of Labels for organizational purposes. See elsewhere in HPE Morpheus Enterprise docs for additional details on utilizing Labels
+- **CONDITIONAL (JS):** JavaScript logic which determines the Operational Workflow which is ultimately run. If it resolves to `true`, the “If” Workflow is run and if it resolves to `false` the “Else” Workflow is run
+- **IF OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `true`
+- **ELSE OPERATIONAL WORKFLOW:** Set the Operational Workflow which should be run if the JavaScript conditional resolves to `false`
+
+## Groovy script
+
+![groovy](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DA7C204B-DFAC-493A-A877-21B026F00D4D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the Groovy script if not sourcing it from a repository
+
+## Email
+
+![email](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9C895BAB-4D33-430F-8250-668229AB3E8A-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **SOURCE:** Choose local to draft or paste the email directly into the Task. Choose Repository or URL to bring in a template from a Git repository or another outside source
+- **EMAIL ADDRESS:** Email addresses can be entered literally or HPE Morpheus Enterprise automation variables can be injected, such as `<%=instance.createdByEmail%>`
+- **SUBJECT:** The subject line of the email, HPE Morpheus Enterprise automation variables can be injected into the subject field
+- **CONTENT:** The body of the email is HTML. HPE Morpheus Enterprise automation variables can be injected into the email body when needed
+- **SKIP WRAPPED EMAIL TEMPLATE:** The HPE Morpheus Enterprise-styled email template is ignored and only HTML in the Content field is used
+
+TIP
+
+To whitelabel email sent from Tasks, select SKIP WRAPPED EMAIL TEMPLATE and use an HTML template with your own CSS styling
+
+## HTTP (API)
+
+![http](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3D6C1D43-48AE-4C22-AB38-7FF3748A8812-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **URL:** An HTTP or HTTPS URL as the HTTP Task target
+- **HTTP METHOD:** GET (default), POST, PUT, PATCH, HEAD, or DELETE
+- **AUTH USER:** Username for username/password authentication
+- **PASSWORD:** Password for username/password authentication
+- **BODY:** Request Body
+- **HTTP HEADERS:** Enter requests headers, examples below:
+
+|  |  |
+| --- | --- |
+| Authorization | Bearer token |
+| Content‐Type | application/json |
+
+- **IGNORE SSL ERRORS:** Mark when making REST calls to systems without a trusted SSL certificate
+
+## Javascript
+
+![javascript](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-20848F50-8905-4E2C-B84A-2964DB407179-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Javascript contents to execute
+
+## jRuby Script
+
+![jruby](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6DDC7639-A017-4555-A527-0F3DD5216833-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Contents of the jRuby script is entered here if it’s not being called in from an outside source
+
+## Library Script
+
+![libraryscript](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C1C0F695-54E0-43B9-90F3-A1112041085D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SCRIPT:** Search for an existing script in the typeahead field
+
+## Library Template
+
+![template](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-296B3993-FE5F-4AB8-B8AE-71D293861775-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **TEMPLATE:** Search for an existing template in the typeahead field
+
+## Nested Workflow
+
+![../../_images/nestedworkflow.svg](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-949F99E1-949C-499A-980C-1AB5753BA11D-high.svg)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **OPERATIONAL WORKFLOW:** The Workflow to be embedded as a Task for reference inside other Workflows
+
+## Powershell Script
+
+![powershell](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-69279397-D83C-4B50-9330-CA25F54BE9B0-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **VERSION:** Select the version of Powershell this Task should run in. Powershell 5 is the default selection, Powershell 6 or 7 must be installed on the target to select those versions
+- **ELEVATED SHELL:** Run script with administrator privileges
+- **IP ADDRESS:** IP address of the PowerShell Task target
+- **PORT:** SSH port for PowerShell Task target (5985 default)
+- **USERNAME:** Username for PowerShell Task target
+- **PASSWORD:** Password for PowerShell Task target
+- **Content:** Enter script to execute if not calling the script in from an outside source
+
+NOTE
+
+Setting the execution target to local requires Powershell to be installed on the HPE Morpheus Enterprise appliance box(es). [Microsoft Documentation](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell-on-linux?view=powershell-7.2) contains installation instructions for all major Linux distributions and versions.
+
+## Puppet Agent Install
+
+![puppet](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D625B993-30CE-4020-ACA7-B098CF811E3F-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **PUPPET MASTER:** Select Puppet Master from an existing Puppet integration
+- **PUPPET NODE NAME:** Enter Puppet node name. Variables supported eg. `<%= instance.name %>`
+- **PUPPET ENVIRONMENT:** Enter Puppet environment, eg. `production`
+
+## Python Script
+
+![python](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AB6EBB6F-6FB7-48D7-A2F6-EB4F4012B5A8-high.png)
+
+IMPORTANT
+
+Python Tasks use virtual environments. For this reason, `virtualenv` must be installed on your appliances in order to work with Python Tasks. See the information below for more detailed steps to install `virtualenv` on your HPE Morpheus Enterprise appliance node(s).
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **CONTENT:** Python script to execute is entered here if not pulled in from an outside repository
+- **COMMAND ARGUMENTS:** Optional arguments passed into the Python script. Variables supported eg. `<%= instance.name %>`
+- **ADDITIONAL PACKAGES:** Additional packages to be installed after `requirements.txt` (if detected). Expected format for additional packages: ‘packageName==x.x.x packageName2==x.x.x’, the version must be specified
+- **PYTHON BINARY:** Optional binary to override the default Python binary
+
+NOTE
+
+When troubleshooting errors in Python scripts using line numbers reported in HPE Morpheus Enterprise UI (such as in Task execution histories), you must subtract four line numbers to arrive at the correct line in the Python document. This is because HPE Morpheus Enterprise injects four lines at execution time to add HPE Morpheus Enterprise environment variables.
+
+**Enterprise Proxy Considerations**
+
+Additional considerations must be made in enterprise proxy environments where Python Tasks are run with additional package download requirements. These additional packages are downloaded using `pip` and may not obey global HPE Morpheus Enterprise proxy rules. To deal with this, create or edit the pip configuration file at `/etc/pip.conf`. Your configuration should include something like the following:
+
+```
+```
+[global]  
+proxy = http://some-proxy-ip.com:8087
+```
+```
+
+For more information, review the Pip documentation on using proxy servers [here](https://pip.pypa.io/en/stable/user_guide/#using-a-proxy-server).
+
+**CentOS 7 / Python 2.7 (RHEL system Python)**
+
+With a fresh install of HPE Morpheus Enterprise on a default build of CentOS 7, Python Tasks will not function due to the missing requirement of `virtualenv`.
+
+If you attempt to run a python task, you will get an error similar to the following:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-8ae51ebf-749c-4354-b6e4-11ce541afad5/bin/python: command not found
+```
+```
+
+In order to run HPE Morpheus Enterprise Python Tasks in CentOS 7, install `virtualenv`: `yum install python-virtualenv`
+
+If you require `python3`, you can specify the binary to be used while building the virtual environment. In a default install, do the following: `yum install python3`. Then, in your HPE Morpheus Enterprise Python Task, specify the binary in the PYTHON BINARY field as “/bin/python3”. This will build a virtual environment in `/tmp` using the `python3` binary, which is equivalent to making a virtual environment like so: `virtualenv ~/venv -p /bin/python3`.
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+**CentOS 8 and Python**
+
+In CentOS 8, Python is not installed by default. There is a `platform-python` but that should not be used for anything in userland. The error message with a default install of CentOS 8 will be similar to this:
+
+```
+```
+Task Execution Failed on Attempt 1  
+sudo: /tmp/py-cffc9a8f-c40d-451d-956e-d6e9185ade33/bin/python: command not found
+```
+```
+
+The default `virtualenv` for CentOS 8 is the python3 variety, for HPE Morpheus Enterprise to use Python Tasks, do the following: `yum install python3-virtualenv`
+
+If Python2 is required, do the following: `yum install python2` and specify `/bin/python2` as the PYTHON BINARY in your HPE Morpheus Enterprise Task.
+
+This will build a `virtualenv` in `/tmp` using the `python2` binary, which is equivalent to making a `virtualenv` like so: `virtualenv ~/venv -p /bin/python2`
+
+If you wish to install additional Python packages into the virtual environment, put them in `pip` format and space-separated into the ADDITIONAL PACKAGES field on the Python Task. Use the help text below the field to ensure correct formatting.
+
+## Restart
+
+![restart](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12DFE21D-BC68-4969-B496-340CA3E40690-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+
+## Shell Script
+
+![shellscript](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-66BC263C-CF8F-4199-B05B-99D786BF9288-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **SUDO:** Mark the box to run the script as `sudo`
+- **CONTENT:** Script to execute is entered here if not pulled in from an outside repository
+
+TIP
+
+When the EXECUTE TARGET option is set to “Local” (in other words, the Task is run on the appliance itself), two additional fields are revealed: GIT REPO and GIT REF. Use GIT REPO to set the PWD shell variable (identifies the current working directory) to the locally cached repository (ex. /var/opt/morpheus-node/morpheus-local/repo/git/76fecffdf1fe96516e90becdab9de) and GIT REF to identify the Git branch the Task should be run from if the default (typically main or master) shouldn’t be used. If these options are not set, the working folder will be /opt/morpheus/lib/tomcat/temp which would not allow scripts to reference file paths relative to the repository (if needed).
+
+## vRealize Orchestrator Workflow
+
+![vro](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ABE75AA7-6B9F-46FE-9A67-D463924B577D-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **RESULT TYPE:** Single Value, Key/Value Pairs, or JSON
+- **vRO INTEGRATION:** Select an existing vRO integration
+- **WORKFLOW:** Select a vRO workflow from the list synced from the selected integration
+- **PARAMETER BODY (JSON):**
+
+## Write Attributes
+
+![wa](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C48074E2-3DB2-4459-98D0-AC5282256582-high.png)
+
+- **NAME:** Name of the Task
+- **CODE:** Unique code name for API, CLI, and variable references
+- **ATTRIBUTES:** A JSON map of arbitrary values to write to the attributes property of the target resource
+
+TIP
+
+This is often useful for storing values from one phase of a Provisioning Workflow for access in another phase. See the video demo below for a complete example.
+
+There are a number of ways that a JSON payload can be statically drafted within a Write Attributes Task or called into the Task as a result from a prior Task. Consider the following examples:
+
+To pass in a static JSON map with static values, use the format shown below.
+
+```
+```
+{  
+  "my_key1": "my_value1",  
+  "my_key2": "my_value2"  
+}
+```
+```
+
+To pass in a static JSON map with dynamic values seeded from prior Task results, ensure the RESULT TYPE value of one or more of the prior Tasks in the Workflow phase is set to “Single Value” and refer to the values within the JSON map as shown in the next example. Note that “taskCode1” and “taskCode2” refer to the CODE field value for the Task whose output you wish to reference.
+
+```
+```
+{  
+  "my_key1": "<%=results.taskCode1%>",  
+  "my_key2": "<%=results.taskCode2%>"  
+}
+```
+```
+
+To pass in a dynamic JSON map returned from a prior Task, format your Write Attributes Task as shown in the next example. Ensure that the RESULT TYPE value for the Task returning a JSON map is set to “JSON”. Note that “taskCode” in the example refers to the CODE field value for the Task being referenced. In order for the JSON map to be set correctly and able to be referenced from future Tasks, you must set the “instances” key and call the `encodeAsJSON()` Groovy method as shown in the example.
+
+```
+```
+{  
+  "instances": <%=results.taskCode?.encodeAsJSON()%>  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json b/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
new file mode 100644
index 0000000..1319e92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+  "title": "Containers",
+  "ordinal": 213,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8808CDAD-319E-4259-99D8-4D43440E63FE",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md b/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
new file mode 100644
index 0000000..eaed2bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.md
@@ -0,0 +1,9 @@
+# Containers
+
+![../../_images/infra_compute_header_containers_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ECD57864-C48E-460D-A2E1-5B01CC0F8610-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Container Type Cloud
+
+The containers tab lists all Containers associated with HPE Morpheus Enterprise Instances accessible to the user. Note additional system level containers from Kubernetes and Docker Clusters are not listed here but are accessible in Cluster detail sections.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json b/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
new file mode 100644
index 0000000..220b30b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+  "title": "Plugins",
+  "ordinal": 313,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.html",
+  "topic_cluster": {
+    "clustering_title": "Plugins",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3",
+        "clustering_title": "Plugins"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md b/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
new file mode 100644
index 0000000..5615723
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8838F0ED-76A6-4E9A-ACE2-BB544ED1E5B3.md
@@ -0,0 +1,23 @@
+# Plugins
+
+## Overview
+
+HPE Morpheus Enterprise is extendable with custom plugins for Task types, UI tabs, reports, approvals, cypher, and more. Plugins are added from the Plugins tab of the Integration page under Administration (Administration > Integrations > Plugins). Simply browse for a local plugin file (.jar) to add it to the UI. Custom plugins can also be edited or deleted by clicking on the pencil or trash can icons in the corresponding row.
+
+HPE Morpheus Enterprise maintains a repository of internally-developed and vetted plugins at HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/). These plugins can be downloaded and added to HPE Morpheus Enterprise using the instructions in the prior paragraph. Alongside the download link, you can also find helpful readme information that discusses how the plugin can be used and which versions of HPE Morpheus Enterprise it’s compatible with.
+
+With at least one plugin integrated, HPE Morpheus Enterprise will show details on each plugin from the Plugins List View. The following information is displayed:
+
+- **NAME:** The name given to the plugin
+- **DESCRIPTION:** A description value (if any) coded into the plugin
+- **FILE NAME:** The .jar filename
+- **VERSION:** The plugin version number
+- **STATUS:** The status of the plugin, such as “loaded” when the plugin is ready for use
+- **STATUS MESSAGE:** A status message (if any) for the plugin
+- **ENABLED:** If the plugin is enabled, a check mark appears here. Disabled plugins are also grayed out
+
+Additional information about each plugin can be viewed by clicking on the pencil (edit) icon. Most of the information in this modal is read-only but you can enable or disable plugins from this pane.
+
+Please visit the [Morpheus Developer Portal](https://developer.morpheusdata.com) for Plugin Architecture SDK documentation and help getting started with custom Plugin development.
+
+![../../_images/plugins_new.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E806E13E-76E4-477E-BE44-5A16FC97B809-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json b/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
new file mode 100644
index 0000000..e078947
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+  "title": "Troubleshooting",
+  "ordinal": 345,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md b/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
new file mode 100644
index 0000000..9914324
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8849B97F-1E78-4FD1-9000-CA1BA48F8D62.md
@@ -0,0 +1,20 @@
+# Troubleshooting
+
+- [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+**Subtopics**  
+
+- **[logback config](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7BF390A3-E01F-45A6-BE49-68F0CE828FD7_2.html)**
+- **[Ansible Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-014CB518-CCE4-449A-9BCC-241FF8FEA3C5.html)**
+- **[Attaching Logs to Case](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3771B5D9-F61F-4ACF-B1A6-30C04369B2F6.html)**
+- **[CLI Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html)**
+- **[Cannot Login](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-099A151A-FA2C-4C2C-B3C5-5E3DB3DFCDE9.html)**
+- **[How to un-manage an Instance/VM/Host](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8143252C-EC38-43B2-B2E0-443A60C01768.html)**
+- **[MySQL Too many connections error](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html)**
+- **[HPE Morpheus Enterprise Agent Install Troubleshooting](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html)**
+- **[HPE Morpheus Enterprise UI not loading after upgrade or reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-44644079-BC85-448F-B542-23E18E9D5602.html)**
+- **[Remote Console](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html)**
+- **[SSL Self-signed Certificate Regeneration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-008B6CB0-CC99-4E40-89CE-2EA5D3389D8F.html)**
+- **[Unable to Delete Tenant](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-444458D2-C75F-4017-9EBC-B9715EFB5AE2.html)**
+- **[Unable to Provision a Custom Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7D6FFE9A-0436-49ED-9453-93C35F0B86C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json b/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
new file mode 100644
index 0000000..f2f3d16
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+  "title": "Options",
+  "ordinal": 152,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.html",
+  "topic_cluster": {
+    "clustering_title": "Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C",
+        "clustering_title": "Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md b/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
new file mode 100644
index 0000000..e50a2c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8955636C-10F0-4B97-A0B2-9E1E1D5E2B9C.md
@@ -0,0 +1,11 @@
+# Options
+
+Options are user-defined custom inputs that are used throughout HPE Morpheus Enterprise. Depending on the type of Input being created, users may need to create only an Input, or it might need to be paired with an Option List. Option Lists are static or dynamic lists of selections that would be associated with an Input if the user must make choices from a select list or typeahead field. This section discusses how to create different types of Inputs depending on the situation and powerful tools the user can take advantage of, such as dynamically filtered cascading inputs, logically generated Option Lists called from local or remote sources, and more.
+
+**Subtopics**  
+
+- **[Forms](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3E6007AB-2F77-4783-8610-592F1BB9125B.html)**
+- **[Inputs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2CE25FBB-DE0F-4B4C-8FF7-07535555A706.html)**
+- **[Option Lists](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6EDDD562-5A37-4E44-B3C0-A209C0DAA299.html)**
+- **[LDAP Query Variables](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html)**
+- **[Creating an Option List Based on an LDAP Query](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json b/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
new file mode 100644
index 0000000..29da548
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+  "title": "Firmware and Driver Lifecycle Management",
+  "ordinal": 452,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html",
+  "topic_cluster": {
+    "clustering_title": "Firmware and Driver Lifecycle Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779",
+        "clustering_title": "Firmware and Driver Lifecycle Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md b/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
new file mode 100644
index 0000000..b110063
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.md
@@ -0,0 +1,6 @@
+# Firmware and Driver Lifecycle Management
+
+| S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Morpheus / iLO fails to initialize the server after the SPP update | Server provisioning fails with errors similar to:  - `Base.1.18.ResourceMissingAtURI` - `Drives/64515 not found` - `HTTP null` - Storage object lists drive URIs that cannot be resolved | 1. Verify storage drive URIs:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Systems/1/Storage/<controller> | jq    ```    ``` 2. Validate drive URI exists:     ```    ```    curl -k -u <user>:<pass>                   https://<ilo>/redfish/v1/Chassis/<chassis>/Drives/<id> | jq    ```    ``` 3. Confirm SPP was applied recently | Morpheus / iLO logs | Typically caused by stale Redfish drive references after SPP. |
+| 2 | After SPP, Redfish drive tree mismatch | Storage object shows drive count and IDs, but drive URIs return ResourceMissingAtURI | Perform a **Full Cold Power Cycle** (not reboot):   1. Power OFF the server (OS or iLO) 2. Remove both power cables 3. Wait 60 seconds 4. Reconnect power cables 5. Power ON the server | iLO event log, Smart Array logs | Required for Gen11/Gen12 after firmware updates. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json b/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
new file mode 100644
index 0000000..2ac78c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+  "title": "Automation Integrations",
+  "ordinal": 532,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-89FD5558-DFD3-459B-A56D-BD998574F805",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md b/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
new file mode 100644
index 0000000..432a272
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-89FD5558-DFD3-459B-A56D-BD998574F805.md
@@ -0,0 +1,14 @@
+# Automation Integrations
+
+- Ansible
+- Ansible Tower
+- Chef
+- Puppet
+
+NOTE
+
+Automation integrations can be added and managed in Administration > Integrations as well. Adding and editing Integrations in Library > Integrationsand Administration > Integrations are the same dataset and additions and updates are reflected in both sections.
+
+NOTE
+
+Role access for `Integrations: Ansible` determines user access to Ansible Integration detail page, which contains Ansible command line and execution access.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json b/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
new file mode 100644
index 0000000..47b0f13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+  "title": "Add Load Balancer to Instance",
+  "ordinal": 497,
+  "parent_title": "Add F5BigIP load balancer",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer to Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E",
+        "clustering_title": "Add Load Balancer to Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md b/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
new file mode 100644
index 0000000..0a1467e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A0A2E25-5A12-4D5C-AB3F-53B62D7D2B3E.md
@@ -0,0 +1,11 @@
+# Add Load Balancer to Instance
+
+Load Balancers can be added to Instances during Provisioning or to existing Instances. For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+NOTE
+
+For Load Balancer settings to appear during provisioning, or for the scale tab to be available on an Instance, the instances Node Type must have a LB port defined.
+
+**Subtopics**  
+
+- **[Add Load Balancer during Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json b/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
new file mode 100644
index 0000000..7a19e74
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+  "title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+  "ordinal": 353,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391",
+        "clustering_title": "HPE Morpheus Enterprise Agent Install Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md b/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
new file mode 100644
index 0000000..1606b54
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A557829-64DF-4A0A-84FC-FC2C8755B391.md
@@ -0,0 +1,172 @@
+# HPE Morpheus Enterprise Agent Install Troubleshooting
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Methods
+
+Morpheus Agent installation supports multiple install methods.
+
+- SSH/WinRM
+- VM Tools
+- Cloud-Init & Cloudbase-Init
+- Windows Unattended
+- Manual
+
+### For All Agent Install Methods
+
+When an Instance is provisioned and the Agent does not install, verify the following for any Agent install mode:
+
+- The HPE Morpheus Enterprise Appliance URL (Administration > Settings) is both reachable and resolvable from the provisioned node
+- The Appliance URL begins with https://, not http://
+
+NOTE
+
+Be sure to use https:// even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise appliance from provisioned VMs and container hosts on port 443 (needed for Agent communication)
+- Private (non-HPE Morpheus Enterprise provided) VM images and templates must have their credentials stored. These can be entered or edited in the Library > Virtual Images section by clicking the Actions dropdown on an image detail page and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+- The Instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced Options section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to Cloud network sections for IPAM
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or Cloud appliance
+
+### SSH
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials set on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+NOTE
+
+Administrator user is required for Windows Agent install.
+
+### VMware Tools (vmtools)
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Sudo privileges required for Linux
+- Administrator User required for Windows (SID 500)
+
+### Cloud-Init
+
+- Cloud-Init settings configured in Administration > Settings > Provisioning section
+- Cloud-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+
+### Cloudbase-Init
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- Cloudbase-Init installed on Virtual Image
+- `Cloud-Init` enabled on Virtual Image config
+- Cloudbase-Init is only required for OpenStack Cloud types
+
+NOTE
+
+Unattend Agent Installation and customizations are recommended over Cloudbase-Init
+
+### Windows Unattended
+
+- Windows Administrator Password defined in Administration > Settings > Provisioning section
+- VMware: `Force Guest Customizations` set to forced on Virtual Image config when using DHCP (Static Assignment will already force Guest Customizations)
+- Nutanix & SCVMM: Virtual Image is sysprepped and shutdown, `Sysprep Enabled` flagged on Virtual Image config
+
+### Manual
+
+Agent Install scripts can be downloaded from HPE Morpheus Enterprise by selecting Actions  >  Download Agent Script from an Server detail page, then run manually on the target host when required for a given managed resource. Please note the script will be unique per managed resource and should not be saved to run as needed on any arbitrary resources in the future.
+
+When installing on Windows, continue with the steps below to complete manual installation:
+
+- Open powershell as an administrator
+- Run the `unblock-file cmdlet` against the download agent installation script:
+
+  ```
+  ```
+  Unblock-File -Path C:\Users\User01\Documents\Downloads\agentInstall.ps1  
+  Get-ExecutionPolicy  
+  Set-ExecutionPolicy -ExecutionPolicy Unrestricted -Scope CurrentUser
+  ```
+  ```
+- After running the powershell script, ensure the script downloaded the msi and the Agent service started correctly:
+
+  ```
+  ```
+  Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser
+  ```
+  ```
+
+Following setup, verify that the Agent is reporting back to the HPE Morpheus Enterprise appliance.
+
+## Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+### Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+### Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
+
+## Uninstall HPE Morpheus Enterprise Agent
+
+### Linux Agents
+
+You can use the following to uninstall the linux agent (contains commands for both rpm and deb agents)
+
+```
+```
+sudo rm /etc/apt/sources.list.d/morpheus.list \  
+sudo morpheus-node-ctl kill \  
+sudo apt-get -y purge morpheus-node \  
+sudo apt-get -y purge morpheus-vm-node \  
+sudo yum -y remove morpheus-node \  
+sudo yum -y remove morpheus-vm-node \  
+sudo yum clean all \  
+sudo systemctl stop morpheus-node-runsvdir \  
+sudo rm -f /etc/systemd/system/morpheus-node-runsvdir.service \  
+sudo systemctl daemon-reload \  
+sudo rm -rf /var/run/morpheus-node \  
+sudo rm -rf /opt/morpheus-node \  
+sudo rm -rf /etc/morpheus \  
+sudo rm -rf /var/log/morpheus-node \  
+sudo pkill runsv \  
+sudo pkill runsvdir \  
+sudo pkill morphd \  
+sudo usermod -l morpheus-old morpheus-node \
+```
+```
+
+### Windows Agents
+
+```
+```
+$app = Get-WmiObject -Class Win32_Product -Filter "Name = 'Morpheus Windows Agent'"  
+$app.Uninstall()
+```
+```
+
+## CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json b/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
new file mode 100644
index 0000000..a11725b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+  "title": "HPE Morpheus Enterprise Blueprints",
+  "ordinal": 136,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Morpheus Enterprise Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD",
+        "clustering_title": "HPE Morpheus Enterprise Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md b/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
new file mode 100644
index 0000000..41933d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8A5D661E-2FC1-45BC-8D78-3C7D62B139FD.md
@@ -0,0 +1,191 @@
+# HPE Morpheus Enterprise Blueprints
+
+HPE Morpheus Enterprise App Blueprints allow pre-configured full multi-tier application deployments for multiple environments. Blueprints can be provisioned from the Provisioning > Apps section and can be fully configured for one click provisioning. Blueprints can be built within the `Builder` section or by code in the `Raw` section. Blueprints can also be exported as YAML or JSON and created with the HPE Morpheus Enterprise API and CLI.
+
+A unique capability of the YAML/JSON based Morpheus blueprint structure is the ability to have multiple configurations per instance being provisioned within the app blueprint. This can be a scoped configuration that acts as overrides based on selected cloud, group, and/or environment the app is being provisioned in as a target. For example. maybe the “development” environment doesn’t need as many horizontally scaled nodes as the “production” environment. Another great aspect of this configuration markup is a blueprint can be defined as a hybrid cloud blueprint. This makes the app blueprint structure very powerful and in some ways better than alternative infrastructure as code orchestrators. For Example, ARM is locked into Azure, while CloudFormation is locked into AWS. Even Terraform does not allow a tf file to expand its bounds beyond a specific provider type.
+
+## Basic Blueprint Structure
+
+In a Morpheus App Blueprint there are a few structural concepts to be aware of. Firstly there is a concept of a Tier. A Tier is a grouping of instances within an app blueprint. Tiers can be used for a variety of things including sequenced booting of instances or even properly creating endpoint groups and security group contexts in network security tools like Cisco ACI. An example of a Tier structure might be a `Web` tier and a `Database` tier. These tiers can also be marked as connected such that network communication rules can appropriately be defined. A basic 2 Tier blueprint skeleton might look something like this:
+
+```
+```
+name: Tier Example  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers:  
+      - Database  
+    tier:  
+      bootOrder: 1  
+    instances:  
+  Database:  
+    tier:  
+      bootOrder: 0  
+    instances:
+```
+```
+
+This example has defined 2 tiers as yaml properties under the tiers object. They are called Web and Database. A Tier can optionally define its connected tiers which are bi-directional even though only one tier has to define them. This is the linkedTiers array and simply lists the connected tiers by tier name. A Boot Order can also optionally be defined under a nested `{"tier": {"bootOrder": 1}}` object structure.
+
+## Configuration Scopes
+
+Another capability of Morpheus App Blueprint structure is its configuration scoping. This allows properties to be overridden based on the apps target environment or even target group and cloud. For example. Maybe we want to use a larger plan size in production vs. development
+
+An example of that can be done using “environments” overrides.
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              code: container-128  
+         environments:  
+           Production:  
+             groups:  
+               All Clouds Demo:  
+                 clouds:  
+                   AWS Cali:  
+                     plan:  
+                       code: container-256
+```
+```
+
+Note the new environments object. The object graph of the morpheus blueprint structure gets merged and flattened at provision time based on the scope of the configurations provided as well as the users target cloud, group, and environment selection. In the Above example, a selective override was done for the AWS Cali cloud when using a Production Environment and deploying to the group All Clouds Demo. This specific example changes the plan to a larger size. Scoped configurations have various levels of precedence. Cloud is the lowest level of precedence. a cloud configuration in a group is the next level higher and finally an environment configuration in a group in a cloud is the highest level of scoped precedence.
+
+## Getting Started
+
+To get started, it may be best to look at a simple App Blueprint configuration. Docker templates are less complex than virtual machine based templates so lets look at a Blueprint that deploys a single Nginx container to a target cloud:
+
+```
+```
+name: Simple Nginx  
+type: morpheus  
+tiers:  
+  Web:  
+    linkedTiers: []  
+    instances:  
+      - instance:  
+          type: docker  
+          name: Sample Nginx  
+        clouds:  
+          AWS Cali:  
+            instance:  
+              layout:  
+                code: docker-1.7-single  
+                id: 206  
+            volumes:  
+              - rootVolume: true  
+                name: root  
+                size: 1  
+            backup:  
+              createBackup: false  
+            config:  
+              dockerImageVersion: latest  
+              dockerRegistryId: ''  
+              dockerImage: nginx  
+            plan:  
+              id: 68  
+              code: container-128  
+            ports:  
+              - name: HTTP  
+                port: 80  
+                lb: HTTP
+```
+```
+
+Theres some useful things to look at in the above docker example. One is there are different objects based on the different available configuration options for the target provision type. These options are actually data driven and can be extracted from the Inputs api in the morpheus api doc. That is a useful resource to look at while building morpheus blueprints or by using the morpheus-cli which provides prompts for helping build custom morpheus app blueprints.
+
+![../../../_images/templates_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-06C21D16-B31C-492D-9170-EAC44622138F-high.png)
+
+## Creating Morpheus App Blueprints
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Enter a NAME for the Blueprint and select NEXT
+4. Optionally add a Description, Category, and Image for the Blueprint.
+
+### Add Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + to add a Tier
+2. Select or enter a Tier Name.
+3. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+
+### Add Instances to Tiers
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in a Tier to add an Instance
+2. Select an Instance Type
+3. Optionally add a name for the Instance. Instances with blank names will automatically be named based off the App name.
+
+#### Results
+
+TIP
+
+You can use the variable `${app.name}` in your instance naming convention to reference the name of the application you’re deploying.
+
+### Add Configurations to Instances
+
+#### Procedure
+
+1. In the STRUCTURE section, select + in an Instance to add a Configuration
+2. Select at least one option from Group, Cloud or Environment.
+3. Select `ADD CONFIG` to create the configuration
+4. Populate the Configuration 
+
+   - Configurations can be fully partially or populated
+   - Fields can be locked or hidden by selecting the Lock icon next to the Field. Locking prevents the field from being editable when provisioning an App using the Blueprint while hidden fields are not revealed to the user at all
+   - ALLOW EXISTING INSTANCE will allow users to add existing Instances to the App when using the blueprint
+
+### Save
+
+Once all desired Tiers, Instances and Configurations are added, select Save. The Blueprint will be created, can be edited after saving, and will available in the Apps section for provisioning.
+
+NOTE
+
+Blueprints are not provisioned when created. To provision a Blueprint, use Provisioning > Apps.
+
+### RAW
+
+#### About this task
+
+Blueprints can be create, edited or Exported in the RAW section when creating or editing a blueprint.
+
+![../../../_images/templates_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2F7949E9-D5DB-4089-970D-854F88DA140D-high.png)
+
+To Export a Blueprint as JSON or YAML:
+
+#### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Edit an existing App by clicking on the pencil icon
+3. On the Edit Blueprint modal, select the Raw tab
+4. Select YAML or JSON from the dropdown in the top right
+5. Click the Export button
+6. Select the configurations to include in the export by selecting or deselecting configurations as needed. Selected configurations will be highlighted
+7. Click the DOWNLOAD CONFIGURATION button
+8. The Blueprint export file will be downloaded to your computer as `{app_name}-config.json or {app_name}-config.yaml`
+
+## Provisioning
+
+To provision a Blueprint, navigate to Provisioning > Apps and select the Blueprint when creating an App. See the [App section](https://docs.morpheusdata.com/en/latest/provisioning/apps/apps.html) of HPE Morpheus Enterprise docs for more on provisioning Apps.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
new file mode 100644
index 0000000..4428fc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+  "title": "Costing: User Costing",
+  "ordinal": 61,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: User Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8AC08484-473F-41E8-B106-A90BC96B03C4",
+        "clustering_title": "Costing: User Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
new file mode 100644
index 0000000..ecae023
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.md
@@ -0,0 +1,31 @@
+# Costing: User Costing
+
+![../_images/4usercosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-19673F2B-9D42-4067-BC83-078B0046D28B-high.png)
+
+The User Costing dashboard allows administrators to analyze costs for a group of Users that meet specific filters. Once the group is selected, total costs by User for the current month and projected totals are displayed. Administrators can identify their costliest Users and anticipate the total cost by User for budgeting purposes.
+
+## Filters
+
+Filter the Groups pulled into the dashboard by one or more of the following fields:
+
+- User (all matched by search)
+- Group
+- Cloud
+- Period (Current month, last three months, last six months, or last 12 months)
+- Tenant
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Users that meet set filters:
+
+- **USERS:** The total number of Users that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Users meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Users meeting dashboard filters
+
+## User List
+
+Each User that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual User:
+
+- **USERNAME:** The username given to the User in HPE Morpheus Enterprise at the time of creation
+- **MONTH TO DATE:** The current month-to-date spend for the individual User listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual User listed
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json b/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
new file mode 100644
index 0000000..0f0de55
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+  "title": "Docker Registry",
+  "ordinal": 479,
+  "parent_title": "Containers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html",
+  "topic_cluster": {
+    "clustering_title": "Docker Registry",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0",
+        "clustering_title": "Docker Registry"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md b/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
new file mode 100644
index 0000000..6acbe73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.md
@@ -0,0 +1,39 @@
+# Docker Registry
+
+## Overview
+
+Without any additional configuration, HPE Morpheus Enterprise can provision images from Docker’s public hub at <https://hub.docker.com/> using their public API.
+
+However, many organizations maintain private Docker registries for security measures. Additional public and private Docker registries can be added to Morpheus.
+
+## Adding a Docker Registry Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click “New Integration”
+3. Select the Docker Repository Type
+4. Add the following: 
+
+   Name
+   :   Name for the Registry in HPE Morpheus Enterprise
+
+   Repository url
+   :   Docker Registry url or IP address
+
+   Username
+   :   Username if private registry
+
+   Password
+   :   Password if private registry
+5. Save Changes
+
+### Results
+
+NOTE
+
+You must either have signed certificates for your registry or configure your docker host(s) to accept insecure registries
+
+## Provisioning an Instance from Docker Registry
+
+Docker images from the Integrated Registry can be provisioned using the generic Docker Instance Type, or by adding images to Node Types for custom Library Instance Types.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json b/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
new file mode 100644
index 0000000..66d437a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+  "title": "Tenant Users",
+  "ordinal": 278,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8C608C16-055C-4708-BA01-87FACE15EF6D",
+        "clustering_title": "Tenant Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md b/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
new file mode 100644
index 0000000..6a0b90d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.md
@@ -0,0 +1,86 @@
+# Tenant Users
+
+The Tenant View displays a list of users belonging to the Tenant and their Name, Username, Email, and Role.
+
+From this page: Create, Edit, and Delete users within the Tenant.
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Create Tenant User
+
+### About this task
+
+To create a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name on the row of the Tenant where the user will be added.
+4. Click + ADD USER
+5. From the New User wizard, input the fields below: 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email address
+   - Role (to be inherited by the user)
+   - Password
+   - Any default Windows or Linux credentials
+
+### Results
+
+Click SAVE CHANGES
+
+IMPORTANT
+
+In versions 3.1.1 and 2.12.5 and later, a Multi-Tenant User Role must be created prior to adding Subtenant Users or the User will not save. In previous versions a default Multi-Tenant Role was seeded. Due to customer requests, the seeded role was removed and a Multi-Tenant Role must be created by the Master Tenant for Subtenant Users.
+
+## Edit a Tenant User
+
+### About this task
+
+To edit a User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the specific Tenant name from the row of available Tenants.
+4. Click the Edit pencil icon for your selected Tenant.
+5. Edit User information 
+
+   NOTE
+
+   Name, Username, Passwords and e-mail addresses cannot be edited on Users created from Identity Source Integrations.
+
+### Results
+
+Click SAVE CHANGES
+
+## Delete Tenant User
+
+### About this task
+
+To delete a Tenant User:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Click the Tenant Name from the row for the Tenant containing the user.
+4. Click the Delete trashcan icon of the row of the user to delete.
+5. Confirm
+
+## Subtenant User Login
+
+Child Tenant Users can have the same Username as the User on the parent Tenant or any other Tenant. Subtenant Users will now have to login using the subdomain prefix.
+
+IMPORTANT
+
+Subtenant users will no longer be able to login from the main login page without specifying their subdomain.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json b/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
new file mode 100644
index 0000000..1ec8188
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+  "title": "Persona Access",
+  "ordinal": 343,
+  "parent_title": "Personas",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html",
+  "topic_cluster": {
+    "clustering_title": "Persona Access",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF",
+        "clustering_title": "Persona Access"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md b/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
new file mode 100644
index 0000000..972492b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.md
@@ -0,0 +1,30 @@
+# Persona Access
+
+## Configuring Persona Access
+
+### About this task
+
+Access to Personas is controlled by a user’s Role. Additionally, Persona access can be configured on the Tenant Role to set maximum Persona access for any user in the Tenant. By default, new Roles and Roles that existed prior to the creation of Personas will only have access to the Standard Persona. If desired, new Roles can be configured to have access to one or both Personas and existing Roles can be edited in the same way.
+
+TIP
+
+It’s recommended to set access to all Personas to “None” if you intend not to use Personas at all. Under this configuration, HPE Morpheus Enterprise gives access only to the Standard Persona and hides the Persona selection menu from the user. New Roles and Roles that existed prior to creation of the Personas feature are pre-configured in this way.
+
+Edit Persona access on a Role with the following steps:
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Select the desired Role to edit
+3. Go to the Personas tab
+4. Allow access to one or both Personas as needed, changes are saved automatically
+
+### Results
+
+![../_images/1rolePerms2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B7E6E923-4BC1-45EC-8A41-9862C023911F-high.png)
+
+## Accessing Alternate Personas
+
+Switch Personas by clicking on your name in the upper-right corner of the application window. If your Role gives you access to any additional Personas, they will be listed here.
+
+![../_images/2switchPersona2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-79453DE4-A795-4FEB-9670-0F214A7163FF-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json b/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
new file mode 100644
index 0000000..704972d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+  "title": "Troubleshooting",
+  "ordinal": 249,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB",
+        "clustering_title": "Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md b/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
new file mode 100644
index 0000000..dcadadf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8D1B051D-008D-4E15-A7B0-DB38DAAB05FB.md
@@ -0,0 +1,9 @@
+# Troubleshooting
+
+If you do not get the Morpheus boot menu, there are a few things to check:
+
+- First, make sure the filename is correct. It must be `pxelinux.0`
+- Next, check the TFTP server is responding by using a TFTP client to get the `pxelinux.0` file from the HPE Morpheus Enterprise server using the same host name as you have configured in the DHCP server configuration. Do this test on a machine on the same network as the machines you are trying to boot using PXE
+- Leave the port number as 69 (the default) as this will also check the redirect is working
+- If a GET call on the default port does not work, and the client allows (most do) try using port 6969. If this works, then the redirect is wrong
+- If it will not work on either, check you can access the HPE Morpheus Enterprise server from the network you are on and also check there are no firewalls between the test network and the HPE Morpheus Enterprise Server
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json b/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
new file mode 100644
index 0000000..3f0089f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+  "title": "Logs",
+  "ordinal": 256,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.html",
+  "topic_cluster": {
+    "clustering_title": "Logs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB",
+        "clustering_title": "Logs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md b/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
new file mode 100644
index 0000000..108a442
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB.md
@@ -0,0 +1,176 @@
+# Logs
+
+## Overview
+
+The logging architecture backing HPE Morpheus Enterprise uses the latest and greatest technologies and standards to be able to service large amounts of log traffic as well as facilitate easy viewing. Utilizing Opensearch behind the scenes and buffered log transmission protocols HPE Morpheus Enterprise provides a highly efficient and highly scalable solution for capturing log data from anything provisioned via the system. By utilizing common formats (syslog) it is also very easy to forward logs to external third party log services.
+
+### Configuration
+
+Logging configuration can be setup in the Administration > Settings > Logs section. There are useful settings here, including customizing the retainment policy (7 days by default). This could be expanded to years for PCI compliance purposes or other requirements an organization might have.
+
+NOTE
+
+When increasing the retainment policy of the logging system, it may be necessary to scale out the Opensearch cluster. Please refer to the relevant information with regards to scaling Opensearch and advanced installation options for externalizing the Opensearch cluster.
+
+The Log administration section also provides options for setting custom syslog forward rules. These rules are applied on each individual host therefore keeping the HPE Morpheus Enterprise appliance itself out of the data plane. For information on different syslog formatting rules please refer to the [rsyslog](http://www.rsyslog.com/sending-messages-to-a-remote-syslog-server/) documentation.
+
+### Usage
+
+HPE Morpheus Enterprise automatically sets up and configures logging for all of the standard catalog items provisioned through morpheus. This includes both Docker containers as well as virtual machines. Simply view instance-specific logs in instance detail via the “Logs” tab.
+
+There are several filtering capabilities built into the logging UI with more being added continually. Easily toggle log level filters from the dropdown or change the date range filter using the handy date filter component. A chart is also displayed above logs representing the log counts by level over the selected time range (default last 24 hours). A handy pattern search is also available with some rather capable features based on Lucene search syntax.
+
+TIP
+
+It may be useful to review the [Lucene search query syntax](https://lucene.apache.org/core/2_9_4/queryparsersyntax.html) for powerful use cases.
+
+There are several other places logs can be viewed. Not only can they be viewed across an application in app detail but also across all instances in the account. The main level `Logs` section provides an ability to query all logs produced by the system. It is also possible to view host-specific logs on a docker host by viewing the host detail page via `Infrastructure`.
+
+NOTE
+
+New features are on the roadmap for the main logs section including saved searches, and handy charting dashboards for garnering insights out of log data.
+
+## Exporting Logs
+
+### Log Settings
+
+There are three main log areas in HPE Morpheus Enterprise
+
+- Agent Logs
+- HPE Morpheus Enterprise Server Logs
+- Activity / Audit Logs
+
+## Agent Logs
+
+When Instances are deployed through HPE Morpheus Enterprise, the installed Agent captures application logs and sends them back to the HPE Morpheus Enterprise server.
+
+In most cases, the built-in HPE Morpheus Enterprise logging features are sufficient for tracking and reviewing Agent logs. However, if needed, HPE Morpheus Enterprise supports integration with advanced logging systems. See the [log integration section](https://docs.morpheusdata.com/en/latest/logs/logging.html#integrations) above for more information.
+
+## HPE Morpheus Enterprise Server Logs
+
+### About this task
+
+The main HPE Morpheus Enterprise application log is in `/var/log/morpheus/morpheus-ui` and the latest log file is named current. This log is archived every 24hrs. There are a number of other log files for the individual infrastructure components as well.
+
+If you wish to export these to an external syslog platform, do the following:
+
+### Procedure
+
+1. Once you have configured your syslog destination (edit rsyslog.conf), create a morpheus-syslog.conf file in the `/etc/rsyslog.d` directory and add the following entries 
+
+   ```
+   ```
+   module(load="imfile" PollingInterval="10")  
+   input(type="imfile" File="/var/log/morpheus/morpheus-ui/current" Tag="morpheus-ui" ReadMode="2" Severity="info" StateFile="morpheus-ui")  
+   input(type="imfile" File="/var/log/morpheus/check-server/current" Tag="check-server" ReadMode="2" Severity="info" StateFile="check-server")  
+   input(type="imfile" File="/var/log/morpheus/guacd/current" Tag="guacd" ReadMode="2" Severity="info" StateFile="guacd")  
+   input(type="imfile" File="/var/log/morpheus/opensearch/current" Tag="opensearch" ReadMode="2" Severity="info" StateFile="opensearch")  
+   input(type="imfile" File="/var/log/morpheus/mysql/current" Tag="mysql" ReadMode="2" Severity="info" StateFile="mysql")  
+   input(type="imfile" File="/var/log/morpheus/nginx/current" Tag="nginx" ReadMode="2" Severity="info" StateFile="nginx")  
+   input(type="imfile" File="/var/log/morpheus/rabbitmq/current" Tag="rabbitmq" ReadMode="2" Severity="info" StateFile="rabbitmq")
+   ```
+   ```
+2. Restart rsyslog
+
+### Results
+
+The log files will now be forwarded to the destination you have defined.
+
+This configuration is valid for an ‘all-in-one’ HPE Morpheus Enterprise server. If the infrastructure components are running on separate servers /clusters, you will need to create the relevant redirects for the logs on those boxes.
+
+## Activity Log
+
+### About this task
+
+The final log type that may require export is the HPE Morpheus Enterprise Activity log. This tracks system changes made by users, for example create and delete instances etc.
+
+### Procedure
+
+1. To set up CEF/SIEM auditing export, you should edit the following file: `logback.xml` located at `/opt/morpheus/conf/logback.xml`.
+2. Add the below appender above or below the other appenders in the logback.xml configuration file: 
+
+   ```
+   ```
+     <appender name="AUDIT" class="ch.qos.logback.core.rolling.RollingFileAppender">  
+         <file>/var/log/morpheus/morpheus-ui/audit.log</file>  
+         <rollingPolicy class="ch.qos.logback.core.rolling.SizeAndTimeBasedRollingPolicy">  
+             <fileNamePattern>audit.%d{yyyy-MM-dd}.%i.log</fileNamePattern>  
+               <maxFileSize>50MB</maxFileSize>  
+               <maxHistory>30</maxHistory>  
+         </rollingPolicy>  
+         <encoder>  
+             <pattern>[%d] [%thread] %-5level %logger{15} - %maskedMsg %n</pattern>  
+         </encoder>  
+     </appender>  
+   .. note:: ``maxFileSize`` and ``maxHistory`` values can be updated as needed.
+   ```
+   ```
+3. Add the below logger above or below the other loggers in the logback.xml configuration file (make sure it is below, not above, the appender from the previous step or an error will occur): 
+
+   ```
+   ```
+   <logger name="com.morpheus.AuditLogService" level="INFO" additivity="false">  
+       <appender-ref ref="AUDIT" />  
+   </logger>
+   ```
+   ```
+4. Once you have done this, you need to restart the HPE Morpheus Enterprise Application server: 
+
+   ```
+   ```
+   morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   NOTE
+
+   Please be aware this will stop the web interface for HPE Morpheus Enterprise.
+5. Once the service has stopped enter the following at the shell prompt to restart (if the service does not stop, replace stop with graceful-kill and retry) 
+
+   ```
+   ```
+   morpheus-ctl start morpheus-ui
+   ```
+   ```
+6. To know when the UI is up and running you can run the following command 
+
+   ```
+   ```
+   morpheus-ctl tail morpheus-ui
+   ```
+   ```
+
+   Once you see the ASCI art show up you will be able to log back into the User Interface. A new audit file will have been created called audit.log and will found in the default HPE Morpheus Enterprise log path which is `/var/log/morpheus/morpheus-ui/`
+
+### Results
+
+This is only an example and other configurations are possible, such as creating an appender definition for your SIEM audit database product.
+
+## morpheus-ssl nginx logs
+
+NOTE
+
+Morpheus does not put a logrotate in for Morpheus-ssl access logs
+
+svlogd will only rotate the current file, nginx is setup to write the access logs to separate files and not stdout.
+
+Implementation of a log rotate is left up to up to end users for files outside of the services. This is done in case end users have a log management solution.
+
+Below is what a suggested configuration looks like for the file `/etc/logrotate.d/morpheus-nginx`:
+
+```
+```
+/var/log/morpheus/nginx/morpheus*access.log {  
+        daily  
+        rotate 14  
+        compress  
+        delaycompress  
+        missingok  
+        notifempty  
+        create 644 morpheus-app morpheus-app  
+        postrotate  
+                [ ! -f /var/run/morpheus/nginx/nginx.pid ] || kill -USR1 `cat /var/run/morpheus/nginx/nginx.pid`  
+        endscript  
+}
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json b/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
new file mode 100644
index 0000000..137a345
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+  "title": "Getting started with Morpheus and AWS",
+  "ordinal": 361,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with Morpheus and AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821",
+        "clustering_title": "Getting started with Morpheus and AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md b/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
new file mode 100644
index 0000000..874af94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.md
@@ -0,0 +1,212 @@
+# Getting started with Morpheus and AWS
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of Morpheus with AWS. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get Morpheus installed and are ready to move forward from that point. There is a lot more to see and do in Morpheus that is beyond the scope of this guide. For more, consult the complete Morpheus documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, Morpheus needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in [Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63B50C5A-C3AD-4543-8A89-58110DDD5064.html#GUID-FD8026F1-B4DB-4778-9588-728A05838892). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, Morpheus will automatically set up a lab license on installation. A lab license is a time-unlimited license for Morpheus that limits you to 25 managed and discovered workloads. If you have a timed trial or a paid license, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in Morpheus define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on Morpheus groups is available in the [Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html#GUID-E0307462-456B-4D4E-82E3-0BD04A42F824) section. A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling Morpheus through Morpheus API or Morpheus CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![../../_images/1groupConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in Morpheus consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with AWS.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of Morpheus but soon we will see our integrated AWS cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “AMAZON” and click the “NEXT” button.
+
+On the “CONFIGURE” tab, give your cloud a “NAME”. Select your Amazon region and enter your credentials in the “ACCESS KEY” and “SECRET KEY” fields. We can also set a number of advanced options here that may be relevant to your AWS use case.
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, Morpheus will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first AWS cloud, we can stop for a moment to review what Morpheus gives us from the cloud detail page. We can see that Morpheus gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our AWS cloud configured, Morpheus will automatically sync in available resource pools and data stores.
+
+Resource pools, once Morpheus has had time to ingest them, will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in Amazon. For example, we can restrict access to a specific resource pool within Morpheus completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within Morpheus.
+
+![../../_images/1resourcePools.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5EDE80B8-04C2-42AD-95C9-11EA1E8E8331-high.png)
+
+Often our clients will want to make specific blocks of resources available to certain groups. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![../../_images/2editResourceGroups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3D217ABE-3194-420B-A2D6-DD5262F136EC-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into Morpheus. Depending on the number of clouds Morpheus has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![../../_images/1networksSection.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html) section of Morpheus Docs.
+
+![../../_images/2addIPAM.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a Morpheus-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, Morpheus will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, Morpheus will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![../../_images/3addIPPool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within the AWS cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your AWS cloud)  >  NETWORKS tab. Just as with resource pools, we have the ability to make certain networks inactive in Morpheus, or scope them to be usable only for certain groups or tenants.
+
+![../../_images/1cloudNetwork.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1A883CF2-9673-460A-B1AC-A1CB858CD226-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, Morpheus comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with the images included in Morpheus by default but have guides in Morpheus Docs for [Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html#GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798) which are consumable in Morpheus.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our AWS cloud.
+
+Navigate to |ProIns|. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![../../_images/1createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the AWS cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, Morpheus will only show plans at or above these limits. User-defined plans can also be created in |AdmPla|.
+- **VOLUMES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+- **SECURITY GROUPS**
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click NEXT.
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of Morpheus docs.
+
+Review the settings for your first instance and click COMPLETE.
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends selections made when provisioning the instance. For more detailed information on the status of various provisioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, Morpheus allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click +ADD.
+
+![../../_images/1addNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: Amazon
+- **AMI IMAGE**: Morpheus Redis 3.0 on Ubuntu 14.04.3 v2
+
+![../../_images/2nodeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B58E92CB-BAAC-4B7B-A743-4E04B13DC487-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![../../_images/3addInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![../../_images/4instanceTypeSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![../../_images/5openInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: Amazon
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to |ProIns| and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+As before when we manually provisioned an instance, Morpheus will now begin to spin up the new VM. Once the privisioning process has completed, open the instance detail page in Morpheus and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+## Automation and Configuration Management
+
+Morpheus automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the Morpheus Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in [Automation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6779EFD7-BD52-4678-AC19-30AE09F26217.html). Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![../../_images/1newIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+ NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![../../_images/2configureIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to |LibAut|, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![../../_images/3taskConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to |ProIns| and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![../../_images/4executeTask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in |LibAut| we will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![../../_images/5newWorkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to |ProIns| and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![../../_images/6automationInProvisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see Morpheus executing the tasks that were contained in our workflow.
+
+This is just one example of using Morpheus to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-89FD5558-DFD3-459B-A56D-BD998574F805.html) guide in Morpheus docs.
+
+## Conclusion
+
+At this point you should be up and running in Morpheus, ready to consume AWS. This guide only scratches the surface, there is a lot more to see and do in Morpheus. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json b/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
new file mode 100644
index 0000000..fe81d71
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+  "title": "Morpheus DB Migration",
+  "ordinal": 26,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus DB Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576",
+        "clustering_title": "Morpheus DB Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md b/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
new file mode 100644
index 0000000..2d8f77c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.md
@@ -0,0 +1,80 @@
+# Morpheus DB Migration
+
+If your new installation is part of a migration or you need to move the data from your original Morpheus database, this is easily accomplished by using a stateful dump.
+
+To begin this, stop the Morpheus UI on your original Morpheus server:
+
+```
+```
+[root@app-server-old ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Once this is done you can safely export. To access the MySQL shell we will need the password for the Morpheus DB user. We can find this in the morpheus-secrets file:
+
+```
+```
+[root@app-server-old ~] cat /etc/morpheus/morpheus-secrets.json | grep morpheus_password  
+"morpheus_password": "451e122cr5d122asw3de5e1b", <---------------this one  
+"morpheus_password": "9b5vdj4de5awf87d",
+```
+```
+
+Take note of the first `morpheus_password` as it will be used to invoke a dump. Morpheus provides embedded binaries for this task. Invoke it via the embedded path and specify the host. In this example we are using the morpheus database on the MySQL listening on localhost. Enter the password copied from the previous step when prompted:
+
+```
+```
+[root@app-server-old ~] /opt/morpheus/embedded/mysql/bin/mysqldump -u morpheus -h 127.0.0.1 morpheus -p > /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+This file needs to be pushed to the new Morpheus Installation’s backend. Depending on the GRANTS in the new MySQL backend, this will likely require moving this file to one of the new Morpheus frontend servers.
+
+Once the file is in place it can be imported into the backend. Begin by ensuring the Morpheus UI service is stopped on all of the application servers:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl stop morpheus-ui
+```
+```
+
+Then you can import the MySQL dump into the target database using the embedded MySQL binaries, specifying the database host, and entering the password for the morpheus user when prompted:
+
+```
+```
+[root@app-server-new ~] /opt/morpheus/embedded/mysql/bin/mysql -u morpheus -h 127.0.0.1 morpheus -p < /tmp/morpheus_backup.sql  
+Enter password:
+```
+```
+
+The data from the old appliance is now replicated on the new appliance. Simply start the UI to complete the process:
+
+```
+```
+[root@app-server-new ~] morpheus-ctl start morpheus-ui
+```
+```
+
+With the migration complete, you will also need to update the stored password for the appliance backup job as the destination appliance will have a different dynamically-generated MySQL password. We can update that password value by altering the backup directly in the HPE Morpheus Enterprise database.
+
+```
+```
+select * from backup where `name` ='Morpheus Appliance';  
+UPDATE `morpheus`.`backup` SET `ssh_host` = '127.0.0.1', `target_password` = 'its-a-secret' WHERE `id` = '1';
+```
+```
+
+IMPORTANT
+
+After the migration it is important to reset the unique ID of the Morpheus Appliance. This will ensure your new installation will communicate correctly with the Morpheus Hub.
+
+The final step is to generate a new unique ID for the Morpheus Appliance. Firstly run the following SQL command on the database for the new installation:
+
+```
+```
+UPDATE appliance_instance SET hub_unique_id = NULL;
+```
+```
+
+Secondly, re-apply your Morpheus license key within the Morpheus UI via the “Upgrade A License” action within Administration -> Settings -> License
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json b/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
new file mode 100644
index 0000000..9e594f0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+  "title": "Adding an NFS Datastore",
+  "ordinal": 191,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html",
+  "topic_cluster": {
+    "clustering_title": "Adding an NFS Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3",
+        "clustering_title": "Adding an NFS Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md b/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
new file mode 100644
index 0000000..360c33b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.md
@@ -0,0 +1,13 @@
+# Adding an NFS Datastore
+
+Existing NFS shares can be used with HPE Morpheus Enterprise HVM clusters for virtual machine storage. These are added and viewed from the Storage tab of the HVM cluster detail page and, once added and active, become selectable as targets for virtual machine storage.
+
+NOTE
+
+Ensure NFS is properly configured to allow all of the HVM hosts to access the shared directory, including permissions to read and write. For backup purposes, it’s also helpful to give HPE Morpheus Enterprise access to NFS.
+
+Start by navigating to the Storage tab of the HVM cluster detail page. Make sure the Data Stores subtab is also selected. Here you will see a list of existing datastores with some additional information, such as type, capacity, and status. Click ADD. Enter the NAME for the datastore in HPE Morpheus Enterprise and select the TYPE as NFS Pool. Note that the datastore name cannot be changed once it has been created. This will update the available fields to include the additional fields needed to integrate the NFS server. Enter the SOURCE HOST which is the hostname or the IP address of the NFS server. Finally, enter the SOURCE DIRECTORY which is the directory path of the NFS share. Click SAVE.
+
+Once the modal is saved, it will take a few minutes to initialize the new datastore and show a successful online status in HPE Morpheus Enterprise. Once this initialization process is completed, the datastore can now be used as VM storage for cluster.
+
+![../../_images/addNfsDatastore.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-90F23A24-CA56-4100-94CD-13EA1247EBD5-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json b/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
new file mode 100644
index 0000000..10f1b75
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+  "title": "Post-Provisioning",
+  "ordinal": 418,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.html",
+  "topic_cluster": {
+    "clustering_title": "Post-Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9",
+        "clustering_title": "Post-Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md b/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
new file mode 100644
index 0000000..ab6eba5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-910B7DB4-B418-4281-B5FC-3A6C0FC02CD9.md
@@ -0,0 +1,20 @@
+# Post-Provisioning
+
+After provisioning the instance:
+
+- The new instance appears under Provisioning > Instances.
+
+    
+  ![Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EB7CC689-A95F-43C0-8F65-D43E35C97D7B-high.png)
+- To monitor provisioning progress, select the instance from the list.   
+  ![Summary](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AA864681-E71F-4DAA-BC8C-9594A4F366CC-high.png)
+
+  Once provisioning completes successfully, review the tabs as required.
+- To access the instance console, click the Console tab
+- After successful provisioning, verify that the instance and its corresponding bare metal host are listed in:
+  - Under Provisioning > Instances.  
+    ![Provisioning Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-49E0E201-4ED4-41C1-A8F4-D31630076D56-high.png)
+  - Under Infrastructure > Bare Metal.   
+    ![Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1647C09E-6E21-4A92-A088-1AC8E3A64B52-high.png)
+  - Go to the Instances page to view the instance Status, Health, CPU, Memory, and Storage details.   
+    ![Details](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-55629E53-1010-42C1-BE7F-DCF13B743BBE-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json b/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
new file mode 100644
index 0000000..3bec5e2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+  "title": "Base Cluster Details",
+  "ordinal": 178,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9132296F-B580-4107-8041-9E30C7EC4291.html",
+  "topic_cluster": {
+    "clustering_title": "Base Cluster Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9132296F-B580-4107-8041-9E30C7EC4291",
+        "clustering_title": "Base Cluster Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md b/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
new file mode 100644
index 0000000..75fc431
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9132296F-B580-4107-8041-9E30C7EC4291.md
@@ -0,0 +1,8 @@
+# Base Cluster Details
+
+An HVM cluster using the hyperconverged infrastructure (HCI) Layout consists of at least three hosts. Physical hosts are recommended to experience full performance of the HVM cluster solution. In smaller environments, it is possible to create an HVM cluster with three nested virtual machines, a single physical host (non-HCI only), or a single nested virtual machine (non-HCI only) though performance may be reduced. With just one host it won’t be possible to migrate workloads between hosts or take advantage of automatic failover. Currently, a host must be a pre-existing Ubuntu 22.04 box with environment and host system requirements contained in this section. HPE Morpheus Enterprise handles cluster configuration by providing the IP address(es) for your host(s) and a few other details. Details on adding the cluster to HPE Morpheus Enterprise are contained in the next section.
+
+**Subtopics**  
+
+- **[Hardware Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-29D63377-0FE6-40DD-BCCF-1A5319D2D9C2.html)**
+- **[Example Cluster Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5CBD20D3-D323-4F6E-A543-E19708439C5D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json b/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
new file mode 100644
index 0000000..58d661b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+  "title": "Usage",
+  "ordinal": 76,
+  "parent_title": "Costing",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.html",
+  "topic_cluster": {
+    "clustering_title": "Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA",
+        "clustering_title": "Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md b/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
new file mode 100644
index 0000000..a78c920
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-91F88F3F-E69B-482A-9E00-689DEBF31FAA.md
@@ -0,0 +1,35 @@
+# Usage
+
+The Operations  >  Costing  >  Usage section shows billing information for Instances and hosts that have pricing configured on their Service Plan.
+
+IMPORTANT
+
+Pricing must be enabled in Administration > Settings > Provisioning and Service Plans configured with price sets in Administration > Plans & Pricing for pricing to show in the Usage section.
+
+## View Usage
+
+All Instances, discovered resources, virtual images, snapshots are listed by default, with the most recent usage information showing first. When additional details are available, usage records will display a small arrow on the left side of the row. Click this arrow to expand the details for that usage record. Details can include more granular cost breakdowns, such as specific CPU, memory, and/or storage costs for containers (Instances).
+
+Usage records can be filtered by Cloud, type and date:
+
+Cloud
+:   Default view is for all Clouds. Select a Cloud to show Instance, host and other usage for only one Cloud.
+
+Date
+:   Default view shows most current Usage. Select the Date filter to scope to a different date range.
+
+Type
+:   All usage record types are shown by default, select a specific type to filter the list to just one
+
+Example:
+:   Below is an example of a discovered instance from AWS, which shows different usage periods and the pricing that would be related. In this case, the compute and storage are used to calculate the Usage Price when the instance is **Running** but only the storage when the instance is **Stopped**:
+
+    ![../_images/usage_example.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E455650E-5DD7-40E6-BF40-5449281F27C2-high.png)
+
+## API & CLI
+
+Usage information can also be extracted via the HPE Morpheus Enterprise API and CLI, including the ability to extract usage per Tenant.
+
+NOTE
+
+Appropriate Role permissions for Operations: Usage are required to view the Usage section.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json b/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
new file mode 100644
index 0000000..e685b60
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+  "title": "Morpheus Agent",
+  "ordinal": 42,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209",
+        "clustering_title": "Morpheus Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md b/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
new file mode 100644
index 0000000..de8fc5e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.md
@@ -0,0 +1,17 @@
+# Morpheus Agent
+
+- [Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)
+- [Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)
+- [Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)
+- [CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-607895C8-5308-4A68-9219-1EA342DB9C6C.html)**
+- **[HPE Morpheus Enterprise Agent Key Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7499B18D-B7D9-4E75-A4C3-75C1EB409A38.html)**
+- **[Morpheus Agent OS Support](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-65F84F63-FB7B-42D2-B76A-AF457B2E4184.html)**
+- **[Agent Installation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html)**
+- **[Agent Install Methods](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7A5C2EEE-C74B-4D98-A2C4-F8E4BA0D1FCE.html)**
+- **[Restarting the HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9B75C475-9243-4444-BF22-C43480298274.html)**
+- **[Uninstall HPE Morpheus Enterprise Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6419DED6-4E66-4440-8EBC-CE8E762FF98D.html)**
+- **[CentOS/RHEL 7 Images](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json b/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
new file mode 100644
index 0000000..539ef0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+  "title": "Personas",
+  "ordinal": 340,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9372294C-3A13-490D-BF63-BA01AB008C43.html",
+  "topic_cluster": {
+    "clustering_title": "Personas",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9372294C-3A13-490D-BF63-BA01AB008C43",
+        "clustering_title": "Personas"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md b/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
new file mode 100644
index 0000000..e33f531
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9372294C-3A13-490D-BF63-BA01AB008C43.md
@@ -0,0 +1,11 @@
+# Personas
+
+Personas are alternate views in HPE Morpheus Enterprise UI. A user’s access to the various Personas is controlled by Role permissions. At present, there are four Persona types: Standard, API, Service Catalog, and Virtual Desktop. The Standard Persona is the typical full HPE Morpheus Enterprise UI experience. The Service Catalog Persona is a simplified view where users are presented with pre-configured Instance types, Blueprints, and Workflows to choose from based on their Role. The Virtual Desktop Persona allows administrators to grant user access to remote workstations and applications. The API persona allows almost no access to HPE Morpheus Enterprise UI, it offers API access only for service accounts.
+
+The rest of this section goes through the use of the Service Catalog Persona and Virtual Desktop Persona in greater detail, including how administrators can curate catalog item and virtual desktop selections for their users.
+
+**Subtopics**  
+
+- **[Service Catalog Persona](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html)**
+- **[Virtual Desktop Persona](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html)**
+- **[Persona Access](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8CC5D3BF-C295-4ED7-B0E3-8E9833A225EF.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json b/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
new file mode 100644
index 0000000..c6e7668
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+  "title": "Domains",
+  "ordinal": 222,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-94133965-3802-4768-A71D-2AD5F8402BD9.html",
+  "topic_cluster": {
+    "clustering_title": "Domains",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-94133965-3802-4768-A71D-2AD5F8402BD9",
+        "clustering_title": "Domains"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md b/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
new file mode 100644
index 0000000..dfd4c5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-94133965-3802-4768-A71D-2AD5F8402BD9.md
@@ -0,0 +1,116 @@
+# Domains
+
+Infrastructure  >  Network  >  Domains
+
+## Overview
+
+The Domains section is for creating and managing domains for use in HPE Morpheus Enterprise. Domains are used for setting FQDNs, joining Domains, and creating DNS records. The Domains section is also a multi-tenant endpoint for managing domain settings across multiple tenants.
+
+- Domains are synced in from Cloud, DNS and Network Integrations. Domains can also be user created.
+- Active Domains are available for selection in the Domain dropdown when provisioning an Instance
+- Default Domains can be set for Clouds and Networks in their Advanced Options sections.
+- Images can be flagged to Auto-Join Domains in the Infrastructure  >  Network  >  Domains section
+
+IMPORTANT
+
+For an Instance to auto-join a Domain, a Domain must set in the Advanced Options section of the Cloud or Network used when provisioning
+
+## Adding Domains
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Domains
+2. Select + ADD
+3. Enter the following: 
+
+   Domain Name
+   :   Ex. demo.example.com
+
+   Description
+   :   Descriptive metadata for use in HPE Morpheus Enterprise
+
+   Display Name
+   :   Overrides the displayed name in domain selection components, which is useful when using many OU paths
+
+   Public Zone
+   :   Check for Public Zones, leave uncheck for Private Zones
+
+   Workflow
+   :   Select an existing Workflow which will be applied to Instances at provision time when they are associated with the domain. This is useful for any domain-related scripting you may currently use. For example, you may want to ensure a machine is removed from the domain when it’s torn down which could be accomplished by creating a Provisioning Workflow (with teardown phase Tasks) and associating the Workflow with the domain
+
+   Active
+   :   Active Domains are available for selection in Domain selection fields across HPE Morpheus Enterprise. Inactive Domains are removed from Domain selection fields.
+
+   Join Domain Controller
+   :   Enable to have Windows instances join a Domain
+
+   Username
+   :   Admin user for Domain. `domain\username` format required when specifying OU Path
+
+   Password
+   :   Password for DC user account
+
+   DC Server
+   :   (optional) Specify the URL or Path of the DC Server
+
+   OU Path
+   :   (optional) Enter the OU Path for the connection string.
+
+   Guest Username
+   :   (optional) If set, this will change the provisioned hosts RPC Service User after domain join. Useful when a domain policy disables the Administrator account that typically would be set as the RPC user on a host record. HPE Morpheus Enterprise will update the RPC username and password on the host(s) record after domain join with the specified Guest Username and Guest Password. The RPC username and password are used for auth during Remote Procedure Call (RPC) executions over winrm, ssh and guest tools.
+
+   Guest Password
+   :   (optional) The password for the Guest User account indicated in the prior field
+4. Click Save Changes
+
+### Results
+
+The Domain has been added and will be selectable in the Domain dropdown during provisioning, and in Cloud and Network settings.
+
+## Editing Domain Permissions
+
+To edit visibility permissions for a domain, navigate to Infrastructure  >  Network  >  Domains. In the row for the selected domain, click MORE > Permissions. Within the Permissions modal, set Group and Tenant access permissions.
+
+NOTE
+
+Only resources assigned to the Master Tenant can be set as Publicly visible. If the Tenant assigned is not the Master Tenant, visibility will automatically change to private. Additionally, only Master Tenant users can set visibility for domains. Domains originating in a subtenant will always be private to that subtenant.
+
+### Group Access
+
+The Group Access control affects which Groups have access to the domain at provision time. Select “all” to allow workloads provisioned to any Group access to the domain. If specific Groups are selected, only workloads provisioned to those Groups will have visibility of the domain during provisioning.
+
+### Tenant Permissions
+
+When set to public, all Tenants will have visibility into the domain and can join their Instances to the domain. When set to private, users can select specific Tenants which should have access to the domain.
+
+## Editing and Removing Domains
+
+- Domains can be edited by selecting the Actions dropdown for the Domain and selecting Edit, or by selecting the ✎ icon in list views.
+- Added Domains can be removed from HPE Morpheus Enterprise by selecting the Actions dropdown for the Domain and selecting Remove, or the 🗑 icon in list views.
+
+## Setting the default domain on a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds.
+2. Edit the target Cloud.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Setting the default domain on a Network
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network.
+2. Edit the target Network.
+3. Expand Advanced Options section.
+4. In the Domain dropdown, select the Domain.
+5. Save Changes
+
+## Selecting a Domain while provisioning an instance
+
+### Procedure
+
+1. While creating an instance, in the Configure section, expand the DNS Options.
+2. Select Domain from the Domain dropdown.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json b/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
new file mode 100644
index 0000000..808b5de
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+  "title": "Hardware Passthrough",
+  "ordinal": 193,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-949DC89F-26C2-4028-9A1F-2616FB466736.html",
+  "topic_cluster": {
+    "clustering_title": "Hardware Passthrough",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-949DC89F-26C2-4028-9A1F-2616FB466736",
+        "clustering_title": "Hardware Passthrough"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md b/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
new file mode 100644
index 0000000..1998092
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-949DC89F-26C2-4028-9A1F-2616FB466736.md
@@ -0,0 +1,13 @@
+# Hardware Passthrough
+
+HPE Morpheus VM Essentials includes hardware passthrough and pooling support for VMs provisioned to HVM Clusters. This support extends to GPU, USB, NVME, and any other PCIe device types. In order to be usable, such devices must be attached to a HVM Host or to multiple HVM Hosts. HPE Morpheus VM Essentials includes controls to detach hardware devices from the underlying OS on the hypervisor host and add them to a pool where they are available for consumption by VMs. GPU hardware can be attached to VMs at provision time through custom Service Plans or on an ad-hoc basis by manually attaching hardware to existing VMs. Other supported hardware types must be passed through to the VM after provisioning.
+
+NOTE
+
+HVM Clusters sync certain data every few minutes (short sync) and other data once nightly (daily sync). New hardware attached to hosts is synced into HPE Morpheus VM Essentials during the nightly sync. To consume newly attached hardware immediately, you can force an additional daily sync at any time from the cluster detail page. Just expand the ACTIONS menu and click "Refresh Daily." Within a short time the additional daily sync will complete and newly attached hardware should be consumable from the UI.
+
+**Subtopics**  
+
+- **[Viewing and Assigning Hardware Devices](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html)**
+- **[Creating Service Plans for GPU Hardware Passthrough](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-10D04894-711A-400A-98A7-A3DECE437CDA.html)**
+- **[GPU Passthrough Example](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-580E4107-827A-43F6-888D-5CDD41EB42E0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json b/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
new file mode 100644
index 0000000..7667404
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+  "title": "Compute",
+  "ordinal": 450,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md b/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
new file mode 100644
index 0000000..2bb7baf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.md
@@ -0,0 +1,8 @@
+# Compute
+
+The topic describes troubleshooting procedures for compute.
+
+**Subtopics**  
+
+- **[OS Imaging](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html)**
+- **[Firmware and Driver Lifecycle Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-89F63373-6CC7-4498-9A70-75BB1FD6D779.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json b/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
new file mode 100644
index 0000000..41e090e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+  "title": "Add HaProxy container load balancer",
+  "ordinal": 501,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.html",
+  "topic_cluster": {
+    "clustering_title": "Add HaProxy container load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362",
+        "clustering_title": "Add HaProxy container load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md b/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
new file mode 100644
index 0000000..de63c51
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96732ACE-6F43-453A-8F9B-FD0F1C717362.md
@@ -0,0 +1,33 @@
+# Add HaProxy container load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **HaProxy Container**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Container LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-56213FAB-222F-45BB-A5DD-748546C526A1-high.png)
+4. Configure the following parameters: 
+
+   GROUP
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   RESOURCE POOL
+   :   From the drop-down list, select the resource pool.
+
+   HOST
+   :   From the drop-down list, select the host.
+
+   PLAN
+   :   From the drop-down list, select the plan (size of HaProxy container to be provisioned).
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json b/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
new file mode 100644
index 0000000..3da2da3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+  "title": "Tenancy",
+  "ordinal": 373,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html",
+  "topic_cluster": {
+    "clustering_title": "Tenancy",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4",
+        "clustering_title": "Tenancy"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md b/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
new file mode 100644
index 0000000..4adf364
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.md
@@ -0,0 +1,268 @@
+# Tenancy
+
+HPE Morpheus Enterprise appliances may be multi-tenanted, that is, they may contain multiple isolated environments known as Tenants. Successfully building a multi-Tenanted HPE Morpheus Enterprise environment requires creating and pulling together multiple constructs. This guide aims to describe the pieces needed to create functioning Tenants with Users, identity integrations, Roles, Groups, and whitelabeling. We will also share a Cloud and Library item from the Master Tenant which is provisionable from the new Subtenant.
+
+On installation, a single Tenant is created. This Tenant is often referred to as the Master Tenant and has some special properties that additional created Tenants (known as Subtenants) do not have. Tenants manage their own workloads, may have their own custom whitelabeling, and also have their own users and integrations. The Master Tenant may (or may not) share down integrations, Library items, Roles, and more but Subtenants are fully isolated from each other.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The Master Tenant creates and controls all Subtenants.
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants
+- Subtenants cannot share their resources with other Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant
+
+## Tenant Roles
+
+### About this task
+
+Before even creating the Tenant, we need to understand what a Tenant Role is and ensure that a Tenant Role with correct rights permissions exists. Tenant Roles set the maximum feature permissions levels for any User in the Subtenant and also give (or revoke) access to Clouds, Library items, Tasks, Workflows, and other things integrated or created in and shared from the Master Tenant. Only Master Tenant administrators have the ability to create Tenant Roles.
+
+NOTE
+
+User Roles within the Tenant may be created with lesser permissions than the Tenant Role allows but we will discuss User Roles further in a later section.
+
+In a new environment, the only Tenant Role will be the included “Tenant Admin” Role but this Role is not editable. It’s advisable to create your own Tenant Roles so they may be edited as needed. To get started, we can create a new Tenant Role and copy from the pre-existing “Tenant Admin” Role.
+
+### Procedure
+
+1. Navigate to Administration > Roles
+2. Click + CREATE ROLE
+3. Set a NAME, TYPE (Tenant Role), and COPY FROM ROLE (Tenant Admin)
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/addTenantRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9D86F36B-590B-424C-A1E6-13B6779D961F-high.png)
+
+Once created, click into the new Role and edit feature permissions if you wish. Remember the Tenant Role is setting the maximum available Role permissions for each feature that Users within the Tenant can have. We’ll worry about scoping resources to the Subtenant (such as Clouds) in a later section.
+
+With a Tenant Role created, we can move on to creating the Tenant itself.
+
+## Create a Tenant
+
+### About this task
+
+We’ll now create a Tenant and apply the Tenant Role we’ve just created.
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Click CREATE TENANT
+3. Name your Tenant and set the Tenant Role in the BASE ROLE field
+4. Click SAVE CHANGES
+
+### Results
+
+The NAME and BASE ROLE are the most important settings and the only two required. See the Tenants section of HPE Morpheus Enterprise documentation to learn more about other settings which may be applied when adding or editing Tenants.
+
+![../../_images/addTenant.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-702D1FEA-8C54-4BBA-AEC7-7C1575EC9D28-high.png)
+
+With the Tenant created, the rest of the guide will pertain to configuring the new Tenant and demonstrating how to provision new workloads using resources shared down from the Master Tenant.
+
+## Users and User Roles
+
+### About this task
+
+In the prior steps we’ve created a new Tenant and associated our created Tenant Role with it. If you click into the new Tenant you’ll notice that there are currently no users so the new Tenant is still unusable. We could go ahead and create a new User but if this is a new HPE Morpheus Enterprise environment, the new Tenant will not have any User Roles to apply to the new User we wish to create.
+
+To remedy this problem, we can add a “Multi-Tenant User Role” from the Master Tenant. This is essentially a Role Template from which a Role is created and seeded down to each Tenant. Only Master Tenant administrators can create Multi-Tenant User Roles. After creation, edits can be made and permission changes will be filtered down to the child Role that exists within each Subtenant. However, it’s important to know that should the child Role ever be edited in the Subtenant, the link back to the Multi-Tenant User Role will be broken and it will become like any other User Role created in the Subtenant. To prevent this situation, Master Tenant administrators can set a “MULTITENANT LOCKED” option to restrict such edits in the Subtenant.
+
+New Multi-Tenant User Roles are created in Administration > Roles:
+
+### Procedure
+
+1. Click + CREATE ROLE
+2. Provide a NAME, TYPE (User Role), COPY FROM ROLE (if desired)
+3. Mark the boxes to set MULTITENANT ROLE and MULTITENANT LOCKED
+4. Click SAVE CHANGES
+
+### Results
+
+After saving the Role, it will appear in the Master Tenant and will also be seeded down to the Tenant we’ve already created since it is a Multi-Tenant User Role. We’ve also locked the Role so that Subtenant users cannot edit it and thus unlink it from future permissions edits made in the Master Tenant. Keep in mind that no matter what permissions we set, Users in the Subtenant will not be able to exceed permissions set on the Tenant Role as discussed in a prior section. If desired, you can click into this User Role now and edit its permissions to suit your needs.
+
+![../../_images/addUserRole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-870C9D97-516B-4D34-8339-550FCB2EA699-high.png)
+
+At this point we’re ready to add a User which will make the Tenant usable. We can create one in the new Tenant by navigating to the Tenant list page (Administration > Tenants) and selecting the Tenant. There are a number of configurations to make when creating a user but when selecting the User’s Role you should see the previously-created Multi-Tenant User Role.
+
+![../../_images/addUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E03CE619-CA56-4601-95F4-61D3F0A0EE7B-high.png)
+
+After saving the new User, we can make the first test of the new Tenant by impersonating the User and entering the Tenant. In the list of Users on the Tenant detail page, click the gear (⚙) icon at the end of the User’s row and select “Impersonate.” You should end up inside the new Tenant operating as the new user. This can be confirmed by making note of the updated name given in the upper-right portion of the application window. To quit impersonating, click on the name and select “Quit Impersonating.”
+
+At this point we’ve created a User manually but it’s important to point out that HPE Morpheus Enterprise can also use an existing identity integration, such as Microsoft Active Directory, to manage User creation and Role assignment. Expand the section below to see an example use case or continue on if you’d prefer to administer your Users directly in HPE Morpheus Enterprise. The complete integration guide elsewhere in HPE Morpheus Enterprise docs also includes common Active Directory troubleshooting steps should those be needed.
+
+Microsoft Active Directory Example
+
+Active Directory is Microsoft’s primary authentication service. It is widely used in enterprise organizations and even in Microsoft cloud services. While Active Directory also supports LDAP protocol support (which HPE Morpheus Enterprise can integrate with as well), HPE Morpheus Enterprise includes a dedicated identity integration type specifically for Active Directory. By integrating Active Directory, HPE Morpheus Enterprise administrators can fully offload the work of managing the user lifecycle to Active Directory. Creating new users, applying roles to users, updating basic user data, disabling users, and more can be handled in Active Directory and automatically filtered down to HPE Morpheus Enterprise. This section includes an example integration walkthrough as well as additional details on the integration feature set.
+
+NOTE
+
+should be used when integrating more than one Active Directory identity source with the same HPE Morpheus Enterprise Tenant. You must ensure the users on each identity source are unique users or that the two domains use different naming conventions for users.
+
+In HPE Morpheus Enterprise, identity sources (if used) are configured per Tenant. In order to see an identity integration or create a new one, navigate to a Tenant detail page (Administration > Tenants > Selected Tenant) and click IDENTITY SOURCES. From this page we can add a new identity source or click the pencil (✎) icon next to an existing identity source to view or edit it. Any configured identity source will apply to just one Tenant and they cannot be shared. One scenario where this is especially useful is in an MSP appliance where each Tenant is a siloed environment for a specific customer. The customer’s own existing Active Directory server and groups can be leveraged to build HPE Morpheus Enterprise user accounts with correct role mapping automatically.
+
+When configuring an Active Directory integration in HPE Morpheus Enterprise, AD groups are mapped to HPE Morpheus Enterprise roles. When the user logs in for the first time, HPE Morpheus Enterprise adds the new user account with correct name, email address, and applies one or more roles depending on configuration. Going forward, HPE Morpheus Enterprise will sync down any changes to the user, including any role changes based on changes to the user’s associated AD groups or updated passwords. Additionally, disabling a user in AD will prevent them from accessing HPE Morpheus Enterprise.
+
+IMPORTANT
+
+HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP. Ensure that HPE Morpheus Enterprise is able to talk to the AD server on the proper port.
+
+In a simple example, we have an Active Directory server which has two groups relevant to HPE Morpheus Enterprise, “Morpheus Users” and “Morpheus Admins.” We will configure HPE Morpheus Enterprise so that only users in the “Morpheus Users” group can access HPE Morpheus Enterprise in any capacity. Users who are also in the “Morpheus Admins” group will take on the System Admin role in HPE Morpheus Enterprise. We’ll see later when the integration is configured how HPE Morpheus Enterprise roles can be mapped to AD groups. In the same AD server, I have two users. John Smith is in groups “Morpheus Users” and “Morpheus Admins”. John Jones is only in the “Morpheus Users” group.
+
+![../../_images/ad.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37CF710C-C556-4604-8944-85D5F68F7113-high.png)
+
+Knowing the AD scheme and the requirements for HPE Morpheus Enterprise user roles, we can begin the process of creating the integration. Identity integrations are specific to each Tenant so begin by navigating to the Tenant detail page (Administration > Tenants > Selected Tenant) and clicking IDENTITY SOURCES. On setting the type to “Active Directory,” the form will update with the needed fields. Note the following basic fields:
+
+- **AD SERVER:** The IP address or hostname for the Active Directory Server
+- **DOMAIN:** The AD domain in which the relevant users and groups reside
+- **BINDING USERNAME:** A server user which has access to relevant objects on the AD server. In my example, I’ve used the in‐built Administrator user which is the easiest option. Other users may be used depending on your organization’s IT security policies but the integration with HPE Morpheus Enterprise will not work properly if the user does not have the needed access
+- **BINDING PASSWORD:** The password for the user in the prior field
+
+With the basic configurations completed, the remaining configurations will affect HPE Morpheus Enterprise user and role generation. A REQUIRED GROUP is optional and is a group the user must be in to have any HPE Morpheus Enterprise access. Here we require that users be in the “Morpheus Users” group. A DEFAULT ROLE is required and will be assigned to all users regardless of any additional roles they may be assigned based on their AD group membership. Beyond that, all other HPE Morpheus Enterprise roles will be listed here and an AD group name can be associated with as many as you required. In this example, we are giving users in the “Morpheus Admins” group the HPE Morpheus Enterprise System Admin role. Though we did not use them, it’s worth pointing out that ENABLE ROLE MAPPING PERMISSION will give administrators in the Tenant the ability to update the AD role mappings (though they will not have access to the core integration fields such as AD SERVER, DOMAIN, or binding user details). MANUAL ROLE ASSIGNMENT allows users to manually update HPE Morpheus Enterprise roles outside of the automatic mappings created by the AD integration.
+
+![../../_images/intConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-97C6395B-C01C-4B57-B67A-4D1DE7000BBB-high.png)
+
+With the above integration steps completed, users can now log into HPE Morpheus Enterprise and a user account with correct roles will automatically be created. In our example case, John Smith has logged in and we can see he is assigned the default role as well as the System Admin role based on his AD group associations. Going forward, HPE Morpheus Enterprise will continue to sync any changes to these users. For example, HPE Morpheus Enterprise roles may be updated based on changing AD groups or user access may be completely revoked by disabling the user in AD.
+
+![../../_images/user.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C3D36630-6135-4FE6-950F-230FE31AFEC9-high.png)
+
+1. Navigate to Administration > Tenants
+2. Select a Tenant
+3. Select IDENTITY SOURCES
+4. Select + ADD IDENTITY SOURCE
+5. Set the TYPE to “Active Directory”
+6. Populate the following:
+
+   Name
+   :   A friendly name in HPE Morpheus Enterprise for the AD integration
+
+   AD Server
+   :   The Hostname or IP address of AD Server
+
+   Domain
+   :   The AD domain in which the relevant user and group objects reside
+
+   USE SSL
+   :   Indicates whether SSL should be used for communication with the AD server. HPE Morpheus Enterprise will connect over port 389 for non‐secure LDAP and port 636 for secure LDAP, ensure HPE Morpheus Enterprise can connect to the AD server over the correct port
+
+   Binding Username
+   :   A username for a service account which has access to relevant objects (users, groups, etc.). For ease, the “Administrator” user may be used
+
+   Binding Password
+   :   The password for the above account
+
+   Required Group
+   :   The AD group users must be in to have access (optional, see example in the prior section)
+
+   Default Role
+   :   The default role a user is assigned when they are in the required group or if no specific group mapping applies to the user (see example in prior section)
+
+   ENABLE ROLE MAPPING PERMISSION
+   :   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the basic Identity Source configuration (AD server, domain, binding user details, etc)
+
+   MANUAL ROLE ASSIGNMENT
+   :   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user)
+
+   NOTE
+
+   For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+7. Select SAVE CHANGES.
+
+   Now allowed AD users can login to HPE Morpheus Enterprise via their Active Directory credentials and a User will be automatically generated to HPE Morpheus Enterprise with matching metadata and mapped Role permissions.
+
+## Whitelabeling
+
+HPE Morpheus Enterprise allows each Tenant to be customized with its own look and feel through whitelabeling features. Your organization can replace the stock HPE Morpheus Enterprise logo and color scheme with your own logos and colors. Whitelabel settings are held in Administration > Settings > Whitelabel and are mostly self-explanatory. Upload logos and set custom hexadecimal colors in each field. When done, be sure to set the “Enable Whitelabel” configuration and click SAVE all the way at the bottom of the page. If needed, review a more detailed explanation of each [whitelabel setting](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#whitelabel) in HPE Morpheus Enterprise documentation.
+
+![../../_images/whitelabelSettings.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-458BDDBC-723A-4A05-9745-372AC60C08DD-high.png)
+
+## Scoping Clouds to Tenants
+
+### About this task
+
+With the Tenant now created and seeded with a User and Roles, we’re ready to look at how to set up useful provisioning resources. Of course, Tenants are complete (yet isolated) HPE Morpheus Enterprise environments which can create their own Cloud integrations or utilize integrations with other third party technologies (assuming they haven’t been restricted from doing so by the Tenant Role). However, Master Tenant administrators may also choose to share integrations created in the Master Tenant down to Subtenant users.
+
+Many constructs in HPE Morpheus Enterprise have a “Visibility” attribute when viewed from the Master Tenant. This attribute controls whether the construct is “Private” (in other words reserved for a selected Tenant) or Public (available to all Tenants). In our example, we’re going to expose an Amazon AWS Cloud integrated in the Master Tenant down to our newly-created Subtenant. To set the Cloud visibility, use the following steps:
+
+### Procedure
+
+1. Navigate to the Clouds list page (Infrastructure > Clouds)
+2. Edit the Cloud by clicking the pencil icon (✎) in its row
+3. Toggle the VISIBILITY attribute to “Public”
+4. Click SAVE CHANGES
+
+### Results
+
+![../../_images/editCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BED65BE1-AF4D-4EC6-9680-03FADB9422C3-high.png)
+
+The Cloud is now exposed to the Subtenant but we also need to expose a Resource Pool (A VPC, in Amazon parlance) for Subtenant users to provision into. We do this from the Cloud detail page (Infrastructure > Clouds) > Click on selected Cloud.
+
+1. Select the Resources subtab
+2. Click ACTIONS next to the selected Resource Pool (VPC)
+3. Click Edit
+4. Expand the “Tenant Permissions” section
+5. Set Visibility to Public (alternatively, you could keep the Private visibility and add the new Tenant in the next field)
+6. Click SAVE CHANGES
+
+![../../_images/addResourcePool.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7E26EBB1-E238-4E5A-9BE2-ACEB243DDDE0-high.png)
+
+Repeat the same process for Networks and Security Groups, both of which are contained in the Networks subtab of the Cloud detail page.
+
+## Groups
+
+### About this task
+
+The last thing to take a look at before Library items and provisioning are Groups. Groups define which resources a User can access. Group access is defined by the User Role and many resources have a Group access component which allows administrators to control User access to things like Clouds, Networks, Datastores, Resource Pools, Folders and more.
+
+Groups exist solely within the Tenant that creates them, they cannot be shared down from Master Tenant to Subtenants. In order to create a Group for our new Tenant, impersonate the User we’ve created in previous steps. Once working in the Tenant, use the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Groups
+2. Click + CREATE
+3. Set a NAME for the Group and click SAVE CHANGES
+
+### Results
+
+We’ll now add the shared Cloud to the Group:
+
+1. Click on the name of the Group to access the Group detail page
+2. Click on the Clouds tab
+3. Click + ADD
+4. Use the typeahead field to select the shared Cloud
+5. Click SAVE CHANGES
+
+![../../_images/addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DA5D5406-4991-4E35-B064-4B94E55FE9C3-high.png)
+
+At this point the basic configuration steps are complete and we will attempt a provisioning test using built-in Instance Types which are preinstalled with HPE Morpheus Enterprise.
+
+## Provisioning Test
+
+### About this task
+
+At this point, you can conduct a test by attempting to provision one of the basic Instance Types shipped with HPE Morpheus Enterprise for demonstration purposes. To test, we’ll provision a basic Ubuntu box to our AWS Cloud.
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Ubuntu Instance Type
+4. Click NEXT
+5. Select the Group and Cloud noting that only resources shared with the Subtenant are selectable
+6. Name the Instance
+7. Click NEXT
+8. On the CONFIGURE tab, select a Resource Pool, Network, and Security Group once again noting that only resources shared with the Subtenant are selectable
+9. Click NEXT
+10. Click NEXT once again
+11. Click COMPLETE
+
+### Results
+
+![../../_images/createInstance.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-96B45365-D416-4CFC-9A46-6ADCC0455916-high.png)
+
+After a minute or two, the Instance should be fully provisioned.
+
+## Exposing Custom Instance Types to Subtenants
+
+Master Tenant administrators can also share custom Library items down to Subtenants. Do do this, navigate to Library > Blueprints and select an Instance Type. Click the pencil (✎) icon in the row for the selected Instance Type to edit it. As we’ve done before, update the VISIBILITY setting to Public. In addition, ensure the User Role for the Subtenant User grants access to the selected Instance Type. Once configurations have been made, conduct a similar test to the previous section. When you attempt to provision a new Instance, the new Instance Type should be selectable and the User should be able to provision the custom Instance Type in the same was as the default Instance Type was provisioned in the previous step.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json b/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
new file mode 100644
index 0000000..5ce9f72
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+  "title": "Virtual Desktop Persona",
+  "ordinal": 342,
+  "parent_title": "Personas",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.html",
+  "topic_cluster": {
+    "clustering_title": "Virtual Desktop Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB",
+        "clustering_title": "Virtual Desktop Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md b/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
new file mode 100644
index 0000000..3b196d4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96CA9359-BF7E-4C9B-8CB5-8A7B62B462AB.md
@@ -0,0 +1,64 @@
+# Virtual Desktop Persona
+
+The Morpheus VDI Persona provides a virtual desktop environment to grant users access to workstations and applications in a secure manner. Deploy pools of virtual machines on any supported HPE Morpheus Enterprise Cloud for users to reserve and use! HPE Morpheus Enterprise leverages open source client technologies, such as Apache Guacamole, to provide a performant and secure virtual desktop client for the end user while wrapping its frontend in a completely new framework. For information on configuring VDI pools for consumption in the Virtual Desktop Persona, see the [Tools section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html) of HPE Morpheus Enterprise docs.
+
+NOTE
+
+This is not an integration with existing VDI Pool Managers such as VMWare Horizon, Citrix VDI, or Nutanix XiFrame. It is a standalone HPE Morpheus Enterprise feature.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BCC17FD5-DF6E-4653-96F8-5647B13E6ED8-high.png)
+
+## Key Features
+
+- VDI Pool Management
+- Virtual Desktop Persona
+- RDP/SSH/VNC Console Support
+- RDP Remote App Support
+- Clipboard Copy/Paste
+- HiDPI Support
+- Auto Compression Scanning based on User Bandwidth
+- Audio Playback (RDP)
+- Local Printer (RDP)
+- Auto-Resize
+- Auto-Login based on HPE Morpheus Enterprise User Settings
+- Customizable User Background
+
+## Configuring Access to the Virtual Desktop Persona
+
+### About this task
+
+Access to the Virtual Desktop Persona and individual VDI pools is handled through the user Role and, where applicable, Tenant Role. When creating a new Role, access is restricted to the Virtual Desktop Persona and all VDI pools by default. To grant access:
+
+### Procedure
+
+1. Navigate to the Role (Administration > Roles > Selected Role)
+2. Access the Personas tab
+3. Toggle the Virtual Desktop permission to “Full” or “None”
+4. Access the VDI Pool Access tab
+5. Toggle access to selected VDI pools to “Full” or “None”, you can also toggle permission on all pools to “Full” or “None” with the Global Access selection
+6. Role changes are saved automatically, there is no need to manually save
+
+## Launching a VDI Instance
+
+VDI Instances are launched from the Virtual Desktops Persona. Depending on Role permissions, your account may default to this view or may even restrict you solely to this view. To access the Virtual Desktops Persona from the standard view or from another Persona, click on the user’s name in the upper-right corner of the application window. When available, this dropdown menu will list the standard HPE Morpheus Enterprise Persona view as well as any other Personas the user has permission to access. Click on Virtual Desktop to access the Virtual Desktop Persona.
+
+The Virtual Desktop Persona view lists out each of the virtual desktop types they can access. Click on the desired virtual desktop type to launch it. If there are virtual apps available for any listed desktop types, they are presented in a flyout menu alongside a “desktop” option to access the base OS over an individual app. Items categorized as “Desktops” are VDI pools configured in the Tools menu of the Standard Persona. Items categorized as “Instances” are Instances favorited by the current user in the Standard Persona (if they have access and they have favorited any Instances). Clicking on an Instance tile offers quick access to the Instance console.
+
+IMPORTANT
+
+Virtual Desktops are launched in a pop-up window. Be sure your web browser is not blocking pop-ups or create an appropriate exception for HPE Morpheus Enterprise virtual desktop pop-ups.
+
+## Changing the Virtual Desktop Persona Background
+
+### About this task
+
+The HPE Morpheus Enterprise Virtual Desktop Persona includes default backgrounds for an elegant look out of the box. If desired, users may change this background to suit personal taste or organizational branding. This change is unique to each individual account. At this time, there is no option for appliance-wide whitelabeling for Virtual Desktop Persona backgrounds.
+
+### Procedure
+
+1. Click on the user’s name in the far upper-right corner of the application window
+2. Click USER SETTINGS
+3. The section for “VDI Settings” is in the lower-right corner of the page
+4. Mark the RESET box and click SAVE to reset the Virtual Desktop Persona to the default background
+5. Click “Browse” and upload a local image to add a custom background
+6. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json b/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
new file mode 100644
index 0000000..75683c0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+  "title": "Invoices",
+  "ordinal": 75,
+  "parent_title": "Costing",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.html",
+  "topic_cluster": {
+    "clustering_title": "Invoices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09",
+        "clustering_title": "Invoices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md b/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
new file mode 100644
index 0000000..200caa1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-96CE6685-57DE-4E5F-9D14-9CBC2C75DF09.md
@@ -0,0 +1,135 @@
+# Invoices
+
+HPE Morpheus Enterprise offers highly-granular costing data through invoices. Invoice views are highly customizable, allowing for nearly unlimited combinations of output columns and filtering. Invoices are based on monthly periods and allow you to slice costs in a highly granular way, as well as predict final monthly costs before the end of the period. As with other HPE Morpheus Enterprise UI pages that support advanced table customization, these views can be saved to provide easy access to costing views specific to varying business needs. By default, the invoice list page will show the last three months’ invoices across all clouds and invoice types but the list can be modified to target differing time periods or resource groupings. Read on in this section to discover the meaning of various invoice types and how this tool can be used to create targeted costing views.
+
+## Invoices for Public vs On-Prem Clouds
+
+HPE Morpheus Enterprise supports live cost syncing for many public clouds, including all of the most commonly-used public clouds like Amazon AWS, Microsoft Azure, and Google Cloud Platform. For these clouds, costing sync is enabled through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). When live costs are synced from public clouds, invoices will be generated for this activity including month-to-date costs, projected monthly totals, historical cost data, and a lot more which is discussed in the following sections.
+
+Additionally, HPE Morpheus Enterprise has implemented a costing service for on-prem clouds to closely mirror the live costing experience through a public cloud. As with public clouds, this costing service is enabled for on-prem clouds through the COSTING field on the Add/Edit Cloud modal (Infrastructure > Clouds > selected Cloud > EDITbutton). Change the setting to “Sync Costing” and save the changes to the cloud integration. From this point, costs will be aggregated into invoices for on-prem clouds in the same way as public clouds including complete line item listings, current costs for the month, month-end projections, and much more as discussed in the next sections.
+
+## Invoice List Page
+
+The invoices list page shows high-level aggregate data on a group of invoices and allows you to locate a specific invoice for a deeper look. By default, invoices from the last three months across all clouds and types are shown here. Depending on settings, this page can automatically refresh itself so the list of displayed invoices and the aggregate information on them is up to date.
+
+![../_images/1listInvoices.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7D08D7CC-C9FD-4013-9B64-78A4F9C8B639-high.png)
+
+### Aggregated Invoice Data
+
+The following aggregate totals are displayed for all invoices picked up by set filters:
+
+- **Periods:** The total number of months in the period determined by your start and end date filters. If no start and end dates are set, a three month period will be shown. If a one-month period is selected, the name of that month (ex. Aug 2020) is shown
+- **Total Invoices:** The total number of invoices captured by current filters
+- **MTD Cost:** The combined month-to-date cost for all invoices captured by current filters
+- **Total Cost:** The expected total month-end cost for all invoices captured by current filters
+
+## Creating Views
+
+### About this task
+
+Invoice list views are highly-customizable allowing for virtually limitless combinations of output columns and filtering. A common set of output columns is provided in a default view but users can add and remove columns from a large list of data points and even save multiple views for easy access to different data sets. Any of your stored views can be set as the default to be displayed each time the invoices list page is active.
+
+To create a new invoices view:
+
+### Procedure
+
+1. Click the gear icon (⚙)
+2. Click on one or more columns from the “Columns” list to add or remove an output field
+3. Click “+ add view”
+4. Provide a name and a description value for your new view
+5. If desired, mark the box to set the new view as your default view so it appears automatically each time the invoices list page is accessed
+6. Click SAVE
+
+### Results
+
+![../_images/2createViews.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E081EF68-3B0E-4A5A-8CFE-8E8B47D87BAD-high.png)
+
+### Available Output Columns
+
+When creating an invoices view, there are many output columns available to select. Consult the list below for more details on each of the available columns:
+
+#### Available Output Columns: Expand for Complete List
+
+- **Invoice ID:** The unique ID in HPE Morpheus Enterprise for the invoice
+- **Type:** The invoice type; Cloud, Container, Group, Server, Instance, Resource, User, or Volume
+- **Ref ID:** An ID for the reference object tied to the invoice (server, instance, cloud, etc.). Reference IDs are reused across invoice types so invoices referring to identical Ref IDs may not necessarily refer to the same reference object
+- **Reference:** The name of the reference object (server, cloud, user, group, etc.) tied to the invoice
+- **Cloud ID:** The internal ID for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Cloud:** The name for a Cloud integration in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Cloud
+- **Instance ID:** The internal ID for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Instance:** The name for an Instance in HPE Morpheus Enterprise. This field will be blank unless the invoice references an Instance
+- **Server ID:** The internal ID for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Server:** The name for a server in HPE Morpheus Enterprise. This field will be blank unless the invoice references a server
+- **Cluster ID:** The internal ID for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Cluster:** The name for a cluster in HPE Morpheus Enterprise. This field will be blank unless the invoice references a cluster
+- **Plan ID:** The internal ID for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Plan:** The name for a service plan in HPE Morpheus Enterprise. This field will be populated only for invoices that reference an object which would be associated with a service plan (server, Instance, container, etc.).
+- **Group ID:** The internal ID for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **Group:** The name for a Group in HPE Morpheus Enterprise. This field will be blank unless the invoice references a Group
+- **User ID:** The internal ID for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **User:** The name for a User in HPE Morpheus Enterprise. This field will be blank unless the invoice references a User.
+- **Tenant ID:** The internal ID for the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Tenant:** The name of the HPE Morpheus Enterprise Tenant which owns the reference object
+- **Period:** The monthly period during which the invoice was generated
+- **Interval:** The length of the invoice billing period, currently all invoices are generated at a one-month interval
+- **Start Date:** The start date and time for the invoice period, typically the first of the month at midnight
+- **End Date:** The end date and time for the invoice period, typically the last day of the month at midnight
+- **Ref Start:** The date and time the reference object is created or the start of the invoicing period if the reference object existed prior to the start of the invoicing period
+- **Ref End:** The date and time the reference object is decommissioned or the end of the invoicing period if the reference object still existed at the end of the period
+- **Compute Cost:** The actual compute costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Cost:** The actual storage costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Cost:** The actual network costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Cost:** The actual additional costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Cost:** The actual month-to-date costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Cost:** The actual total costs for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Cost:** Compute costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Cost:** Storage costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Cost:** Network costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Cost:** Additional costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Cost:** Month-to-date costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Cost:** Total costs determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Compute Price:** The actual compute price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Storage Price:** The actual storage price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Network Price::** The actual network price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Extra Price:** The actual additional price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **MTD Price:** The actual month-to-date price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Total Price:** The actual total price (cost plus markup) for the invoice (from public cloud costing API when available or from an on-prem cloud with “Sync Costing” enabled)
+- **Metered Compute Price:** Compute price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Storage Price:** Storage price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Network Price:** Network price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Extra Price:** Additional price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered MTD Price:** Month-to-date price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Metered Total Price:** Total price (cost plus markup) determined by HPE Morpheus Enterprise usage and pricing data (when live pricing data is not available, such as with an on-prem cloud without “Sync Costing” enabled)
+- **Active:** Indicates whether or not the reference object is currently existing and active
+- **Date Created:** The date and time the invoice is created
+
+## Invoice Types
+
+Invoices can reference any of the HPE Morpheus Enterprise workload element types or resource reference types in the list below. Some invoice types are broader and may account for resource costs calculated in other narrower invoice types. For instance, a container-type invoice returns costs for a single node of an Instance while an Instance-type invoice for the same period may be including costs for that same single node. The invoices list view can be filtered to show just one type or all types. Complete descriptions of each invoice type are included below:
+
+- Cloud: In HPE Morpheus Enterprise, a Cloud is any connection into a public cloud, private cloud, hybrid cloud, or bare metal server
+- Container: A single node of a service, in other words, a single node of a HPE Morpheus Enterprise Instance. This could be a virtual machine or Docker container which is part of a HPE Morpheus Enterprise-managed Instance
+- Group: In HPE Morpheus Enterprise, Groups define which resources a user has access to through their role. Clouds are added to Groups and users access Clouds to which their roles give access
+- Server: A server refers to any individual host, virtual machine, or bare metal server that is inventoried or managed by HPE Morpheus Enterprise. This can include servers which are parts of HPE Morpheus Enterprise-managed Instances or inventoried servers from integrated Clouds
+- Instance: A set of containers or virtual machines which correlate to a single horizontally-scalable entity. This could be a single VM or it could be many VMs operating as a service
+- Resource: Resource-type invoices are generated when HPE Morpheus Enterprise cannot determine that the referenced costs belong to any of the other resource reference types in this list
+- User: User-type invoices aggregate the costs of resources owned by a specific HPE Morpheus Enterprise user during the invoicing period
+- Volume: When possible, costs will be tied to known volumes and a volume-type invoice is generated as a result
+
+## Invoice Detail Page
+
+### Summary
+
+The summary tab of the invoice detail page displays a great deal of reference information about the resource identified by the invoice. This will vary depending on the type of resource. In addition, total and projected costs are displayed along with cost breakdowns for compute, storage, network, and other categories. Month-to-date totals and final month projections are given.
+
+### History
+
+The history tab displays the costs and prices for the associated resource over time. This tab is especially valuable for resources that have existed through at least a few invoicing periods to show changes over time. In addition, cost breakdowns for compute, storage, network, and other categories are shown for each invoicing period. These costs can be displayed visually through graphs.
+
+![../_images/4invoiceHistory.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-66262EA5-76D1-41C6-AE62-C1CF505E9976-high.png)
+
+### Line Items
+
+For supported resource types, HPE Morpheus Enterprise includes a tab to display all costing line items. This provides the user with a complete list of line items that make up the costing totals on the invoice.
+
+![../_images/5invoiceLineItem.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-035126CA-FDE7-492E-842A-094558CB1655-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json b/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
new file mode 100644
index 0000000..1fe3106
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+  "title": "Overview",
+  "ordinal": 247,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md b/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
new file mode 100644
index 0000000..d710e5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9817DF88-2C4B-485C-8C0E-B15B0EEA2166.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise provides a simple-to-use Bare Metal boot capability based on PXE. When a server boots and is redirected to the HPE Morpheus Enterprise server for the installation files, they can be configured to be simply passed an OS or Hypervisor (in which case HPE Morpheus Enterprise will see them as Bare Metal servers with no further detail) or they can be brought on as Virtual Machines or Docker Hosts. Installation of the HPE Morpheus Enterprise Agent can also be done during the initial configuration stage.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json b/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
new file mode 100644
index 0000000..991ee08
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+  "title": "VMware Fusion",
+  "ordinal": 476,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-98351F93-76B4-480B-91F1-58E3E3492651.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Fusion",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-98351F93-76B4-480B-91F1-58E3E3492651",
+        "clustering_title": "VMware Fusion"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md b/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
new file mode 100644
index 0000000..e3aba07
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-98351F93-76B4-480B-91F1-58E3E3492651.md
@@ -0,0 +1,152 @@
+# VMware Fusion
+
+## Add a VMware Fusion Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select VMware Fusion, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   VMWARE FUSION HOST
+   :   IP or URL of VMware Fusion Host
+
+   WORKING PATH
+   :   Existing folder HPE Morpheus Enterprise will write to on Host
+
+   USERNAME
+   :   Host Username
+
+   PASSWORD
+   :   Host Password
+
+   BRIDGE NAME
+   :   Will auto-populate upon successful authentication with the Fusion Host (E.X. ‘EN0: ETHERNET’)
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.json b/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.json
new file mode 100644
index 0000000..1804fe0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+  "title": "Restarting the HPE Morpheus Enterprise Agent",
+  "ordinal": 48,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9B75C475-9243-4444-BF22-C43480298274.html",
+  "topic_cluster": {
+    "clustering_title": "Restarting the HPE Morpheus Enterprise Agent",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9B75C475-9243-4444-BF22-C43480298274",
+        "clustering_title": "Restarting the HPE Morpheus Enterprise Agent"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.md b/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.md
new file mode 100644
index 0000000..73b4ff6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9B75C475-9243-4444-BF22-C43480298274.md
@@ -0,0 +1,15 @@
+# Restarting the HPE Morpheus Enterprise Agent
+
+In some situations, it may necessary to restart the HPE Morpheus Enterprise Agent on the host to re-sync communication from the Agent to the HPE Morpheus Enterprise appliance.
+
+## Linux
+
+On the target host, run `sudo morpheus-node-ctl restart morphd` and the HPE Morpheus Enterprise agent will restart. `morpheus-node-ctl status` will also show the agent status.
+
+## Windows
+
+The HPE Morpheus Enterprise Windows Agent service can be restarted in Administrative Tools > Services.
+
+TIP
+
+The HPE Morpheus Enterprise Remote Console is not dependent on Agent communication and can be used to install or restart the HPE Morpheus Enterprise agent on an Instance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json b/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
new file mode 100644
index 0000000..11eb03f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+  "title": "Requirements",
+  "ordinal": 3,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md b/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
new file mode 100644
index 0000000..19024fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9B880B72-11C3-4E3A-8610-E34BC8CBFDCC.md
@@ -0,0 +1,17 @@
+# Requirements
+
+HPE Morpheus Enterprise Software is a software-based appliance installation capable of orchestrating many clouds and hypervisors. Before an installation is started it is important to understand some of the base requirements.
+
+In the simplest configuration HPE Morpheus Enterprise needs one Appliance Server. The Appliance Server, by default, contains all the components necessary to orchestrate both VMs and containers. To get started some base requirements are recommended:
+
+**Subtopics**  
+
+- **[Base Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html)**
+- **[Storage Considerations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-45DBACB2-9ED7-4538-9BF9-2D121178F539.html)**
+- **[Network Connectivity](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html)**
+- **[Components](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html)**
+- **[Common Ports & Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0DB10170-9557-43A8-BF4B-76F2A2C25FBE.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-72A18F4A-3841-45DA-8D48-53A23DCFFEA9.html)**
+- **[SELinux](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html)**
+- **[OpenSearch Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html)**
+- **[Supported Locales](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6F84861F-7AAD-462D-A85C-CC3FDB9269C4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json b/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
new file mode 100644
index 0000000..47969f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+  "title": "Upgrades & Maintenance",
+  "ordinal": 19,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrades & Maintenance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313",
+        "clustering_title": "Upgrades & Maintenance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md b/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
new file mode 100644
index 0000000..9feb1fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9BBC42D3-B99F-451A-9D0B-E3B7CC589313.md
@@ -0,0 +1,9 @@
+# Upgrades & Maintenance
+
+**Subtopics**  
+
+- **[Upgrading](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C6CCEE5-9F7E-45C2-8632-7D67240C5BC2.html)**
+- **[morpheus-ctl tips](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html)**
+- **[Morpheus DB Migration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8F72A3D3-1A97-4BE5-8295-7DF36301E576.html)**
+- **[Scaling Morpheus Nodes](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3F974C16-B0C9-4848-810A-74F7CC8CA82B.html)**
+- **[Morpheus UI war files](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2BA625F8-895A-414C-9DAD-BD07A04CEB03.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json b/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
new file mode 100644
index 0000000..2eeb8e7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+  "title": "License",
+  "ordinal": 330,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.html",
+  "topic_cluster": {
+    "clustering_title": "License",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97",
+        "clustering_title": "License"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md b/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
new file mode 100644
index 0000000..3d23c49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9BDE2563-18FC-49B0-83D7-47F57E044D97.md
@@ -0,0 +1,38 @@
+# License
+
+## Overview
+
+HPE Morpheus Enterprise requires a valid license for provisioning new Instances, Apps and Hosts, and converting existing Instances and Hosts to managed. Licenses can be applied and updated in this section, and the current license status can be checked.
+
+NOTE
+
+HPE Morpheus Enterprise is licensed for a certain number of concurrent workload elements (WLEs) that may be managed or inventoried at any one time. See our [Knowledge Base](https://support.morpheusdata.com/s/article/What-is-a-Workload-Element-or-WE-for-purposes-of-Morpheus-licensing?language=en_US) for specific information on the types of WLEs that count against HPE Morpheus Enterprise licensing.
+
+## Current License
+
+If a License Key has already been applied, it will be shown in the list of Current Licenses. This page also contains useful information on license usage including start and end dates for the license, the total number of HVM sockets licensed, and how many of the licensed HVM sockets have been used.
+
+NOTE
+
+Once a current License expires or has reached its limits, users will no longer be able to provision new Instances or Clusters and will not be able to convert existing VMs to managed. HPE Morpheus VM Essentials will otherwise continue to function.
+
+![The license settings page](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DEE9EE99-95C7-48D3-9CA5-26BD14693D4D-high.png)
+
+## Upgrade License Key
+
+### About this task
+
+To add a new or update an existing License:
+
+### Procedure
+
+1. Copy the license key into the large text area at the bottom of the page
+2. Click UPDATE
+
+### Results
+
+If valid, the new License will be applied. Note that the new license may replace an existing license or may stack onto an existing license.
+
+## Request new License
+
+To request a new license, use the [My HPE Software Center](https://myenterpriselicense.hpe.com) or contact your account manager.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json b/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
new file mode 100644
index 0000000..07b393e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+  "title": "vRealize Orchestrator",
+  "ordinal": 381,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html",
+  "topic_cluster": {
+    "clustering_title": "vRealize Orchestrator",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7",
+        "clustering_title": "vRealize Orchestrator"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md b/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
new file mode 100644
index 0000000..7a87863
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.md
@@ -0,0 +1,185 @@
+# vRealize Orchestrator
+
+The vRealize Orchestrator (vRO) Integration provided for HPE Morpheus Enterprise enables users to easily trigger existing workflows that may already exist in vRealize Orchestrator. Not only can the user trigger these workflows, but they can also be chained easily into non-vRO workflows and process both output and input parameters of a workflow.
+
+## Adding the Integration
+
+Setting up the vRO integration involves some steps which vary depending on the authentication model being used.
+
+NAME
+:   Name of the integration
+
+API URL
+:   Typically, the API URL is run on port 8283. A sample API URL may look like the following example: `https://vrahost.com:8283/`
+
+AUTH TYPE
+:   Chosen based on the authentication provider configured on vRO
+
+CREDENTIALS
+:   Choose `Local Credentials` to enter credentials for this integration or choose to create/use an existing credentials
+
+USERNAME
+:   Username that will be configured on the integration that can authenticate with vRO
+
+PASSWORD
+:   Password that will be configured on the integration for the username that can authentication with vRO
+
+Tenant Token
+:   The domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`
+
+    NOTE
+
+    At times, this can vary depending on how authentication and role assignments for the user have been set up for vRO.
+
+CLIENT ID
+:   The ID used and obtained from the vRO server, typically used when using `OAuth 2.0` Auth Type
+
+### Basic Auth Type
+
+The `Basic` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `vSphere` Authentication Provider. When vRO is configured with this provider, users login to vRO using their vSphere/vCenter credentials, which HPE Morpheus Enterprise will use the same.
+
+NOTE
+
+The `CLIENT ID` field can contain any value. It will be unused with the `Basic` Auth Type
+
+Example of a configured `vSphere` Authentication Provider from the vRO Control Center:
+
+![../../_images/vsphere_auth_provider.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A89B217A-D71D-497C-9346-6E62C493B2B7-high.png)
+
+Example of a configured `Basic` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/basic_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4B3F0F89-D9C0-49D3-B0CE-52017F8F3ADE-high.png)
+
+### OAuth 2.0 Auth Type
+
+The `OAuth 2.0` Auth Type should be used when configuring the HPE Morpheus Enterprise integration to a vRO instance configured with the `VIDM` option or other OAuth provider.
+
+When using `OAuth 2.0`, the Client ID must be gathered first. This can be found by browsing a file on the actual VRA server using SSH. On the vRA server, run the following command: `grep -i cafe_cli= /etc/vcac/solution-users.properties | sed -e 's/cafe_cli=//'`
+
+Be sure to fill in the tenant token as the domain or tenant ID, for example: `vsphere.local`, with a username of `administrator@vsphere.local`.
+
+Example of a configured `OAuth 2.0` Auth Type in the HPE Morpheus Enterprise integration:
+
+![../../_images/oauth_auth_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-709086F0-E900-49AD-8D31-0CFD87259E9A-high.png)
+
+### vRA Auth Type
+
+The `vRA` Auth Type should be used when the vRA identity provider is configured for your vRO. The `vRA` Auth Type and `OAuth` Auth Type fields requirements are the same, execept when using `vRA` Auth Type the `Client ID` is no longer needed.
+
+## Using vRealize Orchestrator
+
+One of the first things HPE Morpheus Enterprise does when it is tied into a vRO integration is sync all available workflows by category. These workflows become available when creating a new HPE Morpheus Enterprise task in Library > Automation. HPE Morpheus Enterprise allows a user to map these vRO workflows into the task engine. The task engine allows users to design workflows that chain tasks in order or operate at different phases of a provisioning request. For more information on tasks, please read the Automation documentation.
+
+Creating a task for vRO is simple.
+
+First, go to Library > Automationand create a new task. Enter a Name and a Code, the Code can be used later to reference the results of tasks. Choose a task type of `vRealize Orchestrator Workflow`. A dropdown will appear allowing one to first select the active vRO Integration you would like to use. Once that is selected, a list of workflows becomes available.
+
+NOTE
+
+The next part is where things can get a bit tricky. The parameter body (expected in JSON) format can be a bit difficult to track down. One way is to use the Network Chrome inspector when kicking off a sample workflow from the vRO HTML5 client and grabbing the parameter JSON. Another is to query the API yourself and look at the samples from historical run history.
+
+An example payload for the SSH / Run SSH Command Workflow would look like this:
+
+```
+```
+{  
+    "parameters": [  
+        {  
+            "name": "hostNameOrIP",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "x.x.x.x"  
+                }  
+            }  
+        },  
+        {  
+            "name": "port",  
+            "type": "number",  
+            "value": {  
+                "number": {  
+                    "value": 22  
+                }  
+            }  
+        },  
+        {  
+            "name": "cmd",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "echo \"Hello <%=instance.name%>\""  
+                }  
+            }  
+        },  
+        {  
+            "name": "encoding",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        },  
+        {  
+            "name": "username",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "myuser"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passwordAuthentication",  
+            "type": "boolean",  
+            "value": {  
+                "boolean": {  
+                    "value": true  
+                }  
+            }  
+        },  
+        {  
+            "name": "password",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "password"  
+                }  
+            }  
+        },  
+        {  
+            "name": "path",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": "\/var\/lib\/vco\/app-server\/conf\/vco_key"  
+                }  
+            }  
+        },  
+        {  
+            "name": "passphrase",  
+            "type": "string",  
+            "value": {  
+                "string": {  
+                    "value": ""  
+                }  
+            }  
+        }  
+    ]  
+}
+```
+```
+
+Note that all HPE Morpheus Enterprise variables can be injected into the parameter body. In the above example we inject the instance name into the sample command with `<%=instance.name%>` but other values can be used, such as `<%= server.sshHost %>` for the hostname and `<%= server.sshPort %>` for the port. Additional variable examples can be found here: [Variables](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3EDAD6F4-CF03-45A0-8073-FC430DE11CA7.html)
+
+Adding this task to a workflow allows the result parameters to be referenced in subsequent tasks called throughout the workflow. For example, a local script task type could reference the output text of the above ssh command by injecting the following results map: `echo "results.vro: <%=results.vro.find{it.name == 'outputText'}?.value?.string?.value%>"` With this example, `vro` refers back to the “Code” of the vRO task that would contain the ouput we wish to referece. More information on Task Results can be found here: [Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)
+
+Additional output/map examples referencing a previous task with the “Code” of `vrossh`:
+
+- Print all output: `echo '<%=results.vrossh.encodeAsJson().toString() %>'`
+- Print the `outputText` variable/output: `echo "results.vrossh.outputText: <%=results.vrossh.find{it.name == 'outputText'}?.value?.string?.value%>"`
+- Print the `errorText` variable/output: `echo "results.vrossh.errorText: <%=results.vrossh.find{it.name == 'errorText'}?.value?.string?.value%>"`
+- Print the `result` variable/output, returned as a string: `echo "results.vrossh.result: <%=results.vrossh.find{it.name == 'result'}?.value?.string?.value%>"`
+- Print the `exitcode` variable/output, returned as a number: `echo "results.vrossh.exitcode: <%=results.vrossh.find{it.name == 'exitcode'}?.value?.number?.value%>"`
+
+There are very powerful options available for chaining results and injecting variables relevant to the instance being provisioned or even custom inputs from an operational workflow. Please reference the rest of the Automation documentation for examples.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
new file mode 100644
index 0000000..eb44054
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+  "title": "Syslog",
+  "ordinal": 504,
+  "parent_title": "Logs",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.html",
+  "topic_cluster": {
+    "clustering_title": "Syslog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC",
+        "clustering_title": "Syslog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
new file mode 100644
index 0000000..9755802
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9C89A56C-2ED4-4085-B2D7-62953B9028DC.md
@@ -0,0 +1,10 @@
+# Syslog
+
+## Adding Syslog Integration
+
+### Procedure
+
+1. Navigate to Administration > Settings > Logs
+2. Expand the HPE Morpheus Enterprise logging section
+3. Add the Syslog forwarding rules
+4. Select QUICK ADD
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json b/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
new file mode 100644
index 0000000..3c72289
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+  "title": "Add Amazon ELB load balancer",
+  "ordinal": 493,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.html",
+  "topic_cluster": {
+    "clustering_title": "Add Amazon ELB load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80",
+        "clustering_title": "Add Amazon ELB load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md b/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
new file mode 100644
index 0000000..7443f42
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9CC817B3-66AB-4F5C-87A4-1B4F37385C80.md
@@ -0,0 +1,33 @@
+# Add Amazon ELB load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Amazon ELB**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Amz ELB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C14F7BC3-0BDA-4CF2-A85A-19B1C1EF8694-high.jpg)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   SCHEME
+   :   From the drop-down list, select the configured scheme.
+
+   AMAZON VPCS
+   :   From the drop-down list, select the configured private cloud.
+
+   AMAZON SUBNETS
+   :   From the drop-down list, select the subnets to enable.
+
+   AMAZON SECURITY GROUPS
+   :   From the drop-down list, select the configured security group.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json b/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
new file mode 100644
index 0000000..fac13a2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+  "title": "Health",
+  "ordinal": 320,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html",
+  "topic_cluster": {
+    "clustering_title": "Health",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2",
+        "clustering_title": "Health"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md b/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
new file mode 100644
index 0000000..d34d351
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.md
@@ -0,0 +1,142 @@
+# Health
+
+## HPE Morpheus Enterprise Health
+
+![../../_images/morpheusHealth500.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BB8CA295-BF75-426C-941D-EBB1FB9233DC-high.png)
+
+The HPE Morpheus Enterprise Health section provides an overview of the health of your HPE Morpheus Enterprise appliance. It includes an appliance health summary in the following areas:
+
+- **CPU:** Appliance CPU usage is checked. If usage is greater than 50%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to upgrade to increase CPU. The **Overall** health indicator will mirror the CPU health indicator
+- **Memory:** If swap usage is above 60% or HPE Morpheus Enterprise memory usage is above 95%, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to complete the check for any reason, it will be in a red or error state. Depending on appliance performance and how frequently this indicator is in a warning state, it may be necessary to increase swap, upgrade the appliance to add memory, or consider a different appliance architecture for those using single-node appliances
+- **Storage:** If utilization of the filesystem mounted at “/” exceeds 80%, this indicator will be in a yellow warned status. Above 90% will put this indicator in red or error status
+- **Database:** The database is checked. If the number of database connections exceeds the configured maximum number of connections or if any test queries are reported as being slow, this indicator will be in a yellow or warning state. If HPE Morpheus Enterprise is unable to communicate with the database, it will be in a red or error state. In the database section further down the page, you can check the number of maximum used connections against the number of max connections. In the case of database connections exceeding the maximum, consider increasing the maximum settings connection
+- **Elastic:** Opensearch is polled for the health status of each index. If any indices are not reporting a “green” health status, this indicator will be in a yellow or warning state.
+- **Queues:** RabbitMQ queues are checked. Any queues containing more than 1000 messages are considered to be in an error state. Appliance Queue health is given in a yellow or warning status when any queues are in such an error state. In the Queues section further down the page you can see the individual Queues listed and which have messages piling up. When the appliance is unable to complete the check for any reason, this indicator will be in a red or error state
+
+### Health Levels
+
+Health levels provide a live representation of the current memory and CPU load on the appliance. Bear in mind that in an HA appliance, this data will be specific to the appliance node you happen to be accessing. By default, HPE Morpheus Enterprise does not include any endpoint or UI tool which can show you the currently used app node. However, a plugin has been developed which can surface this information if needed. See [this thread](https://discuss.morpheusdata.com/t/custom-ping-endpoint-via-morpheus-plugin/389) in the HPE Morpheus Enterprise official forums for additional details about accessing and using the plugin.
+
+- **Morpheus CPU:** Instantaneous amount of CPU capacity in use by HPE Morpheus Enterprise processes
+- **System CPU:** Instantaneous amount of CPU capacity in use by all processes
+- **Morpheus Memory:** Instantaneous amount of system memory currently in use by HPE Morpheus Enterprise processes (see the Knowledge Base article linked in the TIP box below for more information on how HPE Morpheus Enterprise claims and manages available memory)
+- **System Memory:** Instantaneous amount of total system memory currently claimed (this is commonly a high percentage, see the TIP box below)
+- **Used Swap:** Instantaneous amount of total available system swap in use
+- **Storage:** The instantaneous percentage utilization of the filesystem mounted at “/”
+
+TIP
+
+It’s common to see a high percentage of system memory being used [due to the way Morpheus allocates and manages memory](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US). If HPE Morpheus Enterprise is performing well, high system memory use is not necessarily an indicator that any action needs to be taken.
+
+### Additional System Health Indices
+
+CPU
+:   - Processor Count
+    - Process Time
+    - Morpheus CPU
+    - System CPU
+    - System Load
+
+MEMORY
+:   - Morpheus Memory
+    - Morpheus Used Memory
+    - Morpheus Free Memory
+    - Morpheus Memory Usage
+    - System Memory
+    - System Used Memory
+    - System Free Memory
+    - System Memory Usage
+    - System Swap
+    - Free Swap
+
+DATABASE
+:   - Lifetime Connections
+    - Aborted Connections
+    - Max Used Connections
+    - Max Connections
+    - Threads Running
+    - Threads Connected
+    - Slow Queries
+    - Temp Tables
+    - Key Reads
+    - Handler Reads
+    - Buffer Pool Free
+    - Open Tables
+    - Table Scans
+    - Full Joins
+    - Key Read Requests
+    - Key Reads
+    - Engine Waits
+    - Lock Waits
+    - Handler Reads
+    - Engine IO Writes
+    - Engine IO Reads
+    - Engine IO Double Writes
+    - Engine Log Writes
+    - Engine Memory
+    - Dictionary Memory
+    - Buffer Pool Size
+    - Free Buffers
+    - Database Pages
+    - Old Pages
+    - Dirty Page Percent
+    - Max Dirty Pages
+    - Pending Reads
+    - Insert Rate
+    - Update Rate
+    - Delete Rate
+    - Read Rate
+    - Buffer Hit Rate
+    - Read Write Ratio
+    - Uptime
+
+ELASTIC
+:   - Status
+    - Cluster
+    - Node Count
+    - Data Nodes
+    - Shards
+    - Primary Shards
+    - Relocating Shards
+    - Initializing
+    - Unassigned
+    - Pending Tasks
+    - Active Shards
+
+NOTE
+
+status is typical for Opensearch
+
+Elastic Nodes
+:   - Node
+    - Master
+    - Location
+    - Heap Usage
+    - Memory Usage
+    - CPU Usage
+    - 1M Load
+    - 5M Load
+    - 15M Load
+
+Elastic Indices
+:   - Health
+    - Index
+    - Status
+    - Primary
+    - Replicas
+    - Doc
+    - Count
+    - Primary
+    - Size
+    - Total Size
+
+Queues
+:   - Queue Count
+    - Busy Queues
+    - Error Queues
+
+## HPE Morpheus Enterprise Logs
+
+The HPE Morpheus Enterprise logs section aggregates appliance-specific logs into one list. If needed, users can export the logs by clicking EXPORT. This action triggers a download containing the last 10,000 log entries as a `.log` file.
+
+![../../_images/healthlogs.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3DA732C6-1956-4606-ADD4-153E80D23E9D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json b/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
new file mode 100644
index 0000000..4910798
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+  "title": "Networks",
+  "ordinal": 217,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.html",
+  "topic_cluster": {
+    "clustering_title": "Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479",
+        "clustering_title": "Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md b/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
new file mode 100644
index 0000000..a13f658
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9D8AB7AE-EC56-4637-BCD1-7B588E8BB479.md
@@ -0,0 +1,116 @@
+# Networks
+
+Infrastructure  >  Network  >  Networks
+
+## Overview
+
+The Networks section is for configuring networks across all clouds in HPE Morpheus Enterprise. Existing networks from Clouds added in HPE Morpheus Enterprise will auto-populate in the Networks section.
+
+Networks can be configured for DHCP or Static IP assignment, assigned IP pools, and configured for visibility and account assignment for multi-tenancy usage. Inactive Networks are unavailable for provisioning use. In addition, HPE Morpheus Enterprise allows administrators to restrict management of HPE Morpheus Enterprise-created Networks through Role permissions.
+
+## Configuring Networks
+
+### DHCP
+
+#### About this task
+
+To configure a network for DHCP:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, set the DHCP flag as Active (default)
+5. Save Changes
+
+#### Results
+
+IMPORTANT
+
+The DHCP flag tells HPE Morpheus Enterprise this network has a DHCP server assigning IP Addresses to hosts. HPE Morpheus Enterprise does not act as the DHCP server, and provisioning to a network that has the DHCP server flag active in HPE Morpheus Enterprise , but no DHCP server actually on the network will in most cases cause the instance to not receive an IP address.
+
+NOTE
+
+When selecting a network with DHCP enabled during provisioning, “DHCP” will populate to the right of the selected network:
+
+### Static and IP Pools
+
+#### About this task
+
+To configure a network for Static IP Assignment:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Search for the target network
+3. Edit the Network by either: 
+
+   - Select Actions  >  Edit
+   - Select the Network, then select Edit
+4. In the Network Config modal, add the following: 
+
+   - Gateway
+   - DNS Primary
+   - DNS Secondary
+   - CIDR ex 10.10.10.0/22
+   - VLAN ID (if necessary)
+   - Network Pool \* Leave as “choose a pool” for entering a static IP while provisioning \* Select a Pool to use a pre-configured HPE Morpheus Enterprise or IPAM Integration IP Pool
+   - The Permissions settings are used for Multi-Tenant resource configuration
+
+     - Leave settings as default if used in a single-tenant environment (only one Tenant in your HPE Morpheus Enterprise appliance)
+     - To share this network across all accounts in a multi-tenant environment, select the Master Tenant and set the Visibility to Public
+     - To assign this network to be used by only one account in a multi-tenant environment, select the account and set visibility to Private
+   - Active
+
+     - Leave as enabled to use this network
+     - Disable the active flag to remove this network from available network options
+5. Save Changes
+
+#### Results
+
+NOTE
+
+When selecting a network with DHCP disabled and no IP Pool assigned during provisioning, an IP entry field will populate to the right of the selected network(s):
+
+NOTE
+
+When selecting a network with an IP Pool assigned during provisioning, the name of the IP pool will populate to the right of the selected network(s). IP Pools override DHCP.
+
+### Advanced Options (Search Domains)
+
+Search domains are appended to DNS searches when a **non** fully qualified domain name (short name) is queried. Search domains can be entered as comma separated values, which will be added to DNS configurations, such as /etc/resolv.conf. These domains are injected through cloud-init or other method chosen for the virtual image.
+
+### Group and Tenant Access
+
+Networks can be configured to provide specific Group and Tenant access, if desired. **Group Access** controls which Groups at provision time will have access to the Network resource. Only workloads being provisioned to the selected Groups would have visibility into the Network. Workloads provisioned to other Groups would not see the Network as an available selection. **Tenant Permissions** control which Tenants may see the Network. Public visibility allows access to the Network for users in all Tenants (subject to additional RBAC controls) while Private visibility allows access only for selected Tenants. Select all that may apply.
+
+### Guest Console SSH Tunnel
+
+In some scenarios, instances that are segregated from the HPE Morpheus Enterprise appliance by port restrictions, or other mechanisms, can cause difficulties to access the guest console via the HPE Morpheus Enterprise web UI. Guest Console SSH Tunnel settings allow the administrator to configure a jump host’s settings that is dual-homed, accessible by HPE Morpheus Enterprise but also resides on the segregated network. When the guest console is configured with the SSH protocol, the traffic will be routed to the jump host, which will then relay to the target instance.
+
+GUEST CONSOLE JUMP HOST
+:   DNS hostname or IP of the jump host to relay the traffic
+
+GUEST CONSOLE JUMP PORT
+:   Port override, if different than 22 for SSH
+
+GUEST CONSOLE JUMP USERNAME
+:   Username used to authenticate to the jump host
+
+GUEST CONSOLE JUMP PASSWORD
+:   Password that is used with the username to autenticate to the jump host
+
+GUEST CONSOLE KEYPAIR
+:   Keypair saved in HPE Morpheus Enterprise to be used in lieu of, or in addition to, the password to the jump host, which is associated with the configured username Keypairs can be imported at: Infrastructure > Trust > Key Pairs
+
+### Subnets
+
+Subnet details can be viewed from the SUBNETS tab on the detail page of a specific network. From the SUBNETS tab, Morpheus allows the user to search and edit existing subnets.
+
+In an Azure VNet, you can also create new subnets with the +ADD button.
+
+![../../_images/create_subnet_421.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DAD09131-AC63-418D-9EE5-811611F8FB08-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json b/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
new file mode 100644
index 0000000..e95e532
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+  "title": "Archives",
+  "ordinal": 265,
+  "parent_title": "Tools",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.html",
+  "topic_cluster": {
+    "clustering_title": "Archives",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9DA820B7-7477-4980-848B-7161BDB5C43E",
+        "clustering_title": "Archives"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md b/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
new file mode 100644
index 0000000..8dd97d1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9DA820B7-7477-4980-848B-7161BDB5C43E.md
@@ -0,0 +1,53 @@
+# Archives
+
+## Overview
+
+Archives provides a way to store your files and make them available for download by your scripts and Users. Archives are organized by buckets and can be tied to any existing Bucket or File Share that may be currently integrated (for more on integrating new storage targets, see [storage documentation](https://docs.morpheusdata.com/en/latest/infrastructure/storage/storage.html)). Thus, storage buckets in public clouds, on networked storage, or even on the appliance itself may be used to host files.
+
+## Archives List Page
+
+To view or create Archives, navigate to Tools > Archives. At the Archives list page is a list of all currently-configured Archives. From the list view, the following details about each Archive are shown:
+
+- **NAME:** The name for the Archive in HPE Morpheus Enterprise
+- **BUCKET:** The integrated bucket or file share where files in this Archive are stored
+- **# Files:** The number of files in the Archive
+- **SIZE:** The total size of all files in the Archive
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants listed here have access to the Archive
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **PUBLIC URL:** Indicates whether HPE Morpheus Enterprise is automatically generating a public download URL for files in this Archive
+- **ACTIONS:** Within the ACTIONS menu users may download a ZIP folder containing all files in the Archive, edit the Archive, or remove it
+
+![../_images/archivelist.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C069FB35-5152-45DA-B2FE-5C7DDE5F3563-high.png)
+
+## Adding an Archive
+
+To add a new Archive, click + ADD from the Archives list page. Configure the following:
+
+- **NAME:** A friendly name for the Archive in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the Archive
+- **BUCKET:** Select an existing bucket or file share to store files in for this Archive. To integrate a new bucket or file share to use for an Archive, navigate to Infrastructure > Storage
+- **VISIBILITY:** Public or Private, public Archives are available in all Tenants
+- **TENANTS:** When Archive visibility is set to Private, only the Tenants selected will have access to the Archive
+- **PUBLIC URL:** When marked, HPE Morpheus Enterprise will create a public download URL for all files in the Archive
+
+WARNING
+
+Be sure that no sensitive data will be stored in the Archive if it will be configured to generate public URLs. Anyone with the public URL will be able to download the file without authentication.
+
+Once done, click SAVE CHANGES
+
+## Archive Detail Page
+
+The Archive detail contains information about the Archive configuration as well as a list of files currently stored in the Archive. The Archive detail is accessed by navigating to the Archives list page (Tools > Archives) and selecting an existing Archive. As on the Archives List Page, users can download a ZIP folder containing all files in the Archive and edit the Archive from the ACTIONS menu.
+
+To delete the Archive, click DELETE. New files are added by clicking + ADD. When adding a new file, users may browse the file system on the local computer to select a file.
+
+From the files list, download or delete individual files by clicking on the appropriate selection from the ACTIONS menu.
+
+![../_images/archivedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3A823ED0-F545-4405-AC60-EAF927081936-high.png)
+
+## File Detail Page
+
+The File Detail Page contains details about the file itself as well as private and public (if available) URLs. In the lower section are three tabs. The Links tab contains any download links which have been generated (both active and expired). The History tab contains historical information about the file including creation and deletion of download links and download events. The scripts tab contains a guide for getting started using Archive-stored files in scripts.
+
+![../_images/filedetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json b/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
new file mode 100644
index 0000000..ca14fdf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+  "title": "Apps",
+  "ordinal": 87,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md b/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
new file mode 100644
index 0000000..db4981b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.md
@@ -0,0 +1,10 @@
+# Apps
+
+Apps allow instances having general relationships to be grouped in a clean and organized manner. App functionality enables full control of which instances belong in an app as well setting Firewall and Access Control List (ACL) rules. Use Apps to structure all necessary components into a single place. Add checks and groups for web servers, database nodes, etc.
+
+Apps can be created from Blueprints, which are made in Library > Blueprints > App Blueprints or from Existing Apps.
+
+**Subtopics**  
+
+- **[Creating Apps](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html)**
+- **[Managing Apps](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-643C0C8E-E6AF-43C6-94CE-693C11FA8AF1.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json b/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
new file mode 100644
index 0000000..5414786
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+  "title": "Migrations Requirements",
+  "ordinal": 269,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9EC70919-852C-427E-ACDF-D59319D72468.html",
+  "topic_cluster": {
+    "clustering_title": "Migrations Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9EC70919-852C-427E-ACDF-D59319D72468",
+        "clustering_title": "Migrations Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md b/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
new file mode 100644
index 0000000..de3253d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9EC70919-852C-427E-ACDF-D59319D72468.md
@@ -0,0 +1,24 @@
+# Migrations Requirements
+
+This section contains requirements and recommendations that will ensure migrations run successfully. Keep an eye on this section as some requirements will change as this feature is updated over time to become more flexible.
+
+General Requirements
+:   - HVM Hosts must be upgraded to Agent version 2.10.0 at minimum. To upgrade the HVM Host Agent, navigate to the host detail page, open the ACTIONS menu, and select "Upgrade Agent." If this is unsuccessful, you may instead select "Download Agent Script" to download a shell script which may be run manually on the HVM Host. These download scripts are specific to the HVM Host so an individual install script would need to be downloaded for each HVM Host and run on the correct HVM Host.
+    - HVM Hosts must be able to reach ESXi hosts and vCenter on the target VMware vCenter Cloud via the Management Network
+    - The source VMs must be running for the preparation phase of the migration to complete successfully. If VMs are not running, they will automatically be restarted
+
+First Release Requirements
+:   This section includes requirements for the current version of the migration feature which are subject to change and improvement as road-mapped enhancements are included with subsequent versions of the product.
+
+    - If the target datastore is GFS2 or NFS, migrations will be "thin" QCOW2 rather than "thick" to reduce overhead and on-disk footprint. Other target datastore types must have enough "thick" space for each VM
+    - VMs will power down prior to the transfer meaning service of the source workload will be disrupted during the transfer
+    - VirtIO / VirtIO-SCSI target storage must be supported by the source VM
+    - Currently supported operating systems: RedHat, CentOS, Rocky, Alma, SUSE, Ubuntu, Debian, Windows (currently requires manual preparation steps described below)
+    - Source VMs must be capable of getting the `qemu-guest-tools` or `qemu-guest-agent` package installed.
+    - RDM (Raw Device Mappings) are not yet supported
+    - Source VMs must not have any attached ISOs or cdroms. These are not supported and the migration will fail.
+
+Recommendations
+:   - Batch limits and bandwidth limitations testing is still in progress. It's currently recommended you migrate no more than 20 VMs at a time. Testing is still ongoing to determine the upper limits of migrations and this recommendation is likely to increase over time
+    - Begin using this feature with a smaller migration than the limit to make sure your workloads are moving correctly
+    - When migrating to NFS-backed datastores, setting `async` on the NFS server may improve performance
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json b/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
new file mode 100644
index 0000000..35b5dfc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+  "title": "Bluecat",
+  "ordinal": 514,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html",
+  "topic_cluster": {
+    "clustering_title": "Bluecat",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9ECF72A1-9565-4202-A087-82313C2F8D58",
+        "clustering_title": "Bluecat"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md b/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
new file mode 100644
index 0000000..a7e0024
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.md
@@ -0,0 +1,58 @@
+# Bluecat
+
+## Overview
+
+HPE Morpheus Enterprise integrates with Bluecat IPAM to scope pools to networks for static IP assignment from Bluecat to your HPE Morpheus Enterprise Instances.
+
+## Adding Bluecat to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select Bluecat
+4. Enter in the following information 
+
+   Name
+   :   Name of the Bluecat Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Uncheck to disable sync with the Bluecat endpoint
+
+   URL
+   :   URL of the Bluecat server, ex: `http://10.30.20.10`
+
+   Username
+   :   Username of Bluecat API User. API and root level propagating read access required, read/write access required for target Networks and Domains.
+
+   Password
+   :   Bluecat User password
+
+   Network Filter
+   :   Optionally enter a comma-separated list of `entityIds` for config(s), block(s) or network(s) (ex. `entityId1,entityId2...`) to filter the synced IP pools, networks and domains
+5. Click SAVE CHANGES
+
+### Results
+
+The Bluecat Integration will be saved, IP pools will sync in and populate under Infrastructure  >  Network  >  IP Pools, and Domains will populate in Infrastructure  >  Network  >  Domains. Pools and Domains can also be found in the Bluecat Integration details page, which can be accessed by clicking on the name of the added Bluecat Integration in Infrastructure  >  Network  >  Services.
+
+IMPORTANT
+
+Quick Deployments must be enabled in Bluecat for HPE Morpheus Enterprise to create instantly available DNS records when using Bluecat DNS.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available Bluecat IP in an IP/Network Pool and create the corresponding DNS records, as well as remove the records upon teardown. To enable this, add an Bluecat IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to `Infrastructure - Network- Networks`
+2. Select a Network name and EDIT, or select ACTIONS - Edit
+3. In the NETWORK POOL section, search for and select the name of the IP/Network Pool. 
+
+   - Gateway, DNS and CIDR must be populated for static/pool IP assignment
+   - Select Allow IP Override to allow selecting between DHCP, Static entry and Pool Selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json b/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
new file mode 100644
index 0000000..5f7ab3f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+  "title": "Using Volume",
+  "ordinal": 448,
+  "parent_title": "Volume Consumption",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html",
+  "topic_cluster": {
+    "clustering_title": "Using Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2",
+        "clustering_title": "Using Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md b/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
new file mode 100644
index 0000000..3a3a55c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.md
@@ -0,0 +1,14 @@
+# Using Volume
+
+## About this task
+
+Perform the following to use the configured volume:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Click Add.
+3. After selecting the HPE BareMetal ILO server for type and specifying the cloud, group, and a name for the instance, click Next to advance to the Configure section.
+4. Click on the + sign next to Volumes to add a volume to this instance.
+5. Specify a name for the volume, desired size, volume type to indicate whether it is a replicated volume or not, the datastore to create it in, and whether it’s a shared volume.   
+   ![Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-090D059F-2321-4377-B832-EEAF50ED173E-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json b/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
new file mode 100644
index 0000000..cd7c4f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+  "title": "Creating Policies",
+  "ordinal": 318,
+  "parent_title": "Policies",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48",
+        "clustering_title": "Creating Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md b/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
new file mode 100644
index 0000000..67f62e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.md
@@ -0,0 +1,80 @@
+# Creating Policies
+
+Policies can be created in three different locations.
+
+- Administration > Policies
+- Infrastructure  >  Groups  >  Group  >  Policies
+- Infrastructure  >  Clouds  >  Cloud  >  Policies
+
+Policies can be disabled and re-enabled at anytime.
+
+IMPORTANT
+
+Precedence is applied to matching or conflicting Policies in the following order: Cloud > Group > Role > User > Global.
+
+## To create a Global Policy:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under Filter next to scope select Global
+5. Select SAVE CHANGES
+
+## To create a Policy for a User:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select User a drop down menu will appear below allowing you to select a user
+5. Select SAVE CHANGES
+
+## To create a Policy for a Role:
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD Policy and choose from the available policy types.
+3. Refer to Policy Type sections below for Configuration options.
+4. Under filter next to scope select Role a drop down menu will appear below allowing you to select a Role
+5. For `APPLY INDIVIDUALLY TO EACH USER IN ROLE`
+   :   - Select for Max Resource/Quota Policies to be calculated per user
+       - Leave unselected to calculate by total usage of all users within that Role.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Cloud:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Cloud the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created or moved into the Group after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select a Cloud by clicking on the name of the Cloud to go to the Cloud Detail page.
+3. Select the `POLICIES` tab in the Cloud Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Type sections below for Configuration options.
+6. Select SAVE CHANGES
+
+## To create a Policy for a Group:
+
+### About this task
+
+NOTE
+
+Resource Limitation Policies apply to all Instances in the Group the Policy is added to. Approval, Naming, Power, Shutdown and Expiration Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Select a Group by clicking on the name of the Group to go to the Group Detail page.
+3. Select the `POLICIES` tab in the Group Detail page.
+4. Select + ADD and choose from the available policy types.
+5. Refer to Policy Types sections below for Configuration options.
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json b/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
new file mode 100644
index 0000000..de17b20
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+  "title": "Workloads: Instance Type Usage",
+  "ordinal": 67,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Type Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F78ED42-26BC-405F-88BC-3B14279A3306",
+        "clustering_title": "Workloads: Instance Type Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md b/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
new file mode 100644
index 0000000..0d1a6ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Type Usage
+
+![../_images/9instancetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Instance Type Usage dashboard organizes workloads meeting dashboard filters by their Instance type. In additional to counts, administrators can view resource consumption and cost figures by Instance type groupings as well.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance type name (all matching search terms, Morpheus-default Instance types are not included when using the search filter)
+- Metric (apply to see the top Instance types by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **TYPES:** The total number of Instance types represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Type Usage List
+
+Each Instance type represented in the dashboard is listed below the graph. For each Instance type shown, we see the number of Groups the Instance type is represented in, the number of Clouds the Instance type has been provisioned into, and the total amount of memory allotted to workloads of each Instance type.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json b/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
new file mode 100644
index 0000000..4b6df73
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+  "title": "Data Encryption",
+  "ordinal": 36,
+  "parent_title": "Additional Configuration Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.html",
+  "topic_cluster": {
+    "clustering_title": "Data Encryption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4",
+        "clustering_title": "Data Encryption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md b/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
new file mode 100644
index 0000000..5905180
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-9F8A2061-C5F1-4549-A7CC-C62094441FA4.md
@@ -0,0 +1,69 @@
+# Data Encryption
+
+By default, Morpheus encrypts sensitive data in the Database using AES encryption mode with GCM. Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files such as `morpheus-secrets.json` and `morpheus.rb` are in plain text as they are only accessible by root.
+
+Passwords and other strings in HPE Morpheus Enterprise Appliance configuration files can be set to an encrypted string using the HPE Morpheus Enterprise crypto utility to generate ENC strings and then using `ENC(string)` as the value in the configuration file.
+
+Additionally a custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 hash, which is used to generate the AES encryption key.
+
+## Generate ENC Strings for morpheus-secrets.json
+
+### About this task
+
+System generated passwords are set in `/etc/morpheus/morpheus-secrets.json`. These entries can be updated to ENC strings with the following steps:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string migrate` which will output ENC() strings for the passwords in morpheus-secrets.json
+2. Update the desired password strings in the `morpheus-secrets.json` config file with the matching ENC() string.
+3. Save `morpheus-secrets.json`
+4. Run `morpheus-ctl reconfigure`
+
+## Generate ENC Strings for custom morpheus.rb entries
+
+### About this task
+
+ENC() strings can be generated for sensitive data set in morpheus.rb, such as the password to an external service.
+
+To generate ENC(0) strings for morpheus.rb entries:
+
+### Procedure
+
+1. On the HPE Morpheus Enterprise appliance, run `morpheus-ctl get-crypto-string string $clear_text '$suffix'` which will output strings for the passwords in morpheus-secrets.json 
+
+   - Replace `$clear_text` with the string to be encrypted
+   - If a suffix is defined in morpheus.rb (as described in the next section), replace `$suffix` with your suffix.
+
+   NOTE
+
+   It is advisable to disable bash history logging by running `unset HISTFILE` before running the morphesu-ctl get-crypto-string command and then `set HISTFILE=$HOME/.bash_history` to reenable.
+2. Update the desired password strings in the `morpheus.rb` config file with the matching string output, using `ENC($output)` format 
+
+   - Example: `mysql['morpheus_password'] = 'ENC($ZI5DnaO0quhxKe$kDFD+U2ZeJUuYiNC$F1+czPNyo+3lAdq7V0gcrWwHnkINYqr13cUGrDVyog==)'`
+3. Save `morpheus.rb`
+4. Run `morpheus-ctl reconfigure`
+
+## Encrypted Key Suffix
+
+### About this task
+
+A custom Encryption Key Suffix can be set in the morpheus.rb configuration file. This suffix will be combined with a system string to generate a SHA-256 Hash, which is used in the generation of the system AES encryption key.
+
+DANGER
+
+Setting a custom Encryption Key Suffix affects all data encrypted by HPE Morpheus Enterprise, including database and cypher data. Encryption Key Suffix is required in the event data needs to be migrated or recovered. Once the Encryption Key Suffix is set, data cannot be recovered without it. Store any Encryption Key Suffix externally where it can be referenced for future scenarios.
+
+IMPORTANT
+
+The Encryption Key Suffix cannot be changed or removed after being set. Changing or removing an existing Encryption Key Suffix will prevent data access. If an existing suffix is altered in the morpheus.rb file, it must be restore to its original value.
+
+### Procedure
+
+1. Add `app['encryption_key_suffix'] = '$suffix'` to `/etc/morpheus/morpheus.rb`, replacing `$suffix` with your suffix. 
+
+   DANGER
+
+   Once an Encryption Key Suffix is set and applied via reconfigure, it cannot be altered or removed and data cannot be migrated or recovered without it.
+2. Run `morpheus-ctl reconfigure` 
+
+   - Reconfigure will generate a new encryption key using the suffix and set (ENC) values for the service password in application.yml
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json b/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
new file mode 100644
index 0000000..ae1d8e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+  "title": "Integrating Hashicorp Vault",
+  "ordinal": 239,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html",
+  "topic_cluster": {
+    "clustering_title": "Integrating Hashicorp Vault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A0DC9F48-028D-4283-8572-FDD0A432E125",
+        "clustering_title": "Integrating Hashicorp Vault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md b/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
new file mode 100644
index 0000000..ee8c9e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.md
@@ -0,0 +1,27 @@
+# Integrating Hashicorp Vault
+
+The Hashicorp Vault integration is not included with HPE Morpheus Enterprise by default. Download the plugin from HPE Morpheus Enterprise [Exchange](https://share.morpheusdata.com/) and add the plugin to HPE Morpheus Enterprise through the [Plugins](https://docs.morpheusdata.com/en/latest/administration/integrations/integrations.html#plugins) section. This allows users to store credential sets completely outside of HPE Morpheus Enterprise and in Hashicorp Vault, which may be required by your organization’s IT policies.
+
+NOTE
+
+The plugin space is universal and not specific to Tenants. If Subtenant users have access to Administration > Integrations > Plugins, any integrated plugins will be available in all Tenants across the appliance. In most cases, it makes sense to restrict access to this section from Subtenant users through the associated Tenant Role. Instead integrate plugins from the Primary Tenant and expose them to various Subtenants as needed.
+
+Once downloaded, plugins are added to HPE Morpheus Enterprise in Administration > Integrations > Plugins. Simply browse your local filesystem for the JAR file downloaded from HPE Morpheus Enterprise Exchange and its capabilities will immediately be added to the appliance. After adding the plugin, configure access for the plugin to your Vault server. Do this by clicking the Edit (pencil) button in the row for the Vault plugin. Supply a URL for your Vault server and an access token, then save your changes.
+
+NOTE
+
+When creating a Vault integration, it’s recommended that you use a long-lived token. If the token suddenly becomes invalid, HPE Morpheus Enterprise will be unable to write new credential sets to Vault and will be unable to edit or delete any existing ones. Additionally, you won’t be able to use Vault-stored credential sets elsewhere in HPE Morpheus Enterprise, such as when creating new Cloud integrations or populating REST-based Option Lists which require authentication. Should this happen, simply obtain a new token, edit the Vault integration, update the token, and save your changes.
+
+With the plugin added, a new integration type will appear in Infrastructure > Trust > Integrations. Click + ADD, then “Hashicorp Vault Credentials” to get started. The fields in the list below are available for configuration but it’s possible that no configuration will be necessary. If you do not enter a new API URL and TOKEN value, these are taken from the plugin configuration set a moment ago. Similarly, The Vault Secret Engine and Secret Path can be left at default values (or empty) if those values are acceptable. If you need to override the defaults or the URL/token set on the plugin, you may do so here.
+
+- **NAME:** A friendly name for the Vault integration in HPE Morpheus Enterprise
+- **ENABLED:** When marked, this Vault integration will be available to have credentials written to it
+- **API URL:** The URL for the Vault server (ex. <http://xx.xx.xx.xx:8200>)
+- **TOKEN:** A valid API token for the server (see note below)
+- **HASHICORP VAULT SECRET ENGINE:** Select KV Engine version 1 or 2, additional engines may be available in the future
+- **ENGINE MOUNT:** If desired, enter a custom engine mount. By default, if left empty, credentials are written to the “secret/” engine mount
+- **SECRET PATH:** If desired, enter a custom path and HPE Morpheus Enterprise will write new credential sets to that path. By default, if left empty, new credentials are written to “morpheus-credentials/”
+
+When done, click SAVE CHANGES.
+
+With the above process finished, this Vault integration will be available as a storage target when creating new credential sets. In Infrastructure > Trust > Credentials, after clicking + ADD and selecting the type of credential set to add, select the new Vault integration in the CREDENTIAL STORE field (default selection is “Internal”).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json b/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
new file mode 100644
index 0000000..d368125
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+  "title": "UpCloud",
+  "ordinal": 473,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.html",
+  "topic_cluster": {
+    "clustering_title": "UpCloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC",
+        "clustering_title": "UpCloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md b/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
new file mode 100644
index 0000000..8b66f6a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A148BEB8-9553-44A9-8FCD-77C4BDD62ABC.md
@@ -0,0 +1,264 @@
+# UpCloud
+
+## Overview
+
+UpCloud is a cloud hosting provider that offers both Linux and Windows virtual machines on their MAXIOPS infrastructure which is billed as I.A.A.S ( infrastructure-as-a-service ). They have datacenters based in the UK, USA, Germany, Netherlands, Singapore and Finland. Servers can be created a lightning fast 45 seconds with their faster than SSD technology.
+
+## Features
+
+- Virtual Machine Provisioning
+- Containers
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Inventory
+- Cloudinit
+
+## Requirements
+
+### About this task
+
+An UpCloud User with API, Server and Storage permissions is required.
+
+To enable API access for a Main Account UpCloud User:
+
+### Procedure
+
+1. Login to UpCloud
+2. Select My Account  >  User Accounts
+3. Select Change on the target user
+4. Check the box for API connections: Allow API connections from
+5. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+6. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+7. Save
+
+### Results
+
+To Enable API, API, Server and Storage permissions for a SubAccount User:
+
+When creating or editing a Sub Account UpCloud user:
+
+1. Check the box for API connections: Allow API connections from
+2. Under Access Permissions  >  Allow access to individual servers, check the box for User has control access to all servers.
+3. Under Access Permissions  >  Allow control access to individual storages, check the box for User has control access to all storages
+4. Save
+
+## Adding an UpCloud Cloud
+
+### Configure
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud Button
+3. Select UpCloud from the Add Cloud modal
+4. Select NEXT
+5. Enter the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   USERNAME
+   :   UpCloud User Account Username
+
+   PASSWORD
+   :   UpCloud User Account Password
+
+   ZONE
+   :   Select UpCloud Datacenter to scope cloud to
+
+   INVENTORY
+   :   - Off: Existing UpCloud Servers will not be inventoried in HPE Morpheus Enterprise
+       - Basic: Existing Servers are Inventoried with Power state, Memory and Cores statistics synced.
+       - Full: Existing Servers are Inventoried with Power state, Memory and Cores statistics, plus IP Addresses, Storage Info, and Console VNC Information.
+
+   NOTE
+
+   Full Inventory level recommended. Basic Inventory level can reduce Cloud Sync times when inventorying Datacenters with large amounts of servers. Credentials need to be added by editing the Virtual Machine in order to connect.
+
+   The Cloud can now be added to a Group or configured with additional Advanced options.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+### Group
+
+A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+- USE EXISTING: Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+- CREATE NEW: Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+
+### Review
+
+Confirm all settings are correct and select COMPLETE.
+
+The UpCloud Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of:
+
+- UpCloud Servers will added as Virtual Machines (if Inventory is enabled)
+- UpCloud Templates (My Templates) will sync and be added to Library > Virtual Images.
+
+NOTE
+
+The Console tab will only appear for Inventoried Servers if Inventory Level is set to Full
+
+## Provisioning to UpCloud
+
+Instances and Apps can be created using the private Images synced from UpCloud or from the HPE Morpheus Enterprise provided Image Catalog.
+
+## Provision a synced Image
+
+Images synced from UpCloud can be provisioned by using:
+
+- The UPCLOUD Instance Type and selecting the Image from the Image dropdown in the configure section when provisioning and Instance, App, or creating an App Blueprint.
+- Creating custom Library Instance Types and selecting a synced Image when creating a Node Type for the custom Instance Type.
+
+IMPORTANT
+
+Synced images should be configured prior to provisioning by editing the Image in the Library > Virtual Images section.
+
+## Provision a HPE Morpheus Enterprise provided UpCloud Image
+
+HPE Morpheus Enterprise provides a number of pre-configured Images that are available in the default HPE Morpheus Enterprise Catalog when provisioning and Instance, App, or creating an App Blueprint. UpCloud Images are included in the following Instance Types in the default HPE Morpheus Enterprise catalog.
+
+- ACTIVEMQ
+- APACHE
+- CASSANDRA
+- DEBIAN
+- ELASTICSEARCH
+- GRAILS
+- JAVA
+- MONGO
+- MYSQL
+- NGINX
+- PHP
+- RABBITMQ
+- REDIS
+- OMCAT
+- UBUNTU
+- WINDOWS
+- GRAILS
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json b/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
new file mode 100644
index 0000000..528bcbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+  "title": "Layouts",
+  "ordinal": 129,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.html",
+  "topic_cluster": {
+    "clustering_title": "Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0",
+        "clustering_title": "Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md b/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
new file mode 100644
index 0000000..c1aa3e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A1BFF247-858B-4915-BBF1-FC8CDEA5C8F0.md
@@ -0,0 +1,94 @@
+# Layouts
+
+Layouts are attached to Instance Types. A Layout can only be attached to a single Instance Type and a single Technology. An Instance Type can have one or many Layouts attached to it, allowing for a single Instance Type to work with any Technology type. Node Types are added to Layouts. A Layout can have one or many node types attached to it. Node types can be shared across Layouts of matching Technology types.
+
+IMPORTANT
+
+Once an Instance Type is defined on a Layout and saved, the Instance Type setting and Technology selections on the Layout cannot be changed.
+
+## Layout List View
+
+The default page for Layouts is the Layout list view. Select + ADD to create a new Layout. Layouts can also be created from an Instance Type detail page.
+
+The following fields are displayed for each Layout:
+
+- **INSTANCE TYPE:** Select the Instance Type to associate with the Layout. This attribute is automatically set and not shown when creating the Layout from an Instance Type detail page
+- **NAME:** Links to the Layout detail page
+- **VERSION**
+- **DISPLAY ORDER:** Determines the Layout display order in the provisioning wizard when adding an Instance of the associated Instance Type
+- **DESCRIPTION**
+
+NOTE
+
+The order of Layouts given when an Instance Type is being provisioned is in high-to-low order of the Layout Display Order property. Bear in mind this is reversed from how Service Plans are ordered, which is in low-to-high order based on the Display Order value.
+
+The Actions menu in each row reveals the following options:
+
+- **Permissions:** Scope the Layout to Group(s) to narrow the list of available groups for a chosen Instance Type at provision time
+- **Edit:** Edit the Layout
+- **Delete:** Delete the Layout
+
+NOTE
+
+A Layout that is in use cannot be deleted.
+
+Available Filters:
+
+- **Technology:** Display Layouts by selected Cloud technology
+- **Instance Type:** Display Layouts by the associated Instance Type
+
+## Layout Detail View
+
+The Layout Detail view shows details on the Layout including Name, Short Name, Version, and Category. It also lists all associated Node Types.
+
+- Select a Layout Name from the list page or Instance Type detail page to get to a Layout detail page.
+
+## Layout Configuration Options
+
+Instance Type
+:   Select the Instance Type to add to the new Layout. Custom Instance Types must already be created and one Layout cannot be added to multiple instance types. The Instance Type also cannot be changed after creation.
+
+    NOTE
+
+    Layouts cannot be added to Morpheus pre-defined Instance Types
+
+Name
+:   The name the Layout presents as in the Configuration Options dropdown of the provisioning wizard
+
+Version
+:   The version number or name for the Layout. Layouts in an Instance Type with the same version will all show under the Configuration Options dropdown when that version is selected while provisioning
+
+Description
+:   Description of the Layout, viewable on the Layout list view
+
+Creatable
+:   When checked, this Layout will be selectable at provision time for the associated Instance Type (assuming the Layout is otherwise compatible with provisioning conditions). Instance Types with no Creatable Layouts will not be selectable from the provisioning wizard
+
+Technology
+:   Technology determines which Cloud this layout will be available for and which Node Types can be added to it
+
+Minimum Memory
+:   Defines the minimum amount of memory required for this Layout. Only Service Plans that meet the defined memory minimum will be available during provisioning when this Layout is selected. Custom memory values must also meet this minimum. Entering a minimum memory value of zero (the default value) indicates no minimum. This minimum memory value will override any Virtual Image minimum memory requirements
+
+Workflow
+:   Select a Workflow which will be associated as the Provisioning Workflow for Instances provisioned using this Layout. If a Workflow is defined, it is not shown to the user at provision time and will be run in addition to any Workflows set on the Instance Type, in Workflows Policies, defined in App Blueprints, or selected manually at provision time.
+
+Supports Convert to Managed
+:   Enabled to allow users to select this layout when converting a Discovered workload to Managed
+
+Enable Scaling (Horizontal)
+:   Enables Instances with this layout to use scaling features
+
+Environment Variables
+:   Custom environment variables to be added to the Instance when provisioned
+
+Inputs
+:   Search for and select one or multiple Inputs to add to the Layout. Inputs (except for Hidden Inputs) will appear in Provisioning, App, Blueprint, and Cloning wizards when this layout is selected
+
+Nodes
+:   Single or multiple nodes can be added to a Layout by searching for and selecting the Node(s)
+
+Price Sets
+:   Associate a Price Set with the Layout, Price Sets are created in Administration > Plans & Pricing > Price Sets. Price Sets which are added to Layouts become additive with any pricing which may apply on the Service Plan. For example, a “fixed” Price Set of $1000/month has been associated with the Layout. If this Layout is provisioned to an Amazon AWS Cloud, the additional fixed price would be computed along with any Price which is pre-existing on the AWS Service Plan
+
+    **Layout Price Sets Demo**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json b/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
new file mode 100644
index 0000000..1acb2fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+  "title": "Supported Software Versions",
+  "ordinal": 397,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.html",
+  "topic_cluster": {
+    "clustering_title": "Supported Software Versions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110",
+        "clustering_title": "Supported Software Versions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md b/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
new file mode 100644
index 0000000..11461cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A1E36C88-9447-4A8E-814F-A3DBB8DD4110.md
@@ -0,0 +1,15 @@
+# Supported Software Versions
+
+**Required Software**
+
+Ensure your environment uses the following software versions before you proceed. Features and behavior may vary across different releases.
+
+- HPE Morpheus Enterprise: Version 8.1.0
+- HPE BMaaS: Version 1.0.0
+
+**Managed Networking and External Storage Requirements**
+
+Install the following integrations only if your environment requires managed networking or external storage:
+
+- HPE ArubaCX Network Integration: Version 1.9.0
+- HPE Alletra MP Integration: Version 1.9.0
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.json b/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
new file mode 100644
index 0000000..310069b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+  "title": "CentOS/RHEL 7 Images",
+  "ordinal": 50,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A2766933-3113-44EF-8458-88636F4301B3.html",
+  "topic_cluster": {
+    "clustering_title": "CentOS/RHEL 7 Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A2766933-3113-44EF-8458-88636F4301B3",
+        "clustering_title": "CentOS/RHEL 7 Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.md b/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
new file mode 100644
index 0000000..256607e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A2766933-3113-44EF-8458-88636F4301B3.md
@@ -0,0 +1,3 @@
+# CentOS/RHEL 7 Images
+
+For custom CentOS 7 images we highly recommend setting up Cloud-Init and fixing the network device names. More information for custom CentOS images can be found in the CentOS 7 image guide.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json b/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
new file mode 100644
index 0000000..07f3f9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+  "title": "Distributed Workers",
+  "ordinal": 314,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.html",
+  "topic_cluster": {
+    "clustering_title": "Distributed Workers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF",
+        "clustering_title": "Distributed Workers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md b/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
new file mode 100644
index 0000000..b35dd77
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A306B71B-A1BD-449B-AD1C-6EE4E8462ECF.md
@@ -0,0 +1,146 @@
+# Distributed Workers
+
+## Overview
+
+The HPE Morpheus Enterprise distributed worker is installed using the same package as the VDI Gateway worker. Organizations which have already deployed VDI Gateway(s) can use the same worker for both purposes if desired, you’d simply need to update configuration in `/etc/morpheus/morpheus-worker.rb` and run a reconfigure. When creating a distributed worker or VDI Gateway object in HPE Morpheus Enterprise UI, an API key is generated. Adding one or both types of API keys to the worker configuration file determines if the worker is running in VDI gateway and/or distributed worker mode.
+
+### Supported Cloud Types
+
+The following Cloud/Zone types support Distributed Workers
+
+- vmware
+- vmwareCloudAws
+- nutanix
+- openstack
+- xenserver
+- macstadium
+
+## Installation
+
+A distributed worker VM is installed and configured similarly to a HPE Morpheus Enterprise appliance via `rpm` or `deb` package.
+
+NOTE
+
+Package URLs for the distributed worker are available at <https://app.morpheushub.com> in the downloads section.
+
+NOTE
+
+The distributed worker requires that the HPE Morpheus Enterprise appliance has a trusted SSL certificate. This can be accomplished by configuring a public trusted SSL certificate on the HPE Morpheus Enterprise appliance (or load balancer) or ensure the certificate and chain are added to the Java Keystore of the Distributed Worker to trust the certificate.
+
+### Requirements
+
+Table 1. Supported Operating Systems
+
+    | OS | Version(s) |
+| --- | --- |
+| Amazon Linux | 2 |
+| CentOS | 7.x, 8.x |
+| Debian | 11, 12 |
+| RHEL | 7.x, 8.x |
+| SUSE SLES | 12 |
+| Ubuntu | 18.04, 20.04, 22.04 |
+
+- **Memory:** 4 GB RAM minimum recommended
+- **Storage:** 10 GB storage minimum recommended. Storage is required for installation packages and log files
+- **CPU:** 4-core minimum recommended
+- Network connectivity **to** the HPE Morpheus Enterprise appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise worker package
+- Access to base `yum` or `apt` repos. Access to Optional RPM repos may be required for RPM distros
+
+IMPORTANT
+
+In order to proxy VMware vCenter Cloud traffic through a Distributed Worker, you must have a static public DNS entry for the internal IP address of the vCenter appliance. If this is not done, everything may appear to be working properly when configuring the Cloud but problems will arise at provision time. This is not a HPE Morpheus Enterprise limitation but is a limitation of the VMware SDK client which does not natively support proxies.
+
+Download the appropriate package from HPE Morpheus Enterprise Hub based on your target Linux distribution and version for installation in a directory of your choosing. The package can be removed after successful installation.
+
+```
+```
+wget https://www.hpe.com/support/hpesc/path/to/morpheus-worker-$version.distro
+```
+```
+
+Validate the package checksum as compared with the values indicated on Hub. For example:
+
+```
+```
+sha256sum morpheus-worker-$version.distro
+```
+```
+
+Next, install the package using your selected distribution’s package installation command and your preferred options. Example, for RPM:
+
+**rpm**:
+
+```
+```
+$ sudo rpm -ihv morpheus-worker-$version.$distro  
+Preparing...                          ################################# [100%]  
+Updating / installing...  
+   1:morpheus-worker-x.x.x-1.$distro    ################################# [100%]  
+Thank you for installing Morpheus Worker!  
+Configure and start the Worker by running the following command:  
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+## Configuration
+
+With the package installed, we need to add a new distributed worker in HPE Morpheus Enterprise UI. Distributed workers are added in Administration > Integrations > Distributed Workers. To create one, populate the following fields:
+
+- **NAME:** A name for the distributed worker in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the distributed worker
+- **PROXY HOSTS:** A comma-delimited list of global proxy hosts, any endpoint listed here will be proxied through the HPE Morpheus Enterprise worker. For VMware, you must list the host addresses for any vCenter you wish to proxy through the worker. Xen hosts and PowerVC hosts must be listed here as well. Other Cloud types which are supported by the HPE Morpheus Enterprise worker need only have the worker configured on the Edit Cloud modal (Infrastructure > Clouds > Selected Cloud > Editbutton)
+- **ENABLED:** When marked, the selected worker is available for use
+
+IMPORTANT
+
+The proxy host URL entered in the Worker configuration must match the URL set in the Cloud configuration. That is, if you use the URL in the Cloud configuration you must also use it in the Worker configuration. The reverse is also true, if an IP address is used in the Cloud configuration, that should be used in the Worker configuration as well. There are also configuration considerations that must be made for proxying vCenter Cloud traffic through a Distributed Worker. See the “IMPORTANT” box in the “Requirements” section for additional details.
+
+After clicking SAVE CHANGES, an API key is generated and displayed. Make note of this as it will be needed in a later configuration step.
+
+![../../_images/createWorker.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C9464126-F50C-4309-9A8F-892576EBC646-high.png)
+
+With the worker configured in HPE Morpheus Enterprise, the next step is to update supported Cloud integrations which should be proxied through the worker. Select the desired Cloud from the Clouds List Page (Infrastructure > Clouds) and click EDIT from the chosen Cloud’s Detail Page. Within the Connection Options section, choose a configured worker from the WORKER dropdown menu. Click SAVE CHANGES.
+
+![../../_images/addWorkerToCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-42AD2A2E-CE88-4F15-AECE-FC70A4C7B574-high.png)
+
+With the API key in hand and configuration complete in HPE Morpheus Enterprise UI, head back to the worker box. Configure the gateway by editing `/etc/morpheus/morpheus-worker.rb` and updating the following:
+
+```
+```
+worker_url = 'https://gateway_worker_url' # This is the worker URL the Morpheus appliance can resolve and reach on 443  
+worker['appliance_url'] = 'https://morpheus_appliance_url' # The resolvable URL or IP address of Morpheus appliance which the worker can reach on port 443  
+worker['apikey'] = 'API KEY FOR THIS GATEWAY' # VDI Gateway API Key generated from Morpheus Appliance VDI Pools > VDI Gateways configuration. For worker only mode, a value is still required but can be any value, including the 'API KEY FOR THIS GATEWAY' default template value  
+worker['worker_key'] = 'DISTRIBUTED WORKER KEY' # Distributed Worker API Key from Administration > Integrations > Distributed Workers configuration  
+worker['proxy_address'] = 'http://proxy.address:1234' # For environments in which the worker must go through a proxy to communicate with the Morpheus appliance or other resources, configure the address  
+worker['no_proxy'] = 'vcenter.example.com,192.168.xx.xx' # A comma-separated list of resources that should be accessed directly and not through the proxy
+```
+```
+
+NOTE
+
+By default the worker\_url uses the machine’s hostname, ie `https://your_machine_name`. The default `worker_url` value can be changed by editing `/etc/morpheus/morpheus-worker.rb` and changing the value of `worker_url`. Additional appliance configuration options are available below.
+
+After all configuration options have been set, run `sudo morpheus-worker-ctl reconfigure` to install and configure the worker, nginx and guacd services:
+
+```
+```
+sudo morpheus-worker-ctl reconfigure
+```
+```
+
+The worker reconfigure process will install and configure the worker, nginx and guacd services and dependencies.
+
+TIP
+
+If the reconfigure process fails due to a missing dependency, add the repo that the missing dependency can be found in and run
+
+NOTE
+
+Configuration options can be updated after the initial reconfigure by editing `/etc/morpheus/morpheus-worker.rb` and running `sudo morpheus-worker-ctl reconfigure` again.
+
+Once the installation is complete the morpheus worker service will automatically start and open a web socket with the specified HPE Morpheus Enterprise appliance. To monitor the startup process, run `morpheus-worker-ctl tail` to tail the logs of the worker, nginx and guacd services. Individual services can be tailed by specifying the service, for example `morpheus-worker-ctl tail worker`
+
+## Highly-Available (HA) Deployment
+
+If desired, multiple distributed worker nodes may be associated to the same HPE Morpheus Enterprise appliance to eliminate a single point of failure should a distributed worker node go down. Configure each distributed worker node using the same worker key (process described in the prior section) and add redundancy using as many additional workers nodes as needed. When multiple worker nodes are using the same worker key, proxy calls will always go through the primary worker node when possible. The primary node is the first worker node configured using a specific worker key. When necessary, automatic failover will take place and another active worker node will be used. While proxy calls will always try to use the primary node when available, HPE Morpheus Enterprise Agent communications can be balanced equally across worker nodes by placing a VIP in front of your distributed workers.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json b/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
new file mode 100644
index 0000000..74bc1e2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+  "title": "Base Requirements",
+  "ordinal": 4,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.html",
+  "topic_cluster": {
+    "clustering_title": "Base Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A",
+        "clustering_title": "Base Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md b/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
new file mode 100644
index 0000000..0ecfcbf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A3332B9C-D74E-4095-AE33-18F65AB33A7A.md
@@ -0,0 +1,38 @@
+# Base Requirements
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x, 9.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+| Rocky | 8, 9 |  |
+
+- **Memory:**[16 GB recommended](https://support.morpheusdata.com/s/article/How-does-Morpheus-manage-the-memory-it-uses?language=en_US) for default installations. 8 GB minimum required with 4 GB+ available storage swap space
+- **Storage:** 200 GB storage minimum (see Storage Considerations below)
+- **CPU:** 4-core, 1.4 GHz (or better), 64-bit CPU recommended for all-in-one systems. For a distributed-tier installation, it’s recommended each tier have 2-core, 1.4 GHz (or better), 64-bit CPU
+- Network connectivity from your users to the appliance over TCP 443 (HTTPS)
+- Superuser privileges via the `sudo` command for the user installing the HPE Morpheus Enterprise appliance package
+- HPE Morpheus Enterprise service nodes must be configured to use accurate NTP servers. A service node may be an app node, database node, RabbitMQ, or Elasticsearch node (see HPE Morpheus Enterprise system architecture details further on in the installation section for more details)
+- Required repository access:
+  :   - Prior to installing the HPE Morpheus Enterprise Appliance you will need to ensure that the target server or virtual machine has access to the base YUM/DNF or APT repositories
+      - A RHEL 8 server requires the `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repository be enabled and accessible
+      - A RHEL 7 server requires access to Optional RPMs repo. The repository need to be enabled and accessible
+- An appliance license is required for any operations involving provisioning
+- Current major web browsers supporting modern standards, such as Google Chrome, Mozilla Firefox, Apple Safari, and Microsoft Edge are supported
+- Internet Connectivity (optional)
+  :   - Access to `https://www.hpe.com/support/hpesc`, `https://share.morpheusdata.com`, and `https://d2u3hdjdxt56gx.cloudfront.net` (the share.morpheusdata.com cloudfront domain that share package requests will redirect to) over port 443 required on app nodes when reconfiguring to download embedded packages and plugins.
+      - Access to `https://morpheus-images.morpheusdata.com`, `https://registry.morpheusdata.com`, and `https://playbooks.morpheusdata.com` To download HPE Morpheus Enterprise’ system images and playbooks.
+      - Offline installation requires installing the supplemental package in addition to the regular installation package. Local yum/apt repo access still required for offline installations.
+
+NOTE
+
+Access to `yum` and `apt` repos is still required for offline installations.
+
+- VM and Host Agent Install (optional)
+  :   - Inbound connectivity access from provisioned VMs and container hosts on port 443 (Agent install and communication). Port 80 may be required for older `apt` distros.
+      - An Appliance URL that is accessible/resolvable to all managed hosts. It is necessary for all hosts that are managed by HPE Morpheus Enterprise to be able to communicate with the appliance server ip on port 443. This URL is configured under Administration > Settings.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json b/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
new file mode 100644
index 0000000..c83326d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+  "title": "Creating a Storage Server",
+  "ordinal": 440,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Storage Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C",
+        "clustering_title": "Creating a Storage Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md b/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
new file mode 100644
index 0000000..8c4313d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A450E1F4-7639-4C2C-9A32-0C6117C0816C.md
@@ -0,0 +1,19 @@
+# Creating a Storage Server
+
+## About this task
+
+This procedure guides you through creating a storage server.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > Servers.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage HVM for type, specify the URL for the storage array, and the credentials.
+5. Click the Save Changes to create the storage server.   
+   ![Add Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-27BC7480-6D59-4328-A9E6-34871F98D44A-high.png)
+
+## Results
+
+The added storage server appears under Servers.   
+![storage server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-34DE4590-20A0-495D-BF21-0EC690472E30-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json b/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
new file mode 100644
index 0000000..4714224
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.json
@@ -0,0 +1,21 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+  "title": "Host Hardware Sensor Data Collection",
+  "ordinal": 189,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html",
+  "topic_cluster": {
+    "clustering_title": "Host Hardware Sensor Data Collection",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35",
+        "clustering_title": "Host Hardware Sensor Data Collection"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md b/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
new file mode 100644
index 0000000..fe3e37e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.md
@@ -0,0 +1,27 @@
+# Host Hardware Sensor Data Collection
+
+If properly configured, HVM Hosts can display detailed hardware information on the HVM Hosts detail pages. This information includes system health LED state, CPU temperature, ambient temperature, fan speeds, power supply state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BC8DF5F3-1416-4BE4-B58F-CB1926EF7DD2-high.png)
+
+Configuration
+
+In order to surface hardware sensor data into the UI, IPMI tool and it's dependency packages must be installed on each host. Following installation, the host agent must be restarted.
+
+1. Install IPMI tool and its dependency packages (`freeipmi-common`, `ipmitool`, `libfreeipmi17`, `openipmi`)
+
+   NOTE
+
+   This tool can also be installed via apt package manager provided that the corresponding Ubuntu mirrors (main and universe module repos) are enabled. Run `sudo apt update` and then `sudo apt install ipmitool`.
+2. To confirm installation, run `sudo ipmitool -v` and the installed version should be displayed
+3. Restart the host agent with `sudo morpheus-node-ctl restart`
+4. Repeat this process on all cluster hosts
+
+Viewing Hardware Sensor Data
+
+When properly configured, hardware sensor data may be viewed from the host detail page:
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM cluster
+3. Select the Health subtab
+4. The hardware sensor states and hardware events are shown in the Sensors and Events subtabs
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json b/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
new file mode 100644
index 0000000..73a8770
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+  "title": "Cluster Layouts",
+  "ordinal": 144,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.html",
+  "topic_cluster": {
+    "clustering_title": "Cluster Layouts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C",
+        "clustering_title": "Cluster Layouts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md b/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
new file mode 100644
index 0000000..56b690d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A47333AC-3343-485B-BF3D-6C7C71F0F89C.md
@@ -0,0 +1,13 @@
+# Cluster Layouts
+
+HPE Morpheus Enterprise includes many different types of Cluster Layouts out-of-the-box which support a number of provisioning technologies. Many of these HPE Morpheus Enterprise-provided Cluster Layouts may also be cloned for use in creating custom layouts. Edit or delete user-created Cluster Layouts using the pencil (✎) or trash can (🗑) icons next to the desired layout on the Cluster Layouts list page. See the next section for an
+
+![../../_images/clusterLayouts.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-828B4DE9-16E1-4F18-9F19-FDC0410DB2C6-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise now syncs available (non-preview) AKS k8s versions daily. Existing synced versions that are no longer supported by Azure are automatically disabled. The table below includes available AKS versions at time of v8.0.7 release.
+
+**Subtopics**  
+
+- **[Creating Custom Cluster Layouts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-382BFCD5-DE8D-4C54-B3D6-704970132153.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json b/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
new file mode 100644
index 0000000..12a1f99
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+  "title": "2 Factor Authentication",
+  "ordinal": 335,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.html",
+  "topic_cluster": {
+    "clustering_title": "2 Factor Authentication",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB",
+        "clustering_title": "2 Factor Authentication"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md b/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
new file mode 100644
index 0000000..5077937
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A4D2B5B8-19D2-48B5-8E4F-2717C97467EB.md
@@ -0,0 +1,21 @@
+# 2 Factor Authentication
+
+HPE Morpheus Enterprise supports two-factor authentication (2FA) for local user accounts as well as those authenticating through Active Directory and LDAP identity sources. Authentication is handled through a 2FA app such as Authy or Google Authenticator. Other common methods for handling 2FA, such as through email or SMS text message are not currently supported. Two-factor authentication is handled on a per-user basis through the User Settings section. There is not currently a way for an administrator to enforce the use of two-factor authentication appliance-wide.
+
+## Setting Up Two-Factor Authentication
+
+When two-factor authentication isn’t yet set up, this section contains a single button: ENABLE 2FA. To get started, click this button and HPE Morpheus Enterprise will prompt for your password. After entering the password, you’ll be shown a QR code which can be scanned into your authenticator application of choice. Once the QR code is shown, 2FA is active and the supplemental code will need to be entered each time the user logs in.
+
+![../../_images/2fa_qr.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B46B6795-F044-4E76-BEB1-3A96F5575CE6-high.png)
+
+On subsequent login attempts, the user will be prompted to enter a 2FA code after successful entry of the username and password. Retrieve this code from the 2FA app you set up in the prior section and enter it to complete the login process.
+
+## Disabling Two-Factor Authentication
+
+When two-factor authentication is set up, this section contains two buttons: DISABLE 2FA and GET 2FA CODE. To generate a new QR code and configure an authenticator app, click GET 2FA CODE. Once you generate a new QR code, the old one is no longer valid. At that point you must reconfigure your authenticator app or you will not be able to access your account on the next login attempt. Generating a new QR code requires your password.
+
+To disable 2FA, click DISABLE 2FA. This action does not require a password.
+
+## Handling User Lock-Out
+
+If a user loses the device they’ve configured for authentication or if they cannot proceed through 2FA login for any other reason, an administrator should impersonate the user’s account, reset their password, disable 2FA, then share the new temporary password with the user. At that point, the user can login, reset their password to something more secure, and re-enable 2FA (if desired).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json b/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
new file mode 100644
index 0000000..2405fc3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+  "title": "Troubleshooting and Diagnostics",
+  "ordinal": 449,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A50734F6-41F7-4350-B07E-92C559E94119.html",
+  "topic_cluster": {
+    "clustering_title": "Troubleshooting and Diagnostics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A50734F6-41F7-4350-B07E-92C559E94119",
+        "clustering_title": "Troubleshooting and Diagnostics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md b/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
new file mode 100644
index 0000000..5b2070a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A50734F6-41F7-4350-B07E-92C559E94119.md
@@ -0,0 +1,30 @@
+# Troubleshooting and Diagnostics
+
+This section provides a structured approach to diagnose and resolve common issues encountered during compute, OS imaging, networking, and storage operations.
+
+Use the following details to obtain the accurate troubleshooting details:
+
+- Identify the symptom: locate the closest match in the table or subsection.
+- Confirm the likely cause: check the listed items using the provided tools and logs.
+- Apply the suggested fix: perform the recommended actions.
+- Collect diagnostic information: if the issue persists, gather logs and screenshots for support escalation.
+
+When reporting an issue, you require the following diagnostics details:
+
+- **System Details**
+  - Hostname / Device ID
+  - OS version and build
+  - BIOS/Firmware version
+- **Event Details**
+  - Date and time of failure
+  - Step at which failure occurred
+  - Any error messages or codes
+- **Logs**
+  - Relevant log files for the failed component
+  - Screenshots of errors (if applicable)
+
+**Subtopics**  
+
+- **[Compute](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9646B8E1-8BBB-4D2A-B0F6-B3265547CBB0.html)**
+- **[Networking](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5B7DB753-B382-4E98-BF3A-599C15334A69.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json b/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
new file mode 100644
index 0000000..d191d44
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+  "title": "Catalog Items",
+  "ordinal": 138,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.html",
+  "topic_cluster": {
+    "clustering_title": "Catalog Items",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A",
+        "clustering_title": "Catalog Items"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md b/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
new file mode 100644
index 0000000..e8a6117
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A5363EB4-95EC-4901-82B6-4B15C6A7948A.md
@@ -0,0 +1,19 @@
+# Catalog Items
+
+The Self Service catalog (Library > Blueprints > Catalog Items) is where administrators can create easily-deployable items for consumption by users operating under the “Service Catalog” Persona in HPE Morpheus Enterprise. Catalog items can be fully-configured HPE Morpheus Enterprise Instances or Blueprints, complete with user input through HPE Morpheus Enterprise Inputs, automation Workflows, and more. The catalog items are presented in a simplified interface for ease of deployment without sacrificing configurability for administrators. All available catalog items are built in the Self Service area and users will see relevant items in their catalogs based on Role permissions.
+
+NOTE
+
+For more on Personas and using the Service Catalog persona, see the Personas sections of our documentation.
+
+Access is granted to the Self Service section through the Library: Catalog Items Role permission. Users with Read rights can view the catalog while users with full rights can create and edit catalog items. Users without any rights to Self Service will not be able to access the page at all.
+
+Additionally, a user’s Role determines access to the standard and/or service catalog persona and which service catalog items are available for a user under the service catalog persona. See the Roles section of HPE Morpheus Enterprise documentation for more information on administering Roles.
+
+**Subtopics**  
+
+- **[Viewing the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html)**
+- **[Building Catalog Instances](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1F30FE4D-FAD1-444B-9570-E20C339F257C.html)**
+- **[Building Catalog Blueprints](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1AA91E38-BE43-4571-ADEB-714F77E9E728.html)**
+- **[Building Catalog Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-669BC598-B756-4F95-8F4B-7CBBB2AE3135.html)**
+- **[Editing and Deleting from the Self Service Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1E4F2B1B-4D5D-44BD-AF29-E0610E2E246E.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json b/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
new file mode 100644
index 0000000..108618f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+  "title": "Identity Management",
+  "ordinal": 487,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html",
+  "topic_cluster": {
+    "clustering_title": "Identity Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4",
+        "clustering_title": "Identity Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md b/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
new file mode 100644
index 0000000..e224c66
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.md
@@ -0,0 +1,9 @@
+# Identity Management
+
+**Subtopics**  
+
+- **[Active Directory](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-27FB9EA7-F54A-4B56-B3C8-0E5BF78A62C6_2.html)**
+- **[SAML Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96_2.html)**
+- **[Azure Active Directory SSO (SAML)](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E_2.html)**
+- **[OneLogin](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-78DC62BA-524C-456D-827F-465C10A1AA6F_2.html)**
+- **[Okta](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2C8CA91E-083D-424F-A910-1E6CFFD8A997_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json b/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
new file mode 100644
index 0000000..1b5d330
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+  "title": "Containers",
+  "ordinal": 478,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html",
+  "topic_cluster": {
+    "clustering_title": "Containers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E",
+        "clustering_title": "Containers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md b/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
new file mode 100644
index 0000000..71c28a6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.md
@@ -0,0 +1,5 @@
+# Containers
+
+**Subtopics**  
+
+- **[Docker Registry](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8C2BA6FC-5D42-4465-9866-B45FD50AECB0.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json b/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
new file mode 100644
index 0000000..1e8b0f8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+  "title": "Commvault",
+  "ordinal": 383,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.html",
+  "topic_cluster": {
+    "clustering_title": "Commvault",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633",
+        "clustering_title": "Commvault"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md b/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
new file mode 100644
index 0000000..b297d1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AAB2A3F5-883C-4E19-9443-73AB2E7FE633.md
@@ -0,0 +1,97 @@
+# Commvault
+
+HPE Morpheus Enterprise integrates with Commvault for selection as a Cloud backup target. Compatible Clouds include VMware and OpenStack. HPE Morpheus Enterprise integrates with your existing Commvault appliance, which can then be set as the preferred backup solution for any existing Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Commvault with HPE Morpheus Enterprise, sharing a Commvault integration with multiple Tenants, setting backup during Instance provisioning, and restoring Instances from backup.
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Commvault integration as the default backup target for compatible clouds
+- Select Commvault integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Commvault Integration
+
+### Procedure
+
+1. Navigate to Backups  >  Services
+2. Select + ADD
+3. Select Commvault
+4. Fill in the following: 
+
+   Name
+   :   Name of the Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enable the Commvault integration
+
+   Host
+   :   IP or Hostname of the Commvault server.
+
+   Port
+   :   Port number configured to access the Commvault server
+
+       TIP
+
+       Enter the port to connect with the Commvault web server, by default this is port 81. For more, see [Commvault port requirement documentation](https://documentation.commvault.com/11.24/essential/7102_port_requirements_for_commvault.html).
+
+   Username
+   :   Admin Username for Commvault
+
+   Password
+   :   Password for Username provided (encrypted in HPE Morpheus Enterprise).
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only Available to the Tenant the Integration is added by
+
+           Public
+           :   Available to Sub-Tenants (master tenant option only)
+5. SAVE
+
+## Set Commvault as Cloud Backup Target
+
+### About this task
+
+Once the initial integration is made, set this integration as the backup provider for as many supported Clouds as needed. Commvault integrations are supported as backup target for VMware and OpenStack Clouds at this time.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Select an existing VMware or OpenStack Cloud
+3. Click EDIT
+4. Expand the Advanced Options section
+5. Under “Backup Provider”, select the relevant Commvault integration
+6. Click SAVE CHANGES
+
+### Results
+
+![../../_images/1setProviders.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-81075293-A540-4075-BAC0-19F608D18FA8-high.png)
+
+## Configure Backup at Provision Time
+
+When provisioning an Instance into a Cloud where Commvault is set as the backup provider, Commvault will be selectable as the “Backup Type” on the Automation tab of the provisioning wizard. Expand the Backups section on this tab and enter the following:
+
+- **Backup Type:** Select the desired Commvault backup type
+- **Backup Server:** Select the desired server synced from the Commvault backup provider associated with the Cloud
+- **Backup Set:** Select a configured backup set synced from the Commvault backup provider associated with the Cloud
+- **Storage Policy:** Gold, Silver, or Bronze. Select the applicable SLA or retention policy for the workload being provisioned. The meanings of these retention tiers are configurable in Commvault
+- **Backup Name:** A name for the backup in HPE Morpheus Enterprise, this field is pre-populated with the Instance name but can be overwritten
+- **Backup Job Type:** Clone an existing backup job (Backups > Jobs) or add this backup to an existing job. A job contains a retention count and backup frequency schedule and can have as many Instances backing up under it as needed
+- **Backup Job:** Select the job which will be cloned or have a backup added to it depending on your selection in the prior field
+- **Job Name:** A name for the new cloned job (if you are cloning and not creating a new Backup Job)
+
+![../../_images/2createBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7E2EA78B-D0ED-4017-A07E-8815E86AB7D3-high.png)
+
+## Viewing Backups
+
+After provisioning, users can review backup details from the Instance detail page (Provisioning > Instances > Selected Instance > Backupstab). Additionally, backups can be configured here if this was not done during provision time by clicking ADD BACKUP. Users can also run one-off backups from this page by opening the ACTIONS menu and clicking Backup. Backups will still continue to run based on the schedule configured in their job but additional runs can be made on-demand this way.
+
+Within the Backups section (Backups > Backups) users can also view all currently-configured backups and whether or not recent backup runs have succeeded.
+
+![../../_images/3viewBackups.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7BEAAAB4-4ED9-44C1-8A1C-C06C362C29E9-high.png)
+
+## Restore an Instance from Commvault
+
+For Instances with current backups, the Backup Results section will be populated on the Instance detail page (Provisioning > Instances > Selected Instance > Backuptab). If the Instance needs restored, simply click Actions (within the Backup Results area, not the main actions menu for the Instance itself) and then click Restore. The status icon at the top of the Instance detail page will turn green once this process is finished and the Instance will be fully restored from your selected backup.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
new file mode 100644
index 0000000..0b28077
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+  "title": "Overview",
+  "ordinal": 293,
+  "parent_title": "Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB0E1772-B646-49E2-8318-B2495341839D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB0E1772-B646-49E2-8318-B2495341839D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
new file mode 100644
index 0000000..00eb1cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB0E1772-B646-49E2-8318-B2495341839D.md
@@ -0,0 +1,11 @@
+# Overview
+
+Within HPE Morpheus Enterprise is a wide array of role based access control capabilities. These roles can be managed within the Admin > Roles section of the HPE Morpheus Enterprise UI as well as through the API or CLI. They are designed to be robust enough to fit within a wide array of enterprise and managed service provider scenarios so they can be a bit hard to grasp at first, but should make sense once a few simple concepts are explained. There are two types of roles within HPE Morpheus Enterprise called Tenant and User based roles. Both sets of roles allow restrictions to be imposed on a user at the feature access level. Entire sections within the appliance UI can be hidden based on the specified access levels for features within HPE Morpheus Enterprise. Features have different access scopes that can be selected from and can range depending on the specific feature. The most common scope set involves none, read, and full. Instance Type access is also common among both role types which allow the administrator to restrict which service catalog items they are allowed to provision within HPE Morpheus Enterprise .
+
+There are several handy tricks for creating new roles within HPE Morpheus Enterprise and users can be assigned more than one role. When a user is assigned more than one role, permissions are granted by the role with the highest level of scope access. This allows roles to be built with small subsets of features and combined to grant different individuals relevant permission control. With resource permissions (that is, all types of permissions other than Feature permissions), a default access can be given as opposed to a specific (Full or None) permission for any resource. A specific permission will always supersede a default permission regardless of whether it’s more permissive or more restrictive. In other cases (default vs default OR specific vs specific) the more permissive access will be given.
+
+It’s also important to note that built-in Roles, such as the System Admin “Superuser” Role carry no special prominence. For resource permissions, the System Admin user has defaults set to Full in each section. Thus, pairing the System Admin Role with another Role that may include specific line item permissions for various resource categories may cause your System Admin users to take on a reduced permission set.
+
+NOTE
+
+Feature access control not only applies to the HPE Morpheus Enterprise UI but also applies to the public developer API. It is sometimes necessary to logout and back in for changes to a users feature access level to be respected.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
new file mode 100644
index 0000000..08d562d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+  "title": "Linux OS Imaging",
+  "ordinal": 414,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.html",
+  "topic_cluster": {
+    "clustering_title": "Linux OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C",
+        "clustering_title": "Linux OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
new file mode 100644
index 0000000..a7d342f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB6DFB41-D93F-4C53-BBD5-1F6EAA322B2C.md
@@ -0,0 +1,95 @@
+# Linux OS Imaging
+
+This section describes the supported Linux distributions and guides for deploying Linux on bare metal using Morpheus. It includes validated OS versions, required virtual image settings, boot loader configuration for unattended installation, and troubleshooting steps for common deployment issues (see Section Troubleshooting for more details).
+
+The following Linux distributions have been validated for deployment:
+
+- Red Hat Enterprise Linux (RHEL) and derivatives
+
+  - RHEL 9.5
+  - Oracle Linux 8.10
+  - Oracle Linux 9.5
+- Ubuntu Server
+
+  - Ubuntu Server 22.04.5 LTS
+  - Ubuntu Server 24.04.3 LTS
+
+## Virtual Image Configuration
+
+When adding a Linux ISO to Library > Virtual Images, ensure the following settings:
+
+- Operating System: Select the appropriate OS (e.g., RHEL 9, Oracle Linux 9, Ubuntu 22.04, Ubuntu 24.04)
+- Is Cloud Init Enabled: Checked
+- Advanced
+
+  - VM Tools Installed: Checked
+
+## Boot Prompt Configuration - RHEL and Oracle Linux
+
+Unmodified RHEL and Oracle Linux ISOs include a default boot menu entry: `Test this media & install OS`.
+
+This entry performs a **full media verification** before installation.
+
+NOTE
+
+- The media check does not cause installation failure.
+- It can, however, delay deployment by 30–60 minutes, particularly in remote or virtual media environments.
+- Skipping the media check is recommended to reduce installation time.
+
+**Supported Options**
+
+- Preferred: Modify the ISO
+  - Adjust the ISO boot loader to remove or bypass the media check from the default boot entry.
+  - Ensures faster, fully unattended deployment.
+- Alternative: Manual Boot Selection
+  - At boot: Select `Install OS` (without media test).
+  - Do NOT select `Test this media & install OS`.
+- **Reference**
+  - Grub menu example (for clarity):
+  - `0 → Install Red Hat Enterprise Linux 9.5`
+  - `1 → Test this media & install Red Hat Enterprise Linux 9.5`
+  - Default entry index `1` triggers the media check.
+- Changing the default to `0` or manually selecting `Install OS` skips verification.
+
+  
+![Test media and install](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-65FC9E75-A386-4A4A-A6BE-591A95640685-high.png)
+
+## Boot Prompt Configuration - Ubuntu Server
+
+Ubuntu Server requires kernel boot parameters to enable unattended installation using cloud-init autoinstall.
+
+Unmodified ISOs do not automatically perform unattended installation.
+
+## Required Manual Step (Unmodified ISO)
+
+At the GRUB boot menu:
+
+- Highlight the default Ubuntu entry.
+- Press **e** to edit.
+- Append the following kernel parameters: `autoinstall ds=nocloud`
+- Boot with the modified entry.
+- Example Boot Entry:
+
+  ```
+  ```
+  menuentry "Ubuntu" {  
+      set gfxpayload=keep  
+      linux   /casper/vmlinuz quiet autoinstall ds=nocloud ---  
+      initrd  /casper/initrd  
+  }
+  ```
+  ```
+
+This enables cloud-init–based unattended installation.
+
+## Licensing and Registration
+
+After installation, register the OS to receive updates and support.
+
+Table 1. License and Registration
+
+     | Distribution | Registration Reference | Notes |
+| --- | --- | --- |
+| RHEL | [Red Hat Subscription-Manager Registration Guide](https://access.redhat.com/solutions/253273?utm_source=chatgpt.com) | Use `subscription-manager` to register and attach subscriptions. |
+| Oracle Linux | [Registering Oracle Linux System with ULN](https://docs.oracle.com/en/engineered-systems/exadata-database-machine/dbmmn/registering-oracle-linux-system-uln.html?utm_source=chatgpt.com) | Use the `uln_register` tool to register with Oracle Unbreakable Linux Network. |
+| Ubuntu | [Ubuntu 24.04 LTS Release Notes](https://discourse.ubuntu.com/t/ubuntu-24-04-lts-noble-numbat-release-notes/39890) | Ubuntu does not require mandatory registration. An optional Ubuntu Pro subscription provides extended security maintenance and support. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
new file mode 100644
index 0000000..e751fa2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+  "title": "Networking",
+  "ordinal": 453,
+  "parent_title": "Troubleshooting and Diagnostics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB883016-0848-46D7-8BB0-37DF09076725.html",
+  "topic_cluster": {
+    "clustering_title": "Networking",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB883016-0848-46D7-8BB0-37DF09076725",
+        "clustering_title": "Networking"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
new file mode 100644
index 0000000..16fe6b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB883016-0848-46D7-8BB0-37DF09076725.md
@@ -0,0 +1,15 @@
+# Networking
+
+| S.No. | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Cloud Network Mode Configuration | Cloud can operate in **Unmanaged** or **Managed (ArubaCX-Int)** network modes. This choice is made during cloud creation under **Advanced Options**. | Verify the correct network mode selected during cloud creation. | Morpheus UI log | Use Unmanaged for external network control; use Managed for Morpheus-managed ArubaCX switches. |
+| 2 | Unmanaged Network - Default Setup | In Unmanaged mode, Morpheus creates a minimal configuration: a default Resource Pool and a default unmanaged network. The default network is **untagged** and uses **DHCP**. | Ensure the DHCP server exists and the network is configured for an untagged VLAN. | Morpheus UI log | This allows instances to boot with connectivity without extra network configuration. |
+| 3 | Unmanaged Network - Additional VLANs | Users can create additional VLANs/networks as required. | Check VLAN configuration and availability in provisioning options. | Morpheus UI log | Additional networks can be consumed by bare-metal instances. |
+| 4 | Managed Network - ArubaCX Integration | Managed mode uses ArubaCX switches and requires the ArubaCX plugin. | Confirm the ArubaCX plugin is loaded in Morpheus. | Morpheus UI log | Managed networks allow Morpheus to configure VLANs on switches automatically. |
+| 5 | Adding HPE ArubaCX Plugin | The plugin must be loaded to enable managed network features. Follow the procedure Adding HPE BMaaS Integration to load the plugin JAR. | Verify plugin status in Morpheus. | Morpheus UI log | Required before creating network integrations. |
+| 6 | Creating ArubaCX Network Integration | Integration defines switch credentials and switch pairs (typically 2 per rack). | Verify switch IPs, username, and password are correct. | Morpheus UI log | One integration is needed per rack (switch pair). |
+| 7 | Creating Managed Networks | Networks represent VLANs and include attributes like subnet, gateway, DNS, and IP allocation method. | Ensure VLAN ID, trunks, and subnet are correct. | Morpheus UI log | Primary VLAN is untagged, VLAN trunks are tagged. |
+| 8 | Private Network Option | Private networks do not configure a primary VLAN on the uplink, making them inaccessible outside the cloud. | Confirm if the network should be private or public. | Morpheus UI log | Used for internal workload networks only. |
+| 9 | Network Consumption During Provisioning | Networks are attached to physical or bonded interfaces. Primary VLAN is untagged, trunk VLANs are tagged. | Check interface type (physical or bond) and correct VLAN assignment. | Morpheus UI log | Supports Static Bond, LACP Bond, and Switch Independent Bond. |
+| 10 | Bond Interface Configuration | Bond interfaces require two physical ports to form an aggregated link. | Ensure both physical ports are available and correctly mapped. | Morpheus UI log | Bonding provides bandwidth aggregation and redundancy. |
+| 11 | Virtual Network Interfaces | Virtual networks allow tagged VLANs to be configured as IP interfaces on the server OS. | Verify if tagged networks require an IP interface. | Morpheus UI log | If not needed, do not configure the virtual interface. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
new file mode 100644
index 0000000..e441172
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+  "title": "Routers",
+  "ordinal": 219,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.html",
+  "topic_cluster": {
+    "clustering_title": "Routers",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB938CF2-D0FE-4516-931D-0238D0662B84",
+        "clustering_title": "Routers"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
new file mode 100644
index 0000000..b4a6e2a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB938CF2-D0FE-4516-931D-0238D0662B84.md
@@ -0,0 +1,41 @@
+# Routers
+
+## Overview
+
+Routers can be viewed, created, and managed from the Routers tab of the Infrastructure > Networks page. HPE Morpheus Enterprise supports the creation of the following router types depending on networks that are currently configured:
+
+- Amazon Internet Gateway
+- Huawei Router
+- Neutron Router
+- NSX Edge Gateway
+- NSX Edge Logical Router
+- NSX Cloud Tier0 Gateway
+- NSX Cloud Tier1 Gateway
+- NSX Tier0 Gateway
+- NSX Tier1 Gateway
+- Open Telekom Router
+
+## Create New Router
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click + ADD
+3. Select the router type and complete the fields on the resulting modal
+4. Once complete, click ADD NETWORK ROUTER
+
+## Editing Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the pencil icon for the appropriate router
+3. After editing router fields, click SAVE
+
+## Deleting Existing Routers
+
+### Procedure
+
+1. Navigate to Infrastructure > Networks > Routerstab
+2. Click on the trash can icon for the appropriate router
+3. Acknowledge the pop-up banner ensuring you wish to delete the router
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
new file mode 100644
index 0000000..51f2634
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+  "title": "Avamar",
+  "ordinal": 387,
+  "parent_title": "Backups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.html",
+  "topic_cluster": {
+    "clustering_title": "Avamar",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14",
+        "clustering_title": "Avamar"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
new file mode 100644
index 0000000..0d510b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB95AFDD-C12B-416D-B289-B10B0A1ABE14.md
@@ -0,0 +1,57 @@
+# Avamar
+
+HPE Morpheus Enterprise integrates with an existing Avamar appliance which can then be set as the preferred backup solution for any compatible Clouds. From there, easily schedule backup routines during Instance provisioning and restore Instances when needed. This section discusses the process for integrating Avamar with Morpheus. Once the integration is complete, when editing or adding compatible Clouds, set the Avamar integration as the backup provider for the Cloud. At provision time, set Avamar backup configurations for the workload. When necessary, restore Instances from Avamar backup.
+
+IMPORTANT
+
+Avamar API must be installed on Avamar server (not installed by default)
+
+## Features
+
+- Share one backup provider across multiple Tenants
+- Apply Avamar integration as the default backup target for compatible Clouds
+- Select Avamar integrations as backup provider at Instance provision time
+- Automate backups with HPE Morpheus Enterprise Backup Jobs
+- When needed, easily restore Instance backups
+
+## Adding Avamar Integration
+
+### Procedure
+
+1. Navigate to Backups > Integrations
+2. Select + ADD
+3. Select Avamar
+4. Fill in the following: 
+
+   Name
+   :   Name for the Avamar integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   When checked, the integration is selectable as a backup provider for compatible Clouds
+
+   Host
+   :   IP or Hostname of the Avamar API server
+
+   Port
+   :   Port number configured to access the Avamar server
+
+   Username
+   :   Admin username for Avamar
+
+   Password
+   :   Password for the user provided. Choose to enter credentials locally or use a securely-stored credential set saved previously
+
+   Tenant
+   :   Avamar Tenant/Domain scoping for the integration
+
+   Hypervisor
+   :   Avamar Hypervisor scoping for the integration
+
+   Visibility
+   :   Sets Multi-Tenant Visibility
+       :   Private
+           :   Only available to the Tenant that adds the integration
+
+           Public
+           :   Available to Subtenants (Master Tenant option only)
+5. Click SAVE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json b/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
new file mode 100644
index 0000000..6b773cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+  "title": "Costing: Tenant Costing",
+  "ordinal": 60,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Tenant Costing",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E",
+        "clustering_title": "Costing: Tenant Costing"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md b/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
new file mode 100644
index 0000000..61a6bdb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.md
@@ -0,0 +1,31 @@
+# Costing: Tenant Costing
+
+![../_images/3tenantcosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D08A61BD-C24A-4D73-82C0-45BAEBC26DCB-high.png)
+
+The Tenant Costing dashboard aggregates costing totals across all Tenants that meet the filters set on the dashboard. This information helps administrators track the current spend of each Tenant for the current monthly period. It also helps identify the costliest Tenants and to anticipate month-end costs for each individual Tenant.
+
+## Filters
+
+Filter the Tenants pulled into the dashboard by one or more of the following fields:
+
+- Tenant (all matched by search)
+- Cloud
+- Tenant (selected from dropdown)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all Tenants that meet set filters:
+
+- **TENANTS:** The total number of Tenants that meet set filters
+- **MONTH TO DATE:** The total spend in the current month for all Tenants meeting dashboard filters
+- **PROJECTED:** The projected total spend for the current month for all Tenants meeting dashboard filters
+- **LAST MONTH:** The total spend in the prior month for all Tenants meeting dashboard filters
+
+## Tenant List
+
+Each Tenant that meets set filters is listed at the bottom of the dashboard, the following data points are revealed for each individual Tenant:
+
+- **NAME:** The name given to the Tenant in HPE Morpheus Enterprise at the time of creation
+- **DESCRIPTION:** The Tenant description (if available)
+- **MONTH TO DATE:** The current month-to-date spend for the individual Tenant listed
+- **PROJECTED TOTAL:** The projected total spend for the current month for the individual Tenant listed
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json b/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
new file mode 100644
index 0000000..2ccbe8f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+  "title": "AWS",
+  "ordinal": 389,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html",
+  "topic_cluster": {
+    "clustering_title": "AWS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F",
+        "clustering_title": "AWS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md b/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
new file mode 100644
index 0000000..c874d35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.md
@@ -0,0 +1,959 @@
+# AWS
+
+## Overview
+
+AWS is the Amazon public cloud, offering a full range of services and features across the globe in various datacenters. AWS provides businesses with a flexible, highly scalable, and low-cost way to deliver a variety of services using open standard technologies as well as proprietary solutions. This section of documentation will help you get HPE Morpheus Enterprise and AWS connected to utilize the features below:
+
+## Features
+
+- Instance, Service, Infrastructure Provisioning & Synchronization
+- EKS Cluster Creation & Synchronization
+- HPE Morpheus Enterprise Kubernetes, Docker & KVM Cluster Creation
+- ELB Classic Load Balancer Creation & Synchronization
+- ELB Application Load Balancer (ALB) Creation & Synchronization
+- Security Group Creation & Synchronization
+- Security Group Rule Creation & Synchronization
+- Network Synchronization
+- VPC Creation & Synchronization
+- CloudFormation Provisioning & Resource Synchronization
+- Terraform Provisioning & Resource Synchronization
+- Pricing & Costing Synchronization
+- MetaData Tag Creation & Synchronization
+- S3 Bucket Creation & Synchronization
+- Route53 Automation & Synchronization
+- IAM Profile Synchronization and Assignment
+- RDS Support
+- Backups / Snapshots
+- Migrations
+- Auto Scaling
+- Remote Console (SSH & RDP)
+- Lifecycle Management and Resize
+- Restore from Snapshots
+- Elastic IP Assignment
+- Network Pools
+- Enhanced Invoice Costing
+
+## Requirements
+
+AWS IAM Security Credentials
+:   Access Key Secret Key Sufficient User Privileges (see [MinimumIAMPolicies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ABC2295F-BA5B-49C6-BF73-263A724F948F.html#GUID-4A622A6F-E3FD-431B-B748-EF492C316D40) section for more info)
+
+Security Group Configuration for Agent Install, Script Execution, and Remote Console Access
+:   - Typical Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389 (22 & 3389 required for Console. 22 & 5985 required for agent-less comms)
+    - Typical Outbound to HPE Morpheus Enterprise Appliance: 443 (Required for Agent install & comms)
+
+    NOTE
+
+    These are required for HPE Morpheus Enterprise agent install, communication, and remote console access for windows and linux. Other configurations, such as docker instances, will need the appropriate ports opened as well. Cloud-init Agent Install mode does not require incoming access for port 22.
+
+Network(s)
+:   IP assignment required for Agent install, Script Execution, and Console if the HPE Morpheus Enterprise Appliance is not able to communicate with AWS instances private ip’s.
+
+## Adding an AWS Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + Create Cloud
+3. Select AWS
+4. Enter the following:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+#### About this task
+
+REGION
+:   Select AWS Region for the Cloud. AWS Clouds may also be scoped to all regions.
+
+ACCESS KEY
+:   Access Key ID from AWS IAM User Security Credentials.
+
+SECRET KEY
+:   Secret Access Key associated with the Access Key ID.
+
+USE HOST IAM CREDENTIALS
+:   Check to use use Host IAM Credentials
+
+ROLE ARN
+:   Supports security token service (STS) to AssumeRole by entering an AWS Role ARN
+
+EXTERNAL ID
+:   When required to AssumeRole, included the needed External ID
+
+INVENTORY
+:   Basic
+    :   HPE Morpheus Enterprise will sync information on all EC2 Instances in the selected VPC the IAM user has access to, including Name, IP Addresses, Platform Type, Power Status, and overall resources sizing for Storage, CPU and RAM, every 5 minutes. Inventoried EC2 Instances will appear as Unmanaged VM’s.
+
+    Full
+    :   In addition to the information synced from Basic Inventory level, HPE Morpheus Enterprise will gather Resource Utilization metrics for Memory, Storage and CPU utilization per VM.
+
+    Off
+    :   Existing EC2 Instances will not be inventoried
+
+    NOTE
+
+    Cloud Watch must be configured in AWS for HPE Morpheus Enterprise to collect Memory and Storage utilization metrics on inventoried EC2 instances.
+
+USE VPC
+:   Specify if the target account is using EC2-VPC or EC2-Classic Platform. In almost all cases, VPC should be selected, and then select the target VPC from the synced available VPC’s list, or All VPC’s.
+
+#### Procedure
+
+The AWS cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+IMAGE TRANSFER STORE
+:   S3 bucket for Image transfers, required for migrations into AWS.
+
+EBS ENCRYPTION
+:   Enable or disable encryption of EBS Volumes
+
+COSTING KEY
+:   For Gov Cloud pricing only, key for standard managing cost account
+
+COSTING SECRET
+:   For Gov Cloud pricing only, secret for standard managing cost account
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+KMS KEY ID
+:   For specify an AWS KMS key for encrypting EBS Volumes when volume encryption is enabled
+
+## Provisioning and Keypairs
+
+During provisioning, users do not need to create or select a keypair as you would do when provisioning directly from the AWS console. If needed, HPE Morpheus Enterprise will create an AWS keypair without input from the user. In the AWS console and in the HPE Morpheus Enterprise Keypairs Section (Infrastructure > Trust > Key Pairs) you will see these keypairs listed. HPE Morpheus Enterprise will also inventory other keypairs which are created in your integrated AWS clouds and these will be listed out in the HPE Morpheus Enterprise Keypairs section.
+
+These created keypairs are not accessible to the user as you do not see them at creation time and they are encrypted as stored in the HPE Morpheus Enterprise database. To have access to the Instance after provisioning, the user should have his or her user created during provisioning. This is done by creating a Linux user in HPE Morpheus Enterprise [User Settings](https://docs.morpheusdata.com/en/latest/administration/user_settings/user_settings.html#linux-settings) and associating a keypair with the user. If you don’t currently have a keypair to use, HPE Morpheus Enterprise can generate one for you in the Keypairs section.
+
+![../../../_images/userKeypair.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A382092A-E8E1-4130-835B-6700A0619EDB-high.png)
+
+With your user set in HPE Morpheus Enterprise User Settings, ensure that your user is being created during Instance provisioning. On the CONFIGURE tab of the Instance provisioning wizard, mark the “CREATE YOUR USER” box. This is normally checked by default if a user is configured in HPE Morpheus Enterprise User Settings but you can confirm that here.
+
+![../../../_images/createUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5670B0FB-6FFF-4925-860C-C8117AA15A1C-high.png)
+
+It’s worth noting that adding your user to the provisioned workload does not replace the keypair used by HPE Morpheus Enterprise during provisioning. Instead it adds the public key for your user to the authorized keys file on the workload which allows you to access it. You can confirm this by catting out the authorized key file on any of your HPE Morpheus Enterprise-provisioned workloads (~/.ssh/authorized\_keys). You will at least see two keys, one for the HPE Morpheus Enterprise service user and one for your own user.
+
+NOTE
+
+In general it should not cause problems if HPE Morpheus Enterprise-generated keypairs are deleted from the AWS console or from the HPE Morpheus Enterprise keypairs section. You would not lose console access to the VM. If needed, however, HPE Morpheus Enterprise will create more keypairs and there is currently no functionality to automatically remove these keypairs. They can be safely ignored, generally speaking there is no need to manually delete them.
+
+## Enhanced Invoice Costing Configuration
+
+AWS cloud integrations in HPE Morpheus Enterprise will sync highly-granular costing data through the use of AWS Costing & Utilization Reports (CUR). If desired, users can turn on costing in the HPE Morpheus Enterprise Cloud configuration without linking a CUR to use AWS Cost Explorer instead. HPE Morpheus Enterprise version 4.2.3 also simplified the way CUR reports can be selected or created in order to sync costing data. The section below discusses setting up enhanced costing through CUR reports both in 4.2.3 and versions prior. For additional details on setting up costing with AWS GovCloud, see the next section.
+
+NOTE
+
+Even with a costing report configured in the Cloud integration as described below, the COSTING value must also be set to “Costing and Reservations” in order for enhanced invoice data to be brought into HPE Morpheus Enterprise. Confirm this setting by editing the Amazon Cloud integration, and checking the COSTING value in the Advanced Options panel before continuing.
+
+**v4.2.3 and Above**
+
+In HPE Morpheus Enterprise 4.2.3+, edit the Amazon cloud integration or create a new Amazon Cloud to get started. On the Create/Edit Cloud modal, open the advanced options section. The relevant fields for configuring invoice costing are shown below:
+
+![../../../_images/0billingFields.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6603376C-13FF-4A08-BCE0-30DD28A95B76-high.png)
+
+In the example case above, a new report and a new S3 bucket are created but HPE Morpheus Enterprise will also sync in buckets and reports that meet the required parameters if they already exist. For reports to be synced they must meet the requirements listed below:
+
+- Hourly time granularity
+- Include resource IDs
+- GZIP compression
+- CSV format
+
+If you don’t currently have a report meeting those criteria, you can create one by selecting “New Report” from the REPORT NAME dropdown menu. A new S3 bucket can be created in similar fashion if needed. You may also want to review the section below on configuration for HPE Morpheus Enterprise 4.2.2 and below to note policies that will be applied to your selected bucket and Cost Explorer permissions required for the AWS cloud user associated with the HPE Morpheus Enterprise Cloud integration.
+
+In the end, the following fields must be filled in order to complete the process:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+Using the HPE Morpheus Enterprise interface to create a CUR, and optionally a new S3 bucket, the IAM user requires permissions in AWS to be successful. By default, only the root user will have access to billing (including CUR), but billing can be enabled for IAM users following Amazon’s documentation for [Activating IAM Access](https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/control-access-billing.html). Once IAM access is activated, policies need to be assigned to the user being configured on the cloud in HPE Morpheus Enterprise. If the user is an administrator of the AWS account, no additional policies are needed. Below are some example policies needed for different scenarios:
+
+Creating a new CUR and new S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:PutBucketPolicy",  
+              "s3:CreateBucket",  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Creating a new CUR and using an existing S3 bucket
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "s3:ListBucket",  
+              "s3:GetBucketPolicy",  
+              "cur:DescribeReportDefinitions",  
+              "cur:PutReportDefinition"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+Using an existing CUR
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "cur:DescribeReportDefinitions"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+IMPORTANT
+
+The user configured on the cloud will need access to the objects in the S3 bucket configured on the CUR. If creating the CUR via the HPE Morpheus Enterprise UI, this should be done automatically. If an existing CUR report or existing S3 bucket was selected, ensure the user has permissions to access the objects in the configured S3 bucket. Alternatively, the **COSTING KEY** and **COSTING SECRET** can be used to configure a different user that has access to the S3 bucket.
+
+**v4.2.2 and Below**
+
+Begin by logging into the [AWS Billing Console](https://console.aws.amazon.com/billing/home?#/), then click Create report.
+
+![../../../_images/1billingConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6DE8607B-F2EC-42DB-ABD4-570B5A337D97-high.png)
+
+Include a name for your report and mark the box to “Include resource IDs”. HPE Morpheus Enterprise uses these resource IDs to map costs to various resources. Click Next.
+
+![../../../_images/2reportConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BAA21B68-8956-49FD-958B-97FC16160E26-high.png)
+
+On the following page, begin by identifying an S3 bucket to house reports. Click Configure near the top of the page and select an existing bucket or create a new one.
+
+![../../../_images/4chooseBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7D2040F4-3B7E-4CE5-82C7-2373F73C9F42-high.png)
+
+After identifying the bucket, you must mark the box to accept the default policy being applied to the bucket. Click Save.
+
+![../../../_images/5confirmPolicy.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5BDEF27D-8DC9-4554-A3D0-DAC2B41DEEEE-high.png)
+
+The default policy applied to the bucket is below:
+
+```
+```
+{  
+  "Version": "2008-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:GetBucketAcl",  
+        "s3:GetBucketPolicy"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name"  
+    },  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Principal": {  
+        "Service": "billingreports.amazonaws.com"  
+      },  
+      "Action": [  
+        "s3:PutObject"  
+      ],  
+      "Resource": "arn:aws:s3:::bucket-name/*"  
+    }  
+  ]  
+}
+```
+```
+
+After choosing a bucket, accepting the default policy, and saving the change, you’re brought back to the report delivery page. By default, CUR reports are saved to a folder at the path `my-report-name/date-folder`. If this bucket already contains CUR reports, you may want to specify a prefix path in the “Report path prefix” field. Outside of this field, use the default values as shown in the screenshot below, then click Next.
+
+![../../../_images/6completeDelivery.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DBCE8764-455B-450D-9C77-F16E527402D5-high.png)
+
+On the following page, make your final review and click Review and Complete. Following this, you will see your newly configured report in the list of CUR report(s).
+
+In addition, the AWS cloud user associated with the integration in HPE Morpheus Enterprise needs IAM policy permission to access Cost Explorer. Attach a policy like the one below to this cloud user:
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Id": "SomeID",  
+  "Statement": [  
+    {  
+      "Sid": "SomeStmtID",  
+      "Effect": "Allow",  
+      "Action": [  
+        "ce:DescribeReportDefinitions",  
+        "ce:DescribeCostCategoryDefinition",  
+        "ce:ListCostCategoryDefinitions"  
+      ],  
+      "Resource": [  
+        "*"  
+      ]  
+    }  
+  ]  
+}
+```
+```
+
+NOTE
+
+If the Cost Explorer permissions are granted at the master account level, the user will see all costs for each member account; if granted at the member account, only the costs for that member account are available.
+
+With the AWS console configuration steps complete, we can move back into HPE Morpheus Enterprise. Keep in mind it is only necessary to set up one AWS cloud for Costing since we process all records in the CUR report.
+
+Once back in HPE Morpheus Enterprise, add or edit the relevant AWS cloud integration (Infrastructure > Clouds > + ADD OR click the pencil icon in the row for the chosen AWS integration). Expand the Advanced Options drawer and complete the following fields:
+
+- **COSTING BUCKET:** The S3 bucket name
+- **COSTING REGION:** The region the bucket was created in
+- **COSTING FOLDER:** This is the report path prefix if you configured one earlier
+- **COSTING REPORT NAME:** The name given to your CUR report
+- **COSTING KEY:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Key ID for an IAM user with access
+- **COSTING SECRET:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS Secret Key for the IAM account whose Key ID you entered in the previous field
+- **LINKED ACCOUNT ID:** If the IAM user for this AWS cloud integration does not have access to the S3 bucket with the CUR data, enter the AWS account number that the IAM user from the above step resides in
+
+NOTE
+
+If the AWS cloud account is a GovCloud account, enter the COSTING KEY, COSTING SECRET, and LINKED ACCOUNT ID for the master commercial account your GovCloud account is associated with.
+
+![../../../_images/7morphConfig.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C5CA9E0D-35CE-4209-BAD7-B2091E1795EC-high.png)
+
+Save changes to your cloud integration.
+
+IMPORTANT
+
+It may take as long as one hour for HPE Morpheus Enterprise to process the next CUR report.
+
+### Global (Costing Aggregator Only) (v5.5.1+)
+
+Costing can be created for specific clouds individually, following the steps previously mentioned. If the same account is added multiple times, using different regions, the same CUR file is available to be selected (if the configured user has access). However, this can become a tedious process in needing to configure the CUR on each cloud added to HPE Morpheus Enterprise. However, HPE Morpheus Enterprise has a region of Global (Costing Aggregator Only), which can be chosen at the time of adding a cloud. This region is not designed for deploying workloads, it is here primarily for syncing costs. This means that the AWS account added as a cloud in HPE Morpheus Enterprise as a Global region can sync the cost for all the other regions of the same account added as clouds into HPE Morpheus Enterprise. When using AWS Organizations, if the AWS account added as a global region is the management account (formerly known as master account) and consolidated billing is enabled, costs for **all** accounts can be sync’d using the Global region. This means when any AWS and/or regions in the organization are added as clouds in HPE Morpheus Enterprise, the appropriate costs are applied to them automatically. It does require that **Costing** is enabled on the cloud to see the costs but a Costing Report does not need to be chosen. This enables the use of one cloud added as Global to sync all costs and apply to all AWS clouds added in HPE Morpheus Enterprise. Additionally, some costs in AWS are not region specific, for example the Global and No Region regions. These costs do not apply to the regions of the clouds added in HPE Morpheus Enterprise. With the Global region added as a cloud in HPE Morpheus Enterprise, you would be able to see these costs that are applicable to your accounts.
+
+## Costing and AWS GovCloud
+
+### About this task
+
+AWS GovCloud delivers Amazon public cloud infrastructure and features in a way that complies with U.S. government standards for security. GovCloud accounts are applied for and must be associated with a pre-existing standard AWS account and the usage and billing data for the GovCloud account is rolled up into that of the standard AWS account. For that reason, Amazon recommends creating a new standard account solely to house the GovCloud account if usage and billing must be tracked separately.
+
+Since GovCloud accounts do not have access to billing data directly, HPE Morpheus Enterprise must be able to access it through the associated standard account. You could do this by creating the HPE Morpheus Enterprise cloud integration through the standard account itself or by integrating the GovCloud account and supplying an Access Key and Secret Key for the standard account when configuring costing. When needed, add the additional credentials for the standard commercial account as described below:
+
+### Procedure
+
+1. Add a new AWS Cloud or edit an existing one
+2. Expand the Advanced Options section
+3. Complete the following fields in addition to other required fields needed to set up costing as described in the previous section: 
+
+   - COSTING KEY: The AWS Key ID for an IAM user with sufficient access who is associated with the standard commercial account
+   - COSTING SECRET: The AWS Secret Key for an IAM user with sufficient access who is associated with the standard commercial account
+   - LINKED ACCOUNT ID: The AWS account number for the standard commercial account in which the IAM user referenced in the prior bullets resides
+4. Save the changes to the AWS Cloud integration
+
+### Results
+
+When credentials are configured correctly, you will be able to select an existing Costing and Usage Report (CUR) from the appropriate S3 bucket if it already exists. If not, you can create one directly from the add/edit AWS Cloud modal in HPE Morpheus Enterprise.
+
+![../../../_images/8govcloudCosting.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AC3216FF-1BBA-4E49-808F-3B612BC88276-high.png)
+
+## AWS Reserved Instances and Savings Plans
+
+Amazon AWS public cloud offers Reserved Instances (RI) and Savings Plans, which allow organizations with consistent use patterns to reduce cloud spend significantly. HPE Morpheus Enterprise analyzes AWS cloud usage and spend, which allows it to make intelligent recommendations that can lead to significant savings. This data can be reviewed in the Reservation Recommendations and Savings Plan Recommendations tables on any AWS Cloud detail page (Infrastructure > Clouds > Selected Amazon Cloud).
+
+Savings Plans potentially offer greater than 70% savings in exchange for a commitment to consistent usage levels for a 1- or 3-year term. HPE Morpheus Enterprise provides Savings Plan guidance based on learned analytics; allowing you to analyze Savings Plans based on different term commitments and upfront costs to choose the best savings plan.
+
+![../../../_images/savingsPlan.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ED40B92B-4283-4FD5-9536-06034CC07CC0-high.png)
+
+Reserved Instances (RI) provide a discounted hourly rate and optional capacity reservation for EC2 instances. AWS billing automatically applies your RI-discounted rate when the attributes of EC2 instance usage match attributes of an active RI. HPE Morpheus Enterprise provides RI guidance based on learned analytics.
+
+![../../../_images/ri.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A93A0997-98E0-4177-91AF-1CC07D579581-high.png)
+
+To retrieve Reserved Instances and Savings Plans data, the user configured on the cloud will require access to **Cost Explorer**. Below is an example IAM policy with Cost Explorer access:
+
+### Cost Explorer Policy
+
+```
+```
+{  
+  "Version": "2012-10-17",  
+  "Statement": [  
+      {  
+          "Effect": "Allow",  
+          "Action": [  
+              "ce:*"  
+          ],  
+          "Resource": "*"  
+      }  
+  ]  
+}
+```
+```
+
+## AWS IAM Permissions
+
+Below are the AWS IAM Permissions required for HPE Morpheus Enterprise services.
+
+### autoscaling
+
+```
+```
+"autoscaling:AttachInstances",  
+"autoscaling:AttachLoadBalancerTargetGroups",  
+"autoscaling:CreateAutoScalingGroup",  
+"autoscaling:DeleteAutoScalingGroup",  
+"autoscaling:DeleteLaunchConfiguration",  
+"autoscaling:DeletePolicy",  
+"autoscaling:DescribeAutoScalingGroups",  
+"autoscaling:DescribeLaunchConfigurations",  
+"autoscaling:DescribeLoadBalancers",  
+"autoscaling:DescribePolicies",  
+"autoscaling:DetachInstances",  
+"autoscaling:PutScalingPolicy",  
+"autoscaling:UpdateAutoScalingGroup",
+```
+```
+
+### cloudformation
+
+```
+```
+"cloudformation:CreateStack",  
+"cloudformation:DeleteStack",  
+"cloudformation:DescribeStackEvents",  
+"cloudformation:DescribeStackResources",  
+"cloudformation:DescribeStacks",  
+"cloudformation:GetTemplate",  
+"cloudformation:UpdateStack",  
+"cloudformation:ValidateTemplate",
+```
+```
+
+### cloudwatch
+
+```
+```
+"cloudwatch:DeleteAlarms",  
+"cloudwatch:DescribeAlarms",  
+"cloudwatch:GetMetricStatistics",  
+"cloudwatch:PutMetricAlarm",
+```
+```
+
+### costexplorer
+
+```
+```
+"ce:*",
+```
+```
+
+### Cost and Usage Reports
+
+```
+```
+"cur:DescribeReportDefinitions",  
+"cur:PutReportDefinition",
+```
+```
+
+### ec2
+
+```
+```
+"ec2:AllocateAddress",  
+"ec2:AssignPrivateIpAddresses",  
+"ec2:AssociateAddress",  
+"ec2:AttachInternetGateway",  
+"ec2:AttachNetworkInterface",  
+"ec2:AttachVolume",  
+"ec2:AuthorizeSecurityGroupEgress",  
+"ec2:AuthorizeSecurityGroupIngress",  
+"ec2:CancelExportTask",  
+"ec2:CancelImportTask",  
+"ec2:CopyImage",  
+"ec2:CopySnapshot",  
+"ec2:CreateEgressOnlyInternetGateway",  
+"ec2:CreateImage",  
+"ec2:CreateInstanceExportTask",  
+"ec2:CreateInternetGateway",  
+"ec2:CreateKeyPair",  
+"ec2:CreateNatGateway",  
+"ec2:CreateNetworkAcl",  
+"ec2:CreateNetworkAclEntry",  
+"ec2:CreateNetworkInterface",  
+"ec2:CreateRoute",  
+"ec2:CreateSecurityGroup",  
+"ec2:CreateSnapshot",  
+"ec2:CreateSubnet",  
+"ec2:CreateTags",  
+"ec2:CreateVolume",  
+"ec2:CreateVpc",  
+"ec2:DeleteEgressOnlyInternetGateway",  
+"ec2:DeleteInternetGateway",  
+"ec2:DeleteKeyPair",  
+"ec2:DeleteNatGateway",  
+"ec2:DeleteNetworkAcl",  
+"ec2:DeleteNetworkAclEntry",  
+"ec2:DeleteNetworkInterface",  
+"ec2:DeleteRoute",  
+"ec2:DeleteSecurityGroup",  
+"ec2:DeleteSnapshot",  
+"ec2:DeleteSubnet",  
+"ec2:DeleteTags",  
+"ec2:DeleteVolume",  
+"ec2:DeleteVpc",  
+"ec2:DeregisterImage",  
+"ec2:DescribeAccountAttributes",  
+"ec2:DescribeAddresses",  
+"ec2:DescribeAvailabilityZones",  
+"ec2:DescribeClassicLinkInstances",  
+"ec2:DescribeClientVpnConnections",  
+"ec2:DescribeClientVpnEndpoints",  
+"ec2:DescribeConversionTasks",  
+"ec2:DescribeEgressOnlyInternetGateways",  
+"ec2:DescribeExportTasks",  
+"ec2:DescribeImageAttribute",  
+"ec2:DescribeImages",  
+"ec2:DescribeImportImageTasks",  
+"ec2:DescribeImportSnapshotTasks",  
+"ec2:DescribeInstances",  
+"ec2:DescribeInstanceStatus",  
+"ec2:DescribeInstanceTypes",  
+"ec2:DescribeInternetGateways",  
+"ec2:DescribeKeyPairs",  
+"ec2:DescribeNatGateways",  
+"ec2:DescribeNetworkAcls",  
+"ec2:DescribeNetworkInterfaceAttribute",  
+"ec2:DescribeNetworkInterfaces",  
+"ec2:DescribeRegions",  
+"ec2:DescribeRouteTables",  
+"ec2:DescribeSecurityGroupReferences",  
+"ec2:DescribeSecurityGroups",  
+"ec2:DescribeSnapshotAttribute",  
+"ec2:DescribeSnapshots",  
+"ec2:DescribeStaleSecurityGroups",  
+"ec2:DescribeSubnets",  
+"ec2:DescribeTags",  
+"ec2:DescribeTransitGateways",  
+"ec2:DescribeTransitGatewayVpcAttachments",  
+"ec2:DescribeVolumeAttribute",  
+"ec2:DescribeVolumes",  
+"ec2:DescribeVolumeStatus",  
+"ec2:DescribeVpcAttribute",  
+"ec2:DescribeVpcClassicLink",  
+"ec2:DescribeVpcClassicLinkDnsSupport",  
+"ec2:DescribeVpcEndpoints",  
+"ec2:DescribeVpcEndpointServices",  
+"ec2:DescribeVpcPeeringConnections",  
+"ec2:DescribeVpcs",  
+"ec2:DescribeVpnGateways",  
+"ec2:DetachInternetGateway",  
+"ec2:DetachNetworkInterface",  
+"ec2:DetachVolume",  
+"ec2:DisassociateAddress",  
+"ec2:GetPasswordData",  
+"ec2:ImportImage",  
+"ec2:ImportInstance",  
+"ec2:ImportKeyPair",  
+"ec2:ImportSnapshot",  
+"ec2:ImportVolume",  
+"ec2:ModifyImageAttribute",  
+"ec2:ModifyInstanceAttribute",  
+"ec2:ModifyNetworkInterfaceAttribute",  
+"ec2:ModifySnapshotAttribute",  
+"ec2:ModifySubnetAttribute",  
+"ec2:ModifyVolumeAttribute",  
+"ec2:RebootInstances",  
+"ec2:RegisterImage",  
+"ec2:ReleaseAddress",  
+"ec2:ReplaceNetworkAclAssociation",  
+"ec2:ReplaceNetworkAclEntry",  
+"ec2:ResetImageAttribute",  
+"ec2:ResetInstanceAttribute",  
+"ec2:ResetNetworkInterfaceAttribute",  
+"ec2:ResetSnapshotAttribute",  
+"ec2:RevokeSecurityGroupEgress",  
+"ec2:RevokeSecurityGroupIngress",  
+"ec2:RunInstances",  
+"ec2:StartInstances",  
+"ec2:StopInstances",  
+"ec2:TerminateInstances",  
+"ec2:UnassignPrivateIpAddresses",  
+"ec2:UpdateSecurityGroupRuleDescriptionsEgress",
+```
+```
+
+### eks
+
+```
+```
+"eks:*",
+```
+```
+
+### elasticloadbalancing
+
+```
+```
+"elasticloadbalancing:AddTags",  
+"elasticloadbalancing:ApplySecurityGroupsToLoadBalancer",  
+"elasticloadbalancing:AttachLoadBalancerToSubnets",  
+"elasticloadbalancing:CreateListener",  
+"elasticloadbalancing:CreateLoadBalancer",  
+"elasticloadbalancing:CreateRule",  
+"elasticloadbalancing:CreateTargetGroup",  
+"elasticloadbalancing:DeleteListener",  
+"elasticloadbalancing:DeleteLoadBalancer",  
+"elasticloadbalancing:DeleteRule",  
+"elasticloadbalancing:DeleteTargetGroup",  
+"elasticloadbalancing:DescribeLoadBalancers",  
+"elasticloadbalancing:DescribeRules",  
+"elasticloadbalancing:DescribeTargetGroups",  
+"elasticloadbalancing:ModifyListener",  
+"elasticloadbalancing:ModifyTargetGroupAttributes",  
+"elasticloadbalancing:RegisterTargets",  
+"elasticloadbalancing:SetSecurityGroups",  
+"elasticloadbalancing:SetSubnets",
+```
+```
+
+### elasticsearch
+
+```
+```
+"es:DescribeElasticsearchDomains",  
+"es:ListDomainNames",
+```
+```
+
+### iam
+
+```
+```
+"iam:ListGroups",  
+"iam:ListInstanceProfiles",  
+"iam:ListRoles",
+```
+```
+
+### kms
+
+```
+```
+"kms:Decrypt",  
+"kms:GenerateDataKey",
+```
+```
+
+### rds
+
+```
+```
+"rds:AddRoleToDBCluster",  
+"rds:AddTagsToResource",  
+"rds:ApplyPendingMaintenanceAction",  
+"rds:AuthorizeDBSecurityGroupIngress",  
+"rds:CopyDBClusterSnapshot",  
+"rds:CopyDBParameterGroup",  
+"rds:CopyDBSnapshot",  
+"rds:CreateDBCluster",  
+"rds:CreateDBClusterSnapshot",  
+"rds:CreateDBInstance",  
+"rds:CreateDBInstanceReadReplica",  
+"rds:CreateDBSecurityGroup",  
+"rds:CreateDBSnapshot",  
+"rds:DeleteDBCluster",  
+"rds:DeleteDBInstance",  
+"rds:DeleteDBSecurityGroup",  
+"rds:DeleteDBSnapshot",  
+"rds:DescribeAccountAttributes",  
+"rds:DescribeCertificates",  
+"rds:DescribeDBClusterParameterGroups",  
+"rds:DescribeDBClusterParameters",  
+"rds:DescribeDBClusters",  
+"rds:DescribeDBClusterSnapshotAttributes",  
+"rds:DescribeDBClusterSnapshots",  
+"rds:DescribeDBEngineVersions",  
+"rds:DescribeDBInstances",  
+"rds:DescribeDBLogFiles",  
+"rds:DescribeDBParameterGroups",  
+"rds:DescribeDBParameters",  
+"rds:DescribeDBSecurityGroups",  
+"rds:DescribeDBSnapshotAttributes",  
+"rds:DescribeDBSnapshots",  
+"rds:DescribeDBSubnetGroups",  
+"rds:DescribeEngineDefaultClusterParameters",  
+"rds:DescribeEngineDefaultParameters",  
+"rds:DescribeEventCategories",  
+"rds:DescribeEvents",  
+"rds:DescribeOptionGroupOptions",  
+"rds:DescribeOptionGroups",  
+"rds:DescribeOrderableDBInstanceOptions",  
+"rds:ListTagsForResource",  
+"rds:ModifyDBCluster",  
+"rds:ModifyDBClusterParameterGroup",  
+"rds:ModifyDBClusterSnapshotAttribute",  
+"rds:ModifyDBInstance",  
+"rds:ModifyDBParameterGroup",  
+"rds:ModifyDBSnapshotAttribute",  
+"rds:PromoteReadReplica",  
+"rds:RebootDBInstance",  
+"rds:RemoveTagsFromResource",  
+"rds:RestoreDBClusterFromSnapshot",  
+"rds:RestoreDBClusterToPointInTime",  
+"rds:RestoreDBInstanceFromDBSnapshot",  
+"rds:RestoreDBInstanceToPointInTime",  
+"rds:RevokeDBSecurityGroupIngress",  
+"rds:StartDBInstance",  
+"rds:StopDBInstance",
+```
+```
+
+### route53
+
+```
+```
+"route53:ChangeResourceRecordSets",  
+"route53:GetHostedZone",  
+"route53:ListHostedZones",  
+"route53:ListResourceRecordSets",
+```
+```
+
+### s3
+
+```
+```
+"s3:AbortMultipartUpload",  
+"s3:CreateBucket",  
+"s3:DeleteBucket",  
+"s3:DeleteObject",  
+"s3:DeleteObjectVersion",  
+"s3:GetBucketLocation",  
+"s3:GetBucketPolicy",  
+"s3:GetObject",  
+"s3:GetObjectVersion",  
+"s3:ListAllMyBuckets",  
+"s3:ListBucket",  
+"s3:ListBucketMultipartUploads",  
+"s3:ListBucketVersions",  
+"s3:ListMultipartUploadParts",  
+"s3:PutBucketPolicy",  
+"s3:PutObject",
+```
+```
+
+### Systems Manager
+
+```
+```
+"ssm:GetParameters",
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json b/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
new file mode 100644
index 0000000..ec05481
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+  "title": "Cannot Login",
+  "ordinal": 349,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.html",
+  "topic_cluster": {
+    "clustering_title": "Cannot Login",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556",
+        "clustering_title": "Cannot Login"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md b/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
new file mode 100644
index 0000000..d8cc326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ABF1416B-D30B-4AA6-AF1B-489885AC2556.md
@@ -0,0 +1,34 @@
+# Cannot Login
+
+## Forgot password
+
+If a user forgets their password, they can use the FORGOT PASSWORD? link on the login page. They can then enter their username or email address to send a reset password email to the email address defined on the user.
+
+If the default or user added SMTP server is not functioning or blocked, a System Admin user can impersonate that user and update their password.
+
+If the System Admin user password needs to be reset and the default or user added SMTP server is not functioning or blocked, please contact Morpheus support for assistance.
+
+## Sub-Tenant user cannot login after 3.4.0 upgrade
+
+HPE Morpheus Enterprise v3.4.0 added support for all subtenant users to login via the main tenant url using subtenant id or subdomain prefix, ie `tenantId\username` or `subdomain\username`.
+
+NOTE
+
+Tenant subdomains can be defined by editing Tenant settings and updating the SUBDOMAIN field.
+
+IMPORTANT
+
+Subtenant local users will no longer be able to login from main login url without using their subtenant id or subdomain prefix.
+
+The login requirements were added in v3.4.0 to allow subtenant users with identity source integration generated user accounts to be able to login to the master tenant, gain API and CLI access, and remove the requirement for usernames to be unique across all tenants.
+
+Previously subtenant users that had local/morpheus generated user accounts could login to their tenant via the master tenant url, while subtenant users that had identity source integration generated user accounts had to use the subtenant specific login url.
+
+In v3.4.0+ all subtenant users can login via the master tenant url by specifying their tenant id or subdomain prefix, `\`, then username. Subtenants can still use the tenant specific login url as well.
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `acme` and tenant id `58`. When logging in from the main login url, I now need to enter in: `acme\subuser` and the password. Alternatively the tenant ID can be used, ie `58\subuser`
+
+## Active Directory user suddenly cannot Login
+
+In HPE Morpheus Enterprise v3.4.0 and prior, OU changes in Active Directory can disable logins for AD users who had previously authenticated/have existing user accounts in HPE Morpheus Enterprise. If an Active Directory user cannot login to HPE Morpheus Enterprise after their OU was changed in AD, please contact Morpheus support for a resolution. The OU association for the user(s) can also be manually updated in the database. This issue is resolved in HPE Morpheus Enterprise versions 3.4.1 and higher.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json b/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
new file mode 100644
index 0000000..cc522b1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+  "title": "Execute Scheduling",
+  "ordinal": 124,
+  "parent_title": "Automation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.html",
+  "topic_cluster": {
+    "clustering_title": "Execute Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375",
+        "clustering_title": "Execute Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md b/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
new file mode 100644
index 0000000..32fac17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AC4D31AC-1CBE-4D99-8C2D-A621EEDB1375.md
@@ -0,0 +1,36 @@
+# Execute Scheduling
+
+Execute Scheduling creates time schedules for Jobs, including Task, Workflow and Backup Jobs. Jobs, which are discussed in greater detail in [another section](https://docs.morpheusdata.com/en/4.2.0/provisioning/jobs/jobs.html#jobs) of HPE Morpheus Enterprise docs, combine either a Task or Workflow with an Execute Schedule to run the selected Task or Workflow at the needed time. Backup Jobs are a special type of Job configured in the Backups section which also use Execute Schedules to time backup runs as needed.
+
+Schedules use CRON expressions, such as `0 23 * * 2` equalling `Executes every week on Tuesday at 23:00`. CRON expressions can easily be created by clicking the corresponding translation in the create or edit Execution Schedule modal below the Schedule field and selecting a new value.
+
+NOTE
+
+Execute Schedules CRON expressions should not include seconds or years. The days of the week should be numbered 1-7, beginning with Monday and ending with Sunday. SUN-SAT notation may also be used. For more on writing CRON expressions, many guides are hosted on the Internet including [this one](https://docs.oracle.com/cd/E12058_01/doc/doc.1014/e12030/cron_expressions.htm). HPE Morpheus Enterprise execution schedules support most cron syntax but certain more complex expressions may fail to evaluate and the execute schedule will not save. Additionally, some complex expressions may save and work correctly while the friendly written evaluation below the SCHEDULE field is not interpreted correctly. This is due to an issue with the underlying library used to build this feature and cannot easily be resolved at this time.
+
+## Create Execution Schedules
+
+NAME
+:   Name of the Execution Schedule
+
+    NOTE
+
+    When assigning Execution Schedules, the name value will appear in the selection drop-down. Using a name that references the time interval is often helpful
+
+DESCRIPTION
+:   Description of the Execution Schedule for reference in the Execution Schedules list
+
+VISIBILITY
+:   Master Tenant administrators may share Execute Schedules with Subtenants by setting the visibility to Public
+
+TIME ZONE
+:   The time zone for execution
+
+Enabled
+:   Check to enable the schedule. Uncheck to disable all associated executions and remove the schedule as an option for Jobs in the future
+
+SCHEDULE
+:   Enter CRON expression for the Execution Schedule, for example `0 0 * * *` equals `Every day at 00:00`
+
+SCHEDULE TRANSLATION
+:   The entered CRON schedule is translated below the SCHEDULE field. Highlighted values can be updated by selecting the value, and relevant options will be presented. The CRON expression will automatically be updated
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json b/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
new file mode 100644
index 0000000..e93bd5f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+  "title": "Network Connectivity",
+  "ordinal": 6,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.html",
+  "topic_cluster": {
+    "clustering_title": "Network Connectivity",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF",
+        "clustering_title": "Network Connectivity"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md b/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
new file mode 100644
index 0000000..b5f60e0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ACEB9448-EE82-43E6-A16B-7F34FBD4D7AF.md
@@ -0,0 +1,7 @@
+# Network Connectivity
+
+HPE Morpheus Enterprise primarily operates via communication with its Agent that is installed on all managed VMs or docker hosts. This is a lightweight agent responsible for aggregating logs and stats and sending them back to the client with minimal network traffic overhead. It also is capable of processing instructions related to provisioning and deployments instigated by the appliance server.
+
+The HPE Morpheus Enterprise Agent exists for both Linux and Windows-based platforms and opens NO ports on the guest operating system. Instead it makes an outbound SSL (HTTPS/WSS) connection to the appliance server. This is what is known as the `appliance url` during configuration (in Administration > Settings). When the Agent is started it automatically makes this connection and securely authenticates. Therefore, it is necessary for all VMs and docker based hosts that are managed by HPE Morpheus Enterprise to be able to reach the appliance server IP on port 443.
+
+HPE Morpheus Enterprise has numerous methods to execute Agent installation, including zero open port methods.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json b/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
new file mode 100644
index 0000000..bc09e9e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+  "title": "Overview",
+  "ordinal": 275,
+  "parent_title": "Tenants",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md b/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
new file mode 100644
index 0000000..a6c325a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.md
@@ -0,0 +1,11 @@
+# Overview
+
+A Tenant in HPE Morpheus Enterprise is an isolated environment with unique users and workloads. The Master Tenant is the default Tenant in HPE Morpheus Enterprise, created upon installation. All other Tenants outside of the Master Tenants are Subtenants. These terms are useful in differentiating the Master Tenant (which has a few special privileges) from Subtenants for the sake of discussion but within the product, all Tenants are known simply as Tenants.
+
+- The Master Tenant is the default Tenant created during the installation of HPE Morpheus Enterprise
+- All Tenants created after installation are Subtenants. Only one Master Tenant can exist
+- The first layer of new Tenants (subtenants) is created from the Master Tenant. Created Tenants may have Tenants of their own
+- Tenants are isolated environments with unique users, workloads, and Groups
+- The Master Tenant can share or assign its resources to Subtenants. Subtenants may only assign resources to its first layer of children Tenants
+- Subtenants cannot see resources from other Subtenants
+- Subtenants can only access Master Tenant resources that have been set to Public visibility or specifically assigned to the Subtenant from a higher level Tenant
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json b/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
new file mode 100644
index 0000000..b24e728
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+  "title": "Remote Storage",
+  "ordinal": 456,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A",
+        "clustering_title": "Remote Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md b/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
new file mode 100644
index 0000000..c001297
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD4869F0-8B72-41F7-8E27-E651CCD6994A.md
@@ -0,0 +1,14 @@
+# Remote Storage
+
+Table 1. Remote Storage
+
+        | S.No | Topic / Symptom | Additional Details | Common Checks | Log Files | Comments |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Failure to Integrate HPE Alletra MP Plugin | Issues during plugin loading or integration of the HPE Alletra MP plugin in the Morpheus Enterprise environment. | - Confirm that the plugin `.jar` file is properly loaded as per section 5.2 “Adding HPE BMaaS Integration”. - Check if the correct credentials and URL for the storage array are used. | - **Plugin Logs**: Look for errors during plugin loading. - **System Logs**: Check for authentication or configuration failures. | - Ensure compatibility between the plugin version and Morpheus Enterprise. - Network/firewall issues may prevent communication with the storage array. |
+| 2 | Storage Server Creation Failure | Failure when adding a new storage server (URL, credentials, or type mismatch). | - Verify the URL and credentials for accessing the storage array. - Ensure the correct type (“HPE Alletra Block Storage HVM”) is selected. | - **Storage Server Logs**: Check for error messages related to server creation (authentication issues, network problems). | - An incorrect URL or credentials can prevent server creation. - Make sure the storage server is accessible and reachable from the Morpheus interface. |
+| 3 | Datastore Creation Failure | Issues while creating a datastore, such as selecting an incorrect storage server, or specifying incompatible resource pools or protocols. | - Verify that the storage server was created successfully. - Ensure correct datastore type and resource pool selection. - Ensure "FC" is selected for protocol. | - **Datastore Logs**: Check for errors when trying to create the datastore (incorrect type, wrong resource pool). | - Mismatched storage configuration or resource pool selection can lead to datastore creation failures. - Confirm network configurations for FC protocol. |
+| 4 | Volume Creation Issues | Errors when creating volumes, including failure to assign the correct size, volume type (replicated/unreplicated), or datastore. | - Ensure the storage server is selected correctly. - Verify the volume size and type are correct. - Confirm the datastore is properly associated. | - **Volume Logs**: Errors related to volume creation (incorrect parameters, missing datastore). | - Volume size can only be increased - check the requirements. - Ensure correct replication type (CPP/APP) based on the storage array setup. |
+| 5 | Volume Deletion Failure | Unable to delete volumes due to them being attached to servers or due to incorrect permission settings. | - Confirm the volume is detached from all servers. - Ensure you have the necessary permissions to delete the volume. | - **Volume Deletion Logs**: Look for errors related to detachment or permission issues during deletion. | - Volumes can only be deleted once detached. - Ensure no active processes are using the volume. |
+| 6 | Volume Resize Failure | Unable to resize a volume, typically due to a lack of rescan on the server OS or exceeding size limits. | - Confirm the server OS has rescanned the volume. - Ensure the new size does not exceed any system or storage limits. | - **Volume Resize Logs**: Look for errors when attempting to resize (e.g., "resize failed" messages). | - Resize operations are only allowed for volume increases, not reductions. - Ensure the OS is aware of the new size after the resize. |
+| 7 | Volume Consumption Issues During Provisioning | Difficulty attaching volumes during instance provisioning (shared/unshared, existing/new, replicated/unreplicated). | - Ensure the correct volume type (shared/unshared) is specified. - Verify replication settings (CPP/APP) are correct. - Check if the volume exists and is accessible. | - **Provisioning Logs**: Check for errors related to volume attachment (invalid volume, replication mismatch). | - Volumes must be properly configured before provisioning. - Shared volumes should be attached to all servers within the instance. |
+| 8 | FC Protocol Issues | Issues with FC protocol during volume creation or consumption (e.g., failed attachments or slow response). | - Check if the storage server and datastore are properly configured for FC. - Confirm FC switches and network paths are properly set up. | - **Fibre Channel Logs**: Look for errors indicating FC connectivity or protocol issues. | - FC issues may be related to network misconfigurations or cable/connectivity problems. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json b/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
new file mode 100644
index 0000000..4b2e16c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+  "title": "Jobs",
+  "ordinal": 90,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html",
+  "topic_cluster": {
+    "clustering_title": "Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB",
+        "clustering_title": "Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md b/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
new file mode 100644
index 0000000..2a5fe90
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.md
@@ -0,0 +1,12 @@
+# Jobs
+
+Jobs are for scheduled execution of Automation Tasks and Workflows. Jobs can be set to execute on a schedule, at one specific point in time, and/or execute manually (on-demand). Jobs are linked to existing Tasks or Workflows, and allow for custom configuration options. Jobs can be associated with Instances, Servers, or have no association, such as a job for an SSH task.
+
+Jobs allow for scheduled execution of nearly anything as Tasks Types include Bash, Powershell, HTTP/API, Ansible, Chef, Puppet, Groovy, Python, jRuby, Javascript, and library scripts and templates, which can be configured for resource, remote, or local execution targets. If you need something to execute on a schedule, HPE Morpheus Enterprise Jobs can deliver.
+
+Jobs are configured in the `JOBS` tab, and the `JOB EXECUTIONS` tab contains Job execution history with result output.
+
+**Subtopics**  
+
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-101B0634-4367-4B11-ACA0-923AC1CA635E.html)**
+- **[Job Executions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json b/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
new file mode 100644
index 0000000..3309857
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+  "title": "3Par",
+  "ordinal": 519,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html",
+  "topic_cluster": {
+    "clustering_title": "3Par",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288",
+        "clustering_title": "3Par"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md b/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
new file mode 100644
index 0000000..16769ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.md
@@ -0,0 +1,32 @@
+# 3Par
+
+## Adding 3Par Storage Server
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select 3Par
+
+   URL
+   :   URL Of 3Par Server Example : `https://192.168.190.201:8008`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+5. Select SAVE CHANGES
+
+### Results
+
+The 3Par Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json b/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
new file mode 100644
index 0000000..9a9bfa8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+  "title": "Core Functionality",
+  "ordinal": 40,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.html",
+  "topic_cluster": {
+    "clustering_title": "Core Functionality",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59",
+        "clustering_title": "Core Functionality"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md b/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
new file mode 100644
index 0000000..7c700c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ADDCF3D8-0D72-434F-BDB2-ADF363C66B59.md
@@ -0,0 +1,8 @@
+# Core Functionality
+
+**Subtopics**  
+
+- **[Morpheus Discovery](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html)**
+- **[Morpheus Agent](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-91FC2F9F-A3F2-49DA-8C85-D3F634F36209.html)**
+- **[Communication Data](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2EC9F4F8-8A77-4259-958F-7DC5EE782A2E.html)**
+- **[VMware Support Statement](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json b/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
new file mode 100644
index 0000000..c09af0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+  "title": "Integration Guides",
+  "ordinal": 374,
+  "parent_title": "Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AE27985B-5909-407F-A105-5B0574715D13.html",
+  "topic_cluster": {
+    "clustering_title": "Integration Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AE27985B-5909-407F-A105-5B0574715D13",
+        "clustering_title": "Integration Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md b/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
new file mode 100644
index 0000000..92c1d1b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AE27985B-5909-407F-A105-5B0574715D13.md
@@ -0,0 +1,19 @@
+# Integration Guides
+
+**Subtopics**  
+
+- **[Automation Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html)**
+- **[Backups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2DEB33CC-132A-494C-B242-CA09B02E9333_2.html)**
+- **[Clouds](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA_2.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A75681BD-B103-4441-AAD7-E1F848FFE56E.html)**
+- **[Deployment](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html)**
+- **[DNS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0429DE80-5EF4-4D9F-B617-CB41D31DE60E.html)**
+- **[Identity Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A586E426-9C40-4FD0-B749-7E962F9F04C4.html)**
+- **[ITSM](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4F4F8735-4673-4408-BDA3-C295F2A88174.html)**
+- **[Load Balancers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-563347AC-C86B-4AC7-BF58-B80A3201662F.html)**
+- **[Logs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8E6A77CF-6AED-4725-BD4B-566E2FA357DB_2.html)**
+- **[Monitoring](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B4134705-AFEC-46A8-92BD-5723ABF491AA_3.html)**
+- **[Networking Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html)**
+- **[Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html)**
+- **[Supported Integration Versions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6D9C8CF5-C73F-47D1-9D81-6548E69F00D8.html)**
+- **[Trust](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3559161C-E53A-419A-B7E5-663F1440004F.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json b/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
new file mode 100644
index 0000000..dae2f9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+  "title": "MySQL Too many connections error",
+  "ordinal": 352,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.html",
+  "topic_cluster": {
+    "clustering_title": "MySQL Too many connections error",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1",
+        "clustering_title": "MySQL Too many connections error"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md b/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
new file mode 100644
index 0000000..f96a623
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AE6ACD69-CAB1-4DDF-A57F-6C261255B6D1.md
@@ -0,0 +1,57 @@
+# MySQL Too many connections error
+
+If you see the following error in the HPE Morpheus Enterprise UI logs:
+
+```
+```
+SqlExceptionHelper - Data source rejected establishment of connection,  message from server: "Too many connections"
+```
+```
+
+it means the number connections between HPE Morpheus Enterprise application and mysql have reached the max\_connections limit set in mysql (default is 151), or the max\_active setting, which limits the number of connections on the HPE Morpheus Enterprise end (default is 150), and the limit needs to be raised, either in HPE Morpheus Enterprise or mysql, or both depending on the number of connections and configuration.
+
+NOTE
+
+The max\_connections setting in mysql and the maximum used connections between an app node and mysql can be viewed in the HPE Morpheus Enterprise ui in the Administration - Health section under Database.
+
+IMPORTANT
+
+In Single HPE Morpheus Enterprise app node configurations, the `max_active` setting on the app node must be less than the `max_connections` setting in mysql.
+
+IMPORTANT
+
+In HA configurations, the `max_active` setting is per app node, and the `max_connections` setting in mysql must be greater than all app nodes `max_active` values combined, ie `(max_active` \* $number\_of\_app\_nodes) <= max\_connections``.
+
+## HPE Morpheus Enterprise `max_active` setting
+
+Edit `/etc/morpheus/morpheus.rb` and add `mysql[‘max_active’] = $value` replacing `$value` with desired desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql. For example, to set max\_active at 150:
+
+```
+```
+mysql[‘max_active’] = 150
+```
+```
+
+Replacing 100 with the desired number of maximum connections allowed by HPE Morpheus Enterprise to mysql.
+
+Run `morpheus-ctl reconfigure` for the setting to be applied. Reconfigure will not restart the ui unless additional ram has been added to the appliance host since the previous reconfigure. To edit the max\_active without a reconfigure, update the `max_active` setting in `/opt/morpheus/conf/application.yml`. Please note the default setting of 150 will be applied upon the next reconfigure unless `max_active` is defined as instructed above in the `morpheus.rb` file.
+
+## mysql `max_connections` setting
+
+IMPORTANT
+
+Customers are responsible for configuring and maintaining external databases used by HPE Morpheus Enterprise. This explains how to set the `max_connections` setting, but the value for the setting needs to be established by a customers qualified db admin.
+
+In mysql prompt,
+
+run `mysql> SET GLOBAL max_connections = $value;`
+
+This will immediately write the variable, however it is only a temporary setting that will be overwritten upon restart of the mysql service.
+
+To persist the `max_connections` setting, edit my.cnf, and add `max_connections = $value` replacing `$value` with desired value, ie to set max\_connections at 300 in in my.cnf, add:
+
+```
+```
+max_connections = 300
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.json b/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
new file mode 100644
index 0000000..c78c1ee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+  "title": "Role Types",
+  "ordinal": 294,
+  "parent_title": "Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-AFA85086-2874-4303-8999-E919DF886C44.html",
+  "topic_cluster": {
+    "clustering_title": "Role Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-AFA85086-2874-4303-8999-E919DF886C44",
+        "clustering_title": "Role Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.md b/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
new file mode 100644
index 0000000..be60dc5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-AFA85086-2874-4303-8999-E919DF886C44.md
@@ -0,0 +1,31 @@
+# Role Types
+
+## Tenant Roles
+
+A Tenant based role (formerly called an Account based role) is used to ensure access control enforcement across an entire tenant with many sub-users. This allows the subtenant to manage their own set of internal user based roles without worrying master tenant involvement in setting them up. The master tenant is the only tenant able to create and manage these types of roles. When editing a Tenant, a singular tenant role can be assigned to the account. Users within the tenant can be assigned roles but those user based roles will never be able to supersede the level of access granted by the tenant role. This allows a super administrator the ability to restrict access at the department or organization level without having to worry about per user access control within said tenant.
+
+Tenant roles also have an additional section not in User based roles related to Cloud Access. Cloud Access allows the master tenant the ability to assign cloud integration resources to specific subtenants or groups of subtenants. An example would be granting access to a specific VMware cluster only to a subset of tenants using the tenant based role control.
+
+## User Roles
+
+User roles can be created by any tenant given permission at the tenant role level. These allow tenants to manage their own sets of users and their levels of access. They also allow tenants to control which users have access to specific “Groups” for provisioning into within HPE Morpheus Enterprise. Groups are not cross tenant and therefore need to be controlled within the individual tenant in HPE Morpheus Enterprise.
+
+Master tenant users are able to create a special type of user role called a multi-tenant user role. A multi-tenant user role is copied / duplicated down to all subtenants within HPE Morpheus Enterprise. These can be viewed as canned role templates available to new tenants when their account is first created. Any changes made to the main role are propagated down to the subtenants version of the shared role so long as the subtenant users have not previously adjusted/changed that role. The moment a subtenant makes adjustments to the shared role within their account, it is unlinked from the parent role and treated entirely independently. In order to relink the Role in the Subtenant, a Master Tenant user would have to edit the Role, uncheck MULTITENANT USER ROLE, save the Role, check MULTITENANT USER ROLE once again, then save the Role once again.
+
+Another note about user roles is that when a user role is copied down to a subtenant, the permission scopes cannot supersede the tenant’s assigned tenant role. If they do they are automatically downgraded when propagated to the specific tenant. Any changes made to the tenant role will automatically ensure roles within the tenant are downgraded appropriately.
+
+NOTE
+
+Master Tenant administrators may edit permissions for Roles in other Tenants by viewing the Tenant detail page (Administration > Tenants > Selected Tenant) and accessing the Roles tab. From there, select the Role to edit and make changes on the resulting Role detail page.
+
+## Multi-Tenant User Role Lock
+
+As discussed above, Multi-Tenant User Roles are made available within all Subtenants and can be thought of as ‘canned’ user role sets provided to the Subtenant. Master Tenant administrators can prevent changes to these ‘canned’ user roles by marking the box labeled ‘MULTITENANT LOCKED’ when creating or editing the role. In addition to preventing Subtenant administrators from modifying permissions of the role copied down to their Subtenant, this option also ensures Master Tenant administrators can propagate new changes to that role. Modification of the role by the subtenant (if allowed) breaks the link back to the Master Tenant and the copy of the role within the Subtenant will become its own unlinked role.
+
+NOTE
+
+Multi-tenant role lock applies only to permission sets on the Features, Report Types, Personas and VDI Pools tabs. Permissions in other tabs (such as Groups, Instance Types, Blueprints or Catalog Item Types) tabs are not locked. Similarly, changes made to the role on these tabs in the master tenant are not synced down.
+
+## Editing User Roles in other Tenants
+
+Administrators in the Primary Tenant have the unique ability to edit feature permissions for User Roles that exist within other Tenants (Subtenants). In order to view the Roles within the Tenant, navigate to the Tenant detail page (Administration > Tenants) and select the Roles tab. Click the pencil (✎) icon to the right of a Role in the list to edit basic information, such as the name and description of the Role. Click on the name of the Role to view its complete permission set and edit the permissions if desired. This will update the feature access rights of users in the selected Tenant which have the Role.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json b/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
new file mode 100644
index 0000000..3430f9c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+  "title": "Azure Stack",
+  "ordinal": 391,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Stack",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099",
+        "clustering_title": "Azure Stack"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md b/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
new file mode 100644
index 0000000..46d1026
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B015C973-8C54-4EDE-BDEA-DD475DD3A099.md
@@ -0,0 +1,300 @@
+# Azure Stack
+
+## Overview
+
+Azure Stack is Microsoft’s Azure Cloud for on-premises environments. Azure Stack contains the core Azure services, allowing organizations to take advantage of Azure’s offerings with the security, compliance, and financial benefits of hosting it in their own data-centers.
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Group Sync & Selection
+- Network Sync & Selection
+- Security Group Sync & Selection
+- Storage Account Sync & Selection
+- Marketplace Search and Provisioning
+- Remote Console
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- Availability Set Support
+- Azure Load Balancers
+- Azure Storage
+- Docker Host Provisioning & Management
+- Service Plan Sync
+- Pricing Sync with markup options
+- Cost Estimator
+
+Combine these features with public Azure and HPE Morpheus Enterprise can provide a single pane of glass and self service portal for managing instances scattered across both Azure offerings.
+
+## Requirements
+
+### Azure Stack Accessibility
+
+By default, the Azure Stack management url’s are not accessible from an external network. Port mappings and DNS must be configured for communication between the HPE Morpheus Enterprise Appliance and Azure Stack.
+
+IMPORTANT
+
+In order to communicate with Azure Stack, HPE Morpheus Enterprise must be able to reach the internal Azure Stack network. The Azure Stack Portal needs to be exposed to the HPE Morpheus Enterprise Appliances’ network with corresponding entries added to DNS.
+
+One option to expose the Internal Azure Stack network to the HPE Morpheus Enterprise Appliances network is to use the `Expose-AzureStackPortal.ps1` powershell script from <https://gallery.technet.microsoft.com/scriptcenter/Expose-the-Azure-Stack-7ef68b19>. An Azure Stack Port Mapping Tool is also available.
+
+Below is a sample output from the script for reference:
+
+```
+```
+[Admin Portal] Created port mappings on 10.30.23.120 to 192.168.102.8  
+[Admin Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Admin Portal] DNS: 10.30.23.120 - adminportal.local.azurestack.external adminmanagement.local.azurestack.external  
+[Tenant Portal] Created port mappings on 10.30.23.121 to 192.168.102.10  
+[Tenant Portal] Ports: 13011 30015 13001 13010 13021 13020 443 13003 12646 12647 12648 12649 12650 12495 13026 12499  
+[Tenant Portal] DNS: 10.30.23.121 - portal.local.azurestack.external management.local.azurestack.external  
+[Blob Storage] Created port mappings on 10.30.23.122 to 192.168.102.4  
+[Blob Storage] Ports: 80 443  
+[Blob Storage] DNS: 10.30.23.122  *.blob.local.azurestack.external  
+VERBOSE: DNS delegation/forwarding is optional, change the DNS records on MAS-DC01 manually (dnsmgmt.msc from Host).  
+[DNS Delegation] Created port mappings on 10.30.23.120 to 192.168.200.224  
+[DNS Delegation] Ports: 53 (TCP/UDP)  
+[DNS Delegation] DNS: local.azurestack.external NS 10.30.23.120  
+[DNS Delegation] Change records on MAS-DC01 manually `if` you plan to use DNS forwarding.  
+[DNS Delegation] Change records back to the original internal IPs before running this script again.  
+VERBOSE: App Service detected and external IPs specified, creating mappings.  
+[App Service API] Created port mappings on 10.30.23.123 to 192.168.102.17  
+[App Service API] Ports: 443  
+[App Service API] DNS: 10.30.23.123  api.appservice.local.azurestack.external  
+[App Service Apps] Created port mappings on 10.30.23.124 to 192.168.102.15  
+[App Service Apps] Ports: 80 443 21 990  
+[App Service Apps] DNS: 10.30.23.124  *.appservice.local.azurestack.external
+```
+```
+
+### Azure Stack Resources
+
+The following resources need to be created and configured inside Azure Stack for successful provisioning:
+
+- Resource Group(s)
+- Virtual Network(s)
+- Storage Account(s)
+- Network Security Group(s)
+
+  - Inbound ports open from HPE Morpheus Enterprise Appliance: 22, 5985, 3389
+  - Outbound ports open to HPE Morpheus Enterprise Appliance: 80, 443
+
+NOTE
+
+Proper Network and Network Security Group configuration is required for HPE Morpheus Enterprise agent install, communication, and remote console access. Other configurations, such as docker instances, will need the appropriate ports opened as well.
+
+### Required Credentials & Permissions
+
+Credentials to integrate HPE Morpheus Enterprise with Azure Stack are located in both the public Azure Portal and the Private Azure Stack Portal. The Azure Active Directory Application used must be an owner of the Azure Stack subscription.
+
+Azure Portal:
+:   - Azure Active Directory Application Credentials
+    - Directory ID
+    - Management URL
+    - Identity Resource URL
+    - Application ID
+    - Key Value
+
+Azure Stack Portal:
+:   - Azure Stack Subscription ID
+    - Active Directory App from Azure portal added as owner of the Azure Stack Subscription in Azure Stack.
+
+## Adding an Azure Stack Cloud
+
+### Configure
+
+#### Procedure
+
+1. In the HPE Morpheus Enterprise UI, navigate to Infrastructure  >  Clouds and Select + CREATE CLOUD
+2. Select AZURE STACK (PRIVATE) from the Clouds list and select NEXT
+3. In the Configure section, enter: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   IDENTITY URL
+   :   <https://login.microsoftonline.com>
+
+   MANAGEMENT URL\*
+   :   Azure AD Azure Stack Administrator app or Microsoft Azure Stack Administrator app url. Example: <https://adminmanagement.local.azurestack.external/>
+
+   IDENTITY RESOURCE URL
+   :   Azure AD Azure Stack Administrator App ID URI Example: <https://adminmanagement.xxxxxxx.onmicrosoft.com/4a80e607-4259-4ac6-83e2-2fabeaf2eh83>
+
+   BASE DOMAIN
+   :   This should match the base domain in your Management url. Example: local.azurestack.external
+
+   SUBSCRIPTION ID
+   :   Subscription ID from Azure Stack portal (this is different from the Subscription ID in you Azure portal used when configuring Azure Stack)
+
+   TENANT ID
+   :   This is the Directory ID from the Azure AD directory
+
+   CLIENT ID
+   :   Application ID of Azure AD app with Azure Stack permissions granted, and has been added as an owner of the Azure Stack subscription (in the Azure Stack portal).
+
+   CLIENT SECRET
+   :   Key Value of Application ID used above
+
+       NOTE
+
+       Once all credentials are entered and validated, the Location and Resource Group fields will populate.
+
+   Location
+   :   Select an Azure Stack region for the cloud to scope to. This typically will be “local”.
+
+   Resource Group
+   :   Select All or a single Resource Group to scope the cloud to. Selecting a single Resource Group will only sync resources in that Resource Group and disable Resource Group selection during provisioning. All will sync all resources and allow specifying the Resource Group during provisioning.
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise.
+4. The Azure Stack cloud is ready to be added to a group and saved. Additional configuration options available: 
+
+   NOTE
+
+   All fields and options can be edited after the Cloud is created.
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+5. Once all options are configured, select NEXT to add the cloud to a Group. 
+
+   GROUP
+   :   A Group must be specified or created for the new Cloud to be added to. Clouds can be added to additional Groups or removed from Groups after being created.
+
+   USE EXISTING
+   :   Add the new Cloud to an exiting Group in HPE Morpheus Enterprise .
+
+   CREATE NEW
+   :   Creates a new Group in HPE Morpheus Enterprise and adds the Cloud to the Group.
+6. Confirm all settings are correct and select COMPLETE. The Azure Stack Cloud will be added, and HPE Morpheus Enterprise will perform the initial cloud sync of: 
+
+   - Virtual Machines (if Inventory Existing Instances is enabled)
+   - Networks
+   - Virtual Images/Blueprints
+   - Network Security Groups
+   - Storage Accounts
+   - Marketplace Catalog
+   - Availability Sets
+
+   TIP
+
+   Synced Networks can be configured or deactivated from the Networks section in this Clouds detail page, or in the Infrastructure  >  Networks section.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json b/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
new file mode 100644
index 0000000..28c83f7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+  "title": "Scale Thresholds",
+  "ordinal": 122,
+  "parent_title": "Automation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.html",
+  "topic_cluster": {
+    "clustering_title": "Scale Thresholds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181",
+        "clustering_title": "Scale Thresholds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md b/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
new file mode 100644
index 0000000..7e9a0ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B1E8A4DA-E24C-4C01-9382-EC35D7182181.md
@@ -0,0 +1,55 @@
+# Scale Thresholds
+
+Scale Thresholds are pre-configured settings for auto-scaling Instances. When adding auto-scaling to an instance, existing Scale Thresholds can be selected to determine auto-scaling rules.
+
+## Creating Scale Thresholds
+
+### Procedure
+
+1. Navigate to Library > Automation > Scale Thresholds
+2. Select + ADD
+3. Populate the following:
+
+### Results
+
+NAME
+:   Name of the Scale Threshold
+
+AUTO UPSCALE
+:   Enable to automatically upscale per Scale Threshold specifications
+
+AUTO DOWNSCALE
+:   Enable to automatically downscale per Scale Threshold specifications
+
+MIN COUNT
+:   Minimum node count for Instance. Auto-scaling will not downscale below MIN COUNT, and will auto upscale if the MIN COUNT is not met)
+
+MAX COUNT
+:   Maximum node count for Instance. Auto-scaling will not upscale past MAX COUNT, and will auto downscale if MAX COUNT is exceeded.
+
+ENABLE MEMORY THRESHOLD
+:   Check to set auto-scaling by specified memory utilization threshold (%)
+
+MIN MEMORY
+:   Enter MIN MEMORY % for triggering downscaling.
+
+MAX MEMORY
+:   Enter MAX MEMORY % for triggering upscaling.
+
+ENABLE DISK THRESHOLD
+:   Check to set auto-scaling by specified disk utilization threshold (%)
+
+MIN DISK
+:   Enter MIN DISK % for triggering downscaling.
+
+MAX DISK
+:   Enter MAX DISK % for triggering upscaling.
+
+ENABLE CPU THRESHOLD
+:   Check to set auto-scaling by specified overall CPU utilization threshold (%)
+
+MIN CPU
+:   Enter MIN CPU % for triggering downscaling.
+
+MAX CPU
+:   Enter MAX CPU % for triggering upscaling.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json b/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
new file mode 100644
index 0000000..3fae143
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+  "title": "Apps",
+  "ordinal": 257,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.html",
+  "topic_cluster": {
+    "clustering_title": "Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B2113088-6A1D-4A43-A781-BD280C35FA69",
+        "clustering_title": "Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md b/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
new file mode 100644
index 0000000..35f5e79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B2113088-6A1D-4A43-A781-BD280C35FA69.md
@@ -0,0 +1,18 @@
+# Apps
+
+App monitors are very useful for seeing an aggregation of failures or impact based on a set of checks and groups. App monitors typically correlate to Apps provisioned from HPE Morpheus Enterprise Blueprints but can also be manually created and organized. They can be great for visualizing the customer impact a failure might have or even keeping up on a screen in a NOC. To create an App monitor:
+
+Name
+:   A friendly name for the new app monitor in HPE Morpheus Enterprise
+
+Description
+:   An optional description value to identify the app monitor
+
+Max Severity
+:   The maximum severity incident a failed app may create. This setting overrides check and group max severity settings
+
+Affects Availability
+:   When checked, this failed app impacts system-wide availability calculations
+
+App Checks
+:   Use the typeahead field to select as many checks as needed to complete the app monitor. Checks are created in Monitoring > Checks and must exist prior to creating the app monitor
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json b/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
new file mode 100644
index 0000000..e4deddc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+  "title": "Trust",
+  "ordinal": 236,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.html",
+  "topic_cluster": {
+    "clustering_title": "Trust",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B299B747-2692-4406-9FCD-760C2EFE1E65",
+        "clustering_title": "Trust"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md b/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
new file mode 100644
index 0000000..a7f9398
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B299B747-2692-4406-9FCD-760C2EFE1E65.md
@@ -0,0 +1,15 @@
+# Trust
+
+The Trust section is where credentials, SSH keypairs, and SSL certificates are stored. In addition, related integrations to outside technologies can be made in this section as well. Integration types include HPE Morpheus Enterprise Cypher and Hashicorp Vault for externalized credential storage. Continue onto the next section for more on standing up an external Cypher credential store.
+
+**Subtopics**  
+
+- **[Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html)**
+- **[OAuth 2.0 Credentials](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-139EC691-D4C3-4E3B-98E9-F108FF4E7A7F.html)**
+- **[Integrating Hashicorp Vault](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A0DC9F48-028D-4283-8572-FDD0A432E125.html)**
+- **[Installing and Integrating an External Cypher Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-52D18727-341E-4E46-A2C4-CC8F9C0E0F5D.html)**
+- **[Key Pairs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html)**
+- **[SSL Certificates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7D50ECE1-F97E-4C65-85A7-221570A50BCF.html)**
+- **[Add SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html)**
+- **[Delete SSL Certificate](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html)**
+- **[Trust Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json b/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
new file mode 100644
index 0000000..324341d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+  "title": "Add Workflow",
+  "ordinal": 114,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B379FDF9-2963-4336-AFC1-14372793FA70.html",
+  "topic_cluster": {
+    "clustering_title": "Add Workflow",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B379FDF9-2963-4336-AFC1-14372793FA70",
+        "clustering_title": "Add Workflow"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md b/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
new file mode 100644
index 0000000..98f263f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B379FDF9-2963-4336-AFC1-14372793FA70.md
@@ -0,0 +1,21 @@
+# Add Workflow
+
+## Procedure
+
+1. Select the Library link in the navigation bar
+2. Select Automation from the sub-navigation menu
+3. Click the Workflows tab to show the Workflows tab panel
+4. Click the + Add dropdown and select a Workflow type (Operational or Provisioning, see the section above for more on Workflow type differences)
+5. From the New Workflow Wizard input a name for the workflow
+6. Optionally input a description and a target platform
+7. Add Tasks and Inputs using the typeahead fields, Tasks must be added to the appropriate phases for Provisioning Workflows
+8. If multiple tasks are added to the same execution phase, their execution order can be changed by selecting the grip icon and dragging the task to the desired execution order
+9. For multi-Tenant environments, select Public or Private visibility for the Workflow
+10. For Operational Workflows, optionally mark “Allow Custom Config” from the Advanced Options section if needed. See the next section for more on this selection
+11. Click the SAVE CHANGES button to save
+
+## Results
+
+NOTE
+
+When setting Workflow visibility to Public in a multi-Tenant environment, Tenants will be able to see the Workflow and also execute it directly from the Workflows list (if it’s an Operational Workflow). They will not be able to edit or delete the Workflow.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json b/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
new file mode 100644
index 0000000..86433e4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+  "title": "Users",
+  "ordinal": 309,
+  "parent_title": "Users & User Groups",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html",
+  "topic_cluster": {
+    "clustering_title": "Users",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123",
+        "clustering_title": "Users"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md b/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
new file mode 100644
index 0000000..4e8f45d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.md
@@ -0,0 +1,183 @@
+# Users
+
+## Overview
+
+The Users page displays a list of all Users. The following fields are surfaced for each User:
+
+- Tenant
+- Display Name
+- Username
+- Email
+- Role
+
+Users which are grayed out in the list are currently inactive and cannot log in. From the Actions menu in each User row, the option is given to Impersonate the User, Edit, or Remove the User.
+
+In HPE Morpheus Enterprise 4.2.1 and higher, click on the hyperlinked Display Name of the User to see a page detailing their effective Role permissions. This is especially useful for Users in multiple Roles where it might otherwise be difficult to determine their exact rights. This page looks identical to a User Role create/edit page except none of the fields are editable. Edit the User Role permissions for the User if changes need to be made.
+
+NOTE
+
+Some User data created through an Identity Source integration (such as Active Directory) is not editable in HPE Morpheus Enterprise, as it is synced from the Identity Source.
+
+## Create User
+
+### About this task
+
+Users can be created from Administration > Users or Administration > Tenants > (selected Tenant) > Users tab`.
+
+NOTE
+
+Authorized Identity Source Users will be automatically created upon first sign in.
+
+To create a User:
+
+### Procedure
+
+1. Navigate to either Administration > Users or Administration > Tenants > Select a Tenant``.
+2. Select + CREATE USER.
+3. From the New User Wizard input: 
+
+   Username & Email
+   :   - First Name
+       - Last Name
+       - Username
+       - Email address
+
+   Receive Notifications
+   :   Enable to receive Provisioning and Policy email notifications.
+
+   Roles
+   :   Role(s) to be inherited by the user. If multiple roles are selected, the higher permission levels of one role will override the other role(s).
+
+   Password
+   :   Password must contain at least one uppercase letter, one lowercase letter, a number, and a symbol.
+
+   Enabled
+   :   If unchecked, the user will no longer be able to sign into HPE Morpheus Enterprise, but their user data will remain.
+
+   Password Expired
+   :   If enabled, the User will be forced to create a new password upon next login. The expired password cannot be used again.
+
+   Linux Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Linux Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+   Windows Settings
+   :   Creates a User with the supplied Username, Password and/or Key-pair on Windows Instances when “Create my User” is selected during provisioning, or a User Group is added to an Instance of which this HPE Morpheus Enterprise user is a member of.
+
+       IMPORTANT
+
+       Please ensure password entered is allowable by Windows.
+
+### Results
+
+NOTE
+
+Instance Resource Limits for a user are now configured through [Policies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3D3058F0-C2FE-4995-8D62-55A069D50709.html#GUID-B0152179-D5F5-49E3-9CDD-E6BD2573DC0F)
+
+1. Select SAVE CHANGES.
+
+## Edit User
+
+### About this task
+
+User settings can be edited from Administration > Users, Administration > Tenants > Select a Tenant > Userstab`, or from User Settings.
+
+NOTE
+
+Some User data from Users created via an Identity Source Integration such as Active Directory is not editable in HPE Morpheus Enterprise, as it is synced with the Identity Source.
+
+To edit a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Click ACTIONS on the row of the user to edit.
+4. Select EDIT in the ACTIONS dropdown.
+5. Make changes.
+6. Select SAVE CHANGES.
+
+### Results
+
+To edit a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to edit.
+5. Select **EDIT** in the ACTIONS dropdown.
+6. Make changes.
+7. Select SAVE CHANGES.
+
+## User Settings
+
+### About this task
+
+Additional settings for a User can be found in the User Settings section, including:
+
+- User Photo
+- Default Group
+- Default Cloud
+- API Access
+
+To access User Settings:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings
+
+### Results
+
+To edit the User you are currently logged in as from User Settings:
+
+1. Select your name in the header
+2. Select User Settings
+3. Make changes.
+4. Select SAVE.
+
+## API Access
+
+### About this task
+
+API and CLI Access Tokens can be regenerated from the User Settings section.
+
+To regenerate a CLI or API Access Token:
+
+### Procedure
+
+1. Select your name in the header
+2. Select User Settings.
+3. Select API ACCESS under the Windows Settings section.
+4. Select ACTIONS for the Client ID the token will be generated for.
+5. Select Regenerate.
+6. Copy the Generated Access Token. 
+
+   IMPORTANT
+
+   The Access Token will be masked after User Setting are saved.
+7. Select SAVE.
+
+## Delete User
+
+### About this task
+
+To delete a User from the Administration > Users Section:
+
+### Procedure
+
+1. Select the Administration link in the navigation bar.
+2. Select the Users link in the sub navigation bar.
+3. Select ACTIONS on the row of the user to delete.
+4. Select REMOVE in the ACTIONS dropdown.
+5. Confirm
+
+### Results
+
+To delete a User from the Administration > Tenants > Select a Tenant > Userstab`:
+
+1. Select the Administration link in the navigation bar.
+2. Select the Tenants link in the sub navigation bar.
+3. Select a Tenant
+4. Click **ACTIONS** on the row of the user to delete.
+5. Select **REMOVE** in the ACTIONS dropdown.
+6. Confirm
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
new file mode 100644
index 0000000..1370f94
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+  "title": "Ansible",
+  "ordinal": 376,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html",
+  "topic_cluster": {
+    "clustering_title": "Ansible",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC",
+        "clustering_title": "Ansible"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
new file mode 100644
index 0000000..77b216b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.md
@@ -0,0 +1,295 @@
+# Ansible
+
+## Overview
+
+Ansible is a configuration management engine that is rapidly growing in popularity in the IT and DevOPS community. While it lacks some of the benefits at scale that solutions such as Chef or Puppet offer. It is very easy to get started and allows engineers to develop tasks in a simplistic markup language known as YAML. HPE Morpheus Enterprise integrates with an existing repository of playbooks as the master in a master-slave Ansible architecture.
+
+HPE Morpheus Enterprise not only supports Ansible but greatly enhances Ansible to do things that it could not do in its native form. For example, Ansible can now be configured to run over the HPE Morpheus Enterprise agent communication bus. This allows playbooks to be run against instances where SSH/WinRM access may not be feasible due to networking restrictions or other firewall constraints. Instead it can run over the HPE Morpheus Enterprise Agent which only requires port 443 access back to the HPE Morpheus Enterprise appliance URL.
+
+This integration supports both Linux-based and Windows platforms for playbook execution and can also be configured to query secrets from HPE Morpheus Enterprise Cypher services (similar to Vault).
+
+## Requirements
+
+- Minimum Ansible Version Requirement is 2.7.x
+- For agentless non-commandbus, sshpass is required
+- For Windows non-agent command bus, pywinrm is required
+- `Integrations: Ansible` User Role Permission required for access to Ansible Details Pages and Ansible tabs in Groups and Clouds
+- Calling HPE Morpheus Enterprise Cypher secrets into Ansible scripts requires the Python `requests` module which is not part of the Python standard library. For Ubuntu 18.04 or 20.04 run `sudo apt install python-requests` or `sudo apt install python3-requests`, respectively. For RHEL/CentOS, run `sudo yum install python2-requests`
+
+NOTE
+
+Installing Ansible on the HPE Morpheus Enterprise appliance is a requirement. In some cases, this is handled automatically but in certain situations you may have to install manually. See the section below on [troubleshooting Ansible](https://docs.morpheusdata.com/en/latest/troubleshooting/Ansible_Troubleshooting.html) for installation steps.
+
+## Add Ansible Integration
+
+### Procedure
+
+1. Navigate to Library > Integrationsand select + New Integration
+2. Select Integration Type “Ansible”
+3. Populate the following fields: 
+
+   Name
+   :   Name of the Ansible Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Enabled by default
+
+   Ansible Git URL
+   :   https or git url format of the Ansible Git repo to use
+
+   Keypair
+   :   For private Git repos, a keypair must be added to HPE Morpheus Enterprise and the public key added to the git account.
+
+   Playbooks Path
+   :   Path of the Playbooks relative to the Git url.
+
+   Roles Path
+   :   Path of the Roles relative to the Git url.
+
+   Group Variable Path
+   :   Path of the Group Variables relative to the Git url.
+
+   Host Variables Path
+   :   Path of the Host Variables relative to the Git url.
+
+   Use Ansible Galaxy
+   :   Install roles defined in `requirements.yml`
+
+   Enable Verbose Logging
+   :   Enable to output verbose logging for Ansible task history
+
+   Use Morpheus Agent Command Bus
+   :   Enable for Ansible Playbooks to be executed via Morpheus Agent Command Bus instead of SSH
+4. Save Changes
+
+### Results
+
+Once you have completed this section and saved your changes you can set up a Cloud or Group to utilize this integration.
+
+## Ansible on Windows
+
+When executing Ansible playbooks on Windows platforms, a few requirements must be met:
+
+- `pywinrm` may need to be installed on the HPE Morpheus Enterprise Appliance via `pip install pywinrm`
+- An Ansible Integration must be scoped to a Group or Cloud for Ansible to execute on Windows, as HPE Morpheus Enterprise assumes Ansible local when no group or cloud is scoped to Ansible. The playbooks do not need to be executed solely in the Group or Cloud, one just needs to be scoped to an Ansible Integration for Ansible Windows to run properly.
+
+## Scope Ansible Integration to a Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Edit the target Cloud
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Cloud, a new “ANSIBLE” tab will appear on the Cloud details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Scope Ansible Integration to a Group
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Groups
+2. Edit the target Group
+3. Expand the Advanced Options section
+4. In the Config Management dropdown, select the Ansible Integration.
+5. Save Changes
+
+### Results
+
+Once an Ansible integration is added to a Group, a new “ANSIBLE” tab will appear on the Group details page, populated with the Ansible integrations Playbook and Roles, as well as an editable Inventory list.
+
+## Provisioning Options
+
+When provisioning Instances into a Cloud or Group with a Ansible Integration added, an Ansible section will appear in the Config section of the provisioning wizard. By default, Ansible is enabled, but can be disabled by expanding the Ansible section and unchecking Enable Ansible.
+
+Ansible Integration Provisioning options:
+
+Enable Ansible
+:   Select to bootstrap
+
+Ansible Group
+:   Ansible Inventory Group. Use existing group or enter a new group name to create a new group. Leaving this field blank will place instance in the “unassigned” inventory group.
+
+    NOTE
+
+    An instance can belong to multiple groups by separating group names with a comma
+
+Playbook
+:   Playbook(s) to run. The .yml extension is optional.
+
+## Running Playbooks
+
+Playbooks can also be run on all inventory groups, individual groups, or added as a task and ran with workflows.
+
+To run Ansible on all or a single inventory group, in the Ansible tab of the HPE Morpheus Enterprise Group page, select the Actions dropdown and click Run.
+
+In the Run Ansible modal, you can then select all or an individual group, and then all or a single Playbook, as well as add custom tags.
+
+Playbook’s can also be added as tasks to workflows in the Library > Automationsection, and then selected in the Automation pane during provisioning of new instances, when creating app blueprints, or ran on existing instances using the Actions  >  Run Workflow on the Instance or Host pages.
+
+## Using variables
+
+HPE Morpheus Enterprise variables can be used in playbooks.
+
+Use Case:
+:   Create a user as instance hostname during provisioning.
+    :   Below is the playbook. Add this playbook to a task and run it as a workflow on the instance.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['instance']['hostname'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['instance']['hostname'] }}` is the format of using HPE Morpheus Enterprise Variables
+
+    Create a user with a name which you enter during provisioning using a custom Instance type.
+    :   This instance type has a Text Input that provides a text box to enter a username. The fieldName of the Input in this case would be username. Below is the playbook.
+        :   ```
+            ```
+            ---  
+              - name: Add a user  
+                hosts: all  
+                gather_facts: false  
+                tasks:  
+                  - name: Add User  
+                    win_user:  
+                      name: "{{ morpheus['customOptions']['username'] }}"  
+                      password: "xxxxxxx"  
+                      state: present
+            ```
+            ```
+
+        NOTE
+
+        `{{ morpheus['customOptions']['username'] }}` will be the format.
+
+## Using Secrets
+
+Another great feature with using Ansible and HPE Morpheus Enterprise together is the built in support for utilizing some of the services that HPE Morpheus Enterprise exposes for automation. One of these great services is known as Cypher (please see documentation on [Cypher](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-25C0F475-27A2-4C0A-BF2B-76EE20F51F7A.html) for more details). Cypher allows one to store secret data in a highly encrypted way for future retrieval. Referencing keys stored in cypher in your playbooks is a matter of using a built-in lookup plugin for ansible.
+
+```
+```
+- name: Add a user  
+  win_user:  
+    name: "myusername"  
+    password: "{{ lookup('cypher','secret=password/myusername') }}"  
+    state: present
+```
+```
+
+By using the `{{ lookup('cypher','secret=password/myusername') }}` syntax. One can grab the value directly out of the key for use. This lookup plugin also supports a few other fancy shortcuts. In this above example the password/ mountpoint is capable of autogenerating passwords if they have not previously been defined and storing them within cypher for reference later.
+
+Another capability is accessing properties from within a key in cypher. The value of a key can also be a JSON object which can be referenced for properties within. For example:
+
+```
+```
+{{ lookup('cypher','secret=secret/myjsonobject:value') }}
+```
+```
+
+This would grab the value property off the nested json data stored within the key.
+
+Cypher is very powerful for storing these temporary or permanent secrets that one may need to orchestrate various tasks and workflows within Ansible.
+
+## Custom Inventory Entries
+
+With Morpheus it is possible to add custom inventory entries that exist outside of morpheus host/server entry. This is global across cloud or group and is done on the integration details page of the Ansible integration. To add a custom inventory entry navigate to Library > Integrations> (Your specific Ansible integration). Click on the `ACTIONS` button, then click `EDIT INVENTORY`. Inventory should be in the default Ansible ini format.
+
+![../../_images/ansible_inventory.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0099BB05-0B08-41BB-856E-5403C2315926-high.png)
+
+## Using Ansible over the HPE Morpheus Enterprise Agent Command Bus
+
+In many environments, there may be security restrictions on utilizing SSH or WinRM to run playbooks from an Ansible server on the appliance to a target machine. This could be due to being a customer network (in the environment of an MSP ), or various security restrictions put in place by tighter industries (i.e. Government, Medical, Finance).
+
+Ansible can get one in trouble in a hurry. It is limited in scalability due to its fundamental design decisions that seem to bypass concepts core to all other configuration management frameworks (i.e. Chef and Puppet). Because of its lack of an agent, the Ansible execution binary itself has to handle all the load and logic of executing playbooks on all the machines in the inventory of an Ansible project. This differs from other tools where the workload is distributed across the agents of each vm. Because of this (reaching out) approach, Ansible is very easy to get started with, but can be quite a bit slower as well as harder to scale up. However, HPE Morpheus Enterprise offers some solutions to help mitigate these issues and increase scalability while, at the same time improving security.
+
+### How does the HPE Morpheus Enterprise Agent Command Bus Work?
+
+One of the great things about HPE Morpheus Enterprise is it’s Agent Optional approach. This means that this functionality can work without the Agent, however the agent is what adds the security benefits being represented here. When an instance is provisioned (or converted to managed) within HPE Morpheus Enterprise, an agent can be installed. This agent opens a secure websocket back to the HPE Morpheus Enterprise appliance (over port 443). This agent is responsible for sending back logs, guest statistics, and a command bus for automation. Since it is a WebSocket, bidirectional communication is possible over a STOMP communication bus.
+
+When this functionality is enabled on an Ansible integration, a connection\_plugin is registered with Ansible of type morpheus and morpheus\_win. These direct bash or powershell commands, in their raw form, from Ansible to run over a HPE Morpheus Enterprise api. The Ansible binary sends commands to be executed as an https request over the API utilizing a one time execution lease token that is sent to the Ansible binary. File transfers can also be enacted by this API interface. When HPE Morpheus Enterprise receives these commands, they are sent to the target instances agent to be executed. Once they have completed a response is sent back and updated on the ExecutionRequest within HPE Morpheus Enterprise. Ansible polls for the state and output on these requests and uses those as the response of the execution. This means Ansible needs zero knowledge of a machines target ip address, nor its credentials. These are all stored and safely encrypted within HPE Morpheus Enterprise.
+
+It has also been pointed out that this execution bus is dramatically simpler than utilizing pywinrm when it comes to orchestrating Windows as the winrm configurations can be cumbersome to properly setup, especially in tightly secured Enterprise environments.
+
+## Using Ansible Galaxy
+
+HPE Morpheus Enterprise can use a `requirements.yml` file to define Ansible roles to download prior to running your playbook. Place `requirements.yml` into the root of your Git repository and make sure Use Ansible Galaxy is checked in the integration. Roles will be installed in the root of the repository if a directory is not defined in Roles Path.
+
+- Example requirements.yml:
+
+```
+```
+- src: https://github.com/geerlingguy/ansible-role-java  
+  name: java
+```
+```
+
+- Example playbook.yml:
+
+```
+```
+- hosts: all  
+  gather_facts: true  
+  roles:  
+    - java
+```
+```
+
+## Troubleshooting Ansible
+
+- When a workflow is executed manually, the Ansible run output is available in the Instance History tab. Select the `i` bubble next to the Ansible task to see the output. You can also see the run output in the ui logs in /var/log/morpheus/morpheus-ui/current​ which can be tailed by running `morpheus-ctl tail morpheus-ui`.
+- Verify Ansible is installed on the HPE Morpheus Enterprise Appliance.
+
+  Ansible should be automatically installed but certain OS or network conditions can prevent the automated install. You can confirm installation by running `ansible --version` in the HPE Morpheus Enterprise appliance, or by viewing the Ansible integration details page (Administration > Integrations > Select Ansible Integration). We also see it in the Ansible tab of a Group or Cloud scoped to Ansible, just run `--version` as ansible is already included in the command.
+
+  If Ansible is not installed, follow these instructions to install, or use your preferred installation method:
+
+  Ubuntu:
+
+  ```
+  ```
+  sudo apt-get install software-properties-common  
+  sudo apt-add-repository ppa:ansible/ansible  
+  sudo apt-get update  
+  sudo apt-get install ansible
+  ```
+  ```
+
+  CentOS:
+
+  ```
+  ```
+  sudo yum install epel-release  
+  sudo yum install ansible
+  ```
+  ```
+
+  Then create the working Ansible directory for HPE Morpheus Enterprise:
+
+  ```
+  ```
+  mkdir -p /opt/morpheus/.ansible/tmp  
+  chown -R morpheus-local. /opt/morpheus/.ansible  
+  chmod -R 775 /opt/morpheus/.ansible
+  ```
+  ```
+- Validate the git repo is authorizing and the paths are configured correctly.
+
+  The public and private ssh keys need to be added to the HPE Morpheus Enterprise appliance via “Infrastructure > Keys& Certs” and the public key needs to be added to the git repo via user settings. If both are set up right, you will see the playbooks and roles populate in the Ansible Integration details page.
+- The Git Ref field on playbook tasks is to specify a different git branch than default. It can be left to use the default branch. If your playbooks are in a different branch you can add the brach name in the Git Ref field.
+- When running a playbook that is in a workflow, the additional playbooks fields do not need to be populated, they are for running a different playbook than the one set in the Ansible task in the Workflow, or using a different Git Ref.
+- If you are manually running Workflows with Ansible tasks on existing Instances through Actions  >  Run Workflow​ and not seeing results, set the Provision Phase on the Ansible task to Provision​ as there may be issues with executing tasks on other phases when executing manually.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json b/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
new file mode 100644
index 0000000..5fb27ef
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+  "title": "User Photo",
+  "ordinal": 333,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B5387FE3-B36D-4924-B168-329B6E41D811.html",
+  "topic_cluster": {
+    "clustering_title": "User Photo",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B5387FE3-B36D-4924-B168-329B6E41D811",
+        "clustering_title": "User Photo"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md b/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
new file mode 100644
index 0000000..36ec146
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B5387FE3-B36D-4924-B168-329B6E41D811.md
@@ -0,0 +1,3 @@
+# User Photo
+
+Upload a custom image for your user avatar that is displayed in the top header and user administration sections. **Suggested Photo Dimensions: 128 x 128**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json b/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
new file mode 100644
index 0000000..43ba63c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+  "title": "Administration",
+  "ordinal": 273,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.html",
+  "topic_cluster": {
+    "clustering_title": "Administration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54",
+        "clustering_title": "Administration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md b/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
new file mode 100644
index 0000000..8f451c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B54430C0-BD4D-4BC5-80B5-1EE64456EF54.md
@@ -0,0 +1,16 @@
+# Administration
+
+There are several administrative integrations built into HPE Morpheus Enterprise that make it great to work with within any organization ranging from small to large. Especially, with its built in white label support and multitenancy capabilities, managed service providers have a wide range of capabilities when it comes to managing customer accounts and users.
+
+**Subtopics**  
+
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html)**
+- **[Identity Sources](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7C6154EA-09BC-4E68-8BAB-D784F0582440.html)**
+- **[Plans](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-09A31CD3-8237-4668-8509-A1C2EA9F3775.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1D25F7CB-F8A2-4AE7-83B2-AFD6B08A64D0.html)**
+- **[Users & User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56_2.html)**
+- **[Policies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html)**
+- **[Health](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9CE510A1-706F-4E58-9F34-B60ACE99B9A2.html)**
+- **[Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-00CE7A1B-7CBC-4227-B285-2E8E4FFC73B1.html)**
+- **[User Settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-758DC0EE-FB74-428D-9A35-6FCE6AA43D84.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json b/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
new file mode 100644
index 0000000..0c679ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+  "title": "Volume Consumption",
+  "ordinal": 447,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html",
+  "topic_cluster": {
+    "clustering_title": "Volume Consumption",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B637812E-A51A-4AD5-B6F1-5E5822709711",
+        "clustering_title": "Volume Consumption"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md b/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
new file mode 100644
index 0000000..fcdc1ec
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.md
@@ -0,0 +1,23 @@
+# Volume Consumption
+
+Consumption of volume is typically done through compute instance provisioning, where the user can specify volumes to attach to, whether existing volumes or new volumes to be created. It can also be done using the reconfigure action.
+
+## Instance Provisioning
+
+During instance provisioning, the user can specify volumes to be attached to the servers within the instance. There are various types of volumes user can specify.
+
+## Sharing
+
+Volumes can be shared or unshared (attached to a specific server only). Specifying a shared volume means a single volume is attached to all the servers within that instance. Specifying an unshared volume means a volume is created for each server within the instance and exported to the corresponding server.
+
+## Existing vs New
+
+The user can specify a new volume to be created or specify to attach to an existing volume. Existing volume is applicable only to shared volumes.
+
+## Replicated vs Unreplicated
+
+When creating new volumes, the user can specify that the volume is unreplicated or replicated. Depending on the storage array deployed and the HA configuration, replicated volumes can be specified as CPP (classic peer persistence) or APP (active peer persistence).
+
+**Subtopics**  
+
+- **[Using Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9ED69FBC-FFF6-47A7-86A1-A330063CB3A2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
new file mode 100644
index 0000000..d330708
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+  "title": "Overview",
+  "ordinal": 57,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
new file mode 100644
index 0000000..4428a55
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.md
@@ -0,0 +1,3 @@
+# Overview
+
+The HPE Morpheus Enterprise Analytics engine gives administrators the tools to break down costs and usage, then filter the results by relevant delineations including Groups, Clouds, Tenants or even tag values. Analytics dashboards can be organized into three primary categories based on their measurement intentions: costing, utilization, and workloads. Each dashboard type is discussed in further detail below.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json b/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
new file mode 100644
index 0000000..71ad77b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+  "title": "SolarWinds IPAM",
+  "ordinal": 515,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html",
+  "topic_cluster": {
+    "clustering_title": "SolarWinds IPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE",
+        "clustering_title": "SolarWinds IPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md b/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
new file mode 100644
index 0000000..175ccbe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.md
@@ -0,0 +1,90 @@
+# SolarWinds IPAM
+
+## Features
+
+- Automate static IP assignment across environments using Solarwinds IPAM
+- Network pool sync: Network pools can be set on networks in HPE Morpheus Enterprise for automated IP allocation and record creation
+- Optional Network Pool allocation and record sync. `Inventory Existing` option syncs all individual IP records and corresponding status. Inventory is not required for provisioning
+- Grid and list displays with IP record overlays and color coding for static, available, reserved and transient status
+- Manual IP Host record creation from Network Pool detail pages
+
+## Adding SolarWinds to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Click + ADD
+3. Select SolarWinds
+4. Enter in the following information 
+
+   Name
+   :   Name of the SolarWinds Integration in HPE Morpheus Enterprise
+
+   Enabled
+   :   Deselect to disable sync with the SolarWinds endpoint
+
+   URL
+   :   URL of the SolarWinds server, ex: `http://10.30.20.10:17778`
+
+   Username
+   :   Username of SolarWinds API User. See the NOTE box below for information on minimum rights requirements
+
+   Password
+   :   SolarWinds User password
+5. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+At minimum you will need credentials for a user with API and root-level propagating read access, as well as read/write access for target networks and domains. For a quicker solution, you can also use an account with the Power User role in situations where you aren’t concerned with providing only the minimum required access.
+
+## Consuming SolarWinds in HPE Morpheus Enterprise
+
+On saving your new integration, SolarWinds networks will be synced and can be viewed by navigating to Infrastructure  >  Network  >  IP POOLS. They’re also viewable from the detail section of the SolarWinds integration at Infrastructure  >  Network  >  INTEGRATIONS  >  (your SolarWinds integration)  >  NETWORK POOLS.
+
+![../../_images/networkpools.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4DA0027F-E1C3-4F28-80BC-929C5E44ADA2-high.png)
+
+Host records can also be viewed here by clicking on the name of a SolarWinds network.
+
+![../../_images/hostrecords.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-374CAAAE-F29E-46E2-93D5-F1B68E9A6477-high.png)
+
+NOTE
+
+HPE Morpheus Enterprise SolarWinds integration does not support zone record syncing despite the presence of the ZONES tab on the integration detail page. This is a UI feature carried over from other networking integrations and is not supported at this time.
+
+## Adding IP Pools to Networks
+
+### About this task
+
+HPE Morpheus Enterprise can automatically assign the next available SolarWinds IP in an IP/Network Pool and create the corresponding DNS records. HPE Morpheus Enterprise will also remove the records upon teardown. To enable this, add an SolarWinds IP/Network Pool to the Network Pool section on a Network(s).
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Networks
+2. Select a Network name and click EDIT
+3. In the NETWORK POOL typeahead field, search for and select the name of the selected IP/Network Pool. 
+
+   - Gateway, DNS, and CIDR must be populated for static/pool IP assignment
+   - Select ALLOW IP OVERRIDE, if desired, to allow selecting between DHCP, static IP address entry, and pool address selection at provision time
+   - Deselect DHCP server if a DHCP server will not be used on the network (only static and/or IP Pool IP assignment)
+4. Select SAVE CHANGES
+
+## Creating Host Records
+
+### Procedure
+
+1. Select a Network Pool from Infrastructure  >  Network  >  IP POOLS
+2. Click + ADD
+3. Enter the following 
+
+   HOSTNAME
+   :   Hostname for the record
+
+   IP ADDRESS
+   :   IP address for the Host Record
+4. Select SAVE CHANGES
+
+### Results
+
+![../../_images/createhost1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7ACA8930-1EBE-46C3-93A0-FF538FFF439B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json b/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
new file mode 100644
index 0000000..a71a5ce
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+  "title": "Features",
+  "ordinal": 175,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B6F5194C-290E-464F-A718-232984A6E8B5.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B6F5194C-290E-464F-A718-232984A6E8B5",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md b/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
new file mode 100644
index 0000000..a22f487
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B6F5194C-290E-464F-A718-232984A6E8B5.md
@@ -0,0 +1,6 @@
+# Features
+
+**Subtopics**  
+
+- **[Host Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6B3F1B8D-1909-436F-ACD9-E0E9AC5FCEF0.html)**
+- **[VM Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-6DDAE4B3-B4CF-4A8A-B4CF-344B695026F3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json b/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
new file mode 100644
index 0000000..06fb3a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+  "title": "vCloud Director",
+  "ordinal": 474,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.html",
+  "topic_cluster": {
+    "clustering_title": "vCloud Director",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779",
+        "clustering_title": "vCloud Director"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md b/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
new file mode 100644
index 0000000..9f7ecac
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B73068EC-E619-4EA2-B84B-D4941E1D1779.md
@@ -0,0 +1,314 @@
+# vCloud Director
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Datastores
+- Brownfield VM management and migration
+- Periodic Synchronization
+- Lifecycle Management and Resize
+- IP Pool Support
+- Multi-NIC Interfaces
+- Kubernetes and Docker
+- Proxy Support
+- Image Builder
+- Monthly estimated pricing and usage tracker
+- Custom plan discovery and utilization at provision time
+
+## Configuration
+
+### Add vCD Cloud From Infrastructure > Clouds
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select VCLOUD DIRECTOR from the Clouds list
+4. Select NEXT
+5. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   NOTE
+
+   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. You do not need both despite the fact that all four of those fields are indicated as required fields.
+
+   API URL
+   :   vCloud Director API Url
+       :   Example: `https://org.vcd.company.com`
+
+   CREDENTIALS
+   :   Authenticating a new vCD Cloud requires either a username and password combination OR an API token and Tenant. These may be locally entered (select Local Credentials), locally entered and stored securely for future use (select “username and password” or “api token, tenant” from within the “New Credentials” section), or a pre-existing credential set may be selected from the HPE Morpheus Enterprise secure credential store. Depending on the selection, additional fields will appear (or some may disappear) to facilitate your choice
+
+   USERNAME
+   :   vCD Organization Administrator or System Administrator User
+
+       - User must have an Organizational Administrator or System Administrator Role
+       - Username must be in the format of <name>@<org>
+       - When using a user with the System Administrator role, give the username in the format of <username>@system. Additionally, ensure this user has permission set correctly, such as to view objects created by the organization administrator if needed. Otherwise, things like catalogs and vApps created by the Organization Administrator might not be visible to HPE Morpheus Enterprise
+       - In some cases, it may not be advisable to use the system administrator user. This is because some environments will have API access turned off for the system administrator for security reasons as the user would be able to remove key pieces of infrastructure. If your system administrator user does have API access and you understand the risks, you can authenticate HPE Morpheus Enterprise with this user
+
+   PASSWORD
+   :   Password for the user indicated above
+
+   API TOKEN
+   :   A generated API token for the service account user
+
+   TENANT
+   :   The Tenant to which the service account user authenticates
+
+   ORG
+   :   Select Organization. Dropdown populates upon successful authorization.
+
+   VDC
+   :   Select VDC. Dropdown populates upon successful authorization.
+
+   API VERSION
+   :   Full version required which much be in the “xx.x” format. When applicable, do not drop a trailing “0” (Ex. `31.0`). HPE Morpheus Enterprise will attempt to discover the API version, which would make this field optional. However, vCD allows disabling of the API versions API. In such an environment, the user would need to specify the API version here
+
+   CATALOG
+   :   Optionally select a vCD catalog to store HPE Morpheus Enterprise artifacts or use the default “morpheus\_auto” catalog
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise
+
+   Enable Hypervisor Console
+   :   Mark to use VNC hypervisor console for the HPE Morpheus Enterprise console rather than the default SSH or RDP connection methods
+
+   Advanced Options
+
+   DOMAIN
+   :   Specify a default domain for instances provisioned to this Cloud.
+
+   SCALE PRIORITY
+   :   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+   APPLIANCE URL
+   :   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+   TIME ZONE
+   :   Configures the time zone on provisioned VM’s if necessary.
+
+   DATACENTER ID
+   :   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+   NETWORK MODE
+   :   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+   LOCAL FIREWALL
+   :   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+   SECURITY SERVER
+   :   Security Server setting is for Security Service Integrations such as ACI
+
+   TRUST PROVIDER
+   :   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+   STORAGE MODE
+   :   Single Disk, LVM or Clustered
+
+   BACKUP PROVIDER
+   :   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+   REPLICATION PROVIDER
+   :   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+   GUIDANCE
+   :   Enable Guidance recommendations on cloud resources.
+
+   COSTING
+   :   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+   DNS INTEGRATION
+   :   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+   SERVICE REGISTRY
+   :   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+   CONFIG MANAGEMENT
+   :   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+   CMDB
+   :   Select CMDB Integration to automatically update selected CMDB.
+
+   CMDB DISCOVERY
+   :   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+   CHANGE MANAGEMENT
+   :   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+   AGENT INSTALL MODE
+   :   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+       - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+   VDI GATEWAY
+   :   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+   CUSTOM LOGOS
+
+   When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+   INVENTORY OPTIONS
+
+   Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+   - Service Plans
+   - Resource Pools
+   - Networks
+   - Security Groups
+   - Datastores
+   - Folders
+
+   Provisioning Command
+
+   PROXY
+   :   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+   Bypass Proxy for Appliance URL
+   :   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+   NO PROXY
+   :   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+   USER DATA (LINUX)
+   :   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+6. Select NEXT
+7. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+8. Select NEXT
+9. Review and then Select COMPLETE
+
+## How to create vCloud Director templates for Morpheus
+
+### To create a Windows Template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build.
+
+#### Procedure
+
+1. Apply any service packs / updates to the operating system.
+2. Set the Network location to Private the below PowerShell will set the location. 
+
+   ```
+   ```
+   Get-NetConnectionProfile | Set-NetconnectionProfile -NetworkCategory private
+   ```
+   ```
+3. Configure WinRM to allow remote management and open the firewall. 
+
+   - To do this, under local computer Administrator, open a command prompt and run `winrm quickconfig`
+4. Install VMware tools
+5. Install .Net at least 4.5
+6. Enable remote PowerShell this can be done in PowerShell. 
+
+   ```
+   ```
+   Enable-PSremoting
+   ```
+   ```
+7. Shutdown the virtual machine and convert to a template. 
+
+   NOTE
+
+   Do not run sysprep
+
+### To create a Linux Centos template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install vmware tools
+6. Install git by running `yum install git`
+7. epel-release
+8. selinux set to permissive (enforced can cause problems with cloud-init)
+
+### To create a Linux Ubuntu template
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+#### Procedure
+
+1. Before installing the operating system setup a single `ext` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Ensure you have set a root password
+4. Install cloud-init by running `sudo apt install cloud-init`
+5. Install cloud-utils-growpart `sudo apt install cloud-utils`
+6. Install desired hypervisor drivers (Virto, Open-VM Tools)
+7. Install git by running `sudo apt install git`
+8. As Debian 9 includes network manager ensure this is disabled. Change the below file
+
+#### Results
+
+```
+```
+/etc/NetworkManager/NetworkManager.conf
+```
+```
+
+to the following:
+
+```
+```
+managed=false
+```
+```
+
+We also recommend disabling network manager and setting the network adapter to eth0 rather than the automatically assigned name. See a more detailed guide on VMware image prep [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware_templates.html?highlight=vmware%2520image%2520prep#creating-a-centos-rhel-7-image).
+
+To import your template into vCloud director you will need to login as either an administrator or organisation administrator.
+
+Once logged into vCloud director you will then need select `Manage Organizations` and then select your organization.
+
+From within the organisation click on `Catalogues` > select an existing catalogue or create a new catalogue.
+
+NOTE
+
+Please note once you connect HPE Morpheus Enterprise to your vCD environment, it will create a catalogue called Auto HPE Morpheus Enterprise. This is a working catalogue and is ignored by HPE Morpheus Enterprise when searching for images, so any images in the catalogue will not be synced into HPE Morpheus Enterprise
+
+Open the catalogue and select the import template from vCenter and then browse the data stores for your templates. Select your template and the type in a new name and description then check the copy template into vCloud director.
+
+Once you click ok the import process will begin. When the import has completed the template will appear in HPE Morpheus Enterprise within Library > Virtual Images
+
+If the image does not appear within the virtual images you may need to use the filters to filter the virtual images by the vmware ( vmdk / ovf / ova) type.
+
+You may also need to refresh the cloud. To do this go to Infrastructure  >  Clouds > select the vCloud Director cloud > selectRefresh.
+
+​
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.json b/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
new file mode 100644
index 0000000..da80deb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+  "title": "phpIPAM",
+  "ordinal": 508,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html",
+  "topic_cluster": {
+    "clustering_title": "phpIPAM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7496F21-B633-436F-850B-507E482F96F2",
+        "clustering_title": "phpIPAM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.md b/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
new file mode 100644
index 0000000..251c04e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7496F21-B633-436F-850B-507E482F96F2.md
@@ -0,0 +1,30 @@
+# phpIPAM
+
+## Configuration
+
+### Procedure
+
+1. Within phpIPAM dashboard, enable api in Administration > phpIPAMsettings > featuresettings. Toggle API switch to `on` and save.
+2. Go to Admin > API > create API key.
+3. Create unique App ID.
+4. Enable `read/write/admin` access under App Permissions.
+5. Under App Security select `SSL with User Token`.
+
+## Add phpIPAM integration to HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Network  >  Integrations
+2. Select + ADD > IPAM > phpIPAM
+3. Enter the following: 
+
+   - Name
+   - URL
+     :   Add `/api/` to end of URL ex. `http://10.30.20.196/api/`
+   - App ID
+     :   From phpIPAM API Key
+   - Username
+   - Password
+   - Enable or Disable SSL SNI Verification
+   - Enter Network Filter
+4. Select SAVE IPAM INTEGRATION
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json b/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
new file mode 100644
index 0000000..eca773b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+  "title": "Creating an HPE BMaaS Cloud",
+  "ordinal": 402,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an HPE BMaaS Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70",
+        "clustering_title": "Creating an HPE BMaaS Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md b/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
new file mode 100644
index 0000000..1c7e482
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B75849CE-88E1-40A5-BA3B-0AE8C47C9F70.md
@@ -0,0 +1,38 @@
+# Creating an HPE BMaaS Cloud
+
+## About this task
+
+Creating an HPE BMaaS Cloud integrates physical infrastructure into the Morpheus management plane, establishing a logical boundary for bare-metal resources to enable group-based policies and proxy configurations. This setup allows for onboarding HPE ProLiant servers for automated provisioning and lifecycle management.
+
+To create an **HPE BMaaS Cloud** in Morpheus for HPE ProLiant bare-metal operations, follow this procedure:
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds in the Morpheus interface.
+2. Click the + Add button.
+3. Locate and select the HPE BMaaS Cloud type as HPE Bare Metal (BMaaS), and then click Next.  
+   ![Create Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C875F0A7-EDDE-42E3-B87B-DE90F18B9A51-high.png)
+4. Enter the name, code, Labels, Location, and complete any additional required details for the cloud.   
+   ![Cloud Configure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0C50D8A2-3CA6-416E-AA73-0DA3FA82167B-high.png)
+5. **Optional:**  In Provisioning Command, select a Proxy for provisioned bare metal instances if required, then click Next.  
+   ![Provisioning Command](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-172BEA46-96D8-4D0D-83D8-B0D6428A0ED5-high.png)
+6. For the group, you may either select Use Existing or Create New: 
+
+   - To use an existing group, choose Use Existing and select the desired group from the drop-down list.   
+     ![Existing Group](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6EC50EB8-DE0B-43B4-A168-B43E3A87CAB5-high.png)
+   - To create a new group, select Create New and follow the on-screen prompts.   
+     ![Create New](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-213FFFF2-8183-4E33-A2A3-9437A433373E-high.png)
+7. Click Next to review your cloud configuration details, then click Complete to finalize cloud creation.
+
+   NOTE
+
+   By default, the Network Mode is set to Unmanaged for the created Bare metal cloud. If you need to use ArubaCX integration, modify the Bare metal cloud and set the Network Mode to the ArubaCX-Integration.
+
+## Results
+
+After completion, the newly created group appears in the list of groups.   
+![Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3917DB5B-D58F-4FFF-A06C-40BD5401CFE7-high.png)
+
+**Subtopics**  
+
+- **[Default Unmanaged Network Support](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2F776F04-B8E7-428D-823B-AB121DFE48AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json b/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
new file mode 100644
index 0000000..c63bc0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+  "title": "Templates",
+  "ordinal": 158,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.html",
+  "topic_cluster": {
+    "clustering_title": "Templates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9",
+        "clustering_title": "Templates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md b/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
new file mode 100644
index 0000000..b86da06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7DA13FA-788B-4429-8B62-D32D4C85D9C9.md
@@ -0,0 +1,11 @@
+# Templates
+
+Templates can be created directly in HPE Morpheus Enterprise and/or sourced from version control, depending on the type. They can be used to help users consume IaC technologies, generate configuration files, utilize scripts or store security scan packages. Once stored, they can be used with provisioned Instances, configured as part of Tasks or Workflows, or run regularly as part of security scan Jobs. Each section below discusses template types in greater detail.
+
+**Subtopics**  
+
+- **[Spec Templates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-127B939B-0C18-40CC-AC49-8DD0D58BE444.html)**
+- **[File Templates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0424B3D1-E018-49DD-B584-AEFE6CB4866D.html)**
+- **[Script Templates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-61826D87-6DAB-456B-8B0A-C2DE871B2E2C.html)**
+- **[Security Packages](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ED404402-F168-4635-ADEB-02609465196E.html)**
+- **[Cluster Packages](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7BD87211-4E8A-480C-A7B6-E502808743EC.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.json b/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
new file mode 100644
index 0000000..aab7455
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+  "title": "Automation Integrations",
+  "ordinal": 375,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B7E3F043-2330-4392-9803-B649558F488B.html",
+  "topic_cluster": {
+    "clustering_title": "Automation Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B7E3F043-2330-4392-9803-B649558F488B",
+        "clustering_title": "Automation Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.md b/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
new file mode 100644
index 0000000..4c70572
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B7E3F043-2330-4392-9803-B649558F488B.md
@@ -0,0 +1,10 @@
+# Automation Integrations
+
+**Subtopics**  
+
+- **[Ansible](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B47A4967-DCA3-45C4-B983-83CEB43711DC.html)**
+- **[Ansible Tower](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-573DCEB5-7585-4DAE-A53B-9A4734E4C8D9.html)**
+- **[Chef](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-826F09D8-C40B-483D-9CB5-CE504BD18810.html)**
+- **[Puppet](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html)**
+- **[Terraform](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html)**
+- **[vRealize Orchestrator](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9C6D79E5-A94A-4357-891C-D1D13AD5DCA7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json b/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
new file mode 100644
index 0000000..dc0db12
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+  "title": "Guidance",
+  "ordinal": 71,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html",
+  "topic_cluster": {
+    "clustering_title": "Guidance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B86C6485-C80C-480F-87B4-4352963D74A5",
+        "clustering_title": "Guidance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md b/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
new file mode 100644
index 0000000..8f200ed
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B86C6485-C80C-480F-87B4-4352963D74A5.md
@@ -0,0 +1,93 @@
+# Guidance
+
+## Overview
+
+The Operations  >  Guidance section shows recommendations for resource and cost optimization. By analyzing the CPU, RAM, and Storage activity of Instances and Hosts, HPE Morpheus Enterprise can recommend actions for sizing and power state. Guidance is customizable to show recommendations based on 30, 60, or 90 day periods, this dropdown toggle is visible on the Guidance list page (Operations > Guidance). Guidance thresholds are also customizable, they can be edited in Administration > Settings > Guidance.
+
+### Configuration
+
+#### About this task
+
+Guidance is configured per Cloud and is turned off by default.
+
+To turn on HPE Morpheus Enterprise Guidance for a Cloud:
+
+#### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Click EDIT
+3. Expand the Advanced Options section in the Edit Cloud modal
+4. In the Guidance dropdown, select Manual
+5. Click SAVE CHANGES
+
+#### Results
+
+Guidance recommendations will begin to appear in the guidance section when generated.
+
+NOTE
+
+It will take approximately seven days before HPE Morpheus Enterprise gathers sufficient data to make guidance recommendations.|morpheus| Guidance is significantly improved when the Agent is installed on provisioned workloads. When the Agent is not installed, HPE Morpheus Enterprise still makes a best effort to provide relevant guidance recommendations.
+
+Once Guidance has been turned on for a Cloud, HPE Morpheus Enterprise will determine if a guidance recommendation should be made once every 30 minutes. In the event that no recommendations can be made, no entry will be added to the list of suggested guidances. As the guidance list continues to grow, sorting and filtering may become necessary to focus on the recommendations that are relevant to the user at the time.
+
+It’s important to note that acting on recommendations is entirely manual at this time. In many cases, Morpheus provides one-click action to take the recommended steps but Guidance recommendations cannot be taken automatically. This is a feature that is being explored for a future update but has not been tagged for any specific release version at this time. In addition, it’s recommended that HPE Morpheus Enterprise Agent be installed to maximize the benefits of Guidance. While Guidance will still work without installing the Agent, the greatly-enhanced statistics provided by the Agent will significantly improve Guidance recommendations.
+
+To see more detail on a Guidance recommendation in your list, click on the (i) button at the far right side of each list row. This will open a detail modal that gives additional information on the Guidance entry. In some cases, such as with sizing and shutdown recommendations, the user can simply click the “EXECUTE” button to take the recommended action as shown below.
+
+![The execute button allows the user to immediately take action on a sizing recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6493DA77-2790-4079-9636-57D2B389DBCD-high.png)
+
+Other types of Guidance recommendations, such as reserve compute recommendations, must be taken in the cloud and Morpheus does not offer the execute button.
+
+![The execute button is not present on a reserve compute recommendation](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-88431DCD-48BE-4414-BC59-89F31565FE07-high.png)
+
+NOTE
+
+The IGNORE button will remove the recommendation from the UI. Subsequent recommendations of the same type will NOT display for the same object (VM, Cloud etc) again unless the original recommendation is resolved.
+
+### Recommendations
+
+To view and act on Guidance recommendations, navigate to Operations  >  Guidance.
+
+The Guidance list contains the following details:
+
+Severity Icon
+:   Indicates the severity of the recommended action.
+
+Type
+:   Recommended action Type
+
+Metric
+:   Guidance Metric used for recommended action.
+
+Action
+:   Recommended Action for the Instance or Host, such as “Reduce Host memory” or “Shutdown Instance”
+
+RESOURCE
+:   The Instance or Host targeted
+
+SAVINGS
+:   Shows projected Monthly Costs savings if recommended action is taken.
+
+DATE
+:   Date and Time stamp the recommended action was generated.
+
+Information Link
+:   Click to view details on the recommendation.
+
+NOTE
+
+Guidance Actions are not automatically triggered at this time.
+
+### Filters
+
+Search
+:   Search for Guidance recommendations
+
+Type
+:   Filter by Sizing or Shutdown Guidance Types.
+
+Severity
+:   Filter by Guidance Severity of All, Info, Warning, or Critical.
+
+Metric
+:   Filter by All, Memory, CPU, or Power Guidance Metrics.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json b/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
new file mode 100644
index 0000000..b43f36d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+  "title": "AWS Route53",
+  "ordinal": 484,
+  "parent_title": "DNS",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.html",
+  "topic_cluster": {
+    "clustering_title": "AWS Route53",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3",
+        "clustering_title": "AWS Route53"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md b/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
new file mode 100644
index 0000000..3ca30c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B882BBCA-C655-44F1-B570-D8902CDAE0D3.md
@@ -0,0 +1,78 @@
+# AWS Route53
+
+## Overview
+
+HPE Morpheus Enterprise integrates directly with Amazon Route 53 to automatically create DNS entries for Instances provisioned to a configured Cloud or Group. HPE Morpheus Enterprise also syncs in Route 53 Domains for easy selection while provisioning, or setting as the default Domain on a Cloud or Network.
+
+## Add Route 53 Integration
+
+### About this task
+
+Route 53 can be added in the Administration or Infrastructure sections:
+
+### Procedure
+
+1. In Administration > Integrations, select + New Integration
+2. In Infrastructure  >  Networks  >  Services, select Add Service
+3. Provide the following: 
+
+   TYPE
+   :   Route 53
+
+   NAME
+   :   Name for the Integration in HPE Morpheus Enterprise
+
+   REGION
+   :   AWS Region for the Integration
+
+   ACCESS KEY
+   :   AWS User IAM Access Key
+
+   SECRET KEY
+   :   AWS User IAM Secret Key
+4. Once saved the Integration will be added and visible in both Administration > Integrations and Infrastructure  >  Networks  >  Services
+
+### Results
+
+NOTE
+
+All fields can be edited after saving.
+
+## Domains
+
+Once the integration is added, Route 53 Domains will sync and listed under Infrastructure  >  Networks  >  Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Networks  >  Domains
+
+## Configuring Route 53 with Clouds and Groups
+
+DNS Integrations are available in the DNS Integration dropdown in Cloud and Group settings.
+
+HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the Advanced Options section.
+3. In the DNS Integration dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the Edit button for the Group
+3. Expand the Advanced Options section.
+4. In the DNS Integration dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json b/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
new file mode 100644
index 0000000..7622056
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+  "title": "Task Management",
+  "ordinal": 110,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html",
+  "topic_cluster": {
+    "clustering_title": "Task Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C",
+        "clustering_title": "Task Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md b/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
new file mode 100644
index 0000000..7292d13
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.md
@@ -0,0 +1,40 @@
+# Task Management
+
+## Adding Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. On the Tasks tab, click the Add button
+3. From the New Task Wizard input a name for the task
+4. Select the type of task from from the type dropdown
+5. Input the appropriate configuration details. These will vary signficiantly based on the selected Task type. More details on each Task type are contained in the preceding sections.
+6. Once done, click SAVE CHANGES
+
+### Results
+
+TIP
+
+When writing a Task config, it’s often necessary to reference HPE Morpheus Enterprise variables which pertain to the specific Instance the Task is being run against. HPE Morpheus Enterprise includes a pop-out column along the right side of the Add/Edit Task modal which lists available variables. Click and drag the relevant variable into the config area and HPE Morpheus Enterprise will automatically fill in the variable call formatted for the currently chosen Task type. See the screenshot below.
+
+TIP
+
+When writing a Task that calls back into the HPE Morpheus Enterprise API, pass an `Authorization: Execution <%=executionLeaseToken%>` header. The system API will authenticate against that during the life of the Task execution only. This is preferred over other methods of authorizing Task calls as there was a risk of the token expiring in the middle of the Task run.
+
+![../../_images/taskvars.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BA459071-AEAD-4E96-8DB9-FD67DDE9ABC5-high.png)
+
+## Editing Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the pencil icon (✎) on the row of the task you wish to edit
+3. Modify Task as needed
+4. Once done, click SAVE CHANGES
+
+## Deleting Tasks
+
+### Procedure
+
+1. Select Automation from within the Library menu
+2. Click the trash icon (🗑) on the row of the Task you wish to delete
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json b/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
new file mode 100644
index 0000000..fcb4d4b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+  "title": "Kubernetes Blueprints",
+  "ordinal": 135,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.html",
+  "topic_cluster": {
+    "clustering_title": "Kubernetes Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C",
+        "clustering_title": "Kubernetes Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md b/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
new file mode 100644
index 0000000..863a6fd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-B9F1F6ED-F256-4222-B6F2-6EF83256928C.md
@@ -0,0 +1,39 @@
+# Kubernetes Blueprints
+
+HPE Morpheus Enterprise allows you to store Kubernetes configuration YAML files for easy deployment on-demand. Kubernetes Blueprints can be built by pulling in Kubernetes spec stored as a HPE Morpheus Enterprise Spec Template object, those tracked under version control in a Git repository, or you can write them directly in the New Blueprint modal.
+
+To create a new Kubernetes Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Kubernetes. NEXT
+
+In the Cluster Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Complete the Kubernetes Configuration section as follows depending on your Config Type selection.
+
+To consume a HPE Morpheus Enterprise Spec Template containing Kubernetes spec:
+
+- **CONFIG TYPE:** “Kubernetes Spec”
+- **SPEC TEMPLATE:** Use the typeahead field to locate the desired Spec Template
+
+To draft or paste configuration directly in the New Blueprint modal:
+
+- **CONFIG TYPE:** “Kubernetes Yaml Spec”
+- **CONFIG:** Enter your YAML configuration template here
+
+To consume YAML configuration files tracked in a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new Kubernetes Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json b/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
new file mode 100644
index 0000000..6a85bab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+  "title": "LDAP Query Variables",
+  "ordinal": 156,
+  "parent_title": "Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.html",
+  "topic_cluster": {
+    "clustering_title": "LDAP Query Variables",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8",
+        "clustering_title": "LDAP Query Variables"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md b/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
new file mode 100644
index 0000000..8bad4f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BAB8B9BF-9D34-4A34-8CE3-36959C5AA6E8.md
@@ -0,0 +1,29 @@
+# LDAP Query Variables
+
+The current user and dependant parameters are loaded into the query using the <%=phrase%> syntax.
+
+```
+```
+LDAP Query Variables (Example <%=user.email%>)
+```
+```
+
+```
+```
+ user {  
+    accountId,  
+    attributes,  
+    displayName,  
+    email,  
+    firstName,  
+    id,  
+    lastName,  
+    linuxUsername,  
+    username,  
+    windowsUsername  
+ }  
+ customOptions {  
+    fieldName  
+ }
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json b/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
new file mode 100644
index 0000000..9b75fd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+  "title": "Common Options",
+  "ordinal": 107,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html",
+  "topic_cluster": {
+    "clustering_title": "Common Options",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BB270862-D56D-4B6F-86B7-030ED273E907",
+        "clustering_title": "Common Options"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md b/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
new file mode 100644
index 0000000..6f710f4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BB270862-D56D-4B6F-86B7-030ED273E907.md
@@ -0,0 +1,60 @@
+# Common Options
+
+When creating a Task, the required and optional inputs will vary significantly by the Task type. However, there are options which are common to Tasks of all types.
+
+## Target Options
+
+When creating a Task, users can select a target to perform the execution. Some Task types allow for any of the three execution targets listed below and some will limit the user to two or just one. The table in the next section lists the available execution targets for each Task type.
+
+- **Resource:** A HPE Morpheus Enterprise-managed Instance or server is selected to execute the Task
+- **Local:** The Task is executed by the HPE Morpheus Enterprise appliance node
+- **Remote:** The user specifies a remote box which will execute the Task
+
+## Execute Options
+
+- **Continue on Error:** When marked, Workflows containing this Task will continue and will remain in a successful state if this Task fails
+- **Retryable:** When marked, this Task can be configured to be retried in the event of failure
+- **Retry Count:** The maximum number of times the Task will be retried when there is a failure
+- **Retry Delay:** The length of time (in seconds) HPE Morpheus Enterprise will wait to retry the Task
+- **Allow Custom Config:** When marked, a text area is provided at Task execution time to allow the user to pass extra variables or specify extra configuration. See the next section for an example.
+
+## Source Options
+
+Task configuration code may be entered in a number of ways depending on the Task type. Changing the SOURCE type will often update the available fields in the Task modal to accommodate the selected sourcing. Not every Task type supports every sourcing type listed here.
+
+- **Local:** The Task configuration code is written directly in HPE Morpheus Enterprise in a large text area. HPE Morpheus Enterprise includes syntax highlighting for supported Task languages for easier debugging and script writing
+- **Repository:** Source the Task configuration code from an integrated Git or Github repository. This requires a pre-existing integration with a Github or other Git-based repository. See the [relevant integration guides](https://docs.morpheusdata.com/en/latest/integration_guides/Deployments/deployment.html) for full details on creating such an integration. Specify the path to the appropriate file through the WORKING PATH field. The appropriate branch may also be specified (if a branch other than ‘main’ is required) in the BRANCH/TAG field. To reference a tag from this field, use the following syntax: `refs/tags/<tag-name-here>`. Unless otherwise specified, Task config is sourced fresh from the repository each time the Task is invoked which ensures the latest code is always used
+- **URL:** For Task configuration that can be source via an outside URL, specify the address in the URL field
+
+## Allow Custom Config
+
+When “Allow Custom Config” is marked on a Task, the user is shown a text area for custom configuration when the Task is executed manually from the Tasks List Page. If the Task is to be part of an Operational Workflow, mark the same box on the Workflow rather than on the Task to see the text area at execution time. This text area is inside the “Advanced Options” section, which must be expanded in order to reveal the text area. Within the text area, add a JSON map of key-value pairs which can be resolved within your automation scripts. This could be used to pass extra variables that aren’t always needed in the script or for specifying extra configuration.
+
+## Example JSON Map:
+
+```
+```
+{"key1": "value1",  
+"key2": "value2",  
+"os": "linux",  
+"foo": "bar"}
+```
+```
+
+When the Task is executed, these extra variables would be resolved where called into the script such as in the following simple BASH script example:
+
+```
+```
+echo "<%=customOptions.os%>"  
+echo "<%=customOptions.foo%>"
+```
+```
+
+The above example would result in the following output:
+
+```
+```
+linux  
+bar
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json b/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
new file mode 100644
index 0000000..85085af
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+  "title": "Boot Volume Selection During Instance Creation for Local Storage",
+  "ordinal": 438,
+  "parent_title": "Storage Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14",
+        "clustering_title": "Boot Volume Selection During Instance Creation for Local Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md b/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
new file mode 100644
index 0000000..76cf228
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.md
@@ -0,0 +1,47 @@
+# Boot Volume Selection During Instance Creation for Local Storage
+
+During Morpheus instance creation, the provisioning workflow will **delete existing logical volumes**, **create a boot volume**, and then **identify the correct disk device** using the device’s unique identifier (UID).
+
+The boot volume is determined by matching the device UID found in the storage controller to the corresponding Linux device path.
+
+## Log Details
+
+When creating a Morpheus instance, you may see the following log entries:
+
+```
+```
+[2026-02-09 02:45:39,023] ... Deleting all logical volumes on server  
+[2026-02-09 02:45:42,887] ... Attempting to create boot volume  
+[2026-02-09 02:45:43,470] ... Waiting for device discovery complete. Success  
+[2026-02-09 02:45:44,442] ... GET /redfish/v1/.../Drives/2556 -> error: ResourceMissingAtURI ... Retrying in 10 seconds...  
+[2026-02-09 02:45:44,442] ... Boot volume for server created with unique identifier: 600508B1001C40706B7600592D4A5C5A
+```
+```
+
+The logs show:
+
+- Logical volumes are cleared on the server.
+- Morpheus creates a new boot volume.
+- The system waits for Redfish device discovery to complete.
+- If a drive is not yet visible, it may return `ResourceMissingAtURI` and retry.
+- Once the boot volume is created, it logs the unique device identifier.
+- How Boot Volume is Determined.
+
+For OS installation, the boot volume is identified based on the **device UID**. Depending on the server storage controller, the device UID format differs
+
+Table 1. UID Format
+
+       | Storage Device | Name | RAID Type | Identifiers.DurableNameFormat | Identifiers.DurableName |
+| --- | --- | --- | --- | --- |
+| HPE MegaRAID (MR216i-o) Storage Controller | BootVolume | RAID1 | NAA | 600508B1001C40706B7600592D4A5C5A |
+| HPE NVMe SHIELD (NS204i) Boot Device | BootVolume | RAID1 | EUI | 1234:5678:9ABC:DEF0 |
+
+## Finding the Device Path
+
+Once the device UID is known (from the storage controller), the provisioning script searches for the matching device in `/dev/disk/by-id/`
+
+The script looks for the **first entry that contains the UID** (or a stripped version of the UID). These entries are **stable identifiers** that point to the actual Linux block device.
+
+Once a match is found, the script resolves the symbolic link to determine the real boot device path, which will be in the form: `/dev/sdX`
+
+This `/dev/sdX` path is then used for OS installation.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json b/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
new file mode 100644
index 0000000..785b7fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+  "title": "Unisys Stealth",
+  "ordinal": 516,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html",
+  "topic_cluster": {
+    "clustering_title": "Unisys Stealth",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7",
+        "clustering_title": "Unisys Stealth"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md b/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
new file mode 100644
index 0000000..77d7907
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.md
@@ -0,0 +1,182 @@
+# Unisys Stealth
+
+## Introduction
+
+Unisys Stealth is a network security tool for safeguarding sensitive information across shared networks. By creating pre-defined communities of interest (COIs) and curating user access to these groups, the need to create separate networks for handling restricted data is reduced.
+
+HPE Morpheus Enterprise includes a full integration with Stealth allowing administrators to create and manage COIs, work with configurations and roles, and provision new endpoints into COIs.
+
+## Stealth Concepts
+
+- **Communities of Interest (COIs):** A collection of endpoints cryptographically separated so they can only communicate to each other
+- **Endpoints:** Any system or device with a Stealth agent
+- **Configuration:** Tells the endpoints which authorization methods and services to use for obtaining COI membership
+- **Role:** Defines COI membership. Users and groups are assigned to a role which grants access to that role’s COIs
+- **Filters:** Customizes Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints
+
+## Integrating Stealth with HPE Morpheus Enterprise
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Click + ADD
+3. Complete the following fields: 
+
+   - NAME: A name for this Stealth integration in HPE Morpheus Enterprise
+   - API HOST: The address for the server hosting Stealth (ex: <https://x.x.x.x:8448>)
+   - USERNAME: A username for the portaladmin, or the user who logs into the web console
+   - PASSWORD: A password for the account
+   - MANAGER USERNAME: A username for the manager account
+   - MANAGER PASSWORD: A password for the manager account
+4. Click ADD SECURITY INTEGRATION
+
+### Results
+
+![../../_images/add_stealth.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E5EFDABE-E6AE-4E24-A24A-E39E52F95B1D-high.png)
+
+## Summary View
+
+The default view when accessing a Stealth integration in HPE Morpheus Enterprise is the Summary view. In addition to basic information about the Stealth server itself, we can see system status, license and service information.
+
+![../../_images/stealth_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2EDC17EA-E415-404A-936D-E6FCC06BD235-high.png)
+
+## Endpoints
+
+Endpoints are any system or device with a Stealth agent. Stealth endpoints can be provisioned in HPE Morpheus Enterprise in the same way other cloud resources are provisioned. With Stealth integrated, workloads provisioned on the appointed networks are assigned Stealth configuration and a Stealth role during the provisioning process. Based on a user’s assigned roles and COIs assigned to those roles, only workloads on the appointed COIs will be visible to the user. Additionally, workloads can only see other workloads within their COI.
+
+NOTE
+
+Machines on the same network which are not Stealth-managed will be able to see and communicate with each other but will not be able to see workloads which are assigned to a Stealth COI.
+
+### Endpoints View
+
+The endpoints view will display all available Stealth-managed resources. Endpoints are not created here but will be synced into this view as they are created (through HPE Morpheus Enterprise provisioning or outside creation). Stealth-managed endpoints can be deleted by clicking the trash can icon at the end of each row in this view.
+
+The following fields are exposed in the endpoints list view:
+
+- **DISPLAY NAME**
+- **NAME**
+- **DESCRIPTION**
+
+## Configurations
+
+Configurations in Stealth are the top-level construct and house COIs, roles, groups, users and endpoints. Your Stealth integration will include at least one configuration but often they will include more.
+
+Configurations are primarily created and managed from the Stealth console but we can opt to remove them from HPE Morpheus Enterprise by clicking the trash can icon at the end of each row on the configurations list page. Configurations are selected along with a Stealth role at provision time in HPE Morpheus Enterprise.
+
+### Configurations View
+
+The following fields are exposed in the configurations list view:
+
+- **NAME:** The name of the configuration
+- **DESCRIPTION:** A description value for the configuration
+
+## Roles
+
+Users are placed into roles which are associated with COIs. A user’s role(s) determine which COIs he or she will be able to see and access. Roles are synced into HPE Morpheus Enterprise once the integration process is complete and can be viewed in the Roles list view. Roles can also be created from the HPE Morpheus Enterprise integration as described later in this section.
+
+### Roles View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the role
+- **DESCRIPTION:** A description value for the role
+
+NOTE
+
+More detail on each item in the roles list can be revealed by clicking on the (i) icon in each row, including the COIs associated with the role.
+
+### Creating Stealth Roles
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > Roles
+2. Click + CREATE ROLE
+3. Complete the following fields: 
+
+   - NAME: The name for the new role
+   - DESCRIPTION: A description value for the new role
+   - CONFIGURATION: Select an existing Stealth configuration to associate with the role
+   - ROLE TYPE: Identifies how the role is used. Can be Global (for roles used to isolate endpoints and users), Service (for roles used by endpoints in service mode to access an authorization service) or WorkGroup (for roles used by endpoints in normal operation)
+   - FILTER SET: Choose a filter set to apply to the role to allow or deny clear text communication with non-Stealth-managed endpoints
+   - COIs: Select the COIs to be associated with the role
+   - PROVISION CHANGES:
+4. Click ADD ROLE
+
+#### Results
+
+![../../_images/add_role.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FE9AB72A-8680-480B-98F5-3795480217A0-high.png)
+
+## COIs (Communities of Interest)
+
+COIs exist within configurations and create a logical separation between endpoints in separate COIs. Communication between endpoints in the COI is encrypted and those outside the COI are unable to see or access endpoints despite being on the same network.
+
+On completing the integration, HPE Morpheus Enterprise will sync in existing COIs. COIs can also be created from HPE Morpheus Enterprise UI which is described later in this section. COIs are deleted by clicking on the trash can icon at the end of each row in the COIs list view.
+
+### COIs View
+
+The following fields are exposed in the roles list view:
+
+- **NAME:** The name of the COI
+- **DESCRIPTION:** A description value for the COI
+
+### Creating Stealth COIs
+
+#### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations > (Your Stealth integration) > COIs
+2. Click + CREATE COI
+3. Complete the following fields: 
+
+   - NAME: The name for the new COI
+   - DESCRIPTION: A description value for the new COI
+   - TYPE: Workgroup or Service
+   - DIRECTION: Default (enables COI to accept inbound and initiate outbound tunnels), Initiate (restricts the COI to only initiate outbound tunnels), or Accept (restricts the COI to only accept inbound tunnels)
+4. Click CREATE COI
+
+#### Results
+
+![../../_images/create_coi.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EA1DA1E2-1AB6-494A-A776-013769EB3C4D-high.png)
+
+## Filters
+
+Filters customize Stealth communication. More specifically, filters constrain Stealth communication to specific addresses, ports, or protocols and allow Stealth endpoints to communicate with non-Stealth endpoints.
+
+Filters are synced into HPE Morpheus Enterprise when integrating with Stealth and are viewable from the filters list view. They are created and managed from within the Stealth console itself.
+
+When accessing the filters list view, all filter sets are displayed. Each filter set can be expanded to view the individual filters within. Information on each filter is displayed once the filter set has been expanded to reveal the individual filters.
+
+## Provisioning with Stealth
+
+In order to provision new Stealth-managed endpoints, Stealth must be integrated with HPE Morpheus Enterprise as described above. In addition, Stealth must be selected as the Security Server for the cloud you’re provisioning into. Security servers can be selected at the time a new Cloud integration is created or by editing an existing Cloud integration.
+
+### Choosing a Cloud Security Server
+
+#### About this task
+
+Assuming the Cloud is already integrated with HPE Morpheus Enterprise, use the steps below to set the security server and activate Stealth prompts at provision time. The steps to set the security server during the time the cloud is initially integrated with HPE Morpheus Enterprise is very similar.
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds > (Your Selected Cloud)
+2. Click EDIT
+3. Click on Advanced Options to reveal additional selections
+4. In the dropdown for SECURITY SERVER, choose an existing Stealth integration
+
+### Provisioning to a Stealth-enabled Cloud
+
+#### About this task
+
+Once we have selected our Stealth integration as the security server for at least one Cloud in HPE Morpheus Enterprise, new Instances (endpoints) can be provisioned and managed by Stealth.
+
+#### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Click + ADD
+3. Select the Instance Type, Cloud, and Group making sure to choose a Cloud that has been set up for an existing Stealth integration
+4. On the Configure tab of the provisioning wizard, choose a Stealth Configuration and a Stealth Role according to the needs of the machine(s) being provisioning
+5. Once the provisioning process is complete, the new Stealth-managed endpoints will be available and restricted based on the Stealth implementation
+
+#### Results
+
+![../../_images/provision_endpoint.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C5EBFD40-8381-4497-9E9F-05EEC4AB65F6-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json b/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
new file mode 100644
index 0000000..9df8cc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+  "title": "Networking Integrations",
+  "ordinal": 506,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.html",
+  "topic_cluster": {
+    "clustering_title": "Networking Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC",
+        "clustering_title": "Networking Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md b/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
new file mode 100644
index 0000000..eeed3d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BC17942D-DE0B-4244-900F-DE38D31A09EC.md
@@ -0,0 +1,15 @@
+# Networking Integrations
+
+**Subtopics**  
+
+- **[Infoblox](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-51A5DCC0-B5B6-40E6-9B5E-A378FB95BF25.html)**
+- **[phpIPAM](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B7496F21-B633-436F-850B-507E482F96F2.html)**
+- **[NSX](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-064FEBCE-E38F-45E0-9349-4177EBFFF70D.html)**
+- **[ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7E4CDD31-B45F-4D53-B476-D933EBCCA38A.html)**
+- **[HPE Aruba CX DSS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html)**
+- **[NSX Cloud](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html)**
+- **[Cisco ACI](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3F7EB49F-0147-4EB3-894B-B8E8D4E95F1B.html)**
+- **[Bluecat](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9ECF72A1-9565-4202-A087-82313C2F8D58.html)**
+- **[SolarWinds IPAM](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B6D4283B-948C-4722-8C96-21CDB727D0EE.html)**
+- **[Unisys Stealth](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BBB97945-24EA-49FA-BD70-78DE398F8EB7.html)**
+- **[EfficientIP SOLIDserver](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0C0FBC8C-5C50-44CF-8872-9C47EF00A8AB.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json b/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
new file mode 100644
index 0000000..2560679
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+  "title": "Hyper-V",
+  "ordinal": 459,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.html",
+  "topic_cluster": {
+    "clustering_title": "Hyper-V",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3",
+        "clustering_title": "Hyper-V"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md b/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
new file mode 100644
index 0000000..45e829f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BC3CA03C-A804-4838-A462-9DD47EF37FD3.md
@@ -0,0 +1,179 @@
+# Hyper-V
+
+Hyper-V is the virtualized server computing environment introduced by Microsoft. Hyper-V is consumed by HPE Morpheus Enterprise as a private cloud offering and is a common hypervisor technology in data centers. HPE Morpheus Enterprise provides an avenue to aggregate Hyper-V resources together to allow efficient and seamless deployment of applications as a virtual machine (VM) or Docker host in the world of Hyper-V.
+
+## Features
+
+- Virtual Machine Provisioning
+- Discovery of Existing Instances
+- Containers
+- Backups / Snapshots
+- Resources Groups
+- Migrations
+- Auto Scaling
+- Load Balancing
+- Remote Console
+- Periodic Synchronization
+- Veeam Integration
+- Lifecycle Management and Resize
+- Unique Kerberos Authentication
+
+## Getting Started
+
+To get started, a few prerequisites must first be met. The Hyper-V host must be installed with its firewall enabled and it can either be joined to a domain or standalone. The Hyper-V host must also have the external network of Hyper-V configured and it can share this network with the management operating system. A user account that is part of the local administrators group on the Hyper-V host is also required. This document covers Hyper-V 2008 and Hyper-V 2012.
+
+## Understanding WinRM
+
+HPE Morpheus Enterprise uses WinRM to communicate to the Hyper-V host for deployment of the HPE Morpheus Enterprise Agent. The HPE Morpheus Enterprise Agent allows for the host dashboard to be populated with information in the form of graphs that cover CPU, Network, Storage, and memory consumption. Furthermore, this Agent provides logging and monitoring capabilities.
+
+If Windows Remote Management (WinRM) is not installed and configured, WinRM scripts do not run and the WinRM command line tool cannot perform data operations or allow for the HPE Morpheus Enterprise Agent to be installed. WinRM uses HTTP port 5985 or HTTPS port 5986 for communications.
+
+To better understand all of the default settings of WinRM please refer to the [following page](https://msdn.microsoft.com/en-us/library/aa384372%28v=vs.85%29.aspx) in Microsoft documentation.
+
+## Native Authentication
+
+To configure WinRM with default settings (WINRM\_NATIVE)
+
+Type the following command at a command prompt:
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the Runas command at a command prompt.
+
+When the tool displays `Make these changes [y/n]?`, type `y`.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. By default Kerberos is enabled and if domain authentication is not being used we want to disable that. Issue the below commands to setup basic authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth '@{Basic="true"}'  
+$ winrm set winrm/config/service '@{AllowUnencrypted="true"}'  
+$ winrm set winrm/config/service/Auth '@{Kerberos="false"}'
+```
+```
+
+## Domain Authentication
+
+To configure WinRM with Domain Authentication (WINRM\_INTERNAL)
+
+Type the following command at a command prompt
+
+```
+```
+$ winrm quickconfig
+```
+```
+
+If you are not running under the local computer Administrator account, you must either select Run as Administrator from the Start menu or use the runas command at a command prompt.
+
+When the tool displays Make these changes [y/n]?, type y.
+
+If configuration is successful, the following output is displayed:
+
+```
+```
+$ WinRM has been updated for remote management.  
+$ WinRM service type changed to delayed auto start.  
+$ WinRM service started.  
+$ Created a WinRM listener on HTTP://* to accept WS-Man requests to any IP on this machine.
+```
+```
+
+Keep the default settings for client and server components of WinRM, or customize them. Issue the below commands to setup domain authentication:
+
+```
+```
+$ winrm set winrm/config/service/Auth @{Basic="true"}  
+$ winrm set winrm/config/service @{AllowUnencrypted="false"}  
+$ winrm set winrm/config/service/Auth @{Kerberos="true"}
+```
+```
+
+Kerberos authentication will also need to be configured on the HPE Morpheus Enterprise appliance to support Windows domain accounts to access the remote host with WINRM\_INTERNAL connection type.
+
+On the HPE Morpheus Enterprise appliance the krb5-user package must be installed.
+
+For Ubuntu the command is as follows:
+
+```
+```
+$ sudo apt-get install krb5-user
+```
+```
+
+For Centos the command is as follows:
+
+```
+```
+$ sudo yum install krb5-workstation pam_krb5 -y
+```
+```
+
+Create a file in /etc called krb5.conf and replace the domain name with the name of the domain to be used. In this case we used HPE Morpheus Enterprise .com as the domain.
+
+```
+```
+[libdefaults]  
+        default_realm = |morpheus| .COM  
+            dns_lookup_kdc = true  
+            verify_ap_req_nofail = false  
+        default_tgs_enctypes = rc4-hmac  
+        default_tkt_enctypes = rc4-hmac  
+[realms]  
+        |morpheus| .COM = {  
+                kdc = win-ad.|morpheus| .COM:88  
+                admin_server = win-ad.|morpheus| .COM:749  
+     }  
+[domain_realm]  
+    .|morpheus| .COM = |morpheus| .COM  
+        |morpheus| .COM = |morpheus| .COM  
+[login]  
+     krb4_convert = true  
+     krb4_get_tickets = false
+```
+```
+
+After creation of the krb5.conf a keytab file is also required. See below for instructions on how to create a keytab file. <http://www.itadmintools.com/2011/07/creating-kerberos-keytab-files.html>
+
+## Adding Hyper-V as a Private Cloud
+
+The Hyper-V host is prepared for HPE Morpheus Enterprise to communicate with it via WinRM so the Hyper-V private cloud is ready to be configured. Create a group and then create a HPE Morpheus Enterprise cloud for Hyper-V. Populated the information as show in Figure 1: specific for the environment being configured.
+
+![../../../_images/hyperv1_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-23A922A0-C860-4705-AA64-BF5363B4B77A-high.png)
+
+NOTE
+
+The working path, vm path, and disk path should be created on the Hyper-V host by the Hyper-V administrator. If these paths are not created they will need to be setup and the Hyper-V settings will need to adjusted to reference them.
+
+![../../../_images/hyperv2_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F3DBACFA-EE94-4CE0-AF6F-D79405736F55-high.png)
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to Hyper-V or create a new one. These are managed from the Admin > Plans& Pricing section.
+
+![../../../_images/hyperv3_original.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F6FDCC9D-AFEE-4EF5-B32C-A8B200171F83-high.png)
+
+## Docker
+
+So far this document has covered how to add the Hyper-V cloud integration and has enabled users the ability to provision virtual machine-based instances via the Add Instance catalog under the Provisioning menu. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into Hyper-V (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there click + ADD CLUSTER to add a Hyper-V Docker Host. A cluster is created when adding Docker hosts, even when only one host is needed.
+
+HPE Morpheus Enterprise views a Docker host just like any other hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Admin | Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json b/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
new file mode 100644
index 0000000..e6f968b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+  "title": "Hypervisor Console Keyboards",
+  "ordinal": 197,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.html",
+  "topic_cluster": {
+    "clustering_title": "Hypervisor Console Keyboards",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3",
+        "clustering_title": "Hypervisor Console Keyboards"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md b/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
new file mode 100644
index 0000000..295da27
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BCD3CA0B-5C7E-46CB-94F2-BD00465D06D3.md
@@ -0,0 +1,52 @@
+# Hypervisor Console Keyboards
+
+HVM VMs support guest console access as well as hypervisor console access. For each HVM VM, users can set a keyboard layout configuration which will then be set for use on each session.
+
+IMPORTANT
+
+This feature requires HVM Host agent version 3.0.3 or greater. Upgrade the host agent from the host detail page for **each** host by expanding the ACTIONS menu and clicking "Upgrade Agent." Alternatively, select "Download Agent Script" to download a script to run against the host manually from a terminal session. These scripts are specific to each host so you must download a script for each host and run the correct script against the correct host.
+
+Currently, the following layouts are supported:
+
+- Dutch (Belgium)
+- French (Belgium)
+- German
+- Italian
+- English (United Kingdom)
+- English (United States)
+- French
+- Spanish
+- German (Switzerland)
+- Finnish
+- French (Switzerland)
+- Icelandic
+- Norwegian
+- Portuguese
+- Danish
+
+Setting the Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click EDIT
+6. Expand the Advanced Options section
+7. In the KEYBOARD LAYOUT field, select the desired keyboard localization
+8. Click SAVE CHANGES
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6EC36C91-5E13-4B5B-AB20-10DE225F85B3-high.png)
+
+Using the Configured Keyboard Layout
+
+1. Navigate to Infrastructure > Clusters
+2. From the list of Clusters, select the appropriate HVM Cluster
+3. Click on the VMs tab
+4. Click on the hyperlinked "name" value of the appropriate HVM VM
+5. Click on the Console tab
+6. Click on the dropdown labeled GUEST and change the selection to Hypervisor
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B75612CA-1867-4066-937C-B66FA952D251-high.png)
+7. Click on the keyboard icon and see the keyboard layout has changed to the selected layout
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EC09C556-7F46-4036-ABDF-7E36BE8BFD8D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json b/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
new file mode 100644
index 0000000..555a3e9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+  "title": "Affinity Groups",
+  "ordinal": 187,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html",
+  "topic_cluster": {
+    "clustering_title": "Affinity Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53",
+        "clustering_title": "Affinity Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md b/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
new file mode 100644
index 0000000..214f7a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.md
@@ -0,0 +1,28 @@
+# Affinity Groups
+
+HVM Clusters offer affinity groups and anti-affinity groups. These work similarly to affinity groups on other platforms, such as the affinity rules concept in VMware vSphere. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Whenever possible, servers configured to "Keep Together" will run on the same HVM Host. Servers configured to "Keep Separate" will be balanced across HVM Hosts to the maximum extent possible.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C5C8E073-11BC-4D5A-A900-14571F77280D-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the HVM Cluster detail page (Infrastructure > Clusters, then select the appropriate HVM Cluster). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next cluster sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+TIP
+
+Placement settings (ex. pinning a VM to a specific host) can override an affinity group. HVM Clusters will attempt to implement affinity groups intelligently to work around VM placement. For example, in a group of five VMs configured to "keep together" with one pinned to host 1, the Cluster would run all five VMs on host 1 (if possible) to simultaneously honor the placement and the affinity group. In some scenarios, it will not be possible to simultaneously honor all placements and affinities/anti-affinities.
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9C039E15-FE97-4CFD-987E-07A16E644534-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12E8B43B-9A47-46D9-8A99-3EBDF1FAD577-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json b/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
new file mode 100644
index 0000000..b4323c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+  "title": "Deployment",
+  "ordinal": 480,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.html",
+  "topic_cluster": {
+    "clustering_title": "Deployment",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BD4F0587-C0E9-4120-9D74-B54015579A60",
+        "clustering_title": "Deployment"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md b/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
new file mode 100644
index 0000000..8747a0d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BD4F0587-C0E9-4120-9D74-B54015579A60.md
@@ -0,0 +1,6 @@
+# Deployment
+
+**Subtopics**  
+
+- **[Git](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-62B00AB4-5670-4F7D-9EDA-E0E2E4FB3D4A.html)**
+- **[Github](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json b/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
new file mode 100644
index 0000000..ba4521c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+  "title": "Instances",
+  "ordinal": 83,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html",
+  "topic_cluster": {
+    "clustering_title": "Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863",
+        "clustering_title": "Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md b/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
new file mode 100644
index 0000000..dcb0126
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.md
@@ -0,0 +1,26 @@
+# Instances
+
+Instances are a great starting point for taking advantage of self service features and spinning up both VMs and containers. In HPE Morpheus Enterprise it may be advisable to cover the definition of a few terms used within the application so as to reduce confusion. These concepts are also covered in greater detail in the [Provisioning Concepts](https://docs.morpheusdata.com/en/latest/provisioning/concepts/concepts.html) section.
+
+Instance
+:   A set of containers or virtual machines that can correlate to a single horizontally-scalable entity or a service suite, like a database. It is important to note that an Instance can contain one or more containers/VMs depending on the Instance type and configuration.
+
+Container
+:   Typically a docker container provisioned via a HPE Morpheus Enterprise Docker host.
+
+Virtual Machine
+:   A virtualized compute server provisioned onto various hypervisor hosts.
+
+The top of the main Instances page shows overall statistics for the listed Instances, including count, status, and resource utilization. You can search for Instances by name, or filter by group, instance type, or category.
+
+NOTE
+
+Instances listed are determined by group access and role permissions. When filtered to show Instances of “All Statuses”, any Instances which are in a state of pending removal due to a delayed delete policy in place are not shown under this filter. Instead you must filter for “Pending Removal” to see these Instances and prevent deletion, if desired.
+
+The Instance list contains important information about each instance, including the instance name, environment tag, instance type icon, IP address and port info, Instance version, the number of virtual machines or containers in the instance, the group the instance is in, and the cloud or clouds the instance is in.
+
+**Subtopics**  
+
+- **[Creating Instances](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html)**
+- **[Instance Details](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html)**
+- **[Managing Instances](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-35F886E0-C4F0-42F5-AF68-AA1481040D76.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json b/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
new file mode 100644
index 0000000..b3101a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+  "title": "Components",
+  "ordinal": 7,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.html",
+  "topic_cluster": {
+    "clustering_title": "Components",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4",
+        "clustering_title": "Components"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md b/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
new file mode 100644
index 0000000..20686cd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE80C9FF-D456-4120-937D-6FB30FA422D4.md
@@ -0,0 +1,13 @@
+# Components
+
+The Appliance Server automatically installs several components for the operation of HPE Morpheus Enterprise. This includes:
+
+- RabbitMQ (Messaging)
+- MySQL (Logistical Data store)
+- Opensearch (Logs / Metrics store)
+- Tomcat (HPE Morpheus Enterprise Application)
+- Nginx (Web frontend)
+- Guacamole (Remote console service for clientless remote console)
+- Check Server (Monitoring Agent for custom checks added via UI)
+
+All of these are installed in an isolated way using chef zero to `/opt/morpheus`. It is also important to note these services can be offloaded to separate servers or clusters as desired. For details check the installation section and high availability.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json b/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
new file mode 100644
index 0000000..c934104
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+  "title": "VMware vCenter",
+  "ordinal": 475,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.html",
+  "topic_cluster": {
+    "clustering_title": "VMware vCenter",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BE852729-65DF-4377-9A64-F05D47CD9D49",
+        "clustering_title": "VMware vCenter"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md b/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
new file mode 100644
index 0000000..79c2c3b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BE852729-65DF-4377-9A64-F05D47CD9D49.md
@@ -0,0 +1,591 @@
+# VMware vCenter
+
+## Overview
+
+VMware is a very common cloud integration choice supported by HPE Morpheus Enterprise . They have provided a top notch virtualization solution and one might argue pioneered the virtualization space altogether. As such, many companies utilize this technology and all the features that come with it, so HPE Morpheus Enterprise covers a broad feature set in vCenter.
+
+## Features
+
+- Virtual Machine Provisioning
+- Backups / Snapshots
+- Resource Groups
+- Datastores and DRS Clusters
+- Distributed Switches
+- Affinity Groups
+- Datacenter / Cluster scoping
+- Brownfield VM management and migration
+- VMware to VMware migrations
+- VMDK/OVF image conversion support
+- Hypervisor Remote Console
+- Periodic Synchronization
+- Veeam Backup Integration
+- Lifecycle Management and Resize
+- Metadata tag sync
+
+On top of all these features, HPE Morpheus Enterprise also adds additional features to VMware that do not exist out of the box to make it easier to manage in multitenant environments as well as hybrid cloud environments:
+
+- Cloud-Init Support
+- VHD to VMDK Image Conversion
+- QCOW2 to VMDK Image Conversion
+- Multitenancy resource allocation
+- Virtual Image management (Blueprints)
+- Auto-scaling and recovery
+
+## Getting Started
+
+To get started with VMware, simply start by adding a Cloud in the Infrastructure  >  Clouds section.
+
+To start adding a VMware cloud there will be some things you will need:
+
+vCenter API Url
+:   Typically this is the url to the vCenter web client with a `/sdk` in the path
+
+Username/Password
+:   A set of credentials with high level access to VMware (ensure the account has Datacenter level access)
+
+Once these fields are entered, some selections will start pre-populating. A cloud integration is scoped to a specific data center, and can optionally be scoped down to a single cluster or even a single resource pool. If the drop downs do not populate, please verify the api url is resolvable, morpheus has access to vCenter on 443, and the provided credentials are correct and the user has sufficient permissions.
+
+Another cool feature provided with the cloud integration is optional Resource Pool scoping. One can choose to allow the cloud to provision into All Resource Pools or a singular Resource Pool. When choosing All, these Resource Pools can be managed from a sub-account and visibility perspective via the Cloud Detail page (multi-tenancy).
+
+The VMware cloud integration provides a few additional options including allowing users to make host selections or keeping that aspect hidden such that the best host is automatically chosen for the requested provision.
+
+The RPC Mode feature can be configured to allow HPE Morpheus Enterprise to install its agent on the Guest operating system via either SSH/WinRM or Vmware Tools Guest Process feature. The VMware tools Guest Execution API can be tricky so it is recommended to use SSH/WinRM if possible. However, if it is not possible for the Appliance to have outbound access to all networks in which VMs are being provisioned to the SSH/WinRM ports (22, 5985 respectively) then Guest Execution is the only option.
+
+The Use VNC console option on the VMware cloud requires special configuration on each ESXI host but allowed hypervisor level remote console support. (See the Advanced Section for details)
+
+When following this add cloud wizard an option will be presented to create a group or add to an existing group. These groups can be given provisioning permission via role based access control. It is normally recommended that groups are organized such that one cloud exists in one group unless the networks are setup such that internal routing is possible between the clouds. This is very useful for bursting, or hybrid cloud configurations.
+
+## Windows Provisioning Tips
+
+By default when provisioning windows templates, HPE Morpheus Enterprise performs guest customizations which initiates a sysprep. This resets the Administrator user and password. HPE Morpheus Enterprise will set the Administrator password from Administration > Settings > Provisioning > Windows Settings > Password.
+
+Users can also set the username on an image as Administrator and enter a different password if unique passwords are required per image.
+
+Guest customizations are required when assigning static IP’s manually or using IP pools. They can be disabled per virtual image advanced settings under Library > Virtual Images > Edit Image > Advanced > Uncheck “Force Guest Customization” if using DHCP. However the SID will not be changed from the source template. In addition, new VM’s will not be able to join a domain that had already been joined by the source template or any other VM’s with that SID.
+
+## Existing Instances
+
+HPE Morpheus Enterprise provides several features regarding pulling in existing virtual machines and servers in an environment. Most cloud options contain a checkbox titled ‘Inventory Existing Instances’. When this option is selected, all VMs found within the specified scope of the cloud integration will be scanned periodically and Virtual Machines will be synced into HPE Morpheus Enterprise. Users may also choose to onboard only virtual machines that are running within specific Resource Pools. Once the vCenter Cloud is integrated, navigate to the detail page for the specific Cloud (select it from the list at Infrastructure > Clouds). From the Resources tab, locate the Pools section. Click ACTIONS > Editnext to a selected Resource Pool. If INVENTORY is checked, HPE Morpheus Enterprise will automatically onboard virtual machines from that Resource Pool.
+
+By default these virtual machines are considered ‘unmanaged’ and do not appear in the Provisioning > Instances area but rather Infrastructure  >  Compute  >  Virtual Machines. However, a few features are provided with regards to unmanaged instances. They can be assigned to various accounts if using a multitenant master account, however it may be best suited to instead assign the ‘Resource Pool’ to an account and optionally move all servers with regards to that pool (more on this later).
+
+A server can also be made into a managed server. During this process remote access is requested and an agent install is performed on the guest operating system. This allows for guest operations regarding log acquisition and stats. If the agent install fails, a server will still be marked as managed and an Instance will be created in Provisioning, however certain features will not function. This includes stats collection and logs.
+
+NOTE
+
+All Cloud data is resynchronized on a 5 minute interval. This includes Datastores, Resource Pools, Networks, Blueprints, and Virtual Machines.
+
+## Service Plans
+
+A default set of Service Plans are created in HPE Morpheus Enterprise for the VMware provisioning engine. These Service Plans can be considered akin to AWS Flavors or Openstack Flavors. They provide a means to set predefined tiers on memory, storage, cores, and cpu. Price tables can also be applied to these so estimated cost per virtual machine can be tracked as well as pricing for customers. By default, these options are fixed sizes but can be configured for dynamic sizing. A service plan can be configured to allow a custom user entry for memory, storage, or cpu. To configure this, simply edit an existing Service Plan tied to VMware or create a new one. These all can be easily managed from the Admin  >  Plans & Pricing section.
+
+## Virtual Images / Blueprints
+
+HPE Morpheus Enterprise will automatically take an inventory of all blueprints configured in vCenter and present them as options during provisioning. However, in order for HPE Morpheus Enterprise to properly provision these virtual machines and provide accurate stats and health of these virtual machines, an agent must be installed during virtual machine startup. This means remote access needs to be granted at the guest operating system level to HPE Morpheus Enterprise . To properly configure these virtual images, find the relevant images in Library > Virtual Images and edit the entry. On this form, a few options are presented. The first is a check box asking whether or not cloud-init is enabled. If cloud-init is enabled, simply provide the default OS username configured (for Ubuntu the username is ubuntu and for CentOS the username is centos). For those looking to add cloud-init to existing blueprints HPE Morpheus Enterprise requires no special configuration and can use the default cloud.cfg settings.
+
+A global cloud-init username/password can also be configured per account as well as a keypair via the `Admin->Provisioning` settings section. The great benefit of utilizing cloud-init is default blueprints do not need common credential sets thereby increasing provisioning security.
+
+Windows systems do not typically support cloud-init. So simply turn this checkbox off and provide the Administrator credentials. It should be noted that these credentials are encrypted in the database. If using WinRM for the RPC Mode instead of VMware tools, a Local or Domain Administrator account credential set can be provided instead.
+
+## Snapshots
+
+HPE Morpheus Enterprise allows the ability to create a snapshot of a VM in VMware vCenter. From the instance detail page, simply select Actions  >  Create Snapshot to begin creation of a new Snapshot. Existing snapshots can be viewed in the `BACKUPS` tab on the instance detail page. Snapshots taken in vCenter will sync into HPE Morpheus Enterprise every five minutes. To revert to a previous snapshot, click on the revert icon located on the right side of the Snapshot. Snapshots can be deleted by clicking on the trash can icon.
+
+NOTE
+
+Access to Snapshots can be limited or removed entirely for specific user roles as needed. To edit a role’s Snapshots permissions, go to Administration > Roles > (Your selected role) > Snapshots. Users can be given Full, Read-only, or No access.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Bear in mind that VMware does not support Snapshots for this network adapter type and for that reason Snapshot and backup-related features will also fail in HPE Morpheus Enterprise for VMs using SR-IOV network adapters.
+
+## Affinity Groups
+
+HPE Morpheus VM Essentials Software offers two-way sync for affinity groups with integrated VMware vCenter Clouds. An affinity group contains a type (either Keep Together or Keep Separate) and a list of servers which should have the rule applied. Affinity groups created from HPE Morpheus VM Essentials create "Should" rules (soft rules) rather than "Must" rules (hard rules) in vCenter. Thus whenever possible, servers configured to "Keep Together" will run on the same cluster host while servers configured to "Keep Separate" will be balanced across cluster hosts to the maximum extent possible. These rules may be broken if necessary to balance resources or recover from failures.
+
+TIP
+
+It is possible to create an empty affinity group (that is, one with no servers selected) in HPE Morpheus VM Essentials even though this is not possible in vCenter. If such an affinity group is created, HPE Morpheus VM Essentials will hold it without syncing to vCenter until at least one server is added and the affinity group becomes compatible with the vCenter API.
+
+Viewing Affinity Groups
+
+Affinity groups are listed on the Resources tab of the Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From the ACTIONS menu for each affinity group, they may be edited or deleted. By editing an affinity group, users may view or edit its enabled status (affinity groups which are not enabled will not be acted on).![A list of current-existing affinity groups.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7AD47077-8387-4499-9BDE-BBACFDDA2989-high.png)
+
+Adding Affinity Groups
+
+As mentioned in the previous section, affinity groups are listed on the Resources tab of the VMware Cloud detail page (Infrastructure > Clouds, then select the appropriate VMware Cloud). From here, to create a new affinity group, click + ADD. Configure the following:
+
+- **NAME:** A name for the affinity group
+- **TYPE:** Select either "Keep Together" or "Keep Separate" to indicate whether the selected servers should run on as few or as many servers as possible within the capabilities of the HVM Cluster
+- **CLUSTER:** Select the vCenter cluster
+- **ACTIVE:** When checked, the rules defined in the affinity group will be applied to the HVM Cluster
+- **SERVERS:** Select as many servers as desired from the typeahead list
+
+Once finished, click SAVE CHANGES. Following the next Cloud sync, the affinity rule will be applied and VMs will begin to migrate (if applicable).
+
+![Adding a new affinity group.](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C4C3EDB1-CA6E-4DEA-890C-B5C5B0E3DE13-high.png)
+
+Adding Servers to Affinity Groups at Provision Time
+
+In addition the adding servers from the affinity group, newly-provisioned servers may be added to an affinity group at provision time. From the CONFIGURE tab of the provisioning wizard, expand the Advanced Options section. Within Advanced Options, select an affinity group. The affinity group must be pre-existing and this list will be filtered to show only affinity groups that apply depending on other configuration parameters set on the new Instance.![Setting an affinity group on a new vmware instance at provision time](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-688F89C9-1444-4D3A-94B5-E8DFE9BDC066-high.png)
+
+## Tagging and Metadata
+
+As of Morpheus version 4.1.0, tagging support is included for vCenter in addition to the other clouds that have already supported it in past versions. Tags will sync to vCenter from Morpheus and existing tags are also inventoried from vCenter into Morpheus.
+
+NOTE
+
+This feature requires a minimum API version of vCenter 6.5. The API version can be edited by navigating to ‘Infrastructure > Clouds’ and clicking the edit (pencil) button in the row for the relevant cloud. The field is labeled ‘VERSION’.
+
+Tags can be created on-demand when provisioning from the ‘CONFIGURE’ tab of the ‘CREATE INSTANCE’ wizard (Provisioning > Instances). Within the ‘Metadata’ drawer, you will see sets of fields to enter key/value pairs. On creation of the instance, this metadata will be synced into vCenter.
+
+‘Inputs’ from your library can also be exported as metadata for use with vCenter. When adding or editing a new Input (Library > Options > Inputs), simply mark the box labeled ‘EXPORT AS METADATA’. The ‘FIELD NAME’ becomes the tag category in VMWare.
+
+![../../../_images/tagging_at_provisioning.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-789342B0-CEC8-46F9-83A6-4B8EC288D2D8-high.png)
+
+## Docker
+
+So far this document has covered how to add the VMware cloud integration and has enabled users the ability to provision virtual machine based instances via the Add Instance catalog in Provisioning. Another great feature provided by HPE Morpheus Enterprise out of the box is the ability to use Docker containers and even support multiple containers per Docker host. To do this a Docker Host must first be provisioned into VMware (multiple are needed when dealing with horizontal scaling scenarios).
+
+To provision a Docker Host simply navigate to the Clusters tab of the Cloud detail page or Infrastructure > Clusters section. From there, click + ADD CLUSTER to add a VMware Docker Host. This host will show up in the Hosts tab next to other ESXi servers that were inventoried by the VMware cloud integration. HPE Morpheus Enterprise views a Docker host just like any other Hypervisor with the caveat being that it is used for running containerized images instead of virtualized ones. Once a Docker Host is successfully provisioned a green checkmark will appear to the right of the host marking it as available for use. In the event of a failure click into the relevant host that failed and an error explaining the failure will be displayed in red at the top.
+
+Some common error scenarios include network connectivity. For a Docker Host to function properly, it must be able to resolve the HPE Morpheus Enterprise appliance url which can be configured in Administration > Settings. If it is unable to resolve and negotiate with the appliance than the agent installation will fail and provisioning instructions will not be able to be issued to the host.
+
+## Multitenancy
+
+A very common scenario for Managed Service Providers is the need to provide access to VMware resources on a customer by customer basis. With VMware several administrative features have been added to ensure customer resources are properly scoped and isolated. For VMware it is possible to assign specific Networks, Datastores, and Resource Pools to customer accounts or even set the public visibility of certain resources, therefore allowing all sub accounts access to the resource.
+
+## Advanced
+
+There are several advanced features provided within HPE Morpheus Enterprise that can leverage some cool aspects of VMware. One of these features is Remote Console support directly to the hypervisor. To enable this feature a few prerequisites must be met. First, the HPE Morpheus Enterprise appliance must have network access to the ESXi hosts within VCenter. Secondly, firewall settings need to be adjusted on each ESXi host. This can be done in VSphere under firewall configuration on the host. Simply check the gdbserver option, which will open up the necessary ports (starting at 5900 range).
+
+IMPORTANT
+
+Hypervisor Console for vCenter 6.5 requires HPE Morpheus Enterprise v3.2.0+
+
+Now that the ESXi hosts are ready to utilize remote console, simply edit the cloud in HPE Morpheus Enterprise via Infrastructure  >  Clouds. Check the option that says Enable Hypervisor Console. It is important to note that currently this functionality only works for newly provisioned vm’s provisioned directly via HPE Morpheus Enterprise. This should change soon however.
+
+It is also possible to import vm snapshots for backup or conversion purposes from VCenter and also an ESXi host. However, this does require that the ESXi host license has an enterprise level license as it will not allow the appliance to download a virtual image if it is not a paid VMware license.
+
+## VMware Permissions
+
+When integrating VMware vCenter with HPE Morpheus Enterprise, users must supply credentials for a vCenter account and HPE Morpheus Enterprise will only have access privileges equal to the integrated account. Many users will choose to use a vCenter administrator account so that HPE Morpheus Enterprise can freely do any function in vCenter without worrying about hitting access limits. Others, for security reasons, may want to restrict HPE Morpheus Enterprise only to the minimum permissions it needs to perform its functions. Follow the guide in this section to configure a user with minimal permissions and associate it with the appropriate usage levels before using it to create a HPE Morpheus Enterprise Cloud integration.
+
+### Create vCenter Users and Roles
+
+For this example, I’ve added a new local user to be my HPE Morpheus Enterprise integration user (Menu > Administration > Users and Groups) but any existing user, whether locally-created or sourced from an identity integration (like Active Directory), works fine.
+
+![../../../_images/addUsers.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2664505C-63D5-43FB-9E16-21AD005B561C-high.png)
+
+The next step is to create a Role (Menu > Administration > Roles). You can edit an existing Role to be sure it has the correct privileges, I’ve opted to create a new role and assign the correct privileges. Below the screenshot, take note of the complete set of required privileges. Once all privileges are set, name the Role (if it’s a new one) and click Finish.
+
+![../../../_images/addRoles.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3152339A-7CAC-4795-8CBD-67503905D112-high.png)
+
+### Privileges
+
+Content Library
+:   - All Content Library privileges
+
+Datastore/Datastore Cluster
+:   - Allocate Space
+    - Browse Datastore
+    - Low Level file Operations
+    - Remove File
+    - Update virtual machine files
+    - Update virtual machine metadata
+
+Distributed Switch
+:   - Port configuration operation
+    - Port setting operation
+
+Global
+:   - Log Event
+    - Manage custom attributes
+    - Set custom attribute
+
+Network
+:   - Assign Network
+    - Configure
+    - Remove
+
+Resource
+:   - Apply recommendation
+    - Assign vApp to resource pool
+    - Assign virtual machine to resource pool
+    - Migrate powered off virtual machine
+    - Migrate powered on virtual machine
+
+Scheduled task
+:   - Create tasks
+    - Modify task
+    - Remove task
+    - Run task
+
+Tasks
+:   - Create task
+    - Update task
+
+Virtual Machine
+:   - Configuration (all)
+    - Guest Operations (all)
+    - Interaction (all)
+    - Inventory (all)
+    - Provisioning (all)
+    - Service configuration (all)
+    - Snapshot management (all)
+    - vSphere Replication (all)
+
+vApp
+:   - Clone
+    - Export
+    - Import
+
+vSphere Tagging
+:   - Assign or Unassign vSphere Tag
+    - Assign or Unassign vSphere Tag on Object
+    - Create vSphere Tag
+    - Create vSphere Tag Category
+    - Delete vSphere Tag
+    - Delete vSphere Tag Category
+    - Edit vSphere Tag
+    - Edit vSphere Tag Category
+    - Modify UsedBy Field For Category
+    - Modify UsedBy Field For Tag
+    - privilege.InventoryService.Tagging.CreateScope.label
+    - privilege.InventoryService.Tagging.DeleteScope.label
+
+With the User and Role created, add permissions to associate the User and Role to the appropriate usage constructs. Navigate to the usage construct you wish to work with, navigate to the permissions tab, click the plus (+) button. In the screenshot below, I’m adding the permission for the vCenter usage construct. The complete list of usages and whether or not to mark the propagation box is below the image.
+
+NOTE
+
+For organization and security purposes, permissions can also be added to folders. This allows HPE Morpheus Enterprise to see the folders and onboard any resources within them (if desired). Once the vCenter Cloud integration has been created in HPE Morpheus Enterprise, you can view folders from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > ResourcesTab). By editing the folder here (Actions > Edit), folders can be set as the “Default” and/or the “Image Target”. When a folder is set as Default, this folder is pre-selected when provisioning new Instances into the Cloud. When a folder is set as the Image Target, HPE Morpheus Enterprise will look into this folder to onboard VMware images into HPE Morpheus Enterprise.
+
+![../../../_images/addPerms.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C8A5BC12-8BBF-47AF-A193-BD89D2392417-high.png)
+
+### Usage
+
+vCenter
+:   - Non-Propagating
+
+Datacenter
+:   - Non-Propagating
+
+Cluster
+:   - Non-Propagating
+
+Host
+:   - Non-Propagating
+
+Datastore/Datastore Cluster
+:   - Propagating
+
+After completing the above steps, all VMware Cloud functionality should be available in HPE Morpheus Enterprise without running into permissions errors.
+
+## Creating a HPE Morpheus Enterprise VMware Image
+
+HPE Morpheus Enterprise comes out of the box with a default set of blueprints for use in many modern deployment scenarios. These consist mostly of base operating system images with a few additional adjustments. These adjustments typically include the addition of cloud-init (which is highly recommended to be used in most environments, but not mandatory). However, in many on-premise deployments there are custom image requirements as well as networking requirements. This guide will go over how to create a VMware Images for use within HPE Morpheus Enterprise.
+
+NOTE
+
+A HPE Morpheus Enterprise appliance may have many vCenter Clouds tied to any number of vCenter appliances. If the same images need to be available to multiple vCenter Clouds, you will need to download the OVF from one vCenter and upload it into the others. At that point you can make multiple HPE Morpheus Enterprise Node Types from the images and it will be available to all needed vCenter Clouds. This is a vCenter limitation but one which may not be obvious when provisioning via HPE Morpheus Enterprise.
+
+## Creating a Windows Image
+
+### Supported Versions
+
+2008R2, 2012, 2012R2, 2016, 2019, 2022
+
+### Image Preparation
+
+#### About this task
+
+Create a new machine in VMware vCenter and install a base version of your preferred Windows build. The smaller the VMDK drive, typically the faster you can clone and deploy. Utilizing HPE Morpheus Enterprise, provisioning and post deploy scripts can expand drives to desired sizing.
+
+#### Procedure
+
+1. Ensure VMware Tools is installed on the operating system.
+2. Apply any service packs / updates to the operating system.
+3. Configure WinRM to allow remote management and open the firewall. This is optional if using VMware Tools RPC mode for agent install and HPE Morpheus Enterprise Agent for guest exec. To enable this, under local computer Administrator, open a command prompt and run 
+
+   ```
+   ```
+   winrm quickconfig
+   ```
+   ```
+4. Install .Net at least 4.5.2
+5. Ensure Windows Firewall will allow WinRM connections.
+6. Shutdown the virtual machine and convert to a template.
+
+#### Results
+
+NOTE
+
+WinRM is not required and is used as a fallback when using vmtools guest exec and customizations
+
+NOTE
+
+Morpheus will sysprep images based on the “Force Guest Customizations” flag under the Virtual Image’s settings when using DHCP. Ensure a sysprep has not been performed on the template if this flag is enabled or if using Static IPs/IP Pools when provisioning, which will always use Guest Customizations and trigger a sysprep.
+
+IMPORTANT
+
+HPE Morpheus Enterprise supports the use of SR-IOV network adapters with VMware Clouds. Windows images must have SR-IOV network drivers installed to work with this adapter type. If they do not, provisioning will fail.
+
+## Creating a CentOS/RHEL 7 Image
+
+### About this task
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux distro build. If you are using cloud init as part of your image you will need to ensure your virtual machine has a cdrom.
+
+### Procedure
+
+1. Before installing the operating system setup a single `ext` or `xfs` partition without a swap disk (This is so that growpart can extend the disk. growpart currently does not support lvm)
+2. Install the distro and apply any updates to the operating system and security updates
+3. Install cloud-init using command `yum install cloud-init`
+4. Install cloud-utils-growpart using command `yum install cloud-utils-growpart`
+5. Install open-vm-tools using command `yum install open-vm-tools`
+6. Install git by running `yum install git`
+7. Install epel-release repo using command `yum install epel-release`
+8. selinux set to permissive (enforced can cause problems with cloud-init) `sudo vi /etc/selinux/config`
+
+### Cloud-Init
+
+To get started with a base CentOS image we first install cloud-init. This is a relatively simple process using yum:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+There are two parts to this yum installation. We are first ensuring some core dependencies are installed for automation as well as cloud-init. git for example is installed for use by ansible playbook automation down the line and is therefore optional if not using ansible. The dracut-modules-growroot is responsible for resizing the root partition upon first boot to match the virtual disk size that was potentially adjusted during provisioning.
+
+A great benefit to using cloud-init is credentials don’t have to be locked into the blueprint. It is advisable, within HPE Morpheus Enterprise , to configure the default cloud-init user that gets created when the vm boots automatically by cloud-init. This is located in Administration > Settings > Provisioning, within the Cloud-Init Settings section.
+
+### Network Interfaces
+
+A slightly annoying change with centOS 7 is that the network interfaces have changed naming convention. You may notice when running ifconfig that the primary network interface is set to something like ens2344 or some other random number. This naming is dynamic typically by hardware id and we don’t want this to fluctuate when provisioning the blueprint in various VMware environments. Fortunately, there is a way to turn this functionality off and restore the interface back to eth0.
+
+Firstly we need to adjust our bootloader to disable interface naming like this.
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The above command adds a few arguments to the kernel args list (namely `net.ifnames=0` and `biosdevname=0`. It may be useful to view the `/etc/default/grub` file and ensure these settings were indeed applied.
+
+The next step is to adjust the network-scripts in centOS. we need to ensure we have a file called `/etc/sysconfig/network-scripts/ifcfg-eth0`
+
+Below is a script that we run on our packer builds to prepare the machines network configuration files.
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to ensure there is a new ifcfg-eth0 config created to replace the old ens config file. Please do verify this config exists after running. If it does not you will have to be sure to build one on your own.
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+## Creating a CentOS/RHEL 8 Image
+
+Create a new virtual machine in VMware vCenter and install a base version of your preferred Linux build. You must be running ESXi 6.7 Update 2 or later.
+
+### Prepare The New CentOS 8/RHEL8 Image
+
+#### Procedure
+
+1. Install epel-release: `yum -y install epel-release` (This step is not necessary for RHEL)
+2. Install git, wget, curl, cloud-init, cloud-utils-gropart, and open-vm-tools: `yum -y install git wget curl cloud-init cloud-utils-growpart open-vm-tools`
+3. Update: `yum -y update`
+4. Finally run: `rpm -qa kernel | sed 's/^kernel-//' | xargs -I {} dracut -f /boot/initramfs-{}.img {}`
+
+### SELinux Settings
+
+#### About this task
+
+If allowed by your internal IT policies, set SELinux to permissive to avoid potential issues with cloud-init down the road.
+
+#### Procedure
+
+1. Edit the following: `vi /etc/selinux/config`
+2. Make the following change: `setenforce 0`
+
+### Network Interfaces
+
+#### About this task
+
+Run the following to rename the network NIC. Values inside angle brackets should be filled in with the appropriate value for your environment (ex. <varname>):
+
+#### Procedure
+
+1. `sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub`
+2. `grub2-mkconfig -o /boot/grub2/grub.cfg` (location may be different, could be located at /boot/efi/EFI/centos/grub.cfg)
+3. `ifdown <orginal-nic>`
+4. `mv /etc/sysconfig/network-scripts/<orginal-nic> /etc/sysconfig/network-scripts/ifcfg-eth0` (this changes name/device to eth0)
+5. Edit `ifcfg-eth0` and change the NAME to `eth0`
+6. `bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'`
+7. `ip link set <orginal-nic> down`
+8. `ip link set <orginal-nic> name eth0`
+9. `ip link set eth0 up`
+10. `ifup eth0`
+
+### Final VMWare Tasks
+
+#### Procedure
+
+1. Detach any install media
+2. Shutdown the VM
+3. Convert the VM to template on the HPE Morpheus Enterprise side
+4. Refresh the HPE Morpheus Enterprise Cloud to allow the new template to sync
+
+## Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Change the network interface to `eth0` by editing `/etc/default/grub`. The line `GRUB_CMDLINE_LINUX=""` should be edited to `GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"`.
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Gotchas
+
+SELinux can cause issues with cloud-init when in enforced mode. It may be advisable to set this to permissive unless it is mandatory within your organization to use an enforced SELinux configuration. If that is the case please see the documentation for the cloud\_init\_t security policies.
+
+Network Manager will also prevent the required restart of the Network Service when assigning static IP’s. Disable Network Manager when possible or Static IP assignment may not work until the Network Service is restarted manually.
+
+## A Note on Proxies
+
+Proxy configurations are known to vary in some organizations and makes building a base blueprint a little more difficult. In order to fully configure proxies a few environment variables must be set in the /etc/environment file (This can be done automatically in a default user-data script for cloud-init as well in edit cloud).
+
+```
+```
+http_proxy="http://myproxyaddress:8080"  
+https_proxy="http://myproxyaddress:8080"  
+ftp_proxy="http://myproxyaddress:8080"  
+no_proxy=127.0.0.1,localhost,applianceUrl  
+https_no_proxy=127.0.0.1,localhost,applianceUrl
+```
+```
+
+IMPORTANT
+
+It is very important to properly set the no\_proxy list (applianceUrl) should be replaced with the actual appliance url. In future releases, morpheus plans to automatically take care of this.
+
+NOTE
+
+If using cloud-init agent install mode these settings need to be set in the custom Cloud-Init User data section of “Edit Cloud” or “Edit Virtual Image”
+
+IMPORTANT
+
+If using this virtual machine as a docker host, proxy settings must also be configured in the docker config. See Docker guides for instructions on how to properly set this. If necessary this can be wrapped in a task automation workflow for your own use.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json b/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
new file mode 100644
index 0000000..937afc1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+  "title": "Overview",
+  "ordinal": 203,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md b/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
new file mode 100644
index 0000000..034a7d6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.md
@@ -0,0 +1,9 @@
+# Overview
+
+The OpenShift integration adds a new Cluster type, which can be added to HPE Morpheus Enterprise from the Clusters list page (Infrastructure > Clusters). Once a pre-existing OpenShift cluster is integrated, HPE Morpheus Enterprise can onboard any currently-running virtualized workloads along with the cluster hosts, network objects, storage objects, and virtual images needed to provision additional virtualized workloads. In addition to a new Cluster type, the OpenShift integration adds a new Instance Type to the provisioning wizard, which is used to provision new Instances to any integrated Clusters.
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise and is not part of the product by default. Information on accessing the plugin and adding it to the HPE Morpheus Enterprise appliance is included in a subsequent section.
+
+NOTE
+
+The OpenShift integration with HPE Morpheus Enterprise is currently limited to support of virtualized workloads only. There is not currently support for container-based workloads.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json b/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
new file mode 100644
index 0000000..65c48bc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+  "title": "Policies",
+  "ordinal": 315,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.html",
+  "topic_cluster": {
+    "clustering_title": "Policies",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BF226F62-E06D-4C61-8326-523D3F8CE492",
+        "clustering_title": "Policies"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md b/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
new file mode 100644
index 0000000..348ca41
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BF226F62-E06D-4C61-8326-523D3F8CE492.md
@@ -0,0 +1,8 @@
+# Policies
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-879CBF83-F8F8-4618-9B3C-9C3C5E4311D0.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html)**
+- **[Creating Policies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9F022B96-52CA-499B-978C-2CB55DCCAF48.html)**
+- **[Policy Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0441F3DD-FF73-49C0-8900-718B95266989.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json b/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
new file mode 100644
index 0000000..311634b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+  "title": "Workloads: Instance Usage",
+  "ordinal": 68,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html",
+  "topic_cluster": {
+    "clustering_title": "Workloads: Instance Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382",
+        "clustering_title": "Workloads: Instance Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md b/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
new file mode 100644
index 0000000..ae1328b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.md
@@ -0,0 +1,32 @@
+# Workloads: Instance Usage
+
+![../_images/10instanceusage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-70A9C315-58C0-4BF7-94E0-3F370A17D1E4-high.png)
+
+The Instance Usage dashboard shows Instance counts, resource utilization, and cost breakdowns by Cloud. Administrators can set filters to limit the workloads that are considered for dashboard analysis and then see the results given by Cloud groupings.
+
+## Filters
+
+Filter the workloads pulled into the dashboard by one or more of the following fields:
+
+- Instance name (all matching search terms)
+- Metric (apply to see the top Clouds by workload count, price, memory, storage, or CPU cores)
+- Group
+- Cloud
+- Tenant
+- Tag (Key)
+- Value (Tag value)
+
+## Data Displayed
+
+The following aggregate totals are compiled for workloads that meet set filters:
+
+- **CLOUDS:** The total number of Clouds represented among workloads meeting the dashboard filters
+- **INSTANCES:** The total number of Instances represented in the data
+- **MONTH TO DATE:** The total spend in the current month for selected workloads
+- **PROJECTED:** The total projected current-month spend for selected workloads
+- **MEMORY:** The total memory allotted to selected workloads
+- **STORAGE:** The total storage allotted to selected workloads
+
+## Instance Usage List
+
+All Clouds represented in the dashboard are listed here. For each Cloud, we see the total Instance count, total memory allotted, total storage allotted, total CPU cores, and the total price.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json b/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
new file mode 100644
index 0000000..57e25d0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+  "title": "HA Installation Overview",
+  "ordinal": 17,
+  "parent_title": "Installation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html",
+  "topic_cluster": {
+    "clustering_title": "HA Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983",
+        "clustering_title": "HA Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md b/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
new file mode 100644
index 0000000..94b277a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.md
@@ -0,0 +1,47 @@
+# HA Installation Overview
+
+HPE Morpheus Enterprise provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability (HA) configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the HPE Morpheus Enterprise HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the HPE Morpheus Enterprise appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Messaging Tier. Each of these tiers have their own recommendations for High availability deployments.
+
+IMPORTANT
+
+This is a sample configuration only. Customer configurations and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment.
+
+## Application Tier
+
+The application tier is easily installed with the same apt or yum repository package that HPE Morpheus Enterprise is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. They can be configured across all regions and placed behind a central load-balancer or geo-based load balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is shared storage, which is necessary when it comes to maintaining deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. Alternatively, a simple NFS cluster can also be used to handle the shared storage structure. Alternatively, supported (Platform as a Service) PaaS offerings can be used that provide a NFS compatible shared storage, eliminating the need to manage the underlying infrastructure.
+
+## Transactional Database Tier
+
+The Transactional Database tier consists of a MySQL compatible database. It is recommended that a lockable clustered configuration be used, such as a Galera cluster, which can also provide high availability. Alternatively, supported PaaS offerings can be used that provide a mySQL compatible database, eliminating the need to manage the underlying infrastructure.
+
+## Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an Opensearch cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a java based system and does require a sizable chunk of memory for larger data sets. Alternatively, supported PaaS offerings can be used that provide an Opensearch compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. Alternatively, supported PaaS offerings can be used that provide a RabbitMQ compatible deployment, eliminating the need to manage the underlying infrastructure.
+
+## HA Installation Architectures
+
+3-Node HA (Recommended)
+:   In this architecture, all tiers are deployed on three machines by HPE Morpheus Enterprise during the installation, with the exception of the Transactional Database Tier. This provides HA not just for the HPE Morpheus Enterprise Application Tier but all underlying tiers that support HPE Morpheus Enterprise. The Transactional Database Tier will remain external, either as a separate cluster or PaaS, following the supported services. An external MySQL cluster must still be set up outside of the HPE Morpheus Enterprise app nodes.
+
+Distributed HA
+:   In this architecture, the tiers do not need to reside on the same machines, each can be hosted by a supported cluster or PaaS offering. This provides flexibility and reuse of already existing technologies such as RabbitMQ or Opensearch. Each tier should be architected to provide HA following the vendor’s documentation, to ensure no downtime for the HPE Morpheus Enterprise Application Tier.
+
+## Supported PaaS Offerings
+
+The Morpheus Application Tier can be deployed to any public or private cloud. Morpheus has underlying technologies that support the Application Tier, which can be automatically installed and embedded on the applications nodes. Alternatively, the services can be provided externally and not be embedded. Many cloud providers have Platform as a Service (PaaS) offerings of these underlying technologies but some are not native or don’t provide the performance required. Below is a list of PaaS offerings that are supported to be used for Morpheus:
+
+Table 1. PaaS Offering Support
+
+       | Cloud | Messaging (RabbitMQ) | Log (Opensearch) | Database (mySQL) | Shared Storage (NFS) |
+| --- | --- | --- | --- | --- |
+| AWS | Amazon MQ | Amazon OpenSearch | Amazon Aurora | Elastic File System |
+| GCP | N/A | N/A | mySQL Instance | Cloud Filestore |
+| Azure | N/A | N/A | N/A | Storage Account |
+| OCI | N/A | N/A | N/A | N/A |
+| Alibaba | N/A | N/A | N/A | N/A |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json b/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
new file mode 100644
index 0000000..c87ee6e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+  "title": "Upgrading Overview",
+  "ordinal": 21,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html",
+  "topic_cluster": {
+    "clustering_title": "Upgrading Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45",
+        "clustering_title": "Upgrading Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md b/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
new file mode 100644
index 0000000..691656a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.md
@@ -0,0 +1,190 @@
+# Upgrading Overview
+
+IMPORTANT
+
+Known issue with embedded Opensearch upgrade: When upgrading to v5.4.8+, v5.4.9 or v5.5.1, there is a potential issue with embedded Opensearch clustering on rolling upgrades and existing data migration for all embedded Opensearch architechtures. Refer to the Release Notes for additional informaiton.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Upgrade Requirements
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and VM node packages from the package-repo when appliance free space is needed.
+
+IMPORTANT
+
+BACKUP YOUR DATABASE before the upgrade! You can use the [appliance backup job in Morpheus](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#create-a-backup-job), then [rollback and restore your appliance](https://docs.morpheusdata.com/en/latest/getting_started/guides/backup_restore.html#restoring-an-appliance-from-backup) if needed. Make sure you download the backup before you do the upgrade!
+
+- For firewall/proxy/acl considerations, the domain for Appliance, Supplemental and Agent packages was changed recently to <https://downloads.morpheusdata.com> from <https://downloads.gomorpheus.com>. Please update ACL’s to allow access to <https://downloads.morpheusdata.com> when necessary.
+
+### v8.1.2 Compatibility & Breaking Changes
+
+When installing and upgrading to HPE Morpheus Enterprise v8.1.2, refer to the following to ensure compatibility.
+
+#### Breaking Changes
+
+- 7.0.8, 8.0.0: On first ui startup after upgrade, HPE Morpheus Enterprise will normalize all IPv6 records within HPE Morpheus Enterprise-type pools. There will be a warning in appliance logs warning how many records will be normalized. This takes between 5-15 minutes per 1m records
+- 7.0.8, 8.0.0: Updated the AccountUsage table in the appliance database to accept LONGTEXT data type to prevent data from oversetting the table in specific scenarios. Note that this schema change will take time for databases with large numbers of account usage records
+- 6.3.0: Version 6.3.0 is the first version to require Plugin API 1.0.0+. Small changes will need to be made in order to make plugins created for prior versions of HPE Morpheus Enterprise compatible with 6.3.0+. See the [related article in our KnowledgeBase](https://support.morpheusdata.com/s/article/Making-plugins-compatible-with-Morpheus-6-3-0?language=en_US) on the small changes that will need to be made to ensure plugin compatibility
+- 6.2.2, 6.0.7 v8.0.7 contains embedded MySQL v8 upgrade when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1. BACKUP YOUR DATABASE PRIOR TO UPGRADE when using embedded MySQL (all-in-one appliances)
+- 6.2.2, 6.0.7 Minimum v6.x required to upgrade to v8.0.7 for environments using embedded RabbitMQ. Environments running 5.5.x or earlier using embedded RabbitMQ must upgrade to v6.0.0 - v6.0.6, or 6.1.0 - 6.2.1 prior to upgrading to v8.0.7
+- 6.2.2, 6.0.7 Rolling upgrades for HA environments using embedded RabbitMQ and/or embedded Elasticsearch services are not supported when upgrading from v6.0.0 - v6.0.6 or 6.1.0 - 6.2.1
+- 6.1.1 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records when upgrading from any version other than 6.0.3
+- 6.1.1 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades from any version other than 6.0.3 are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.1.1: NSX-V networking integration support is removed and no longer supported as of HPE Morpheus Enterprise 6.1.1
+- 6.0.3 contains database datatype mondifications on account\_invoice and account\_invoice\_item that may cause long initial ui start up times while the modifications are ran in MySQL for environments with over 100k invoice records.
+- 6.0.3 relocates the embedded plugin folder and remove the previous folder. For HA environments using shared storage, rolling upgrades are not advised as the embeeded plugins will not be found on non-upgraded nodes after one node is upgraded.
+- 6.0.0: NSX-V support is deprecated though still supported as of HPE Morpheus Enterprise 6.0.0. It will be removed and unsupported in 6.1.1 and higher.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, many third party integrations have been moved out of the core installer package and converted to HPE Morpheus Enterprise plugins. As a result, during the upgrade process your appliance will need to be able to access share.morpheusdata.com, the online repository for all HPE Morpheus Enterprise plugins. Where this is not possible, users may instead apply the supplemental installer package which is also available at HPE Morpheus Enterprise Hub alongside the main installer package.
+- 6.0.0+: In HPE Morpheus Enterprise 6.0.0+, older service specific system provided Instance Types and Layouts were deprecated and disabled. Updating to 6.0.0 will not affect existing Instances that are associated with the disabled types, however existing catalog item configurations, blueprints and api requests that use disabled Instance Types and layouts will need to be updated.
+- 5.5.2: VM Node Packages: Due to build java version requiremnets, the i386.deb and i386.rpm (32-bit) VM Node Packages can no longer be updated, and remain on v3.2.9.
+- 5.4.12: Guacd: Guacd is now complied iwth libssh2-1.10.0 on all platforms. Appliances on SLES15 may need openssl-devel manually installed for guacd to succesfully compile.
+- 5.4.12: Session Manager: Morpheus features a new session manager that was necessary in order to resolve expiring connections from the agents due to a Spring framework update. This new session manager no longer requires Sticky Sessions and they can now be turned off at the load balancer if so desired. However, keeping them on is totally reasonable as well as it reduces overall system load. Rolling restarts no longer kick you out of your session if sticky sessions are off as it distributes your session data across the morpheus nodes in an HA environment. Additionally, overall system load is reduced as a result of the new session manager.
+- 5.4.9: HPE Morpheus Enterprise 5.4.9 adds the “Provisioning: State” Role permission. This permission determines access to the State tab for Terraform-backed Instances and is set to “None” by default. On upgrade, only System Admin users will be able to see the State tab for these Instances. For other users who should have this access, edit their Roles to include “Provisioning: State” permissions.
+- 5.4.5: Warning: Database indexes added for account\_usage and metadata\_tag tables. Customers with very large account\_usage and/or metadata\_tag tables (10 million+) may experience slower initial morpheus-ui loading time after upgrading to 5.4.5, as well as additional database load.
+- 5.4.5: ‘AVI Load Balancer’ renamed to ‘NSX Advanced Load Balancer’
+- 5.4.5: Cloud Types disabled by default: Dell, HPE (NOT HPE Oneview), Supermicro and Cloud Foundry. Users would still be able to re-enable this clouds in the appliance settings. Does not affect existing Clouds.
+- 5.4.5: A10 Load Balancer type has been disabled, and will no longer be an option when adding new Load Balancers. This does not affect existing Load Balancers.
+- 5.4.5: HPE Morpheus Enterprise Cluster type “Combo Cluster” renamed to “KVM/Docker Cluster”
+- 5.4.5: Greenfield managed vm’s (provisioned with HPE Morpheus Enterprise) can no longer be deleted in HPE Morpheus Enterprise without removing the actual vm/infrastructure. Restriction does not apply to brownfield vm’s that have been converted to managed.
+- 5.4.4: The Venafi and AppDynamics integrations are deprecated in v5.4.4 and will be removed in v5.4.5. AppDynamic will return as a plugin at a later date.
+- 5.4.4: The morpheus-ui logging configuration file has changed from logback.groovy to logback.xml in v5.4.4 (/opt/morpheus/conf/logback.xml). The logback.groovy file from previous versions can be removed, and any updates to logback.groovy will not result in any logging configuration changes.
+- 5.4.3: vCloud Director: Support for integrations with vCD 9 ended
+- 5.4.3: HPE Morpheus Enterprise Worker/Gateway v5.4.3 packages are now available. Existing Worker & Gateway nodes must be upgraded to v5.4.3 for compatibility with HPE Morpheus Enterprise v5.4.3 Appliances.
+- 5.4.2: vCloud Director: vCD 9.x will no longer be supported by Morpheus
+- 5.4.2: ServiceNow: Instance and Blueprint specific exposures will be removed from ServiceNow plugin support. More advanced configurations of Instances and Blueprints, in addition to Workflows, can be exposed utilizing Catalog Items
+- 5.4.2: After upgrading, it is recommended that you manually perform one “Daily” refresh Amazon Clouds to ensure availability of Amazon Service Plans for each region. To manually refresh a Cloud, navigate to Infrastructure > Clouds > (Selected Amazon Cloud) and select “Daily” from the REFRESH dropdown menu. If this is not done, HPE Morpheus Enterprise may not show Amazon Service Plans in the provisioning wizard until after Midnight UTC following the upgrade when the next automatic Daily sync would run.
+- 5.3.3: Support for OpenStack v2 Identity API is removed
+- 5.3.2+: The local code repository path moved from `/var/opt/morpheus/morpheus-ui/repo` to `/var/opt/morpheus/morpheus-local/repo` to reduce potential shared storage issues and performance restrictions. The reconfigure process creates the folders and sets the paths in application.yml, no manual intervention is needed unless symlinks exisit on `/var/opt/morpheus/morpheus-ui/repo/git` which will need to be removed prior to reconfiguring - 5.3.2+ The deprecated `/var/opt/morpheus/morpheus-ui/repo` path will be automatically deleted in a future release but can be manually recursively deleted at any time for storage reclamation.
+- 5.3.2+: Provisioning ‣ Deployments has been moved to Provisioning ‣ Code ‣ Deployments
+- 5.2.9: OpenStack v2 Identity API is deprecated as of v5.2.9 (and is removed as of v5.3.3)
+- 5.2.6, 5.3.1: Appliance & Agent java version updated to `8u292-b10`. jdk8u292 disables TLS 1.0 and 1.1 by default
+- 5.2.3+: `codeready` (codeready-builder-for-rhel-8-x86\_64-rpms) repo access required for RHEL 8+ Appliances, replacing the previous PowerTools/powertools requirement
+- 5.2.1 & 4.2.5: API: Metadata: Metadata tags now referred to as `tags` and labels now referred to as `labels`. Previously metadata tags were referred to as `metadata` and labels were referred to as `tags`
+- 5.0.0+: When upgrading to 5.0.0+ from 4.x.x, any bearer tokens that have been generated are deleted which requires users to request new bearer tokens
+- 4.2.4: For appliances with externalized MySQL databases, due to MySQL deprecation of the “EDT” timezone you may need to update your database timezone to UTC or another compatible value. If this is not done, you will receive errors referencing timezone and HPE Morpheus Enterprise will not start. HPE Morpheus Enterprise should handle this change automatically for all-in-one appliances.
+- 4.2.1+: Tasks: Python: Virtual environment are now used for Python Tasks. Note: `virtualenv` is required on all Appliance App nodes
+- 4.2.1+: Puppet: HPE Morpheus Enterprise integration now supports version 6+. Puppet versions prior to 6 are no longer supported
+- 4.2.1+: Clouds: VirtualBox, VirtuSteam, and MetaCloud Cloud Types are no longer supported or available
+- 4.2.1+: Appliance: OS: Ubuntu 14.04 has reached its end of life (EOL) and is no longer supported as a Morpheus Appliance Host Operating System. Any HPE Morpheus Enterprise Appliance running on 14.04 must be upgraded to 16.04, 18.04, 20.04, 22.04 or 24.04 BEFORE upgrading to 4.2.1+. Upgrades on 14.04 will not succeed
+
+#### HPE Morpheus Enterprise Application OS
+
+HPE Morpheus Enterprise can be installed on the following platforms. Please note the table below is for HPE Morpheus Enterprise Application OS support, not HPE Morpheus Enterprise Agent OS Support.
+
+Table 1. Supported Appliance Operating Systems
+
+     | OS | Version(s) | Notes |
+| --- | --- | --- |
+| Amazon Linux | 2 |  |
+| CentOS | 7.x (deprecated). 8.x (stream) 9.x (stream) |  |
+| Debian | 11, 12 |  |
+| RHEL | 7.x (deprecated), 8.x, 9.x |  |
+| Oracle Enterprise Linux (OEL) | 7.x (deprecated), 8.x |  |
+| SUSE SLES | 15 |  |
+| Ubuntu | 20.04, 22.04, 24.04 | 14.04 is no longer supported for Appliance OS. Note: 14.04 is still supported by the HPE Morpheus Enterprise Agent. |
+
+#### Services
+
+##### v8.1.2 Service Versions & Compatibility
+
+Table 2. v8.1.2 Service Versions and Compatibility
+
+      | Service | Compatible Branch | Current Installer Version | Updated in v8.1.2 |
+| --- | --- | --- | --- |
+| Plugin API | 1.3.4 | 1.3.4 |  |
+| Morpheus Worker | 5.4.8+ |  |  |
+| MySQL | v8.0 | v8.0.40 | Yes |
+| MySQL (FIPS) | v8.0 | v8.0.36 |  |
+| OpenSearch | v8.9+ | v8.15.5 |  |
+| RabbitMQ | v3.5-3.13 | v3.13.7 |  |
+| Tomcat |  | v9.0.106 |  |
+| Nginx |  | v1.26.2 |  |
+| OpenSSL |  | 1.1.1w, 1.0.2u (FIPS) |  |
+| Java |  | 17.0.14+7 |  |
+| Java (MacOS Agent) |  | 11.0.14+9 |  |
+
+##### HPE Morpheus Enterprise Agent & Node Package Versions
+
+Table 3. v8.1.2 Agent & Node Package Versions
+
+     | Package | Version | v8.1.2 changes from v8.1.1 |
+| --- | --- | --- |
+| Morpheus Node and VM Node Packages | 3.3.11 | Updated to 3.3.11 |
+| Morpheus Linux Agent | v3.1.0 | Updated to v3.1.0 |
+| Morpheus Windows Agent | v2.6.1.0 | No changes |
+| Morpheus macOS Agent | v2.4.0 | No changes |
+
+##### HPE Morpheus Enterprise Software Upgrade Paths
+
+Depending on the specific changes from version to version, HPE Morpheus Enterprise may support rolling upgrades for multi-node HA appliances. For some version hops, specific changes such as database schema modifications may make the upgrade unsuitable for a rolling upgrade. Use this table to confirm if a rolling upgrade will be possible in each case. Instructions for both rolling and non-rolling upgrades are contained in this documentation.
+
+Table 4. v8.1.2 Upgrade Paths
+
+                   | From Version | To 8.0.1 | To 8.0.2 | To 8.0.3 | To 8.0.4 | To 8.0.5 | To 8.0.6 | To 8.0.7 | To 8.0.8 | To 8.0.9 | To 8.0.10 | To 8.0.11 | To 8.0.12 | To 8.0.13 | To 8.1.0 | To 8.1.1 | To 8.1.2 |
+| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
+| Versions 6.0.0 - 7.0.11 | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.0 | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.1 | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.2 | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.3 | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.4 | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.5 | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.6 | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.7 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.8 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.9 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.10 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.11 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.12 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.0.13 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ | Non-Rolling️ |
+| 8.1.0 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Non-Rolling️ | Non-Rolling️ |
+| 8.1.2 | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | **X** | Rolling️ |
+
+#### Integrations
+
+NOTE
+
+Current iterations of Amazon AWS, Microsoft Azure, Google Cloud Platform, Digital Ocean, OpenTelekom Cloud, IBM Bluemix, Softlayer and UpCloud are all supported.
+
+Table 5. Integration Compatibility
+
+     | Integration | Supported Version(s) | Notes |
+| --- | --- | --- |
+| Ansible | 2.7.x or higher |  |
+| Ansible Tower | 3.8.x |  |
+| App Dynamics | 4.5.x |  |
+| ArubaCX | 8325 series ‐ GL.10.10.x or higher |  |
+| Avamar | 18 |  |
+| Azure Stack | 2002 back to 1908 | `2019‐03‐01‐hybrid` api‐profile version used which is supported in 1908 and later Azure Stack versions |
+| Cisco ACI | 3.x,4.x,5.x |  |
+| Citrix Netscaler | v12.1 |  |
+| Commvault | v11 sp 19 |  |
+| F5 Big‐IP | 11.4+ |  |
+| HPE Alletra MP Storage | 10.4.2 or higher |  |
+| Infoblox | Latest Versions Supported |  |
+| Kubernetes | 1.21+ |  |
+| Microsoft Hyper‐V | 2012R2, 2016, 2019, 2022, 2025 |  |
+| Nutanix AOS | For HPE Morpheus Enterprise version 6.3.4 and higher, Nutanix AOS version 6.5.3.7+ is required. See the [Nutanix Compatibility and Interoperability table](https://portal.nutanix.com/page/documents/compatibility-interoperability-matrix/software?partnerName=Morpheus%2520Data&solutionType=all&componentVersion=all&hypervisor=all&validationType=all) for additional information | In 5.5 ‐ 5.7 if Prism Central is managing Prism Element, image creation will not function due to PC Image Management. |
+| Nutanix Prism Central | Plugin QA tested against pc.2024.3.0.1 | Nutanix Prism Central Cloud integration is added through an officially‐developed plugin. See share.morpheusdata.com and the Prism Central integration guide in this documentation for more details. |
+| Openstack | Latest Versions Supported | When creating an OpenStack integration, select the latest available from the OS Version dropdown menu when running a later version |
+| Puppet | 6+ | Puppet Agent version will be latest 6 version from yum.puppetlabs.com or apt.puppetlabs.com |
+| Rubrik | Up to 7.x |  |
+| SCVMM | 2016, 2019, 2022, 2025 |  |
+| ServiceNow | Per servicenow plugin version | Refer to the [servicenow store](https://store.servicenow.com/sn_appstore_store.do#%21/store/application/8d8b6bbf0ff07e009c84306be1050e67) for Morpheus Catalog compatibility |
+| Terraform | Latest | When HPE Morpheus Enterprise is handling Terraform installation, the version used will be 1.5.5 for licensing reasons. If a later version is required, you will need to manually handle Terraform installation. See the “Terraform Installation” section of HPE Morpheus Enterprise docs for more details. |
+| vCloud Director | 10.0, 10.2, 10.3, 10.4 | When upgrading a vCD environment, you should update the API Version setting on the HPE Morpheus Enterprise Cloud configuration first |
+| Veeam | 11, 12, 12 |  |
+| VMware ESXi | 6.5, 6.7, 7, 8 |  |
+| VMware Fusion | 8, 9, 10+ |  |
+| VMware NSX | NSX (up to 4.1) |  |
+| VMware vCenter | 5.5, 6.0, 6.5, 6.7, 7.x, 8.x |  |
+| XenServer | 7.x |  |
+| Zerto | 10 |  |
+
+NOTE
+
+Non-listed versions may be compatible but are not verified.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json b/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
new file mode 100644
index 0000000..d6c6a0f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+  "title": "Puppet",
+  "ordinal": 379,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.html",
+  "topic_cluster": {
+    "clustering_title": "Puppet",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1680569-1170-4460-B42D-9B8D3D5125B6",
+        "clustering_title": "Puppet"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md b/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
new file mode 100644
index 0000000..e7a29ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1680569-1170-4460-B42D-9B8D3D5125B6.md
@@ -0,0 +1,61 @@
+# Puppet
+
+Each HPE Morpheus Enterprise Puppet integration ties to a specific Puppet Master and makes it easy to install the Puppet Agent onto target Instances and Servers. Once integrated, we can trigger the agent installation by creating Puppet Agent Install Tasks through HPE Morpheus Enterprise automation or at provision time when spinning up instances in Clouds associated with a Puppet integration.
+
+## Add Puppet Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Click + NEW INEGRATION
+3. Select Integration type “Puppet”
+4. Populate the following fields 
+
+   - Name: A friendly name for this Puppet integration in HPE Morpheus Enterprise
+   - Enabled: When marked, this Puppet integration will be available to users at provision time and when creating Tasks
+   - Puppet Master (Hostname): The resolvable DNS name to the Puppet Master, communicating on port 443 by default
+   - Allow Immediate Execution: Yes or No (See additional details below)
+5. Click SAVE CHANGES 
+
+   ![../../_images/new_puppet_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-89930173-D087-4C3D-AD78-83569C611401-high.png)
+
+### Allow Immediate Execution
+
+When adding or editing a Puppet integration, users have the option to “Allow Immediate Execution”. Using this feature will connect to the Puppet Master after the Puppet Agent is installed and force configuration application immediately. This is an optional convenience feature, if it’s not used, the Puppet Master will still apply configuration to the node on its own schedule. Using this feature requires supplying SSH credentials. If you do not wish to provide SSH credentials to HPE Morpheus Enterprise select “No” to opt out of this feature and they do not need to be provided.
+
+## Associating a Puppet Integration with a Cloud
+
+### About this task
+
+By associating a Puppet Integration with a Cloud, users are able to automatically install the Puppet Agent, select a Puppet environment, and supply a Puppet Node Name at provision time. The integration association is made when adding or editing a Cloud integration in HPE Morpheus Enterprise.
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Identify the Cloud to associate with Puppet and edit it by clicking on the pencil icon at the right end of the row
+3. In the EDIT CLOUD modal, expand the Advanced Options section
+4. In the CONFIG MANAGEMENT dropdown, choose the Puppet integration
+5. Save changes to the Cloud integration
+
+## Creating Puppet Agent Install Tasks
+
+### About this task
+
+Puppet Agent Install Tasks automate the process of installing the Puppet Agent, selecting the Puppet environment, and supplying the Puppet Node Name. We can run this Task on-demand as needed for individual Instances or servers or add them to workflows to build a Puppet Agent installation step into larger automation suites.
+
+### Procedure
+
+1. Navigate to Library > Automation
+2. Select the Tasks tab
+3. Click + ADD
+4. From the “Type” field, select Puppet Agent Install
+5. Complete the fields as needed to target a specific Puppet Master and to identify Puppet environment and node names
+6. Save changes
+
+### Results
+
+![../../_images/puppet_task.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F59908B8-FAEC-4C47-859E-087396FDCB98-high.png)
+
+## Installing Puppet Agent at Provision Time
+
+With a Puppet integration associated with a Cloud (as described above), users can opt to install the Puppet Agent at provision time. When provisioning into an associated Cloud, a new “Puppet” section will appear on the CONFIGURE tab of the provisioning wizard. Here users can select a specific Puppet Master, select the Puppet environment, and select a Puppet node name. During provisioning, the Puppet Agent will be automatically installed and configured for the selected Master.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json b/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
new file mode 100644
index 0000000..fa1282e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+  "title": "Provisioning Concepts",
+  "ordinal": 81,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Concepts",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E",
+        "clustering_title": "Provisioning Concepts"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md b/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
new file mode 100644
index 0000000..70f85a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.md
@@ -0,0 +1,31 @@
+# Provisioning Concepts
+
+HPE Morpheus Enterprise is a powerful infrastructure-agnostic Cloud Application Management Platform. Compared to other CMP platforms in the space, some terminology and concepts may differ. These concepts are documented in this section along with places where terminology may be slightly different compared with other platforms or with common industry parlance.
+
+HPE Morpheus Enterprise refers to itself as a CAMP (Cloud Application Management Platform) as opposed to a (Cloud Management Platform). While that may seem minor, it actually is a big deal. Many CMP applications start at the IaaS layer and work up to the application layer (often needing additional PaaS architectures to fill out the model). HPE Morpheus Enterprise was designed from a middle-ground perspective. As such, some concepts are a bit different. This provides a more complete platform that allows for greater capabilities out of the box as will be seen when these concepts are covered.
+
+## Instances
+
+HPE Morpheus Enterprise starts with provisioning Instances. In some platforms, an Instance is representative of a singular object like a virtual machine in Amazon AWS. In HPE Morpheus Enterprise, this concept was rethought. An Instance is more of a representation of a resource or service. This service may involve several virtual machines or several Docker containers.
+
+For example, in the HPE Morpheus Enterprise Instance wizard, MongoDB is an option and contains several Instance configurations. One of these configurations is a full MongoDB cluster consisting of either seven virtual machines or seven Docker containers. Rather than representing these directly as seven individual “instances”, HPE Morpheus Enterprise groups them together into a singular Instance of a service that contains multiple containers or virtual machines within it. This even allows for Instance actions that can be performed to expand capacity on an Instance (either horizontally or vertically). In the past, a database server may have been representative of a singular server, but this model has drastically changed in a big data world. This same concept also can apply to something like a simple Apache web server where there are 10 copies of a web server which are horizontally scaled out to handle traffic.
+
+When viewing an Instance detail page, one is able to look at details and statistics specific to a virtual machine or container. HPE Morpheus Enterprise simply helps simplify the management model for tracking these services.
+
+## Containers / Nodes / Virtual Machines
+
+In relation to Instances, an Instance can have many nodes. A node is a generic representation of a container or a virtual machine. In most cases, HPE Morpheus Enterprise will represent a node as a Container or Virtual Machine depending on the provisioning engine used for the Instance. Node is just a generic naming representation when referring to these types of items. The public HPE Morpheus Enterprise developer API, however, often refers to both virtual machines and Docker containers as “containers”. The UI was since updated to better delineate this concept for easier understanding but, in essence, the name is valid for both concepts of containerized environments as well as Virtual Machines. In fact, one can even think of a Docker Host as a Hypervisor (which we do).
+
+## Hosts / Servers
+
+This concept is mostly tailored to users of HPE Morpheus Enterprise who are responsible for managing and maintaining the underlying infrastructure integrations. A Host typically refers to a Docker Host in which a container (within an Instance) is running, or a hypervisor that virtual machines can be provisioned onto. A server is the underlying general representation of a physical or virtual server. It could be a Host representation, a Virtual Machine, or even a Bare Metal delineation.
+
+When a user provisions a VM-based Instance, a corresponding server record is created to represent the link to the actual resource via the underlying provisioning engine. This may seem a bit odd but provides an aspect of HPE Morpheus Enterprise that is quite powerful. This singular concept is what allows HPE Morpheus Enterprise to ingest “brownfield” environments. We do not need to start clean. HPE Morpheus Enterprise can be integrated into existing environments and manage existing virtual machines. The way HPE Morpheus Enterprise does this is by periodically syncing existing VMs from the added cloud integrations. A server record will be created and periodically updated (every five minutes, by default) with realtime information and changes. This, in essence, provides CMDB-like capabilities as well. When a server is discovered, the user (given the appropriate access) can convert the virtual machine to a managed Instance. When this is done, a corresponding Instance is made in the provisioning section of HPE Morpheus Enterprise and the HPE Morpheus Enterprise Agent can optionally be installed to provide more refined guest operating system-level statistics and logging.
+
+## Apps
+
+On top of all the previous concepts, HPE Morpheus Enterprise provides an Apps layer. An App is a collection of Instances linked together via application tiers. Tiers allow the user to define segregated sections of connectivity between the various elements (Instances) within an application. Once these Instances are all linked together in an application concept, this may affect Instance environments and provide service discovery capabilities for them to cross connect. There are several service discovery aspects within HPE Morpheus Enterprise as well as integrations with services.
+
+## App Blueprints
+
+An App Blueprint allows a user to define an application structure for easy reproducibility and deployment into various environments. They can be used to mix and match various Instance types to provision an application dependent on multiple layers of services.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json b/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
new file mode 100644
index 0000000..6c2c121
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+  "title": "Credentials",
+  "ordinal": 237,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.html",
+  "topic_cluster": {
+    "clustering_title": "Credentials",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27",
+        "clustering_title": "Credentials"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md b/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
new file mode 100644
index 0000000..3c7d2a6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1CAC383-1FBB-4D17-B097-F2D67A084C27.md
@@ -0,0 +1,27 @@
+# Credentials
+
+The credentials section allows for various credential types to be securely stored and called back when necessary, such as when creating new integrations with Cloud accounts or other outside technologies. Credentials can also be used to populate REST-based Option Lists sourced from data behind an authentication wall, as well as to run automation Tasks on remote targets that require authentication. Credentials can be securely stored internally on the appliance or stored in an external Cypher integration, more information about setting up and integrating with an external Cypher store are in the next section. The following credential pair types are currently supported:
+
+- Access Key and Secret Key
+- Client ID and Secret
+- Email and Private Key
+- OAuth 2.0
+- Tenant, Username, and Keypair
+- Username and API Key
+- Username and Keypair
+- Username and Password
+- Username, Password, and Keypair
+
+To create a new credential set, click + ADD and then select the type of credential set you’d like to store. Complete the following:
+
+- **CREDENTIAL STORE:** Select “Internal”, an integrated external Cypher store (if any), or an integrated Hashicorp Vault server (if any). See the section below for instructions on integrating with Vault or standing up and integrating with an external Cypher store.
+- **NAME:** A name for the credential set in HPE Morpheus Enterprise
+- **DESCRIPTION:** An optional description for the credential set
+- **ENABLED:** If checked, the credential set will be available for use
+- **CREDENTIAL VALUES:** Depending on the credential pair type selected (listed above), the remaining fields will be specific to the chosen type. See the next section for a more complete walkthrough on storing and using OAuth 2.0 credentials
+
+![../../_images/addCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6107BD26-E1BA-4F6E-888A-10CEDF3C01D7-high.png)
+
+Finally, click ADD CREDENTIALS. Once saved, the credential set will be available for selection where appropriate in HPE Morpheus Enterprise UI. In the screenshot below, I’m integrating a new VMware Cloud. In the credentials section, I have the following options: Creating (and using) a new Username and Password credential set (which includes the option to save internally or to an external Cypher store), choosing a previously-stored credential set, or simply entering my credentials locally and not saving them for reuse.
+
+![../../_images/useCredentials.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-714A8DE9-4992-4DB9-B9E2-5CAAD363B7A2-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json b/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
new file mode 100644
index 0000000..f2972a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+  "title": "Plans",
+  "ordinal": 289,
+  "parent_title": "Plans",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html",
+  "topic_cluster": {
+    "clustering_title": "Plans",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243",
+        "clustering_title": "Plans"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md b/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
new file mode 100644
index 0000000..e41c538
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.md
@@ -0,0 +1,118 @@
+# Plans
+
+Plans types include Service Plans and Price Plans. Service Plans determine the memory, storage and cores configuration during provisioning and reconfigure.
+
+## Service Plans
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
+
+### Service Plan Configuration
+
+NOTE
+
+Not all fields listed below are available for every provision type. After selecting the provision type, the correct fields for that type of Service Plan will be revealed. Not all fields are required to save a valid Service Plan
+
+- **NAME:** The name of the Service Plan in HPE Morpheus Enterprise
+- **ACTIVE:** Inactive Service Plans are not available for selection during provisioning or reconfigure. New discovered records cannot be associated with deactivated Plans when converting to managed resources. Any resources attached to a Plan will continue to be associated if the Plan is later deactivated
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **DISPLAY ORDER:** Configures the order in which plans are displayed relative to other plans associated with the same provision type. Note that Plans will be displayed in low-to-high order based on the Display Order property. This is reversed from Layouts which are displayed in high-to-low order
+- **PROVISION TYPE:** Determines the resource Provision Type this Service Plan is available for when provisioning, reconfiguring and converting discovered resources to managed
+- **REGION CODE:** (Optional) Limits availability of the Service Plan to Clouds with the specified Region Code
+- **STORAGE:** The default storage size of the root volume (in MB or GB)
+- **CUSTOMIZE ROOT VOLUME:** Allows the root volume size to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CUSTOMIZE EXTRA VOLUMES:** Allows the extra volume sizes to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **ADD VOLUMES:** Allows additional volumes to be added during provisioning or reconfigure
+- **MEMORY:** The amount of memory included with the plan (in MB or GB)
+- **CUSTOM MEMORY:** Allows the amount of memory to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORE COUNT:** The number of virtual CPU cores included with the plan
+- **CUSTOM CORES:** Allows the number of virtual CPU cores to be customized during provisioning or reconfigure. Custom Range limits, if set, will apply
+- **CORES PER SOCKET:** Determines core distribution across sockets. CORES PER SOCKET cannot be larger than CORE COUNT, and CORE COUNT must be divisible by CORES PER SOCKET. For example four CORES with two CORES PER SOCKET means two sockets would have two cores each assigned. Four CORES with one CORE PER SOCKET would have four sockets with one core each assigned, and four CORES with four CORES PER SOCKET would have one socket with four cores assigned
+- **TOTAL STORAGE:** When custom storage is enabled for the plan, this sets a minimum and maximum total storage allowed (all disks combined)
+- **PER DISK SIZE:** When custom storage is enabled for the plan, this sets the minimum and maximum storage for each disk
+- **CUSTOM MEMORY RANGE:** The minimum and maximum allowed amount of memory for the Plan when CUSTOM MEMORY is enabled for the Plan
+- **CUSTOM CORES RANGE:** The minimum and maximum allowed amount of virtual CPU cores for the Plan when CUSTOM CORES is enabled for the Plan
+- **SOCKETS:** The minimum and maximum allowed sockets range for the Plan when CUSTOM CORES is enabled for the Plan
+- **CORES PER SOCKET:** The minimum and maximum allowed cores per socket for the Plan when CUSTOM CORES is enabled for the Plan
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. See [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+TIP
+
+Custom Range storage and memory values units (GB/MB) are inherited from the :STORAGE:: and :MEMORY:: GB/MB settings in the same Plan. For example, if :STORAGE: is configured for for 40 GB, a custom range for Storage would also be in GB.
+
+### Create Service Plan
+
+#### About this task
+
+HPE Morpheus Enterprise offers a few distinct types of service plans, each with different data fields to track and valid Price Set types which can be associated. For more on Service Plan configuration, see the preceding section.
+
+Price Sets can be added to the Plan at creation time so often it makes sense to create the Prices and associate them with Price Sets before creating the Plan. Additional instructions for creating Prices and Price Sets are in the next section. With the Price Sets ready, continue with the instructions below to create Price Plans of various types.
+
+#### Procedure
+
+1. Navigate to Administration > Plans & Pricing (`/admin/service-plans`)
+2. Click the + ADD dropdown and select the appropriate Plan type
+3. Configure details for the Plan on the General tab, the configuration options will depend on the Plan type. See the section above for a detailed description of each configuration option available for Service Plans
+4. On the Price Sets tab, associate all relevant Price Sets with the Plan. The desired Price Sets must already exist. If needed, you may save the Plan at this point and come back to associate Price Sets later
+5. Click SAVE CHANGES
+
+### Add Price Set(s) to Plan
+
+#### Procedure
+
+1. Select a Price Unit to list available Price Sets which have the selected Price Unit. Available Price Sets are filtered to show only those which are relevant for the Plan type you’ve selected
+2. Select a Price Set from the list and click + ADD
+3. Add additional Price Sets if desired (multiple Price Sets can be associated with a Plan)
+4. Added Price sets can be removed from a Plan by clicking the 🗑 icon
+5. Once all Price Sets have been added, select SAVE CHANGES
+
+#### Results
+
+TIP
+
+The +ADD button must be clicked after selecting a Price Set or it will not be added to a Plan.
+
+### Service Plan Permissions
+
+Group and Tenant Access permissions determine availability of a Service Plan.
+
+- Group Access determines what Groups the Service Plan will be available in for Provisioning and Reconfigure.
+- Group Access settings only apply to the Tenant they are configured in, as Groups are not multi-tenant.
+- For multi-tenant environments, the Master Tenant can set Tenant Permissions to determine if the Service Plan is available to all Tenants (public visibility) or assign the Service Plan to one or multiple Tenants.
+
+### Removing Plans
+
+Plans can be removed by navigating to the Service Plans list page (Administration > Plans & Pricing > Plans), opening the ACTIONS menu for a Plan, and then selecting “Remove”. Removing a Plan makes it no longer visible, however, it does not hard delete the Plan as the record must remain for any existing associations’ usage and price tracking. Synced Plans should be deactivated rather than removed.
+
+## Load Balancer Price Plans
+
+Load Balancer Price Plans configure pricing for Load Balancers and Load Balancer Virtual Servers.
+
+Load Balancer Price Plan Configuration:
+
+- **NAME:** The name of the Load Balancer Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **LOAD BALANCER TYPE:** Select the load balancer type the Price Plan should be associated with
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Load Balancer Price Sets may be associated with Load Balancer-type and Load Balancer Virtual Server-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Virtual Image Price Plans
+
+Virtual Image Price Plans configure pricing for Virtual Images. Pricing is associated per Price and Price Set configurations, but in general applies to Images with location records in the Price Plans specified Cloud type. Virtual Image Price Plans are for setting pricing for Virtual Image storage, not for adding pricing to resources that use Virtual Images associated with Virtual Image Price Plans. Virtual Image Price Plans do not apply to uploaded Virtual Images that have not been copied to a location in the specified Cloud type yet.
+
+Virtual Image Price Plan Configuration:
+
+- **NAME:** The name of the Virtual Image Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Virtual Image Pricing applies to Virtual Images with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Virtual Image Price Sets may be associated with Storage-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
+
+## Snapshot Price Plans
+
+Snapshot Price Plan Configuration:
+
+- **NAME:** The name of the Snapshot Price Plan in HPE Morpheus Enterprise
+- **ACTIVE:** When Active, Prices in Price Sets added to the Price Plan will apply to associated resources as configured
+- **CODE:** A unique identifier for use in HPE Morpheus Enterprise API and CLI
+- **CLOUD TYPE:** Snapshot Pricing applies to Snapshots with location records in the specified Cloud type
+- **PRICE SETS:** In the Price Sets tab, associate Price Sets with the Plan. Snapshot Price Sets must have at least one Storage-type Price but may also have Datastore-type Prices. Fore more, see [Add Price Set(s) to Plan](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1E03C38-4DD6-43E9-8310-61A2FE452243.html#GUID-A2E34E1B-1A4A-4D63-9985-F7220012659C)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json b/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
new file mode 100644
index 0000000..2699595
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+  "title": "Navigation Updates",
+  "ordinal": 530,
+  "parent_title": "See Also",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html",
+  "topic_cluster": {
+    "clustering_title": "Navigation Updates",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94",
+        "clustering_title": "Navigation Updates"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md b/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
new file mode 100644
index 0000000..cea3df9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.md
@@ -0,0 +1,38 @@
+# Navigation Updates
+
+[  ](https://www.youtube.com/embed/B46qgEwoblY)
+
+v8.0.7 contains major changes to the UI navigation structure. The following table lists updated paths for affected sections.
+
+NOTE
+
+API endpoints are not affected by the UI navigation changes
+
+Table 1.
+
+     | Target | Old Path | New Path |
+| --- | --- | --- |
+| Blueprints | provisioning > blueprints | library > blueprints |
+| Automation | provisioning > automation | library > automation |
+| Tasks | provisioning > automation > tasks | library > automation > tasks |
+| Workflows | provisioning > automation > workflows | library > automation > workflows |
+| Executions | provisioning > automation > executions | provisioning > executions |
+| Scale Thresholds | provisioning > automation > scale thresholds | library > automation > scale thresholds |
+| Power Scheduling | provisioning > automation > power scheduling | library > automation > power scheduling |
+| Execute Scheduling | provisioning > automation > execute scheduling | library > automation > execute scheduling |
+| Automation Integrations | provisioning > automation > integrations | library > integrations |
+| Security Packages | provisioning > jobs > security packages | library > templates > security packages |
+| Virtual Images | provisioning > virtualimages | library > virtualimages |
+| Library | provisioning > library | library |
+| Instance Types | provisioning > library > instance types | library > blueprints > instance types |
+| Layouts | provisioning > library > layouts | library > blueprints > layouts |
+| Node Types | provisioning > library > node types | library > blueprints > node types |
+| Option Types (Inputs) | provisioning > library > option types | library > options > inputs |
+| Option Lists | provisioning > library > option lists | library > options > option types |
+| File Templates | provisioning > library > file templates | library > templates > file templates |
+| Scripts | provisioning > library > scripts | library > templates > script templates |
+| Spec Templates | provisioning > library > spec templates | library > templates > spec templates |
+| Cluster Layouts | provisioning > library > cluster layouts | library > blueprints > cluster layouts |
+| Catalog/Self Service | tools > selfservice | library > blueprints > catalog items |
+| Service Catalog | service catalog persona | provisioning > catalog& service catalog persona |
+| Logs | logs | monitoring > logs |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json b/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
new file mode 100644
index 0000000..e78625c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+  "title": "Getting started with HPE Morpheus Enterprise and VMware",
+  "ordinal": 362,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html",
+  "topic_cluster": {
+    "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C20033B6-4C42-4BEC-84C0-D313859D9126",
+        "clustering_title": "Getting started with HPE Morpheus Enterprise and VMware"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md b/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
new file mode 100644
index 0000000..873bfb3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.md
@@ -0,0 +1,514 @@
+# Getting started with HPE Morpheus Enterprise and VMware
+
+## Introduction
+
+This guide is designed to help you get started and quickly get the most out of HPE Morpheus Enterprise with VMWare. By the end, you will integrate your first cloud, configure networking, prepare and consume images, provision instances, and get started with automation. We will briefly discuss installation and account setup but will provide links to additional resources for those very first steps. For the most part, this guide assumes you are able to get HPE Morpheus Enterprise installed and are ready to move forward from that point. There is a lot more to see and do in HPE Morpheus Enterprise that is beyond the scope of this guide. For more, consult the complete HPE Morpheus Enterprise documentation or take part in our user community forum.
+
+## Installation & Setup
+
+In the simplest configuration, HPE Morpheus Enterprise needs one appliance server which will contain all the components necessary to orchestrate virtual machines and containers. Full requirements, including storage and networking considerations, can be found in HPE Morpheus Enterprise documentation [here](https://docs.morpheusdata.com/en/4.1.0/getting_started/requirements/requirements.html#requirements). In order to provision any new instances, hosts, or applications, (or convert any discovered resources to managed resources) you will need a valid license. If you don’t have one, you can request a lab license for free at [Morpheus Hub](https://app.morpheushub.com). Once obtained, the license can be applied in Administration > Settings > License.
+
+## Groups
+
+Groups in HPE Morpheus Enterprise define which resources a user has access to. Clouds are added to groups and a user can only access clouds that are in the groups to which their roles give them access. More information on HPE Morpheus Enterprise groups is [here](https://docs.morpheusdata.com/en/4.1.1/infrastructure/groups/groups.html#groups). A deep dive into groups goes beyond the scope of this guide but it’s often useful to create a group that contains all clouds for testing purposes. We will create that group now so that we can add our first cloud into this group in the next section.
+
+Navigate to Infrastructure  >  Groups. Here we will see a list of all configured groups but, of course, this will be empty immediately after installation. Click “+CREATE”. Give your group a name, such as “All Clouds”. The “CODE” field is used when calling HPE Morpheus Enterprise through HPE Morpheus Enterprise API or HPE Morpheus Enterprise CLI. It’s useful in most cases to have an “All Clouds” group for testing purposes so this will likely help you down the road.
+
+![The new group dialog box showing a name for the group filled in](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-74C68A7E-D6DD-4E56-A374-AF1DCA8F68DA-high.png)
+
+Click “SAVE CHANGES”. Your group is now ready to accept clouds.
+
+## Integrating Your First Cloud
+
+Clouds in HPE Morpheus Enterprise consist of any consumable endpoint whether that be On-Prem, Public clouds, or even bare metal. In this guide, we will focus on integrating and working with VMWare vCenter.
+
+To get started, we will navigate to Infrastructure  >  Clouds. This is the cloud detail page which lists all configured clouds. It will be empty if you’ve just completed installation and setup of HPE Morpheus Enterprise but soon we will see our integrated vCenter cloud here.
+
+Click the “+ADD” button to pop the “CREATE CLOUD” wizard. Select “VMWARE VCENTER” and click the “NEXT” button.
+
+![The list of clouds available to integrate with, vCenter is selected](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-37B199A3-DCEC-41E4-AE0B-8BE8A37EA55B-high.png)
+
+On the “CONFIGURE” tab, we’re asked to set the initial connection strings into vSphere. The **API URL** should be in the following format: <https:/>/<URL>/sdk. The **USERNAME** should be in [user@domain](mailto:user%40domain) format.
+
+![The create cloud dialog box with relevant fields filled](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-670B6AE2-46C2-4917-A452-B8D72082823E-high.png)
+
+HPE Morpheus Enterprise allows vCenter clouds to be scoped to the **VDC** and **CLUSTER** or even the specific **RESOURCE POOL** if you choose. Once you’ve entered your URL and credentials, these dropdown menus will become populated.
+
+The **RPC MODE** setting determines how HPE Morpheus Enterprise will connect to VMs and make configuration and scripting calls if [Morpheus Agent](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent) is not installed. In a VMware environment, it is recommended to select **Vmware Tools** but WinRM/SSH are able to be used to configure the guest directly. If using WinRM, ensure it is configured on the virtual image, discusssed below.
+
+Additionally, we can opt to **INVENTORY EXISTING INSTANCES** to begin polling VMs for statistics and rightsizing recommendations as well as **ENABLE HYPERVISOR CONSOLE** to use native vSphere console with port 443 connectivity between HPE Morpheus Enterprise and ESXi hosts.
+
+To move on, expand the “Advanced Options” section.
+
+Within the “Advanced Options” drawer are additional configurations to consider for your first cloud. Some of these won’t usable until they reference additional configured integrations. Common settings to consider are **DOMAIN**, **STORAGE TYPE**, **APPLIANCE URL** (overrides the HPE Morpheus Enterprise URL for external systems), **GUIDANCE** (setting “Manual” will make recommendations for rightsizing), and **AGENT INSTALL MODE**.
+
+![The advanced options section of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5564447E-D7BC-4DE8-832D-D63909A3B49E-high.png)
+
+Once you’re satisfied with your selections, click “NEXT”
+
+We have now arrived at the “GROUP” tab. In this case, we will mark the radio button to “USE EXISTING” groups if you wish to use the group we configured earlier.
+
+![The group tab of the create cloud dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-21078778-ABE2-4EC9-A236-0F982B727DDB-high.png)
+
+Once you’ve selected the group, click “NEXT”
+
+On the final tab of the “CREATE CLOUD” wizard, you’ll confirm your selections and click “COMPLETE”. The new cloud is now listed on the cloud detail page. After a short time, HPE Morpheus Enterprise will provide summary information and statistics on existing virtual machines, networks, and other resources available in the cloud.
+
+## Viewing Cloud Inventory
+
+Now that we’ve integrated our first VMware cloud, we can stop for a moment to review what HPE Morpheus Enterprise gives us from the cloud detail page. We can see that HPE Morpheus Enterprise gives us estimated costs and cost histories, metrics on used resources, and also lists out resource counts in various categories including container hosts, hypervisors, and virtual machines. We can drill into these categories to see lists of resources in the various categories individual resources within them by clicking on the category tabs. We can link to the detail page for any specific resource by clicking on it from its resource category list.
+
+## Configuring Resource Pools
+
+With our VMware cloud configured, HPE Morpheus Enterprise will automatically sync in available resource pools and data stores.
+
+For resource pools, once HPE Morpheus Enterprise has had time to ingest them, then will be visible from the cloud detail page. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  RESOURCES tab. In here, we are able to see and control access to the various resource pools that have been configured in vCenter. For example, we can restrict access to a specific resource pool within HPE Morpheus Enterprise completely by clicking on the “ACTIONS” button, then clicking “Edit”. If we unmark the “ACTIVE” button and then click “SAVE CHANGES” we will see that the resource pool is now grayed out in the list. The resources contained in that pool will not be accessible for provisioning within HPE Morpheus Enterprise.
+
+![The list of synced resource pools in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5E044CF2-DC63-48CA-BFE5-FB99E8B3CA6B-high.png)
+
+Often our clients will want to make specific blocks of resources available to their own customers. This can be easily and conveniently controlled through the same “EDIT RESOURCE POOL” dialog box we were just working in. If we expand the “Group Access” drawer, we are able to give or remove access to each pool to any group we’d like. We can also choose to make some or all of our resource pools available to every group. Specific resource pools can also be defined as the default for each group if needed.
+
+![The edit resource pools dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12509E33-3DEA-47DD-8838-3D4B76599043-high.png)
+
+Additionally, we may choose to allow only certain service plans to be provisioned into a specific pool of resources. For example, perhaps a specific cluster is my SQL cluster and only specific services plans should be consumable within it. We can control that through this same dialog box.
+
+## Configuring Data Stores
+
+To take a look at data stores, we’ll move from the “RESOURCES” tab to the “DATA STORES” tab on our cloud detail page.
+
+HPE Morpheus Enterprise gives the user similar control with data stores to what we saw with our resources pools earlier. Just like with resource pools, we can disable access within HPE Morpheus Enterprise completely by clicking on “ACTIONS” and then “Edit”. If we unmark the “ACTIVE” checkbox and click “SAVE CHANGES”, you will see that specific data store has been grayed out.
+
+![The list of synced data stored in |morpheus|](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9D16EAEE-4391-4B7B-B0FA-D46DB90A3E59-high.png)
+
+Just like with resource pools, we are also able to scope data stores to specific groups. This ensures that the members of each group are only able to consume the data stores they should have access to.
+
+![The edit data stores dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-14F14768-224B-4188-A052-48C37F755907-high.png)
+
+## Configuring Folders
+
+Still within the “RESOURCES” tab, within the “FOLDERS” subtab we see the folders discovered from the vCenter Cloud. Edit folder configurations by selecting “ACTIONS” from the end of the row, then clicking “Edit”. Consider the following configurations for specific folders:
+
+- **DEFAULT:** If selected, this folder will be pre-selected when provisioning new Instances to this Cloud (See the Folder option on the CONFIGURE tab of the Instance provisioning wizard)
+- **IMAGE TARGET:** HPE Morpheus Enterprise will look in the image target folder(s) to onboard VMware images
+
+After saving the changes, you’ll see any folders set as default or image target indicated in the folders list.
+
+## Configuring Network for Provisioning
+
+When configuring networking, we can set global defaults by going to Infrastructure  >  Network  >  NETWORKS tab. Here we can add or configure networks from all clouds integrated into HPE Morpheus Enterprise. Depending on the number of clouds HPE Morpheus Enterprise has ingested, this list may be quite large and may also be paginated across a large number of pages. In such a case, it may be easier to view or configure networks from the specific cloud detail page so that networks from other clouds are not shown.
+
+![The list of configured neworks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2168C77C-8C1C-4580-B2A2-785BFF097D39-high.png)
+
+Still in Infrastructure  >  Network, make note of the “INTEGRATIONS” tab. It’s here that we can set up any integrations that may be relevant, such as IPAM integrations. Generally speaking, when adding IPAM integrations, we simply need to name our new integration, give the API URL, and provide credentials. There’s more information in the [IPAM integration](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#networking) section of HPE Morpheus Enterprise Docs.
+
+![The add IPAM integration dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-66A48C34-D132-42F8-BABB-C12A096F8910-high.png)
+
+In Infrastructure  >  Networking we can also set up IP address pools from the IP Pools tab. These pools can be manually defined, known as a HPE Morpheus Enterprise-type IP pool, or they can come from any IPAM integrations you’ve configured. As instances are provisioned, HPE Morpheus Enterprise will assign IP addresses from the pool chosen during provisioning. When the instance is later dissolved, HPE Morpheus Enterprise will automatically release the IP address to be used by another instance when needed. When adding or editing a network, we can opt to scope the network to one of these configured IP address pools. Edit an existing network by clicking the pencil icon on the Networks List Page (Infrastructure > Networks > NetworksTab) and fill in the “Network Pool” field to associate the IP Pool with the network.
+
+![Creating a |morpheus|-type IP pool](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3EEAE850-7B84-4E9C-8699-3319344FCFA6-high.png)
+
+Since this guide is focused on working within a VMware cloud that we integrated at the start, we will take a look at our network configurations on the cloud detail page as well. Navigate to Infrastructure  >  Clouds  >  (your VMware cloud)  >  NETWORKS tab. Just as with resource pools and data stores, we have the ability to make certain networks inactive in HPE Morpheus Enterprise, or scope them to be usable only for certain groups or tenants.
+
+![Viewing networks on the cloud detail page](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D8873C52-F566-49ED-AE8C-825EA4B169B1-high.png)
+
+## Prepping an Image
+
+As we’ll discuss and try out in the next section, HPE Morpheus Enterprise comes out of the box with a default set of blueprints that are relevant to many modern deployment scenarios. For the most part, these are base operating system images with a few additional adjustments. However, in many on-premise deployments, there are often custom image and networking requirements. We will work with images included in HPE Morpheus Enterprise by default in this guide but it’s important to discuss how to prep custom images as well.
+
+### Creating a Windows Image
+
+The following versions of Windows Server are supported:
+
+- 2008 R2
+- 2012
+- 2012 R2
+- 2016
+- 2019
+- 2022
+
+To start, create a new Windows VM in vCenter using a base version of your selected Windows build.
+
+NOTE
+
+It’s recommended to make the VMDK drive as small as possible for your purposes as this generally speeds cloning and deploy times. Morpheus provisioning and post-deploy scripts allow to to expand the drive to any size that you need.
+
+Once the VM is created, ensure VMware Tools is installed on the operating system. This will ensure the virtual machine can communicate correctly with vCenter but also if the cloud was configured to use `RPC MODE` of `Vmware Tools`, and the HPE Morpheus Enterprise agent is not installed, HPE Morpheus Enterprise can communicate with the virtual machine directly for tasks and other processes.
+
+NOTE
+
+If the cloud was configured to use `RPC MODE` of `SSH/WinRM`, it will be necessary to configure WinRM on the virtual machine. Ensure WinRM is allowed from your Morpheus appliance through the local Windows firewall. Also, run the following command to enable WinRM in the guest: `winrm quickconfig`
+
+Next, install .NET 4.5.2 or higher as a [requirement](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/agentInstallation.html#agent-install-requirements) for the Morpheus agent.
+
+Finally, choose a method that will be used to customize the operating system:
+
+- Guest Customization
+- Sysprep
+- Cloudbase-Init
+
+#### Using Guest Customization (Recommended)
+
+HPE Morpheus Enterprise can utilize the vCenter guest customizations feature, creating its own customization specification and applying it at deployment. There are no other changes needed in the guest operating system when using this method. Turn off the virtual machine and convert it to a template Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **VMware Guest Customization?** is checked.
+
+#### Using Windows Sysprep
+
+HPE Morpheus Enterprise can inject an unattend file via CD-ROM to override the default sysprep process when preparing a virtual machine. Run the following command from the guest operating system to sysprep the operating system: `C:\Windows\System32\sysprep /oobe /generalize /shutdown` The unattend file created on the virtual machine can be ignored, no changes will be needed. Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Sysprepped/Generalized Image?** is checked.
+
+NOTE
+
+If **VMware Guest Customization?** is enabled on the virtual image or if using static IP addresses or IP pools when provisioning, ensure a Sysprep has not been performed in the guest. In such cases, a guest customization will always be performed.
+
+#### Using Cloudbase-init
+
+IMPORTANT
+
+Some admins may struggle with using Cloudbase-Init, especially if they are not familiar with cloud-init (used in Linux). It is recommended to use either **Guest Customization** or **Windows Sysprep** if the admins are more famililar with those tools.
+
+HPE Morpheus Enterprise can inject a cloud-init file via CD-ROM to override the default sysprep process when preparing a virtual machine, if the Cloudbase-Init service is installed. Download Cloudbase-Init from <https://cloudbase.it> for your appropriate architecture. Run the installer and keep the default settings. Below is an example of the final settings page: ![Cloudbase-Init settings](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ABBCBC9E-8CE1-4EE2-B15D-EC25F255D11A-high.png) At the end of the installer, options will be available to sysprep and shutdown the virtual machine. Checkmark both boxes and click **Finish**: ![Cloudbase-Init sysprep](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-14880EC6-E2C4-486D-AEA8-D66AE8573877-high.png) Once started, the sysprep process should continue until the virtual machine shutsdown. ![Cloudbase-Init progress](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A52DA0FA-2608-4AE6-B741-DC4B98D23778-high.png) Once the virtual machine has completed shutting down, convert it to a template. Refresh your cloud (Infrastructure > Clouds > Click Cloud > Refresh > Short). Once the Virtual Image has been synced into Library > Virtual Images, edit it and ensure **Is Cloud Init Enabled?** is checked.
+
+### Creating a CentOS/RHEL Image
+
+Create a new machine in vCenter and install a base version of your preferred Linux distro.
+
+NOTE
+
+If you are using cloud-init as part of your image, you will need to ensure your virtual machine has a cdrom.
+
+Before installing the operating system, set up a single ext or xfs partition without a swap disk. Next, install the distro applying any updates to the operating system or security updates. Once the operating system is running and updated, install the following:
+
+```
+```
+yum install cloud-init  
+yum install cloud-utils-growpart  
+yum install open-vm-tools  
+yum install git  
+yum install epel-release
+```
+```
+
+Set selinux to permissive as the enforced setting can cause problems with cloud-init:
+
+```
+```
+sudo vi /etc/selinux/config
+```
+```
+
+#### Cloud-Init
+
+We’ll get started by installing cloud-init using the following command:
+
+```
+```
+yum -y install epel-release  
+yum -y install git wget ntp curl cloud-init dracut-modules-growroot  
+rpm -qa kernel | sed 's/^kernel-//'  | xargs -I {} dracut -f /boot/initramfs-{}.img {}
+```
+```
+
+NOTE
+
+The above command will install some core dependencies for cloud-init and automation later as you work with your provisioned instances. For example, we install Git here as it is used for Ansible automation. If you had no plans to use Ansible, this installation could be skipped. The dracut-modules-growroot is responsible for resizing the root partition upon initial boot which was potentially adjusted during provisioning.
+
+One key benefit of using cloud-init is that we don’t have to lock credentials into the blueprint. We recommend configuring a default cloud-init user that will get created automatically when the VM is booted by cloud-init. We can define that default user in Administration > Settings > Provisioning > Cloud-Init
+
+#### Network Interfaces
+
+As of CentOS 7, network interface naming conventions have changed. You can check this by running ifconfig and noting that the primary network interface has some value similar to “ens2344”. The naming is dynamic and typically set based on hardware ID. We don’t want this to fluctuate when provisioning this blueprint in our VMware environments. To accomplish this end, we will rename the interface back to “eth0” using the steps below.
+
+First, adjust the bootloader to disable interface naming:
+
+```
+```
+sed -i -e 's/quiet/quiet net.ifnames=0 biosdevname=0/' /etc/default/grub  
+grub2-mkconfig -o /boot/grub2/grub.cfg
+```
+```
+
+The next step is to adjust network scripts in CentOS. Start by confiming the presence of a file called /etc/sysconfig/network-scripts/ifcfg-eth0. Once confirmed, run the following script:
+
+```
+```
+export iface_file=$(basename "$(find /etc/sysconfig/network-scripts/ -name 'ifcfg*' -not -name 'ifcfg-lo' | head -n 1)")  
+export iface_name=${iface_file:6}  
+echo $iface_file  
+echo $iface_name  
+sudo mv /etc/sysconfig/network-scripts/$iface_file /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo sed -i -e "s/$iface_name/eth0/" /etc/sysconfig/network-scripts/ifcfg-eth0  
+sudo bash -c 'echo NM_CONTROLLED=\"no\" >> /etc/sysconfig/network-scripts/ifcfg-eth0'
+```
+```
+
+This script tries to confirm there is a new ifcfg-eth0 config created to replace the old config file. Confirm this config exists after running and if not you will have to build your own:
+
+```
+```
+TYPE=Ethernet  
+DEVICE=eth0  
+NAME=eth0  
+ONBOOT=yes  
+NM_CONTROLLED="no"  
+BOOTPROTO="dhcp"  
+DEFROUTE=yes
+```
+```
+
+For more on CentOS/RHEL image prep, including additional configurations for specific scenarios, take a look at the [VMware image prep](https://docs.morpheusdata.com/en/4.1.1/integration_guides/Clouds/vmware/vmware_templates.html#gotchas) page in HPE Morpheus Enterprise Docs.
+
+#### Creating an Ubuntu 20.04 Image
+
+Download the Ubuntu 20.04 ISO from Canonical, and upload the base image to vCetner. Then, create a new virtual machine in vCenter.
+
+NOTE
+
+Since we’ll include cloud-init with our image, we will need to ensure the virtual machine has a cdrom. Select the Ubuntu 20.04 ISO we just downloaded from the CD/DVD drive dropdown menu when creating the new virtual machine.
+
+Before installing the operating system, set up a single ext partition without a swap disk. Then, continue on installing Ubuntu making the following selections during the setup process:
+
+- Update to the latest installer if a later version is available
+- Use the entire disk and deselect the option to set up the disk as an LVM group
+- Configure an account and set a password
+- Opt to install OpenSSH Server
+- Other optional packages aren’t needed for this basic Ubuntu image
+
+Complete the installation process and reboot the machine. Update the package list and apply any upgrades:
+
+```
+```
+apt-get update  
+apt-get upgrade
+```
+```
+
+Disable assignment of new styled names for network interfaces (instead of `ens###` they will be `eth#`):
+
+```
+```
+sudo sed -i -e 's/GRUB_CMDLINE_LINUX=""/GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0"/' /etc/default/grub
+```
+```
+
+Update GRUB:
+
+```
+```
+update-grub
+```
+```
+
+Update the `70-persistent-net.rules` file:
+
+```
+```
+cat << EOF > /etc/udev/rules.d/70-persistent-net.rules  
+SUBSYSTEM=="net", ACTION=="add", DRIVERS=="?*", ATTR{dev_id}=="0x0", ATTR{type}=="1", NAME="eth0"  
+EOF
+```
+```
+
+Remove `subiquity-disable-cloudinit-networking.cfg` as cloud-init will skip network configuration if it’s present:
+
+```
+```
+rm -f /etc/cloud/cloud.cfg.d/subiquity-disable-cloudinit-networking.cfg
+```
+```
+
+Update `99-pve.cfg`:
+
+```
+```
+cat << EOF > /etc/cloud/cloud.cfg.d/99-pve.cfg  
+datasource_list: [ConfigDrive, NoCloud]  
+EOF
+```
+```
+
+Remove Netplan files, they will not be regenerated if they exist:
+
+```
+```
+rm -f /etc/netplan/00-installer-config.yaml  
+rm -f /etc/netplan/50-cloud-init.yaml
+```
+```
+
+Run cloud-init clean:
+
+```
+```
+cloud-init clean
+```
+```
+
+Next, reboot the system and confirm the network interface is labeled `eth0` once the machine comes back up. Then, clear BASH history for root. The history entry has a copy in the memory and it will flush back to the file when you log out. You can avoid this with the following command:
+
+```
+```
+cat /dev/null > ~/.bash_history && history -c && exit
+```
+```
+
+Shutdown the system:
+
+```
+```
+shutdown -h now
+```
+```
+
+Convert the VM to a template in vCenter before moving back to HPE Morpheus Enterprise to onboard the image and use it to begin building your provisioning library.
+
+## Provisioning Your First Instance
+
+At this point, we are ready to provision our first image. As a first instance, we’ll provision an Apache web server to our vCenter cloud.
+
+Navigate to Provisioning > Instances. If any instances are currently provisioned, we will see them listed here. To start a new instance we click the “+ADD” button to pop the “CREATE INSTANCE” wizard. We’ll scroll down to and select the Apache instance type and click “NEXT”.
+
+![Selecting an instance type to provision](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F2E15736-7064-4FD4-8159-E1C54CD3743E-high.png)
+
+First, we’ll specify the group to provision into which determines the clouds available. If you’ve followed this guide to this point, you should at least have a group that houses all of your clouds which you can select here. This will allow us to select the vCenter cloud from the “CLOUD” dropdown menu. Provide a unique name to this instance and then click “NEXT”
+
+From the “CONFIGURE” tab, we’re presented with a number of options. The options are cloud and layout-specific, more generalized information on creating instances and available options is [here](https://docs.morpheusdata.com/en/4.1.1/getting_started/agent/morpheus_agent.html#morpheus-agent). For our purposes, we’ll select the following options:
+
+- **LAYOUT**: Includes options such as the base OS, custom layouts will also be here when available
+- **PLAN**: Select the resource plan for your instance. Some plans have minimum resource limits, HPE Morpheus Enterprise will only show plans at or above these limits. User-defined plans can also be created in Administration > Plans & Pricing.
+- **VOLUMES and DATASTORES**: The minimum disk space is set by the plan, this value may be locked if you’ve selected a custom plan that defines the volume size
+- **NETWORKS**: Select a network, note that IP pools must be linked with the networks defined in VMware in order to assign static IP addresses
+
+Under the “User Config” drawer, mark the box to “CREATE YOUR USER”. Click “NEXT”.
+
+![The configure tab of the create instance dialog box](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B494FF9C-4564-4F58-B523-3D6661254037-high.png)
+
+NOTE
+
+“CREATE YOUR USER” will seed a user account into the VM with credentials set in your Morpheus user account settings. If you’ve not yet defined these credentials, you can do so by clicking on your username in the upper-right corner of the application window and selecting “USER SETTINGS”.
+
+For now, we’ll simply click “NEXT” to move through the “AUTOMATION” tab but feel free to stop and take a look at the available selections here. There is more information later in this guide on automation and even more beyond that in the rest of HPE Morpheus Enterprise docs.
+
+Review the settings for your first instance and click “COMPLETE”.
+
+![Confirming the instance to be provisioned](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BD9754FE-0F3F-45CD-BE37-86185EF667BF-high.png)
+
+We are now dropped back onto the instances list page. We can see a new entry in the list at this point with a status indicator that the new machine is being launched (rocket icon in the status field). We can double click on the instance in the list to move to the instance detail page. For now we will see a progress bar indicating that the instance is being created and is starting up. The exact amount of time this process will take depends on your environment and selections made when provisioning the instance. Initially, HPE Morpheus Enterprise will guess as to how long this will take and the progress bar may not be accurate. Over time, HPE Morpheus Enterprise will learn how long these processes take and progress bar accuracy will improve. For more detailed information on the status of various provisiioning processes, we can scroll down and select the “HISTORY” tab. The “STATUS” icon will change from the blue rocket to a green play button when the instance is fully ready. Furthermore, we can click on the hyperlinked IP address in the “VMS” section of this page to view a default page in a web browser to confirm success.
+
+![Monitoring privisioning progress on the instance detail page](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6CD6B5F1-88DE-44D1-9E25-29FB61D81345-high.png)
+
+## Creating Your First Library Item
+
+In the prior section, we manually provisioned our first instance. However, HPE Morpheus Enterprise allows you to build a catalog of custom provisionable items to simplify and speed provisioning in the future. In this section, we’ll build a catalog item and show how that can translate into quick instance provisioning after configuration.
+
+NOTE
+
+Before starting this process, it’s important to decide which virtual image you plan to use. If you’re not using a Morpheus-provided image, you’ll want to ensure it’s uploaded. You will not be able to complete this section without selecting an available image. In this example we will use Morpheus Redis 3.0 on Ubuntu 14.04.3 v2.
+
+Navigate to Library > Blueprints > Node Types and click “+ADD”.
+
+![Adding a new node type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5563E0E9-B224-4125-AE22-DE55AB2EC41C-high.png)
+
+In this example, I am going to set the following options in the “NEW NODE TYPE” wizard:
+
+- **NAME**
+- **SHORT NAME**
+- **VERSION**: 1 (In this particular case, the version is not important)
+- **TECHNOLOGY**: VMware
+- **VM IMAGE**: HPE Morpheus Enterprise Redis 3.0 on Ubuntu 14.04.3 v2
+
+NOTE
+
+Within the “VMware VM Options” section you should add anything that will always be used for this node, regardless of the specific deployment details. This can include LDAP Authentication, bash scripts that should run on installation, among other things.
+
+![Configuring options for the new node](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0C9573F1-448E-41A1-B2CD-B8F3D6111B7B-high.png)
+
+With the new node created, we’ll now add a new instance type which will be accessable from the provisioning wizard once created. Move from the “NODE TYPES” tab to the “INSTANCE TYPES” tab and click “+ADD”.
+
+![Adding a new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4E4E2CEE-81C1-44B4-9155-A7363D1DC596-high.png)
+
+In the “NEW INSTANCE TYPE” wizard, I’ll simply enter a **NAME** and **CODE** value. Click “SAVE CHANGES”.
+
+![Configuring the new instance type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C286C622-86B7-4107-9028-9DA0D8E4B3E7-high.png)
+
+Now that we’ve created a new instance type, access it by clicking on the name in the list of custom instances you’ve created. In my case, I’ve given the name “NewInstanceType”.
+
+![Opening our newly created instance type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D0E0A6CF-A7B3-43C9-A83F-0628B90D2CFA-high.png)
+
+Once we’ve opened the new instance type, by default, we should be on the “LAYOUTS” tab. Click “+ADD LAYOUT”.
+
+I’ve set the following fields on my example layout:
+
+- **NAME**
+- **VERSION**: This is the version number of the layout itself, which is labeled 1.0 in the example
+- **TECHNOLOGY**: VMware
+- **Nodes**: Select the node we created earlier, if desired you can specify multiple nodes
+
+Click “SAVE CHANGES”.
+
+![Configuring the new layout](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-70C1E76A-8246-418B-956B-D8542254955E-high.png)
+
+At this point we’ve completed the setup work and can now provision the instance we’ve created to our specifications. Navigate to Provisioning > Instances and click “+ADD”. From the search bar we can search for the new instance type we’ve created. In the example case, we called it “newinstancetype”. Click “NEXT”.
+
+![Searching for our custom instance type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-905B43B4-EABB-4271-A555-97203C7A87E5-high.png)
+
+As before, we can select a group and cloud to provision this new instance. Click “NEXT”. On the “CONFIGURE” tab, make note that the layout and plan are already selected because they were configured as part of creating the new instance type. Select a network and click “NEXT”. Once again we will also click “NEXT” through the “AUTOMATION” tab. Finally, click “COMPLETE”.
+
+![Configuring the newlt created instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8D733786-5795-4A40-A81F-F832B79E3B71-high.png)
+
+As before when we manually provisioned an instance, HPE Morpheus Enterprise will now begin to spin up the new VM. How long this will take depends on your environment but HPE Morpheus Enterprise will predict how long this process will take and represent that on a progress bar. Over time, HPE Morpheus Enterprise begins to learn how long these processes take and becomes more accurate in predicting spin-up time.
+
+Once the privisioning process has completed, open the instance detail page in HPE Morpheus Enterprise and click on the “CONSOLE” tab. You’ll be logged in with your user account and are then able to confirm the machine is ready and available.
+
+![Confirming creation of the new instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C9C8D9D2-E462-48F1-B679-A96B28ABAED3-high.png)
+
+## Automation and Configuration Management
+
+HPE Morpheus Enterprise automation is composed of Tasks and Workflows. A task could be a script added directly, scripts or blueprints pulled from the HPE Morpheus Enterprise Library, playbooks, recipes, or a number of other things. The complete list of task types can be found in the [Automation section](https://docs.morpheusdata.com/en/4.1.1/provisioning/automation/automation.html#automation) of HPE Morpheus Enterprise docs. Tasks can be executed individually but they are often combined into workflows. We can opt to run a workflow at provision time or they can be executed on existing instances through the Actions menu.
+
+In this guide we will set up an Ansible integration, create a task, add the task to a workflow, and run the workflow against a new and existing instance. If you’ve worked through this guide to this point, you should already have an Apache instance running. If you don’t yet have that, provision one before continuing with this guide and ensure it’s reachable on port 80.
+
+![Adding a new automation integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-61F3E05A-5E94-4F8B-98D4-007FE5904D98-high.png)
+
+We’ll first set up the Ansible integration, you can integrate with the sample repository referenced here or integrate with your own. Go to ‘Administration > Integrations’. Click “+NEW INTEGRATION” and select Ansible from the dropdown menu. Fill in the following details:
+
+- **NAME**
+- **ANSIBLE GIT URL**: <https://github.com/ncelebic/morpheus-ansible-example>, or enter the URL for your own Ansible git repository
+- **PLAYBOOKS PATH**
+- **ROLES PATH**
+- Mark the box to “USE MORPHEUS AGENT COMMAND BUS”
+
+NOTE
+
+If your git repository requires authentication, you should create a keypair and use the following URL format: [git@github.com](mailto:git%40github.com):ncelebic/morpheus-ansible-example.git.
+
+![Configuring the new Ansible integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4933CF3E-3D5C-4B27-9234-2655E56B605A-high.png)
+
+Click “SAVE CHANGES”. You’ll now see our new Ansible integration listed among any other configured inetegrations. If we click on this new integration to view detail, a green checkmark icon indicates the git repository has been fully synced.
+
+With the Ansible integration set up, we can now create a task that includes our playbook. Go to Library > Automation, click “+ADD”. We’ll first set our “TYPE” value to Ansible Playbook so that the correct set of fields appear in the “NEW TASK” wizard. Set the following options:
+
+- **NAME**
+- **ANSIBLE REPO**: Here we will choose the Ansible integration that we just created
+- **PLAYBOOK**: In our example case, enter ‘playbook.yml’
+
+![Configuring the new task](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12619017-B1FF-4E72-993B-ACA2AC62AAA5-high.png)
+
+Click “SAVE CHANGES” to save our new task. We can test the new task on our Apache VM now by going to Provisioning > Instances and clicking into our VM. From the “ACTIONS” menu select “Run Task”. From the “TASK” dropdown menu, select the task we just added and click “EXECUTE”.
+
+![Executing the new task](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-03265833-F302-4A3E-AA48-30CDEE45722F-high.png)
+
+To see the progress of the task, click on the “HISTORY” tab and click on the (i) button to the right of each entry in the list. In this case, we can also see the results of the task by clicking on the link in the “LOCATION” column of the “VMS” section.
+
+Now that our task is created, we can put it into a workflow. Back in Library > Automationwe will click on the “WORKFLOWS” tab. Click “+ADD” and select Provisioning Workflow. We’ll give the new workflow a name and expand the Post Provision section. As we begin to type in the name of the task we’ve created, it should appear as a selection. Click “SAVE CHANGES”.
+
+![Creating a workflow for our task](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-87FADF2B-1826-45B2-BCD1-BD11A31CB587-high.png)
+
+Now that we have a workflow, return to Provisioning > Instances and begin to provision another Apache instance. More detailed instructions on provisioning a new Apache instance are included earlier in this guide if needed. Now, when you reach the “AUTOMATION” section of the “CREATE INSTANCE” wizard, we have a workflow to select. From the “WORKFLOW” dropdown menu, select the workflow we just created and complete provisioning of the new instance.
+
+![Running the new workflow on provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DEF38048-CF8C-45CE-9EA7-432F6E4DCD55-high.png)
+
+As the instance is provisioning, we can go to the “HISTORY” tab and see HPE Morpheus Enterprise executing the tasks that were contained in our workflow.
+
+This is just one example of using HPE Morpheus Enterprise to automate the process of configuring and instance to your needs. There are a number of other automation types that can be built into your workflows as well. For further information, take a look at the [automation integrations](https://docs.morpheusdata.com/en/4.1.1/integration_guides/integration_guides.html#automation) guide in HPE Morpheus Enterprise docs.
+
+## Conclusion
+
+At this point you should be up and running in HPE Morpheus Enterprise, ready to consume VMware. This guide only scratches the surface, there is a lot more to see and do in HPE Morpheus Enterprise. Take a look at the rest of [Morpheus Docs](https://docs.morpheusdata.com/en/4.1.1/index.html) for more information on supported integrations and other things possible.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json b/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
new file mode 100644
index 0000000..db97358
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+  "title": "Blueprint Development Overview",
+  "ordinal": 127,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.html",
+  "topic_cluster": {
+    "clustering_title": "Blueprint Development Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704",
+        "clustering_title": "Blueprint Development Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md b/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
new file mode 100644
index 0000000..67ac545
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C216CC1D-C5ED-4FE8-BCC0-3E3E9870A704.md
@@ -0,0 +1,5 @@
+# Blueprint Development Overview
+
+When provisioning, the User selects an INSTANCE TYPE from the provisioning wizard. At this stage, we can present custom INPUTS to the User which alter deployment in ways the administrator predetermines. Based on the selected Cloud technology and Version, the User is presented with applicable LAYOUTS selections. LAYOUTS can take advantage of Workflows which automate Tasks and can utilize a wide range of DevOps automation technologies. One or more NODE TYPES is associated with the LAYOUT. NODE TYPES are the bridge between LAYOUTS and Images. NODE TYPES can also take advantage of File Templates for custom configuration and Scripts which can be queued to run at any stage of the Instance lifecycle.
+
+![../../_images/library_item_transparent.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-935505B8-57F2-4C03-A95C-CF46F2AFF987-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json b/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
new file mode 100644
index 0000000..a3833c3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+  "title": "Labels",
+  "ordinal": 102,
+  "parent_title": "Library",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.html",
+  "topic_cluster": {
+    "clustering_title": "Labels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB",
+        "clustering_title": "Labels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md b/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
new file mode 100644
index 0000000..edf251b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C279B4B2-41AC-4F47-9D11-6142FA3E70DB.md
@@ -0,0 +1,45 @@
+# Labels
+
+Labels Video Demo
+
+Labels are a categorization feature designed to allow easier filtering of list views in the HPE Morpheus Enterprise Library. The following library constructs can be labeled:
+
+- Clouds
+- Groups
+- Tasks
+- Workflows
+- Jobs
+- Instance Types
+- Instances
+- Layouts
+- Node Types
+- Servers
+- Virtual Images
+- Inputs
+- Option Lists
+
+Labels are visible from the list views of any constructs listed above. By default, labels are turned on in the list view but if they aren’t showing, click the gear icon (⚙) and then click Labels to enable them.
+
+The list view contains a row of filters above the list, one of which is Labels. Enter a search string to find an existing label or click the dropdown button within the field to select an existing label. This will filter the list to show only constructs which have the selected label.
+
+NOTE
+
+Any list may be filtered by any label which exists anywhere in the current Tenant. When a label is removed from a construct and no other constructs also have that label, HPE Morpheus Enterprise will remove the label from the list during its nightly sync. It is normal for a label to continue to exist in this list, even if it’s not currently applied to any constructs, until the next nightly sync has taken place.
+
+![../_images/labels.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EF84CC50-D2E4-4906-9051-655D7B15CE65-high.png)
+
+## Adding and Removing Labels
+
+Labels can be created when adding or edited any of the supported constructs listed above. When adding or editing the object, enter or edit the comma-separated list of labels you wish to apply.
+
+![../_images/labeladd.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B0C645F7-A738-4975-9AA9-9F5E0C581874-high.png)
+
+## Running Automation Against Label Targets
+
+The HPE Morpheus Enterprise automation constructs Jobs, Tasks, and Workflows can be run against Instance Labels or Server Labels. When creating the Job or executing the Task or Workflow, select either Server Label or Instance Label. After specifying the Label, the automation will be run against all Instances or Servers which have the indicated Label. Currently, only one Label may be selected and users cannot enter multiple Labels in the field. If a non-existent Label is entered, the automation simply will not run against any Workloads since the Label does not match any.
+
+NOTE
+
+Instance and server Labels are separate. Even if some Instances or servers have the same Label, the automation is only run against the selected construct (Instance Labels or Server Labels).
+
+![../_images/executeLabel.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FC1AD46A-80E3-46F9-95D0-3D679C53E596-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json b/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
new file mode 100644
index 0000000..add0224
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+  "title": "Remote Console",
+  "ordinal": 355,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.html",
+  "topic_cluster": {
+    "clustering_title": "Remote Console",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE",
+        "clustering_title": "Remote Console"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md b/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
new file mode 100644
index 0000000..6e1dce8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C2C11C41-6395-4A3F-B1B2-BCEEAA3D9DEE.md
@@ -0,0 +1,204 @@
+# Remote Console
+
+HPE Morpheus Enterprise has a built in Remote Console for Instances, Hosts, Virtual Machines and Bare Metal. The following information reviews the Roles Settings, Protocols, and Requirements necessary to configure and troubleshoot Remote Console access.
+
+## Role Settings
+
+User Role settings determine if the Console tab or `Open Console` Action appear for a user, and if a login prompt is presented or the user is automatically logged in when using the Console.
+
+- Remote Console (None, Provisioned, Full)
+  :   None
+      :   The user will not have access to remote console.
+
+      Provisioned
+      :   The user will only have remote console access for Instances they provisioned.
+
+      Full
+      :   The user will have remote console access for all instances they have access to.
+- Remote Console: Auto Login (No, Yes)
+  :   No
+      :   A login prompt will be present in the console for Linux platforms, and the main login screen will present for Windows platforms.
+
+      Yes
+      :   HPE Morpheus Enterprise will automatically login to the remote console using the credentials defined on the VM or Host. For provisioned Instances, the credentials are defined either from the credentials defined on the Virtual Image used, added via cloud-init or VMware Tools using the global cloud-init settings (Administration - Provisioning) or the Linux or Windows settings defined in User Settings. For Instances created when converting a VM or Host to managed, the credentials are entered when converting to managed. These credentials can be changed by editing the underlying VM or Host of the Instance.
+
+NOTE
+
+If the credentials defined on the VM or Host are not valid, and the `Remote Console: Auto Login` Role setting is set to `Yes`, the console will not be able to connect and no console window or login prompt will be presented. The credentials on the underlying VM or Host must be edited or `Remote Console: Auto Login` Role setting can be set to `No` for a login prompt to present in the console. Credentials cannot be changed from an Instance view, only in the Infrastructure VM or Host view.
+
+## Protocols
+
+Platform Type and Cloud Settings determines the protocol and port used for Remote Console connections.
+
+- SSH
+  :   The SSH protocol will be used for Linux and OSX platform types, and 22 is the default port used.
+- RDP
+  :   The RDP (Remote Desktop) protocol will be used for Windows platform types over port 3389 by default.
+- VNC
+  :   The VNC protocol will be used for all platform types in Clouds with the `Hypervisor Console` option enabled in cloud settings. VNC connection are made directly to the Hypervisor Host over port 443.
+
+NOTE
+
+Alternative ports can be configured per VM or Host by editing the VM or Host and editing the Port field in the RPC host section.
+
+### SSH
+
+For all Linux and OSX platform types, HPE Morpheus Enterprise will use the SSH protocol via port 22 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will SSH using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for SSH Connectivity
+
+- SSH Enabled on the target VM or Host
+- Port 22 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+### RDP
+
+For all Windows platform types, HPE Morpheus Enterprise will use the RDP protocol via port 3389 by default for Remote Console connections, unless the Hypervisor Console` option is enabled for VMware type clouds.
+
+HPE Morpheus Enterprise will RDP using the username, password, RPC Host IP address and Port defined in the VM or Host record.
+
+Default Requirements for RDP Connectivity
+
+- Remote Access enabled on the target VM or Host and Remote Desktop enabled in the Windows Firewall settings. If the VM or Host is on a different network than the HPE Morpheus Enterprise appliance, public access for Remote Desktop must be enabled in the Firewall settings.
+- Port 3389 incoming open on the target VM or Host firewalls and security groups from the HPE Morpheus Enterprise Appliance (not from the users IP address)
+- An IP address defined on the VM or Host record that is routable from the HPE Morpheus Enterprise Appliance.
+- Valid credentials defined on the VM or Host record in the RPC host field.
+- Remote Console Role Permissions set to Provisioned or Full if the User provisioned the instance, or Full if the user did not provision the instance.
+
+NOTE
+
+If Remote Console: Auto Login is set to No in a users Role permissions, Allow connections only from computers running Remote Desktop with Network Level Authentication in the Windows System Properties  >  Remote settings must be DISABLED for Remote Console to connect.
+
+### VNC (VMware Hypervisor Console)
+
+When the `Hypervisor Console` option is enabled in cloud settings, the VNC protocol will be used for all platform types that Cloud.
+
+When using VNC Hypervisor Console, the HPE Morpheus Enterprise Appliance connects directly to the host the VM is on, not directly to the VM.
+
+HPE Morpheus Enterprise features Remote Console support directly to hypervisors. To enable this feature a few prerequisites must be met:
+
+- The HPE Morpheus Enterprise Appliance must have network access to the host the VM is on over 443.
+- The HPE Morpheus Enterprise Appliance must be able to resolve the hypervisor hostnames.
+
+NOTE
+
+VNC connections for VMs and Hosts in VMware type clouds are made directly to the ESXi hosts, not vCenter.
+
+Unlike SSH and RDP, valid credentials do not need to be set on the VM or Host records in HPE Morpheus Enterprise for VNC hypervisor console connections. An IP address is also not required on the VM or Host for VNC hypervisor console connections. HPE Morpheus Enterprise will be able to connect to the VM or Host as soon as the `Host (Hypervisor)` record is set, which can be viewed in the Info section on the VM or Host detail page.
+
+NOTE
+
+- Auto-login is not supported for Hypervisor Console. Auto-login role settings do not apply to console connecting when using Hypervisor Console. Please note Hypervisor Console sessions persist on the ESXi host and once a user manually logs in to the VM they will continue to be logged in, even if the console tab/window in HPE Morpheus Enterprise is closed, until they manually log out.
+- Copy and Paste and Text selection in Linux terminals is not supported when using VNC (VMware Hypervisor Console).
+- In HPE Morpheus Enterprise versions 3.2.0 and higher, a newer Guacamole version is installed that is not compatible with MacOS Platform Types over VNC.
+
+## Copy and Paste
+
+### About this task
+
+NOTE
+
+Copy and Paste for Text is supported for SSH and RDP protocols only. Use of this functionality requires the Role permission of “VDI: Copy/Paste” set to Full.
+
+To Copy text from the console:
+
+### Procedure
+
+1. Select text in the Console window.
+2. Click the COPY button at the top of the Console window.
+3. The selected text is copied to the users clipboard.
+
+### Results
+
+To Paste text into console:
+
+1. Copy text on the local computer to you clipboard
+2. Right click into the “Paste Text Here” field at the top of the Console window. The field will the display “Text Copied, Use Console to Paste.”
+3. Right click into the console window.
+4. The text is pasted into the VM.
+
+## Guacamole
+
+### Overview
+
+HPE Morpheus Enterprise uses Apache Guacamole, a clientless remote console. Guacamole is installed on the HPE Morpheus Enterprise Appliance during the initial reconfigure. In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+The Guacamole proxy daemon, guacd, is used for all Remote Console connections and must be running for Remote Console functionality.
+
+### Troubleshooting guacd
+
+#### About this task
+
+If all console connections are not functioning, the Guacamole proxy daemon (guacd) process may not be running or have a stuck process preventing console connections. This is evident when only the header appears in the console tab/window, and no console window appears below the header and no connection status is show in the console header. The following commands can be used on the HPE Morpheus Enterprise Appliance to restore console functionality.
+
+`morpheus-ctl status`
+:   Lists all local HPE Morpheus Enterprise services including guacd and their states. If guacd is stopped, it will need to be started again for Remote Console to function.
+
+`morpheus-ctl start guacd`
+:   Starts the guacd process
+
+`morpheus-ctl stop guacd`
+:   Stops the guacd process
+
+`morpheus-ctl kill guacd`
+:   Forcefully kills the guacd process
+
+`morpheus-ctl restarts guacd`
+:   Restarts the guacd process
+
+`morpheus-ctl tail guacd`
+:   Tails the guacd current and state logs, located by default at `/var/log/morpheus/guacd/`. This log is useful when troubleshooting console connections, guacamole service status, and to determine the protocol being used for the Remote Console connection.
+
+If guacd continues to stop even after being started, or if guacd is running and no properly configured console connections are functioning, there may be a stuck guacd or multiple guacd processes running, which will need to killed and guacd started again.
+
+To kill all guacd processes on the HPE Morpheus Enterprise Appliance and start guacd again:
+
+#### Procedure
+
+1. Kill the morpheus gaucd proccess: `morpheus-ctl kill guacd`
+2. Grep for all running guacd processes: `sudo ps -aux | grep guacd` and note the guacd pid(s) (minus the process from the grep)
+3. Kill all running guacd processes: `kill -9 pid` replacing pid with the pid(s) of the target processes
+4. Start guacd again: `morpheus-ctl start guacd`
+5. Tail the guacd logs to verify guacd is started and listening: `morpheus-ctl tail guacd` The log output will resemble below when guacd is properly running: 
+
+   ```
+   ```
+   guacd[16899]: INFO:       Guacamole proxy daemon (guacd) version 0.9.14 started  
+   guacd[16899]: INFO:       Listening on host 127.0.0.1, port 4822
+   ```
+   ```
+6. Additional information in the guacd logs appears when HPE Morpheus Enterprise is making a console connection. A successful conneciton will resemble: 
+
+   ```
+   ```
+   guacd[24725]: INFO: Creating new client for protocol "ssh"  
+   guacd[24725]: INFO: Connection ID is "$24f67856-f050-4a17-83eb-9101g0cd8869"  
+   guacd[24743]: INFO: Current locale does not use UTF-8. Some characters may not render correctly.  
+   guacd[24743]: INFO: User "@63102f19-eff4-412e-b1f9-718405f55782" joined connection "$24f67856-f050-4a17-83eb-9101g0cd8869" (1 users now present)  
+   guacd[24743]: INFO: Auth key successfully imported.  
+   guacd[24743]: INFO: SSH connection successful.
+   ```
+   ```
+
+### Guacamole Version
+
+#### About this task
+
+In HPE Morpheus Enterprise versions 3.2.0 and higher, Guacamole version 0.9.14 is automatically installed. On HPE Morpheus Enterprise versions older than 3.2.0, 0.9.9 is installed. The 0.9.14 version is required for VNC Hypervisor Console functionality on ESXi v6.5 and later.
+
+Note Guacamole version 0.9.14 is not compatible with MacOS Platform Types over VNC on ESXi v6.0 or prior (6.5 is supported). If necessary, the guacamole version can be reverted to 0.9.9.
+
+To revert the guacamole version from 0.9.14 to 0.9.9.
+
+#### Procedure
+
+1. Kill guacd - `morpheus-ctl kill guacd`
+2. Check if any guacd processes are still running `ps -aux | grep guac`
+3. If so, kill the processes `kill -9 pid` with id being the actual process id, like 16101.
+4. Go to the guac 0.9.9 directory: `cd /var/opt/morpheus/guacamole-server-0.9.9`
+5. Run: `make install`
+6. Start guacd: `morpheus-ctl start guacd`
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json b/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
new file mode 100644
index 0000000..671b8fe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+  "title": "Setting an Optional Landing URL",
+  "ordinal": 307,
+  "parent_title": "Tenant Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.html",
+  "topic_cluster": {
+    "clustering_title": "Setting an Optional Landing URL",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C3B37EC3-FBB1-40BC-95B2-770849390851",
+        "clustering_title": "Setting an Optional Landing URL"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md b/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
new file mode 100644
index 0000000..66ef113
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C3B37EC3-FBB1-40BC-95B2-770849390851.md
@@ -0,0 +1,5 @@
+# Setting an Optional Landing URL
+
+On login, by default, Users will land on the Dashboard page (Operations > Dashboard). However, User and Tenant Roles may have custom landing URLs set. Setting a custom landing URL on the Tenant Role will apply globally to all Users within the Tenant. Landing URLs set on the User Role will supersede the landing URL set on the Tenant Role (if any). No Tenant Role is applied to the Master Tenant so the custom landing URL can only be set on the User Role for these Users.
+
+To set a custom landing URL, create or edit a Role. Set the custom landing URL in the “LANDING URL” field. For example, set `/provisioning/instances` and the Users having that Role will land on the Instances list page each time they log in. Other paths may be used depending on the desired landing page.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json b/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
new file mode 100644
index 0000000..e74f004
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+  "title": "Storage Management",
+  "ordinal": 437,
+  "parent_title": "HPE Bare Metal (BMaaS)",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.html",
+  "topic_cluster": {
+    "clustering_title": "Storage Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787",
+        "clustering_title": "Storage Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md b/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
new file mode 100644
index 0000000..d4ab212
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C3FB4228-B601-4FD3-9802-8D40BEF90787.md
@@ -0,0 +1,14 @@
+# Storage Management
+
+There are two types of storage that are available for an instance to consume. One is the local storage available on the compute server used to create an instance. The other is the remote storage (SAN), using the Alletra MP storage array.
+
+At present, there is no support for the management of the local storage through HPE Morpheus. They are used to install the OS image, and any storage available beyond that is up to the user to configure and use. They cannot be managed from HPE Morpheus.
+
+The remote storage is fully manageable. The user can create/update/delete volumes and manage their attachment to compute servers.
+
+**Subtopics**  
+
+- **[Boot Volume Selection During Instance Creation for Local Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BB9FECCB-9F0C-4305-90D8-B492001ECE14.html)**
+- **[Remote Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3B6AC391-B993-47A2-8264-7389873C8D6D.html)**
+- **[Volume Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-08DC6ECF-EBF9-43E5-A402-D634F71D6B05.html)**
+- **[Volume Consumption](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B637812E-A51A-4AD5-B6F1-5E5822709711.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json b/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
new file mode 100644
index 0000000..3d74b7d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+  "title": "Xen Server",
+  "ordinal": 477,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.html",
+  "topic_cluster": {
+    "clustering_title": "Xen Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E",
+        "clustering_title": "Xen Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md b/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
new file mode 100644
index 0000000..af4f227
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C414D190-6C9D-441E-AFB2-4C0EE3C7F19E.md
@@ -0,0 +1,152 @@
+# Xen Server
+
+## Add a Xen Server Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + CREATE CLOUD, select Xen, and then click Next.
+3. Enter the following into the Create Cloud modal: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   API URL
+   :   IP or URL of Xen Host. ex: xenserver.domain.com
+
+   CUSTOM PORT
+   :   Port for non standard xen server clouds
+
+   USERNAME
+   :   Xen Host Username
+
+   PASSWORD
+   :   Xen Host Password
+
+   Inventory Existing Instances
+   :   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+4. The Cloud can now be added to a Group or configured with additional Advanced options.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json b/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
new file mode 100644
index 0000000..a3fbfae
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+  "title": "Provisioning the Cluster",
+  "ordinal": 181,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F",
+        "clustering_title": "Provisioning the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md b/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
new file mode 100644
index 0000000..c5f785f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C48BBE9B-C5E3-4F60-8362-0D05D4634B2F.md
@@ -0,0 +1,27 @@
+# Provisioning the Cluster
+
+As mentioned in the previous section, this example is starting with three provisioned Ubuntu 22.04 boxes. I also have a HPE Morpheus Enterprise-type Cloud to house the cluster. Begin the cluster creation process from the Clusters list page (Infrastructure > Clusters). Click + ADD CLUSTER and select “HVM”.
+
+![../../_images/createHpevmCluster.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F721FD37-B1E8-48D5-A817-E9A23048CACD-high.png)
+
+HPE Morpheus Enterprise gives the option to select a hyperconverged infrastructure (HCI) **LAYOUT** or non-HCI. In this example, the HCI Layout is used (requires a three-node minimum). Next, configure the names and IP addresses for the host boxes (**SSH HOST**). The SSH HOST name configuration is simply a display name in HPE Morpheus Enterprise, it does not need to be a hostname. By default, configuration space is given for three hosts which is what this example cluster will have. You must at least configure one and it’s possible to add more by clicking the (+) button. The **SSH PORT** is pre-configured for port 22, change this value if applicable in your environment. Next, set a pre-existing user on the host boxes (**SSH USERNAME** and **SSH PASSWORD**) and **SSH KEY**. Use a regular user with sudo access.
+
+![../../_images/createClusterTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-15EB662D-9111-4C88-826F-235318761007-high.png)
+
+In the next part of the modal, you’ll configure the storage devices and network interfaces. When Ceph initializes, it needs to be pointed to an initial data device. Configure this in the **DATA DEVICE** field. At this time, only one device may be given but in the near future, an update will allow for multiple devices to be configured which would be added to the total Ceph storage as one large volume. Find your disk name, if needed, with the `lsblk` command. In my case, the target device is located at `/dev/sdb`.
+
+Though not strictly required, it’s recommended to have separate network interfaces to handle cluster management, storage traffic, and compute. In this example case, `eth0` is configured as the **MANAGEMENT NET INTERFACE** which handles communication between the cluster hosts. `eth1` is configured as the **STORAGE NET INTERFACE** and `eth2` is configured as the **COMPUTE NET INTERFACE**. The **COMPUTE VLANS** field can take a single value (ex. 1) or a range of values (ex. 22-25). This will create OVS port group(s) selectable as networks when provisioning workloads to the cluster. If needed, you can find your network interface names with the `ip a` command.
+
+Next, only one **CPU TYPE** is currently supported (`x86_64`) though this may change in the future. For **CPU MODEL** configuration, we surface the entire database of model configurations from `libvirt`. If unsure or if you don’t know of a specific reason to choose one or the other, select `host-model` which is the default option.
+
+Finally, select a **DYNAMIC PLACEMENT** and **POWER POLICY**configuration. When enabled, Dynamic Placement will automatically balance VMs across cluster hosts based on resource utilization. When disabled, VMs will only migrate to a new host if they are pinned to a specific host or failed over and not running on the preferred host. With Power Policy, set Balanced (default) or Performance configuration. Balanced optimizes for a mix of performance and efficiency. Performance mode is optimized for scenarios requiring maximum performance. It reduces network latency by applying configurations similar to the `tuned` "network-latency" profile and switches CPUs into performance mode.
+
+NOTE
+
+Power Policy settings require Agent version 3.0.0+ running on the HVM Host and take effect following the next sync cycle. You can upgrade HVM Host Agents by navigating to the Host detail page, opening the ACTIONS menu, and selecting Upgrade Agent. Alternatively, you can select Download Agent Script to download a script which can be run on the HVM Host to upgrade its Agent version. Download scripts are specific to the HVM Host so you will need an individual script per HVM Host. Power Policy settings will persist following a HVM Host reboot.
+
+Click NEXT to move to the Review tab for final review, and COMPLETE to kick off cluster provisioning.
+
+![../../_images/createClusterBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8FF3A6DF-6A14-4A7D-B4C1-7E6BDB83B44D-high.png)
+
+At this point we’ve kicked off the process for configuring the cluster nodes. Drill into the Cluster detail page and click on the History tab. Here we can monitor the progress of configuring the cluster. HPE Morpheus Enterprise will run scripts to install KVM, install Ceph, install OVS, and to prepare the cluster. In just a short time, the cluster provisioning should complete and the cluster will be ready to deploy workloads.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json b/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
new file mode 100644
index 0000000..3f86861
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+  "title": "Terraform",
+  "ordinal": 380,
+  "parent_title": "Automation Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.html",
+  "topic_cluster": {
+    "clustering_title": "Terraform",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C52A3557-8979-44A4-9FCE-480426F55A7F",
+        "clustering_title": "Terraform"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md b/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
new file mode 100644
index 0000000..f0d1459
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C52A3557-8979-44A4-9FCE-480426F55A7F.md
@@ -0,0 +1,499 @@
+# Terraform
+
+## Requirements
+
+### Role Access
+
+- In order to see the Terraform App Blueprint type option and create Terraform App Blueprints in Library > Blueprints > App Blueprints, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+- In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+- Existing Terraform Blueprints must be added before they can be provisioned from Provisioning > Apps.
+- In order to provision Terraform Apps, the user must have Role permissions for Provisioning: Apps set to Full.
+
+### Github/Git Repo
+
+- To use .tf files from a Git repo, a Git or Github integration needs to be configured in Administration > Integrations. If one is not configured, .tf or .tf.json files can be manually drafted in HPE Morpheus Enterprise and added to Terraform App Blueprints but they could not be sourced from version control repositories.
+
+### Supported App Provisioning Targets
+
+- VMware
+- Amazon AWS
+- Microsoft Azure
+- Google Cloud Platform (GCP)
+- Oracle Cloud
+
+NOTE
+
+Additional clouds are planned for later releases.
+
+## Terraform Installation
+
+The first time you attempt to provision a Terraform App, you may come across an error indicating that Terraform is not installed:
+
+```
+```
+bash: line 1: terraform: command not found
+```
+```
+
+### Command Not Found Error Screenshot
+
+![../../_images/1commandNotFound.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-544D6493-88F5-42A8-A371-34CBF5087BB9-high.png)
+
+This likely means you’ve not yet configured Terraform Settings within HPE Morpheus Enterprise global settings. Navigate to Administration > Settings > Provisioning and scroll down to the Terraform Settings section. By default, the Terraform Runtime field is set to “Manual”. When set this way, HPE Morpheus Enterprise will attempt to use Terraform as installed on the appliance box and it may not be currently installed. To have HPE Morpheus Enterprise manage the Terraform installation process for you and manage Terraform versioning on a per-App basis, set the Terraform Runtime to “Auto”. You should also set the Default Terraform Version field as well. When a version is set on a Terraform Spec Template or Terraform App Blueprint, that version will supersede the default version indicated in global settings.
+
+### Configured Terraform Runtime Screenshot
+
+![../../_images/2configuredTfRuntime.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1F6CCDC8-4ED4-49DD-ABF3-DE0929CF7011-high.png)
+
+IMPORTANT
+
+HPE Morpheus Enterprise appliances which do not have access to the Internet will need to leave Terraform Runtime settings on “Manual” and ensure Terraform is installed appropriately on the appliance. Install Terraform in the /usr/sbin/terraform directory and make sure it’s owned by the morpheus-local user.
+
+## Creating Terraform App Blueprints
+
+### About this task
+
+In order to provision Terraform apps, Terraform App Blueprints must be created first.
+
+### Procedure
+
+1. Navigate to Library > Blueprints > App Blueprints
+2. Select + ADD
+3. Name the Blueprint and select Terraform type. 
+
+   NOTE
+
+   In order to see the Terraform Blueprint type option, the HPE Morpheus Enterprise user must have Role permissions for Provisioning: Blueprints - Terraform set to Full.
+4. Select NEXT
+5. Configure the following: 
+
+   NAME
+   :   Friendly name for the App Blueprint in HPE Morpheus Enterprise
+
+   DESCRIPTION
+   :   Description for your App Blueprint shown in the Apps list (optional)
+
+   CATEGORY
+   :   A category for your App (optional)
+
+   IMAGE
+   :   Add reference icon for your App Blueprint to make it more identifiable at provision time (optional)
+
+   CONFIG TYPE (select Terraform Specs, Terraform (.tf), Terraform.json, or Git Repository)
+
+   Terraform (.tf)
+
+   CONFIG
+   :   Draft or paste in .tf content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform (.tf.json)
+
+   CONFIG
+   :   Draft or paste in .tf.json content in the config text area. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned
+
+   Terraform Specs
+
+   SPEC TEMPLATE
+   :   Using the typeahead field, select all Terraform-type Spec Templates which make up your App. Variables will be presented as input fields during App provisioning, or auto-populated with matching values if contained in a selected TFVAR Secret file added to the Cypher service.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+
+   Git Repository
+
+   SCM INTEGRATION
+   :   Select a Github or Git integration that has been added in Administration > Integrations and which contains relevant .tf files. Integrations must be pre-existing prior to creating the App Blueprint.
+
+   Repository
+   :   Select a repository which contains relevant .tf files from the Github or Git integration selected in the prior step.
+
+   BRANCH OR TAG
+   :   Select the Git branch containing the desired version of .tf files for the App. “master” is chosen by default if no value is entered.
+
+   WORKING PATH
+   :   Enter the repo path for the .tf file(s). `./` is default if no value is entered.
+
+   TFVAR SECRET
+   :   Select an existing tfvar secret file stored in HPE Morpheus Enterprise Cypher service. This list is automatically filtered to show all Cypher entries which are currently stored at the “tfvar/” Cypher mount point. Note that tfvars already set in any existing Terraform Cloud Profiles will already be available to your App and wouldn’t need to be set here.
+
+   VERSION
+   :   Specify a version required by your Terraform App (optional). If specified, the given version will supersede the global Terraform version specified in HPE Morpheus Enterprise global settings (Administration > Settings > Provisioning). “Terraform Runtime” must also be set to “auto” in global settings for HPE Morpheus Enterprise to manage the Terraform version for you. When set to “manual”, HPE Morpheus Enterprise will use the Terraform version installed on the appliance box.
+
+   OPTIONS
+   :   Specify any valid Terraform command line options HPE Morpheus Enterprise should append to its internal “terraform apply” call when the App is provisioned.
+6. Select COMPLETE
+
+### Results
+
+HPE Morpheus Enterprise will scan the blueprint to check for validity and will surface any errors which need correcting before the App Blueprint can be saved. Your Terraform App is ready to be provisioned from Provisioning > Apps.
+
+## Cloud Profiles
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+## Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+### Create a Terraform Profile
+
+#### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+#### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+## Provisioning Terraform Apps
+
+### About this task
+
+NOTE
+
+Terraform App Blueprints must be added to Library > Blueprints > App Blueprints before they can be provisioned. At least one Terraform App Blueprint must exist before Terraform Apps can be provisioned from Provisioning > Apps.
+
+NOTE
+
+In order to provision Terraform Apps in Provisioning > Apps, the Morpheus user must have Role permissions for Provisioning: Blueprints - Terraform set to Provision or Full.
+
+### Procedure
+
+1. Navigate to Provisioning > Apps
+2. Select + ADD
+3. Choose an existing Terraform App Blueprint
+4. Select NEXT
+5. Enter a NAME for the App and select the Group, Default Cloud and Environment (optional)
+6. Select NEXT
+7. Configure the following sections: 
+
+   App Settings
+
+   BACKEND TYPE
+   :   Internal is the default selection and the most secure choice. This sends the Terraform state back to the appliance via HTTP loopback to be stored in the appliance database. Users may also select Local which will write Terraform state to the local filesystem first before being stored in the database and removed from the local filesystem. If unsure, use the default Internal value. Backend Type selection is currently only available for Terraform Apps. Selecting Backend Type for Terraform Instance Types is a planned future feature addition.
+
+   VALIDATE PLAN
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not perform its typical validation to ensure the Terraform spec is valid. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   RUN APPLY
+   :   Marked by default. When unmarked, HPE Morpheus Enterprise will not apply the plan at completion of the App wizard. Typically users would only unmark this box if onboarding an existing App with Initial State (see Advanced Options configuration below).
+
+   Terraform Variables Populate any required or optional variables here. Variables whose values are stored in an associated tfvars file sourced from HPE Morpheus Enterprise Cypher are masked from the user. Variables stored in any Terraform Cloud Profile associated with the selected Cloud also are automatically masked. Other variables will be presented in the Terraform Variables section for user entry and any configured default values on the Terraform spec will be pre-loaded. Advanced Options
+
+   REFRESH MODE
+   :   Set an interval at which HPE Morpheus Enterprise should automatically check the App for drift from the Terraform spec. If set to Manual, HPE Morpheus Enterprise will never perform automatic checks and the user must do so when desired. The results of drift checks are reported on the App detail page and users may apply the plan at any time to bring the App back into alignment with the Terraform spec.
+
+   INITIAL STATE
+   :   Paste in existing Terraform state to onboard an existing Terraform App for HPE Morpheus Enterprise management. Though the field is small, it will accept large, multiline Terraform state. When creating an App from existing state, users may want to skip plan validation or may not want to apply right away. Opt out of these functions by unmarking the corresponding box in the App Settings section.
+
+   NOTE
+
+   Terraform state import is a new feature. At this time, some state file components may break the import process. This feature is being iterated on rapidly to increase coverage to as many application types and conditions as possible.
+
+   Terraform Preview Review the Terraform App components here, including any providers invoked, variables surfaced from the App spec, resources to be created, and .tf files utilized. There is no user input to be entered into this section.
+8. Select NEXT
+9. HPE Morpheus Enterprise will now validate the App (unless the user has opted out of this check) and surface any errors which would cause provisioning issues. If all is well, click COMPLETE
+
+### Results
+
+TIP
+
+Review the App in the Terraform Preview section. If any config data needs to be edited, select the RAW tab, edit the config, and then select the BUILDER tab once again. The config changes from the RAW edit will be updated in the preview section for further review. Permanent edits can be made by editing the App Blueprint, pushing .tf changes to your code repository, or Terraform Spec Templates (depending on how the .tf files are sourced for your App Blueprint).
+
+The Terraform App will begin to provision.
+
+Once provisioning is completed, note the State tab in the App details page (Provisioning > Apps > select the App). This tab contains subsections related to state management which is discussed in greater detail in the next section.
+
+## Terraform App State Management
+
+State management is handled from the State Tab of the Terraform App detail page (Provisioning > Apps > selected App). With the tab selected, the Terraform command field will be present regardless of the selected subsection. Use this field to send Terraform commands to your apps just like using Terraform from the command line. Press return on the keyboard or click on the “play” button to the right of the text field to execute the commmand.
+
+TIP
+
+“terraform” is automatically entered for each command as printed along the left edge of the text field. Thus, you don’t need to enter “terraform” with each command sent. Entering “state” or “plan” is equal to entering “terraform state” or “terraform plan” from the command line.
+
+![../../_images/appDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5AB2D1E8-EFB9-43FA-82CE-0229BA99CD63-high.png)
+
+When Terraform commands are executed against the application, HPE Morpheus Enterprise provides progress bars and command output in the UI. Command output is shown underneath the Terraform command field. Users can dismiss individual output windows by clicking the “x” button in the upper-right of each window. All command output can be dismissed by clicking the blue “x” button to the right of the command field itself.
+
+Within the ACTIONS reside four selections: Refresh State, Apply State, Edit Inputs, and Edit STATE. Selecting Refresh State is equivalent to using the “terraform plan” command from the command line. This will read the existing state of any existing objects which are part of the App and compare their current configuration against the prior state. Any differences will be noted in the output. If differences are discovered, the App is considered to be in a “drift” state. This drift status is shown in the UI when the user is viewing the “State” subsection (which is described in greater detail in the next section). The output of the Refresh State command, including detailed information about changes Terraform would make to App objects to in order to realign them with the App spec are shown in the UI.
+
+![../../_images/planOutput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E81EA071-D055-4481-B6FF-CE9642A07B68-high.png)
+
+The Apply State selection brings up a modal which allows the user to view the App spec once again. This includes being able to view and edit Terraform variables if needed. After making any needed edits, click NEXT and HPE Morpheus Enterprise will validate the App once again, just like it did at provision time. On the next tab of the wizard, HPE Morpheus Enterprise will show the user and planned changes that would be executed if the user completes the modal. An output will be shown as if “terraform plan” were run from the command line. Make note of any App objects which would be created, altered, or destroyed if the actions are accepted as HPE Morpheus Enterprise would immediately take them if desired. When ready, click COMPLETE. This will execute all planned changes as if the user had run “terraform apply -auto-approve” from a terminal session.
+
+Edit Inputs allows for editing of Input values without going through the process of applying state. Edit State displays the state in a large text area for direct editing.
+
+### State Subsection
+
+The State Subsection shows the current drift state of the App. This includes when HPE Morpheus Enterprise has last checked for drift and whether the App is currently in a “Drift” or “No Drift” state. If the App is currently in a Drift state, users can select Refresh State from the ACTIONS menu to identify which objects and attributes have deviated from the App configuration.
+
+![../../_images/stateSubsection.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6BEDAC1D-B4E0-4E17-83F3-7A3AD9036241-high.png)
+
+### Specs Subsection
+
+The Specs Subsection will show the user all HPE Morpheus Enterprise Spec Templates (Library > Templates > Spec Templates) which make up the App. Users may even edit Spec Template config directly from this view by clicking the Edit (pencil) icon to the right of each Spec Template listed.
+
+TIP
+
+Editing a Spec Template here will detach it from the source object, essentially making it a brand new object that exists only here. All future updates to that Spec Template would have to be made here going forward. In most cases, it’s advisable to edit the Spec Template directly at the source. For example, if this Spec Template were sourced from an integrated version control repository (ex. Github), it’s likely the best option to make a new commit into your repository and then let Terraform handle the process of bringing your App in line with the new specifications.
+
+![../../_images/editSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4FB5CB67-B878-424C-BA28-531EEB556CB0-high.png)
+
+### Plan Subsection
+
+This section displays the output of the most recent “terraform plan” run against your App. This will either indicate that your infrastructure (App) matches the configuration or it will indicate that a drift of some sort has taken place.
+
+### Input Subsection
+
+This section lists all Terraform inputs, such as variables, which are relevant to the App. Variable values are shown unless they are flagged as sensitive in your configuration. All variables sourced from a HPE Morpheus Enterprise Cypher tfvars mount will automatically be masked.
+
+### Output Subsection
+
+This section lists all configured Terraform output.
+
+## Terraform Instance Type Example
+
+Terraform Spec can also be used within the HPE Morpheus Enterprise Instance Type construct in addition to App Blueprints and Apps. Expand the section below to see a complete end-to-end example of a Terraform Instance Type from drafting new Spec Templates through to provisioning.
+
+### Terraform Instance Type Example
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+**AWS Subnet by Count**
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+**AWS Terraform Default Vars**
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+**AWS Provider Role Assume**
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+**AWS Terrform Locals**
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+**AWS VPC**
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json b/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
new file mode 100644
index 0000000..86df294
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+  "title": "File Shares",
+  "ordinal": 232,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.html",
+  "topic_cluster": {
+    "clustering_title": "File Shares",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA",
+        "clustering_title": "File Shares"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md b/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
new file mode 100644
index 0000000..60fc81c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C5FC61E9-7955-4A9D-8E80-E92683B538AA.md
@@ -0,0 +1,495 @@
+# File Shares
+
+File Shares are for Backup, Archives, Deployment and Virtual Images storage targets. File Shares can be browsed and files and folders can be uploaded, downloaded or deleted from the File Shares section. Retention Policies can be set on Storage File Shares for files to be deleted or backed up to another File Share after a set amount of time.
+
+## Supported File Share Types
+
+- Azure
+- CIFS (Samba Windows File Sharing)
+- Dell EMC ECS Share
+- Dell EMC Isilon Share
+- Local Storage
+- NFSv3
+
+## Azure File Shares
+
+### About this task
+
+To Add an Azure File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Azure from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name for the file share in HPE Morpheus Enterprise.
+
+   STORAGE ACCOUNT
+   :   Name of the Storage Account in Azure for the file share
+
+   STORAGE KEY
+   :   Storage Key provided from Azure
+
+   SHARE NAME
+   :   Enter existing Azure Storage Share name or, to add a new Share, enter a new name and mark the Create Bucket box below
+
+   CREATE BUCKET
+   :   Mark if the share entered in SHARE NAME does not exist and needs to be created
+
+   DEFAULT BACKUP TARGET
+   :   Sets this file share as the default backup target when creating Backups. If selected, the option to UPDATE EXISTING BACKUPS will appear. Mark to update existing backups to this file share
+
+   DEFAULT DEPLOYMENT ARCHIVE TARGET
+   :   Sets this file share as the default storage target when creating deployment archives
+
+   DEFAULT VIRTUAL IMAGE STORE
+   :   Sets this file share as the default storage target when uploading Virtual Images from the Virtual Images section or when importing Images from Instance Actions
+
+   RETENTION POLICY
+   :   None
+       :   Files in the share will not be automatically deleted or backed up
+
+       Backup Old Files
+       :   This option will backup files after a set amount of time and remove them from the file share
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup target
+
+               BACKUP BUCKET
+               :   Search for and then select the desired backup bucket
+
+       DELETE OLD FILES
+       :   This option will delete files from this share after a set amount of days
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the share
+6. Select SAVE CHANGES
+
+### Results
+
+The file share will be created and displayed in the file shares tab.
+
+- To browse, upload, download, or delete files from this file share, select the name of the share from the File Shares tab.
+- To edit the file share, select the edit icon or select the name of the share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Re-pointing a file share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a file share, select the trash icon or select the name of the file share and click DELETE.
+
+  WARNING
+
+  When deleting a file share, all Deployment versions and Backups associated with the file share will be deleted.
+
+## CIFS File Shares
+
+### About this task
+
+To Add a CIFS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select CIFS (Samba Windows File Sharing) from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter host IP or resolvable hostname
+       :   Example: `192.168.200.210`
+
+   USERNAME
+   :   CIFS Share Username
+
+   PASSWORD
+   :   CIFS Share User Password
+
+   SHARE PATH
+   :   Enter CIFS Share Path
+       :   Example: `cifs`
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC ECS File Shares
+
+### About this task
+
+To Add a Dell EMC ECS File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC ECS Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC ECS Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC ECS Share Path
+       :   Example: `ecs-file-share-1`
+
+   USER
+   :   Dell EMC ECS User
+
+   SECRET KEY
+   :   Dell EMC ECS Secret key
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC ECS Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC ECS Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Dell EMC Isilon File Shares
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## Local Storage File Shares
+
+### About this task
+
+IMPORTANT
+
+Local Storage refers to local to the HPE Morpheus Enterprise Appliance and the path must be owned by morpheus-app. Please be conscious of storage space. High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+NOTE
+
+To change the owner of a file path to be used as a Local Storage File Share, run `chown morpheus-app.morpheus-app /path` on the HPE Morpheus Enterprise Appliance.
+
+NOTE
+
+HPE Morpheus Enterprise will validate path and ownership of the File Share Path.
+
+To Add a Local Storage File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Local Storage Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE PATH
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+       :   Example: `/var/opt/morpheus/morpheus-ui/vms/virtual-images`
+
+           IMPORTANT
+
+           High Availability configurations require Local Storage File Shares paths to be shared storage paths between the font end HPE Morpheus Enterprise Appliances.
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
+
+## NFSv3 File Shares
+
+### About this task
+
+NOTE
+
+Configure access to the NFS folder on the NFS Provider prior to adding the NFSv3 File Share.
+
+NOTE
+
+Upon save HPE Morpheus Enterprise will create a persistent mount owned by `morpheus-app.morpheus-app` on the HPE Morpheus Enterprise Appliance for the NFSv3 File Share. The HPE Morpheus Enterprise appliance will require access to the following ports in order to mount the share: 111, 54302, 20048, 2049, 46666, 42955, 875. With some storage solutions, you may need to enable insecure, unprivileged ports, or allow non-root on the export before HPE Morpheus Enterprise is able to successfully mount the share.
+
+To Add a NFSv3 File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select NFSv3 from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   HOST
+   :   Enter the File Share path on the local HPE Morpheus Enterprise Appliance.
+
+   EXPORT FOLDER
+   :   Enter the NFSv3 Folder
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
new file mode 100644
index 0000000..d83d062
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+  "title": "Full HA Upgrade",
+  "ordinal": 24,
+  "parent_title": "Upgrading",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.html",
+  "topic_cluster": {
+    "clustering_title": "Full HA Upgrade",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC",
+        "clustering_title": "Full HA Upgrade"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
new file mode 100644
index 0000000..c1fa233
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C63FE489-0915-45C5-8B26-D9E4F3A8B0DC.md
@@ -0,0 +1,301 @@
+# Full HA Upgrade
+
+Full HA configurations represent multiple app nodes with external (non-system) MySQL, RabbitMQ and Opensearch Clusters or Services.
+
+## HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+## Overview
+
+When upgrading to v8.1.2 only services local to the Morpheus App node(s) will be upgraded. For fully distributed configurations (Full HA) where MySQL, RabbitMQ and Opensearch are external, the upgrade process will not upgrade these services.
+
+Refer to [breaking changes](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-0289251C-DBFE-418E-B794-3B9FCFB184CF) for externalized MySQL, Elasticsearch and/or RabbitMQ version requirements.
+
+## Upgrade Instructions
+
+### Full HA Debian / Ubuntu Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.2.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Elasticsearch and RabbitMQ services are external to the App nodes. The following steps assume 3 app nodes, adjust accordingly.
+
+#### HPE Morpheus Enterprise Packages
+
+HPE Morpheus Enterprise Release packages can be downloaded from My HPE Software Center. Contact your account manager with any questions regarding access.
+
+#### Full HA Non-Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch the UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui  
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with ``morpheus-ctl tail morpheus-ui``.
+   ```
+   ```
+4. Once App Node 2 upgrade has completed and the UI is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (deb)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`.
+2. Download the upgrade package from My HPE Software Center and transfer to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the deb package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+4. Once App Node 2 upgrade has completed and the ui is available, upgrade the deb package on App Node 3, and run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo dpkg -i morpheus-appliance_x.x.x-1_amd64.deb  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`. Once morpheus-ui is started, proceed to the next node.
+5. The upgrade is complete and the HPE Morpheus Enterprise UI services should be running on the three allocated nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+### Full HA RPM Upgrade
+
+The following covers upgrading the HPE Morpheus Enterprise App nodes in Full HA Architecture configurations to v8.1.2.
+
+IMPORTANT
+
+The following is only for Full HA Architecture configurations, where MySQL, Opensearch and RabbitMQ services are external to the App nodes.
+
+#### Full HA Non-Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+IMPORTANT
+
+It is important to stop the morpheus-ui service on all app nodes prior to upgrade. Failure to do so will result in a flood of log errors due to previous message serialization conflict. The messages will eventually expire and the logs will clear.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Starting with App Node 3, on All App Nodes, stop the morpheus-ui services via `morpheus-ctl stop morpheus-ui`. If you receive a timeout, run `morpheus-ctl graceful-kill morpheus-ui`. 
+
+   ```
+   ```
+   [root@app-server-3 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-2 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+
+   ```
+   ```
+   [root@app-server-1 ~]# morpheus-ctl stop morpheus-ui
+   ```
+   ```
+2. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+
+   NOTE
+
+   All services will automatically be stopped and started during the reconfigure process. After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+4. Then upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure
+   ```
+   ```
+5. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
+
+#### Full HA Rolling Upgrade Process (rpm)
+
+##### About this task
+
+WARNING
+
+Depending on your current version, a non-rolling upgrade may be required to upgrade to version v8.1.2. Refer to the [upgrade compatibility table](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C131BD09-5DB9-4C31-8106-AA5A7A735F45.html#GUID-6F0A533B-BEE6-4407-AB67-681A4CC40303) to confirm whether a rolling upgrade is possible. If a rolling upgrade is not possible, refer to the appropriate set of non-rolling upgrade instructions to proceed.
+
+WARNING
+
+HPE Morpheus Enterprise v8.1.2 contains new node and VM node packages that require 3.5GB of storage. It is safe to run `sudo rm -Rf /var/opt/morpheus/package-repos/*` after v8.1.2 package installation and before reconfigure to clean old node and vm node packages from the package-repo when room is needed.
+
+##### Procedure
+
+1. Download the upgrade package from My HPE Software Center and transfer it to each application node. Then, upgrade the deb package on App Node 1, then run a Reconfigure on App Node 1 
+
+   ```
+   ```
+   [root@app-server-1 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-1 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-1 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-1 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+2. Once App Node 1 upgrade has completed and the UI is available, upgrade the RPM package on App Node 2, then run a Reconfigure on App Node 2. 
+
+   ```
+   ```
+   [root@app-server-2 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-2 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-2 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-2 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the UI service to watch UI startup logs with `morpheus-ctl tail morpheus-ui`.
+3. Once App Node 2 upgrade has completed and the UI is available, upgrade the RPM package on App Node 3, then run a Reconfigure on App Node 3 
+
+   ```
+   ```
+   [root@app-server-3 ~]# sudo rpm -Uhv morpheus-appliance-x.x.x-x.x86_64.rpm  
+   [root@app-server-3 ~]# sudo morpheus-ctl stop morpheus-ui  
+   [root@app-server-3 ~]# sudo morpheus-ctl reconfigure  
+   [root@app-server-3 ~]# sudo morpheus-ctl start morpheus-ui
+   ```
+   ```
+
+   After the reconfigure has succeeded, tail the ui service to watch ui startup logs with `morpheus-ctl tail morpheus-ui`.
+4. The upgrade is complete and the HPE Morpheus Enterprise-ui services should be running with clustered Elasticsearch and RabbitMQ services across the 3 nodes.
+
+##### Results
+
+IMPORTANT
+
+If reconfigure after a rpm package upgrade stalls or hangs on starting a local service it is possible the `morpheus-runsvdir` service did not start or a process it was managing was manually shutdown or killed. To resolve, run `systemctl stop morpheus-runsvdir` then `systemctl start morpheus-runsvdir`, then run reconfigure again, `morpheus-ctl reconfigure`.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json b/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
new file mode 100644
index 0000000..dc21dd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+  "title": "Analytics",
+  "ordinal": 56,
+  "parent_title": "Operations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html",
+  "topic_cluster": {
+    "clustering_title": "Analytics",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B",
+        "clustering_title": "Analytics"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md b/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
new file mode 100644
index 0000000..7962a97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.md
@@ -0,0 +1,18 @@
+# Analytics
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B67FF274-342F-4B96-B5F9-0B8222C662DC.html)**
+- **[Costing: Cloud Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-180B8370-AEF2-45C1-9E72-99FF796CB222.html)**
+- **[Costing: Group Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-782ABB81-3DF3-42C4-BDC1-2B38325B7CFA.html)**
+- **[Costing: Tenant Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB95E8ED-82A1-493E-82D0-613D80FB602E.html)**
+- **[Costing: User Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8AC08484-473F-41E8-B106-A90BC96B03C4.html)**
+- **[Costing: Workload Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2E69D481-2EB0-4F2B-AE21-9FF544F76341.html)**
+- **[Costing: Budget Analysis](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html)**
+- **[Costing: Tag Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5AE10D03-5E33-4437-8477-059B0390B662.html)**
+- **[Utilization: Utilization vs Cost](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-44FE85BB-E407-4D90-A1EB-57E6EFF05D6C.html)**
+- **[Capacity: Capacity Planning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-79BE45C2-3437-40AA-9B1F-BDC6D4F2C41F.html)**
+- **[Workloads: Instance Type Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9F78ED42-26BC-405F-88BC-3B14279A3306.html)**
+- **[Workloads: Instance Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BF9EF709-0BC5-4DD9-A523-8A3286A27382.html)**
+- **[Workloads: Blueprint Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-06F0DB01-64F2-4D07-93F8-38AC80DBB09B.html)**
+- **[Workloads: Apps Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2DE45951-E56A-4651-AB77-F8C894E28788.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json b/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
new file mode 100644
index 0000000..ccb4aa1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+  "title": "Monitoring Groups",
+  "ordinal": 259,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C742E2B5-1585-459D-B13A-139DEB0AC122",
+        "clustering_title": "Monitoring Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md b/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
new file mode 100644
index 0000000..1ccf715
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C742E2B5-1585-459D-B13A-139DEB0AC122.md
@@ -0,0 +1,22 @@
+# Monitoring Groups
+
+Group monitors can only contain checks and can be edited or created in Monitoring  >  Groups. Besides simply adding and removing checks to a group there are a few other useful options that can be customized in a group:
+
+Name
+:   A friendly name for the group monitor in HPE Morpheus Enterprise
+
+Min Checks
+:   This specifies the minimum number of checks within the group that must be happy to keep the group from becoming unhealthy
+
+Max Severity
+:   The maximum severity incident a failed check may create. This setting overrides a check’s max severity setting
+
+Affects Availability
+:   If checked, a failing group monitor impacts system-wide availability calculations
+
+Checks
+:   Use the typeahead field to select pre-existing checks for the group monitor. If check(s) need to be created, this can be done in Monitoring > Checks
+
+NOTE
+
+Some useful information can also be seen on the detail page of a check. For example, the average response time of all checks within the group, or an aggregated check history can be viewed.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json b/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
new file mode 100644
index 0000000..4eea273
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+  "title": "Overview",
+  "ordinal": 126,
+  "parent_title": "Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md b/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
new file mode 100644
index 0000000..39712ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7D69012-9F80-4ACD-9F6D-985E827DE63D.md
@@ -0,0 +1,18 @@
+# Overview
+
+The Blueprints section is used to compose provisioning catalogs. The Blueprints section is composed of:
+
+- Instance Types
+- Layouts
+- Node Types
+- App Blueprints
+- Catalog Items
+- Cluster Layouts
+
+Additionally, items from Options and Templates sections are incorporated to call in custom options for users, IaaS spec files, scripts, and more. See Options and Templates within HPE Morpheus Enterprise Library for more information on creating or sourcing the items below from version control. In some cases, they may need to be pre-existing for the most efficient creation of Blueprints.
+
+- Inputs
+- Option Lists
+- File Templates
+- Scripts
+- Spec Templates
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json b/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
new file mode 100644
index 0000000..8d2d6bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+  "title": "Add Load Balancer during Provisioning",
+  "ordinal": 498,
+  "parent_title": "Add Load Balancer to Instance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.html",
+  "topic_cluster": {
+    "clustering_title": "Add Load Balancer during Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953",
+        "clustering_title": "Add Load Balancer during Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md b/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
new file mode 100644
index 0000000..5471a5b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7E46410-93B0-408D-BAF6-B6D4B8DF0953.md
@@ -0,0 +1,55 @@
+# Add Load Balancer during Provisioning
+
+## About this task
+
+In the Instance Provisioning wizard, Load Balancers can be configured in the Automation > LoadBalancer section.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select + ADD.
+3. Select an Instance Type that supports scaling. (ENABLE SCALING (HORIZONTAL) flagged on Instance Type configuration)
+4. Proceed with Instance configuration to the Automation section.
+5. Fill in the following: 
+
+   VIP ADDRESS
+   :   Define IP Address for the Virtual Server
+       :   - Example: 10.30.23.191
+
+   VIP PORT
+   :   Define port for the Virtual Server
+       :   - Example: 80
+
+   VIP HOSTNAME
+   :   Define hostname that will resolve to the VIP IP.
+       :   - Example: jwDemoHaApp59.den.example.com
+
+   VIRTUAL SERVICE NAME
+   :   Define name for the Virtual Service. Defaults to `${instance.name}`
+
+   BALANCE MODE
+   :   Specify balance mode for the VIP
+       :   - Least Connections
+           - Round Robin
+
+   STICKY MODE
+   :   Specify sticky session options for the VIP
+       :   - Source IP
+           - Cookie
+
+   SHARED VIP ADDRESS
+   :   Select if VIP is shared, then enter DIRECT VIP ADDRESS
+
+   SSL CERT
+   :   SSL Certificate that will be applied to the VIP.
+       :   - No SSL
+           - Select existing Certificate from Infrastructure  >  Keys & Certs or from a Trust Provider Integration.
+
+       USE EXTERNAL ADDRESS FOR BACKEND NODES
+       :   - Select if traffic from LB to Backend Nodes needs to be sent to the External Addresses, or leave deselected to use Internal Addresses for Backed Nodes.
+6. Optionally configure auto-scaling configuration in the `Scale` section
+7. Select NEXT and provision the Instance.
+
+## Results
+
+After all nodes in the Instance are provisioned, the LB configuration will be added to the Instance and Virtual Servers, Services and Servers will be created and configured on the NetScaler. The Load Balancer settings and status will be visible in the Instance details page LOAD BALANCER section, with additional details, links, and configurations options available in the `SCALE` tab.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json b/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
new file mode 100644
index 0000000..6edb02d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+  "title": "Image Prep (Windows)",
+  "ordinal": 192,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.html",
+  "topic_cluster": {
+    "clustering_title": "Image Prep (Windows)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62",
+        "clustering_title": "Image Prep (Windows)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md b/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
new file mode 100644
index 0000000..2046c15
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C7F6CB71-54A5-42D2-8EC3-5A847CD7DD62.md
@@ -0,0 +1,102 @@
+# Image Prep (Windows)
+
+This section will go through the steps to prepare a Windows image which can be successfully provisioned to HVM clusters. Additionally, this image can serve as a template from which additional images and HPE Morpheus Enterprise Library items can be built. In this example case, we’ll start from downloading a Windows Server 2019 ISO directly from the Microsoft download center and go all the way through to creating a new Instance Type in HPE Morpheus Enterprise that users can provision on-demand.
+
+With the Windows ISO already downloaded, begin by uploading the ISO as a Virtual Image in HPE Morpheus Enterprise. Virtual Images are added in Library > Virtual Images. Click + ADD and then choose “ISO.” Before adding the file itself, set the following configurations on the Virtual Image:
+
+- **NAME:** A name for the Virtual Image in HPE Morpheus Enterprise, such as “Windows Server 2019 ISO”
+- **OPERATING SYSTEM:** “windows server 2019”
+- **MINIMUM MEMORY:** Filters out Service Plans at provision time which do not meet the minimum value. For this image type, I’ve set 4 GB
+
+In addition to the above, there are a number of checkbox configurations here (many of them are in the expandable “Advanced” section), some of which are checked by default. They should all be unchecked except for “VIRTIO DRIVERS LOADED?” within the “Advanced” expandable section.
+
+With the configurations set, it’s time to upload the ISO to HPE Morpheus Enterprise. Keep in mind that if you do not specify a bucket in which the file should be uploaded, it will be uploaded to the appliance itself. If you choose to do this, be sure you have enough space to store the images you need. Within the UPLOAD VIRTUAL IMAGE modal is a large dropzone labeled “Drop Files Here.” You can drag and drop the ISO file here or you can click the button labeled “Add File” and browse for it. A progress bar will appear, wait until the file is completely uploaded before you save and dismiss the modal. After the file has completely uploaded, click SAVE CHANGES.
+
+![../../_images/progress.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-984BC461-04D2-4759-9E91-D9ACF2C6EB23-high.png)
+
+Next, we’ll provision a VM from the ISO using the built-in HVM Instance Type. Once running, we will configure the VM to any specific requirements and convert it to a template. Navigate to Provisioning > Instances and click + ADD. On the TYPE tab of the Instance provisioning wizard, we select the Instance Type to provision. In this case, select “HVM” and click NEXT.
+
+![../../_images/provisionMvmInstanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9DE2A41A-C675-4E94-819C-7DB350F6B8DA-high.png)
+
+On the GROUP tab, select the Group and Cloud containing the target HVM Cluster and provide a name for the new Instance. In my case, I have an automatic naming policy setting my Instance name, but depending on your appliance configuration you may need to enter a custom name. Click NEXT.
+
+![../../_images/groupTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5C1016FB-39ED-4A2E-9D73-3CE2F1C29456-high.png)
+
+On the CONFIGURE tab, first select the IMAGE. Select the Windows server ISO that was uploaded in the previous step. Based on the minimum memory configuration that was set on the Virtual Image, Plans which are too small will be filtered out. Among compatible Plans, select one that meets your requirements. Next, set the RESOURCE POOL, which is the HVM cluster you’re targeting. Configure disks and disk sizes, as well as network details (this will vary based on HVM cluster configuration). Finally, select the HOST, which is the HVM host within the cluster that the new Instance should initially be provisioned onto.
+
+![../../_images/configTabTop.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8B62B5BD-FAF8-40F3-84C6-E905D7E4E72F-high.png)
+
+As a final step, we need to also expand the “Advanced Options” section and make sure “ATTACH VIRTIO DRIVERS” is checked. This will attach an ISO containing the VirtIO drivers which we’ll use later. Click NEXT.
+
+![../../_images/configTabBottom.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4F832198-6A42-4B65-96DB-614E7AA109F5-high.png)
+
+The final two tabs of the wizard, AUTOMATION and REVIEW, do not require any configuration changes though you may want to review the Instance settings on the final tab. When done, click COMPLETE.
+
+Click on the newly provisioning Instance from the Instances list page. Since this image is being provisioned for the first time, the image must be uploaded to the HVM host. This can take a little bit of time but any future attempts to provision workloads from this image will skip this step. Wait for the Instance to fully complete and appear in a green “Ready” status.
+
+Once the Instance has fully finished provisioning, launch a console session by clicking ACTIONS and then “Open Console.” This will open a new window with a console session into the VM.
+
+![../../_images/initialConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-83AEDC4E-1DB0-4F7E-ABD9-A3D11F699F3D-high.png)
+
+After selecting the language, click “Next.” On the following screen, click “Install Now.” This will begin the Windows setup process on our new VM. You’ll next select the operating system type you wish to install. For this example, I’m installing 2019 standard with desktop experience. Click “Next.”
+
+![../../_images/chooseOs.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D2229A74-662F-4D7F-91A4-166C0050AEE5-high.png)
+
+Accept the licensing terms and click “Next.”
+
+![../../_images/eula1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-270D1487-8799-4388-B67D-3EF2A1EE3631-high.png)
+
+On the next screen, choose a custom install.
+
+![../../_images/clickInstall.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DFF443AF-638B-4234-860C-811B6717A890-high.png)
+
+The next screen asks where Windows should be installed and may be empty. Click “Load Driver” to locate the mounted disk image containing the VirtIO drivers. The search should return a number of VirtIO SCSI controller packages for various Windows flavors. Select the proper package for the Windows version being installed. Click “Next.”
+
+![../../_images/selectVirtioPackage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8941A511-5E0F-4C6B-85F2-BAF23A4AD8CA-high.png)
+
+After a moment, we’re back at the screen asking where Windows should be installed. We should see the disk(s) of size and type selected at the time the VM was provisioned. Select the proper disk and click “Next.” The Windows installation will now begin. Once Windows has fully installed, proceed to the next step.
+
+![../../_images/selectDisk.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4AE6BBA1-CDFA-4D64-A10E-5797AD61C438-high.png)
+
+Following installation, Windows will restart and prompt for an Administrator user password. Set the password and log in as Administrator. Currently, there are no network interfaces configured. We need to install the VirtIO drivers to get this machine onto the network. We have a disk image mounted with the driver installer so we need to navigate to that drive and launch the installer. Open Windows Explorer and locate the drive in the side bar. In my case, it’s the E: drive. Right-click on `virtio-win-guest-tools` and select “Install.”
+
+![../../_images/windowsExp.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EE6DD2F5-7B81-4697-8A32-4A04675D0EAC-high.png)
+
+Step through the installer. Simply click “Next” or “Install” through each step, there are no configuration changes needed. Once the installer has completed, click “Finish.” You can confirm we now have a network interface by opening a Command Prompt session and using the `ipconfig` command. One network adapter should be listed.
+
+![../../_images/showInterface.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-55CC0981-E007-492E-BFE7-373ADB87FE9D-high.png)
+
+We can now eject the two virtual disks, drives D: and E: in my case. Then, launch Windows Security so we can disable firewalls. Turn off firewall for domain, private network, and public network.
+
+![../../_images/winDefender.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DAA8652B-17E0-4AF2-9273-C548F0FA0614-high.png)
+
+Next, back in Command Prompt, run `winrm quickconfig` to configure `winrm`. Within `Services`, ensure that `winrm` (Windows Remote Management) is set to automatic on startup. Right-click on the Start button and select Run. Enter “sysprep” and click OK. In the Windows Explorer window that appears, right-click on `sysprep` and click “Run as Administrator”. Under “Shutdown Options”, choose Quit and click OK. If this is set to shutdown, HPE Morpheus Enterprise will simply restart the VM. Once this is completed, a new file `Sysprep_succeeded.tag` appears in Windows Explorer.
+
+![../../_images/sysprepComplete.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A11613FB-FC10-42BC-A6A3-3FB44D08260B-high.png)
+
+We’re now done configuring Windows and the console window can be closed. We’ll move on to creating a template from the VM we just configured. Begin by opening an SSH session into the HPE Morpheus Enterprise appliance server. Confirm `jq` is up to date on the appliance box (`apt install jq`). Then, go ahead and stop the running Windows VM. We can do this from the Instance detail page in HPE Morpheus Enterprise. Click ACTIONS and then “Stop Server.” Still on the Instance detail page, click ACTIONS and then “Import as Image.” This will perform a snapshot and create a new Virtual Image (Library > Virtual Images).
+
+![../../_images/importImage.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FBFB8AA8-171F-4668-BD6A-CAE4F5870AA8-high.png)
+
+The Virtual Image is not usable until it’s in an active status and the UI indication may display an active status even before it’s fully ready. If it’s “SAVING” or “QUEUED,” it is still being prepared and saved. To determine the current status of the Virtual Image, check with a call to HPE Morpheus Enterprise API like the one below. When the return output lists a status of “Active,” the image is ready to be provisioned from.
+
+```
+```
+curl -k --request GET --url https://xx.xx.xx.xx/api/virtual-images/<id>  
+--header 'accept: application/json' --header 'authorization: Bearer xxx-xxx-xxx-xxx-xxx' |  
+jq '.virtualImage.status'
+```
+```
+
+Once saved, additional configurations are needed on the Virtual Image in HPE Morpheus Enterprise. Edit the new Virtual Image and check the following configurations:
+
+- **MINIMUM MEMORY:** Set as appropriate
+- **SYSPREPPED/GENERALIZED IMAGE?:** Checked
+- **INSTALL AGENT?:** Checked
+- **USERNAME:** Remove if present
+- **PASSWORD:** Remove if present
+- **VIRTIO DRIVERS LOADED?:** Checked
+
+All other checkbox-type configurations not mentioned in the above list should be unchecked. Click SAVE CHANGES.
+
+At this point all image preparation steps are completed. HPE Morpheus Enterprise library items can now be created from this image by adding new Node Types, Layouts, and Instance Types. The complete steps for building a library item go beyond the scope of this particular guide but more detail on that process is available elsewhere in HPE Morpheus Enterprise UI documentation. Once the library items are created, new Instances may be provisioned complete with HPE Morpheus Enterprise Agent installed.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json b/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
new file mode 100644
index 0000000..f38b458
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+  "title": "Configuring Access with Clouds, Groups, and Roles",
+  "ordinal": 372,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Access with Clouds, Groups, and Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC",
+        "clustering_title": "Configuring Access with Clouds, Groups, and Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md b/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
new file mode 100644
index 0000000..732008a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.md
@@ -0,0 +1,55 @@
+# Configuring Access with Clouds, Groups, and Roles
+
+As you get started, it’s vital to understand constructs such as Clouds and Groups as they are implemented in HPE Morpheus Enterprise. Deploying an effective strategy for dividing organizational resources and people groups under these constructs will ensure all parties have convenient access to the resources they need. Map currently-existing strategies for splitting resources and controlling costs into HPE Morpheus Enterprise and your teams will have access only to resources allocated to their department.
+
+This guide discusses the constructs of Clouds, Groups, Roles, Users, and Policies while also presenting an example use case for allocating resources and distributing access under these umbrellas. We’ll end up with a permissions structure represented by the diagram below and step through each part of the implementation process.
+
+![../../_images/0permsDiagram.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DAC903C8-75F8-45F5-8C24-8217DDD1758F-high.png)
+
+## Clouds
+
+Clouds have broad meaning in HPE Morpheus Enterprise and can be integrations into public clouds, private clouds, or bare metal servers. You can read more about Clouds in HPE Morpheus Enterprise Docs [here](https://docs.morpheusdata.com/en/latest/infrastructure/clouds/clouds.html).
+
+In our example case, the organization has an Azure account and three separate departmental projects consolidated under separate resource groups. The HPE Morpheus Enterprise integration with Azure public cloud allows users to scope the Cloud to one specific resource group, if desired. We will do so in this case because it will allow us to restrict our users to the appropriate Azure resource groups in a later step. In the screenshot below, note how I am scoping the HPE Morpheus Enterprise Azure Cloud to a specific resource group when adding or editing the Cloud. This process will be repeated two additional times to create the three HPE Morpheus Enterprise Clouds we need. Complete details on integrating HPE Morpheus Enterprise with Azure public cloud are [here](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/azure/azure.html) in HPE Morpheus Enterprise Docs.
+
+![../../_images/1configCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-04D720D8-D7A9-44B8-8585-DBDEDD802C3D-high.png)
+
+## Groups
+
+[Groups](https://docs.morpheusdata.com/en/latest/infrastructure/groups/groups.html) in HPE Morpheus Enterprise allow administrators to determine which Clouds their users have access to. Part of defining a Role, which we’ll see in the next section, is selecting which Groups are associated with the Role. One or multiple Clouds are added to each Group and passed to users through their assigned Roles.
+
+When creating a Cloud, it must be added to a Group. Additionally, Clouds can be added to a Group at any time from the Clouds tab on the Group detail page (Infrastructure > Groups > Specific Group). In the example case diagrammed above, one Cloud (Azure cloud account scoped to a specific resource group) is associated with each Group but often Groups will contain many Clouds. In the screenshot below, I am adding an Azure Cloud to a Group that is currently empty.
+
+![../../_images/2addCloudToGroup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0AB9B625-EF46-4CA2-B797-B86D533F52B4-high.png)
+
+## Roles
+
+HPE Morpheus Enterprise Roles determine user access to many things, including application features, Groups, configured Instance Types, configured Blueprints, Personas, and Catalog Item configurations for the Service Catalog Persona. It’s important to note that a user can have multiple Roles and will take the most permissive rights across all of these Roles. In many cases, this greatly simplifies Role configuration for administrators as it prevents the need to create highly-specific individual Roles that can suit every case. To illustrate this for our example case, I will create a set of Roles to handle Group access for my users and another set of Roles to give access to the correct feature permissions.
+
+For this example case, I’ll start by creating one Role for each of the three Groups we created in the previous step. By default, a new Role will have all feature permissions set to “None” as shown below meaning we can skip directly to the Group Access tab.
+
+![../../_images/3roleFeatureAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E0F14807-7823-4651-8193-7E2F04ADC12E-high.png)
+
+On the Group Access tab, I will toggle the Global Access setting to Custom and give access only to one Group as shown in the next image. By doing this for each of our Groups created in the last section, we can easily control Group access for each user by applying one or more of our Group Roles to their user which we will do in the next section.
+
+![../../_images/4roleGroupAccess.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1F85B206-FDB4-478F-BCEC-96E7184EF31F-high.png)
+
+In addition to Roles for handling Group access, we need additional Role sets which will control our feature access. For example, we might have highly permissive feature access for administrators and more restrictive ones for developers or other users who have specific responsibilities requiring access to just a few specific areas of the UI. These additional Roles are created in the same way as the Group Roles we just created but all Group access will be set to “None” and the appropriate feature access will be configured on the “Feature Access” tab.
+
+## Users
+
+With the groundwork laid in the previous steps, we can easily configure permissions for any user accounts we might add to HPE Morpheus Enterprise. In the screenshot below, I’m adding a user account for a developer at my organization. I’ve applied one Role to handle correct Group access for this user and I’ve applied the “Developer” role to give only the feature access needed for this user to carry out his or her responsibilities.
+
+![../../_images/5newUser.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-295DFC03-0A0D-4350-B2DB-30692FE51851-high.png)
+
+## Policies
+
+One final consideration for this example case is policy application. HPE Morpheus Enterprise enables administrators to place fine-grained governance scoped to specific users, Roles, Groups, Clouds, Tenants, or globally. You can read more about policies in HPE Morpheus Enterprise docs [here](https://docs.morpheusdata.com/en/latest/administration/policies/policies.html) but we will also create some that apply to the example case discussed in this guide.
+
+Policies are created from the Administration menu in the Policies section. In the screenshot below, I’ve created a new policy and chosen to scope it to a Group. In this case, I’m creating a maximum VMs policy but there are many other types which are listed in our documentation linked above.
+
+![../../_images/6policies.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-21C24B9B-7C14-48A8-AB21-9D31F5DF44DC-high.png)
+
+## Conclusion
+
+At this point, we’ve completed implementation of the access structure. As new users are added, we can easily give them the Group and feature access they need. We can also easily add or edit the policies that are in place or add new Clouds and distribute access to existing users. The key is understanding the relationship between the HPE Morpheus Enterprise constructs discussed in this guide. Armed with that understanding, the example case presented here can be expanded to suit the needs of large-scale enterprise.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json b/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
new file mode 100644
index 0000000..6e2863c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+  "title": "Resources",
+  "ordinal": 214,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html",
+  "topic_cluster": {
+    "clustering_title": "Resources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE",
+        "clustering_title": "Resources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md b/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
new file mode 100644
index 0000000..ea6323f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.md
@@ -0,0 +1,1018 @@
+# Resources
+
+![../../_images/infra_compute_header_resources_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F4C1D71D-FBE1-47F2-A56D-36C1E419CA22-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: Resource Type Cloud
+
+Resources represent objects that do not map to VM or Container types in HPE Morpheus Enterprise, such as IAC resources from Terraform, Cloudformation or ARM Templates like VPC’s, Gateways, Users, Policies, Brokers, API’s, Endpoints, Directories, ACL’s, Routes… well anything really. All resources created from IAC Templates map to iac provider resource types and HPE Morpheus Enterprise maintains a resource object record from the mapped resource.
+
+Expand the **Resource Types** table below to see all Resource types that will be mapped to Resource objects in HPE Morpheus Enterprise:
+
+## Resource Types
+
+The following Resource Types are mapped when provisioning IAC templates including Terraform and CloudFormation templates.
+
+| ICON | RESOURCE NAME | PROVIDER | RESOURCE TYPE | MORPHEUS TYPE |
+| --- | --- | --- | --- | --- |
+| ../../_images/aws-resource.png | Accessanalyzer Analyzer | terraform | accessanalyzerAnalyzer | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate | terraform | acmCertificate | accountResource |
+| ../../_images/aws-resource.png | Acm Certificate Validation | terraform | acmCertificateValidation | accountResource |
+| ../../_images/aws-resource.png | Acmpca Certificate Authority | terraform | acmpcaCertificateAuthority | accountResource |
+| ../../_images/azure-securitycenter.png | Advanced Threat Protection | terraform | AdvancedThreatProtection | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api | cloudFormation | Api | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Authorizer | cloudFormation | Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Deployment | cloudFormation | Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Domain Name | cloudFormation | DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration | cloudFormation | Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Integration Response | cloudFormation | IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Mapping | cloudFormation | ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Model | cloudFormation | Model | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Route Response | cloudFormation | RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Amazon Api Stage | cloudFormation | Stage | accountResource |
+| ../../_images/aws-ec2.png | Ami | terraform | ami | accountResource |
+| ../../_images/aws-ec2.png | Ami Copy | terraform | amiCopy | accountResource |
+| ../../_images/aws-ec2.png | Ami From Instance | terraform | amiFromInstance | accountResource |
+| ../../_images/aws-ec2.png | Ami Launch Permission | terraform | amiLaunchPermission | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-analysis-services-resources.png | Analysis Server | terraform | AnalysisServer | accountResource |
+| ../../_images/azure-resource.png | API | terraform | API | accountResource |
+| ../../_images/azure-resource.png | API Authorization Server | terraform | APIAuthorizationServer | accountResource |
+| ../../_images/azure-resource.png | API Backend | terraform | APIBackend | accountResource |
+| ../../_images/azure-resource.png | API Certificate | terraform | APICertificate | accountResource |
+| ../../_images/azure-resource.png | API Diagnostic | terraform | APIDiagnostic | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Account | terraform | apiGatewayAccount | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Api Key | terraform | apiGatewayApiKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Authorizer | terraform | apiGatewayAuthorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Base Path Mapping | terraform | apiGatewayBasePathMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Client Certificate | terraform | apiGatewayClientCertificate | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Deployment | terraform | apiGatewayDeployment | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Part | terraform | apiGatewayDocumentationPart | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Documentation Version | terraform | apiGatewayDocumentationVersion | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Domain Name | terraform | apiGatewayDomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Gateway Response | terraform | apiGatewayGatewayResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration | terraform | apiGatewayIntegration | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Integration Response | terraform | apiGatewayIntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method | terraform | apiGatewayMethod | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Response | terraform | apiGatewayMethodResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Method Settings | terraform | apiGatewayMethodSettings | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Model | terraform | apiGatewayModel | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Request Validator | terraform | apiGatewayRequestValidator | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Resource | terraform | apiGatewayResource | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Rest Api | terraform | apiGatewayRestApi | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Stage | terraform | apiGatewayStage | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan | terraform | apiGatewayUsagePlan | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Usage Plan Key | terraform | apiGatewayUsagePlanKey | accountResource |
+| ../../_images/aws-api-gateway.png | Api Gateway Vpc Link | terraform | apiGatewayVpcLink | accountResource |
+| ../../_images/azure-resource.png | API Group | terraform | APIGroup | accountResource |
+| ../../_images/azure-resource.png | API Group User | terraform | APIGroupUser | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider AD | terraform | APIIdentityProviderAD | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Facebook | terraform | APIIdentityProviderFacebook | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Google | terraform | APIIdentityProviderGoogle | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Microsoft | terraform | APIIdentityProviderMicrosoft | accountResource |
+| ../../_images/azure-resource.png | API Identity Provider Twitter | terraform | APIIdentityProviderTwitter | accountResource |
+| ../../_images/azure-resource.png | API Logger | terraform | APILogger | accountResource |
+| ../../_images/azure-resource.png | API Management | terraform | APIManagement | accountResource |
+| ../../_images/azure-resource.png | API Named Value | terraform | APINamedValue | accountResource |
+| ../../_images/azure-resource.png | API OpenID Provider | terraform | APIOpenIDProvider | accountResource |
+| ../../_images/azure-resource.png | API Operation | terraform | APIOperation | accountResource |
+| ../../_images/azure-resource.png | API Operation Policy | terraform | APIOperationPolicy | accountResource |
+| ../../_images/azure-resource.png | API Policy | terraform | APIPolicy | accountResource |
+| ../../_images/azure-resource.png | API Product | terraform | APIProduct | accountResource |
+| ../../_images/azure-resource.png | API Product API | terraform | APIProductAPI | accountResource |
+| ../../_images/azure-resource.png | API Product Group | terraform | APIProductGroup | accountResource |
+| ../../_images/azure-resource.png | API Product Policy | terraform | APIProductPolicy | accountResource |
+| ../../_images/azure-resource.png | API Property | terraform | APIProperty | accountResource |
+| ../../_images/azure-resource.png | API Schema | terraform | APISchema | accountResource |
+| ../../_images/azure-resource.png | API Subscription | terraform | APISubscription | accountResource |
+| ../../_images/azure-resource.png | API User | terraform | APIUser | accountResource |
+| ../../_images/azure-resource.png | API Version Set | terraform | APIVersionSet | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api | terraform | apigatewayv2Api | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Api Mapping | terraform | apigatewayv2ApiMapping | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Authorizer | terraform | apigatewayv2Authorizer | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Deployment | terraform | apigatewayv2Deployment | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Domain Name | terraform | apigatewayv2DomainName | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration | terraform | apigatewayv2Integration | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Integration Response | terraform | apigatewayv2IntegrationResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Model | terraform | apigatewayv2Model | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route | terraform | apigatewayv2Route | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Route Response | terraform | apigatewayv2RouteResponse | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Stage | terraform | apigatewayv2Stage | accountResource |
+| ../../_images/aws-api-gateway.png | Apigatewayv2 Vpc Link | terraform | apigatewayv2VpcLink | accountResource |
+| ../../_images/azure-appconfiguration.png | App Configuration | terraform | AppConfiguration | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | App Cookie Stickiness Policy | terraform | appCookieStickinessPolicy | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Analytics Item | terraform | AppInsightsAnalyticsItem | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights API Key | terraform | AppInsightsAPIKey | accountResource |
+| ../../_images/azure-applicationinsights.png | App Insights Web Test | terraform | AppInsightsWebTest | accountResource |
+| ../../_images/azure-resource.png | App Service | terraform | AppService | accountResource |
+| ../../_images/azure-resource.png | App Service Active Slot | terraform | AppServiceActiveSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate | terraform | AppServiceCertificate | accountResource |
+| ../../_images/azure-resource.png | App Service Certificate Order | terraform | AppServiceCertificateOrder | accountResource |
+| ../../_images/azure-resource.png | App Service Environment | terraform | AppServiceEnvironment | accountResource |
+| ../../_images/azure-resource.png | App Service Host Binding | terraform | AppServiceHostBinding | accountResource |
+| ../../_images/azure-resource.png | App Service Network Swift Connection | terraform | AppServiceNetworkSwiftConnection | accountResource |
+| ../../_images/azure-resource.png | App Service Plan | terraform | AppServicePlan | accountResource |
+| ../../_images/azure-resource.png | App Service Slot | terraform | AppServiceSlot | accountResource |
+| ../../_images/azure-resource.png | App Service Source Control Token | terraform | AppServiceSourceControlToken | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Policy | terraform | appautoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Scheduled Action | terraform | appautoscalingScheduledAction | accountResource |
+| ../../_images/aws-autoscaling.png | Appautoscaling Target | terraform | appautoscalingTarget | accountResource |
+| ../../_images/azure-compute.png | Application Definition | terraform | ApplicationDefinition | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-network.png | Application Gateway | terraform | ApplicationGateway | accountResource |
+| ../../_images/azure-applicationinsights.png | Application Insights | terraform | ApplicationInsights | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Application Security Group | terraform | ApplicationSecurityGroup | accountResource |
+| ../../_images/aws-resource.png | Appmesh Mesh | terraform | appmeshMesh | accountResource |
+| ../../_images/aws-resource.png | Appmesh Route | terraform | appmeshRoute | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Node | terraform | appmeshVirtualNode | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Router | terraform | appmeshVirtualRouter | accountResource |
+| ../../_images/aws-resource.png | Appmesh Virtual Service | terraform | appmeshVirtualService | accountResource |
+| ../../_images/aws-appsync.png | Appsync Api Key | terraform | appsyncApiKey | accountResource |
+| ../../_images/aws-appsync.png | Appsync Datasource | terraform | appsyncDatasource | accountResource |
+| ../../_images/aws-appsync.png | Appsync Function | terraform | appsyncFunction | accountResource |
+| ../../_images/aws-appsync.png | Appsync Graphql Api | terraform | appsyncGraphqlApi | accountResource |
+| ../../_images/aws-appsync.png | Appsync Resolver | terraform | appsyncResolver | accountResource |
+| ../../_images/aws-athena.png | Athen Named Query | cloudFormation | NamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Database | terraform | athenaDatabase | accountResource |
+| ../../_images/aws-athena.png | Athena Named Query | terraform | athenaNamedQuery | accountResource |
+| ../../_images/aws-athena.png | Athena Workgroup | terraform | athenaWorkgroup | accountResource |
+| ../../_images/azure-automation.png | Automation Account | terraform | AutomationAccount | accountResource |
+| ../../_images/azure-automation.png | Automation Certificate | terraform | AutomationCertificate | accountResource |
+| ../../_images/azure-automation.png | Automation Credential | terraform | AutomationCredential | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Config | terraform | AutomationDSCConfig | accountResource |
+| ../../_images/azure-automation.png | Automation DSC Node Config | terraform | AutomationDSCNodeConfig | accountResource |
+| ../../_images/azure-automation.png | Automation Job Schedule | terraform | AutomationJobSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Module | terraform | AutomationModule | accountResource |
+| ../../_images/azure-automation.png | Automation Runbook | terraform | AutomationRunbook | accountResource |
+| ../../_images/azure-automation.png | Automation Schedule | terraform | AutomationSchedule | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Boolean | terraform | AutomationVariableBoolean | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Datetime | terraform | AutomationVariableDatetime | accountResource |
+| ../../_images/azure-automation.png | Automation Variable Int | terraform | AutomationVariableInt | accountResource |
+| ../../_images/azure-automation.png | Automation Variable String | terraform | AutomationVariableString | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Attachment | terraform | autoscalingAttachment | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Group | terraform | autoscalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Lifecycle Hook | terraform | autoscalingLifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Notification | terraform | autoscalingNotification | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Policy | terraform | autoscalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | Autoscaling Schedule | terraform | autoscalingSchedule | accountResource |
+| ../../_images/azure-compute.png | Availability Set | terraform | AvailabilitySet | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener | cloudFormation | Listener | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Certificate | cloudFormation | ListenerCertificate | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Listener Rule | cloudFormation | ListenerRule | accountResource |
+| ../../_images/aws-elb.png | AWS ALB Target Group | cloudFormation | TargetGroup | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh | cloudFormation | Mesh | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Node | cloudFormation | VirtualNode | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Router | cloudFormation | VirtualRouter | accountResource |
+| ../../_images/aws-app-mesh.png | AWS App Mesh Virtual Service | cloudFormation | VirtualService | accountResource |
+| ../../_images/aws-elb.png | AWS Application Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Group | cloudFormation | AutoScalingGroup | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Launch Configuration | cloudFormation | LaunchConfiguration | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Lifecycle Hook | cloudFormation | LifecycleHook | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Policy | cloudFormation | ScalingPolicy | accountResource |
+| ../../_images/aws-autoscaling.png | AWS Auto Scaling Scheduled Action | cloudFormation | ScheduledAction | accountResource |
+| ../../_images/aws-elb.png | AWS Elastic Load Balancer | cloudFormation | LoadBalancer | accountResource |
+| ../../_images/aws-elasticsearch-service.png | AWS Elasticsearch Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-sdb.png | AWS SDB Domain | cloudFormation | Domain | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Resource Policy | cloudFormation | ResourcePolicy | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Rotation Schedule | cloudFormation | RotationSchedule | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret | cloudFormation | Secret | accountResource |
+| ../../_images/aws-secrets-manager.png | AWS Secrets Manager Secret Target Attachment | cloudFormation | SecretTargetAttachment | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set | cloudFormation | ConfigurationSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Configuration Set Event Destination | cloudFormation | ConfigurationSetEventDestination | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Filter | cloudFormation | ReceiptFilter | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule | cloudFormation | ReceiptRule | accountResource |
+| ../../_images/aws-ses.png | AWS SES Receipt Rule Set | cloudFormation | ReceiptRuleSet | accountResource |
+| ../../_images/aws-ses.png | AWS SES Template | cloudFormation | Template | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Subscription | cloudFormation | Subscription | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic | cloudFormation | Topic | accountResource |
+| ../../_images/aws-sns.png | AWS SNS Topic Policy | cloudFormation | TopicPolicy | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue | cloudFormation | Queue | accountResource |
+| ../../_images/aws-sqs.png | AWS SQS Queue Policy | cloudFormation | QueuePolicy | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Byte Match Set | cloudFormation | ByteMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Geo Match Set | cloudFormation | GeoMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional IP Set | cloudFormation | IPSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rate Based Rule | cloudFormation | RateBasedRule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Regex Pattern Set | cloudFormation | RegexPatternSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Web ACL Association | cloudFormation | WebACLAssociation | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Regional Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Rule | cloudFormation | Rule | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Size Constraint Set | cloudFormation | SizeConstraintSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Sql Injection Match Set | cloudFormation | SqlInjectionMatchSet | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Web ACL | cloudFormation | WebACL | accountResource |
+| ../../_images/aws-waf.png | AWS WAF Xss Match Set | cloudFormation | XssMatchSet | accountResource |
+| ../../_images/aws-workspaces.png | AWS Workspace | cloudFormation | Workspace | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/azure-resource.png | Azure Resource | terraform | resource | accountResource |
+| ../../_images/aws-backup.png | Backup Plan | terraform | backupPlan | accountResource |
+| ../../_images/azure-backup.png | Backup Policy File Share | terraform | BackupPolicyFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Policy VM | terraform | BackupPolicyVM | accountResource |
+| ../../_images/azure-backup.png | Backup Protected File Share | terraform | BackupProtectedFileShare | accountResource |
+| ../../_images/azure-backup.png | Backup Protected VM | terraform | BackupProtectedVM | accountResource |
+| ../../_images/aws-backup.png | Backup Selection | terraform | backupSelection | accountResource |
+| ../../_images/azure-backup.png | Backup Storage Account | terraform | BackupStorageAccount | accountResource |
+| ../../_images/aws-backup.png | Backup Vault | terraform | backupVault | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-network.png | Bastion Host | terraform | BastionHost | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Account | terraform | BatchAccount | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Application | terraform | BatchApplication | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/azure-batch.png | Batch Certificate | terraform | BatchCertificate | accountResource |
+| ../../_images/aws-resource.png | Batch Compute Environment | terraform | batchComputeEnvironment | accountResource |
+| ../../_images/aws-resource.png | Batch Job Definition | terraform | batchJobDefinition | accountResource |
+| ../../_images/aws-resource.png | Batch Job Queue | terraform | batchJobQueue | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-batch.png | Batch Pool | terraform | BatchPool | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Email | terraform | BotChannelEmail | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel MS Teams | terraform | BotChannelMSTeams | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Registration | terraform | BotChannelRegistration | accountResource |
+| ../../_images/azure-bot.png | Bot Channel Slack | terraform | BotChannelSlack | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Connection | terraform | BotConnection | accountResource |
+| ../../_images/azure-bot.png | Bot Direct Line | terraform | BotDirectLine | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/azure-bot.png | Bot Web App | terraform | BotWebApp | accountResource |
+| ../../_images/aws-resource.png | Budgets Budget | terraform | budgetsBudget | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Endpoint | terraform | CDNEndpoint | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/azure-cdn.png | CDN Profile | terraform | CDNProfile | accountResource |
+| ../../_images/aws-resource.png | Cloud9 Environment Ec2 | terraform | cloud9EnvironmentEc2 | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack | terraform | cloudformationStack | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set | terraform | cloudformationStackSet | accountResource |
+| ../../_images/aws-cloudformation.png | Cloudformation Stack Set Instance | terraform | cloudformationStackSetInstance | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Distribution | terraform | cloudfrontDistribution | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Origin Access Identity | terraform | cloudfrontOriginAccessIdentity | accountResource |
+| ../../_images/aws-cloudfront.png | Cloudfront Public Key | terraform | cloudfrontPublicKey | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Cluster | terraform | cloudhsmV2Cluster | accountResource |
+| ../../_images/aws-resource.png | Cloudhsm V2 Hsm | terraform | cloudhsmV2Hsm | accountResource |
+| ../../_images/aws-cloudtrail.png | Cloudtrail | terraform | cloudtrail | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Dashboard | terraform | cloudwatchDashboard | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Permission | terraform | cloudwatchEventPermission | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Rule | terraform | cloudwatchEventRule | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Event Target | terraform | cloudwatchEventTarget | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination | terraform | cloudwatchLogDestination | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Destination Policy | terraform | cloudwatchLogDestinationPolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Group | terraform | cloudwatchLogGroup | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Metric Filter | terraform | cloudwatchLogMetricFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Resource Policy | terraform | cloudwatchLogResourcePolicy | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Stream | terraform | cloudwatchLogStream | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Log Subscription Filter | terraform | cloudwatchLogSubscriptionFilter | accountResource |
+| ../../_images/aws-cloudwatch.png | Cloudwatch Metric Alarm | terraform | cloudwatchMetricAlarm | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Project | terraform | codebuildProject | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Source Credential | terraform | codebuildSourceCredential | accountResource |
+| ../../_images/aws-codebuild.png | Codebuild Webhook | terraform | codebuildWebhook | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Repository | terraform | codecommitRepository | accountResource |
+| ../../_images/aws-codecommit.png | Codecommit Trigger | terraform | codecommitTrigger | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy App | terraform | codedeployApp | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Config | terraform | codedeployDeploymentConfig | accountResource |
+| ../../_images/aws-codedeploy.png | Codedeploy Deployment Group | terraform | codedeployDeploymentGroup | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline | terraform | codepipeline | accountResource |
+| ../../_images/aws-codepipeline.png | Codepipeline Webhook | terraform | codepipelineWebhook | accountResource |
+| ../../_images/aws-codestar.png | Codestarnotifications Notification Rule | terraform | codestarnotificationsNotificationRule | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/azure-cognitive-services.png | Cognitive Account | terraform | CognitiveAccount | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool | terraform | cognitoIdentityPool | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Pool Roles Attachment | terraform | cognitoIdentityPoolRolesAttachment | accountResource |
+| ../../_images/aws-resource.png | Cognito Identity Provider | terraform | cognitoIdentityProvider | accountResource |
+| ../../_images/aws-resource.png | Cognito Resource Server | terraform | cognitoResourceServer | accountResource |
+| ../../_images/aws-resource.png | Cognito User Group | terraform | cognitoUserGroup | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool | terraform | cognitoUserPool | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Client | terraform | cognitoUserPoolClient | accountResource |
+| ../../_images/aws-resource.png | Cognito User Pool Domain | terraform | cognitoUserPoolDomain | accountResource |
+| ../../_images/aws-resource.png | Config Aggregate Authorization | terraform | configAggregateAuthorization | accountResource |
+| ../../_images/aws-resource.png | Config Config Rule | terraform | configConfigRule | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Aggregator | terraform | configConfigurationAggregator | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder | terraform | configConfigurationRecorder | accountResource |
+| ../../_images/aws-resource.png | Config Configuration Recorder Status | terraform | configConfigurationRecorderStatus | accountResource |
+| ../../_images/aws-resource.png | Config Delivery Channel | terraform | configDeliveryChannel | accountResource |
+| ../../_images/aws-resource.png | Config Organization Custom Rule | terraform | configOrganizationCustomRule | accountResource |
+| ../../_images/aws-resource.png | Config Organization Managed Rule | terraform | configOrganizationManagedRule | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Group | terraform | ContainerGroup | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry | terraform | ContainerRegistry | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-container.png | Container Registry Webhook | terraform | ContainerRegistryWebhook | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Account | terraform | CosmosDBAccount | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Cassandra Keyspace | terraform | CosmosDBCassandraKeyspace | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Database | terraform | CosmosDBGremlinDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Gremlin Graph | terraform | CosmosDBGremlinGraph | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Collection | terraform | CosmosDBMongoCollection | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Mongo Database | terraform | CosmosDBMongoDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Container | terraform | CosmosDBSQLContainer | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB SQL Database | terraform | CosmosDBSQLDatabase | accountResource |
+| ../../_images/azure-cosmosdb.png | CosmosDB Table | terraform | CosmosDBTable | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/azure-cosmosdb.png | Cost Management Export Resource Group | terraform | CostManagementExportResourceGroup | accountResource |
+| ../../_images/aws-resource.png | Cur Report Definition | terraform | curReportDefinition | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/azure-custom.png | Custom Provider | terraform | CustomProvider | accountResource |
+| ../../_images/aws-vpc.png | Customer Gateway | terraform | customerGateway | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-portal.png | Dashboard | terraform | Dashboard | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory | terraform | DataFactory | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Data Lake Storage | terraform | DataFactoryDataLakeStorage | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Integration Runtime | terraform | DataFactoryIntegrationRuntime | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Dataset | terraform | DataFactoryMySQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory MySQL Link | terraform | DataFactoryMySQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Pipeline | terraform | DataFactoryPipeline | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Dataset | terraform | DataFactoryPostgreSQLDataset | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory PostgreSQL Link | terraform | DataFactoryPostgreSQLLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Link | terraform | DataFactorySQLServerLink | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory SQL Server Table | terraform | DataFactorySQLServerTable | accountResource |
+| ../../_images/azure-datafactory.png | Data Factory Trigger Schedule | terraform | DataFactoryTriggerSchedule | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Account | terraform | DataLakeAnalyticsAccount | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Analytics Firewall Rule | terraform | DataLakeAnalyticsFirewallRule | accountResource |
+| ../../_images/azure-storage.png | Data Lake Filesystem | terraform | DataLakeFilesystem | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store | terraform | DataLakeStore | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store File | terraform | DataLakeStoreFile | accountResource |
+| ../../_images/azure-datalake.png | Data Lake Store Firewall Rule | terraform | DataLakeStoreFirewallRule | accountResource |
+| ../../_images/azure-datashare.png | Data Share Account | terraform | DataShareAccount | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Project | terraform | DatabaseMigrationProject | accountResource |
+| ../../_images/azure-databasemigration.png | Database Migration Service | terraform | DatabaseMigrationService | accountResource |
+| ../../_images/azure-databricks.png | Databricks Workspace | terraform | DatabricksWorkspace | accountResource |
+| ../../_images/aws-resource.png | Datapipeline Pipeline | terraform | datapipelinePipeline | accountResource |
+| ../../_images/aws-resource.png | Datasync Agent | terraform | datasyncAgent | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Efs | terraform | datasyncLocationEfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Nfs | terraform | datasyncLocationNfs | accountResource |
+| ../../_images/aws-resource.png | Datasync Location S3 | terraform | datasyncLocationS3 | accountResource |
+| ../../_images/aws-resource.png | Datasync Location Smb | terraform | datasyncLocationSmb | accountResource |
+| ../../_images/aws-resource.png | Datasync Task | terraform | datasyncTask | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Cluster | terraform | daxCluster | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Parameter Group | terraform | daxParameterGroup | accountResource |
+| ../../_images/aws-dynamodb.png | Dax Subnet Group | terraform | daxSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | Db Cluster Snapshot | terraform | dbClusterSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Event Subscription | terraform | dbEventSubscription | accountResource |
+| ../../_images/aws-rds.png | Db Instance | terraform | dbInstance | accountResource |
+| ../../_images/aws-rds.png | Db Instance Role Association | terraform | dbInstanceRoleAssociation | accountResource |
+| ../../_images/aws-rds.png | Db Option Group | terraform | dbOptionGroup | accountResource |
+| ../../_images/aws-rds.png | Db Parameter Group | terraform | dbParameterGroup | accountResource |
+| ../../_images/aws-rds.png | Db Security Group | terraform | dbSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | Db Snapshot | terraform | dbSnapshot | accountResource |
+| ../../_images/aws-rds.png | Db Subnet Group | terraform | dbSubnetGroup | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host | terraform | DedicatedHost | accountResource |
+| ../../_images/azure-compute.png | Dedicated Host Group | terraform | DedicatedHostGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Network Acl | terraform | defaultNetworkAcl | accountResource |
+| ../../_images/aws-vpc.png | Default Route Table | terraform | defaultRouteTable | accountResource |
+| ../../_images/aws-vpc.png | Default Security Group | terraform | defaultSecurityGroup | accountResource |
+| ../../_images/aws-vpc.png | Default Subnet | terraform | defaultSubnet | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc | terraform | defaultVpc | accountResource |
+| ../../_images/aws-vpc.png | Default Vpc Dhcp Options | terraform | defaultVpcDhcpOptions | accountResource |
+| ../../_images/aws-resource.png | Devicefarm Project | terraform | devicefarmProject | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-dev-space.png | DevSpace Controller | terraform | DevSpaceController | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Lab | terraform | DevTestLab | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Linux Vm | terraform | DevTestLinuxVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Policy | terraform | DevTestPolicy | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Schedule | terraform | DevTestSchedule | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Virtual Network | terraform | DevTestVirtualNetwork | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/azure-devtest.png | DevTest Windows Vm | terraform | DevTestWindowsVm | accountResource |
+| ../../_images/aws-resource.png | Directory Service Conditional Forwarder | terraform | directoryServiceConditionalForwarder | accountResource |
+| ../../_images/aws-resource.png | Directory Service Directory | terraform | directoryServiceDirectory | accountResource |
+| ../../_images/aws-resource.png | Directory Service Log Subscription | terraform | directoryServiceLogSubscription | accountResource |
+| ../../_images/azure-compute.png | Disk Encryption Set | terraform | DiskEncryptionSet | accountResource |
+| ../../_images/aws-resource.png | Dlm Lifecycle Policy | terraform | dlmLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Dms Certificate | terraform | dmsCertificate | accountResource |
+| ../../_images/aws-resource.png | Dms Endpoint | terraform | dmsEndpoint | accountResource |
+| ../../_images/aws-resource.png | Dms Event Subscription | terraform | dmsEventSubscription | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Instance | terraform | dmsReplicationInstance | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Subnet Group | terraform | dmsReplicationSubnetGroup | accountResource |
+| ../../_images/aws-resource.png | Dms Replication Task | terraform | dmsReplicationTask | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS A Record | terraform | DNSARecord | accountResource |
+| ../../_images/azure-dns.png | DNS AAAA Record | terraform | DNSAAAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CAA Record | terraform | DNSCAARecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS CName Record | terraform | DNSCNameRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS MX Record | terraform | DNSMXRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS NS Record | terraform | DNSNSRecord | accountResource |
+| ../../_images/azure-dns.png | DNS PTR Record | terraform | DNSPTRRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS SRV Record | terraform | DNSSRVRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Txt Record | terraform | DNSTxtRecord | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/azure-dns.png | DNS Zone | terraform | DNSZone | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster | terraform | docdbCluster | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Instance | terraform | docdbClusterInstance | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Parameter Group | terraform | docdbClusterParameterGroup | accountResource |
+| ../../_images/aws-resource.png | Docdb Cluster Snapshot | terraform | docdbClusterSnapshot | accountResource |
+| ../../_images/aws-resource.png | Docdb Subnet Group | terraform | docdbSubnetGroup | accountResource |
+| ../../_images/aws-directconnect.png | Dx Bgp Peer | terraform | dxBgpPeer | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection | terraform | dxConnection | accountResource |
+| ../../_images/aws-directconnect.png | Dx Connection Association | terraform | dxConnectionAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway | terraform | dxGateway | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association | terraform | dxGatewayAssociation | accountResource |
+| ../../_images/aws-directconnect.png | Dx Gateway Association Proposal | terraform | dxGatewayAssociationProposal | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface | terraform | dxHostedPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Private Virtual Interface Accepter | terraform | dxHostedPrivateVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface | terraform | dxHostedPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Public Virtual Interface Accepter | terraform | dxHostedPublicVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface | terraform | dxHostedTransitVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Hosted Transit Virtual Interface Accepter | terraform | dxHostedTransitVirtualInterfaceAccepter | accountResource |
+| ../../_images/aws-directconnect.png | Dx Lag | terraform | dxLag | accountResource |
+| ../../_images/aws-directconnect.png | Dx Private Virtual Interface | terraform | dxPrivateVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Public Virtual Interface | terraform | dxPublicVirtualInterface | accountResource |
+| ../../_images/aws-directconnect.png | Dx Transit Virtual Interface | terraform | dxTransitVirtualInterface | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Global Table | terraform | dynamodbGlobalTable | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table | terraform | dynamodbTable | accountResource |
+| ../../_images/aws-dynamodb.png | DynamoDB Table | cloudFormation | Table | accountResource |
+| ../../_images/aws-dynamodb.png | Dynamodb Table Item | terraform | dynamodbTableItem | accountResource |
+| ../../_images/aws-ec2.png | Ebs Default Kms Key | terraform | ebsDefaultKmsKey | accountResource |
+| ../../_images/aws-ec2.png | Ebs Encryption By Default | terraform | ebsEncryptionByDefault | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot | terraform | ebsSnapshot | accountResource |
+| ../../_images/aws-ec2.png | Ebs Snapshot Copy | terraform | ebsSnapshotCopy | accountResource |
+| ../../_images/aws-ec2.png | Ebs Volume | terraform | ebsVolume | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Availability Zone Group | terraform | ec2AvailabilityZoneGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Capacity Reservation | cloudFormation | CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Capacity Reservation | terraform | ec2CapacityReservation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Authorization Rule | cloudFormation | ClientVpnAuthorizationRule | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Endpoint | cloudFormation | ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Endpoint | terraform | ec2ClientVpnEndpoint | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Client Vpn Network Association | terraform | ec2ClientVpnNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Route | cloudFormation | ClientVpnRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Client Vpn Target Network Association | cloudFormation | ClientVpnTargetNetworkAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Customer Gateway | cloudFormation | CustomerGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 DHCP Options | cloudFormation | DHCPOptions | accountResource |
+| ../../_images/aws-ec2.png | EC2 Egress Only Internet Gateway | cloudFormation | EgressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP | cloudFormation | EIP | accountResource |
+| ../../_images/aws-ec2.png | EC2 EIP Association | cloudFormation | EIPAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Fleet | cloudFormation | EC2Fleet | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Fleet | terraform | ec2Fleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Flow Log | cloudFormation | FlowLog | accountResource |
+| ../../_images/aws-ec2.png | EC2 Host | cloudFormation | Host | accountResource |
+| ../../_images/aws-ec2.png | EC2 Instance | cloudFormation | Instance | instance |
+| ../../_images/aws-ec2.png | EC2 Internet Gateway | cloudFormation | InternetGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Launch Template | cloudFormation | LaunchTemplate | accountResource |
+| ../../_images/aws-ec2.png | EC2 Nat Gateway | cloudFormation | NatGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl | cloudFormation | NetworkAcl | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Acl Entry | cloudFormation | NetworkAclEntry | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface | cloudFormation | NetworkInterface | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Attachment | cloudFormation | NetworkInterfaceAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Network Interface Permission | cloudFormation | NetworkInterfacePermission | accountResource |
+| ../../_images/aws-ec2.png | EC2 Placement Group | cloudFormation | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route | cloudFormation | Route | accountResource |
+| ../../_images/aws-ec2.png | EC2 Route Table | cloudFormation | RouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Egress | cloudFormation | SecurityGroupEgress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-ec2.png | EC2 Spot Fleet | cloudFormation | SpotFleet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet | cloudFormation | Subnet | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Cidr Block | cloudFormation | SubnetCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Network Acl Association | cloudFormation | SubnetNetworkAclAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Subnet Route Table Association | cloudFormation | SubnetRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter | terraform | ec2TrafficMirrorFilter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Filter Rule | terraform | ec2TrafficMirrorFilterRule | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Session | terraform | ec2TrafficMirrorSession | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Traffic Mirror Target | terraform | ec2TrafficMirrorTarget | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway | terraform | ec2TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway | cloudFormation | TransitGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Attachment | cloudFormation | TransitGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment | terraform | ec2TransitGatewayPeeringAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Peering Attachment Accepter | terraform | ec2TransitGatewayPeeringAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route | terraform | ec2TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route | cloudFormation | TransitGatewayRoute | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table | terraform | ec2TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table | cloudFormation | TransitGatewayRouteTable | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Association | terraform | ec2TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Association | cloudFormation | TransitGatewayRouteTableAssociation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Route Table Propagation | terraform | ec2TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway Route Table Propagation | cloudFormation | TransitGatewayRouteTablePropagation | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment | terraform | ec2TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 Transit Gateway VPC Attachment | cloudFormation | TransitGatewayVpcAttachment | accountResource |
+| ../../_images/aws-ec2.png | Ec2 Transit Gateway Vpc Attachment Accepter | terraform | ec2TransitGatewayVpcAttachmentAccepter | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume | cloudFormation | Volume | accountResource |
+| ../../_images/aws-ec2.png | EC2 Volume Attachment | cloudFormation | VolumeAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC | cloudFormation | VPC | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Cidr Block | cloudFormation | VPCCidrBlock | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC DHCP Options Association | cloudFormation | VPCDHCPOptionsAssociation | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint | cloudFormation | VPCEndpoint | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Connection Notification | cloudFormation | VPCEndpointConnectionNotification | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service | cloudFormation | VPCEndpointService | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Endpoint Service Permissions | cloudFormation | VPCEndpointServicePermissions | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Gateway Attachment | cloudFormation | VPCGatewayAttachment | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPC Peering Connection | cloudFormation | VPCPeeringConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection | cloudFormation | VPNConnection | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Connection Route | cloudFormation | VPNConnectionRoute | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway | cloudFormation | VPNGateway | accountResource |
+| ../../_images/aws-ec2.png | EC2 VPN Gateway Route Propagation | cloudFormation | VPNGatewayRoutePropagation | accountResource |
+| ../../_images/aws-resource.png | Ecr Lifecycle Policy | terraform | ecrLifecyclePolicy | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository | terraform | ecrRepository | accountResource |
+| ../../_images/aws-resource.png | Ecr Repository Policy | terraform | ecrRepositoryPolicy | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Capacity Provider | terraform | ecsCapacityProvider | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Cluster | terraform | ecsCluster | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Service | terraform | ecsService | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Service | cloudFormation | Service | accountResource |
+| ../../_images/aws-elastic-container-service.png | Ecs Task Definition | terraform | ecsTaskDefinition | accountResource |
+| ../../_images/aws-elastic-container-service.png | ECS Task Definition | cloudFormation | TaskDefinition | accountResource |
+| ../../_images/aws-efs.png | Efs File System | terraform | efsFileSystem | accountResource |
+| ../../_images/aws-efs.png | EFS FileSystem | cloudFormation | FileSystem | accountResource |
+| ../../_images/aws-efs.png | Efs Mount Target | terraform | efsMountTarget | accountResource |
+| ../../_images/aws-efs.png | EFS Mount Target | cloudFormation | MountTarget | accountResource |
+| ../../_images/aws-vpc.png | Egress Only Internet Gateway | terraform | egressOnlyInternetGateway | accountResource |
+| ../../_images/aws-ec2.png | Eip | terraform | eip | accountResource |
+| ../../_images/aws-ec2.png | Eip Association | terraform | eipAssociation | accountResource |
+| ../../_images/aws-eks.png | EKS Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-eks.png | Eks Cluster | terraform | eksCluster | accountResource |
+| ../../_images/aws-eks.png | Eks Fargate Profile | terraform | eksFargateProfile | accountResource |
+| ../../_images/aws-eks.png | Eks Node Group | terraform | eksNodeGroup | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | cloudFormation | Application | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application | terraform | elasticBeanstalkApplication | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | cloudFormation | ApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Application Version | terraform | elasticBeanstalkApplicationVersion | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | cloudFormation | ConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Configuration Template | terraform | elasticBeanstalkConfigurationTemplate | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | terraform | elasticBeanstalkEnvironment | accountResource |
+| ../../_images/aws-elastic-beanstalk.png | Elastic Beanstalk Environment | cloudFormation | Environment | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Cluster | cloudFormation | CacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Cluster | terraform | elasticacheCluster | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Parameter Group | terraform | elasticacheParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Parameter Group | cloudFormation | ParameterGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Replication Group | terraform | elasticacheReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Replication Group | cloudFormation | ReplicationGroup | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Security Group | terraform | elasticacheSecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group | cloudFormation | SecurityGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Security Group Ingress | cloudFormation | SecurityGroupIngress | accountResource |
+| ../../_images/aws-elasticache.png | Elasticache Subnet Group | terraform | elasticacheSubnetGroup | accountResource |
+| ../../_images/aws-elasticache.png | ElastiCache Subnet Group | cloudFormation | SubnetGroup | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain | terraform | elasticsearchDomain | accountResource |
+| ../../_images/aws-elasticsearch-service.png | Elasticsearch Domain Policy | terraform | elasticsearchDomainPolicy | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Pipeline | terraform | elastictranscoderPipeline | accountResource |
+| ../../_images/aws-resource.png | Elastictranscoder Preset | terraform | elastictranscoderPreset | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb | terraform | elb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Elb Attachment | terraform | elbAttachment | accountResource |
+| ../../_images/aws-emr.png | EMR Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-emr.png | Emr Cluster | terraform | emrCluster | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Fleet Config | cloudFormation | InstanceFleetConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Instance Group | terraform | emrInstanceGroup | accountResource |
+| ../../_images/aws-emr.png | EMR Instance Group Config | cloudFormation | InstanceGroupConfig | accountResource |
+| ../../_images/aws-emr.png | Emr Security Configuration | terraform | emrSecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Security Configuration | cloudFormation | SecurityConfiguration | accountResource |
+| ../../_images/aws-emr.png | EMR Step | cloudFormation | Step | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Domain | terraform | EventGridDomain | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Event Subscription | terraform | EventGridEventSubscription | accountResource |
+| ../../_images/azure-messaging.png | Event Grid Topic | terraform | EventGridTopic | accountResource |
+| ../../_images/azure-messaging.png | Event Hub | terraform | EventHub | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Authorization Rule | terraform | EventHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Consumer Group | terraform | EventHubConsumerGroup | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Disaster Recovery Config | terraform | EventHubDisasterRecoveryConfig | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace | terraform | EventHubNamespace | accountResource |
+| ../../_images/azure-messaging.png | Event Hub Namespace Authorization Rule | terraform | EventHubNamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit | terraform | ExpressRouteCircuit | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Authorization | terraform | ExpressRouteCircuitAuthorization | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Circuit Peering | terraform | ExpressRouteCircuitPeering | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Express Route Gateway | terraform | ExpressRouteGateway | accountResource |
+| ../../_images/azure-network.png | Firewall | terraform | Firewall | accountResource |
+| ../../_images/azure-network.png | Firewall Application Rule Collection | terraform | FirewallApplicationRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Nat Rule Collection | terraform | FirewallNatRuleCollection | accountResource |
+| ../../_images/azure-network.png | Firewall Network Rule Collection | terraform | FirewallNetworkRuleCollection | accountResource |
+| ../../_images/aws-vpc.png | Flow Log | terraform | flowLog | accountResource |
+| ../../_images/aws-resource.png | Fms Admin Account | terraform | fmsAdminAccount | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door | terraform | FrontDoor | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/azure-frontdoor.png | Front Door Firewall Policy | terraform | FrontDoorFirewallPolicy | accountResource |
+| ../../_images/aws-fsx.png | Fsx Lustre File System | terraform | fsxLustreFileSystem | accountResource |
+| ../../_images/aws-fsx.png | Fsx Windows File System | terraform | fsxWindowsFileSystem | accountResource |
+| ../../_images/azure-resource.png | Function App | terraform | FunctionApp | accountResource |
+| ../../_images/azure-resource.png | Function App Slot | terraform | FunctionAppSlot | accountResource |
+| ../../_images/aws-resource.png | Gamelift Alias | terraform | gameliftAlias | accountResource |
+| ../../_images/aws-resource.png | Gamelift Build | terraform | gameliftBuild | accountResource |
+| ../../_images/aws-resource.png | Gamelift Fleet | terraform | gameliftFleet | accountResource |
+| ../../_images/aws-resource.png | Gamelift Game Session Queue | terraform | gameliftGameSessionQueue | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault | terraform | glacierVault | accountResource |
+| ../../_images/aws-s3-glacier.png | Glacier Vault Lock | terraform | glacierVaultLock | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Accelerator | terraform | globalacceleratorAccelerator | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Endpoint Group | terraform | globalacceleratorEndpointGroup | accountResource |
+| ../../_images/aws-resource.png | Globalaccelerator Listener | terraform | globalacceleratorListener | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Database | terraform | glueCatalogDatabase | accountResource |
+| ../../_images/aws-glue.png | Glue Catalog Table | terraform | glueCatalogTable | accountResource |
+| ../../_images/aws-glue.png | Glue Classifier | terraform | glueClassifier | accountResource |
+| ../../_images/aws-glue.png | Glue Connection | terraform | glueConnection | accountResource |
+| ../../_images/aws-glue.png | Glue Crawler | terraform | glueCrawler | accountResource |
+| ../../_images/aws-glue.png | Glue Job | terraform | glueJob | accountResource |
+| ../../_images/aws-glue.png | Glue Security Configuration | terraform | glueSecurityConfiguration | accountResource |
+| ../../_images/aws-glue.png | Glue Trigger | terraform | glueTrigger | accountResource |
+| ../../_images/aws-glue.png | Glue Workflow | terraform | glueWorkflow | accountResource |
+| ../../_images/aws-resource.png | Guardduty Detector | terraform | guarddutyDetector | accountResource |
+| ../../_images/aws-resource.png | Guardduty Invite Accepter | terraform | guarddutyInviteAccepter | accountResource |
+| ../../_images/aws-resource.png | Guardduty Ipset | terraform | guarddutyIpset | accountResource |
+| ../../_images/aws-resource.png | Guardduty Member | terraform | guarddutyMember | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Admin Account | terraform | guarddutyOrganizationAdminAccount | accountResource |
+| ../../_images/aws-resource.png | Guardduty Organization Configuration | terraform | guarddutyOrganizationConfiguration | accountResource |
+| ../../_images/aws-resource.png | Guardduty Threatintelset | terraform | guarddutyThreatintelset | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Hadoop Cluster | terraform | HDInsightHadoopCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight HBase Cluster | terraform | HDInsightHBaseCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Kafka Cluster | terraform | HDInsightKafkaCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight ML Services Cluster | terraform | HDInsightMLServicesCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Query Cluster | terraform | HDInsightQueryCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight R Cluster | terraform | HDInsightRCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Spark Cluster | terraform | HDInsightSparkCluster | accountResource |
+| ../../_images/azure-hd-insight.png | HD Insight Storm Cluster | terraform | HDInsightStormCluster | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-healthcare-api.png | Healthcare Service | terraform | HealthcareService | accountResource |
+| ../../_images/azure-storage.png | HPC Cache | terraform | HPCCache | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache Blob Target | terraform | HPCCacheBlobTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/azure-storage.png | HPC Cache NFS Target | terraform | HPCCacheNFSTarget | accountResource |
+| ../../_images/aws-iam.png | IAM Access Key | cloudFormation | AccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Access Key | terraform | iamAccessKey | accountResource |
+| ../../_images/aws-resource.png | Iam Account Alias | terraform | iamAccountAlias | accountResource |
+| ../../_images/aws-resource.png | Iam Account Password Policy | terraform | iamAccountPasswordPolicy | accountResource |
+| ../../_images/aws-iam.png | IAM Group | cloudFormation | Group | accountResource |
+| ../../_images/aws-resource.png | Iam Group | terraform | iamGroup | accountResource |
+| ../../_images/aws-resource.png | Iam Group Membership | terraform | iamGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy | terraform | iamGroupPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Group Policy Attachment | terraform | iamGroupPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Instance Profile | terraform | iamInstanceProfile | accountResource |
+| ../../_images/aws-resource.png | IAM Instance Profile | cloudFormation | InstanceProfile | accountResource |
+| ../../_images/aws-iam.png | IAM Managed Policy | cloudFormation | ManagedPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Openid Connect Provider | terraform | iamOpenidConnectProvider | accountResource |
+| ../../_images/aws-iam.png | Iam Policy | terraform | iamPolicy | accountResource |
+| ../../_images/aws-resource.png | IAM Policy | cloudFormation | Policy | accountResource |
+| ../../_images/aws-resource.png | Iam Policy Attachment | terraform | iamPolicyAttachment | accountResource |
+| ../../_images/aws-iam.png | Iam Role | terraform | iamRole | accountResource |
+| ../../_images/aws-resource.png | IAM Role | cloudFormation | Role | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy | terraform | iamRolePolicy | accountResource |
+| ../../_images/aws-resource.png | Iam Role Policy Attachment | terraform | iamRolePolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam Saml Provider | terraform | iamSamlProvider | accountResource |
+| ../../_images/aws-resource.png | Iam Server Certificate | terraform | iamServerCertificate | accountResource |
+| ../../_images/aws-iam.png | Iam Service Linked Role | terraform | iamServiceLinkedRole | accountResource |
+| ../../_images/aws-resource.png | IAM Service Linked Role | cloudFormation | ServiceLinkedRole | accountResource |
+| ../../_images/aws-iam.png | Iam User | terraform | iamUser | accountResource |
+| ../../_images/aws-resource.png | IAM User | cloudFormation | User | accountResource |
+| ../../_images/aws-iam.png | IAM User Group Addition | cloudFormation | UserToGroupAddition | accountResource |
+| ../../_images/aws-resource.png | Iam User Group Membership | terraform | iamUserGroupMembership | accountResource |
+| ../../_images/aws-resource.png | Iam User Login Profile | terraform | iamUserLoginProfile | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy | terraform | iamUserPolicy | accountResource |
+| ../../_images/aws-resource.png | Iam User Policy Attachment | terraform | iamUserPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iam User Ssh Key | terraform | iamUserSshKey | accountResource |
+| ../../_images/azure-compute.png | Image | terraform | Image | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Target | terraform | inspectorAssessmentTarget | accountResource |
+| ../../_images/aws-resource.png | Inspector Assessment Template | terraform | inspectorAssessmentTemplate | accountResource |
+| ../../_images/aws-resource.png | Inspector Resource Group | terraform | inspectorResourceGroup | accountResource |
+| ../../_images/aws-ec2.png | Instance | terraform | Instance | instance |
+| ../../_images/aws-vpc.png | Internet Gateway | terraform | internetGateway | accountResource |
+| ../../_images/azure-iot-central-application.png | IOT Central Application | terraform | IOTCentralApplication | accountResource |
+| ../../_images/aws-resource.png | Iot Certificate | terraform | iotCertificate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub | terraform | IOTHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Access Policy | terraform | IOTHubAccessPolicy | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Consumer Group | terraform | IOTHubConsumerGroup | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS | terraform | IOTHubDPS | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub DPS Certficiate | terraform | IOTHubDPSCertficiate | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Event Hub | terraform | IOTHubEndpointEventHub | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Queue | terraform | IOTHubEndpointQueue | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Storage | terraform | IOTHubEndpointStorage | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Endpoint Topic | terraform | IOTHubEndpointTopic | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Fallback Route | terraform | IOTHubFallbackRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Route | terraform | IOTHubRoute | accountResource |
+| ../../_images/azure-iot-hub.png | IOT Hub Shared Access Policy | terraform | IOTHubSharedAccessPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy | terraform | iotPolicy | accountResource |
+| ../../_images/aws-resource.png | Iot Policy Attachment | terraform | iotPolicyAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Role Alias | terraform | iotRoleAlias | accountResource |
+| ../../_images/aws-resource.png | Iot Thing | terraform | iotThing | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Principal Attachment | terraform | iotThingPrincipalAttachment | accountResource |
+| ../../_images/aws-resource.png | Iot Thing Type | terraform | iotThingType | accountResource |
+| ../../_images/aws-resource.png | Iot Topic Rule | terraform | iotTopicRule | accountResource |
+| ../../_images/aws-ec2.png | Key Pair | terraform | keyPair | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault | terraform | KeyVault | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Access Policy | terraform | KeyVaultAccessPolicy | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Certificate | terraform | KeyVaultCertificate | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Key | terraform | KeyVaultKey | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/azure-key-vault.png | Key Vault Secret | terraform | KeyVaultSecret | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Analytics Application | terraform | kinesisAnalyticsApplication | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Firehose Delivery Stream | terraform | kinesisFirehoseDeliveryStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | terraform | kinesisStream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream | cloudFormation | Stream | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Stream Consumer | cloudFormation | StreamConsumer | accountResource |
+| ../../_images/aws-kinesis.png | Kinesis Video Stream | terraform | kinesisVideoStream | accountResource |
+| ../../_images/aws-resource.png | Kms Alias | terraform | kmsAlias | accountResource |
+| ../../_images/aws-resource.png | Kms Ciphertext | terraform | kmsCiphertext | accountResource |
+| ../../_images/aws-resource.png | Kms External Key | terraform | kmsExternalKey | accountResource |
+| ../../_images/aws-resource.png | Kms Grant | terraform | kmsGrant | accountResource |
+| ../../_images/aws-resource.png | Kms Key | terraform | kmsKey | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Cluster | terraform | KubernetesCluster | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-container.png | Kubernetes Node Pool | terraform | KubernetesNodePool | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Cluster | terraform | KustoCluster | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database | terraform | KustoDatabase | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Database Principal | terraform | KustoDatabasePrincipal | accountResource |
+| ../../_images/azure-dataexplorer.png | Kusto Event Data Connection | terraform | KustoEventDataConnection | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | cloudFormation | Alias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Alias | terraform | lambdaAlias | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | cloudFormation | EventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Event Source Mapping | terraform | lambdaEventSourceMapping | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | cloudFormation | Function | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function | terraform | lambdaFunction | accountResource |
+| ../../_images/aws-lambda.png | Lambda Function Event Invoke Config | terraform | lambdaFunctionEventInvokeConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | terraform | lambdaLayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version | cloudFormation | LayerVersion | accountResource |
+| ../../_images/aws-lambda.png | Lambda Layer Version Permission | cloudFormation | LayerVersionPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | terraform | lambdaPermission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Permission | cloudFormation | Permission | accountResource |
+| ../../_images/aws-lambda.png | Lambda Provisioned Concurrency Config | terraform | lambdaProvisionedConcurrencyConfig | accountResource |
+| ../../_images/aws-lambda.png | Lambda Version | cloudFormation | Version | accountResource |
+| ../../_images/aws-ec2.png | Launch Configuration | terraform | launchConfiguration | accountResource |
+| ../../_images/aws-ec2.png | Launch Template | terraform | launchTemplate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb | terraform | lb | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Cookie Stickiness Policy | terraform | lbCookieStickinessPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener | terraform | lbListener | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Certificate | terraform | lbListenerCertificate | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Listener Rule | terraform | lbListenerRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Ssl Negotiation Policy | terraform | lbSslNegotiationPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group | terraform | lbTargetGroup | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Lb Target Group Attachment | terraform | lbTargetGroupAttachment | accountResource |
+| ../../_images/aws-resource.png | Licensemanager Association | terraform | licensemanagerAssociation | accountResource |
+| ../../_images/aws-resource.png | Licensemanager License Configuration | terraform | licensemanagerLicenseConfiguration | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Domain | terraform | lightsailDomain | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Instance | terraform | lightsailInstance | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Key Pair | terraform | lightsailKeyPair | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip | terraform | lightsailStaticIp | accountResource |
+| ../../_images/aws-amazon-lightsail.png | Lightsail Static Ip Attachment | terraform | lightsailStaticIpAttachment | accountResource |
+| ../../_images/azure-compute.png | Linux VM Scale Set | terraform | LinuxVMScaleSet | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer | terraform | LoadBalancer | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Address Pool | terraform | LoadBalancerAddressPool | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Backend Server Policy | terraform | loadBalancerBackendServerPolicy | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Listener Policy | terraform | loadBalancerListenerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Pool | terraform | LoadBalancerNatPool | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Nat Rule | terraform | LoadBalancerNatRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Outbound Rule | terraform | LoadBalancerOutboundRule | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Load Balancer Policy | terraform | loadBalancerPolicy | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Probe | terraform | LoadBalancerProbe | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-loadbalancer.png | Load Balancer Rule | terraform | LoadBalancerRule | accountResource |
+| ../../_images/azure-network.png | Local Network Gateway | terraform | LocalNetworkGateway | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Linked Service | terraform | LogAnalyticsLinkedService | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Solution | terraform | LogAnalyticsSolution | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Event | terraform | LogAnalyticsWindowsEvent | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Windows Performance Counter | terraform | LogAnalyticsWindowsPerformanceCounter | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-log-analytics.png | Log Analytics Workspace | terraform | LogAnalyticsWorkspace | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Action | terraform | LogicAppCustomAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Custom Trigger | terraform | LogicAppCustomTrigger | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Action | terraform | LogicAppHttpAction | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Http Request | terraform | LogicAppHttpRequest | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Trigger Recurrence | terraform | LogicAppTriggerRecurrence | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-logicapp.png | Logic App Workflow | terraform | LogicAppWorkflow | accountResource |
+| ../../_images/azure-machinelearning.png | Machine Learning Workspace | terraform | MachineLearningWorkspace | accountResource |
+| ../../_images/aws-resource.png | Macie Member Account Association | terraform | macieMemberAccountAssociation | accountResource |
+| ../../_images/aws-resource.png | Macie S3 Bucket Association | terraform | macieS3BucketAssociation | accountResource |
+| ../../_images/aws-vpc.png | Main Route Table Association | terraform | mainRouteTableAssociation | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-maintenance.png | Maitenance Configuration | terraform | MaitenanceConfiguration | accountResource |
+| ../../_images/azure-compute.png | Managed Application | terraform | ManagedApplication | accountResource |
+| ../../_images/azure-compute.png | Managed Disk | terraform | ManagedDisk | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Group | terraform | ManagementGroup | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-management.png | Management Lock | terraform | ManagementLock | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-maps.png | Maps Account | terraform | MapsAccount | accountResource |
+| ../../_images/azure-database.png | MariaDb Configuration | terraform | MariaDbConfiguration | accountResource |
+| ../../_images/azure-database.png | MariaDb Database | terraform | MariaDbDatabase | accountResource |
+| ../../_images/azure-database.png | MariaDb Firewall Rule | terraform | MariaDbFirewallRule | accountResource |
+| ../../_images/azure-database.png | MariaDb Server | terraform | MariaDbServer | accountResource |
+| ../../_images/azure-database.png | MariaDb Virtual Network Rule | terraform | MariaDbVirtualNetworkRule | accountResource |
+| ../../_images/azure-compute.png | Marketplace Agreement | terraform | MarketplaceAgreement | accountResource |
+| ../../_images/aws-resource.png | Media Convert Queue | terraform | mediaConvertQueue | accountResource |
+| ../../_images/aws-resource.png | Media Package Channel | terraform | mediaPackageChannel | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/azure-media.png | Media Services Account | terraform | MediaServicesAccount | accountResource |
+| ../../_images/aws-resource.png | Media Store Container | terraform | mediaStoreContainer | accountResource |
+| ../../_images/aws-resource.png | Media Store Container Policy | terraform | mediaStoreContainerPolicy | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Action Group | terraform | MonitorActionGroup | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Activity Log Alert | terraform | MonitorActivityLogAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Autoscale Setting | terraform | MonitorAutoscaleSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Diagnostic Setting | terraform | MonitorDiagnosticSetting | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Log Profile | terraform | MonitorLogProfile | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Metric Alert | terraform | MonitorMetricAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Alert | terraform | MonitorScheduledQueryRulesAlert | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/azure-monitor.png | Monitor Scheduled Query Rules Log | terraform | MonitorScheduledQueryRulesLog | accountResource |
+| ../../_images/aws-mq.png | MQ Broker | cloudFormation | Broker | accountResource |
+| ../../_images/aws-mq.png | Mq Broker | terraform | mqBroker | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration | cloudFormation | Configuration | accountResource |
+| ../../_images/aws-mq.png | Mq Configuration | terraform | mqConfiguration | accountResource |
+| ../../_images/aws-mq.png | MQ Configuration Association | cloudFormation | ConfigurationAssociation | accountResource |
+| ../../_images/azure-database.png | MS SQL Database | terraform | MSSQLDatabase | accountResource |
+| ../../_images/azure-database.png | MS SQL Elastic Pool | terraform | MSSQLElasticPool | accountResource |
+| ../../_images/azure-database.png | MS SQL Security Alert Policy | terraform | MSSQLSecurityAlertPolicy | accountResource |
+| ../../_images/azure-database.png | MS SQL Server | terraform | MSSQLServer | accountResource |
+| ../../_images/azure-database.png | MS SQL Vm | terraform | MSSQLVm | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment | terraform | MSSQLVulnerabilityAssessment | accountResource |
+| ../../_images/azure-database.png | MS SQL Vulnerability Assessment Rule Baseline | terraform | MSSQLVulnerabilityAssessmentRuleBaseline | accountResource |
+| ../../_images/aws-resource.png | Msk Cluster | terraform | mskCluster | accountResource |
+| ../../_images/aws-resource.png | Msk Configuration | terraform | mskConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Configuration | terraform | MySQLConfiguration | accountResource |
+| ../../_images/azure-database.png | MySQL Database | terraform | MySQLDatabase | accountResource |
+| ../../_images/azure-database.png | MySQL Firewall Rule | terraform | MySQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | MySQL Server | terraform | MySQLServer | accountResource |
+| ../../_images/azure-database.png | MySQL Virtual Network Rule | terraform | MySQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-messaging.png | Namespace Authorization Rule | terraform | NamespaceAuthorizationRule | accountResource |
+| ../../_images/azure-network.png | Nat Gateway | terraform | NatGateway | accountResource |
+| ../../_images/aws-vpc.png | Nat Gateway | terraform | natGateway | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster | terraform | neptuneCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Instance | terraform | neptuneClusterInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Parameter Group | terraform | neptuneClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Cluster Snapshot | terraform | neptuneClusterSnapshot | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Cluster Parameter Group | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Event Subscription | terraform | neptuneEventSubscription | accountResource |
+| ../../_images/aws-neptune.png | Neptune Parameter Group | terraform | neptuneParameterGroup | accountResource |
+| ../../_images/aws-neptune.png | Neptune Subnet Group | terraform | neptuneSubnetGroup | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Account | terraform | NetAppAccount | accountResource |
+| ../../_images/azure-netapp.png | NetApp Pool | terraform | NetAppPool | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Snapshot | terraform | NetAppSnapshot | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/azure-netapp.png | NetApp Volume | terraform | NetAppVolume | accountResource |
+| ../../_images/aws-vpc.png | Network Acl | terraform | networkAcl | accountResource |
+| ../../_images/aws-vpc.png | Network Acl Rule | terraform | networkAclRule | accountResource |
+| ../../_images/azure-network.png | Network DDos Protection Plan | terraform | NetworkDDosProtectionPlan | accountResource |
+| ../../_images/azure-network.png | Network Gateway | terraform | NetworkGateway | accountResource |
+| ../../_images/azure-network.png | Network Interface | terraform | NetworkInterface | accountResource |
+| ../../_images/aws-vpc.png | Network Interface | terraform | networkInterface | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Gateway Backend Address Pool Association | terraform | NetworkInterfaceApplicationGatewayBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Application Security Group Association | terraform | NetworkInterfaceApplicationSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Attachment | terraform | networkInterfaceAttachment | accountResource |
+| ../../_images/azure-network.png | Network Interface Backend Address Pool Association | terraform | NetworkInterfaceBackendAddressPoolAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Nat Rule Association | terraform | NetworkInterfaceNatRuleAssociation | accountResource |
+| ../../_images/azure-network.png | Network Interface Security Group Association | terraform | NetworkInterfaceSecurityGroupAssociation | accountResource |
+| ../../_images/aws-vpc.png | Network Interface Sg Attachment | terraform | networkInterfaceSgAttachment | accountResource |
+| ../../_images/azure-network.png | Network Packet Capture | terraform | NetworkPacketCapture | accountResource |
+| ../../_images/azure-network.png | Network Profile | terraform | NetworkProfile | accountResource |
+| ../../_images/azure-network.png | Network Security Group | terraform | NetworkSecurityGroup | accountResource |
+| ../../_images/azure-network.png | Network Security Rule | terraform | NetworkSecurityRule | accountResource |
+| ../../_images/azure-network.png | Network Watcher | terraform | NetworkWatcher | accountResource |
+| ../../_images/azure-network.png | Network Watcher Flow Log | terraform | NetworkWatcherFlowLog | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub | terraform | NotificationHub | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Authorization Rule | terraform | NotificationHubAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Notification Hub Namespace | terraform | NotificationHubNamespace | accountResource |
+| ../../_images/aws-resource.png | Opsworks Application | terraform | opsworksApplication | accountResource |
+| ../../_images/aws-resource.png | Opsworks Custom Layer | terraform | opsworksCustomLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Ganglia Layer | terraform | opsworksGangliaLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Haproxy Layer | terraform | opsworksHaproxyLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Instance | terraform | opsworksInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Java App Layer | terraform | opsworksJavaAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Memcached Layer | terraform | opsworksMemcachedLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Mysql Layer | terraform | opsworksMysqlLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Nodejs App Layer | terraform | opsworksNodejsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Permission | terraform | opsworksPermission | accountResource |
+| ../../_images/aws-resource.png | Opsworks Php App Layer | terraform | opsworksPhpAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rails App Layer | terraform | opsworksRailsAppLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks Rds Db Instance | terraform | opsworksRdsDbInstance | accountResource |
+| ../../_images/aws-resource.png | Opsworks Stack | terraform | opsworksStack | accountResource |
+| ../../_images/aws-resource.png | Opsworks Static Web Layer | terraform | opsworksStaticWebLayer | accountResource |
+| ../../_images/aws-resource.png | Opsworks User Profile | terraform | opsworksUserProfile | accountResource |
+| ../../_images/aws-resource.png | Organizations Account | terraform | organizationsAccount | accountResource |
+| ../../_images/aws-resource.png | Organizations Organization | terraform | organizationsOrganization | accountResource |
+| ../../_images/aws-resource.png | Organizations Organizational Unit | terraform | organizationsOrganizationalUnit | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy | terraform | organizationsPolicy | accountResource |
+| ../../_images/aws-resource.png | Organizations Policy Attachment | terraform | organizationsPolicyAttachment | accountResource |
+| ../../_images/azure-network.png | Packet Capture | terraform | PacketCapture | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Adm Channel | terraform | pinpointAdmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Channel | terraform | pinpointApnsChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Sandbox Channel | terraform | pinpointApnsSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Channel | terraform | pinpointApnsVoipChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Apns Voip Sandbox Channel | terraform | pinpointApnsVoipSandboxChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint App | terraform | pinpointApp | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Baidu Channel | terraform | pinpointBaiduChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Email Channel | terraform | pinpointEmailChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Event Stream | terraform | pinpointEventStream | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Gcm Channel | terraform | pinpointGcmChannel | accountResource |
+| ../../_images/aws-resource.png | Pinpoint Sms Channel | terraform | pinpointSmsChannel | accountResource |
+| ../../_images/azure-compute.png | Placement Group | terraform | PlacementGroup | accountResource |
+| ../../_images/aws-ec2.png | Placement Group | terraform | placementGroup | accountResource |
+| ../../_images/azure-network.png | Point To Site VPN Gateway | terraform | PointToSiteVPNGateway | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Assignment | terraform | PolicyAssignment | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Definition | terraform | PolicyDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Remediation | terraform | PolicyRemediation | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-policy.png | Policy Set Definition | terraform | PolicySetDefinition | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Configuration | terraform | PostgreSQLConfiguration | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Database | terraform | PostgreSQLDatabase | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Firewall Rule | terraform | PostgreSQLFirewallRule | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Server | terraform | PostgreSQLServer | accountResource |
+| ../../_images/azure-database.png | PostgreSQL Virtual Network Rule | terraform | PostgreSQLVirtualNetworkRule | accountResource |
+| ../../_images/azure-power-bi.png | PowerBI | terraform | PowerBI | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS A Record | terraform | PrivateDNSARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS AAAA Record | terraform | PrivateDNSAAAARecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS CName Record | terraform | PrivateDNSCNameRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS MX Recrod | terraform | PrivateDNSMXRecrod | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Ptr Record | terraform | PrivateDNSPtrRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Srv Record | terraform | PrivateDNSSrvRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Text Record | terraform | PrivateDNSTextRecord | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone | terraform | PrivateDNSZone | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-private-dns.png | Private DNS Zone Virtual Network Link | terraform | PrivateDNSZoneVirtualNetworkLink | accountResource |
+| ../../_images/azure-network.png | Private Endpoint | terraform | PrivateEndpoint | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/azure-network.png | Private Link Service | terraform | PrivateLinkService | accountResource |
+| ../../_images/aws-elastic-load-balancing.png | Proxy Protocol Policy | terraform | proxyProtocolPolicy | accountResource |
+| ../../_images/azure-network.png | Public IP | terraform | PublicIP | accountResource |
+| ../../_images/azure-network.png | Public IP Prefix | terraform | PublicIPPrefix | accountResource |
+| ../../_images/aws-resource.png | Qldb Ledger | terraform | qldbLedger | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/azure-messaging.png | Queue Authorization Rule | terraform | QueueAuthorizationRule | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight Group | terraform | quicksightGroup | accountResource |
+| ../../_images/aws-quicksight.png | Quicksight User | terraform | quicksightUser | accountResource |
+| ../../_images/aws-resource.png | Ram Principal Association | terraform | ramPrincipalAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Association | terraform | ramResourceAssociation | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share | terraform | ramResourceShare | accountResource |
+| ../../_images/aws-resource.png | Ram Resource Share Accepter | terraform | ramResourceShareAccepter | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster | terraform | rdsCluster | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Endpoint | terraform | rdsClusterEndpoint | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Instance | terraform | rdsClusterInstance | accountResource |
+| ../../_images/aws-rds.png | Rds Cluster Parameter Group | terraform | rdsClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster | cloudFormation | DBCluster | accountResource |
+| ../../_images/aws-rds.png | RDS DB Cluster ParameterGroup | cloudFormation | DBClusterParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Instance | cloudFormation | DBInstance | accountResource |
+| ../../_images/aws-rds.png | RDS DB Parameter Group | cloudFormation | DBParameterGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group | cloudFormation | DBSecurityGroup | accountResource |
+| ../../_images/aws-rds.png | RDS DB Security Group Ingress | cloudFormation | DBSecurityGroupIngress | accountResource |
+| ../../_images/aws-rds.png | RDS DB Subnet Group | cloudFormation | DBSubnetGroup | accountResource |
+| ../../_images/aws-rds.png | RDS Event Subscription | cloudFormation | EventSubscription | accountResource |
+| ../../_images/aws-rds.png | Rds Global Cluster | terraform | rdsGlobalCluster | accountResource |
+| ../../_images/aws-rds.png | RDS Option Group | cloudFormation | OptionGroup | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Recovery Services Vault | terraform | RecoveryServicesVault | accountResource |
+| ../../_images/azure-recovery.png | Redis Cache | terraform | RedisCache | accountResource |
+| ../../_images/azure-recovery.png | Redis Firewall Rule | terraform | RedisFirewallRule | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | cloudFormation | Cluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster | terraform | redshiftCluster | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Parameter Group | cloudFormation | ClusterParameterGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group | cloudFormation | ClusterSecurityGroup | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Security Group Ingress | cloudFormation | ClusterSecurityGroupIngress | accountResource |
+| ../../_images/aws-redshift.png | Redshift Cluster Subnet Group | cloudFormation | ClusterSubnetGroup | accountResource |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json b/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
new file mode 100644
index 0000000..dc6334d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+  "title": "Tenants",
+  "ordinal": 274,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.html",
+  "topic_cluster": {
+    "clustering_title": "Tenants",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B",
+        "clustering_title": "Tenants"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md b/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
new file mode 100644
index 0000000..78315f6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-C9B54784-02A9-4194-AFA3-F99B9E08F50B.md
@@ -0,0 +1,9 @@
+# Tenants
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AD3C26B8-A41C-4875-B9C9-1A350E1CF2CD.html)**
+- **[Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-49067498-304A-4C38-B9C1-D8CF296DD3FA.html)**
+- **[Tenants](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-701A5EFA-E128-49D6-B12E-0C2415D4F83A.html)**
+- **[Tenant Users](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8C608C16-055C-4708-BA01-87FACE15EF6D.html)**
+- **[Configuring Tenants and Resources for Multi-Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-81B4F7F1-22DE-4285-BD37-B5C4D03E0063.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json b/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
new file mode 100644
index 0000000..7255187
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+  "title": "Cloud Access Levels",
+  "ordinal": 299,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.html",
+  "topic_cluster": {
+    "clustering_title": "Cloud Access Levels",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0",
+        "clustering_title": "Cloud Access Levels"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md b/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
new file mode 100644
index 0000000..8a35df7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CA31865E-DE19-4F55-BBC0-A231913BB1F0.md
@@ -0,0 +1,13 @@
+# Cloud Access Levels
+
+When creating or editing a Tenant Role, Master Tenant administrators can choose which publicly-visible Clouds to share with Tenants having the current Role. Access can be completely restricted or administrators can choose between Read and Full access.
+
+## Read Access
+
+Master Tenant administrators can opt to give other Tenants read-level access to any integrated Clouds through the Tenant Role. A read-only Cloud allows the Master Tenant to assign resources for viewing by Subtenant users but not allow them to perform any actions or provision new Instances.
+
+With read-level access, Subtenant users will have access to the Cloud detail page (Infrastructure > Clouds). From the Summary subtab on the Cloud detail page, high-level information on Cloud resources are shown regardless of specific resources that have been shared with the Subtenant. Other metrics, such as costing, resource percentages (CPU, Memory, and Storage), VM counts and host counts will only be populated when servers in the Cloud have been assigned to the Tenant.
+
+## Full Access
+
+With full access, Subtenant users also have access to the Cloud detail page (Infrastructure > Clouds > Specific Cloud) and see the same level of detail as Subtenants with read-only rights. However, with full access, Subtenant users can also perform many actions including the addition of Clusters, Hosts, and VMs, changing networks, and more. This cloud will also be selectable as a provisioning target for Subtenant users when deploying Instances or Apps.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json b/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
new file mode 100644
index 0000000..ed09abc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+  "title": "Image Management",
+  "ordinal": 405,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.html",
+  "topic_cluster": {
+    "clustering_title": "Image Management",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970",
+        "clustering_title": "Image Management"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md b/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
new file mode 100644
index 0000000..c059db3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CA96F723-CABE-4A23-AEAC-220BE12D2970.md
@@ -0,0 +1,7 @@
+# Image Management
+
+The topic describes about image catalog and uploading various images.
+
+**Subtopics**  
+
+- **[Image Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5D659229-2AFA-4A63-9194-D128E673AA02.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json b/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
new file mode 100644
index 0000000..ca65ee5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+  "title": "Mapping",
+  "ordinal": 250,
+  "parent_title": "Boot",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.html",
+  "topic_cluster": {
+    "clustering_title": "Mapping",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB",
+        "clustering_title": "Mapping"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md b/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
new file mode 100644
index 0000000..fd59117
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB5EF6C1-AA7D-4EB8-AED2-E07717A77FDB.md
@@ -0,0 +1,51 @@
+# Mapping
+
+## Add Mapping
+
+### Procedure
+
+1. Select the Mapping tab then click the Add Mapping button.
+2. From the New Mapping Wizard input the following information: 
+
+   Match Pattern
+   :   Mac address separated by ‘:’ or an ip address filter
+
+   Description(optional)
+   :   Description of the new mapping.
+
+   Active
+   :   Flag to denote the mapping as active or disabled.
+
+   Operating System
+   :   List of operating systems for the mapping.
+
+   Boot Image
+   :   Lists available PXE boot images.
+
+   Answer File
+   :   Lists available answer files.
+
+   Cloud
+   :   Lists the available clouds.
+
+   Server Mode
+   :   List of server modes:: unmanaged, Managed, Bare metal host, Container host, VM host, and Container & VM host.
+3. Save
+
+### Results
+
+Once the mapping is added, and the target host is powered on, the {morpheus} PXE menu will load and PXE boot will start.
+
+## Edit Mapping
+
+### Procedure
+
+1. Click the edit icon on the row of the mapping you wish to edit.
+2. Modify information as needed.
+3. Click the Save Changes button to save.
+
+### Results
+
+Delete Mapping
+
+1. Click the delete icon on the row of the mapping you wish to delete.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json b/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
new file mode 100644
index 0000000..986699d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+  "title": "Managed Networks",
+  "ordinal": 431,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.html",
+  "topic_cluster": {
+    "clustering_title": "Managed Networks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF",
+        "clustering_title": "Managed Networks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md b/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
new file mode 100644
index 0000000..0dca37b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB677986-BAD6-4C63-9A6E-554F0FA983FF.md
@@ -0,0 +1,13 @@
+# Managed Networks
+
+The managed network mode is used when the network infrastructure is to be managed by Morpheus. In this case, the user can select ArubCX-Int during the cloud creation.
+
+## Adding HPE ArubaCX Plugin
+
+In the managed network mode, the Aruba CX switches are supported as managed switches. To enable that, the ArubaCX plugin needs to be loaded.
+
+You can load the ArubaCX plugin jar using the Administration > Integrations.
+
+**Subtopics**  
+
+- **[Creating ArubaCX Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json b/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
new file mode 100644
index 0000000..0d57048
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+  "title": "Operations",
+  "ordinal": 53,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.html",
+  "topic_cluster": {
+    "clustering_title": "Operations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D",
+        "clustering_title": "Operations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md b/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
new file mode 100644
index 0000000..9a03004
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CB80B1E3-95C3-4D31-A69F-6B24D2AD7C9D.md
@@ -0,0 +1,12 @@
+# Operations
+
+**Subtopics**  
+
+- **[Dashboard](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2277183A-E315-4439-A885-C111A77C7154.html)**
+- **[Reports](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3AF48D4F-1BB9-4B33-B583-6CC73DA6B6B0.html)**
+- **[Analytics](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C6AB6E89-39FB-498A-A333-5550A593DA7B.html)**
+- **[Guidance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B86C6485-C80C-480F-87B4-4352963D74A5.html)**
+- **[Wiki](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0A5AD977-07F5-4278-9CB3-F7D8AB8427A3.html)**
+- **[Costing](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-87AA56DE-79F5-4FDC-A8E1-229022B0EDC1.html)**
+- **[Approvals](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1E955B51-BB03-4BBF-934F-C1EB2130F7BD.html)**
+- **[Activity](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-82C53DF1-4293-41E2-A90A-740C1814DD12.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json b/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
new file mode 100644
index 0000000..d9c559e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+  "title": "Whitelabel",
+  "ordinal": 323,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.html",
+  "topic_cluster": {
+    "clustering_title": "Whitelabel",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7",
+        "clustering_title": "Whitelabel"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md b/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
new file mode 100644
index 0000000..4b31d70
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CC1053C5-D26A-4139-BDB9-34B3C5F60AB7.md
@@ -0,0 +1,114 @@
+# Whitelabel
+
+## Whitelabel Settings
+
+### Overview
+
+HPE Morpheus Enterprise Tenants can be WhiteLabeled with custom Logos, Colors, Copy, and custom CSS. Sub-Tenants can be individually white-labeled, or the Master Tenant Whitelabel can apply to all Sub-Tenants.
+
+Enable Whitelabel
+:   Turns on the configured Whitelabel settings. Disabling will return the Appliance to the default colors and logos, but the configured options will remain saved and will apply if Whitelabel is re-enabled.
+
+Appliance Name
+:   Replaces HPE Morpheus Enterprise in page titles.
+
+Header Logo
+:   Top left header logo. Uploaded image is resized to 38 pixels high with a proportional width at that height.
+
+Disable Support Menu
+:   Enable this flag to hide the support dropdown menu in the header.
+
+Support Menu Links
+:   Customize support links. Label Code can be used for translations and is optional. Be sure to specify fully qualified url if linking to external sites.
+
+Security Banner
+:   The Security Banner section in `/admin/settings#!whitelabel` displays content on the login screen for Security and Consent messaging and warnings.
+    :   - Applicable at Global and Tenant levels
+        - Security Banner input field accepts plain text and markdown
+        - Content is displayed below login section in scoped `/login/auth` pages.
+
+Footer Logo
+:   Footer Logo in bottom left. Uploaded image is resized to 27 pixels high with a proportional width at that height.
+
+Login Logo
+:   Logo shown on Login screen. Uploaded image is resized to 192 pixels wide with an unbound height proportional to that locked width.
+
+Favicon
+:   Must be a .ico file type.
+
+Reset
+:   When selected and Whitelabel settings are saved, associated logo is returned to blank default value.
+
+### Colors
+
+Update Colors by entering HEX value or selecting the Color Selector pop-up next to each filed and selecting a color.
+
+- Header Background
+- Header Foreground
+- Nav Background
+- Nav Foreground
+- Nav Hover
+- Primary Button Bg
+- Primary Button Fg
+- Primary Button Hover Bg
+- Primary Button Hover Fg
+- Footer Background
+- Footer Foreground
+- Login Background
+
+### Override CSS
+
+Override CSS settings by entering CSS in Override CSS field.
+
+Example: (this will add one continues background image to the Header)
+
+```
+```
+header #topHeader {  
+        background-image: url(http://image_url.png);  
+        }  
+header {  
+        background-image: url(http://image_url.png);  
+        }
+```
+```
+
+### Copy
+
+Add custom Copyright String, Terms of Use, Privacy Policy contained in the Footer text and links in the App and on the login page and emails.
+
+Available Copy fields
+
+- Copyright String
+- Terms and Privacy String
+- Terms of Use
+- Privacy Policy
+
+  NOTE
+
+  Terms of Use and Privacy Policy Footer links will load internal pages at `https://applaince_url/privacy-policy` and `https://applaince_url/terms-of-use` displaying the entered info as plain text. The Terms and Privacy String will update the legal text displayed on the HPE Morpheus Enterprise login page. This field takes any custom HTML markup allowing you to link to the internal legal pages or to your own outside legal pages if you prefer.
+
+### ​UI Loading Page
+
+When the HPE Morpheus Enterprise UI is restarted or loading, a default “Morpheus is Loading” page is displayed. This page can be changed by adding the following to `/etc/morpheus/morpheus.rb` and adjusting the values.
+
+NOTE
+
+`morpheus-ctl reconfigure` must be ran for any chnages to `/etc/morpheus/morpheus.rb` to take effect.
+
+```
+```
+nginx['web_root_internal'] = "/opt/morpheus/embedded/nginx/html"  
+nginx['loading_pages']['max_loops'] = 6 * 10 # 10 secs per loop x 6 times to get 60 seconds * 10 to get to 10 minutes  
+nginx['loading_pages']['timeout_page'] = '/timeout.html'  
+nginx['loading_pages']['iteration_time'] = 10_000  
+nginx['loading_pages']['loading_page_title'] = 'Morpheus Loading'  
+nginx['loading_pages']['loading_page_h1'] = 'Morpheus is Loading...'  
+nginx['loading_pages']['loading_page_h2'] = 'please wait'  
+nginx['loading_pages']['timout_page_title'] = 'Morpheus timeout, please try again...'  
+nginx['loading_pages']['timout_page_h1'] = 'Timeout waiting for Morpheus to load, click below to try again.'  
+nginx['loading_pages']['failure_page_title'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h1'] = 'Morpheus Server Error'  
+nginx['loading_pages']['failure_page_h2'] = 'Please contact your system administrator for assistance.'
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json b/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
new file mode 100644
index 0000000..91f0abb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+  "title": "Monitoring the Cluster",
+  "ordinal": 208,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CC1F0809-F068-41F6-853A-0033148C3436",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md b/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
new file mode 100644
index 0000000..916ba43
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CC1F0809-F068-41F6-853A-0033148C3436.md
@@ -0,0 +1,20 @@
+# Monitoring the Cluster
+
+After onboarding the cluster into HPE Morpheus Enterprise, a new Cluster object is added to the Clusters list page. Clicking into the Cluster reveals the Cluster detail page. Note the following subtabs and the cluster details we can monitor in each:
+
+- **Nodes:** Master and worker nodes making up the cluster are shown here. Click into any of them to see a node detail page
+- **VMs:** A list of all virtual machines within the scope of the OpenShift cluster are shown. When creating or editing the cluster, an option is given to inventory all existing instances. If selected, all running virtual machines will be onboarded and shown here even if they were provisioned outside of HPE Morpheus Enterprise. If this option is not selected, then only the OpenShift virtual machines provisioned through HPE Morpheus Enterprise are shown. High level details about each virtual machine are also shown, such as power state and resource usage. Click into any virtual machine to see a detail page with additional options
+- **Virtual Images:** A list of virtual images synced to HPE Morpheus Enterprise is shown. Only custom user images are synced, images which are part of the large OpenShift default catalog are not synced. Click into any virtual image to see a detail page and to edit configurations for any images, if necessary
+
+  IMPORTANT
+
+  Virtual Images used for provisioning OpenShift workloads from HPE Morpheus Enterprise must be updated to set appropriate properties prior to use. Edit the Virtual Image to uncheck the "Install Agent?" configuration and check either "Is Cloud Init Enabled?" or "Sysprepped/Generalized Image" depending on the workload-type. Ensure the OpenShift template has VirtIO drivers and QEMU VM agent tools installed. For Windows images, only the "Sysprepped/Generalized Image" option is currently supported. Do not use the Cloudbase-init option until support is added. For Linux-based images, HPE Morpheus Enterprise expects standardized NIC names (eth0, eth1, etc) on templates so that cloud-init can reliably apply network configuration. For Windows templates, HPE Morpheus Enterprise relies on OpenShift standard interface naming (ex. Ethernet Instance 0) in templates. Currently on Windows Instances, configuration of the first network interface is supported as part of deployment via Sysprep.
+- **Networks:** NetworkAttachmentDefinitions (NADs) define virtual network interfaces that can be attached to VMs, acting as network bridges
+
+IMPORTANT
+
+Edit and update synced network objects (OpenShift NADs) in HPE Morpheus Enterprise with appropriate IPv4/IPv6 configuration details (DHCP, Gateway, DNS, Subnet, etc.)
+
+TIP
+
+IP Pools can be associated with the network definitions synced from OpenShift. These can be Morpheus-type IP Pools created within the HPE Morpheus Enterprise UI or can be IP Pools sourced from IPAM integrations. If IP Pools are used, HPE Morpheus Enterprise can manage IP addresses across the Instance lifecycle (claim a free address at provision time, release an address at teardown, etc)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json b/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
new file mode 100644
index 0000000..5744b2e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+  "title": "Agent Installation",
+  "ordinal": 46,
+  "parent_title": "Morpheus Agent",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.html",
+  "topic_cluster": {
+    "clustering_title": "Agent Installation",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9",
+        "clustering_title": "Agent Installation"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md b/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
new file mode 100644
index 0000000..05786dd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CCC7880B-8316-4FDD-91D6-9680671E23D9.md
@@ -0,0 +1,185 @@
+# Agent Installation
+
+There are many methods to install the HPE Morpheus Enterprise Agent on supported targets. All Agent installation methods are executing a script on the target that calls back to the HPE Morpheus Enterprise appliance over port 443.
+
+IMPORTANT
+
+All Agent installation methods require the Target (VM or Host) to resolve and reach the appliance URL over port 443. In addition to the main Appliance URL (in Administration > Settings), additional Appliance URLs can be set per cloud in the Advanced Options section of the Create/Edit Cloud modal. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+## Basic Installation Steps
+
+### Procedure
+
+1. An Agent installation method is used to get the install script onto the target VM or Host
+2. The Agent installation script is executed on the target VM or Host, installing the Agent and all dependencies
+3. The Agent is started and makes a websocket connection to the configured Appliance URL over port 443 using the target VM or Host API key
+
+### Results
+
+It is important to note these are three separate steps with varying requirements. The first requires a path to get the script on the target. The second requires successful execution of the Agent installation script. The third requires a successful websocket connection. Requirements for the successful execution of each step are covered in the sections below.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
+
+## Agent Install Modes
+
+Agent Installation Method is determined by:
+
+- The AGENT INSTALL MODE setting on target Cloud: - SSH / WinRM / Guest Execution - Cloud Init / Unattend (when available)
+- Platform / OS type on Virtual Image or target (VM or Host)
+- Virtual Image configuration
+- RPC Mode setting (VMware Clouds only)
+
+## Agent Installation Methods
+
+The Morpheus Agent can be installed with a variety of automated methods. It is important to note these methods simply get the Agent install script to the target. Successful execution of the Agent install script is not directly related to the Agent install method.
+
+SSH
+:   HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+    `curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+WinRM
+:   HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+VMware Tools
+:   HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+Cloud-Init
+:   HPE Morpheus Enterprise executes agentInstall.sh via cloud-init runcmd
+
+Cloudbase-Init
+:   HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+Windows Unattend
+:   HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+Manual
+:   User executes agentInstall.sh or agentInstall.ps1 manually on the VM or Host. These scripts can be obtained on the VM or Host detail page via Actions > DownloadAgent Script
+
+### SSH
+
+#### Process
+
+HPE Morpheus Enterprise makes an SSH connection to the VM or Host, CURLs, and executes the Agent install script:
+
+`curl -k -s "https://${applianceUrl}/api/server-script/agentInstall?apiKey=${apiKey}" | bash`
+
+#### Requirements
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+
+### WinRM
+
+#### Process
+
+HPE Morpheus Enterprise makes a WinRM connection to the VM or Host and executes the Agent install script
+
+#### Requirements
+
+- Port 5985 must be open and WinRM enabled for Windows images
+- Credentials have been entered on the image if using a custom or synced image. Credentials can be entered on images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install
+
+### VMware Tools
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh or agentInstall.ps1 via VMware Tools Guest Execution
+
+#### Requirements
+
+- VMware Tools is installed on the template(s)
+- Credentials have been entered on the Image if using an uploaded or synced image when Cloud-init, Guest Customizations, or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section
+- Administrator User (SID 500) is required for Windows Agent install.
+
+### Cloud-Init
+
+#### Process
+
+HPE Morpheus Enterprise executes agentInstall.sh via Cloud-Init runcmd
+
+#### Requirements
+
+- Cloud-Init is installed on Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Cloud-Init User is configured in the Administration > Settings > Provisioning section
+
+### Cloudbase-init
+
+#### Process
+
+HPE Morpheus Enterprise adds WindowsAgentCloudInitInstallScript to CloudbaseInitUserData
+
+#### Requirements
+
+- Cloudbase-Init is installed on the Virtual Image
+- “IS CLOUD INIT ENABLED?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+- Windows Administrator password defined in the Administration > Settings > Provisioning section
+
+### Windows Unattend
+
+#### Process
+
+HPE Morpheus Enterprise adds getWindowsAgentDownloadScript to unattend.xml (RunSynchronousCommand)
+
+#### Requirements
+
+VMware
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “FORCE GUEST CUSTOMIZATION?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record when using DHCP
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+Nutainx/SCVMM/Openstack
+:   - Windows Administrator password defined in the Administration > Settings > Provisioning section OR Administrator User (SID 500) and valid Windows password are defined on the HPE Morpheus Enterprise Virtual Image record
+    - “ENABLED SYSPREP?” is checked (true) on the HPE Morpheus Enterprise Virtual Image record
+    - “IS CLOUD INIT ENABLED?” is unchecked (false) on the HPE Morpheus Enterprise Virtual Image record
+
+### Manual
+
+#### Process
+
+- From the VM or Host record page (`/infrastructure/servers/${id}`) run ACTIONS > `Download Agent Script`
+- This is will generate an Agent install script based off the target OS and platform, Appliance URL, and API key
+- Manually execute the downloaded script on the Target VM or Host
+
+## Agent Install Requirements
+
+Table 1.
+
+          |  |  |  |  |  |  |  |  |
+| --- | --- | --- | --- | --- | --- | --- | --- |
+| Agent Installation Requirements | | | | | | | |
+| Requirement | Agent Installation Method | | | | | | |
+| SSH | WINRM | VMWARE TOOLS | CLOUD‐INIT | CLOUDBASE‐INIT | UNATTEND | MANUAL |
+| Target (vm/host) to resolve and reach Appliance URL over 443 | YES | YES | YES | YES | YES | YES | YES |
+| Target (vm/host) to resolve and reach Appliance URL over 80 | Ubuntu 14.04 Only |  | Ubuntu 14.04 Only | Ubuntu 14.04 Only |  |  | Ubuntu 14.04 Only |
+| Websockets enabled when using load balancer | YES | YES | YES | YES | YES | YES | YES |
+| Access to Target VM/Host on port 22 | YES | NO | NO | NO | NO | NO | NO |
+| Access to Target VM/Host on port 5985 | NO | YES | NO | NO | NO | NO | NO |
+| Vmware Tools installed and flagged on Virtual Image | NO | NO | YES | NO | NO | YES | NO |
+| Syspreped Image and Sysprep Enabled flagged on Virtual Image (Nutanix, Openstack, SCVMM) | NO | NO | NO | NO | NO | YES | NO |
+| Force Guest Customizations flagged on Virtual Image | NO | NO | DHCP | NO | NO | DHCP | NO |
+| Cloud‐Init installed and flagged on Virtual Image | NO | NO | NO | YES | YES | NO | NO |
+| Global Cloud‐Init user populated in Administration > Settings > Provisioning | NO | NO | NO | YES | NO | NO | NO |
+| Windows Administrator Password populated in Administration > Settings > Provisioning | NO | NO | NO | NO | YES | YES | NO |
+| Access to configured YUM or APT repos | NO but will cause delay in Agent Install | N/A | NO but will cause delay in Agent Install | NO but will cause delay in Agent Install | N/A | N/A | NO but will cause delay in Agent Install |
+| .net >=4.5.2 (Windows, Morpheus >= 4.1.2) | N/A | YES | YES | N/A | YES | YES | YES |
+| User with Sudo Access set on Virtual Image (Greenfield) | YES | N/A | YES | NO | N/A | N/A | N/A |
+| Administrator User (SID 500) set on Virtual Image (Greenfield) | N/A | YES | YES | N/A | NO | N/A | N/A |
+| User with Sudo Access set on VM/Host Record (Brownfield) | YES | N/A | YES | N/A | N/A | N/A | N/A |
+| Administrator User (SID 500) set on VM/Host Record (Brownfield) | N/A | YES | YES | N/A | N/A | N/A | N/A |
+
+When provisioning an Instance, there are network and configuration requirements to consider in order to successfully install the HPE Morpheus Enterprise Agent. Typically, when a VM Instance is still in the provisioning phase long after the VM is up, the Instance is unable to reach HPE Morpheus Enterprise. Depending on the Agent install mode, it could also mean HPE Morpheus Enterprise is unable to reach the Instance.
+
+The most common reason an Agent install fails is the provisioned Instance cannot reach the HPE Morpheus Enterprise Appliance via the Appliance URL set in Administration > Settings over port 443. When an Instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the Appliance URL or the Agent will not be installed.
+
+![../../../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main Appliance URL in Administration > Settings, additional Appliance URLs can be set per Cloud in the Advanced Options section of the Cloud configuration modal when creating or editing a Cloud. When this field is populated, it will override the main Appliance URL for anything provisioned into that Cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting Agent installations.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json b/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
new file mode 100644
index 0000000..e1a7249
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+  "title": "Creating an Option List Based on an LDAP Query",
+  "ordinal": 157,
+  "parent_title": "Options",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.html",
+  "topic_cluster": {
+    "clustering_title": "Creating an Option List Based on an LDAP Query",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F",
+        "clustering_title": "Creating an Option List Based on an LDAP Query"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md b/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
new file mode 100644
index 0000000..118b6fc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CD1058AC-228F-424E-A2B0-45B93F4C582F.md
@@ -0,0 +1,51 @@
+# Creating an Option List Based on an LDAP Query
+
+## About this task
+
+In Morpheus version 4.2.1 and higher, Option Lists can be populated from LDAP queries. This gives users the ability to search Active Directory, capture objects, and present them as custom options where needed.
+
+It’s recommended that you connect LDAP-type Option Lists to Typeahead-type Inputs as the list of returned selections can be very large. This also allows you to select multiple options from the list, presuming you’ve allowed for that when creating the Input.
+
+Populating LDAP-type Option Lists requires knowledge of LDAP query syntax. This guide provides one example and there are many publicly-available resources for help writing additional queries.
+
+## Procedure
+
+1. Create a new Option List (Library > Options > Option Lists > ADD)
+2. Enter a name for the new LDAP Option List
+3. Change the Type value to LDAP and the relevant fields will appear as shown in the screenshot:
+4. Enter the LDAP URL in the following format (an example is also shown as a placeholder in the UI form field): 
+
+   ```
+   ```
+   ldap[s]://<hostname>:<port>/<base_dn>
+   ```
+   ```
+5. Enter the fully qualified username with @ suffix syntax, such as: user@ad.mycompany.com
+6. Enter the account password
+7. Enter your LDAP query. You can even inject variables into your query structure to query based on the value the user has entered into the typeahead field as shown in the example below: 
+
+   ```
+   ```
+   (&(objectClass=user)(cn=<%=phrase%>*))
+   ```
+   ```
+8. Finally, enter a translation script which will convert the returned LDAP object into a list of name:value pairs you can work with in Morpheus. The example script below shows the user DisplayName and sets the value to the SAMAccountName: 
+
+   ```
+   ```
+   for(var x=0;x < data.length ; x++) {  
+     var row = data[x];  
+     var a = {};  
+     if(row.displayName != null) {  
+       a['name'] = row.displayName;  
+     } else {  
+       a['name'] = row.sAMAccountName;  
+     }  
+     a['value'] = row.sAMAccountName;  
+     results.push(a);  
+   }
+   ```
+   ```
+9. Click SAVE CHANGES 
+
+   ![../../_images/ldap_option_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F3A370B1-BB00-4177-8AF4-D6E5A2975918-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json b/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
new file mode 100644
index 0000000..9bd2727
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+  "title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+  "ordinal": 364,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html",
+  "topic_cluster": {
+    "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A",
+        "clustering_title": "Automated Single-Node Application Deployment with HPE Morpheus Enterprise"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md b/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
new file mode 100644
index 0000000..881fab9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.md
@@ -0,0 +1,358 @@
+# Automated Single-Node Application Deployment with HPE Morpheus Enterprise
+
+This document provides a complete step-by-step guide to automating the configuration, installation, and deployment of the open source CRM application SuiteCRM using HPE Morpheus Enterprise. In this guide, we will create a custom Instance Type for SuiteCRM which can then be selected during provisioning. Once configured, the provisioning process is completely automated and results in SuiteCRM and a database installed on a single node. There is also an accompanying guide which automates the process for deployed SuiteCRM as a multi-tiered application consisting of a MySQL database on one node and the SuiteCRM application on a second node.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs to fully automate the provisioning process of a single-node application:
+
+- Instance Types
+- Layouts
+- Node Types
+- Cypher
+- Archive
+- Inputs
+- File Templates
+- Tasks
+- Provisioning Workflows
+
+Each of these constructs can be explored more deeply in their own specific sections of HPE Morpheus Enterprise docs but this guide will illustrate how these pieces can be pulled together to automate deployment, ensure consistency and security, and enable self-service. This could be used to create a provisionable Instance Type on any HPE Morpheus Enterprise-supported Cloud type and it’s intentionally left open-ended to be useful for any environment. As I’m building the example, I’ll show screenshots targeting a build for VMware vCenter Clouds. Despite the screenshots, this guide is useful for any environment.
+
+## Create a HPE Morpheus Enterprise Archive for Install Files
+
+HPE Morpheus Enterprise Archives allow you to store files which can then be made available for download in scripts or by users. Archives are backed by buckets or file shares which must exist prior to creating the Archive. Buckets could be backed by Amazon S3, for example. File Shares could be backed by an NFS file share or even point directly to a local folder on the appliance itself. In this example, we’ll use an S3-backed bucket. With an Amazon AWS Cloud already integrated with HPE Morpheus Enterprise, we can even create the S3 bucket itself without leaving HPE Morpheus Enterprise UI.
+
+To create a new bucket, navigate to Infrastructure > Storage. From the Buckets tab, click + ADD and then select “AWS S3 Bucket”. The example bucket configuration is shown below. Bear in mind if you make any changes you may need to carefully confirm Task configurations and calls to Cypher or Archive to ensure they match any changes you’ve made.
+
+- **NAME:** Automation Training S3 Bucket (this is simply a friendly name for the bucket within HPE Morpheus Enterprise)
+- **Storage Service:** Select your pre-existing AWS Cloud
+- **BUCKET NAME:** Enter a unique name for the bucket (this much conform to AWS bucket naming rules, consult AWS documentation if needed)
+- **CREATE BUCKET:** Checked
+- **REGION:** The AWS region to create the bucket in
+- **ACTIVE:** Checked (this makes it available for use in HPE Morpheus Enterprise)
+
+![../../_images/newBucket.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F1FDC927-C674-4E43-A0EC-C9347212EEC5-high.png)
+
+With the bucket created, we can now create the Archive. Start by going to Tools > Archives and clicking + ADD. In the new Archive, we need to configure the following:
+
+- **NAME:** Software Archive
+- **BUCKET:** Select the bucket we just created
+- **PUBLIC URL:** Checked (this automatically creates a public download URL when files are added to the Archive)
+
+NOTE
+
+If you don’t name your Archive “Software Archive” as indicated here, you will have to make manual changes to Task config later in this guide.
+
+At this point, you should go ahead and download the installation ZIP file for SuiteCRM. You can access version 7.14.3 [here](https://github.com/salesagility/SuiteCRM/releases). This guide is designed for version 7.14.3. If you opt to download a different version please note that changes might be needed to the automation scripts to account for any changes to the installation or configuration processes for that version.
+
+Click on the newly created Archive and note there are no files contained in it. Under the Files tab, click + ADD. Slide the installation ZIP file onto the modal and wait for the file to be successfully uploaded. Click DONE. We’ve now added the installation ZIP file and it is visible in the list of files on the Files tab.
+
+Click on the name of the newly added file to access the File detail page. While here, click on the Scripts tab and you’ll see syntax examples for how this and other files might be accessed in your automation scripts. You’ll see this syntax used later in this example as we access the ZIP file directly from this Archive and automate the installation process. Generated links can be viewed from the Links tab and a record of it will be visible on the History tab.
+
+![../../_images/fileDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9154F24C-12F6-46F9-AD91-8B9B5758B985-high.png)
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the MariaDB root user password as a Cypher entry. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here’s we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/dba/mariadb\_root
+- **VALUE:** Password123?
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/cypherMaria.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-9196BD2B-DED5-4018-891A-19D5BCE27DA4-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. We’ll create three inputs in this case for the database name, the database username, and the database user password.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** SuiteCRM DB Name (The name for the Input object in HPE Morpheus Enterprise)
+- **LABEL:** SUITECRM (Labels are a categorizing feature in HPE Morpheus Enterprise)
+- **FIELD NAME:** databaseNameSCRM (The internal property which the input value is assigned to)
+- **SHOW ON EDIT:** Checked (By checking this box, we can view this Input value when editing the Instance after provisioning)
+- **DISPLAY VALUE ON DETAILS:** Checked (By checking this box, we will see the value of this Input on the detail page for the provsioned Instance)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** SuiteCRM DB Name (The label the user will see next to the field at provsion time)
+- **REQUIRED:** Checked (By checking this box, the Input will be required at provision time)
+
+### Database Name Input
+
+![../../_images/dbNameInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C19EB913-4A34-4D5D-A85A-C0620C2BDFCF-high.png)
+
+Click SAVE CHANGES. Then, create two additional Inputs:
+
+- **NAME:** SuiteCRM DB User
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databaseUserSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Text
+- **LABEL:** SuiteCRM DB User
+- **REQUIRED:** Checked
+
+### Database Username Input
+
+![../../_images/dbUserInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CFB7E6DB-864A-4995-B1EB-A77E2D08ABA9-high.png)
+
+- **NAME:** SuiteCRM DB Password
+- **LABEL:** SUITECRM
+- **FIELD NAME:** databasePassSCRM
+- **SHOW ON EDIT:** Checked
+- **DISPLAY VALUE ON DETAILS:** Checked
+- **TYPE:** Password (Password type Inputs are masked on screen when entered by the user)
+- **LABEL:** SuiteCRM DB Password
+- **REQUIRED:** Checked
+
+### Database Password Input
+
+![../../_images/dbPassInput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-35947404-36DD-48AC-A3FF-2E57EE6B68FF-high.png)
+
+## Create File Templates
+
+For our SuiteCRM application, we’ll need to create an Apache config file. We can create a File Template in HPE Morpheus Enterprise and the config file will be generated dynamically at provision time with the appropriate values. Navigate to Library > Templates > File Templates and click + ADD. Enter the following:
+
+- **NAME:** suitecrm - conf
+- **LABELS:** SUITECRM
+- **FILE NAME:** suitecrm.conf
+- **FILE PATH:** /etc/apache2/sites-available
+- **PHASE:** Provision
+- **TEMPLATE:** See below for the complete template, note how we’re able to dynamically resolve HPE Morpheus Enterprise variables within the template
+- **FILE OWNER:** root
+- **SETTING NAME:** suitecrm
+- **SETTING CATEGORY:** App
+
+```
+```
+<VirtualHost *:80>  
+   ServerAdmin admin@localhost  
+   ServerAlias "<%=server.externalIp%>"  
+   DocumentRoot /var/www/html/suitecrm  
+   <Directory /var/www/html/suitecrm/>  
+        Options FollowSymlinks  
+        AllowOverride All  
+        Require all granted  
+   </Directory>  
+   ErrorLog ${APACHE_LOG_DIR}/error.log  
+   CustomLog ${APACHE_LOG_DIR}/access.log combined  
+   <Directory /var/www/html/suitecrm/>  
+          RewriteEngine on  
+          RewriteBase /  
+          RewriteCond %{REQUEST_FILENAME} !-f  
+          RewriteRule ^(.*) index.php [PT,L]  
+  </Directory>  
+</VirtualHost>
+```
+```
+
+![../../_images/filetemplate.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-58E7A9A8-1822-4B60-9860-CA3DFDD3870B-high.png)
+
+## Create Tasks
+
+At this point, we need to create three automation Tasks. One will set the Apache config file we just created, another will be a Bash script Task to actually install and configure SuiteCRM on the box, and the third will be another Bash script Task which will restart the Apache service.
+
+To create a Library Template Task, navigate to Library > Automation > Tasks. Click + ADD. Enter the following:
+
+- **NAME:** suitecrm file template
+- **CODE:** suitecrmfiletemplate
+- **LABELS:** SUITECRM
+- **TYPE:** Library Template (The proper fields will appear once the Type is set)
+- **TEMPLATE:** suitecrm - conf (Select the File Template we already created from this dropdown menu)
+- **EXECUTE TARGET:** Resource
+
+![../../_images/libtemtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3ADB5F3A-1E18-46BD-9DF2-4D467460BEB6-high.png)
+
+Now create the first Bash Task which will install and configure SuiteCRM on a newly-provisioned box:
+
+- **NAME:** suitecrm - single node
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local (We will enter the script locally in this case but if version control repositories are integrated, such as Github, script content can be dynamically pulled from the repository at the time the Task is invoked. This ensures the code is always current without ever manually updating Tasks)
+- **CONTENT:** Expand the section below to see the script content. Note how Cypher secrets and custom option (Input) values are invoked in this script
+- **EXECUTE TARGET:** Resource
+
+### Install Task Content
+
+```
+```
+RPass="<%=cypher.read('secret/dba/mariadb_root')%>"  
+SCRMDb="<%=customOptions.databaseNameSCRM%>"  
+SCRMUser="<%=customOptions.databaseUserSCRM%>"  
+SCRMPass="<%=customOptions.databasePassSCRM%>"  
+PHP_VERSION="8.1"  
+MARIADB_VERSION="mariadb-10.11"  
+#Wait until any apt-get processes have finished  
+if [ `ps -ef | grep [a]pt-get | wc -l` = !0 ]  
+then  
+    sleep 120  
+fi  
+#Install apache, start service and enable on boot  
+apt-get install apache2 -y  
+systemctl stop apache2.service  
+systemctl start apache2.service  
+systemctl enable apache2.service  
+#Install MariaDB, start service and enable on boot  
+curl -LsS https://r.mariadb.com/downloads/mariadb_repo_setup | \  
+sudo bash -s ----mariadb-server-version="$MARIADB_VERSION"  
+apt update  
+apt-get install mariadb-server mariadb-client -y  
+systemctl stop mariadb.service  
+systemctl start mariadb.service  
+systemctl enablemariadb.service  
+#The following commands are from the mysql secure installation guidance  
+mysql -e "ALTER USER 'root'@'localhost' IDENTIFIED BY '$RPass';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='';"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.user WHERE User='root' \  
+AND Host NOT IN ('localhost', '127.0.0.1', '::1');"  
+mysql -u root -p$RPass-e "DROP DATABASE IF EXISTS test;"  
+mysql -u root -p$RPass-e "DELETE FROM mysql.db WHERE Db='test' \  
+OR Db='test\_%';"  
+mysql -u root -p$RPass-e "FLUSH PRIVILEGES;"  
+#Create the SuiteCRM User  
+mysql -u root -p$RPass-e "CREATE User '$SCRMUser'@'localhost' \  
+IDENTIFIED BY '$SCRMPass';"  
+#Create the SuiteCRM database  
+mysql -u root -p$RPass -e "CREATE DATABASE $SCRMDb;"  
+mysql -u root -p$RPass -e "GRANT ALL ON $SCRMDb.* TO \  
+$SCRMUser@localhost IDENTIFIED BY '$SCRMPass';"  
+mysql -u root -p$RPass -e "FLUSH PRIVILEGES;"  
+#Install required software for SuiteCRM  
+add-apt-repository ppa:ondrej/php -y  
+apt-get update  
+apt-get install php$PHP_VERSIONlibapache2-mod-php$PHP_VERSION \  
+php$PHP_VERSION-common php$PHP_VERSION-mysql php$PHP_VERSION-gmp \  
+php$PHP_VERSION-curl php$PHP_VERSION-intl php$PHP_VERSION-mbstring \  
+php$PHP_VERSION-xmlrpc php$PHP_VERSION-gd php$PHP_VERSION-bcmath \  
+php$PHP_VERSION-imap php$PHP_VERSION-xml php$PHP_VERSION-cli \  
+php$PHP_VERSION-zip -y  
+#Update php.ini file with required settings  
+short_open_tag=On  
+memory_limit=256M  
+upload_max_filesize=100M  
+max_execution_time=360  
+for key in short_open_tag memory_limit upload_max_filesize max_execution_time  
+do  
+  sed -i "s/^\($key\).*/\1 $(eval echo = \${$key})/" \  
+/etc/php/$PHP_VERSION/apache2/php.ini  
+done  
+#Restart apache  
+systemctl restart apache2.service  
+#Test file created for debugging  
+echo "<?php phpinfo( ); ?>" | sudo tee /var/www/html/phpinfo.php  
+#Download and install latest SuiteCRM. Composer v2 does not work with Suitecrm.  
+file_url="<%= archives.link('Software Archive', 'SuiteCRM-7.14.3.zip',1200) %>"  
+wget $file_url-O "./SuiteCRM-7.14.3.zip"--no-check-certificate  
+apt-get install unzip -y  
+unzip SuiteCRM-7.14.3.zip -d /var/www/html  
+mv /var/www/html/SuiteCRM-7.14.3/ /var/www/html/suitecrm  
+cd/var/www/html/suitecrm  
+chown -R www-data:www-data /var/www/html/suitecrm/  
+chmod -R 755 /var/www/html/suitecrm/
+```
+```
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/installtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E9CE3244-8398-46FB-B6BD-70FBB18B51D8-high.png)
+
+Finally, we’ll add the Apache restart Task. Configure a new Task as shown below:
+
+- **NAME:** suitecrm apache restart
+- **LABELS:** SUITECRM
+- **TYPE:** Shell Script (The proper fields will appear once the Type is set)
+- **RESULT TYPE:** None
+- **SUDO:** Checked
+- **SOURCE:** Local
+- **CONTENT:** Expand the section below to see the script content
+- **EXECUTE TARGET:** Resource
+
+### Restart Task Content
+
+```
+```
+a2ensite suitecrm.conf  
+a2enmod rewrite  
+systemctl restart apache2.service
+```
+```
+
+![../../_images/restarttask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B205F51E-1A3C-4DEB-8FA7-7E59213395B6-high.png)
+
+## Create the Provisioning Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. We won’t use any Operational Workflows here but these Workflows can be run on-demand as needed or set to run on a recurring time schedule (like a cronjob). Provisioning Workflows are associated with an Instance at provision time and will automatically run when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In this case, we can create a Provisioning Workflow with our Tasks in the provisioning phase so that SuiteCRM will be installed, the Apache config file will be set, and the Apache service will be restarted automatically when the Instance is provisioned.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** SuiteCRM - single node
+- **LABELS:** SUITECRM
+- **PLATFORM:** Linux
+- **TASKS:** Expand the Provision section and begin typing the names of our Tasks in the Search field. After adding them, they can be reordered but they should be set such that the install script is run first, the file template is set second, and the Apache restart is run last
+
+Click SAVE CHANGES
+
+![../../_images/provworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4CD1EFEA-943C-40B9-AC3E-7431042CBD21-high.png)
+
+## Create a Custom Library Item
+
+Having created Cypher entries, Inputs, and Tasks, we’re ready to put them all together into a custom Instance Type for our HPE Morpheus Enterprise Library. We’ll create a new SuiteCRM Library entry that will be available to some or all users (depending on Role permissions) in the provisioning wizard. This will allow them to stand up single node SuiteCRM appliances with just a few clicks. In HPE Morpheus Enterprise there are three layers to such Library items: Instance Types, Layouts, and Node Types. We’ll create the Instance Type first:
+
+Navigate to Library > Blueprints > Instance Types and click + ADD. Enter the following configurations:
+
+- **NAME:** Custom SuiteCRM
+- **CODE:** custSuiteCRM
+- **CATEGORY:** Apps
+- **LABELS:** SUITECRM
+- **ICON:** If desired, search the file system on your local computer for a SuiteCRM logo icon for easier identification of this Instance Type at provision time
+
+![../../_images/instype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0E99A5BF-3532-4F17-94B0-F80D1F98A54F-high.png)
+
+Click SAVE CHANGES. After creating the Instance Type, click into it and then click + ADD LAYOUT from the Instance Type Detail Page. A Layout specifies the technology the Instance will run on, in this case VMware. It’s possible to have multiple Layouts associated with an Instance Type which can be selected depending on the chosen Cloud the user might be provisioning on. Configure the Layout as follows:
+
+- **NAME:** SuiteCRM - Single Node
+- **VERSION:** 7.14.3
+- **LABELS:** SUITECRM
+- **CREATABLE:** Checked (If unchecked, this Layout won’t be an available option at provision time)
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **MINIMUM MEMORY:** 2048 (If entered, this value will override any memory requirement set on the virtual image to ensure your Instance service will run properly)
+- **WORKFLOW:** Select the Workflow we’ve already created, “SuiteCRM - single node”
+- **INPUTS:** Search and find the three custom Inputs we created earlier
+
+![../../_images/layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-87B329F6-4D66-4D7C-8D9B-65796365436F-high.png)
+
+Once the configurations are entered, click SAVE CHANGES. After creating the Layout, we need to associate a Node Type. From the Layout Detail Page, click + ADD within the “VM Types” section. The term VM Types is sometimes used in place of Node Types in HPE Morpheus Enterprise but they refer to the same thing and are fully interchangeable. Node Types are compute images and will be relevant types for the destination Cloud technology (AMIs for provisioning on AWS or VMware virtual images for vCenter Clouds, etc.) In this case, we’re simply going to point to a default Ubuntu image in an appropriate format which is supplied by HPE Morpheus Enterprise. You can associate Node Types with your own custom virtual images as well when needed. Set the following configurations on the new Node Type:
+
+- **NAME:** Custom Ubuntu 22.04 Node
+- **SHORT NAME:** ubuntu2204
+- **VERSION:** 22.04
+- **TECHNOLOGY:** Select the relevant technology for your environment
+- **VM IMAGE:** Select the included Ubuntu 18.04 image
+
+Click SAVE CHANGES
+
+![../../_images/nodetype.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-851F39FE-55AA-4EE3-85A8-94FD5E6ADA2C-high.png)
+
+## Provision the SuiteCRM Instance Type
+
+At this point, the setup is finished and SuiteCRM will be available as an Instance Type option for your users. We’ll go ahead and walk through the provisioning process at this point just to take a look.
+
+To begin provisioning, navigate to Provisioning > Instances and click + ADD. From the list of Instance Types, select the “SUITE\_CRM” Instance Type we just created, click NEXT. From the Group tab, select a Group which contains a destination Cloud relevant to the Instance configuration and then select the Cloud you’d like to provision the app onto. Click NEXT. From the Configuration Tab, select the Layout we created and configure a plan, Resource Pool, and network which makes sense for your environment and the compute needs of the workload. You’ll then notice the Input fields we created where you’ll need to enter a SuiteCRM database name, Username, and Password. Click NEXT. On the Automation tab, we do not need to select a Workflow as our Workflow is already set on the Layout. Click NEXT and click COMPLETE.
+
+![../../_images/provision.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-43E0CE55-E46C-408F-AA4F-F0320E933520-high.png)
+
+## Configure SuiteCRM
+
+SuiteCRM is now ready for its initial setup. In a web browser, go to http://<YOUR\_INSTANCE\_IP > /install.php. You should see the license agreement page and can proceed with the setup steps. SuiteCRM is now up and running. Additional instances of SuiteCRM can be stood up in the future with just a few clicks!
+
+![../../_images/eula.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FA21A2DA-B71D-4C36-BB10-DEFF401E4AEA-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json b/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
new file mode 100644
index 0000000..fa3325c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+  "title": "Capacity and Planning",
+  "ordinal": 13,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.html",
+  "topic_cluster": {
+    "clustering_title": "Capacity and Planning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA",
+        "clustering_title": "Capacity and Planning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md b/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
new file mode 100644
index 0000000..5588f06
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CE37FD46-EDFF-4250-9EA7-4F394048EFAA.md
@@ -0,0 +1,33 @@
+# Capacity and Planning
+
+There are many different architectures HPE Morpheus Enterprise can be deployed as. However, the most common architectures are an All-In-One (AIO) single node and a 3-Node Highly Available (HA) cluster. These architectures can have many variables to determine the capacity of each node, as each users’ environment will be different. Example factors that determine the capacity are:
+
+- Number of virtual machines (VMs)/systems/instances that HPE Morpheus Enterprise will manage, also know as Workload Elements (WLEs)
+- If the WLEs will have agents installed
+- The number of clouds added to HPE Morpheus Enterprise
+- The technologies used, such as: Kubernetes, Terraform, ARM, etc.
+- The number of concurrent worflows
+- Number of active users
+
+Although there are many factors that can contribute to the capacity planning, even outside the list above, below are recommended initial specifications.
+
+Table 1. Recommendations
+
+        | Architecture | # of CPUs per node | Memory (GB) per node | Local Storage (GB) per node | Shared Storage (NFS) | Supported WLEs |
+| --- | --- | --- | --- | --- | --- |
+| AIO | 4 | 16 | 200 | N/A | 5,000 |
+| AIO | 4 | 32 | 400 | N/A | 10,000 |
+| 3‐Node HA | 4 | 16 | 400 | 50 | 10,000 |
+| 3‐Node HA | 8 | 32 | 400 | 50 | 20,000 |
+
+In the above recommendations, an AIO can support ~5,000 WLEs with agents installed at the base requirements. Due to ease of installation and maintenance, an AIO architecture should be strongly considered for environments that will manage less than a few thousand WLEs. Consider the significantly increased complexity of multi-node architectures and opt for an AIO appliance unless there is a specific compelling reason (such as high capacity needs or a zero downtime requirement) to select anything else. However, the AIO architecture cannot tolerate failure and will be unavailable during upgrades, unlike the 3-Node HA, which is the likely choice for ensuring zero downtime upgrades and high availability. A 3-Node HA architecture could support ~15,000 WLEs with agents installed (3 x 5,000) at the base requirements but it is best to consider the possible loss of a node, which would be an effective support of ~10,000 WLEs with agents installed (2 x 5,000).
+
+In the case of both the AIO and 3-Node HA architectures, HPE Morpheus Enterprise nodes can be **scaled up** to a maximum of 32GB of memory, which can support more WLEs per node. Adding more CPU or memory is possible, without adding additional nodes. Also, in the case of the 3-Node HA architecture, HPE Morpheus Enterprise can be **scaled out**, which can support additional WLEs per node added and provides additional redundancy, whereas the AIO configuration cannot add additional nodes. The 3-Node HA architecture should always have an odd number of nodes for quorum.
+
+IMPORTANT
+
+Customer architectures and requirements will vary. Please contact your account manager if you wish to deploy or transition to a HA environment, which can help right-size the environment
+
+Additional information around the various architectures can be found here:
+
+[Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html) [HA Installation Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1061ACC-BCAF-4F7C-A413-2219EAFB7983.html)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json b/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
new file mode 100644
index 0000000..c7730a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+  "title": "Azure Active Directory SSO (SAML)",
+  "ordinal": 283,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.html",
+  "topic_cluster": {
+    "clustering_title": "Azure Active Directory SSO (SAML)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E",
+        "clustering_title": "Azure Active Directory SSO (SAML)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md b/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
new file mode 100644
index 0000000..5d9c3e1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CEEF0E93-5C7D-40EC-859B-BEDA46C86B1E.md
@@ -0,0 +1,204 @@
+# Azure Active Directory SSO (SAML)
+
+Azure Active Directory Single Sign-on can be added as a Identity Source in HPE Morpheus Enterprise using the SAML Identity Source Type. The Azure AD SSO configuration is slightly different than other SAML providers, and this guide will assist in adding a Azure AD SSO Identity Source.
+
+## Create Azure Enterprise Application
+
+### Procedure
+
+1. Login to the [Azure Portal](https://portal.azure.com)
+2. Navigate to: Azure Active Directory  >  Enterprise Applications
+3. Click the `+ New application` button at the top
+4. Click the `+ Create your own application` button at the top
+5. Ensure `Integrate any other application you don't find in the gallery (Non-gallery)` is selected and enter a name for the app. Common examples are: `MorpheusSSO`
+6. Click the `Create` button at the bottom and wait for it to complete
+7. Once created, you’ll be in the `Overview` of the application created. Navigate to the `Single sign-on` section from the left pane
+8. Choose `SAML` as the Single sign-on method
+9. Copy both the `Login URL` and `Logout URL` in Step 4, we’ll need these in some of the next steps
+10. Before we can continue configuring the application, the configuration needs to be generated in HPE Morpheus Enterprise for more data
+
+## Create an Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### About this task
+
+Azure requires inputting the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` in the Azure SSO configuration before it provides the Endpoints and Certificate necessary to add the Integration into HPE Morpheus Enterprise. In order to get the `Identifier (Entity ID)` and `Reply URL (Assertion Consumer Service URL)` to input into Azure SSO configuration, we need to create a `Azure AD SAML SSO` integration in HPE Morpheus Enterprise first.
+
+To add the integration:
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Click the IDENTITY SOURCES button in the Tenant detail page
+5. Click the + ADD IDENTITY SOURCE button
+6. Select `Azure AD SAML SSO` from the `TYPE` dropdown
+7. Add 
+
+   - Name
+   - (Optional) Description
+   - Paste the `Login URL` copied from Azure into the `LOGIN REDIRECT URL` field
+   - Paste the `Logout URL` copied from Azure into the `SAML LOGOUT REDIRECT URL` field
+8. This is the minimum information needed for now, which will let us generate the details needed from HPE Morpheus Enterprise. We’ll return to this configuration page later to enter more information.
+9. Click the SAVE CHANGES button 
+
+   IMPORTANT
+
+   Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+   Upon saving, the Entity ID (`Identifier (Entity ID)`) and SP ACS URL (`Reply URL (Assertion Consumer Service URL)`) will be provide in the Identity Source list view. Copy these for use in Azure SSO configuration.
+
+   ![../../_images/saml_setup.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C3ECE586-166D-49EB-85B2-42D73E125E79-high.png)
+
+## Configure Azure Enterprise Application
+
+### About this task
+
+This guide assumes an Azure AD Enterprise Application has already been created. Please refer to documentation above, if this has not already been configured.
+
+### Procedure
+
+1. Navigate to: Azure Active Directory  >  Enterprise Applications  >  Single sign-on
+2. Choose `SAML` as the Single sign-on method
+3. On Step 1 (`Basic SAML Configuration`), click the `Edit` button and enter the following: 
+
+   - Identifier (Entity ID)
+     :   Enter the `Entity ID` URL from the HPE Morpheus Enterprise Identity Source Integration above
+   - Reply URL (Assertion Consumer Service URL)
+     :   Enter the `SP ACS URL` from the HPE Morpheus Enterprise Identity Source Integration above
+   - Logout URL
+     :   Enter the following format: `https://yourUrl/login/` If this is a sub tenant, the format may instead be the following: `https://yourUrl/login/account/1` The login URL can be found under IDENTITY SOURCES in the tenant
+4. On Step 2 (`Attributes and Claims`), click the `Edit` button
+5. Click the `Add a group claim` button at the top
+6. Choose `All groups` and ensure `Group ID` is selected for the `Source attribute` dropdown 
+
+   NOTE
+
+   You can also choose `Security groups`, which ever makes more sense for the organization
+7. Close the pane and return to the Enterprise Application in the `Single sign-on` section
+8. On Step 3 (`SAML Certificates`), click the `Download` link next to `Certificate (Base64)` and `Federation Metadata XML` 
+
+   NOTE
+
+   The files will download, keep them available for later configuation in HPE Morpheus Enterprise
+9. Navigate to `Users and Groups` in the left pane
+10. Click the `Add user/group` button
+11. Add Azure groups to this application that will be able to login to HPE Morpheus Enterprise 
+
+    NOTE
+
+    the object ID for each of these groups, as they will be used later when configuring HPE Morpheus Enterprise to map the group to roles
+12. Once groups have been added, click the `Assign` button at the bottom
+
+## Configure the Azure AD SAML Integration in HPE Morpheus Enterprise
+
+### Procedure
+
+1. Login to HPE Morpheus Enterprise using `Username and Password`, as usual
+2. Navigate to Administration > Tenants
+3. Click a tenant hyperlink
+4. Select IDENTITY SOURCES in the Tenant detail page
+5. Click the pencil (edit) next to the integration created previously
+6. Ensure the `SAML REQUEST` field is set to `Self Signed` 
+
+   NOTE
+
+   A custom RSA signature can be used here if needed, if required by the orgnaization
+7. Ensure the `SAML RESPONSE` field is set to `Validate Assertion Signature` 
+
+   NOTE
+
+   With this setting, if the assertion signature ever changes in the Azure Enterprise Application, this would need to be updated to match
+8. Edit/view the downloaded `Federation Metadata XML` (`.xml` extension) file from the previous section 
+
+   NOTE
+
+   It is recommended to use `Microsoft Edge`, or another browser, to view the contents
+9. In the `Federation Metadata XML` file, locate the `<X509Certificate> </X509Certificate>` under the `<Signature>` section. Copy the entire contents between the `<X509Certificate>` and `</X509Certificate>`, it is very long
+10. Paste the value copied from the `Federation Metadata XML` file into the `Public Key (Optional)` box, below the `SAML RESPONSE` dropdown
+
+## Configure Role Mappings
+
+### About this task
+
+Role mappings will map Azure AD Groups to Morpheus Roles. Azure AD users will be assigned Roles in HPE Morpheus Enterprise upon signing in based on their Group Membership in Azure AD.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+DEFAULT ROLE
+:   Role a Azure AD user will be assigned by default upon signing in to HPE Morpheus Enterprise using this Identity Source.
+
+REQUIRED AZURE AD GROUP OBJECT ID
+:   Object ID of Azure AD Group a user must be a member of to be authorized to sign in to HPE Morpheus Enterprise. Users not belonging to this Group will not be authorized to login to HPE Morpheus Enterprise. This field is optional, and if left blank, any user from the Azure AD App will be able to sign in to HPE Morpheus Enterprise and will be assigned the Default Role if no Role Mappings match AD Group membership.
+
+GROUP ASSERTION ATTRIBUTE NAME
+:   Enter `http://schemas.microsoft.com/ws/2008/06/identity/claims/groups` for Azure AD SSO
+
+Additional Role Mappings
+:   The existing Roles in HPE Morpheus Enterprise will be listed. To map a HPE Morpheus Enterprise Role to an Azure AD Group, enter the Object ID of the desired Azure AD Group in the Role Attribute Value field for the corresponding HPE Morpheus Enterprise Role.
+
+IMPORTANT
+
+Use an Azure Groups `Object ID`, not Group name, when entering Role Mappings. Example: `7626a4a2-b388-4d9b-a228-72ce9a33bd4b`
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added. The Identity Source can be edited anytime to deactivate or change Role Mappings or other values.
+
+NOTE
+
+If Role mappings are edited after Azure AD SSO users have signed into HPE Morpheus Enterprise, currently logged in users will need to log out of HPE Morpheus Enterprise for the new Role mappings to take effect, when applicable.
+
+### Procedure
+
+1. Under the `Role Azure Group Mappings` secton, verify the `DEFAULT ROLE` dropdown has the role in HPE Morpheus Enterprise selected that all users will be assigned by default 
+
+   - It is recommended that this role contains no permissions, which ensures that anyone who authenticates gets no access
+2. Under the `Role Azure Group Mappings` secton, you will see role names listed. Next to these are text boxes with `Assertion Attribute Mappings` inside. Enter group object IDs from Azure into these text boxes. This will map the Azure AD groups to specific roles in Morpheus
+3. Finally, click `Save Changes` at the bottom of the page 
+
+   Here is an example of the configuration above:
+
+   ![../../_images/saml_setup_complete.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5666456C-8FE1-4305-816E-FD051CC4636F-high.png)
+
+## Azure Group Lookups
+
+When a user in azure ad has more that 150 group attributes, Azure does not include the group claims in the SAML response, and HPE Morpheus Enterprise is required to query Microsoft Graph to obtain the users group attribute values. When there are users that are members of more that 150 groups, populate the `Azure Group Lookups` section in order for those users to be able to use the Azure AD SAML SSO integration, otherwise no groups will be obtained and proper role mappings cannot occur.
+
+AZURE TENANT ID
+:   Add Azure AD Tenant ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Tenant ID
+
+AZURE APP ID
+:   Add Azure AD Application (Client) ID if user group membership will exceed 150. See [Copy Directory (tenant) and Application (client) IDs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-9FD4BFE9-1725-42FF-8EFE-5F297A4D152D) for information on obtaining an Azure AD Application (Client) ID
+
+AZURE APP SECRET
+:   Add Azure Application (Client) Secret if user group membership will exceed 150. See [Generate a Client Secret](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-76D48C9A-CE72-4BB0-B725-DBD8A9469FFB.html#GUID-0A7984C3-E094-45D6-B2D9-ED3179A79988) for information on creating an Azure Application (Client) Secret
+
+ROLE LINK ATTRIBUTE NAME
+:   default: <http://schemas.microsoft.com/claims/groups.link>. This is not normally changed.
+
+## Logging Into HPE Morpheus Enterprise with Azure AD SAML
+
+### Procedure
+
+1. Navigate to the HPE Morpheus Enterprise URL
+2. A new button will appear to allow sign-in using Azure AD SAML, with the same name as the integration. Click the button 
+
+   ![../../_images/sign_in_page.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1FEC124E-FF68-4E72-9872-1D336777E8E5-high.png)
+3. Sign-in with your Microsoft/Azure account 
+
+   ![../../_images/ms_signin.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF8B57F9-055B-4A8C-AEB5-95ABA09BD3DF-high.png)
+
+   NOTE
+
+   If no local users other than the System Admin have been created, “USERNAME AND PASSWORD” option will not be displayed, only the SAML option.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json b/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
new file mode 100644
index 0000000..5ea5cf0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+  "title": "Adding Functionality Through Operational Workflows",
+  "ordinal": 366,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Functionality Through Operational Workflows",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB",
+        "clustering_title": "Adding Functionality Through Operational Workflows"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md b/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
new file mode 100644
index 0000000..844bf70
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.md
@@ -0,0 +1,113 @@
+# Adding Functionality Through Operational Workflows
+
+Operational Workflows, in HPE Morpheus Enterprise, are logically arranged sets of individual automation Tasks designed to accomplish some function. They can be executed on a one-off basis as needed or set on a timed execution schedule, similar to a cron job. While they’re often used to orchestrate some facet of cloud resource management, they can also be used to speed and standardize creation of HPE Morpheus Enterprise constructs.
+
+As an example case for this guide, we’ll create an Operational Workflow which will allow Primary Tenant administrators to create Groups within Subtenants. This is not natively-available functionality as Groups are not a tenanted construct in HPE Morpheus Enterprise. They exist solely within the Tenant that created them and cannot be shared or viewed by others.
+
+In this guide, we’ll use the following HPE Morpheus Enterprise constructs:
+
+- Groups
+- Cypher
+- Tasks
+- Workflows
+- Inputs
+- HPE Morpheus Enterprise API
+
+## Initial Considerations
+
+Since we’re creating Groups in a second Tenant, you’ll need to have at least one other Tenant in your appliance (Administration > Tenants). You’ll also need access to a user account within the Subtenant which has rights to create Groups. You could use a pre-existing user account or create a service user for automated processes like this one.
+
+Impersonate or log in with your service account and create an API Key. API Keys are created by clicking on the user’s name in the upper-right corner of the application window, then clicking User Settings. On the User Settings page, click API ACCESS. Next to one of the entries (it doesn’t matter which one but be careful about overwriting a key that is already in use), click ACTIONS and then Generate. Copy the Access Token into a secure place you can retrieve it from in the next step. You will not be able to see this key again after closing the modal containing the API Keys. Return to your primary HPE Morpheus Enterprise account in the original Tenant to continue with the guide.
+
+## Create Cypher
+
+Cypher is a secure key/value store in HPE Morpheus Enterprise. Using Cypher, we can securely store passwords and other secret values (such as API keys) which can then be called into automation Tasks and templates. Here we will store the API Key for our service account user so we can call it into automation scripts in a later step. In the HPE Morpheus Enterprise UI, go to Tools > Cypher and click + ADD.
+
+There are a number of different types of Cypher keys, which are useful in different contexts. Here we’ll use the “secret” type which allows us to enter some known value which can be securely accessed later. Enter the following:
+
+- **KEY:** secret/subusertoken
+- **VALUE:** Enter HPE Morpheus Enterprise API Key for the Subtenant user
+- **LEASE:** 0 (Lease time is given in seconds, with “0” being unlimited)
+
+Click SAVE CHANGES
+
+![../../_images/createcypher.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EF5395A9-F584-4E5D-B77C-11ED02BF2822-high.png)
+
+## Create Inputs
+
+Inputs are custom input fields which can be added to Layouts, Instance Types, Workflows, and other constructs in HPE Morpheus Enterprise. The input can be consumed as variables within templates and scripts. In this case, the Inputs will be associated with our Operational Workflow. We will create three so the user can define a name for the new Group and optionally provide a code and/or location value if desired.
+
+In HPE Morpheus Enterprise UI, navigate to Library > Options > Inputs. Click + ADD. Complete the following fields:
+
+- **NAME:** Subtenant Group Name (The friendly name for the Input object in HPE Morpheus Enterprise)
+- **FIELD NAME:** subgroupname (The internal property which the input value is assigned to)
+- **TYPE:** Text (The input type, in this case an open text field for the user)
+- **LABEL:** Subtenant Group Name (The label the user sees next to the input field)
+- **REQUIRED:** Checked (A name value is required for our Group so this Input should be marked required. The other two Inputs we’ll create will not be required as they are optional fields when creating a Group)
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createinput.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1081A234-C0CA-4B22-82F1-EE91843663DD-high.png)
+
+Create two more Inputs in a similar fashion with the following configuration:
+
+### Code Input
+
+- **NAME:** Subtenant Group Code
+- **FIELD NAME:** subgroupcode
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Code
+- **HELP BLOCK:** Optional Code Value (I opted to enter help block text to make it clearer to the user that this is an optional input)
+- **REQUIRED:** Unchecked
+
+### Location Input
+
+- **NAME:** Subtenant Group Location
+- **FIELD NAME:** subgrouplocation
+- **TYPE:** Text
+- **LABEL:** Subtenant Group Location
+- **HELP BLOCK:** Optional Location Value
+- **REQUIRED:** Unchecked
+
+## Create Task
+
+Tasks, in HPE Morpheus Enterprise, are individual automation scripts. They can be pieced together into Workflows (as we’ll see later) to create more comprehensive automation packages. They can be written in a number of different languages (including BASH, Powershell, Python, Javascript, and more) or to accomplish specific functions like restarting a server or sending an email notification. In this case, I’ve written a Python script outside HPE Morpheus Enterprise and tracked it in a Github repository. Since my Github account is integrated with HPE Morpheus Enterprise, I can simply refer to the script in a new Task. This prevents me from having to cut and paste code and also ensures the latest version of my code in executed every time the Task is invoked. Integrating with version control is optional, for simplicity you can also draft a quick script directly in HPE Morpheus Enterprise if you’d prefer. If you want to view, copy, or fork the code, you can see it [here](https://github.com/ahark86/morpheus-group-create/blob/master/main.py). New Github integrations can be added in Administration > Integrations.
+
+Navigate to Library > Automation > Tasks and click + ADD. Create a new Task with the following configuration:
+
+- **NAME:** Subtenant Group Create - Task
+- **TYPE:** Python Script (Once Type is selected, available fields will be updated to those specific to the chosen type)
+- **RESULT TYPE:** None
+- **SOURCE:** Repository (Select Local to draft or paste code directly into HPE Morpheus Enterprise)
+- **FILE PATH:** main.py (In my case, the script is in the root of the repository so I can simply refer to it by filename)
+- **COMMAND ARGUMENTS:** Optional command line arguments for the Python script. In my case, I’m passing the HPE Morpheus Enterprise API Key from Cypher as a command line argument (as seen in the screenshot) and consuming it in my code using the sys module, which is part of the Python standard library. There are other ways to consume Cypher secrets in Python scripts as well, which are laid out in a [Knowledge Base article](https://support.morpheusdata.com/s/article/How-to-use-stored-cypher-secrets-in-python-task?language=en_US).
+- **ADDITIONAL PACKAGES:** List packages used which are not part of the standard Python library
+
+Once done, click SAVE CHANGES.
+
+![../../_images/createtask.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5C031817-0262-4BF2-919F-0B9677FB0559-high.png)
+
+## Create Operational Workflow
+
+HPE Morpheus Enterprise Workflows pull multiple Tasks together into a logical group. There are two types of Workflows: Operational and Provisioning. Provisioning Workflows (which aren’t used in this guide) are associated with an Instance at provision time and will automatically run the appropriate Tasks when the Instance reaches certain phases of its lifecycle, such as during provisioning, teardown, startup, or shutdown. In our case, we need an Operational Workflow which are run on-demand when needed or on timed intervals.
+
+Navigate to Library > Automation > Workflows and click + ADD. Set the following configurations:
+
+- **NAME:** Subtenant Group Create
+- **PLATFORM:** All
+- **TASKS:** Subtenant Group Create - Task
+- **INPUTS:** Find Subtenant Group Name, Subtenant Group Code, and Subtenant Group Location using the typeahead field. I think it makes most sense to order them with Name first but it’s not required
+
+Once done, click SAVE CHANGES
+
+![../../_images/createworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-680497EC-0916-4C46-9821-E3DC1A379126-high.png)
+
+## Execute Workflow
+
+After saving the new Operational Workflow, you’ll be left on the Workflows list page. From here we can try the new Workflow. Click on the gear icon at the far-right part of the row, then click Execute. Our three Inputs should be visible. We can see the Name field is marked as required (as we configured) and our help block text underneath the optional Inputs. Complete each field (Context Type can be left at None) and click EXECUTE.
+
+![../../_images/executeworkflow.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E459787E-142E-4A07-819A-E280C1C9021C-high.png)
+
+Once again login in as or impersonate your service account user within the Subtenant. Navigate to Infrastructure > Groups and inspect the list. You should now see that our Group has been created here.
+
+![../../_images/grouplist.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1D03AA1C-1895-4C61-86EB-10C99456022D-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json b/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
new file mode 100644
index 0000000..f4f17a9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+  "title": "CLI Troubleshooting",
+  "ordinal": 348,
+  "parent_title": "Troubleshooting",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.html",
+  "topic_cluster": {
+    "clustering_title": "CLI Troubleshooting",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463",
+        "clustering_title": "CLI Troubleshooting"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md b/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
new file mode 100644
index 0000000..9749045
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CFD1C4B1-6442-4CCC-AAFD-31E75B29D463.md
@@ -0,0 +1,11 @@
+# CLI Troubleshooting
+
+If you have installed the HPE Morpheus Enterprise CLI successfully and get a successful login but see this error `Error Communicating with the Appliance. SSL_connect returned=1 errno=0 state=error: certificate verify failed`
+
+run the command
+
+```
+```
+morpheus remote update {appliancename} --insecure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json b/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
new file mode 100644
index 0000000..c213555
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+  "title": "Tasks",
+  "ordinal": 104,
+  "parent_title": "Automation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.html",
+  "topic_cluster": {
+    "clustering_title": "Tasks",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D",
+        "clustering_title": "Tasks"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md b/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
new file mode 100644
index 0000000..43ad498
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-CFE82665-23A3-49F2-9202-1C2A720CC64D.md
@@ -0,0 +1,10 @@
+# Tasks
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html)**
+- **[Common Options](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BB270862-D56D-4B6F-86B7-030ED273E907.html)**
+- **[Task Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7FAD1058-65F1-409A-9BF8-16AFA4A5C9D6.html)**
+- **[Task Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-87CB98DB-3915-4176-822C-E86A5AA54C4D.html)**
+- **[Task Management](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B9045AFD-6F61-42D7-B5A2-599F56715C4C.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json b/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
new file mode 100644
index 0000000..8bc9ebd
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+  "title": "Users & User Groups",
+  "ordinal": 308,
+  "parent_title": "Administration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.html",
+  "topic_cluster": {
+    "clustering_title": "Users & User Groups",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D",
+        "clustering_title": "Users & User Groups"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md b/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
new file mode 100644
index 0000000..173a481
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D25F3CF3-4DFE-43B6-BFFF-0EE91DE5D63D.md
@@ -0,0 +1,6 @@
+# Users & User Groups
+
+**Subtopics**  
+
+- **[Users](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B385B91E-1FC1-4458-A7C4-E31E68EDA123.html)**
+- **[User Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-589A7663-2242-4FBE-9214-FE0F91A29972.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json b/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
new file mode 100644
index 0000000..b4a0fbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+  "title": "Creating Instances",
+  "ordinal": 84,
+  "parent_title": "Instances",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Instances",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79",
+        "clustering_title": "Creating Instances"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md b/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
new file mode 100644
index 0000000..1b51298
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D28B812E-A196-41C2-8E1D-8FEFFC96BA79.md
@@ -0,0 +1,41 @@
+# Creating Instances
+
+The Instance catalog is the one-stop shop for selecting items to be provisioned and pieced together. It contains not only basic container and VM options but also tailored services for SQL databases, NoSQL databases, cache stores, message busses, web servers, and even full-fledged apps. The list contains a lot of items to choose from and they are represented to the user based on what provisioning engines are enabled and integrated in the HPE Morpheus Enterprise environment.
+
+To get started, simply click the + Add button in the upper right of the Provisioning > Instances section. A modal will display allowing the catalog to be searched. Once an item is selected it is just a matter of following the steps through the wizard.
+
+TIP
+
+The Instance catalog can be customized via role-based access control (RBAC) thereby restricting access to non-sanctioned catalog items, as well as added to via the Library section. It is completely customizable.
+
+The next step will ask for a Group and Cloud to be selected. The Group is an abstract representation that can contain multiple cloud integrations. Clouds can be in multiple Groups and Groups are also useful for using RBAC to restrict provisioning access and set retainment policies. If the environment is new and these do not yet exist, it may be advisable to refer to one of our starter guides, such as the guide on getting started with HPE Morpheus Enterprise and [VMware](https://docs.morpheusdata.com/en/latest/getting_started/guides/vmware_guide.html). The wizard continues by allowing us to choose a name for the Instance as well as an environment.
+
+NOTE
+
+Currently the Environment option is mostly useful for presenting the user with informative metadata around the Instance when coming back to it later.
+
+Moving on, it is now time to configure the Instance. Depending on the Instance Configuration that is chosen, fields will change. This can include cloud-specific fields (i.e. Datastore for VMware or Network). There will also be options like setting an initial user account. Some of these fields are optional and will be represented as such.
+
+Configuration options provided in this screen are very powerful. An example is MySQL where a Master/Slave or Master/Master layout can be selected. These configurations will automatically deploy two MySQL VMs or containers and link them together to provide replication. These types of configurations exist for a wide range of Instance types and are optimized for high performance and scale. It is even possible to provision entire sharded MongoDB clusters.
+
+One last step before the Instance can be provisioned is the Automation step. This wizard step may or may not appear depending on the capabilities of the Instance type or previous configurations in the account. It is here one can easily select a post-provisioning workflow to run (see more on Tasks and Workflows elsewhere in HPE Morpheus Enterprise documentation), assign a load balancer, or even configure the backup job that gets created.
+
+Now that the steps are completed for provisioning the selected Instance type, simply review your selections and complete. The Instance will automatically show up in the Instances list and its provisioning state will be represented. Depending on what was provisioned this step can range from seconds to minutes (typically a container configuration will be rather quick if the Instance type has previously been provisioned before).
+
+## Converting Discovered Resources to Managed Instances
+
+When creating new cloud integrations (or updating existing ones), users may opt for HPE Morpheus Enterprise to onboard any existing resources that currently reside in the Cloud. For example, these may be virtual machines that exist on vCenter hosts prior to integration with HPE Morpheus Enterprise, EC2 instances pre-existing on an Amazon AWS account, or virtual machines that are running on a KVM host. With the Add/Edit Cloud modal open, mark INVENTORY EXISTING INSTANCES for HPE Morpheus Enterprise to automatically onboard these resources. Not only will HPE Morpheus Enterprise inventory these instances at the time the cloud is integrated (or updated), it will also continue to poll the target cloud every five minutes (by default) for newly added or removed servers. Users can see these discovered servers by looking in Infrastructure > Compute. Depending on the type of resource, it may appear on the Virtual Machines tab, the Containers tab, or another tab. Additionally, we can see a list of discovered servers on Cloud detail pages (Infrastructure > Clouds > Selected Cloud). Just click on the tabs for VMs, Containers or Hosts tab. Discovered resources will be indicated as such whereas containers which are associated with a managed Instance will be marked as a “Managed”.
+
+Additionally, HPE Morpheus Enterprise allows users to convert discovered resources into managed Instances. Begin from the server detail page (Infrastructure > Compute > Virtual Machines > selected machine) and from the ACTIONS menu select “Convert to Managed”. At this point, we must make a number of selections:
+
+- Assign to the primary Tenant or one of the Subtenants
+- Select a Group (this dropdown contains a filtered list of Groups which the associated Cloud is in)
+- Username and password for a seeded account
+- Opt to install HPE Morpheus Enterprise Agent or not (for more on HPE Morpheus Enterprise Agent, click [here](https://docs.morpheusdata.com/en/latest/getting_started/functionality/agent/morpheus_agent.html))
+- Select the Instance Type which should be associated with the new Instance containing this VM
+- Select a version number for the Instance (such as 20.04 for a basic Ubuntu Instance)
+- Select a Layout, Instance Types often have multiple Layout configurations
+- Identify the operating system
+- Select a Plan (this dropdown contains a filtered list of plans which correlate to the size of the VM)
+
+Finally, click EXECUTE. Once this process is completed, the server will be indicated as “Managed” in the servers list. Additionally, a new Instance will appear on the Instances List page (Provisioning > Instances). We can now work with it in the same way we can work with any other Instance, such as by adding it to an App or expanding the Instance horizontally with added nodes.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json b/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
new file mode 100644
index 0000000..754b357
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+  "title": "Installing iSUT on Deployed Instances (Optional)",
+  "ordinal": 425,
+  "parent_title": "Firmware and Driver Lifecycle Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.html",
+  "topic_cluster": {
+    "clustering_title": "Installing iSUT on Deployed Instances (Optional)",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC",
+        "clustering_title": "Installing iSUT on Deployed Instances (Optional)"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md b/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
new file mode 100644
index 0000000..d84cff8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D2BBCB6C-328B-4614-A4AA-6F79CC2033DC.md
@@ -0,0 +1,25 @@
+# Installing iSUT on Deployed Instances (Optional)
+
+## About this task
+
+To enable driver inventory and updates within the operating system, iSUT and AMS must be installed on each deployed instance.
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the target instance.
+
+   NOTE
+
+   Since the workflow requires iLO credentials, only one instance can be selected at a time. Multiple instances cannot be targeted for a single iSUT/AMS install.
+3. Click Actions > Run Workflow.
+4. Select the appropriate workflow:
+   1. Download and Install iSUT and AMS (Linux), or
+   2. Download and Install iSUT and AMS (Windows)
+5. Enter the **iLO credentials** for the targeted bare metal server.
+
+   NOTE
+
+   These are iLO credentials, not OS credentials.
+6. Click Execute.
+7. Monitor progress from the History tab until the workflow completes.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json b/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
new file mode 100644
index 0000000..901107f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+  "title": "Alert Rules",
+  "ordinal": 262,
+  "parent_title": "Overview",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.html",
+  "topic_cluster": {
+    "clustering_title": "Alert Rules",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7",
+        "clustering_title": "Alert Rules"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md b/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
new file mode 100644
index 0000000..9ed07e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D2E230F6-81E8-47F6-B38F-1A4DF20E97B7.md
@@ -0,0 +1,12 @@
+# Alert Rules
+
+Alert Rules provide a powerful means to configure who gets notified in various scenarios. These scenarios include targeting specific checks, groups, or apps, and adding the appropriate recipients to be notified during a situation in which those filters are impacted.
+
+- **Min Duration:** This setting delays notification to the recipients by the entered number of minutes required for the incident to be opened.
+- **Min Severity:** Some executives might want to be notified of an outage but only if the severity impact goes above a certain level. This is very useful for scoping escalations.
+
+To add recipients to a rule just start typing their name in the Recipients section towards the button of the edit form. An auto-complete list will start populating with contact names. Once one is selected a delivery method can be selected as well as whether or not they should be notified of any escalation changes and/or closed incidents. The delivery methods available depend on the type of contact information configured for your contact. If needed, contacts can be created or edited in Monitoring  >  Contacts.
+
+TIP
+
+A recipient can be in multiple alert rules and can even be configured to be notified via different methods depending on the rule. A useful example might be to alert someone via email for lower severity incidents but SMS for critical severity levels.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json b/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
new file mode 100644
index 0000000..68530ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+  "title": "Add SSL Certificate",
+  "ordinal": 243,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.html",
+  "topic_cluster": {
+    "clustering_title": "Add SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3100235-F327-4C00-9AF8-F5C974D2F698",
+        "clustering_title": "Add SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md b/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
new file mode 100644
index 0000000..ae1cf17
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3100235-F327-4C00-9AF8-F5C974D2F698.md
@@ -0,0 +1,13 @@
+# Add SSL Certificate
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, click + ADD
+3. From the Add SSL Certificate wizard input the following as needed: 
+
+   - Name
+   - Domain Name
+   - Key File
+   - Cert File
+   - Root Cert
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json b/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
new file mode 100644
index 0000000..2131b14
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+  "title": "Data Stores",
+  "ordinal": 234,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D3548220-4D77-4DBB-8313-CFAD68416264.html",
+  "topic_cluster": {
+    "clustering_title": "Data Stores",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3548220-4D77-4DBB-8313-CFAD68416264",
+        "clustering_title": "Data Stores"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md b/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
new file mode 100644
index 0000000..d70694d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3548220-4D77-4DBB-8313-CFAD68416264.md
@@ -0,0 +1,30 @@
+# Data Stores
+
+Data Stores are logical divisions of underlying storage disk. Organizations may use them to divide and track cloud resources by team or department. When integrating certain Cloud types, HPE Morpheus Enterprise will onboard all existing data stores and administrators can then make them available to Groups or Tenants as needed. At provision time, when applicable based on Cloud and Layout, users can select the data store they wish to provision to.
+
+Here within the Data Store view in the storage section, users can see a list of data stores for each Cloud. In the row for each Cloud, the storage type, associated Cloud, and permissions information are shown.
+
+## Create Data Stores
+
+To a limited extent, data stores can be created from this view. Currently, data store creation is restricted to VMware data store creation on 3Par volumes. In order to create such a data store you would need to first have an integrated 3Par server. See the section on storage servers for more information on setting up this integration.
+
+NOTE
+
+For all other data store types, create the needed data store within the target Cloud and HPE Morpheus Enterprise will automatically sync in the data store on the next Cloud sync. You can force a Cloud sync from the Cloud Detail Page (Infrastructure > Clouds > Selected Cloud > RefreshMenu > Short).
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click +ADD
+- Enter a Name, select a VMware Cloud, select a 3Par Volume, and select a Host Group
+- Manage permissions in the Group Access and Tenant Permissions sections, if needed
+- Click SAVE CHANGES
+
+## Manage Permissions
+
+From this view, users can manage permissions for any data store synced from integrated Clouds. This includes setting which Groups have access to the data store, and which Tenants have access. To edit data store permissions:
+
+- Navigate to Infrastructure > Storage > Data Stores
+- Click ACTIONS > Edit
+- **Groups:** Select “all” Groups or select specific Groups which should have access to the data store
+- **Tenants:** Primary Tenant users can opt to make the data store available to all Tenants (public visibility) or to selected Tenants (private visibility with specific Tenants selected). Subtenant users will only be able to make data stores visible to their own Tenant
+- **Active:** When marked, the data store is active and available for provisioning
+- Click SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json b/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
new file mode 100644
index 0000000..b3a8f3d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+  "title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+  "ordinal": 271,
+  "parent_title": "Migrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0",
+        "clustering_title": "Configuring Windows Workloads (Windows 2022 or later) for Migration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md b/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
new file mode 100644
index 0000000..0bab9c1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D3E08022-96A5-4BD8-9DDF-67D942A361C0.md
@@ -0,0 +1,59 @@
+# Configuring Windows Workloads (Windows 2022 or later) for Migration
+
+Migrating Windows workloads from VMware vCenter Clouds to HVM Clusters using the bulk Migrations feature requires some initial configurations checks. This section goes through an example preparation process for a Windows VM running on vCenter.
+
+This guide makes the following assumptions about the workload to be migrated:
+
+- Configured to boot as EFI or BIOS
+- Virtualization Based Security (VBS) is enabled
+- Secure Boot is enabled
+- Trusted Platform Module (TPM) is disabled
+- The VM has access to the recovery partition (if not, a Windows Recovery Environment disc or installation media may be required to access some of the menus referenced in this section)
+
+Inject VirtIO Drivers
+
+To begin, restart the VMware Windows guest in the [Windows Recovery Environment (Windows RE)](https://support.microsoft.com/en-us/windows/windows-recovery-environment-0eb14733-6301-41cb-8d26-06a12b42770b). In Windows RE, choose a keyboard layout if prompted. Then, select the **Troubleshoot** option. From the Troubleshoot menu, select **Command Prompt**.
+
+Within the Command Prompt session, enter **diskpart** using this command: `diskpart`. Check the disks that are available with `list disk`. At this point, you may receive the message that "There are no fixed disks to show." or the disk with Windows OS might not be listed. If that is the case, follow the steps in the next section to mount the drives. If that is not the case, skip to the following section to continue the process of injecting the VirtIO drivers.
+
+![Enter dispart command line tool and list disks](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6D43B362-18E8-4E21-8CE1-733555398E59-high.png)
+
+Mounting the Drives
+
+From vCenter, mount the VMware Tools installer to the VM using the "Install VMware Tools..." option (**Actions > Guest OS > Install VMware Tools...**). Then, back in diskpart, use the following command to find the CD/DVD-ROM drive letter: `list volume`. Make note of the CD-ROM drive letter, which in the case of this example is drive "D." Exit diskpart with the `exit` command.
+
+![listing volumes in diskpart](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E8FB0956-0BE4-4600-ACC9-DD48E590F2CE-high.png)
+
+Enter the following command to load the storage drivers which will enable you to see the hard disks: `drvload "D:\Program Files\VMware\VMware Tools\Drivers\pvscsi\Win10\amd64\pvscsi.inf"`. Note that the prior command references Windows 10 as the operating system but choose the most appropriate or the latest available. It also references drive "D" which may vary from case to case.
+
+With the driver loaded, once again confirm the disks are mounted with `diskpart` and `list disk`. They're now mounted but the partitions/volumes need drive letters so, while still in diskpart, list the volumes with: `list volume`. In this example case, "Volume 1" is the primary Windows volume. Select the volume and assign a drive letter, in the example case the assigned letter will be "C": `select volume 1` and `assign letter=c`. Check your work by listing the volumes again, the primary Windows volume should be assigned the correct drive letter: `list volume`.
+
+![Assigning a drive letter to a volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8506AA86-13D4-4086-B361-5C5AB0CFC5E9-high.png)
+
+Exit diskpart once again (`exit`) and unmount the VMware Tools installer from the VM back in the vCenter console (**Actions > Guest OS > Unmount VMware Tools Installer**).
+
+Inject VirtIO drivers (cont.)
+
+Download the [latest](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/latest-virtio/) or [stable](https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/stable-virtio/) VirtIO drivers ISO to your local workstation. The latest is recommended but often they are the same. Add the ISO to vCenter either by uploading it to a datastore or to the Content Library. Still in vCenter, mount the ISO using a CD-ROM device on the VM and make sure it's connected. Enter the following commands to inject the VirtIO storage drivers into the Windows boot-start drivers from the mounted ISO: `dism /image:C:\ /add-driver:D:\viostor\2k22\amd64\viostor.inf` and `dism /image:C:\ /add-driver:D:\vioscsi\2k22\amd64\vioscsi.inf`. Note once again that the OS volume will not be assigned the "C" drive letter and the CD-ROM device will not be assigned the "D" drive letter in every case. Similarly, in this example "2k22" is used but that won't be appropriate in every case. If successful, a message will be received that the driver packages were successfully installed. Close the Command Prompt window and click **Continue** to boot Windows once again.
+
+![installing viostor.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A481A334-59CE-42D9-857D-0B5FDEE31BAB-high.png)![installing vioscsi.inf driver](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-10CEA2F9-9885-464E-A57B-303AC913FBBD-high.png)
+
+Prepare the OS
+
+Once logged back in, install the VirtIO drivers in the OS using the ISO, which is still mounted, by navigating to the CD-ROM/DVD-ROM drive. Install `virtio-win-gt-x64.msi` and `virtio-win-guest-tools.exe` from the root of the ISO. Maintain all default selections during the installation. Next, unmount any ISOs still attached to the VM, either by ejecting in Windows or by setting the CD-ROM drive to "Client Device" in vCenter.
+
+Now, shut down the VM. Keep in mind that the VMware Cloud integration may be configured to automatically maintain power state of associated VMs. Navigate to Infrastructure > Clouds and edit the Cloud. Make note of the "AUTOMATICALLY POWER ON VMS" configuration. If checked, you will need to shut down the VM via the product UI tools rather than from the vCenter console or from within the guest OS. Alternatively, you could uncheck "AUTOMATICALLY POWER ON VMS", save changes to the Cloud, and then power down the VM from vCenter or from the guest OS but bear in mind changing this configuration would affect all VMs associated with the Cloud in the product.
+
+Migrating
+
+This completes the preparation steps. From here, create a new Migration Plan that includes the prepared VM and run it. Take a look at the previous section for more information on creating and running Migration Plans.
+
+Post-Conversion
+
+As a final note, bear in mind that the migration tool does not uninstall VMware Tools following conversion, which can lead to start-up errors being surfaced in migrated VMs. In some cases, the VMware Tools installation may become corrupted which prevents simply uninstalling using the Control Panel.
+
+To prevent VMware Tools from executing at startup, within the Windows guest navigate to Settings > Apps > Startup and turn off VMware Tools Core Service. See the example screenshot below for a Windows 2022 Guest.
+
+![Turning off VMware Tools Core Service at Windows guest startup](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EEC38EAD-A903-41BD-8C98-BACAC114BA0E-high.png)
+
+Additionally, you can attempt to uninstall VMware Tools completely using Microsoft recommended processes and tooling for uninstalling stuck programs. See [this article](https://support.microsoft.com/en-us/topic/fix-problems-that-block-programs-from-being-installed-or-removed-cca7d1b6-65a9-3d98-426b-e9f927e1eb4d) from the Microsoft Support for procedure and links to a helpful tool.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json b/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
new file mode 100644
index 0000000..0e34cd5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+  "title": "ServiceNow Monitoring Integration",
+  "ordinal": 505,
+  "parent_title": "Monitoring",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.html",
+  "topic_cluster": {
+    "clustering_title": "ServiceNow Monitoring Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56",
+        "clustering_title": "ServiceNow Monitoring Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md b/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
new file mode 100644
index 0000000..b67a262
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D47A61E0-1F97-4E09-A62C-C8B990640F56.md
@@ -0,0 +1,28 @@
+# ServiceNow Monitoring Integration
+
+NOTE
+
+A ServiceNow Integration must be already configured in Administration > Integrations to enable the ServiceNow Monitoring Integration. Refer to the [ServiceNow](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-D9626410-C815-40BF-94B4-D6A6F34A5E81_2.html) configuration guide for more information.
+
+Enabled
+:   Enables the ServiceNow Monitoring Integration
+
+Integration
+:   Select from a ServiceNow Integration added in Administration > Integrations
+
+New Incident Action
+:   The Service Now action to take when a Morpheus incident is created.
+
+Close Incident Action
+:   The Service Now action to take when a Morpheus incident is closed.
+
+Incident Severity Mapping
+
+Table 1.
+
+    |  |  |
+| --- | --- |
+| HPE Morpheus Enterprise Severity | ServiceNow Impact |
+| Info | Low/Medium/High |
+| Warning | Low/Medium/High |
+| Critical | Low/Medium/High |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json b/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
new file mode 100644
index 0000000..0e31062
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+  "title": "Provisioning",
+  "ordinal": 79,
+  "parent_title": "HPE Morpheus Enterprise",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md b/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
new file mode 100644
index 0000000..240078b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D4CF2219-C8A5-44EA-9EF1-E871454781D1.md
@@ -0,0 +1,14 @@
+# Provisioning
+
+There are several capabilities in the HPE Morpheus Enterprise provisioning engine. Things ranging from application / service deployments via containers, virtual machines, and even bare metal. Deployment management and app template construction are also core aspects of the provisioning engine. Take advantage of custom tasks and workflows within any environment by building tasks and workflows from those tasks. There is a lot of information to cover with regards to provisioning but HPE Morpheus Enterprise makes it intuitive and smooth.
+
+**Subtopics**  
+
+- **[Requirements](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html)**
+- **[Provisioning Concepts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C194B726-EA92-4AE8-8428-C2B1FEA0939E.html)**
+- **[Catalog](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-54B31F8F-2DAD-4126-93B3-52C1F08B61C4.html)**
+- **[Instances](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BE0DA4CA-4746-4343-85BC-E3F52BA9C863.html)**
+- **[Apps](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-9E20F2DB-944A-4496-B4D0-3A82EE22FF69.html)**
+- **[Jobs](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AD96FFBA-4AC1-453A-B207-8D91E15D67BB.html)**
+- **[Executions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-57E6EB88-3EFB-4ED9-8F45-4B1821BD6FF9.html)**
+- **[Code](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json b/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
new file mode 100644
index 0000000..a91cb8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+  "title": "Viewing the Self Service Catalog",
+  "ordinal": 139,
+  "parent_title": "Catalog Items",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing the Self Service Catalog",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55",
+        "clustering_title": "Viewing the Self Service Catalog"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md b/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
new file mode 100644
index 0000000..2bfce7f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D507CF71-5B1B-4509-BBAD-8B807D1F7B55.md
@@ -0,0 +1,5 @@
+# Viewing the Self Service Catalog
+
+The complete Self Service catalog can be viewed by clicking on Catalog from the Provisioning menu. The complete list of items available for the Self Service catalog are shown here but users working in the Service Catalog Persona will see only those allowed based on their user role. In addition to the name and type of each catalog item, we can also see a description and whether not the catalog item is featured or active. Featured items are given special visibility in the Service Catalog Persona and inactive items will not appear as provisioning options.
+
+![../../_images/catalogList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E3A8EE0B-A475-4D68-B6C5-626CB50D9772-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json b/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
new file mode 100644
index 0000000..744df49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+  "title": "Creating Resource Pools",
+  "ordinal": 404,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Resource Pools",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40",
+        "clustering_title": "Creating Resource Pools"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md b/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
new file mode 100644
index 0000000..2499846
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D565793F-EC2F-4DCC-8DB9-30DB5F27EF40.md
@@ -0,0 +1,13 @@
+# Creating Resource Pools
+
+## About this task
+
+This section describes how to create a resource pool within your HPE ProLiant Bare Metal Cloud in Morpheus. Resource pools help you organize and allocate servers for provisioning and management.
+
+## Procedure
+
+1. Navigate to Infrastructure > Clouds. Select the cloud and click the Resources tab.
+2. Click the + Add Resource Pool.
+3. Enter a name and complete any additional required details for the resource pool and then click Next.   
+   ![New Resource Pool](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0192576F-1954-421D-8C37-5CF3A41C0C7D-high.png)
+4. Click Save Changes to finalize resource pool creation.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json b/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
new file mode 100644
index 0000000..39527ff
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+  "title": "Price Phase Task Utilization",
+  "ordinal": 118,
+  "parent_title": "Workflows",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D63E4175-CA68-4648-B912-F20796292DD3.html",
+  "topic_cluster": {
+    "clustering_title": "Price Phase Task Utilization",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D63E4175-CA68-4648-B912-F20796292DD3",
+        "clustering_title": "Price Phase Task Utilization"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md b/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
new file mode 100644
index 0000000..9e3c367
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D63E4175-CA68-4648-B912-F20796292DD3.md
@@ -0,0 +1,52 @@
+# Price Phase Task Utilization
+
+Price Phase Tasks Video Demo
+
+Price Phase Tasks allow computed pricing for any workload in any Cloud (even public Clouds) to be overridden based on custom logic designed by the user. The variable “spec” is fed into the Task which represents the Instance configuration. The Task can be designed to use the Instance config data and compute an appropriate price for the Instance. HPE Morpheus Enterprise expects a return payload in the format below for the price override to work correctly. If used, pricing computed via Task replaces any other costing data which would have been applied to the workload (such as pricing based on the Service Plan). The user will see price estimates based on the Price Phase Task in the Instance provisioning wizard where the Service Plan pricing would otherwise be shown. Additionally, since Workflows which invoke Price Phase Tasks are tied to the Layout, the user can see different pricing depending on which Instance Type Layout is selected.
+
+NOTE
+
+Price Phase Tasks are only invoked if the Workflow is tied to a Layout.
+
+The return payload should be a JSON array of “priceData” objects. priceData objects should contain values for each of the keys in the table below:
+
+| Key | Description | Data Type | Possible Values |
+| --- | --- | --- | --- |
+| incurCharges | Indicates the Instance state when this charge should be applied | String | **Running:** Charge is incurred while the workload is in a running state, **Stopped:** Charge is incurred while the workload is in a stopped or shutdown state, **Always:** This charge is always applied. Some charges may apply simultaneously, for example, “Always” and “Running” states will apply while the workload is running. |
+| currency | Indicates the currency in which the charge will be applied | String | Enter any three‐letter currency code which HPE Morpheus Enterprise supports for its pricing, such as “USD”, “CAD”, or “GBP” |
+| unit | Indicates the time interval at which the charge is applied | String | Enter “minute”, “hour”, “day”, “month”, or “year” |
+| cost | Indicates the amount applied as cost for each configured time unit interval that passes. This is the cost to you, not the price with markup which the customer would see. | Number | A numerical amount such as “3.00” or “34.23” |
+| price | Indicates the amount applied as price for each configured time unit interval that passes. This is the price to the customer with any built‐in markup you need to apply. | Number | A numerical amount such as “3.00” or “34.23” |
+
+A number of different Task types could be used in this phase. As long as the Task is returning the required JSON array, the Task will work correctly. Below is an example using a Groovy Task. This is simply outputting a static payload though in a real world scenario you’d likely use Task logic to output a dynamic array based on the Instance configuration.
+
+```
+```
+def rtn = [  
+  priceData: [  
+    [  
+      incurCharges: 'always',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 2.0,  
+      price: 2.0  
+    ],  
+    [  
+      incurCharges: 'running',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 3.0,  
+      price: 3.0  
+    ],  
+    [  
+      incurCharges: 'stopped',  
+      currency: 'USD',  
+      unit: 'hour',  
+      cost: 1.0,  
+      price: 1.0  
+    ]  
+  ]  
+]  
+return rtn
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json b/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
new file mode 100644
index 0000000..7dd6178
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+  "title": "Storage",
+  "ordinal": 518,
+  "parent_title": "Integration Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.html",
+  "topic_cluster": {
+    "clustering_title": "Storage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014",
+        "clustering_title": "Storage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md b/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
new file mode 100644
index 0000000..f68a9d3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D7A36529-C624-486D-8C0E-FA69A4DC4014.md
@@ -0,0 +1,9 @@
+# Storage
+
+**Subtopics**  
+
+- **[3Par](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-ADDC3274-0758-43B9-BF31-6EA3EB319288.html)**
+- **[AzureStorage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-63BB7C20-DB5C-454C-BD72-F0E48E8C114C.html)**
+- **[Dell ECS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-38B4C746-179D-43CA-9205-9DC63ACC87EF.html)**
+- **[HPE Alletra MP Storage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-45A52EF2-E1DD-4625-BDE5-C4BE51EA01AD.html)**
+- **[Isilon](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json b/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
new file mode 100644
index 0000000..003c7a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+  "title": "Creating and Running Security Scan Jobs",
+  "ordinal": 93,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.html",
+  "topic_cluster": {
+    "clustering_title": "Creating and Running Security Scan Jobs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9",
+        "clustering_title": "Creating and Running Security Scan Jobs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md b/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
new file mode 100644
index 0000000..5c39d92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D7BD39F5-E0A0-4A89-84C9-CF1443E428D9.md
@@ -0,0 +1,86 @@
+# Creating and Running Security Scan Jobs
+
+Security Scan Jobs allow users to create and schedule SCAP program (Security Content Automation Program) scans for groups of managed systems. These Jobs can call in existing SCAP packages and checklists, which are used to scan the targeted systems on-demand or on a scheduled basis. Historical data for these scans is saved in the Job Execution list and in the software section of server detail pages. Detailed scan reports can also be viewed for each system as needed once the scan is complete. See the [SCAP documentation](https://csrc.nist.gov/CSRC/media/Projects/Security-Content-Automation-Protocol/documents/docs/scap-nistir-7343.pdf) on the NIST website for information on developing your own scanning procedures.
+
+NOTE
+
+Creating and editing Security Scan Jobs requires the “Security: Scanning” Role permission set to Full. Viewing Security Scan Jobs and seeing the results for scanned servers requires at least a Read-level permission.
+
+## Add a new Security Scan Job
+
+### About this task
+
+NOTE
+
+New security scan packages are added in HPE Morpheus Enterprise Library rather than here in the Jobs section. Ensure you have uploaded the desired security package in Library > Templates > Security Packages before proceeding with new security Job creation.
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click +ADD
+3. Set the Job type to “Security Scan Job” and provide a friendly name for the Job
+4. Click NEXT 
+
+   ![../../_images/2new_job.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E8A3A8C8-27F1-48F1-8B98-2AF3AAE6E121-high.png)
+5. Select a security package, see the previous section to add a new one
+6. Enter your Scan Checklist (XML document) and Security Profile (XCCDF document), more information on these can be found in the SCAP documentation linked above
+7. Set a schedule or leave as Manual to only run this scan on-demand (new execution schedules can be created in Library > Automationif needed)
+8. Set a specific power state target if desired. This indicates whether the Job should run against workloads having any power state, just an “on” power state, or just an “off” power state
+9. Set the context, can be Instance or Server. Select as many Instances or Servers as needed for this scanning run
+10. Click NEXT
+11. After final review, click COMPLETE 
+
+    ![../../_images/3job_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-77399E18-27B9-465D-885C-F34C86B2EA19-high.png)
+
+## Running Security Scan Jobs
+
+### About this task
+
+Once created, Security Scan Jobs will run based on the configured schedule. They can also be run on-demand when needed:
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Jobs Tab
+2. Click MORE
+3. Click “Execute” 
+
+   ![../../_images/4execute_scan.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-ECB853BF-5ACC-4D03-BCC3-AF5A1D2706A3-high.png)
+
+## Viewing Completed Security Scan Jobs
+
+### About this task
+
+To view a list of completed Security Scan Jobs (and Jobs of other types):
+
+### Procedure
+
+1. Navigate to Provisioning > Jobs > Job Executions Tab
+2. Additional details can be viewed by clicking (i) 
+
+   ![../../_images/5execution_list.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-486B12EC-23D0-4977-9075-9BAE63439855-high.png)
+
+### Results
+
+To view scan results for specific servers:
+
+1. Navigate to the server detail page (Infrastructure > Hosts > Virtual Machines tab > Selectedserver)
+2. Click on the Software tab part way down the page, then click on the Security subtab
+3. High level details on previous scans is viewable here
+
+   ![../../_images/6server_results.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FEF15F44-AFFC-4639-B948-E5077F44A1AA-high.png)
+4. To view the full report, click (i)
+
+   ![../../_images/7scan_report.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-87EF931F-9CF2-4909-BD82-654F0658AE7D-high.png)
+
+## Security Drift
+
+In addition to tracking the scan results over time as described in the previous section, HPE Morpheus Enterprise also provides detail into the change from the most recent scan to the one prior. This information is displayed in the Software tab (and Security subtab) of the detail page for the virtual machine (accessed from the associated Instance detail page or at Infrastructure > Hosts > Virtual Machines). The information surfaced by this view is listed below. If there is no change, you’ll simply see a “No Drift” message.
+
+- **Title:** The criteria for the test that has newly passed or failed
+- **Severity:** The severity level for the indicated security requirement
+- **Result:** The indicator for whether this test has newly passed or failed
+- **New Pass:** The number of tests that have newly passed compared to the prior scan
+- **New Fail:** The number of tests that have newly failed compared to the prior scan
+- **Status:** An indicator of the change in security posture since the prior scan. A net gain in test failures will yield a negative status indicator while net gains in passed tests (or no change) will yield a positive status indicator
+
+![../../_images/8securityDrift.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A56F50AC-F22B-4AB1-84B2-AE09A887951C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json b/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
new file mode 100644
index 0000000..faf178e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+  "title": "Oracle Cloud",
+  "ordinal": 467,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F",
+        "clustering_title": "Oracle Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md b/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
new file mode 100644
index 0000000..6b18e97
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D825F3A4-E3DD-4745-8356-5A4804ED3F2F.md
@@ -0,0 +1,230 @@
+# Oracle Cloud
+
+## Required Permissions
+
+Integrating Oracle Public Cloud with HPE Morpheus Enterprise requires access to a service account with at least the permission set listed below. When creating an Oracle Cloud integration scoped to a specific compartment, the service account needs access only to the listed resource families within the chosen compartment. If the Cloud will be scoped to all compartments, the service account will need access to the listed resource families at the root compartment.
+
+### Oracle Cloud Policy Requirements
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage cluster-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage compute-management-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage data-catalog-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage dns in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage file-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage instance-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage object-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage virtual-network-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+Allow group <GROUP CONTAINING SERVICE USER> to manage volume-family in compartment <CHOSEN COMPARTMENT OR ROOT COMPARTMENT>
+
+## Add Oracle Public Cloud
+
+IMPORTANT
+
+A Keypair (both public and private key) must be added to HPE Morpheus Enterprise with the Public Key in ssh-rsa format. The Public Key in PEM format needs to be added to Oracle Cloud users keys in Oracle Cloud console for authentication.
+
+NOTE
+
+Information on uploading the Public Key and generating Tenancy’s OCID and User’s OCID can be found at <https://docs.cloud.oracle.com/iaas/Content/API/Concepts/apisigningkey.htm>
+
+To get started, navigate to Infrastructure > Clouds. Click + ADD and select Oracle Public Cloud to begin a new one. Configure the following options for the new Cloud:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+TENANCY OCID
+:   The OCID string from Tenancy Information section in Oracle Cloud
+
+USER OCID
+:   OCID String for the OPC API user
+
+SELECT KEY PAIR
+:   Select a keypair added to HPE Morpheus Enterprise matching the public key added to specified OPC API user
+
+REGION
+:   Select the OPC region (populates after successful account authentication)
+
+COMPARTMENT
+:   Choose to scope the Cloud to all compartments or to one specific compartment (populates after successful account authentication)
+
+INVENTORY
+:   Turn on for HPE Morpheus Enterprise to discover and sync existing VMs
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+## Enable Live Costing for Oracle Public Cloud
+
+Morpheus version 4.2.1 and higher support live costing data from the Oracle Cloud metering API. In order to authenticate with this API, edit your existing Oracle Cloud account integration or begin the process of newly integrating an account that wasn’t previously consumable in HPE Morpheus Enterprise (Infrastructure > Clouds > +ADD).
+
+In the advanced options section of the add/edit cloud modal for Oracle Public Cloud, the COSTING KEY and COSTING SECRET fields must be completed to work with metering API data in HPE Morpheus Enterprise. Unlike the OCI API authentication used to initially integrate Oracle Cloud, the metering API uses token-based authentication. We must access a Client ID and Client Secret value from the Oracle Public Cloud console to complete these fields.
+
+![../../../_images/1editcloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CA223A6F-8A57-42C6-B371-5D9F07D3DDBA-high.png)
+
+Navigate to Oracle cloud sign in page, the URL for which is similar to the following example:
+
+`https://idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/signin`
+
+If you’re not redirected to the admin console similar to the one pictured below, log out and replace ‘signin’ at the end of the URL with ‘adminconsole’ as in the following example:
+
+`https:// idcs-00a0xxxxxxxxxxxxx.identity.oraclecloud.com/ui/v1/adminconsole`
+
+You’ll immediately be redirected back to the same signin page but in doing that you should be taken to the admin console after authenticating your session once again.
+
+![../../../_images/2adminconsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E1A971F2-CCF2-4FCF-BCAB-4E9EC09A92EE-high.png)
+
+Create a new application and select the type “Confidential Application”.
+
+![../../../_images/3confapp.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B6335CF7-81F9-4564-9377-E3B26BCA269F-high.png)
+
+On the Details tab, enter a “Name” value and click “Next”.
+
+![../../../_images/4appdetails.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B1C6E805-6451-4525-8A6F-F96C9D28BA31-high.png)
+
+On the Client tab, choose to “Configure this application as a client now” to reveal additional fields. Then, in the Authorization section, mark the boxes for “Client Credentials” and “JWT Assertion”.
+
+![../../../_images/5appauth.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5B10DEAF-82FB-461E-A804-8D2586512948-high.png)
+
+In the Token Issuance Policy section, click the “+Add Scope” button. Click the right-facing arrow button in the row for “CloudPortalResourceApp”. Mark the box to give read access for metering and click “Add”.
+
+![../../../_images/6meteringread.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F724B49C-D954-4EB3-BDAF-20A717A770AA-high.png)
+
+Click “Next” until the “Finish” button is shown, then click “Finish”
+
+The Client ID and Client Secret value will be shown at this point. If these values need to be referenced in the future, simply edit the application and go to the Configuration tab. The Client ID and Client Secret are shown in the General Information section.
+
+![../../../_images/7secretvalues.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-AACE06F0-9EBF-414D-9414-AFC686F70DE7-high.png)
+
+Back in HPE Morpheus Enterprise, enter these values in the COSTING KEY and COSTING SECRET fields of the add/edit cloud modal for your Oracle Public Cloud integration. You also need to fill in the IDENTITY SERVICE value. This value can be found in the URL for your Oracle admin console as shown in the image below. It will be in a format `idcs-xxxxxx`.
+
+![../../../_images/8identityservice.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E608C9F2-141F-4075-9B0D-B3A5EC53F46A-high.png)
+
+Save changes to the Cloud.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json b/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
new file mode 100644
index 0000000..17439d9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+  "title": "Digital Ocean",
+  "ordinal": 393,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.html",
+  "topic_cluster": {
+    "clustering_title": "Digital Ocean",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC",
+        "clustering_title": "Digital Ocean"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md b/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
new file mode 100644
index 0000000..01449da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D94C4B1F-64F4-4F9A-AAA7-C719430BC2CC.md
@@ -0,0 +1,143 @@
+# Digital Ocean
+
+## Add a Digital Ocean Cloud
+
+DigitalOcean Cloud Integration Detail fields:
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+Username
+:   DigitalOcean Username
+
+API Key
+:   Personal access tokens/Key from the DigitalOcean API  >  Tokens/Keys section.
+
+Data Center
+:   Select DigitalOcean DataCenter Region
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json b/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
new file mode 100644
index 0000000..5fd7ece
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+  "title": "SAML Integration",
+  "ordinal": 286,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.html",
+  "topic_cluster": {
+    "clustering_title": "SAML Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96",
+        "clustering_title": "SAML Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md b/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
new file mode 100644
index 0000000..ce3a326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D9851B7F-355C-4C65-BB56-A8996B1A4F96.md
@@ -0,0 +1,150 @@
+# SAML Integration
+
+## Overview
+
+The HPE Morpheus Enterprise SAML identity source integration allows customers to add user SSO to HPE Morpheus Enterprise, authenticated by external login SAML providers.
+
+![../../_images/samlLoginGeneric.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0A6CC774-6C13-4B74-B7A5-C8D414D5D46A-high.png)
+
+## Adding a SAML Integration
+
+### About this task
+
+To add a SAML integration:
+
+### Procedure
+
+1. Navigate to Administration > Tenants
+2. Select a tenant.
+3. Select IDENTITY SOURCES in the Tenant detail page
+4. Select + ADD IDENTITY SOURCE.
+5. Select SAML SSO from the TYPE field
+6. Add a Name and optional Description for the SAML integration
+
+### Results
+
+![../../_images/saml.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FEB50132-F13C-491F-83D8-FEABA6E7BB0C-high.png)
+
+There are 4 sections with fields that need to be populated depending on the desired configuration:
+
+- SAML Configuration
+- Role Mappings
+- Role Options
+- Assertion Attribute Mappings
+
+## SAML Configuration
+
+LOGIN REDIRECT URL
+:   This is the SAML endpoint HPE Morpheus Enterprise will redirect to when a user signs into HPE Morpheus Enterprise via SAML
+
+SAML LOGOUT REDIRECT URL
+:   The URL HPE Morpheus Enterprise will POST to when a SAML user logs out of HPE Morpheus Enterprise
+
+INCLUDES SAML REQUEST PARAMETER
+:   **Yes** (recommended) - the AuthN request will be sent via the ?SAMLRequest= parameter in the URL (GET)
+
+    **No** - the AuthN request will be submitted in the body of the request (POST)
+
+    NOTE
+
+    The SAML SP documentation should mention which binding to use but GET is most common
+
+SAML REQUEST
+:   **No Signature** - No signature is used on the SAML request
+
+    **Self Signed** - A self-signed X.509 Certificate is generated after clicking SAVE CHANGES. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+    **Custom RSA Signature** - Import a custom RSA Private Key and respective X.509 Certificate. This signature value can be used by the SAML SP to verify the authenticity of the request
+
+SAML RESPONSE
+:   **Do Not Validate Assertion Signature** - The SAML response signature from the SAML SP will not be validated
+
+    **Validate Assertion Signature** - The SAML response signature from the SAML SP will be validated. Enter the SAML SP X.509 certificate in the **Public Key** field. This must be in PEM format
+
+IMPORTANT
+
+Setting SAML REQUEST to “No Signature” and SAML RESPONSE to “Do Not Validate Assertion Signature” is allowed but not recommended for security reasons.
+
+## Role Mappings
+
+DEFAULT ROLE
+:   Role any SAML user will be assigned by default
+
+ROLE ATTRIBUTE NAME
+:   The name of the attribute/assertion field that will map to HPE Morpheus Enterprise roles, such a MemberOf
+
+REQUIRED ROLE ATTRIBUTE VALUE
+:   Attribute/assertion value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+<HPE Morpheus Enterprise ROLE NAME>
+:   Additional roles that can be mapped to a user, which will add to the DEFAULT ROLE. Attribute value that a user must be assigned/a member of to be authorized, such as group or role in the SAML SP. This is obtained from the attribute/assertion defined in the ROLE ATTRIBUTE NAME field
+
+NOTE
+
+For more on Identity Source role mapping permissions, see the [associated guide](https://support.morpheusdata.com/s/article/How-to-enable-Subtenant-admins-to-edit-Identity-Source-role-mapping?language=en_US) in our KnowledgeBase.
+
+## Role Options
+
+ENABLE ROLE MAPPING PERMISSION
+:   When selected, Tenant users with appropriate rights to view and edit Roles will have the ability to set role mapping for the Identity Source integration. This allows the Tenant user to edit only the role mappings without viewing or potentially editing the Identity Source configuration.
+
+MANUAL ROLE ASSIGNMENT
+:   When selected, administrators can manually edit Roles for users created through this identity source integration from the user detail page (Administration > Users > Selected user).
+
+## Assertion Attribute Mappings
+
+GIVEN NAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user First Name
+
+SURNAME ATTRIBUTE NAME
+:   SAML SP field value to map to HPE Morpheus Enterprise user Last Name
+
+EMAIL ATTRIBUTE
+:   SAML SP field value to map to HPE Morpheus Enterprise user email address
+
+![../../_images/saml_assertion_attribute_mappings.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A5E51597-2545-4462-AD43-F82AB88434E7-high.png)
+
+Once populated, select SAVE CHANGES and the SAML identity source integration will be added.
+
+In the Identity Sources section, important information for configuration of the SAML integration is provided. Use the SP ENTITY ID and SP ACS URL for configuration on the external login SAML provider side.
+
+NOTE
+
+In some cases, the SAML provider may need these values before providing the LOGIN REDIRECT URL and other values. When creating the integration, the NAME and LOGIN REDIRECT URL can contain any values, then selecting SAVE CHANGES will generate the above values. The NAME and LOGIN REDIRECT URL can be edited later, once the SAML configuration is created in the SAML provider.
+
+- ENTITY ID
+- SP ACS URL
+- LOGIN REDIRECT URL
+- SP METADATA
+
+![../../_images/identity_sources_info.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-112ECB06-8A2B-4025-B4CB-B57B7F12A12B-high.png)
+
+Sample Metadata code output:
+
+```
+```
+<?xml version="1.0" encoding="UTF-8" standalone="yes"?><EntityDescriptor entityID="https://someip.com/saml/eDKL60P25" xmlns="urn:oasis:names:tc:SAML:2.0:metadata"><SPSSODescriptor AuthnRequestsSigned="false" WantAssertionsSigned="true" protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol"><NameIDFormat>urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified</NameIDFormat><AssertionConsumerService index="0" isDefault="true" Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://someip.com/externalLogin/callback/eDKL60P25"/></SPSSODescriptor></EntityDescriptor>
+```
+```
+
+NOTE
+
+Different SAML providers will have different field names and requirements. An Okta SAML Dev environment was used for the example integration in this article.
+
+## Okta SAML SSO
+
+For Okta SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : Identity Provider Single Sign-On URL
+- ENTITY ID: Audience URI (SP Entity ID)
+- SP ACS URL: Single sign on URL
+
+## Onelogin SAML SSO
+
+For Onelogin SAML integration, the following fields are mapped:
+
+- LOGIN REDIRECT URL : SAML 2.0 Endpoint (HTTP)
+- SAML LOGOUT REDIRECT URL : SLO Endpoint (HTTP)
+- SIGNING PUBLIC KEY : X.509 Certificate
+- ENTITY ID: ACS (Consumer) URL Validator
+- SP ACS URL: ACS (Consumer) URL
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json b/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
new file mode 100644
index 0000000..eeb2e43
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+  "title": "OS Imaging",
+  "ordinal": 451,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.html",
+  "topic_cluster": {
+    "clustering_title": "OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF",
+        "clustering_title": "OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md b/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
new file mode 100644
index 0000000..ba7861a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-D9D9DE04-0C2B-4A05-989C-1ED5683180AF.md
@@ -0,0 +1,7 @@
+# OS Imaging
+
+| S. No. | Symptom | Additional Details | Common Checks | Log Files | **Remarks** |
+| --- | --- | --- | --- | --- | --- |
+| 1 | Windows Setup fails before completion | - Do **not** dismiss error dialogs immediately, as this may remove diagnostic information. - Use **iLO Remote Console** to access the system. - Press **Shift + F10** to open a command prompt in the Windows PE environment. | **Disk layout** – Confirm the primary disk is attached to the local RAID controller.  **AutoUnattend.xml** – Verify the file exists and defines required partitions:   - EFI System Partition (500 MB) - Microsoft Reserved Partition (128 MB) - Primary OS partition | Relevant setup logs may be found in:   - `X:\Windows\Panther` - `C:\$WINDOWS.~BT\Sources\Panther`   Key files:   - `setupact.log` - `setuperr.log` | Use logs to identify the specific failure stage and error code. |
+| 2 | RHEL / Oracle Linux  (Autoinstall via Kickstart) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F1: Installer UI - Alt + F2: Interactive shell - Alt + F3: Installation logs | **Key Logs:**   - `/var/log/anaconda/anaconda.log` - `/var/log/anaconda/syslog` - `/root/anaconda-ks.cfg` - `/root/original-ks.cfg` - `/root/post-ks.log` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to validate disk and network configuration before retrying installation. |
+| 3 | Ubuntu Linux  (Autoinstall via Curtin and Subiquity) | If the installation fails or hangs, the installer provides interactive shells and log files for debugging. | **TTY Shortcuts:**   - Alt + F2 or Ctrl + Alt + F2: Interactive shell - Installer runs on TTY1 | **Key Logs**   - `/var/log/installer/curtin-install.log` - `/var/log/installer/early-commands.log` - `/var/log/installer/subiquity-client*` - `/var/log/installer/subiquity-server*` - `/var/log/cloud-init.log` - `/var/log/cloud-init-output.log` | Use interactive shell (Alt + F2) to check network and storage configuration, then review logs for errors. |
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json b/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
new file mode 100644
index 0000000..0bb325c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+  "title": "Configuring Virtual Images",
+  "ordinal": 149,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.html",
+  "topic_cluster": {
+    "clustering_title": "Configuring Virtual Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89",
+        "clustering_title": "Configuring Virtual Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md b/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
new file mode 100644
index 0000000..ea00ba5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DA1898BD-3EB1-432A-BD34-373B29B05B89.md
@@ -0,0 +1,83 @@
+# Configuring Virtual Images
+
+## System Images
+
+System Virtual Images are pre-configured with metadata and have Cloud-Init or Cloudbase-Init installed. These images are ready to be provisioned with no configuration necessary, however it is required to populate Administration > Settings > Provisioning, Cloud-Init section, with user data as well as User Profile(s) users data when creating additional users prior to provisioning, as the user data from these sections is required when provisioning System provided Virtual Images.
+
+NOTE
+
+System Images settings are not editable.
+
+## User Images
+
+Typically HPE Morpheus Enterprise does not have sufficient metatdata to successfully provision synced User Images. After integrating clouds and User Images have synced, it is highly recommended to configure the images prior to provisioning.
+
+### To edit and configure an existing Virtual Image:
+
+#### Procedure
+
+1. Select the pencil icon at the right of any row on the Virtual Images list page, or click EDIT on a Virtual Image detail page.
+2. Configure the following on the Image: 
+
+   Name
+   :   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the image, but editing will not change the name of the actual image
+
+   Operating System
+   :   Specifies the platform and OS of the image. All Windows images will need to have the operating system specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the platform for all images without an operating system specified
+
+   Minimum Memory
+   :   The Minimum Memory setting will filter available Service Plan options during provisioning. Service Plans that do not meet the minimum value set on the Virtual Image will not be provided as Service Plan choices
+
+   Cloud Init Enabled?
+   :   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed
+
+   Install Agent?
+   :   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are still collected for Agent-less hosts and VMs depending on the cloud)
+
+   Username
+   :   Existing username on the image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init or Guest Customizations are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist on the image (such as `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change
+
+   Password
+   :   Password for the user on the image if username is populated
+
+   Bucket
+   :   Location where the Virtual Image will be stored. Default Virtual Image Storage location is `/var/opt/morpheus/morpheus-ui/vms`. Additional Storage Providers can be configured in Infrastructure  >  Storage
+
+   Cloud-Init User Data
+   :   Accepts what would go in `runcmd` and can assume Bash syntax. Example use: Script to configure satellite registration at provision time
+
+   Create Image ID
+   :   Select FILE to browse locally for an image or drop an image file into the dropzone. Alternatively, select URL to download the image from an accessible URL. It is recommend to configure the rest of the settings below prior to uploading the source Image File(s)
+
+   Permissions
+   :   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. Select private visibility and select specific Tenants to which the Virtual Image will be made available. Select public visibility to share the Virtual Image with all Tenants
+
+   Auto Join Domain?
+   :   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure  >  Network and the configured domain set on the provisioned to Cloud or Network)
+
+   VirtIO Drivers Loaded?
+   :   Enable if VirtIO Drivers are installed on the image for provisioning to KVM-based hypervisors
+
+   FIPS Compliant Image?
+   :   When selected, HPE Morpheus Enterprise will install the FIPS-compliant HPE Morpheus Enterprise Agent package
+
+   VM Tools Installed?
+   :   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected
+
+   Force Guest Customization?
+   :   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This options requires that VMware Tools is installed on the image
+
+   Trial Version
+   :   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning
+
+   Enabled Sysprep?
+   :   Applicable to multiple Clouds, including VMware vCenter, SCVMM, Nutanix, Hyper-V, KVM, and Google GCP. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject `unattend.xml`
+3. Click Save Changes 
+
+   NOTE
+
+   Cloud-Init is enabled by default on all images. Images without Cloud-Init or Cloudbase-Init installed must have the `cloud-init` flag disabled on the Virtual Image setting or Provisioning may fail.
+
+   IMPORTANT
+
+   HPE Morpheus Enterprise does not validate or restrict image uploads to certain file types and any type of file may be uploaded as a Virtual Image. For security purposes, these files are stored in a non-executable state so users need not worry about potentially dangerous file types being uploaded (ex. executables).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json b/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
new file mode 100644
index 0000000..fbb2d8a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+  "title": "Morpheus Discovery",
+  "ordinal": 41,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus Discovery",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1",
+        "clustering_title": "Morpheus Discovery"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md b/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
new file mode 100644
index 0000000..2b1859f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DAAC86A8-F098-40C7-B403-3D4472BCF1D1.md
@@ -0,0 +1,28 @@
+# Morpheus Discovery
+
+Morpheus has the ability to ingest existing environments. Existing running workloads will be inventoried into Morpheus and displayed in the UI. In 5-7 days Morpheus will start making recommendations based off of usage and pricing.
+
+NOTE
+
+Workloads that are inventoried do not have to be converted to managed.
+
+Once inventoried, Morpheus can provide valuable data for that instance:
+
+- Morpheus will know about networks
+- Start aggregating cost on public clouds
+- Start tracking usage
+- Some Clouds offer statistical details ( Amazon / VMware)
+- Power Status
+
+Right away inventorying existing environments will provide you with immediate insight to that environment. Once an existing workload has been discovered it can be converted to managed. Once converted to managed, Morpheus can deliver more capabilities and features.
+
+NOTE
+
+Workloads do not need the agent installed to be managed
+
+Once a workload is managed:
+
+- Enforce expiration/shutdown policies. This helps reign in environments (sprawl) and reduce cost.
+- Can tell what instance type it is
+- Can install agent (agent is optional)
+- Installing agent provides credentials and allows you to run workflows against it (day 2 operations)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json b/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
new file mode 100644
index 0000000..08eeade
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+  "title": "User Roles",
+  "ordinal": 302,
+  "parent_title": "Creating Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.html",
+  "topic_cluster": {
+    "clustering_title": "User Roles",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA",
+        "clustering_title": "User Roles"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md b/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
new file mode 100644
index 0000000..981d9a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DAFEAFB8-9516-429B-B6C1-216F044DB4DA.md
@@ -0,0 +1,16 @@
+# User Roles
+
+User Roles can be single or multitenant. A Multitenant User Role is automatically copied into all existing subtenants as well as placed into a subtenant when created. Useful for providing a set of predefined roles a Customer can use. The Multitenant Locked option prevent subtenant from modifying FEATURE ACCESS settings in the Role. Note Group, Instance Type and Blueprint Access settings will still be editable as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+IMPORTANT
+
+Multitenant Roles still need to be configured/managed be each subtenant, as Groups are unique per Tenant, and Instance and Blueprints can be a mix of unique and shared items.
+
+NOTE
+
+User Roles cannot exceed Tenant Role permissions. If a Multitenant User Role has higher permissions than the Tenant Role assigned to a subtenant, the Multitenant User Role permissions in that Tenant will automatically be reduced to match the Tenant Role permissions.
+
+**Subtopics**  
+
+- **[Create a Single Tenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-4CFE73A0-DB2A-4CA2-8E06-EC8FBAC78C47.html)**
+- **[Create a MultiTenant User Role](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1B184F05-C570-446E-8C3A-FC24792DE213.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json b/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
new file mode 100644
index 0000000..5346b49
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+  "title": "Cherwell",
+  "ordinal": 489,
+  "parent_title": "ITSM",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.html",
+  "topic_cluster": {
+    "clustering_title": "Cherwell",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0",
+        "clustering_title": "Cherwell"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md b/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
new file mode 100644
index 0000000..8c67d88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB06F181-C0B5-4D17-A91B-EB788DE593A0.md
@@ -0,0 +1,53 @@
+# Cherwell
+
+## Add Cherwell Integration
+
+### Procedure
+
+1. Navigate to Administration > Integrations
+2. Select `+ NEW INTEGRATION`
+3. Select `Cherwell` from the dropdown.
+4. Add the following: 
+
+   NAME
+   :   Name of the Integration in Morpheus.
+
+   ENABLE
+   :   Leave checked to enable the Integration.
+
+   HOST
+   :   Url of the Cherwell Instance
+
+   USER
+   :   Enter in username
+
+   PASSWORD
+   :   Above Cherwell user’s password
+
+   CLIENT KEY
+   :   Provide your Cherwell client key
+
+   CREATED BY USER
+   :   This is the full name of a user in the Cherwell system. When a new change management record is created in the Cherwell system, this user will be added to the record as the user that created it.
+
+   START DAYS FROM NOW
+   :   Number of days from now to set proposed start date
+
+   END DAYS FROM NOW
+   :   Number of days from now to set proposed end date
+
+   CUSTOM MAPPING
+   :   This is an optional json object that allows the custom setting of the Cherwell fields on the Change Request object.
+
+       NOTE
+
+       The keys in the map correspond to the name of the field on the Change Request in Cherwell that you would like to set (see <https://bertram.d.pr/1Ziuhy> for a reference). In addition, the value in the map corresponds to the value you wish to use. Within the value, Morpheus variables may be used. Here is an example for setting the Description is:
+
+       ```
+       ```
+       {  
+       "Description":"Created from Morpheus by ${instance.createdByUsername} in ${zone.name}"  
+       }
+       ```
+       ```
+5. Save Changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.json b/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
new file mode 100644
index 0000000..59eb7c2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+  "title": "Job Executions",
+  "ordinal": 94,
+  "parent_title": "Jobs",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DB2EE423-511B-432B-8425-82326DC29158.html",
+  "topic_cluster": {
+    "clustering_title": "Job Executions",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB2EE423-511B-432B-8425-82326DC29158",
+        "clustering_title": "Job Executions"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.md b/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
new file mode 100644
index 0000000..df5c568
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB2EE423-511B-432B-8425-82326DC29158.md
@@ -0,0 +1,24 @@
+# Job Executions
+
+## Required Role Permissions
+
+Access and capabilities for the **Job Executions** section is determined by the following role permissions:
+
+Role: Feature Access: `Provisioning: Job Executions`
+:   - None: Cannot access Provisioning: Job Executions section
+    - Read: Can access Provisioning: Job Executions section
+
+The Job Executions tab contains execution history of completed Jobs, including any process outputs and error messages. Information included in the Job Executions list includes:
+
+- Execution Status Icon
+- **Job Name - Task Name - Result Error Message:** The title of each execution includes the Job Name, Task or Workflow name (for Task and Workflow job types), and execution result error messages (when applicable) separated by hyphens (-). The title also links to the Job Execution detail page
+- **Start Date:** The date and time the Job Execution kicked off. When expanded, the start date and time of each individual Task are also shown
+- **Duration:** The time taken for the Job to complete. When expanded, the time to complete each individual Task is also shown
+- **User:** The user who executed or scheduled the Job
+
+Additional details and actions are available per execution:
+
+- Select an execution name to go to the Job Execution Detail page
+- Select the ⌃ icon at the end of the row to expand the execution and view additional details, including task process output
+- Select the 📋 icon to copy process output to local clipboard
+- Select the ⌄ icon at the end of an expanded to to collapse additional execution details
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json b/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
new file mode 100644
index 0000000..33d64d8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+  "title": "Viewing and Assigning Hardware Devices",
+  "ordinal": 194,
+  "parent_title": "Hardware Passthrough",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.html",
+  "topic_cluster": {
+    "clustering_title": "Viewing and Assigning Hardware Devices",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E",
+        "clustering_title": "Viewing and Assigning Hardware Devices"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md b/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
new file mode 100644
index 0000000..67d50a3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DB8D7A27-5E33-428A-BBF3-C4A79FE3C55E.md
@@ -0,0 +1,23 @@
+# Viewing and Assigning Hardware Devices
+
+Hardware Devices are surfaced at the Host detail level and the VM (server) detail level through a Devices tab. The Host detail will show all attached hardware devices and their current status: Attached (to the host), detached (from the host), or assigned (to a VM). The VM detail will show only hardware devices currently attached to that VM. To begin consuming hardware devices with HVM Cluster VMs, look again at the list in the Devices tab on the Host detail page. Detach a piece of hardware from the host using the ACTIONS dropdown for that piece of hardware. As shown in the screenshot below, DETACH DEVICE is selected for a USB device.
+
+![../../_images/detachDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A94BDC5A-C89C-426E-9EF6-2914BC84AC21-high.png)
+
+Once detached, the status of the device is changed to “Detached” (see screenshot below) and the device is available for consumption by VMs running on this host.
+
+![../../_images/deviceDetached.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-34E14A70-071B-4A63-BD76-5D0A1261BC20-high.png)
+
+To assign the hardware to a specific VM, click the ACTIONS dropdown once again for the now-detached hardware. Now, click ASSIGN DEVICE.
+
+![../../_images/assignDevice.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-443A34ED-8373-4AB9-9F26-730FF70DDD3C-high.png)
+
+Within the ASSIGN DEVICE modal that will appear, select the server for device assignment and click EXECUTE.
+
+![../../_images/assignToServer.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F76B03BD-5880-4AC2-8B3D-98537D873BDE-high.png)
+
+The icon and status for the device in the hardware list has now changed to “Assigned.” If we then open a console session with this VM, we can see the USB device is assigned successfully and is usable by the guest OS.
+
+![../../_images/vmConsole.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C1FCF142-72C3-4E92-9EBB-6277EC6DD1AA-high.png)
+
+The same process can be used to detach and assign GPU or NVME devices.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json b/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
new file mode 100644
index 0000000..0e52ed1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+  "title": "Creating ArubaCX Network Integration",
+  "ordinal": 432,
+  "parent_title": "Managed Networks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.html",
+  "topic_cluster": {
+    "clustering_title": "Creating ArubaCX Network Integration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287",
+        "clustering_title": "Creating ArubaCX Network Integration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md b/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
new file mode 100644
index 0000000..b987900
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBE8E5AA-1CE4-4F9E-A4CD-03CBDAC04287.md
@@ -0,0 +1,21 @@
+# Creating ArubaCX Network Integration
+
+## About this task
+
+The network integration allows the user to specify the switch information. It is expected that there are 2 switches per rack acting as the top-of-rack (ToR) switches. You need to specify information for a switch pair for a rack. If there are more than 1 rack, then information for the switch pair for each rack is required.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Network > Integrations.
+3. Click the Add to add a new integration.
+4. Select **HPE**Aruba CX Switches under the Networking section.   
+   ![Aruba CX Switches](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-EFC5C2DB-4496-480A-8039-50B8F31AAC5E-high.png)
+5. Enter the following details for the network integration: 
+
+   - **Name** for network integration
+   - **Username/Password** for the switches
+   - **Switch pair IP Addresses** for each pair of switches
+
+   ![Network Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6902768F-0D2B-472A-8F9F-6F8A7B286581-high.png)
+6. Click the Add Network Integration to create the Network Integration.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json b/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
new file mode 100644
index 0000000..feeff31
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+  "title": "Prerequisites",
+  "ordinal": 204,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html",
+  "topic_cluster": {
+    "clustering_title": "Prerequisites",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF",
+        "clustering_title": "Prerequisites"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md b/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
new file mode 100644
index 0000000..c9d8415
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.md
@@ -0,0 +1,7 @@
+# Prerequisites
+
+- HPE Morpheus Enterprise appliance running version 8.0.13 or higher
+- At least one pre-existing OpenShift 4.x cluster, which can communicate back to the HPE Morpheus Enterprise appliance on the HTTPS port
+- Access to a full administrator account for each cluster which will be integrated
+- Ability for the HPE Morpheus Enterprise appliance to communicate with the OpenShift API on port 6443
+- Ability for the HPE Morpheus Enterprise appliance to communicate with each provisioned VM on port 22 for SSH and on port 3389 for Windows RDP
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json b/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
new file mode 100644
index 0000000..ffd1c4a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+  "title": "Isilon",
+  "ordinal": 523,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.html",
+  "topic_cluster": {
+    "clustering_title": "Isilon",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D",
+        "clustering_title": "Isilon"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md b/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
new file mode 100644
index 0000000..cda08b8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DBFB2C06-AD6F-46B7-B178-B1E28B83A27D.md
@@ -0,0 +1,132 @@
+# Isilon
+
+## Add Dell EMC Isilon Storage Server
+
+### About this task
+
+IMPORTANT
+
+Enable insecure mode on the NFS settings. This allows non-root ports to be used. Setting the insecure/privileged mode will require a restart of the Isilon nodes.
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the SERVERS tab, Click the + ADD button.
+4. From the ADD STORAGE SERVER wizard input the following: 
+
+   NAME
+   :   Name of the Storage Server in HPE Morpheus Enterprise
+
+   TYPE
+   :   Select Dell EMC Isilon
+
+   URL
+   :   URL Of Dell EMC Isilon Server Example : `https://192.168.190.202:8080`
+
+   USERNAME
+   :   Add your administrative user account.
+
+   PASSWORD
+   :   Add your administrative password.
+
+   PROVISION USER
+   :   Select Provision User
+
+   PROVISION GROUP
+   :   Select Provision Group
+
+   ROOT PATH
+   :   Enter Root Path
+       :   Example : `\`
+5. Select SAVE CHANGES
+
+### Results
+
+The Dell EMC Isilon Storage Server will be added and displayed in the Buckets tab.
+
+Buckets, Files Shares and Storage Groups will be synced in.
+
+## Add Dell EMC Isilon File Share
+
+### About this task
+
+To Add a Dell EMC Isilon File Share:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Storage link in the sub navigation bar.
+3. In the FILE SHARES tab, Click the + ADD button.
+4. Select Dell EMC Isilon Share from the dropdown list
+5. From the NEW FILE SHARE Wizard input the following: 
+
+   NAME
+   :   Name of the File Share in HPE Morpheus Enterprise.
+
+   STORAGE SERVICE
+   :   Select existing Dell EMC Isilon Storage Server (configured in Infrastructure - Storage - Servers)
+
+   SHARE PATH
+   :   Enter Dell EMC Isilon Share Path
+       :   Example: `ecs-file-share-1`
+
+   Volume Size
+   :   Specify volume size for the File Share (in MB)
+
+   Allowed IP’s
+   :   Specify IP Addresses to limit accessibility to the File Share
+       :   Leave blank for open access
+           :   Click the `+` symbol to the right of the first ALLOWED IPS field to add multiple IP’s
+
+   NAMESPACE
+   :   Select Dell EMC Isilon Namespace (synced)
+
+   STORAGE GROUP
+   :   Select Dell EMC Isilon Storage Group (synced)
+
+   Default Backup Target
+   :   Sets this File Share as the default backup target when creating Backups. If selected the option to update existing Backup configuration to use this File Share will be presented.
+
+   Archive Snapshots
+   :   Enabled to export VM snapshots to this File Share when creating VMware Backups, after which the snapshot will be removed from the source Cloud.
+
+   Default Deployment Archive Target
+   :   Sets this File Share as the default storage target when uploading Deployment files in the Deployments section.
+
+   Default Virtual Image Store
+   :   Sets this File Share as the default storage target when uploading Virtual Images from the Virtual Images section, importing Images from Instance Actions, creating Images with the Image Builder and when creating new images from Migrations.
+
+   RETENTION POLICY
+   :   None
+       :   Files in the File Share will not be automatically deleted or backed up.
+
+       Backup Old Files
+       :   This option will backup files after a set amount if time and remove them from the File Share.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically backed up to the selected Backup File Share.
+
+               BACKUP File Share
+               :   Search for and select the File Share the files will be backed up to.
+
+       DELETE OLD FILES
+       :   This option will delete files from this File Share after a set amount of days.
+           :   DAYS OLD
+               :   Files older than the set number of days will be automatically deleted from the File Share.
+6. Select SAVE CHANGES
+
+### Results
+
+The File Share will be created and displayed in the File Shares tab.
+
+- To browse, upload, download, or delete files from this File Share, select the name of the File Share.
+- To edit the File Share, select the edit icon or select the name of the File Share and select ACTIONS - EDIT.
+
+  WARNING
+
+  Repointing a File Share that is in use may cause loss of file references. Ensure data is mirrored first.
+- To delete a File Share, select the trash icon or select the name of the File Share and select DELETE.
+
+  WARNING
+
+  When deleting a File Share, all Deployment Versions and Backups associated with the File Share will be deleted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json b/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
new file mode 100644
index 0000000..d260ebe
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+  "title": "Monitoring the Cluster",
+  "ordinal": 183,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.html",
+  "topic_cluster": {
+    "clustering_title": "Monitoring the Cluster",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D",
+        "clustering_title": "Monitoring the Cluster"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md b/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
new file mode 100644
index 0000000..2652012
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DCBE0E82-65B3-4436-8E96-E75E7F36179D.md
@@ -0,0 +1,14 @@
+# Monitoring the Cluster
+
+With the server provisioned and a workload running, take a look at the monitoring and actions capabilities on the cluster detail page (Infrastructure > Clusters, then click on the new HVM cluster). View cluster performance and resource usage (Summary and Monitoring tabs), drill into individual hosts (Hosts tab), see individual workloads (VMs tab), and more.
+
+**Subtopics**  
+
+- **[Moving Workloads Between Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3E01D88E-4D27-486C-93BE-A63D7DFC50BF.html)**
+- **[Adding hosts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3715BCDE-48A0-4FC5-A388-1E84C3EF7AF8.html)**
+- **[Maintenance Mode](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-74AA2AC3-E179-40B9-B1BB-F3050FBC0EE7.html)**
+- **[Affinity Groups](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BD0C3274-B70C-437A-B89C-C77A703FFD53.html)**
+- **[vCPU Placement](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html)**
+- **[Host Hardware Sensor Data Collection](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-A4660857-6FC0-4983-9E0A-FC3B1FEB6D35.html)**
+- **[Failover](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html)**
+- **[Adding an NFS Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-908B32F9-4816-44CF-829A-25AB3A6F2BA3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json b/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
new file mode 100644
index 0000000..8b7d5aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+  "title": "Adding Volume",
+  "ordinal": 443,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.html",
+  "topic_cluster": {
+    "clustering_title": "Adding Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A",
+        "clustering_title": "Adding Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md b/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
new file mode 100644
index 0000000..eaaf905
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DD626086-0E0C-460D-85BC-8E654BEEF70A.md
@@ -0,0 +1,17 @@
+# Adding Volume
+
+## About this task
+
+Perform the following procedure to create a new volume:
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Add button.
+3. Select the storage server to create the volume in and click Next.   
+   ![Storage Server](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-88533534-DD97-4462-88F4-443E815641B6-high.png)
+4. Select the required volume type, unreplicated, CPP replicated, or APP replicated, and click Next.   
+   ![Select Type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3E92F9CE-3785-4A3B-B5EF-BAADC8E40E1C-high.png)
+5. On the Configure screen, specify the volume name, size, datastore in which the volume needs to be created, shared/unshared. You can optionally specify the server/instance to export the volume, depending on whether it is unshared/shared.
+6. Click Complete to finish adding the volume.   
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8DC7D478-39B9-47ED-9F9A-4B6D87200464-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json b/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
new file mode 100644
index 0000000..d6e0e53
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+  "title": "Network Usage",
+  "ordinal": 435,
+  "parent_title": "Networks Configuration",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html",
+  "topic_cluster": {
+    "clustering_title": "Network Usage",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD",
+        "clustering_title": "Network Usage"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md b/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
new file mode 100644
index 0000000..970f159
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.md
@@ -0,0 +1,15 @@
+# Network Usage
+
+Networks are attached to interfaces on a compute server. The interfaces can be the physical ports themselves or bond interfaces that combine two physical ports into an aggregated pipe. Bond interfaces provide the benefits of aggregated bandwidth on a single interface and also high availability by providing port-level redundancy.
+
+Once the decision is made on what kind of interfaces to use, networks can be chosen from the preconfigured list to attach to the network interfaces. This determines which VLANs are configured on which switch ports (or LAGs). As mentioned earlier, the primary VLAN is provisioned as an untagged VLAN, and the trunk VLANs are provisioned as tagged VLANs on the server ports.
+
+The supported bond types are:
+
+- Static Bond: This uses an L2+L3-based hash on the server OS and a static LAG on the switches.
+- LACP Bond: This uses the LACP mode on the server OS and LACP LAG on the switches.
+- Switch Independent Bond: This uses the balance-tlb mode on Linux servers and the switch-independent mode on Windows. The switch is configured as independent physical ports.
+
+**Subtopics**  
+
+- **[Specifying Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-21F2F208-7360-4468-B1FF-524CA30CB993.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json b/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
new file mode 100644
index 0000000..0a9f388
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+  "title": "Trust Integrations",
+  "ordinal": 245,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.html",
+  "topic_cluster": {
+    "clustering_title": "Trust Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16",
+        "clustering_title": "Trust Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md b/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
new file mode 100644
index 0000000..265019e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE1AC4F7-6731-4A55-ACDC-E201EF7A5B16.md
@@ -0,0 +1,3 @@
+# Trust Integrations
+
+This area lists integrations with external services to manage secrets, keys, and certificates. New Cypher integrations can be created here. See [our guide](https://docs.morpheusdata.com/en/latest/infrastructure/keypairs_certificates/keypairs_certs.html#installing-and-integrating-an-external-cypher-appliance) on installing and integrating an external Cypher store for full details. Additionally, some other external trust services may be populated here, such as NSX certificate services.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json b/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
new file mode 100644
index 0000000..1aa787d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+  "title": "Overview",
+  "ordinal": 230,
+  "parent_title": "Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE4B3C05-2C42-42E8-849A-B13E77080955",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md b/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
new file mode 100644
index 0000000..0cb36a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE4B3C05-2C42-42E8-849A-B13E77080955.md
@@ -0,0 +1,11 @@
+# Overview
+
+Infrastructure  >  Storage is for adding and managing Storage Buckets, File Shares, Volumes, Data Stores and Storage Servers for use with other Services in HPE Morpheus Enterprise.
+
+## Role Requirements
+
+There are two Role permissions for the Infrastructure  >  Storage section: Infrastructure: Storage and Infrastructure: Storage Browser. Infrastructure: Storage give Full, Read or No access to the Infrastructure  >  Storage sections, while Infrastructure: Storage Browser is specific to Buckets and Files Shares. Full Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed and files and folders to be added, downloaded and deleted from the Buckets and Files Shares. Read Infrastructure: Storage Browser permissions allows Buckets and Files Shares to be browsed only.
+
+## Default Storage
+
+The default Storage path for Virtual Images, Backups, Deployment Archives, Archive Service, and Archived Snapshots is var/opt/morpheus/morpheus-ui/. Its is recommended to add Storage Buckets and File Shares for these targets in the Infrastructure  >  Storage section to avoid running out of disk space on the HPE Morpheus Enterprise Appliance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json b/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
new file mode 100644
index 0000000..daa4c79
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+  "title": "UCS Manager",
+  "ordinal": 472,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.html",
+  "topic_cluster": {
+    "clustering_title": "UCS Manager",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A",
+        "clustering_title": "UCS Manager"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md b/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
new file mode 100644
index 0000000..c87b46d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DE5B0719-982E-4F56-B7BD-4BFE36819C1A.md
@@ -0,0 +1,75 @@
+# UCS Manager
+
+## Overview
+
+The HPE Morpheus Enterprise UCS Manager Integration enables UCS M B and C Chassis Inventory, VM and Container Host Bare Metal Provisioning, PXE boot with IPMI, Storage Profile, SAN Connection Profile, Server Pool, BIOS Profile, Boot Profile, Maintenance Profile, UUID Pool and Disk Group Profile sync.
+
+## Adding UCS Manager Cloud
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Clouds
+2. Select + ADD
+3. Select UCS MANAGER from the Clouds list
+4. Populate the following: 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   UCS MANAGER
+   :   IP or hostname of UCS Manager
+
+   USERNAME
+   :   UCS Manager User
+
+   PASSWORD
+   :   UCS Manager Password
+
+   ORGANIZATION
+   :   - EXISTING (select)
+       - NEW (create)
+         :   - ORG NAME
+               :   Enter name for the new Organization
+
+   SERVER PREFIX
+   :   String provisioned servers will be prefixed with
+
+   DATA DISK MODE
+   :   - LVM data disk
+       - Single Disk
+
+   DATA VOLUME
+   :   Defaults to `/dev/sdb` \* Check to enable SOFTWARE RAID
+
+   NET INTERFACE
+   :   Defaults to eth0
+5. Select NEXT
+6. Select an existing or create a new Group to add the Cloud to. The Cloud can be added to additional Groups in a Groups Clouds tab.
+7. Select NEXT
+8. Review and then Select COMPLETE
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json b/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
new file mode 100644
index 0000000..a2bdc15
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+  "title": "Oracle VM",
+  "ordinal": 466,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.html",
+  "topic_cluster": {
+    "clustering_title": "Oracle VM",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DED3B0BE-A491-472F-B40B-A08F64835F17",
+        "clustering_title": "Oracle VM"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md b/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
new file mode 100644
index 0000000..bfa1aa3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DED3B0BE-A491-472F-B40B-A08F64835F17.md
@@ -0,0 +1,150 @@
+# Oracle VM
+
+## Add an Oracle VM Cloud
+
+### Cloud Configuration
+
+NAME
+:   Name of the Cloud in HPE Morpheus Enterprise
+
+CODE
+:   Unique code used for api/cli, automation and policies.
+
+LOCATION
+:   Description field for adding notes on the cloud, such as location.
+
+VISIBILITY
+:   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+TENANT
+:   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+ENABLED
+:   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+AUTOMATICALLY POWER ON VMS
+:   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+    NOTE
+
+    When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+### Details
+
+API URL
+:   Oracle VM API URL. ex: <https://10.20.30.40:7002/ovm/core/wsapi/rest>
+
+USERNAME
+:   Oracle VM User
+
+PASSWORD
+:   Oracle VM User Password
+
+REPOSITORY
+:   Available repositories will auto-populate upon successful authentication with the above credentials. Select appropriate repository for this Cloud.
+
+SERVER POOL
+:   Available server pools will auto-populate upon successful authentication with the above credentials. Select appropriate server pool for this Cloud.
+
+Inventory Existing Instances
+:   If enabled, existing Virtual Machines will be inventoried and appear as unmanaged Virtual Machines in HPE Morpheus Enterprise .
+
+The Cloud can now be added to a Group or configured with additional Advanced options.
+
+#### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+#### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+#### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+#### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json b/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
new file mode 100644
index 0000000..26149a0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+  "title": "Provisioning",
+  "ordinal": 325,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF02CF23-8387-4D00-87AF-5F2054075F18",
+        "clustering_title": "Provisioning"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md b/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
new file mode 100644
index 0000000..46c6dd0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF02CF23-8387-4D00-87AF-5F2054075F18.md
@@ -0,0 +1,68 @@
+# Provisioning
+
+## Provisioning Settings
+
+Allow Cloud Selection
+:   Displays or hides Cloud Selection dropdown in Provisioning wizard.
+
+Allow Host Selection
+:   Displays or hides Host Selection dropdown in Provisioning wizard.
+
+Require Environment Selection
+:   Forces users to select and Environment during provisioning
+
+Show Pricing
+:   Displays or hides Pricing in Provisioning wizard and Instance and Host detail pages.
+
+Hide Datastore Stats On Selection
+:   Hides Datastore utilization and size stats in provisioning and app wizards
+
+Cross-Tenant Naming Policies
+:   Enable for the `sequence` value in naming policies to apply across tenants
+
+Reuse Naming Sequence Numbers
+:   When selected, sequence numbers can be reused when Instances are removed. Deselect this option and HPE Morpheus Enterprise will track issued sequence numbers and use the next available number each time.
+
+Deployment Archive Store
+:   Default Storage Provider for storing Deployment Archives.
+
+    NOTE
+
+    Storage Providers can be configured and managed in the Infrastructure  >  Storage section.
+
+## Cloud-Init Settings
+
+HPE Morpheus Enterprise can add global users for Linux and Windows at provision time. Cloud-init/Cloudbase-Init or VMware Tools installed on the provisioned virtual images is required.
+
+Linux
+:   - **Username:** Enter User to be added to Linux Instances during provisioning.
+    - **Password:** Enter password to be set for the above Linux user.
+    - **KeyPair:** Select KeyPair to be added for the above Linux user.
+
+NOTE
+
+Either a password, keypair, or both can be populated for the Linux user. Keypairs can be added in the Infrastructure  >  Keys & Certs section.
+
+## Windows Settings
+
+- **Administrator Password:** Enter password to be set for the Windows Administrator User during provisioning.
+
+## PXE Boot Settings
+
+Default Root Password
+:   Enter the default password to be set for Root during PXE Boots.
+
+## App Blueprint Settings
+
+Determines the Default Blueprint Type selected in new App Wizard
+
+- Morpheus
+- ARM Template
+- CloudFormation
+- Terraform
+- Kubernetes Spec
+- Helm Chart
+
+## Terraform Settings
+
+- **Terraform Runtime:** Select “auto” or “manual”. When selecting “auto”, HPE Morpheus Enterprise will automatically download and use the Terraform version indicated in the VERSION field on the Spec Templates that make up a Terraform Instance type or Blueprint (only up to v1.5.5). When selecting “manual”, HPE Morpheus Enterprise will use the version of Terraform [installed on your appliance](https://docs.morpheusdata.com/en/latest/integration_guides/Automation/terraform.html?#terraform-installation).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json b/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
new file mode 100644
index 0000000..2c32344
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+  "title": "Instance Details",
+  "ordinal": 85,
+  "parent_title": "Instances",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.html",
+  "topic_cluster": {
+    "clustering_title": "Instance Details",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F",
+        "clustering_title": "Instance Details"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md b/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
new file mode 100644
index 0000000..220ce88
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF0B769F-2A5F-4708-9D8C-ABCB0846E95F.md
@@ -0,0 +1,53 @@
+# Instance Details
+
+The instance detail page is where you can view and fully manage an instance. To get to an instance detail page, navigate to Provisioning > Instances, and click on an Instance. Please note Instance details and actions will differ between Instance types and user permissions.
+
+There are several sections within an Instance page that provide useful capabilities to the user.
+
+![../../_images/instanceDetail.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1E7A4007-3C1F-4E44-A046-41A0C62111AA-high.png)
+
+Summary
+:   Basic information, stats and status information
+
+    - **Availability:** The Instance availability is the percentage of time the Instance is up. When stopping Instances, the option is given to mute monitoring if you wish for intentional down time not to count against the availability
+    - **Response Time:** If listed as “N/A” (Not Applicable), the Instance does not have any Checks set against it or does not have any Checks set against it that report a response time. Agent Checks, for example, do not report a response time. Some Checks, such as Docker Checks for Docker containers, require HPE Morpheus Enterprise to ping the container which reports a response time.
+
+Deploy
+:   Track deployment history for instance types that support deployments or manually kick off a deployment (only visible for Instance Types that support deployments)
+
+Settings
+:   Some Instance Types support custom configuration settings (for example, MySQL presents the my.ini)
+
+Resources
+:   VMs, containers, or other resources associated with the Instance are listed here. Some Instance Types, such as XaaS Instances, will not have resources and the tab is not displayed
+
+Runtime
+:   View the environment variables presented to the Instances or exported to the Instances via Apps (more on this in the Apps section). Users may also see Imported environment variables that may be referenced by the running Instance.
+
+    For Instances that support load balancing and auto scaling, configure auto scaling thresholds and load balancer settings in the Scale subsection that pertain to a particular Instance.
+
+    The software subsection will show any tracked software which is Installed as part of the provisioning process and is being tracked.
+
+Storage
+:   See storage information associated with the Instance including the list of volumes and controllers which are associated with each machine that makes up the Instance.
+
+Network
+:   Useful for configuring network interfaces for your VMs or security groups which allow access to the Instance.
+
+Monitoring
+:   Quick summary of the monitoring system and all checks that were configured to test the state of the Instance. Stats views (memory, cpu, etc.) can be zoomed out to a 90-day view if desired (in global settings, ensure your stats retention setting will support this). Logs and guidance for the individual Instance are also shown in their respective subtabs.
+
+Backups
+:   Quick backup dashboard. Useful for viewing historical backups and snapshots as well as adding new backup jobs.
+
+History
+:   See historical information related to automation which has been run against the Instance. This is useful for examining automation which was run as part of a phase of a Provisioning Workflow. Users can also drill into the Workflows to examine individual Tasks, including viewing the output from these Tasks to confirm success or troubleshoot issues.
+
+Costing
+:   Invoices pertaining to the Instance are displayed here. See the Instance level or host level invoices along with individual line items. In the History subtab view historical pricing data to monitor trends. In the Prices subtab view any prices which have been created and used to build a metered costing profile for the workload.
+
+Console
+:   Access the Instance or container via a client-less Console supporting SSH, RDP, VNC, or even hypervisor-level remote consoles.
+
+Wiki
+:   View the Wiki page for this Instance or edit the existing Wiki page (which may currently be blank). The content field supports markdown formatting, see the main Wiki section of HPE Morpheus Enterprise documentation for additional details.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json b/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
new file mode 100644
index 0000000..aa085ca
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+  "title": "HPE Aruba CX DSS",
+  "ordinal": 511,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.html",
+  "topic_cluster": {
+    "clustering_title": "HPE Aruba CX DSS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9",
+        "clustering_title": "HPE Aruba CX DSS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md b/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
new file mode 100644
index 0000000..8a2f9fa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF1C7D84-D4FE-4404-AD77-4C0B106AEAA9.md
@@ -0,0 +1,160 @@
+# HPE Aruba CX DSS
+
+## Overview
+
+The HPE Aruba CX DSS plugin brings advanced networking features to HPE Morpheus Enterprise Software by leveraging Aruba CX 10000 series switches. It supports both micro-segmentation and macro-segmentation, integrating seamlessly with HPE and Aruba technologies to improve user experience and operational efficiency.
+
+Implemented as a HPE Morpheus Enterprise `NetworkProvider` in Groovy, the plugin is purpose-built for the HPE Aruba Networking Distributed Services Switch network type (HPE ANW DSS Port Group) and optimized for HPE Morpheus Enterprise environments. It automates the creation and management of networks for HPE ANW DSS Port Groups, connecting servers to Aruba CX 10000 switches within a HVM Cluster.
+
+On each host, the plugin creates Linux bridge interfaces and associates them with VLANs for streamlined network management and configuration. HPE Morpheus Enterprise integrates directly with Aruba Fabric Composer (AFC) to automatically create or delete networks for HPE ANW DSS Port Groups as they are added to or removed from a configured cluster. Adding or removing HVM Hosts in the HVM Cluster triggers the corresponding network changes in AFC, ensuring the network configurations are always up to date.
+
+The plugin also enables the creation of networks with specific VLAN IDs, supporting flexible segmentation and isolation. When a network is created, the plugin provisions the required VLANs on the Aruba CX 10000 switches, ensuring networks are ready for use by Instances within the HVM Cluster.
+
+Additionally, the plugin creates a Libvirt network of type Private. When an Instance is created on the host and associated with this network, a macvtap interface is generated and mapped to the corresponding Linux Interface VLAN ID, ensuring seamless connectivity and isolation.
+
+## Features
+
+- Create and delete networks of type `HPE ANW DSS Port Group` directly from the integration
+- Automatically create and delete networks in Aruba Fabric Composer (AFC) when HVM Hosts are added or removed from the HVM Cluster
+- Manage network configurations through seamless integration with AFC
+- Enable both micro-segmentation and macro-segmentation for flexible network isolation
+- View detailed summaries and status of Aruba CX 10000 switches
+- Ensure automatic, realtime synchronization of network configurations with Aruba CX 10000 switches
+
+## Prerequisites
+
+The following requirements must be met to deploy and configure the HPE Aruba CX DSS Network plugin in HPE Morpheus Enterprise
+
+- Aruba CX 10000 series switches
+
+  - At least two Aruba CX 10000 switches are configured
+  - VSX and KeepAlive are configured
+  - Switches are connected to the upstream network
+- Pre-existing HVM Cluster
+
+  - Ensure all hosts within the HVM Cluster are physically connected to the CX 10000 switches for optimal network integration and redundancy
+- HPE Morpheus Enterprise appliance version 8.0.6 or higher
+
+  - AFC and PSM are deployed and reachable from the
+- Aruba Fabric Composer (AFC) version 7.2 or higher, deployed as a VM
+- AMD Pensando PSM (Policy and Services Manager), deployed as a VM
+
+NOTE
+
+- Download AFC and PSM from the [HPE Networking Support portal](https://networkingsupport.hpe.com/downloads/software/RmlsZTo0YzQ2MzIyYS0xOTU2LTExZjAtYTMzNS0yZmRkN2QyMjdhOTY%253D)
+- For more information on deploying AFC and PSM, refer to the official documentation
+- The AFC and PSM must have network connectivity to the CX 10000 switches
+- Making full use of the HPE Morpheus Enterprise Aruba CX 10000 integration requires credentials for AFC with API access granted and read/write access to AFC configuration
+
+## Adding HPE Aruba CX DSS Network Integration
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Integrations
+2. Select + Add > Networking > HPEAruba CX DSS 
+
+   ![../../_images/addIntegration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-61F5952F-CDFE-43E1-8A2B-445824B876A5-high.png)
+3. Enter the following details in the ADD NETWORK INTEGRATION form: 
+
+   NAME
+   :   Name of the integration in HPE Morpheus Enterprise
+
+   AFC ADDRESS
+   :   Enter the network address of the AFC
+
+   AFC USERNAME
+   :   Enter the username
+
+   AFC PASSWORD
+   :   Enter the password
+
+   FABRIC NAME
+   :   Enter the fabric name from the AFC
+
+       ![../../_images/2_create_network_integration.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5A349FA9-6B14-494D-B218-9F082BE5E18A-high.png)
+4. Click Add Network Integration
+
+### Results
+
+Upon add, the HPE Aruba CX DSS Network integration will be created.
+
+NOTE
+
+All fields can be edited after saving.
+
+## Manage Security Groups and Rules in Morpheus
+
+To manage security groups and rules in Morpheus, follow these steps:
+
+1. Navigate to Infrastructure > Network > Security Groups
+2. Select + ADD
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7883AC52-480A-4E33-AB01-6703E3A41809-high.png)
+3. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2145D633-F35B-41FC-950C-363353E38E8B-high.png)
+4. Within the new Security Group, select + Add Rule
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2BA30350-BAC9-420C-90A3-381E66B9AF9D-high.png)
+5. Select Save Changes
+
+   ![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CA593188-8380-492C-AAA7-08766D278427-high.png)
+
+## Create HPE ANW DSS Port Group Network
+
+### About this task
+
+To create an HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Network > Networks
+2. Select + Add Network > HPE ANW DSS Port Group 
+
+   ![../../_images/3.1_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3CE7AFEC-D544-4E9A-9277-1343D8DCD7BE-high.png)
+3. Select the Network Service in the CREATE NETWORK form: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3A253CC3-F827-4CA3-A2C5-58F8FEC8C30D-high.png)
+4. Enter the following details in the CREATE NETWORK form. Note that the values in the screenshot are reference examples. Input only the values intended for the actual network: 
+
+   ![../../_images/3.2_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-34B08F15-1A6E-4E91-97C0-59D865049E4A-high.png)
+5. Save the network by clicking on Save changes. 
+
+   ![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-02143765-1935-4568-A755-9A6B134CA122-high.png)![../../_images/3.3_add_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BF4B2385-7813-4CB8-912B-DCF724834F47-high.png)
+6. The network will be created and displayed in the list of networks. 
+
+   ![../../_images/3.4_network_created.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2ABDBDC9-8594-4248-B7F8-056488423C77-high.png)
+
+## Delete HPE ANW DSS Port Group Network
+
+### About this task
+
+To delete a HPE ANW DSS Port Group network, follow these steps:
+
+### Procedure
+
+1. Navigate to
+2. Select the network you want to delete from the list.
+3. Click on the delete icon (🗑) next to the network name. 
+
+   ![../../_images/4_delete_network.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5DFCE9ED-5DDA-469D-B118-24F0B3AC0429-high.png)
+
+## View HPE Aruba CX DSS Network Integration
+
+To view the HPE Aruba CX DSS Network integration, follow these steps:
+:   1. Navigate to Infrastructure > Network > Integrations
+    2. Select the HPE Aruba CX DSS integration from the list.
+
+       ![../../_images/5.1_list_network_integrations.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-5F56F425-47AA-4B32-9A7B-48C69C82CFAB-high.png)
+       - `Summary` - Click on the Summary tab to view the summary of the integration.
+
+         ![../../_images/5.2_view_integration_summary.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-0B2B766C-E581-4C17-BE5D-C95F72BDCB20-high.png)
+       - `Switches` - Click the Switches tab to view detailed information about all Aruba CX 10000 switches managed by the integration.
+
+         ![../../_images/5.3_view_integration_details.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A5481BCF-8C48-4106-B3C2-F0AD92CEFEE3-high.png)
+       - `Networks` - Click on the Networks tab to view the networks associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C93D74CC-3795-4FA8-A12A-BADF901EB1AB-high.png)
+       - `Firewalls` - Click on the Firewall tab to view firewall policies associated with the integration.
+
+         ![../../_images/5.4_view_integration_networks.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-FC71FD7B-012A-4291-9519-0AFD8374D65C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json b/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
new file mode 100644
index 0000000..4f1763d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+  "title": "ESXi",
+  "ordinal": 394,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.html",
+  "topic_cluster": {
+    "clustering_title": "ESXi",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6",
+        "clustering_title": "ESXi"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md b/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
new file mode 100644
index 0000000..d0029da
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF2E9770-41E5-4B45-BF8C-5021CBABF4C6.md
@@ -0,0 +1,159 @@
+# ESXi
+
+## About this task
+
+The ESXi Cloud type enables managing and provisioning to ESXi hosts, even without the ESXi API enabled.
+
+IMPORTANT
+
+The VMware ESXi integration is for adding a single ESXi / vSphere Hypervisor host. If you have vCenter please use the VMWare vCenter cloud type for full vSphere integraiton features.
+
+To get started with VMware ESXi, simply add a VMware ESXi Cloud in either the Infrastructure  >  Clouds or Infrastructure  >  Groups section.
+
+## Procedure
+
+1. Select `+ Create Cloud` Button
+2. Select ESXi from the Add Cloud modal
+3. Select NEXT
+4. Provide the following information. 
+
+   Cloud Configuration
+
+   NAME
+   :   Name of the Cloud in HPE Morpheus Enterprise
+
+   CODE
+   :   Unique code used for api/cli, automation and policies.
+
+   LOCATION
+   :   Description field for adding notes on the cloud, such as location.
+
+   VISIBILITY
+   :   For setting cloud permissions in a multi-tenant environment. Not applicable in single tenant environments.
+
+   TENANT
+   :   If Visibility is set to Private, select the Tenant the Cloud resources will assigned to.
+
+   ENABLED
+   :   When disabled, automatic Cloud sync is paused and the Cloud will not be selectable for provisioning.
+
+   AUTOMATICALLY POWER ON VMS
+   :   When enabled, HPE Morpheus Enterprise will maintain the expected power state of managed VMs. HPE Morpheus Enterprise will power on any managed VMs in the Cloud that have been shut down for unknown reasons (not powered off by HPE Morpheus Enterprise) to ensure availability of services.
+
+       NOTE
+
+       When “AUTOMATICALLY POWER ON VMS” is enabled, the power state of managed VMs should be maintained in HPE Morpheus Enterprise. This setting is not applicable to discovered/unmanaged resources.
+
+   Details
+
+   - ESXi Host name or IP address
+   - Username ( This is normally root )
+   - Password
+
+## Results
+
+NOTE
+
+If you receive the message “Error! Invalid cloud config” Please ensure you have ssh enabled on the ESXi host.
+
+## Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+## CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+## INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+## Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
+
+IMPORTANT
+
+ESXi provisioning require a vmx file, which is not included in an OVF/OVA export from vCenter. A proper vmx file must be included when adding a vmdk/ovf/ova image to Virtual Images in Morpheus for successful provisioning.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json b/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
new file mode 100644
index 0000000..5b1463b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+  "title": "vCPU Placement",
+  "ordinal": 188,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.html",
+  "topic_cluster": {
+    "clustering_title": "vCPU Placement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C",
+        "clustering_title": "vCPU Placement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md b/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
new file mode 100644
index 0000000..045999e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-DF59F3EB-3312-40C8-BCDD-D9BE2EFCDA8C.md
@@ -0,0 +1,28 @@
+# vCPU Placement
+
+vCPU placement settings relate to vCPU placement within the physical topology of the CPU. Since a vCPU is just a schedulable thread the hypervisor maps onto physical cores, we can create performance increases through smart scheduling. A simplified CPU topology might look something like this:
+
+```
+```
+Socket  
+ └── NUMA node  
+     └── Core  
+         └── Threads (SMT / Hyper-Threading)
+```
+```
+
+As you can see from the diagram above, multiple physical cores can reside within the same NUMA node. Physical CPU cores within the same NUMA node share the same region of the L3 cache and local memory access. By scheduling vCPUs making up a single VM to cores within the same NUMA node, we can avoid the performance penalties associated with crossing NUMA boundaries and accessing remote memory locations.
+
+HVM Clusters offer three vCPU placement settings. The default setting is **Unmanaged**. Clusters with unmanaged vCPU placement will make no special effort to schedule vCPUs within the same NUMA region. Next is **Region**. Clusters with this vCPU placement will attempt to schedule vCPUs associated with the same VM within the same NUMA region. When flexibility is needed, vCPUs may hop to different physical cores but they will be kept within the same NUMA region. Third is **Pinned**. Clusters with this vCPU placement will also attempt to schedule vCPUS associated with the same VM within the same NUMA region but the vCPUs will remain pinned to same cores. In certain cases, pinning may improve performance and in other cases creating inflexibility may introduce inefficiency.
+
+TIP
+
+Setting **Region** placement is a sensible starting configuration if you don't have a specific reason to choose one of the other two. In internal testing, a 7-10% improvement in prime number generation time was observed with Region pinning versus Unmanaged pinning.
+
+How to Configure vCPU Placement Settings
+
+1. Navigate to Infrastructure > Clusters
+2. Select the desired HVM Cluster
+3. From the Cluster detail page, click Edit
+4. Within the vCPU Placement field, select the desired value. See the paragraphs above for a description of each configuration
+5. Click Save changes
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json b/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
new file mode 100644
index 0000000..5d7901b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+  "title": "morpheus-ctl tips",
+  "ordinal": 25,
+  "parent_title": "Upgrades & Maintenance",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.html",
+  "topic_cluster": {
+    "clustering_title": "morpheus-ctl tips",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C",
+        "clustering_title": "morpheus-ctl tips"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md b/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
new file mode 100644
index 0000000..a393646
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E012A526-E6C4-408D-A69C-AD7BC08B882C.md
@@ -0,0 +1,63 @@
+# morpheus-ctl tips
+
+`morpheus-ctl` is useful beyond reconfigures and starting the ui, and many commands can be run across all services, or scoped to a singe service.
+
+Some common commands include:
+
+morpheus-ctl status
+:   Lists all the installed services and their current status
+
+morpheus-ctl start (service)
+:   This starts all services if no service is specified, or starts the specified service. For example,
+
+    - `morpheus-ctl start/stop/restart/kill` on an all-in-one appliance will start, stop, restart or kill mysql, opensearch, rabbitmq, check-server, guacd and the morpheus-ui, one by one.
+    - `morpheus-ctl start/stop/restart/kill morpheus-ui` will only start, stop, restart or kill the morpheus-ui service, leaving the other service in their current state. Same goes for `morpheus-ctl start/stop/restart/kill mysql`, `morpheus-ctl start/stop/restart/kill opensearch` etc.
+
+`morpheus-ctl` commands:
+
+```
+```
+General Commands:  
+  cleanse  
+    Delete *all* morpheus data, and start from scratch.  
+  help  
+    Print this help message.  
+  reconfigure  
+    Reconfigure the application.  
+  show-config  
+    Show the configuration that would be generated by reconfigure.  
+  uninstall  
+    Kill all processes and uninstall the process supervisor (data will be preserved).  
+ Service Management Commands:  
+   graceful-kill  
+     Attempt a graceful stop, then SIGKILL the entire process group.  
+   hup  
+     Send the services a HUP.  
+   int  
+     Send the services an INT.  
+   kill  
+     Send the services a KILL.  
+   once  
+     Start the services if they are down. Do not restart them if they stop.  
+   restart  
+     Stop the services if they are running, then start them again.  
+   service-list  
+     List all the services (enabled services appear with a *.)  
+   start  
+     Start services if they are down, and restart them if they stop.  
+   status  
+     Show the status of all the services.  
+   stop  
+     Stop the services, and do not restart them.  
+   tail  
+     Watch the service logs of all enabled services.  
+   term  
+     Send the services a TERM.  
+ Opensearch Commands:  
+   open-util  
+     Backup/Restore OpenSearch data  
+ Firewall Commands:  
+   firewall-enable-blocking  
+     Enables firewall blocking mode.
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json b/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
new file mode 100644
index 0000000..f7a74bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+  "title": "Getting Started with Terraform Instance Types",
+  "ordinal": 369,
+  "parent_title": "User Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html",
+  "topic_cluster": {
+    "clustering_title": "Getting Started with Terraform Instance Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E01FA212-4E9E-4403-9508-E4BB971643A3",
+        "clustering_title": "Getting Started with Terraform Instance Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md b/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
new file mode 100644
index 0000000..24e28f5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.md
@@ -0,0 +1,203 @@
+# Getting Started with Terraform Instance Types
+
+[Terraform](https://www.terraform.io/intro/index.html) is a common tool that allows IT administrators to map out infrastructure as code in configuration files and supports all of the popular providers used in the modern datacenter. Once configured, Terraform will plan, deploy, and manage the infrastructure as needed. Configuration files can be brought under version control so teams can easily make changes to environments. Infrastructure can also be monitored for drift and corrective action can easily be taken.
+
+HPE Morpheus Enterprise allows users to on-board or even draft Terraform spec directly. With the configuration on-board, we can begin to piece together infrastructure constructs into the HPE Morpheus Enterprise Library as Layouts and Instance Types. With the Library items staged, users can deploy new infrastructure directly into the selected providers. Once deployed, infrastructure can be monitored for drift from within HPE Morpheus Enterprise UI. When needed, we can plan and take corrective action easily from the detail page of a HPE Morpheus Enterprise Terraform Instance.
+
+In this section, we’ve discussed a high-level overview of Terraform and working with Terraform in the HPE Morpheus Enterprise context. In the next section, we’ll actually onboard Terraform spec, create Library items, and deploy real infrastructure to AWS with HPE Morpheus Enterprise.
+
+## Terraform Instance Types in Action
+
+In this example, we’re going to deploy a VPC and three subnets to AWS using Terraform and HPE Morpheus Enterprise. I’ve created Spec Templates to onboard `.tf` configuration files which handle the AWS provider (with assume role for account flexibility), VPC creation, subnet creation, and variable injection.
+
+We’ll onboard the Terraform configuration files as modular Spec Templates, create new Instance Types with custom Layouts for the HPE Morpheus Enterprise Library, and set up Inputs to inject variable values at provision time. Once deployed, we’ll take a look at the new infrastructure in HPE Morpheus Enterprise and go over the management capabilities for the new environment.
+
+## Spec Templates
+
+Terraform configuration is stored as a Spec Template in HPE Morpheus Enterprise. You can store your configuration as one monolithic file for each Instance Type you intend to create or you can create individual Spec Templates for modular pieces which can be reused across multiple Instance Types. When added to the Layout later, we’ll be able to include as many Spec Templates as we wish which enables us to reuse smaller modular pieces if desired.
+
+Spec Templates are added in the HPE Morpheus Enterprise Library (Library > Templates > Spec Templates tab). We can pull in the template from some type of repository, such as through a Github integration, or write new spec directly into the New Spec Template modal. In most cases, the spec will be pre-existing and pulled in from a version-controlled repository but here I have my Terraform spec entered locally. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+In the VERSION field at the bottom of the TF Spec Template modal, enter a Terraform version number to force that version to be used. This version is only honored if the Terraform Runtime setting (Administration > Settings > Provisioning) is set to “auto”. When “manual” is selected as the Terraform Runtime setting, HPE Morpheus Enterprise will simply use the version installed on the appliance box.
+
+TIP
+
+When declaring variables, keep in mind that HPE Morpheus Enterprise expects users to follow Terraform best practices. For example, when a variable type is not defined, it defaults to string. See [Terraform Documentation](https://www.terraform.io/docs/language/values/variables.html) for additional resources on variable declaration.
+
+![../../_images/1newSpec.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C459745E-846B-4D4E-8F3B-47D422073E2C-high.png)
+
+### AWS Subnet by Count
+
+```
+```
+# This spec template creates AWS subnets based on the count requested utilizing the vpc cidr provided in var.vpc_cidr variable  
+locals {  
+  bitCount = sum([tonumber(local.subnet_options.cidrMask),-tonumber(split("/",var.vpc_cidr)[1])])  
+}  
+resource "aws_subnet" "main" {  
+    count = tonumber(var.subnetCount)  
+    vpc_id     = aws_vpc.main.id  
+    cidr_block = cidrsubnet(var.vpc_cidr, local.bitCount, count.index)  
+    tags = merge(  
+        local.default_tags,  
+        {  
+        Name = "${var.vpc_name}-subnet-0${count.index}"  
+        }  
+    )  
+}  
+output "aws_subnet" {  
+  value = aws_subnet.main  
+  sensitive = true  
+}
+```
+```
+
+### AWS Terraform Default Vars
+
+```
+```
+variable "access_key" {  
+  type        = string  
+}  
+variable "secret_key" {  
+  type        = string  
+}  
+variable "subnetCount" {  
+  type = number  
+  default = "<%=customOptions.subnetCount%>"  
+}  
+variable "sensitive_thing" {  
+  type = string  
+  default = "this_var_is_sensitive"  
+  sensitive = true  
+}
+```
+```
+
+### AWS Provider Role Assume
+
+```
+```
+terraform {  
+  required_providers {  
+    aws = {  
+      source = "hashicorp/aws"  
+      version = ">= 3.35.0"  
+    }  
+  }  
+}  
+provider "aws" {  
+  region     = local.vpc_options.region  
+  access_key = var.access_key  
+  secret_key = var.secret_key  
+  assume_role {  
+    # The role ARN within Account B to AssumeRole into.  
+    role_arn = "arn:aws:iam::${local.vpc_options.aws_account}:role/OrganizationAccountAccessRole"  
+  }  
+}
+```
+```
+
+### AWS Terrform Locals
+
+```
+```
+locals {  
+  #  Common tags to be assigned to all resources  
+  default_tags = {  
+    Owner    = "<%=username%>"  
+    Group = "<%=groupName%>"  
+    Management_Tool = "Terraform"  
+    Management_Platform = "Morpheus"  
+  }  
+  subnet_options = {  
+    cidrMask = "<%=customOptions.cidrMask%>"  
+    subnetCount = "<%=customOptions.subnetCount%>"  
+  }  
+  vpc_options = {  
+    region = "<%=customOptions.awsRegion%>"  
+    aws_account = "<%=customOptions.awsAccount%>"  
+  }  
+}
+```
+```
+
+### AWS VPC
+
+```
+```
+variable "vpc_cidr" {  
+  type        = string  
+  description = "CIDR for the the VPC"  
+  default = "172.16.0.0/24"  
+}  
+variable "vpc_name" {  
+  type        = string  
+  description = "Name for the VPC"  
+  default = "durka"  
+}  
+resource "aws_vpc" "main" {  
+    cidr_block = var.vpc_cidr  
+ tags = merge(  
+    local.default_tags,  
+    {  
+      Name = var.vpc_name  
+    }  
+  )  
+}  
+output "aws_vpc" {  
+  value = aws_vpc.main  
+  sensitive = true  
+}
+```
+```
+
+NOTE
+
+In the AWS Terraform Locals example Spec Template above, pre-provision variables are used. the use of [pre-provision](https://docs.morpheusdata.com/en/latest/troubleshooting/Variables_Examples.html?highlight=variables#pre-provision-vars) variables to store the value for Owner and Group, among other things. See the variables section of HPE Morpheus Enterprise documentation (linked in the prior sentence) for a listing of other possible pre-provision variables and a complete map of variables which can be resolved after provisioning has completed.
+
+## Inputs and Option Lists
+
+In order to create the Layout later in the guide, I need to create four Inputs so the user can make certain selections at provision time. I wrote my Terraform Configuration with this flexibility in mind so that the same Instance Type can be reused in different scenarios. In this particular case, I’m populating the Inputs with manual Option Lists but they can also be populated through REST calls or calls to the HPE Morpheus Enterprise API when needed.
+
+Option Lists are created in the Library (Library) under the Option Lists tab. These are lists of items which will be used to create dropdown selections at provision time. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES. I’ve created one each for the AWS account selection, region selection, and CIDR mask input.
+
+![../../_images/7optionList.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8AB93390-1CB2-45BF-B910-8C87A842B3E3-high.png)
+
+Inputs are also created in the Library under the Inputs tab. In this case, I’m creating four Inputs. Three of them will display as dropdown selections and will be tied to one of the Option Lists we just made. The other will be a simple text input where the user can indicate the total number of subnets that should be created. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/8optionType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-07E4ED98-50BB-481E-BE1E-02C558B54EB5-high.png)
+
+## Instance Type
+
+At this point we’re ready to create a new Instance Type. We’ll give the Instance Type a name, which users will use to identify the Instance Type from the list in the provisioning wizard. We don’t need to set much else in this case, most of the pieces we’ve created in previous steps will be associated with the Layout that we create next. The Layout will also be tied to the Instance Type we’re creating now. Instance Types are also created in the Library (Library) under the Instance Types tab. Click + ADD, complete the fields as I’ve done in the example below and click SAVE CHANGES.
+
+![../../_images/9instanceType.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A7B59327-4830-4BD7-9653-DBC1F89E3304-high.png)
+
+## Layout
+
+The Layout will bring together everything we’ve made to this point, the Spec Templates, Inputs and the Instance Type. We can add a new one from the Instance Type detail page (Library > Blueprints > Instance Types > Selected Instance Type) by clicking + ADD LAYOUT. We can also create one from the Layouts section (Library > Blueprints > Layouts) by clicking + ADD.
+
+First, change the TECHNOLOGY value to Terraform and the fields will change to allow proper configuration. Next, provide a name for your Layout. If you’re creating the Layout through the Layout tab rather than from the Instance Type detail page, you’ll need to identify the Instance Type the Layout goes with. Using the typeahead fields at bottom of the modal window, add our four Inputs and our five Spec Templates to the Layout. Finally, point the layout to a TFVAR SECRET from HPE Morpheus Enterprise Cypher if needed. You can see a screenshot of my Layout configuration below
+
+![../../_images/10Layout.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6AAAC87D-6445-4F94-A30B-EA2357B3BDE8-high.png)
+
+## Provisioning
+
+Now, we’re ready to provision new infrastructure into AWS using HPE Morpheus Enterprise and Terraform. Just like any other Instance Type, we begin from the Instances list page (Provisioning > Instances) and click + ADD. Select the Instance Type we’ve just created and move on to the GROUP tab of the wizard. Here you’ll give the new instance a name and select your Group and Cloud. Once finished, you’ll move on to the CONFIGURE tab where we’ll see the Inputs we created and associated with the Layout. Once finished with this tab, step through the rest of the wizard to complete the process. You can see the options I’ve selected for this configuration in the image below.
+
+![../../_images/11configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B2B38E32-09D7-4601-BF40-680C861C7B59-high.png)
+
+## Review the New Instance
+
+After completing the wizard, from the History tab of the Instance detail page users can review the Terraform plan being executed and see the output while the resources are still being provisioned.
+
+![../../_images/12historyTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6D94B4FA-C8D4-4F10-81BA-651AC732F741-high.png)
+
+Once the provisioning process is complete, head to the State tab. Here we can see and link through to the associated Spec Templates. If needed, you can also edit the configuration spec by clicking on the pencil icon at the end of the row for any listed Spec Template.
+
+By clicking APPLY STATE, the user can once again see the Input selections which were presented during the initial provisioning and make changes when needed. After making changes and clicking NEXT, HPE Morpheus Enterprise will show the plan output no different than if you’d run `terraform plan`. On clicking COMPLETE, the plan will be executed as if you’d run `terraform apply`. Back on the State tab you will see the output from the Apply process as well as an indicator of the success or failure of the operation.
+
+![../../_images/13stateTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BFBCDC99-36EC-4D45-A29E-222D41543C62-high.png)
+
+HPE Morpheus Enterprise will also regularly check for drift from the Terraform configuration. On the State tab near the top is a “Drift Status” indicator. This will either show Drift or No Drift depending on the situation. HPE Morpheus Enterprise will automatically check for drift every few minutes but you can perform a manual check at any time by clicking REFRESH STATE. Drift can be corrected when needed by reapplying state (APPLY STATE button).
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json b/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
new file mode 100644
index 0000000..bddede4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+  "title": "Helm Blueprints",
+  "ordinal": 134,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.html",
+  "topic_cluster": {
+    "clustering_title": "Helm Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD",
+        "clustering_title": "Helm Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md b/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
new file mode 100644
index 0000000..7edf706
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E02DD704-C987-41BB-AF3F-A23F35C097BD.md
@@ -0,0 +1,27 @@
+# Helm Blueprints
+
+If you’re using Helm Charts to manage Kubernetes applications, HPE Morpheus Enterprise allows you to bring them in from a Git repository as a Blueprint. The selected repository must be integrated with HPE Morpheus Enterprise before creating the Blueprint.
+
+To create a new Helm Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select Helm. Click guilabel:NEXT.
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+In the Helm Configuration section, complete the following fields as needed to sync in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **CHART PATH:** The path to the folder within the repository containing your configuration files, enter “./” if this is the top level folder within the repository
+- **CONFIG:** Config files within your selected folder are displayed here for confirmation
+
+Once finished, click COMPLETE.
+
+Your new Helm Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json b/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
new file mode 100644
index 0000000..8b1bda8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+  "title": "Key Pairs",
+  "ordinal": 241,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.html",
+  "topic_cluster": {
+    "clustering_title": "Key Pairs",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F",
+        "clustering_title": "Key Pairs"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md b/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
new file mode 100644
index 0000000..ffc566b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E04CE9DF-E832-41CB-B559-1800B7943A2F.md
@@ -0,0 +1,65 @@
+# Key Pairs
+
+The key pairs section enables the following actions: Add and Delete key pairs. Key pairs are commonly used by HPE Morpheus VM Essentials for accessing instances via SSH. HPE Morpheus VM Essentials stores key pairs to simplify administration and access across both private and public clouds.
+
+HPE Morpheus VM Essentials only accepts key pairs in PEM format (for example, a private key beginning with `-----BEGIN RSA PRIVATE KEY-----`) and accepts RSA (PKCS#1 or PKCS#8, default), DSA (PKCS#1 or PKCS#8), EC (PKCS#8), and ed25519 (PKCS#8) keys. If you have a key in another format, such as OpenSSH, convert the key:
+
+```
+```
+#No passphrase  
+ssh-keygen -m pem -f /path/to/key  
+#With passphrase  
+ssh-keygen -p -P "old passphrase" -N "new passphrase" -m pem -f path/to/key
+```
+```
+
+## Add Existing Key Pair
+
+### About this task
+
+To generate a existing Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Existing Key Pair”
+3. From the Add Key Pair modal input the following as needed: 
+
+   - Name
+   - Public Key
+   - Private Key
+   - Passphrase
+
+   NOTE
+
+   Certain features do not require storage of the private key.
+
+## Generate Key Pair
+
+### About this task
+
+To generate a Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, click + ADD and select “Generate Key Pair”
+3. After naming the new key pair, HPE Morpheus VM Essentials will reveal both the public and private key
+
+### Results
+
+NOTE
+
+After the private key is initially revealed it will not be shown again. If needed, you may view the public key from the Keypairs list page at any time going forward. This key pair can be associated with your Linux user details in HPE Morpheus VM Essentials user settings. The public key will be added to the authorized\_keys file on provisioned workloads where your Linux user is added at provision time.
+
+## Delete Key Pair
+
+### About this task
+
+To Delete Key Pair:
+
+### Procedure
+
+1. Navigate to Infrastructure > Trust > Key Pairs
+2. On the Key Pairs tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected key pair
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json b/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
new file mode 100644
index 0000000..110ad84
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+  "title": "OpenShift Clusters",
+  "ordinal": 202,
+  "parent_title": "Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.html",
+  "topic_cluster": {
+    "clustering_title": "OpenShift Clusters",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D",
+        "clustering_title": "OpenShift Clusters"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md b/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
new file mode 100644
index 0000000..971cf4d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E1159A9B-4A53-400A-A1E7-8604539EB39D.md
@@ -0,0 +1,11 @@
+# OpenShift Clusters
+
+**Subtopics**  
+
+- **[Overview](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-BEB1E10D-E69E-4065-92C0-9532D37DCDC4.html)**
+- **[Prerequisites](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DBF8B094-37D3-4729-9364-6F6CB1679CDF.html)**
+- **[Features](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html)**
+- **[Adding the OpenShift Plugin](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html)**
+- **[Adding OpenShift Clusters](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-092B4E74-3662-4E21-9DA0-67958362DBE4.html)**
+- **[Monitoring the Cluster](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CC1F0809-F068-41F6-853A-0033148C3436.html)**
+- **[Provisioning into OpenShift](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-786D5554-1448-4001-A39C-647F22CA9278.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json b/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
new file mode 100644
index 0000000..5ab7b96
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+  "title": "SELinux",
+  "ordinal": 10,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.html",
+  "topic_cluster": {
+    "clustering_title": "SELinux",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182",
+        "clustering_title": "SELinux"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md b/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
new file mode 100644
index 0000000..633687f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E2B7B9E6-378C-444C-A3CD-4096BABC2182.md
@@ -0,0 +1,7 @@
+# SELinux
+
+If not required by organizational policy, we recommend setting SELinux to “Permissive” or “Disabled” modes to prevent any unnecessary security-related issues. HPE Morpheus Enterprise versions 3.6.0 and higher do support “Enforcing” mode if it is required by your organization due to IT policies. Set the mode appropriately prior to running the HPE Morpheus Enterprise installer and it will make the required changes based on your chosen SELinux context.
+
+IMPORTANT
+
+Setting SELinux to “Enforcing” mode requires policies to be configured correctly in order for the HPE Morpheus Enterprise appliance to function correctly.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json b/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
new file mode 100644
index 0000000..e658dc0
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+  "title": "Code",
+  "ordinal": 96,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.html",
+  "topic_cluster": {
+    "clustering_title": "Code",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE",
+        "clustering_title": "Code"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md b/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
new file mode 100644
index 0000000..27861ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E2CD25BD-F80D-4E81-B0CD-D11C63E152FE.md
@@ -0,0 +1,37 @@
+# Code
+
+NOTE
+
+In v5.3.2+, `provisioning/deployments` is moved to `provisioning/code`.
+
+Provisioning > Code contains the Repositories, Deployments and Code Integrations sections.
+
+## Required Role Permissions
+
+Access and capabilities for the **Code** section is determined by the following role permissions:
+
+Role: Feature Access: `Infrastructure: Groups`
+:   - None: Cannot access Provisioning: Code section
+    - Read or Full: Can access Provisioning: Code section
+
+Role: Feature Access: `Provisioning: Code Repositories`
+:   - None: Cannot access Provisioning: Code Repositories
+    - List Files: Can browse repo folder and file names, select branch, refresh Repositories. Cannot access/view file contents.
+    - Read or Full: Can browse repo folder and file names, select branch, refresh Repositories and access/view file contents.
+
+Role: Feature Access: `Provisioning: Code Deployments`
+:   - None: Cannot access Provisioning: Code Deployments.
+    - Read: Can view Code Deployments. Cannot create, delete or edit Code Deployments.
+    - Full: Can create, delete and edit Code Deployments.
+
+Role: Feature Access: `Provisioning: Code Integrations`
+:   - None: Cannot access Provisioning: Code Integrations.
+    - Read: Can view Code Integrations. Cannot create, delete or edit Code Integrations.
+    - Full: Can create, delete and edit Code Integrations
+
+**Subtopics**  
+
+- **[Repositories](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-25A367DD-64FA-417A-B88B-B1D95C3E258B.html)**
+- **[Import and Export](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-39D4284E-C733-48AD-94DE-CD929AEB0431.html)**
+- **[Deployments](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5A41A29A-29C5-4A98-8CD6-37E8DAAB42CA.html)**
+- **[Code Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-44272A47-8855-48A0-B475-E940CE97DD7A.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json b/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
new file mode 100644
index 0000000..524cc65
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+  "title": "Github",
+  "ordinal": 482,
+  "parent_title": "Deployment",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.html",
+  "topic_cluster": {
+    "clustering_title": "Github",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7",
+        "clustering_title": "Github"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md b/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
new file mode 100644
index 0000000..541ec0a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E3135D5C-0968-46FE-A61E-CBD55ECE30C7.md
@@ -0,0 +1,92 @@
+# Github
+
+Integrate your Github account with HPE Morpheus Enterprise and have access to all your public and private repositories within the platform. Use your existing code and any future code to build automation Tasks and Workflows, onboard Spec Templates for Terraform and Kubernetes to build App configurations, and more. Integrated Github repositories also populate the Code list page (Provisioning > Code) where repositories can be browsed and individual files can be viewed. Repositories can be configured as [import and export](https://docs.morpheusdata.com/en/latest/provisioning/code/code.html?highlight=import#import-and-export) targets from Code detail pages as well. Each time code from your repositories is invoked in Tasks, Workflows, Spec Templates, and more, HPE Morpheus Enterprise will pull the current live version (depending on configuration) so any recent changes to the code are used.
+
+## Generating a Personal Access Token (Classic)
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens (described in the next section). To create a new access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Tokens (classic)”
+7. Click Generate new token
+8. Click “Generate new token (classic)”
+9. Give the new token at least access to everything in the “repo” scope
+10. Click Generate token
+11. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+We recommend using a long-lived token, Github even includes the option to have no expiration on your tokens (for classic personal access tokens only, not fine-grained tokens). Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Generating a Fine-Grained Token
+
+### About this task
+
+As of August 13, 2021, due to policy changes on the Github platform, HPE Morpheus Enterprise requires an access token to authenticate with Github. Password authentication is no longer possible. HPE Morpheus Enterprise accepts both classic personal access tokens and fine-grained tokens. To create a new fine-grained access token:
+
+### Procedure
+
+1. Log in to Github
+2. Click on your account profile avatar in the upper-right portion of the window
+3. Click Settings
+4. From the left nav, click on Developer Settings
+5. Once again from the left nav, click Personal access tokens
+6. Click “Fine-grained tokens”
+7. Click Generate new token
+8. Give the token access to all repositories unless you will only need to work with specific repositories within HPE Morpheus Enterprise
+9. Click Generate token
+10. Copy the access token and save it for the next step when the integration is created
+
+### Results
+
+TIP
+
+Fine-grained tokens can be created with an expiration date of up to one year. Should the token expire, any HPE Morpheus Enterprise automation, App Blueprints, and Terraform or Kubernetes Spec Templates which are based on code contained in your repositories will no longer work. This could lead to failed provisioning and time spent troubleshooting to isolate the issue until the Github integration is refreshed with a new access token.
+
+## Creating an Integration
+
+### About this task
+
+New Github integrations are created either in the global integrations section (Administration > Integrations) or in the code integrations section (Provisioning > Code > Integrations). You will need a Github access token to complete this step, see the prior section for instructions on obtaining a Github access code.
+
+### Procedure
+
+1. Navigate to the global integrations section (Administration > Integrations) or the code integrations section (Provisioning > Code > Integrations)
+2. Click +ADD
+3. Click Github
+4. Configure the following: 
+
+   - NAME: A friendly name for the Github integration in HPE Morpheus Enterprise
+   - ENABLED: When marked, this Github integration is active and any code repositories are available for building HPE Morpheus Enterprise automation and other constructs within the platform
+   - USERNAME: The username for your Github account
+   - PASSWORD: Copy your access token here rather than in the “ACCESS TOKEN” field. See the “Important” box below for additional details
+   - ACCESS TOKEN: Do not use this field. See the “Important” box below for additional details
+   - KEY PAIR: (Optional) Select a stored SSH keypair for Github SSH authentication
+   - ENABLE GIT REPOSITORY CACHING: When unmarked, HPE Morpheus Enterprise retrieves code fresh from the repository each time it’s invoked. When marked, HPE Morpheus Enterprise will use a cached version of the code if it’s less than five minutes old. In general, this should be left unmarked unless you are experiencing performance issues related to very large amounts of code being invoked many times during a deployment
+5. Click SAVE CHANGES
+
+### Results
+
+IMPORTANT
+
+Your access token should be pasted into the PASSWORD field and not the ACCESS TOKEN field. If the ACCESS TOKEN field is used, the repository will create successfully and many features will work. However, in Code detail pages (Provisioning > Code > Selected code detail page), you will not be able to browse files in private Github repositories unless the access token is pasted into the PASSWORD field. New Github integrations should be created by pasting the access token in the PASSWORD field and the ACCESS TOKEN field should be ignored.
+
+NOTE
+
+In certain cases, it can take several seconds for the integration process to complete and the ADD INTEGRATION modal to be dismissed.
+
+## Viewing an Integrated Github Account
+
+When authentication is successful, click into the new Github integration from the list of available integrations. The Organizations tab will list each organization the Github account is associated with. The Repositories tab lists all public and private repositories which are associated with the account. We can also click in to each repository to view its files and folders, as well as create specific types of automation or Spec Templates from the files directly in this view.
+
+![../../_images/github.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-19D7B591-B18D-4BB5-A378-425A0110A7C7-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json b/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
new file mode 100644
index 0000000..1408812
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+  "title": "Overview",
+  "ordinal": 105,
+  "parent_title": "Tasks",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md b/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
new file mode 100644
index 0000000..e393824
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E32BB52B-7EED-4E8A-8BDC-6AD5D4CC22F0.md
@@ -0,0 +1,7 @@
+# Overview
+
+There are many Task Types available, including scripts added directly, scripts and templates from the Library section, recipes, playbooks, puppet agent installs, and http (api) calls. Tasks are primarily created for use in Workflows, but a single Task can be executed on an existing instance via Actions  >  Run Task.
+
+**Subtopics**  
+
+- **[Role Permissions](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-37778D27-BA20-4EAB-8717-79D7B62A5DC3.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json b/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
new file mode 100644
index 0000000..22db4b4
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+  "title": "Compute",
+  "ordinal": 210,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E3911F3D-F635-42FA-B014-078FD60D3130.html",
+  "topic_cluster": {
+    "clustering_title": "Compute",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E3911F3D-F635-42FA-B014-078FD60D3130",
+        "clustering_title": "Compute"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md b/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
new file mode 100644
index 0000000..8aed992
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E3911F3D-F635-42FA-B014-078FD60D3130.md
@@ -0,0 +1,23 @@
+# Compute
+
+![../../_images/infra_compute_header_5.4.3.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-04AE9DB4-27C9-40E0-8E37-1BCFA3CD8C32-high.png)
+
+NOTE
+
+The Infrastructure `Hosts` page from previous versions has been renamed to `Compute` and updated with `Container` and `Resource` sections.
+
+The Infrastructure  >  Compute section provides a universal stage for viewing and managing Hosts, Virtual Machines, Containers, Resources, and Bare Metal across Clouds.
+
+In this section you can:
+
+- View & Manage and Hosts, Virtual Machines, Containers, Resources, Bare Metal and Hypervisors
+- Add manual Virtual Machines and Bare Metal Hosts
+- Convert Hosts, Virtual Machines and Bare Metal to Managed
+
+**Subtopics**  
+
+- **[Hosts](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-38EBAF72-47D6-4379-AF01-7F073DD7CF6B.html)**
+- **[Virtual Machines](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7CA53A6D-026B-4977-8247-349750CE4EB9.html)**
+- **[Containers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8808CDAD-319E-4259-99D8-4D43440E63FE.html)**
+- **[Resources](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C9A343EC-3D42-45B6-9D74-5FFD5D7F87DE.html)**
+- **[Bare Metal](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json b/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
new file mode 100644
index 0000000..4e28624
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+  "title": "Features",
+  "ordinal": 205,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.html",
+  "topic_cluster": {
+    "clustering_title": "Features",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3",
+        "clustering_title": "Features"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md b/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
new file mode 100644
index 0000000..624c03c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E39624FD-2F0D-44FA-887C-97EBC34A84D3.md
@@ -0,0 +1,14 @@
+# Features
+
+- Adds a new Cluster type, which is used to onboard pre-existing OpenShift clusters into HPE Morpheus Enterprise
+- Enables inventory synchronization for workloads provisioned outside of HPE Morpheus Enterprise in the OpenShift console
+- Monitor high-level cluster health details such as host numbers, alarms, and high CPU, memory or disk use situations
+- Monitor individual host and VM health details such as high CPU, memory, disk use, or network I/O situations
+- Onboard network objects, device-agnostic storage objects, and virtual images to enable OpenShift provisioning from the HPE Morpheus Enterprise provisioning wizard UI
+- Supports IPv4 and IPv6 networking
+- Adds new Instance Type to the HPE Morpheus Enterprise provisioning wizard for easy provisioning of new OpenShift virtualized workloads
+- VM provisioning supports the use of existing templates and service plans
+- Interface with Morpheus-type IP Pools or IP Pools sourced from IPAM integrations throughout the lifecycle of OpenShift workloads
+- Utilize the HPE Morpheus Enterprise automation engine for provisioning and for day two operations across the Instance lifecycle
+- Supports HPE Morpheus Enterprise labels and tagging features for resource organization
+- Provides guest console access into OpenShift-hosted virtual machines
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json b/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
new file mode 100644
index 0000000..3fa94cc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+  "title": "Integrations",
+  "ordinal": 224,
+  "parent_title": "Network",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md b/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
new file mode 100644
index 0000000..8d59ca1
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E4BA656B-FE5C-49B2-BFD3-C627E8C39C56.md
@@ -0,0 +1,49 @@
+# Integrations
+
+## Overview
+
+The Network Integrations section allows you to add and manage IPAM, DNS, and Service Registry integrations. These services can also be added in the Administration > Integrations section.
+
+The following integrations are currently supported:
+
+Networking
+
+- Cisco ACI
+- VMWare NSX
+
+IPAM
+
+- Infoblox
+- Bluecat
+- phpIPAM
+
+Security
+
+- Cisco ACI
+
+DNS
+
+- Microsoft DNS
+- PowerDNS
+- Route 53
+
+## Scoping Services
+
+NETWORKING
+:   Networking integrations are available in the NETWORK MODE dropdown located under the Advanced Options section in Cloud configurations.
+
+IPAM
+:   IPAM integrations will populate pools in the IP Pool section, which are available for assignment to networks in the NETWORK POOL dropdown when configuring a network.
+
+SECURITY
+:   Security integrations are available in the SECURITY SERVER dropdown located under the Advanced Options section in Cloud configurations.
+
+DNS
+:   DNS integrations will populate domains in the Infrastructure  >  Network  >  Domains section, and are available in the DOMAIN dropdown located under the Advanced Options section in Cloud, Group, and Network configurations, as well as in the Configure section of the Create Instance wizard. DNS integrations are also available in the DNS SERVICE dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+Service Registry
+:   Service Registry integrations are available in the SERVICE REGISTRY dropdown located under the Advanced Options section in Cloud and Group configurations.
+
+NOTE
+
+Infoblox will also appear as a DNS INTEGRATION option in Clouds and Groups after adding Infoblox IPAM Integration.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json b/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
new file mode 100644
index 0000000..5234563
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+  "title": "Policy Types",
+  "ordinal": 317,
+  "parent_title": "Policies",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.html",
+  "topic_cluster": {
+    "clustering_title": "Policy Types",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF",
+        "clustering_title": "Policy Types"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md b/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
new file mode 100644
index 0000000..b205c81
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E4F64CCB-AB73-4D5D-BC9A-EB45E697FEAF.md
@@ -0,0 +1,117 @@
+# Policy Types
+
+Approve Delete
+:   Sets an approval requirement for deleting Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow. On delete request, Instances will be shut down and only deleted if approved.
+
+Approve Provision
+:   Sets an approval requirement for provisioning Instances or Apps within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Reconfigure
+:   Sets an approval requirement for reconfiguring Instances and servers within the Policy scope. When setting the Policy, users have the option of using Morpheus Approvals or an Approval Integration such a ServiceNow.
+
+Approve Workflow Execute
+:   If enabled, when Workflows are executed on workloads within the Policy scope, an Approval is generated. This could apply when a Workflow is executed from the Workflows list page or from the detail page for an Instance or server. Approvals can be targeted to HPE Morpheus Enterprise internal Approvals or targeted to a third-party integration (such as ServiceNow). The Workflow will not begin to execute until after the approval is granted.
+
+Backup Creation
+:   Disable or enable the ability to create a backup when provisioning an instance.
+
+Backup Targets
+:   A master account can determine storage provider options for backups with Backup Targets policies.
+
+Budget
+:   Sets a maximum total combined price for all instances in the Group, Cloud, Tenant or owned by the User this policy is applied to.
+
+Cluster Resource Name
+:   The name of Cluster hosts (master and workers) when creating Kubernetes, Docker and KVM Clusters. Pre-populates a fixed or editable Resource Name value for the cluster using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Cypher Access
+:   Granularly set LIST, READ, WRITE, and DELETE access to arbitrary Cypher secret paths scoped globally or to specific Roles and Users. See the section below for a guide to establishing a Cypher access policy.
+
+Delayed Delete
+:   Delayed Delete Policies allow for soft deletion of Instances and Apps. Instead of deleting immediately, Instances and Apps with a Delayed Delete policy applied will be shutdown upon deletion request and hidden by default from the UI. The Instance/App will then be in `Pending Removal` status. In order to see Instances pending deletion on the Instances list page (Provisioning > Instances), you must filter for “Pending Removal” status. These Instances will not show when filtered for “All Statuses”
+
+Expiration
+:   Sets an expiration timeframe in days after which the Instance will be deleted. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration. See HPE Morpheus Enterprise [Knowledge Base](https://support.morpheusdata.com/s/article/How-to-create-an-extensions) for more information about Expiration policies
+
+File Share Storage Quota
+:   Sets a Storage Quota for File Share usage (in GB) to scoped User, Role, Tenant or Global.
+
+Hostname
+:   The `hostname` or `computer name` which is set in the OS and DNS. On some platforms, hostnames are restricted by length, spaces, and/or special characters. Pre-populates a fixed or editable name for hostnames/machine names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings
+
+Instance Name
+:   Pre-populates a fixed or editable name for Instance Names using ${variable} naming patterns and/or text, including ${sequence} numbering. Toggle whether sequence numbers are reusable (after the resource using them is destroyed) by enabling [Reuse Naming Sequence Numbers](https://docs.morpheusdata.com/en/latest/administration/settings/settings.html#provisioning) in Administration > Settings. Note that it’s not recommended administrators include “>”, “<”, “%”, “$”, or “=” in naming policies
+
+Instance Networks
+:   When an Instance is provisioned within the scope of the Policy (Group or Cloud scoping is supported), the network selected on the Policy is automatically set and locked in the provisioning wizard to force provisioning onto the selected network.
+
+Max Containers
+:   Sets the max number of Containers for the Group or Cloud the Policy is added to.
+
+Max Cores
+:   Sets the max number of total of Cores combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Hosts
+:   Sets the max number of total Hosts in the Group or Cloud the Policy is added to.
+
+Max Load Balancer Pools
+:   Sets the max number of load balancer pools within the policy scope
+
+Max Memory
+:   Sets the max number of total of RAM combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Pool Members
+:   Sets the maximum number of members in a load balancer pool
+
+Max Snapshots
+:   Set the maximum number of Snapshots that may be stored for each Instance or VM within the scope. Once the limit is met, HPE Morpheus Enterprise will warn the user when attempting to create more snapshots until the number is reduced
+
+Max Storage
+:   Sets the max number of total of Storage combined for Instances in the Group or Cloud the Policy is added to, includes the option to include or exclude container resources in the Policy.
+
+Max Virtual Servers
+:   Sets the maximum number of virtual servers within the policy scope
+
+Max VMs
+:   Sets the max number of Virtual Machines for the Group or Cloud the Policy is added to.
+
+Message of the Day (MOTD)
+:   Message of the Day”” Policy for displaying Alerts in HPE Morpheus Enterprise. Configurable as a pop-up or full-page notification with Info, Warning and Critical message types.
+
+    NOTE
+
+    Requires role permission: `Admin: Message Of the Day` set to “Full” to create and manage MOTD Policies.
+
+Network Quota
+:   Limits the number of networks that can be created within the policy’s scope
+
+Object Storage Quota
+:   Sets a Storage Quota for Object Storage usage (in GB) to scoped User, Role, Tenant or Global.
+
+Power Scheduling
+:   Adds a Power Schedule for the Instances in a Group or Cloud. Power Schedules can be created in Library > Automation > Power Scheduling
+
+Router Quota
+:   Limits the number of routers that can be created within the policy’s scope
+
+Shutdown
+:   Sets a shutdown timeframe in days upon provision after which the Instance will be stopped. Extensions can be auto-approved or require approval immediately or after x amount of auto-extensions using Morpheus Approvals or an Approval Integration.
+
+Storage Server Storage Quota
+:   Sets a Storage Quota for selected Storage Server (in GB), applied Globally or per specified Tenants.
+
+Tags
+:   Requires the user to add compliant Tags at provision time, this can be enforced on a strict or passive basis
+
+    NOTE
+
+    Tag scanning and enforcement is currently only available for Azure, Amazon, Google, and VMware clouds. For a more comprehensive guide on implementing Tag Policies, see the associated article in our [KnowledgeBase](https://support.morpheusdata.com/s/article/How-to-work-with-cloud-tagging-policies?language=en_US).
+
+User Creation
+:   Controls the “CREATE YOUR USER” flag in the User Config options during provisioning do be always disabled, always enabled, enabled by default, or disabled by default.
+
+User Group Creation
+:   Forces User Creation of members in the selected User Group during Provisioning.
+
+Workflow
+:   Workloads provisioned within the scope of the Policy will have the indicated Workflow applied and the Tasks executed within the proper phase of the Instance lifecycle
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json b/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
new file mode 100644
index 0000000..1e30a37
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+  "title": "NSX Cloud",
+  "ordinal": 512,
+  "parent_title": "Networking Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.html",
+  "topic_cluster": {
+    "clustering_title": "NSX Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF",
+        "clustering_title": "NSX Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md b/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
new file mode 100644
index 0000000..a4f1b53
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E539BB4A-19A8-49AD-9A03-35AF2063ACBF.md
@@ -0,0 +1,31 @@
+# NSX Cloud
+
+NSX Cloud is a networking solution that allows administrators to define networking and security policies for applications running in private and public clouds. When integrated with HPE Morpheus Enterprise, users can apply an NSX Cloud integration with VMware vCenter-type Clouds. This offers robust syncing and manipulation of NSX Cloud constructs as well as the ability to consume those networks when provisioning to VMware Cloud targets.
+
+## Features
+
+- Sync and manage DHCP servers
+- Sync and manage DHCP relays
+- Sync and manage network segments
+- Sync and manage distributed firewall rules
+- Sync and manage tier-1 routers
+- Sync and manage groups, including management groups and compute groups
+- Integration with VMware-type Clouds
+
+## Integrating with VMware Clouds
+
+Integration with a VMware Cloud requires the Cloud integration to be pre-existing. If you need to integrate a VMware Cloud first, refer to the [VMware Cloud integration guide](https://docs.morpheusdata.com/en/latest/integration_guides/Clouds/vmware/vmware.html) in HPE Morpheus Enterprise UI documentation for full details. If you are creating the VMware Cloud now, bear in mind that you will need to update firewall inbound rules to allow the HPE Morpheus Enterprise appliance to connect with VMware. If this step is not done, any attempts to create that Cloud integration will fail. Log into the NSX Cloud web console and click on the Security tab. Within the security tab, go to the Gateway Firewall section and the Management Gateway tab within it. Edit the list of sources for your vCenter inbound rules. The IP address for the HPE Morpheus Enterprise appliance should be among the allowed inbound addresses.
+
+To begin a new NSX Cloud integration, navigate to Infrastructure > Network > Integrations. Click + ADD and then click “NSX Cloud”. Make the following configurations to create the integration with NSX Cloud:
+
+- **NAME:** A friendly name for the NSX Cloud integration in HPE Morpheus Enterprise
+- **VISIBILITY:** This option is only available from the Master Tenant. Select “Public” to make the NSX Cloud integration available to all Tenants. Select “Private” to reserve the integration for the Master Tenant
+- **API HOST:** The API access URL for NSX Cloud. Your API URL will look something like this: <https://nsx-xx-xx-xx-xx.rp.vmwarevmc.com/vmc/reverse-proxy/api/orgs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx/sddcs/xxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxx>
+- **API KEY:** An API token granting sufficient access for HPE Morpheus Enterprise to work with all relevant NSX constructs
+- **CLOUD:** Select the VMware Cloud integration that NSX Cloud should integrate with
+
+Once done, click ADD NETWORK INTEGRATION. After a brief moment, the new integration will be created and will appear alongside other network integrations on the network integration list page. We can verify that NSX Cloud and the VMware Cloud are integrated by editing the VMware Cloud (Infrastructure > Clouds > Selected VMware Cloud > EDITbutton). Expand the Advanced Options panel of the EDIT CLOUD modal and the NSX Cloud integration should be set under the NETWORK MODE configuration.
+
+## Managing NSX Cloud
+
+With the integration complete, you can now examine the detail section for the new integration. From the network integration list page (Infrastructure > Network > Integrations), select the NSX Cloud integration that was just created. From this section, we can create, manage, and delete DHCP servers and relays, network segments, firewall rules, tier-1 routers, and groups.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.json b/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.json
new file mode 100644
index 0000000..798345a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+  "title": "Windows OS Imaging",
+  "ordinal": 412,
+  "parent_title": "Image Catalog",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E55D4270-ED77-4161-8712-45824C891713.html",
+  "topic_cluster": {
+    "clustering_title": "Windows OS Imaging",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E55D4270-ED77-4161-8712-45824C891713",
+        "clustering_title": "Windows OS Imaging"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.md b/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.md
new file mode 100644
index 0000000..c576bd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E55D4270-ED77-4161-8712-45824C891713.md
@@ -0,0 +1,38 @@
+# Windows OS Imaging
+
+This section provides guidance and requirements for deploying **Windows Server on bare metal** using Morpheus Enterprise. It covers required virtual image settings, Windows-specific boot considerations, current licensing limitations, and high-level troubleshooting guidance for failed installations.
+
+The following Windows distributions are supported for deployment:
+
+- Windows Server 2019
+- Windows Server 2022
+- Windows Server 2025
+
+## Virtual Image Configuration
+
+When adding a Windows ISO to the **Morpheus Virtual Images Library**, the following settings **must** be configured:
+
+- Is Cloud Init Enabled: Unchecked
+- Cloud Guest Customization: Checked
+- Sysprepped / Generalized Image: Checked
+- Install Agent: Checked
+- Advanced
+  - VM Tools Installed: Checked
+
+## Windows Install Image Index
+
+By default, Morpheus installs Image Index 2, which typically corresponds to Windows Server Standard (Desktop Experience).
+
+To deploy a different Windows edition:
+
+1. Navigate to Library > Operating Systems.
+2. Add a new Operating System entry with **Platform = Windows**.
+3. Specify the desired Windows Install Index.
+4. Complete the required fields (Vendor, OS Version, Category, OS Name, Codename, OS Family).
+5. Associate the Windows Virtual Image with this Operating System.
+
+You can use the existing Windows Operating System as reference templates.
+
+**Subtopics**  
+
+- **[Boot Prompt Configuration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json b/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
new file mode 100644
index 0000000..2980062
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+  "title": "Tenant Role Permission Sections",
+  "ordinal": 298,
+  "parent_title": "Role Permissions",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.html",
+  "topic_cluster": {
+    "clustering_title": "Tenant Role Permission Sections",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E5C429F5-9F57-481D-968A-64793E86EBCE",
+        "clustering_title": "Tenant Role Permission Sections"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md b/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
new file mode 100644
index 0000000..8bb3768
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E5C429F5-9F57-481D-968A-64793E86EBCE.md
@@ -0,0 +1,34 @@
+# Tenant Role Permission Sections
+
+Features
+:   Controls Tenant access level for sections and features in HPE Morpheus Enterprise. The complete feature permissions grid is included below.
+
+Clouds
+:   Controls Tenant access level for Clouds. This list includes Clouds integrated from the Master Tenant and shared publicly. Tenants given this Tenant Role will have either Full, Read, or None access levels to a given Cloud. See the section below for more information on Cloud Access levels.
+
+Instance Types
+:   Controls Tenant access level for Instance Types. Only Instance Types created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Blueprints
+:   Controls Tenant access level for Blueprints during App provisioning. Only Blueprints created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Report Types
+:   Controls Tenant access for each report type in the Reports section (Operations > Reports). The Tenant must also have Operations: Reports access granted under the Feature permissions tab.
+
+Personas
+:   Controls User access to HPE Morpheus Enterprise Personas, at the time of this writing Users may be given access to the Standard (full HPE Morpheus Enterprise UI experience), API (no GUI access, API-only for service accounts), Virtual Desktop (VDI), or Service Catalog Personas (simplified easy ordering experience)
+
+Catalog Item Types
+:   Controls Tenant access to Catalog Item types within the Service Catalog Persona. Only Catalog Items created in the current Tenant or those created in the Master Tenant and shared with the current Tenant will be available.
+
+Cluster Types
+:   Controls Tenant access to Cluster types. Only Cluster types allowed for the Role may be added in Infrastructure > Clusters within the associated Tenant
+
+VDI Pools
+:   Controls Tenant access to VDI Pools which are currently configured (Tools > VDI Pools) via the Virtual Desktops Persona view
+
+Workflows
+:   Controls Tenant access to Workflows. Only selected Workflows will be shared down to Tenants having the associated Role
+
+Tasks
+:   Controls Tenant access to Tasks. Only selected Tasks will be shared down to Tenants having the associated Role
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json b/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
new file mode 100644
index 0000000..d9b6576
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+  "title": "Provisioning a Workload",
+  "ordinal": 182,
+  "parent_title": "HVM Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning a Workload",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9",
+        "clustering_title": "Provisioning a Workload"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md b/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
new file mode 100644
index 0000000..cefb82a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E5D8BA05-A312-4091-93B4-A1AA9C15E1E9.md
@@ -0,0 +1,15 @@
+# Provisioning a Workload
+
+At this point, the cluster is ready for workloads to be provisioned to it. The system default Ubuntu Instance Type contains a compatible Layout for HVM deployment. Add an Instance from the Instances list page (Provisioning > Instances). After selecting the Instance Type, choose a Group that allows for selection of the HPE Morpheus Enterprise-type Cloud containing the HVM cluster.
+
+![../../_images/groupCloud.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-87BE27BB-2F87-4323-B45A-8A8D0C89DE4B-high.png)
+
+After moving to the next tab, select a Plan based on resource needs. From the **RESOURCE POOL** field, select the desired HVM cluster. When configuring **VOLUMES** for the new workload, note that space can be claimed from the Ceph volume. Within **NETWORKS**, we can add the new workload to one of the **VLANS** set up as part of cluster creation. Finally, note that we can choose the HOST the workload should run on.
+
+TIP
+
+The VOLUMES configuration within the provisioning wizard includes a flyout menu allowing storage type (standard, thin, thick (lazy zero), and thick (eager) and storage profile (cache: none or cache: directsync) configurations to be set on each individual volume.
+
+![../../_images/configureTab.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-36A8D9F5-3920-45A7-A6A6-1803A8897B35-high.png)
+
+Review and complete the provisioning wizard. After a short time, the workload should be up and running. With a workload now running on the cluster, we can take a look at some of the monitoring, migration, failover, and other actions we can take for workloads running on HVM clusters.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json b/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
new file mode 100644
index 0000000..a5d9744
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+  "title": "Roles and Identity Sources",
+  "ordinal": 295,
+  "parent_title": "Roles",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.html",
+  "topic_cluster": {
+    "clustering_title": "Roles and Identity Sources",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2",
+        "clustering_title": "Roles and Identity Sources"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md b/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
new file mode 100644
index 0000000..9ab871a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E6C2AF29-A549-4B96-A778-039FC445D7F2.md
@@ -0,0 +1,3 @@
+# Roles and Identity Sources
+
+It is very common for large Enterprises to have an existing identity source that they would like to plug in to HPE Morpheus Enterprise for authentication. This includes services like LDAP, Active Directory, OKTA, Jump Cloud, One Login, and SAML. When using these services it becomes important to configure a role mapping between the HPE Morpheus Enterprise role assignments to the equivalent identity source groups/roles the user belongs to. This is configurable within the identity source management UI. Sections are provided allowing things like LDAP groups to be directly mapped to specific roles within HPE Morpheus Enterprise. If a user matches more than one LDAP/role group then both sets of roles are applied to the user automatically. Configuring Identity Sources is done in Tenant management or user management in Administration > Tenants or Administration > Users, and has to be configured on a per-tenant basis. Additionally, administrators may opt to lock users to their mapped role in HPE Morpheus Enterprise or keep the roles unlocked to manually administer roles in one-off scenarios.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json b/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
new file mode 100644
index 0000000..00eb1de
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+  "title": "Importing Pre-Provisioned Server",
+  "ordinal": 419,
+  "parent_title": "Compute Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.html",
+  "topic_cluster": {
+    "clustering_title": "Importing Pre-Provisioned Server",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27",
+        "clustering_title": "Importing Pre-Provisioned Server"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md b/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
new file mode 100644
index 0000000..9bfdd2b
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E748BC6D-7E45-4324-A174-9FB2012CBA27.md
@@ -0,0 +1,13 @@
+# Importing Pre-Provisioned Server
+
+Importing a Pre-Provisioned server enables administrators to bring existing physical servers and associated resources (networks and storage) into HPE Morpheus. This is the initial step in migrating an existing workload cluster into Morpheus management. It is completed in two phases:
+
+- **Import**: Import existing servers as Pre-Provisioned resources.
+- **Convert to Managed**: Convert imported servers into managed instances, creating Morpheus instances with associated network and storage attachments.
+
+This process is performed one workload cluster at a time, and each cluster can contain one or more servers. Once the initial server is converted, additional imported servers can be added to the same instance using the Add Node operation.
+
+**Subtopics**  
+
+- **[Import Pre-Provisioned Servers](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-7BE0E73F-EC0B-4C8F-8782-273C813A305E.html)**
+- **[Add Additional Nodes to the Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json b/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
new file mode 100644
index 0000000..08103c6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+  "title": "Deleting Volume",
+  "ordinal": 444,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E7DD5576-68E3-449D-8606-D2861BF53808.html",
+  "topic_cluster": {
+    "clustering_title": "Deleting Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E7DD5576-68E3-449D-8606-D2861BF53808",
+        "clustering_title": "Deleting Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md b/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
new file mode 100644
index 0000000..a4d5377
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E7DD5576-68E3-449D-8606-D2861BF53808.md
@@ -0,0 +1,12 @@
+# Deleting Volume
+
+## About this task
+
+This procedure allows the users to delete a volume. A volume can be deleted only after it is detached from all the servers.
+
+## Procedure
+
+1. Navigate to Infrastructure > Storage > Volumes.
+2. Click the Actions pulldown on the right and select Delete for the volume to be deleted.
+3. Click the Delete on the confirmation screen.   
+   ![Delete Volume](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4385EF29-CF09-4386-B7D5-20D68EC1B8F9-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json b/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
new file mode 100644
index 0000000..a6a3303
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+  "title": "Bare Metal",
+  "ordinal": 215,
+  "parent_title": "Compute",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E816369D-52FD-43B2-88F6-A5F748829203.html",
+  "topic_cluster": {
+    "clustering_title": "Bare Metal",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E816369D-52FD-43B2-88F6-A5F748829203",
+        "clustering_title": "Bare Metal"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md b/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
new file mode 100644
index 0000000..6fe1824
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E816369D-52FD-43B2-88F6-A5F748829203.md
@@ -0,0 +1,10 @@
+# Bare Metal
+
+![../../_images/infra_compute_header_bm_5.3.1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-26D91B4A-96E5-45CF-AC5E-4234F1F3AA28-high.png)
+
+## Section Features & Filters Record Search Custom Views CSV Export JSON Export Paging Config
+
+- Standard Filters: OS Type
+- Advanced Filters: Status Managed Server Type
+
+Bare Metal hosts are from discovered, PXE Boot or manually added Bare Metal hosts. Bare Metal hosts that are also Hypervisors will be listed in the Hosts section.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json b/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
new file mode 100644
index 0000000..b29ea9e
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+  "title": "Networks Configuration",
+  "ordinal": 433,
+  "parent_title": "Network Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.html",
+  "topic_cluster": {
+    "clustering_title": "Networks Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F",
+        "clustering_title": "Networks Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md b/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
new file mode 100644
index 0000000..899aee9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E82A94D5-16DB-4BFB-8DF3-59E49210F93F.md
@@ -0,0 +1,16 @@
+# Networks Configuration
+
+Once the network integration is created, networks can be created using the specific network integration that was created. Networks essentially define the VLAN that they represent along with other attributes such as the subnet’s IPv4 prefix, IP address allocation method, gateway address, DNS, etc. The screenshot below shows those details.
+
+The VLAN Trunks specifies the trunk VLANs to be added when this network is consumed by an instance. The VLAN ID field represents the primary VLAN for this network. This VLAN is configured as the untagged VLAN when this network is consumed by an instance.
+
+The Network Service corresponds to the network integration that was created. This specifies that the network is to be created in the infrastructure (switches) specified in the network integration selected.
+
+The Private checkbox specifies that the network is a private network. By default, all networks are public. If private is selected, the primary VLAN in this network is not configured on the uplink connection. This would render them unreachable from outside of the cloud infrastructure. This is typically used for workload networks that are used to communicate between only the workload servers and other infrastructure within the private cloud.
+
+The configuration of a network will result in the primary VLAN in that network being provisioned on the network switches. The server ports are configured when those networks are consumed during the provisioning of a compute instance.
+
+**Subtopics**  
+
+- **[Creating Network Using the ArubaCX Integration](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-421A3218-7033-4066-AF8E-AA2D46D4385C.html)**
+- **[Network Usage](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-DDF369BF-6EA3-416F-A575-01E5C954A3FD.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json b/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
new file mode 100644
index 0000000..e8a1da5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+  "title": "Add FortiADC load balancer",
+  "ordinal": 500,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.html",
+  "topic_cluster": {
+    "clustering_title": "Add FortiADC load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33",
+        "clustering_title": "Add FortiADC load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md b/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
new file mode 100644
index 0000000..13dc6a7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-E97DD1D7-4888-4CC2-B69E-7F05FA18ED33.md
@@ -0,0 +1,48 @@
+# Add FortiADC load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  load balancers.
+2. Click + ADD.
+3. From the drop-down list, select **FortiADC**.
+
+   The NEW LOAD BALANCER panel opens.  
+   ![FortiADC lb](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-70A960BC-376C-493B-A101-3E02EB65C9C2-high.png)
+4. Configure the following parameters: 
+
+   GROUP \*
+   :   From the drop-down list, select the group for the load balancer.
+
+   CLOUD \*
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME \*
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Identifying information displayed on the load balancer list page.
+
+   API URL \*
+   :   Enter the URL of the FortiADC API.
+   :   For example, <http://10.30.21.55>.
+
+   API PORT \*
+   :   Enter the FortiADC API port.
+   :   For example, 80
+
+   CREDENTIALS
+   :   **USERNAME \***: Enter FortiADC service account username.
+   :   **PASSWORD \***: Enter FortiADC service account password.
+
+   VIRTUAL NAME
+   :   Enter the naming pattern for new FortiADC Virtual Servers.
+   :   If blank, defaults to `morph_lb_${loadBalancer.id}`.
+
+   SERVICE NAME
+   :   Enter the naming pattern for new FortiADC Services.
+   :   If blank, defaults to `morph_service_${container.id}`.
+
+   SERVER NAME
+   :   Enter the naming pattern for new FortiADC Servers.
+   :   If blank, defaults to `morph_server_${server.id}`.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json b/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
new file mode 100644
index 0000000..1530697
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+  "title": "Add Additional Nodes to the Instance",
+  "ordinal": 422,
+  "parent_title": "Importing Pre-Provisioned Server",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.html",
+  "topic_cluster": {
+    "clustering_title": "Add Additional Nodes to the Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D",
+        "clustering_title": "Add Additional Nodes to the Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md b/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
new file mode 100644
index 0000000..9f1d501
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EA88091A-ECBB-4C0A-A6F8-E0C4300C4B6D.md
@@ -0,0 +1,20 @@
+# Add Additional Nodes to the Instance
+
+## About this task
+
+To convert a Pre-Provisioned server into a fully provisioned node, and to make it part of an existing instance, the Add Node action is used, from the context of the Instance to which it is desired to be added.
+
+Once an instance is created with the first converted node, you can add other imported servers to the same instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.
+2. Select the newly created instance.
+3. Click Add Node. ![Add node action](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-E34393DB-6064-4C8B-B3CA-6AC91E7546D5-high.png)
+4. Select Pre-Provisioned.
+5. Choose the imported server and provide the required details.
+6. Click Execute. ![Execute Action](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CCCDD2C8-A5AF-4EBD-9902-85ACA1A99155-high.png)
+
+## Results
+
+This converts the selected imported server into a managed node and adds it to the existing instance.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json b/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
new file mode 100644
index 0000000..4cbd91d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+  "title": "User Guides",
+  "ordinal": 360,
+  "parent_title": "Guides",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.html",
+  "topic_cluster": {
+    "clustering_title": "User Guides",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24",
+        "clustering_title": "User Guides"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md b/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
new file mode 100644
index 0000000..c8d8e71
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EBA68020-47A6-4B8C-B5C9-1BEB7BE15F24.md
@@ -0,0 +1,18 @@
+# User Guides
+
+**Subtopics**  
+
+- **[Getting started with Morpheus and AWS](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-8F33C60A-34CF-47F2-B9D2-526D1E94B821.html)**
+- **[Getting started with HPE Morpheus Enterprise and VMware](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C20033B6-4C42-4BEC-84C0-D313859D9126.html)**
+- **[Getting started with HPE Morpheus Enterprise and Azure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5D6FB58B-B3A0-43A2-9B9B-B1809EC58EAC.html)**
+- **[Automated Single-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CD9193A8-3BB1-4FD2-80AF-1EDFDE19786A.html)**
+- **[Automated Multi-Node Application Deployment with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-3CA69B8E-D437-40EC-9755-668930BA21F4.html)**
+- **[Adding Functionality Through Operational Workflows](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-CEF3A7CD-6CAC-4C34-AC29-68CAD0BD54DB.html)**
+- **[Creating XaaS Instance Types with HPE Morpheus Enterprise](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-2D22E37B-3698-46F3-88BB-A36D96C849EF.html)**
+- **[Morpheus Virtual Desktops](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-17E0EBC8-A495-4198-82BD-63D9D38D6F74.html)**
+- **[Getting Started with Terraform Instance Types](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-E01FA212-4E9E-4403-9508-E4BB971643A3.html)**
+- **[Backing Up and Restoring HPE Morpheus Enterprise Appliance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-1E710344-0932-4A51-B605-18AEF716E46F.html)**
+- **[Cloud Resource Tagging with Morpheus](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-20D6853D-60F1-45A8-90F5-47E242D57DB4.html)**
+- **[Cypher Policies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-0060B753-B50F-4F2A-A500-BABB38426A84_2.html)**
+- **[Configuring Access with Clouds, Groups, and Roles](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C873C84A-4AC6-4CD5-A935-7FF3D4CC53AC.html)**
+- **[Tenancy](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-96AE2ACD-5292-4498-9268-CEB1DAF75BD4.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json b/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
new file mode 100644
index 0000000..49959e6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+  "title": "Add Azure load balancer",
+  "ordinal": 494,
+  "parent_title": "Load Balancers",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.html",
+  "topic_cluster": {
+    "clustering_title": "Add Azure load balancer",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26",
+        "clustering_title": "Add Azure load balancer"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md b/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
new file mode 100644
index 0000000..367c153
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EBE2FE5D-207A-4BDB-BA04-BDDD76873A26.md
@@ -0,0 +1,27 @@
+# Add Azure load balancer
+
+## Procedure
+
+1. Navigate to Infrastructure  >  Load Balancers.
+2. Click + ADD.
+3. From the drop-down list, select **Azure Load Balancer**. 
+
+   The NEW LOAD BALANCER panel opens.  
+   ![Azure LB](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C6A8AF5C-33DF-49FE-9EEA-C205AE35F54B-high.png)
+4. Configure the following parameters: 
+
+   CLOUD
+   :   From the drop-down list, select the cloud that hosts the load balancer.
+
+   NAME
+   :   Enter the load balancer name.
+
+   DESCRIPTION
+   :   Brief description about the load balancer.
+
+   VISIBILITY
+   :   Define Multi-Tenant permissions.
+
+   RESOURCE GROUP
+   :   Select the Resource Group for the load balancer.
+5. Click **SAVE CHANGES**.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json b/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
new file mode 100644
index 0000000..b7532ad
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+  "title": "Delete SSL Certificate",
+  "ordinal": 244,
+  "parent_title": "Trust",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.html",
+  "topic_cluster": {
+    "clustering_title": "Delete SSL Certificate",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598",
+        "clustering_title": "Delete SSL Certificate"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md b/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
new file mode 100644
index 0000000..be44533
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EC0EF4C4-603D-4D7E-9E95-A9B8447C5598.md
@@ -0,0 +1,11 @@
+# Delete SSL Certificate
+
+## About this task
+
+To Delete SSL Certificate:
+
+## Procedure
+
+1. Navigate to Infrastructure > Keys& Certs
+2. On the SSL Certificates tab, select the trash can icon at the end of any row
+3. Acknowledge that you wish to delete the selected SSL Certificate
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json b/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
new file mode 100644
index 0000000..e4bf164
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+  "title": "Clouds",
+  "ordinal": 169,
+  "parent_title": "Infrastructure",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.html",
+  "topic_cluster": {
+    "clustering_title": "Clouds",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EC91E230-8323-4710-9A47-D57A15BE71AA",
+        "clustering_title": "Clouds"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md b/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
new file mode 100644
index 0000000..bc04c10
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EC91E230-8323-4710-9A47-D57A15BE71AA.md
@@ -0,0 +1,191 @@
+# Clouds
+
+## Overview
+
+Clouds are integrations or connections to public, private, hybrid clouds, or bare metal servers. Clouds can belong to many groups and contain many hosts. The clouds view includes clouds status, statistics, tenant assignment, and provides the option to add, edit, delete new clouds. HPE Morpheus Enterprise supports most Public Clouds and Private Clouds.
+
+### Supported Cloud Types
+
+- Alibaba Cloud
+- Amazon
+- Azure (Public)
+- Azure Stack (Private)
+- Canonical MaaS
+- Cloud Foundry
+- Dell (Cloud type for PXE and manually added Dell EMC Hosts)
+- DigitalOcean
+- Google Cloud
+- HPE (Cloud type for PXE and manually added HPE Hosts)
+- Huawei
+- Hyper-V
+- IBM Cloud
+- IBM Cloud Platform
+- Kubernetes
+- MacStadium
+- Morpheus (Generic Cloud type for PXE/Bare Metal and manually added Hosts)
+- Nutanix
+- Open Telekom Cloud
+- OpenStack
+- Oracle Public Cloud
+- Oracle VM
+- Platform 9
+- SCVMM
+- Supermicro (Cloud type for PXE and manually added Supermicro Hosts)
+- UCS
+- UpCloud
+- vCloud Air (OVH)
+- VMWare ESXi
+- VMware Fusion
+- VMWare on AWS
+- VMware vCenter
+- VMware vCloud Director
+- XenServer
+
+Information on each cloud type can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Creating Clouds
+
+Clouds can be added from Infrastructure  >  Clouds or in Infrastructure  >  Groups  >  (select Group)  >  Clouds. Individual Guides for adding specific Cloud Types can be found in the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) section.
+
+## Cloud Detail View
+
+The Cloud Detail view shows metrics on health, sync status, current month costs, average monthly costs, resource utilization statistics, and resource counts for Container Hosts, Hypervisors, Bare Metal, Virtual Machines, and Unmanaged resources.
+
+![../../_images/clouddetailview1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-79A36EB1-C3D0-4D23-9067-DD12ABD6EDB7-high.png)
+
+To view the Cloud List View, select the name of a Cloud to display the clouds Detail View.
+
+EDIT
+:   Edit the setup configuration of the Cloud.
+
+REFRESH
+:   Force a sync with the Cloud. Depending on the Cloud, choose to force a standard Cloud sync (occurs every five minutes by default) or a nightly sync. When syncing Costing data, HPE Morpheus Enterprise will force a pull of costing data for your specified period. If opting to “rebuild” the costing data, HPE Morpheus Enterprise will delete all costing data from the Cloud for that period and attempt to rebuild the data by calling the Cloud API.
+
+DELETE
+:   Delete the Cloud from HPE Morpheus Enterprise
+
+IMPORTANT
+
+All Instances and managed Hosts and VM’s associated with the Cloud must be removed prior to deleting a cloud.
+
+### Cloud Detail Tabs
+
+NOTE
+
+Not all tabs are available for all Cloud Types.
+
+Clusters
+:   The Clusters tab displays clusters provisioned into the Cloud being viewed, including their status, type, name, layout, workers, and compute, memory, and storage stats. You can add a cluster by clicking ADD CLUSTER.
+
+Hosts
+:   The Hosts tab displays available hosts in the Cloud and displays power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status. You can add a resource by clicking ADD RESOURCE, add a hypervisor host by clicking ADD HYPERVISOR, or perform action an action by selecting one or more Hosts and clicking ACTIONS.
+
+    VMs
+    :   Displays an inventory of existing Instances in your Cloud configuration and provides details such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Bare Metal
+:   Setup PXE Boot in the Boot section to add bare metal servers. Once set up you can view information such as power, OS, name, type, cloud, IP address, nodes, disk space, memory, and status.
+
+Security Groups
+:   The Security Groups tab displays a list of existing security groups in the cloud. You can add a security group to this cloud by clicking EDIT SECURITY GROUPS.
+
+Load Balancers
+:   The load balancers tab panel displays available load balancers in the cloud including the name, description, type, cloud and host. You can add a load balancer from this tab by clicking ADD LOAD BALANCER.
+
+Networks
+:   Displays Networks synced or added to the Cloud, including their name, type, CIDR, pool, DHCP status, visibility and targeted Tenant.
+
+Data Stores
+:   Displays Datastores synced or added to the Cloud, including their name, type, capacity, online status, visibility, and targeted Tenant.
+
+Resources
+:   Displays Resource Pools synced from the Cloud, including their name, description, and targeted Tenant.
+
+Policies
+:   Manages Policies enforced on the Cloud. Setting a policy on this tab is equal to creating a policy in Administration > Policies and scoping it to the selected Cloud.
+
+Profiles
+:   Manages Terraform, Key/Value Profiles that create custom object associated secrets and metadata that will automatically be mapped per Cloud selection during provisioning and automation.
+
+## Deleting Clouds
+
+### About this task
+
+To delete a cloud:
+
+### Procedure
+
+1. Select the Infrastructure link in the navigation bar.
+2. Select the Clouds link in the sub navigation bar.
+3. Click the Delete icon of the cloud to delete.
+
+### Results
+
+IMPORTANT
+
+All Instances, managed Hosts and VMs must be removed prior to deleting a Cloud. To remove Instances, hosts and VMs from HPE Morpheus Enterprise without deleting the Cloud resources they represent, select Delete on the host or VM, unselect “Remove Infrastructure”, and select “Remove Associated Instances” if Instance are associated with the selected Hosts or VMs.
+
+## Cloud Profiles
+
+### Role Permissions
+
+Access to **Profiles** tab is determined by the following role permissions:
+
+Role: Feature Access: `Admin: Profiles`
+:   - None: Cannot access Profiles tab or create/view/edit/delete profiles
+    - Read: Can access Profiles tab, can view profiles, cannot create/edit/delete profiles
+    - Full: Can access Profiles tab, can create/view/edit/delete profiles
+
+### Terraform Profiles
+
+- Terraform Profiles allow creation of Cloud-associated tfvars secrets, allowing tf apps and specs to be provisioned across multiple clouds that required different tfvars.
+- Target Cloud Terraform Profiles are automatically mapped to tf apps/specs during provisioning, no manual scoping is required.
+- Terraform Profiles are encrypted in Cypher and creating a profile creates a Cypher entry with key tfvars/profile/cloud/$cloudCode/variables`
+- Terraform Profiles can be edited after creation
+- Terraform Profiles are limited to one per Cloud, once one is created for the Cloud the option to create a Terraform Profile is no longer present. Edit the existing Terraform Profile to make changes at that point
+
+IMPORTANT
+
+Since HPE Morpheus Enterprise mounts Terraform Profiles in Cypher using a mount point which contains the Cloud code value, any Clouds which have the same code will share a Terraform Profile. Create or edit Clouds to have a unique code value if they should have a unique Terraform Profile. It’s also important to understand that HPE Morpheus Enterprise does not require Clouds have a code at creation time. When Clouds are created without a code, HPE Morpheus Enterprise applies a generic non-unique code based on the Cloud type (“amazon” for AWS Clouds, as an example). This sets up a potential situation where all Clouds of the same type have the same generic Cloud code and thus share a Terraform Profile. To avoid this situation, enter a Cloud code value at creation time or edit existing Clouds to have a unique code.
+
+#### Create a Terraform Profile
+
+##### Procedure
+
+1. Navigate to Infrastructure > Clouds and select a Cloud
+2. Select the “Profiles” tab
+3. Select + ADD PROFILE
+4. Select Terraform Profile Type
+5. Enter tfvars in the Terraform Profile Variables field 
+
+   - example Terraform Profile Variables
+
+     ```
+     ```
+     access_key="****acccessKey****"  
+     secret_key="********secretKey**********"  
+     region="us-west-1"
+     ```
+     ```
+6. Select SAVE CHANGES
+
+##### Results
+
+Now, when provisioning a Terraform Instance or App to the Cloud the profile was created in, the tfvars in the profile become available to Terraform. It is not necessary to manually tie this tfvars files to your App Blueprint, these tfvars will automatically be available to Terraform whenever you provision an App to this cloud.
+
+### Key/Value Store Profiles
+
+- Key/Value Profiles (Key/Value Store) expand provisioning, automation, billing and reporting capabilities by allowing dynamic custom object specific metadata in provisioning and automation mappings
+- Key/Value Profile entries are available using `<%=cloud.profile.key%>`
+- Terraform Profiles are limited to one Profile per Cloud, however multiple key/value pairs can be added to a single profile
+
+#### Create a Key/Value Profile
+
+##### Procedure
+
+1. Navigate to `/infrastructure/clouds/` and select a Cloud
+2. Select the `Profiles` tab
+3. Select + ADD PROFILE
+4. Select Key/Value Profile Type
+5. Enter key/value entries, selecting + to add additional entries
+6. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json b/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
new file mode 100644
index 0000000..c4667f2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+  "title": "Preferences",
+  "ordinal": 336,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.html",
+  "topic_cluster": {
+    "clustering_title": "Preferences",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8",
+        "clustering_title": "Preferences"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md b/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
new file mode 100644
index 0000000..8715b0c
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ECF59AB8-EBD6-4006-BFDA-62AB73ECEFF8.md
@@ -0,0 +1,8 @@
+# Preferences
+
+- **Default Group:** Sets the default Group selection when provisioning
+- **Default Cloud:** Sets the default Cloud selection when provisioning
+- **Default Persona:** Sets the default Persona used when logging in
+- **Default Locale:** Sets the user’s preferred language and region, this setting will override the global locale for the individual user
+
+![../../_images/user_settings_preferences_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1FDED76C-74B0-4FCA-A922-28AD152EC59A-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json b/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
new file mode 100644
index 0000000..87e86a8
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+  "title": "OpenSearch Configuration",
+  "ordinal": 11,
+  "parent_title": "Requirements",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.html",
+  "topic_cluster": {
+    "clustering_title": "OpenSearch Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C",
+        "clustering_title": "OpenSearch Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md b/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
new file mode 100644
index 0000000..85b9cba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ECFD4939-8F53-44BB-B8D7-094E28DFAB7C.md
@@ -0,0 +1,423 @@
+# OpenSearch Configuration
+
+Starting with HPE Morpheus Enterprise Software 8.1.0, the embedded search service changes from Elasticsearch to OpenSearch. All HPE Morpheus VM Essentials Software versions already use OpenSearch — this change only affects HPE Morpheus Enterprise appliance upgrades. Hewlett Packard Enterprise continues to support both Elasticsearch and OpenSearch for external clusters.
+
+During upgrade, the reconfigure process will:
+
+- Automatically disable the old Elasticsearch service
+- Start OpenSearch in its place
+- Migrate the Elasticsearch PKCS12 CA to PEM format if `secure_mode` is enabled
+
+No changes to /etc/morpheus/morpheus.rb are required. Existing `elasticsearch[...]` settings are bridged to the `opensearch` namespace automatically (see Notes for details on key precedence).
+
+Data (indices) must be migrated separately using `morpheus-ctl migrate-elasticsearch` (see upgrade sections below, or run `morpheus-ctl migrate-elasticsearch help` on an appliance after upgrade for more info).
+
+## What the settings control
+
+| Setting | opensearch.yml | Purpose |
+| --- | --- | --- |
+| `enable` | — | Enable/disable the embedded OpenSearch service. Set to `false` when using an external cluster. Default `true`. |
+| `es_hosts` | `cluster.initial_master_nodes`, `discovery.seed_hosts` | Cluster membership and discovery. For external clusters, lists the external hosts. |
+| `node_name` | `node.name` | Unique name for this node within the cluster. |
+| `host` | `network.host` or `network.bind_host` | Interface to bind to. Default `127.0.0.1`. Set to `0.0.0.0` for cluster use. |
+| `publish_ip` | `network.publish_host` | The IP other nodes use to reach this node. Falls back to Ohai's `node['ipaddress']` if not set. |
+| `secure_mode` | `plugins.security.disabled: false`, TLS config | Enables TLS on HTTP and transport layers, generates certs, runs securityadmin.sh. |
+| `cluster` | `cluster.name` | Cluster name. Defaults to `morpheus`. Must be the same on all nodes. |
+| `use_tls` | — | Connect to OpenSearch over HTTPS. Automatically set to `true` when `secure_mode` is enabled on the embedded service. Set manually for external TLS clusters. |
+| `auth_user` | — | Username for Morpheus to authenticate with OpenSearch. Used for external clusters. When nil and `secure_mode` is enabled, the auto-created `morpheus` internal user is used. |
+| `auth_password` | — | Password for `auth_user`. Used for external clusters. |
+| `replica_count` | `numberOfReplicas` | Number of index replicas. Default `1`. Set to `0` for single-node deployments. |
+| `admin_dn` | `plugins.security.authcz.admin_dn` | Distinguished name for the admin certificate. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+| `nodes_dn` | `plugins.security.nodes_dn` | Distinguished name for trusted node certificates. Defaults to `O=Morpheus,OU=Ops,CN=<node_name>`. |
+
+## Ports
+
+For embedded clusters, ensure the following ports are open between all cluster nodes:
+
+- **9200** — HTTP (client queries)
+- **9300** — Transport (inter-node communication and cluster formation)
+
+## Notes
+
+- You can use either `elasticsearch[...]` or `opensearch[...]` keys in morpheus.rb. The `elasticsearch` keys are bridged to `opensearch` automatically. If the same key is set under both namespaces, the `opensearch[...]` value takes precedence.
+- The reconfigure strips `127.0.0.1` from `es_hosts` when more than one host is present, so you don't need to exclude it.
+- In secure mode, `admin_dn` and `nodes_dn` default to `O=Morpheus,OU=Ops,CN=<node_name>` and are set automatically per node. These only need to be overridden when using custom certificates (see below).
+
+## Custom certificates (admin\_dn and nodes\_dn)
+
+When using your own certificates instead of the auto-generated ones, set `admin_dn` and `nodes_dn` to match the subject DN of your certificates. These values map to `plugins.security.authcz.admin_dn` and `plugins.security.nodes_dn` in opensearch.yml.
+
+- `admin_dn` — Identifies the certificate authorized to run administrative operations (e.g., `securityadmin.sh`). Only requests signed by a certificate matching this DN can modify the security index.
+- `nodes_dn` — Identifies certificates trusted for inter-node transport communication. Nodes will reject transport connections from certificates that don't match.
+
+To extract the subject DN from an existing certificate:
+
+```
+```
+openssl x509 -in /path/to/cert.pem -noout -subject -nameopt RFC2253
+```
+```
+
+Set the values in /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['admin_dn'] = 'CN=admin,OU=MyTeam,O=MyOrg'  
+opensearch['nodes_dn'] = 'CN=node,OU=MyTeam,O=MyOrg'
+```
+```
+
+If the admin and node certificates share the same DN (common when a single wildcard or shared cert is used), both values can be set to the same string. With the default auto-generated certificates, these are set to `O=Morpheus,OU=Ops,CN=<node_name>` per node and do not need to be configured manually.
+
+## Setting the HPE Morpheus Enterprise user password
+
+When `secure_mode` is enabled, reconfigure creates an internal OpenSearch user named `morpheus` that HPE Morpheus Enterprise uses to authenticate with OpenSearch. The password for this user is auto-generated and stored in /etc/morpheus/morpheus-secrets.json under the `elasticsearch.morpheus_password` key. No manual configuration is needed in the default case.
+
+To set a custom password, add it to /etc/morpheus/morpheus.rb on each node:
+
+```
+```
+opensearch['morpheus_password'] = 'my-custom-password'
+```
+```
+
+## Encrypting the password
+
+Passwords in morpheus.rb can be stored in encrypted form using the `ENC{...}` wrapper. During reconfigure, the recipe detects the `ENC` prefix and decrypts the value automatically. Plaintext values are used as-is.
+
+To generate an encrypted string:
+
+```
+```
+morpheus-ctl get-crypto-string string 'my-custom-password'
+```
+```
+
+This outputs an encrypted value that can be used in morpheus.rb:
+
+```
+```
+opensearch['morpheus_password'] = 'ENC{aBcDeFgHiJkLmNoPqRsTuVwXyZ...}'
+```
+```
+
+The encryption uses the appliance's `encryption_key_suffix` (from /etc/morpheus/morpheus-secrets.json), so the encrypted value is specific to that appliance. All nodes in the cluster share the same secrets file contents, so the same encrypted string works on all nodes.
+
+Any password setting in morpheus.rb supports this format (under either the `opensearch[...]` or `elasticsearch[...]` namespace), including `morpheus_password` and `auth_password`. As with other settings, `opensearch[...]` takes precedence over `elasticsearch[...]` if both are set.
+
+## Single Node
+
+A single-node setup uses the embedded OpenSearch service with default settings. No morpheus.rb changes are required unless enabling secure mode.
+
+## Single Node — Fresh Install
+
+The embedded OpenSearch service starts automatically after the initial reconfigure. No configuration is needed:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+To enable secure mode, add to /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['secure_mode'] = true
+```
+```
+
+## Single Node — Upgrading from Elasticsearch
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new HPE Morpheus Enterprise package. Do **NOT** run reconfigure yet.
+
+**Step 2 — Run the migration script**
+
+For single-node Morpheus appliances, the migration script handles everything automatically. Run `sudo morpheus-ctl migrate-elasticsearch`. This script does the following:
+
+1. Start a temporary Elasticsearch instance using the preserved ES installation
+2. Reset voting configuration if needed (for nodes which were previously part of a cluster)
+3. Set replicas to 0 for single-node operation
+4. Export all indices to JSON files
+5. Import into OpenSearch
+6. Stop the temporary ES cluster
+
+**Step 3 — Reconfigure**
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The old Elasticsearch service is disabled automatically (if necessary) and OpenSearch starts in its place. If `secure_mode` was enabled, the Elasticsearch PKCS12 CA is automatically migrated to PEM format.
+
+## 3-Node Embedded Cluster
+
+## 3-Node Embedded Cluster — Prerequisites
+
+**Networking**
+
+- All 3 nodes must be able to reach each other on:
+
+  - **Port 9200 (TCP)** — HTTP API (client queries, health checks)
+  - **Port 9300 (TCP)** — Transport (inter-node communication, cluster formation, shard replication)
+- Each node needs a stable, routable IP address or resolvable hostname that the other nodes can reach (no NAT between nodes)
+- Both IP addresses and hostnames are supported in `es_hosts` and `publish_ip`
+
+**Configuration**
+
+- Each node must have:
+
+  - The same `es_hosts` hash listing all 3 nodes
+  - A unique `node_name`
+  - A unique `publish_ip` matching that node's routable IP
+  - `host` set to `0.0.0.0` (default `127.0.0.1` only listens locally and will not allow cluster formation)
+- All nodes must share the same `cluster` name (defaults to `morpheus` — only set this if you need to change it)
+
+**Secure Mode**
+
+- When `secure_mode` is enabled, TLS is used on both HTTP and transport layers
+- All nodes must share the **same root CA** — Node 1 must be reconfigured first to generate the CA, then the CA files are copied to the remaining nodes before their first reconfigure
+- Each node auto-generates its own node certificate signed by the shared CA
+
+**Example nodes:**
+
+- Node 1: `10.0.0.1` (morpheus-1)
+- Node 2: `10.0.0.2` (morpheus-2)
+- Node 3: `10.0.0.3` (morpheus-3)
+
+## Fresh Install — Without Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+**Node 1** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'
+```
+```
+
+**Node 2** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'
+```
+```
+
+**Node 3** — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'
+```
+```
+
+**Apply**
+
+Run on all three nodes:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Nodes can be reconfigured in any order. The cluster will form once all nodes are up and can reach each other on ports 9200 and 9300.
+
+## Fresh Install — With Secure Mode
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Secure mode enables TLS on both the HTTP and transport layers. Each node generates its own node certificate, but all nodes must share the **same root CA** so they trust each other.
+
+**Step 1 — Configure and reconfigure Node 1 first**
+
+Node 1 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-1'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.1'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Node 1:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+This generates the root CA and node certificate at:
+
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem
+- /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem
+
+**Step 2 — Copy the root CA to Nodes 2 and 3**
+
+Copy both CA files from Node 1 to the same path on Nodes 2 and 3 **before** running reconfigure on them:
+
+```
+```
+# From Node 1:  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node2:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca.pem     node3:/opt/morpheus/embedded/opensearch-2.18.0/config/  
+scp /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca-key.pem  node3:/opt/morpheus/embedded/opensearch-2.18.0/config/
+```
+```
+
+Set ownership on Nodes 2 and 3:
+
+```
+```
+chown morpheus-es:morpheus-es /opt/morpheus/embedded/opensearch-2.18.0/config/root-ca*.pem
+```
+```
+
+**Step 3 — Configure and reconfigure Nodes 2 and 3**
+
+Node 2 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-2'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.2'  
+opensearch['secure_mode'] = true
+```
+```
+
+Node 3 — /etc/morpheus/morpheus.rb:
+
+```
+```
+opensearch['es_hosts'] = {'10.0.0.1' => 9200, '10.0.0.2' => 9200, '10.0.0.3' => 9200}  
+opensearch['node_name'] = 'morpheus-3'  
+opensearch['host'] = '0.0.0.0'  
+opensearch['publish_ip'] = '10.0.0.3'  
+opensearch['secure_mode'] = true
+```
+```
+
+Run reconfigure on Nodes 2 and 3:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+Each node will skip CA generation (the files already exist) and generate its own node certificate signed by the shared CA.
+
+## Upgrading from a 3-Node Elasticsearch Cluster
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on all 3 nodes. Do **not** run reconfigure yet. The preinstall script preserves the Elasticsearch installation at `/var/opt/morpheus/elasticsearch-8.15.5/home/`. The ES data and binaries are preserved across package install, reconfigure, and normal operation, thus, the migration export can be run at any time until the ES data and binaries are removed with the export cleanup option (or manually removed).
+
+**Step 2 — Check the ES cluster configuration**
+
+Run `cat /var/opt/morpheus/elasticsearch-8.15.5/home/config/elasticsearch.yml` and note the `discovery.seed_hosts` and `cluster.initial_master_nodes`. These are the cluster nodes.
+
+**Step 3 — Start Elasticsearch on all nodes**
+
+Start ES on each node within 30 seconds of each other. The order does not matter, they will discover each other. Run `su -s /bin/bash es-morpheus -c 'ES_JAVA_HOME=/var/opt/morpheus/elasticsearch-8.15.5/home/jdk /var/opt/morpheus/elasticsearch-8.15.5/home/bin/elasticsearch -d'`.
+
+**Step 4 — Verify cluster health**
+
+From any node, run `curl hrrp://127.0.0.1:9200/_cluster/health?pretty`. You should see: `"status": "green" - "number_of_nodes": 3 - "unassigned_shards": 0`
+
+**Step 5 — Run the migration export**
+
+From any node, run `sudo morpheus-ctl migrate-elasticsearch`. The script will detect the running ES cluster and export from it.
+
+**Step 6 — Stop elasticsearch on all nodes**
+
+After the migration completes, on each node, run `pkill -f 'elasticsearch-8.15.5'`
+
+## External Cluster
+
+When using an externally managed OpenSearch (or Elasticsearch) cluster, disable the embedded service and point Morpheus at the external hosts.
+
+## External Cluster — Fresh Install
+
+NOTE
+
+`elasticsearch[...]` keys can also be used in place of `opensearch[...]` on fresh installs. They are bridged automatically.
+
+Add the following to /etc/morpheus/morpheus.rb on each Morpheus appliance node:
+
+```
+```
+opensearch['enable'] = false  
+opensearch['es_hosts'] = {'os-node1.example.com' => 9200, 'os-node2.example.com' => 9200, 'os-node3.example.com' => 9200}  
+opensearch['auth_user'] = 'morpheus'  
+opensearch['auth_password'] = 'the-external-cluster-password'
+```
+```
+
+If the external cluster uses TLS:
+
+```
+```
+opensearch['use_tls'] = true
+```
+```
+
+Then reconfigure:
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
+
+The embedded OpenSearch service will not be started. Morpheus will connect directly to the external cluster using the provided hosts and credentials.
+
+- `auth_user` and `auth_password` are sent to the external cluster for authentication. These must match a user configured on the external cluster.
+- `auth_password` supports the `ENC{...}` encrypted format (see Encrypting the password).
+- Do not set `secure_mode` — that setting controls the embedded service's certificate generation and security plugin. For external TLS clusters, use `use_tls` instead.
+- `replica_count` can be adjusted to match the external cluster's topology (default `1`).
+
+## Upgrading with an External Cluster
+
+If the existing Morpheus installation was already configured to use an external Elasticsearch or OpenSearch cluster, the upgrade is straightforward — no data migration is needed on the appliance side since the data lives on the external cluster. The external cluster does not need to be migrated to OpenSearch; Morpheus supports both.
+
+**Step 1 — Upgrade the Morpheus package**
+
+Install the new Morpheus package on each appliance node.
+
+**Step 2 — Reconfigure**
+
+No morpheus.rb changes are needed. The existing `elasticsearch[...]` settings are bridged automatically.
+
+```
+```
+morpheus-ctl reconfigure
+```
+```
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.json b/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.json
new file mode 100644
index 0000000..3f63469
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+  "title": "Security Packages",
+  "ordinal": 162,
+  "parent_title": "Templates",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-ED404402-F168-4635-ADEB-02609465196E.html",
+  "topic_cluster": {
+    "clustering_title": "Security Packages",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-ED404402-F168-4635-ADEB-02609465196E",
+        "clustering_title": "Security Packages"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.md b/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.md
new file mode 100644
index 0000000..0885bbb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-ED404402-F168-4635-ADEB-02609465196E.md
@@ -0,0 +1,20 @@
+# Security Packages
+
+The Security Packages Section is for uploading SCAP packages which can then be consumed in Security Scan Jobs (Provisioning > Jobs).
+
+## Add a new Security Package
+
+### Procedure
+
+1. Navigate to Library > Templates > Security Packages
+2. Click +ADD > SCAP Package
+3. Provide a name in addition to a URL to source the package
+4. Click SAVE CHANGES
+
+### Results
+
+NOTE
+
+Currently URL is the only source option for security packages
+
+![../../_images/1add_package.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-8BD09052-92FA-4310-AE20-7EF52079B937-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json b/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
new file mode 100644
index 0000000..77e38ab
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+  "title": "Creating a Datastore",
+  "ordinal": 441,
+  "parent_title": "Remote Storage",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.html",
+  "topic_cluster": {
+    "clustering_title": "Creating a Datastore",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA",
+        "clustering_title": "Creating a Datastore"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md b/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
new file mode 100644
index 0000000..8cfc946
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EE8FF2B4-653E-448C-A0E8-80CA38DC0BCA.md
@@ -0,0 +1,19 @@
+# Creating a Datastore
+
+## About this task
+
+This procedure guides you through creating a Datastore. The datastore acts as a container for volumes and must be created before volumes can be created.
+
+## Procedure
+
+1. Log in to the HPE Morpheus Enterprise Software web interface using your administrator credentials.
+2. Navigate to Infrastructure > Storage > DataStores.
+3. Click the Add.
+4. Provide a Name, select **HPE** Alletra Block Storage Baremetal for type, select your cloud, the storage server previously created, FC as the protocol type, and the Resource Pool that applies to this storage server.
+5. Click the Save to create the DataStore.   
+   ![Add Datastore](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4455C3A5-99BD-49B4-86A3-C2CB67FDD579-high.png)
+
+## Results
+
+The added data store appears under Data Store.   
+![Data Store](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-A1A160B8-E303-4B49-85E6-20044732C34B-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json b/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
new file mode 100644
index 0000000..6392eb2
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+  "title": "CloudFormation Blueprints",
+  "ordinal": 133,
+  "parent_title": "App Blueprints",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.html",
+  "topic_cluster": {
+    "clustering_title": "CloudFormation Blueprints",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947",
+        "clustering_title": "CloudFormation Blueprints"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md b/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
new file mode 100644
index 0000000..680a6bb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EF20CD89-B756-4F84-BC6A-55B2488B5947.md
@@ -0,0 +1,46 @@
+# CloudFormation Blueprints
+
+CloudFormation Blueprints consume new or existing CloudFormation templates to create easily-deployable application stacks. CloudFormation templates in HPE Morpheus Enterprise are JSON or YAML-formatted text documents that declare all relevant AWS resources needed for the provisioned application. They can be created directly in the New Blueprint modal or pulled in from existing Git repositories.
+
+If needed, Amazon has educational resources available for getting started with CloudFormation. They can be found in the [AWS CloudFormation documentation](https://docs.aws.amazon.com/AWSCloudFormation/latest/UserGuide/Welcome.html).
+
+To create a new CloudFormation Blueprint, navigate to Library > Blueprints > App Blueprints. Click + ADD.
+
+On the Name tab of the New Blueprint modal, enter a name for your new Blueprint. In the Type dropdown menu, select CloudFormation. Click NEXT
+
+In the Blueprint Summary section, complete the following fields as needed:
+
+- **NAME:** Enter a name for this Blueprint as it will appear in the HPE Morpheus Enterprise Blueprints list
+- **DESCRIPTION:** An optional description field for your Blueprint
+- **CATEGORY:** An optional category tag for your Blueprint, such as web, utility, or app
+- **IMAGE:** An optional image icon to more easily identify your Blueprint from a list. If no image is uploaded, a default image will be used
+
+Depending on whether we need the HPE Morpheus Enterprise Agent installed and/or cloud-init enabled, mark the following boxes in the next section:
+
+- **INSTALL AGENT**
+- **CLOUD INIT ENABLED**
+
+In some cases, you must explicitly acknowledge that your template contains certain capabilities in order for the application to successfully be deployed. There is more information on this in Amazon’s documentation [here](https://docs.aws.amazon.com/AWSCloudFormation/latest/APIReference/API_CreateStack.html). If any of the following capabilities are contained in your application, acknowledge them by marking any of the following boxes that apply:
+
+- **CAPABILITY\_IAM**
+- **CAPABILITY\_NAMED\_IAM**
+- **CAPABILITY\_AUTO\_EXPAND**
+
+Continuing on with the CloudFormation Configuration section, complete the following fields as needed when entering your configuration directly into the new Blueprint:
+
+- **CONFIG TYPE:** “CloudFormation Template JSON (.json)”
+- **CONFIG TYPE:** “CloudFormation Template YAML (.yaml)”
+- **CONFIG:** Enter your configuration here
+
+In the CloudFormation Configuration section, complete the following fields as needed when syncing in configuration from a Git repository:
+
+- **CONFIG TYPE:** “Git Repository”
+- **SCM INTEGRATION:** If a pre-existing SCM integration is selected here, the available selections in the “Repository” dropdown menu will be filtered to show only those associated with the chosen SCM integration
+- **REPOSITORY:** Select the repository in which your configuration resides
+- **BRANCH OR TAG:** The branch in which your configuration resides
+- **WORKING PATH:** The path to your configuration files
+- **CONFIG:** Your selected config file
+
+Once finished, click COMPLETE.
+
+Your new CloudFormation Blueprint is now saved and should be visible in the list of Blueprints. Blueprints are deployed in the Provisioning > Apps section of HPE Morpheus Enterprise. See the Apps section of HPE Morpheus Enterprise docs for more information on that process.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json b/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
new file mode 100644
index 0000000..401c52d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+  "title": "Windows Settings",
+  "ordinal": 338,
+  "parent_title": "User Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.html",
+  "topic_cluster": {
+    "clustering_title": "Windows Settings",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD",
+        "clustering_title": "Windows Settings"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md b/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
new file mode 100644
index 0000000..e5dd2d7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-EF272A77-D8E0-48D0-8A32-DFF688731CDD.md
@@ -0,0 +1,13 @@
+# Windows Settings
+
+When provisioning a Windows-based resource and opting to have your user created during the provisioning process, the credentials entered in this section will be used to seed that user into the provisioned resource.
+
+- **Username:** The username that will be used with your Windows accounts
+- **Password:** The password that will be used with your Windows accounts
+- **Confirm:** Confirm your entered password. These must match in order for the new password value to be saved
+
+WARNING
+
+If your users Windows Settings password is not defined, and ‘Create User” is enabled during provisioning (default), a random password will be generated but not exposed and you will not be able to login with your user.
+
+![../../_images/user_settings_windows_500.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4558D828-A24E-42F3-8ACD-F5E4ACCD556C-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json b/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
new file mode 100644
index 0000000..2eb2674
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+  "title": "IBM Cloud",
+  "ordinal": 460,
+  "parent_title": "Clouds",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F003BCEE-0E64-412A-9045-295910E15A5A.html",
+  "topic_cluster": {
+    "clustering_title": "IBM Cloud",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F003BCEE-0E64-412A-9045-295910E15A5A",
+        "clustering_title": "IBM Cloud"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md b/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
new file mode 100644
index 0000000..93aa104
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F003BCEE-0E64-412A-9045-295910E15A5A.md
@@ -0,0 +1,133 @@
+# IBM Cloud
+
+IBM Cloud offers a wide set of cloud computing services including compute, storage, database, networking, and more. It is deployed in data centers across the world and its services can scale to meet the needs of small development teams as well as large-scale enterprises. HPE Morpheus Enterprise integrates with IBM Cloud to offer virtual machine provisioning, brownfield discovery, and lifecycle management.
+
+## Integrating IBM Cloud with HPE Morpheus Enterprise
+
+### About this task
+
+Connecting an IBM Cloud account with HPE Morpheus Enterprise is a simple process requiring only an API key. You can create an API key from the IBM Cloud web console if you don’t currently have access to one. Integrating with HPE Morpheus Enterprise requires a user API key. If needed, create one by clicking “Manage” in the upper menu bar of the IBM Cloud web console and clicking “Access (IAM)”. Select “Users” from the left navigation menu and click on the desired user. Create a new API Key from within the API Keys section and store the API Key in a secure place to retrieve in the next step. It’s recommended that you integrate HPE Morpheus Enterprise using an IBM Cloud admin account to ensure you won’t run into any blockers while working in HPE Morpheus Enterprise. Using HPE Morpheus Enterprise role-based access you can limit which IBM Cloud constructs and capabilities are accessible to your users.
+
+With the API key created, head back to HPE Morpheus Enterprise and continue with the following steps:
+
+### Procedure
+
+1. Navigate to Infrastructure > Clouds
+2. Click + ADD
+3. Complete the following required fields:
+
+### Results
+
+- **NAME:** A friendly name for the cloud inegration in HPE Morpheus Enterprise
+- **USERNAME:** Enter “apikey” (Do not enter your IBM Cloud username or anything other than “apikey”)
+- **API Key:** The API key value
+- **DATACENTER:** Select the IBM Cloud data center
+- **OBJECT STORE:** If desired and if any are found, select an object store
+
+1. Click NEXT
+2. Select a Group for this Cloud or create a new one if desired
+3. Complete the wizard to save the new integration
+
+![../../../_images/1createCloud1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-55120133-3640-459B-B4C4-796C4CC5C741-high.png)
+
+Once the wizard has completed, the new IBM Cloud integration will appear alongside other Clouds currently available in HPE Morpheus Enterprise. If you’ve selected to automatically onboard existing resources, those will appear shortly.
+
+IBM Cloud integrations also support a number of advanced options which were not discussed as part of the initial integration set up discussed above. For more information on the advanced options, consult the section below.
+
+### Advanced Options
+
+DOMAIN
+:   Specify a default domain for instances provisioned to this Cloud.
+
+SCALE PRIORITY
+:   Only affects Docker Provisioning. Specifies the priority with which an instance will scale into the cloud. A lower priority number means this cloud integration will take scale precedence over other cloud integrations in the group.
+
+APPLIANCE URL
+:   Alternate Appliance url for scenarios when the default Appliance URL (configured in admin  >  settings) is not reachable or resolvable for Instances provisioned in this cloud. The Appliance URL is used for Agent install and reporting.
+
+TIME ZONE
+:   Configures the time zone on provisioned VM’s if necessary.
+
+DATACENTER ID
+:   Used for differentiating pricing among multiple datacenters. Leave blank unless prices are properly configured.
+
+NETWORK MODE
+:   Unmanaged or select a Network Integration (NSX, ACI etc)
+
+LOCAL FIREWALL
+:   On or Off. Enable to managed Host and VM firewall/IP Table rules (linux only)
+
+SECURITY SERVER
+:   Security Server setting is for Security Service Integrations such as ACI
+
+TRUST PROVIDER
+:   Select Internal (Morpheus) or an existing Trust Provider Integration
+
+STORAGE MODE
+:   Single Disk, LVM or Clustered
+
+BACKUP PROVIDER
+:   Select a backup provider. Depending on the Cloud type and any currently-configured backup plugins you may select Internal Backups (Morpheus) or another configured backup solution
+
+REPLICATION PROVIDER
+:   Sets the default Replication Provider for the Cloud. Select an existing Replication Provider Integration
+
+GUIDANCE
+:   Enable Guidance recommendations on cloud resources.
+
+COSTING
+:   Enable for HPE Morpheus Enterprise to sync Costing data from the Cloud provider, when available. For on-prem Clouds, enabling costing activates a costing service designed to mirror the live costing experience of public clouds, including invoicing with line items and real-time cost data (Operations > Costing > Invoices). If your organization utilizes reserved instances and you want to pull in related pricing data, some Cloud integrations include the option to select Costing and Reservations. If this is not relevant, select Costing to save money on additional calls to the Cloud provider’s costing API.
+
+DNS INTEGRATION
+:   Records for instances provisioned in this cloud will be added to selected DNS integration.
+
+SERVICE REGISTRY
+:   Services for instances provisioned in this cloud will be added to selected Service Registry integration.
+
+CONFIG MANAGEMENT
+:   Select a Chef, Ansible or Puppet integration to be used with this Cloud.
+
+CMDB
+:   Select CMDB Integration to automatically update selected CMDB.
+
+CMDB DISCOVERY
+:   When checked, any automatically discovered (unmanaged) servers onboarded into HPE Morpheus Enterprise from this Cloud will also have CMDB records created for them.
+
+CHANGE MANAGEMENT
+:   Select an existing Change Management Integration to set on the Cloud. ex: Cherwell
+
+AGENT INSTALL MODE
+:   - SSH / WINRM / Guest Execution: HPE Morpheus Enterprise will attempt to use SSH, WINRM or Guest Execution for Agent install.
+    - Cloud Init / Unattend (when available): (DEFAULT) HPE Morpheus Enterprise will utilize Cloud-Init or Cloudbase-Init for agent install when provisioning images with Cloud-Init/Cloudbase-Init installed. HPE Morpheus Enterprise will fall back on SSH or WINRM if cloud-init is not installed on the provisioned image. Morpheus will also add Agent installation to Windows unattend.xml data when performing Guest Customizations or utilizing syspreped images.
+
+VDI GATEWAY
+:   Set a VDI Gateway for outbound communication from the HPE Morpheus Enterprise Appliance to the vdi endpoints. VDI Gateways can be added in `/tools/vdi/gateways`
+
+### CUSTOM LOGOS
+
+When integrating a Cloud, it will appear by default throughout the UI with its standard logo (VMware logo for VMware Clouds, etc.). If desired, you may upload a custom logo that should appear instead. This might be useful for MSPs which might not want to reveal the Cloud type underlying its services. A dark mode version of the logo may also be uploaded if the standard logo doesn’t look right against the HPE Morpheus Enterprise dark mode theme. Checking USE DEFAULT CLOUD LOGOS allows the user to return to the standard logo for the Cloud type without deleting the custom uploaded logo.
+
+### INVENTORY OPTIONS
+
+Inventory options allow you to set a default active or inactive state for certain discovered resources. The list of available resources to configure will vary based on the Cloud type and its supported resources. By default, all possible resources for the Cloud type will be discovered in an active state. Uncheck the box for some or all resources to discover them in an inactive state. The list of potential resources that may appear include:
+
+- Service Plans
+- Resource Pools
+- Networks
+- Security Groups
+- Datastores
+- Folders
+
+### Provisioning Command
+
+PROXY
+:   Set a proxy for inbound communication from Instances to the HPE Morpheus Enterprise Appliance. Proxies can be added in the Infrastructure  >  Networks  >  Proxies tab.
+
+Bypass Proxy for Appliance URL
+:   Enable to bypass proxy settings (if added) for HPE Morpheus Enterprise Agent communication to the Appliance URL.
+
+NO PROXY
+:   Include a list of IP addresses or name servers to exclude from proxy traversal
+
+USER DATA (LINUX)
+:   Add cloud-init user data. HPE Morpheus Enterprise 4.1.0 and earlier assumes bash syntax. HPE Morpheus Enterprise 4.1.1 and later supports all User Data formats. Refer to <https://cloudinit.readthedocs.io/en/latest/topics/format.html> for more information.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json b/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
new file mode 100644
index 0000000..40c184a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+  "title": "Overview",
+  "ordinal": 281,
+  "parent_title": "Identity Sources",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md b/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
new file mode 100644
index 0000000..0234f78
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F0ED15D7-B004-43FE-8AD7-E20CCF4DB052.md
@@ -0,0 +1,3 @@
+# Overview
+
+HPE Morpheus Enterprise can integrate with many of the most common identity source technologies, such as Active Directory, Okta, and many others. These can be configured via the Identity Sources button on any Tenant detail page (Administration > Tenants > Selected Tenant) or on the Users list page (Administration > Users). These integrations map roles within these sign-on tools to equivalent roles in HPE Morpheus Enterprise so at first log in users are assigned the appropriate role.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json b/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
new file mode 100644
index 0000000..4826d5d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+  "title": "Service Catalog Persona",
+  "ordinal": 341,
+  "parent_title": "Personas",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.html",
+  "topic_cluster": {
+    "clustering_title": "Service Catalog Persona",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4",
+        "clustering_title": "Service Catalog Persona"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md b/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
new file mode 100644
index 0000000..bb5f37f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F1C09D1D-CBAF-47D3-8B8A-374C9758F1D4.md
@@ -0,0 +1,53 @@
+# Service Catalog Persona
+
+The Service Catalog Persona presents a simplified catalog where users can select and deploy Instances or Blueprints with pre-defined configuration with just a few clicks and without presenting an overwhelming list of options.
+
+## Configuring Catalog Item Access
+
+Within the Service Catalog Persona, users are presented with Catalog Items based on their User Role. Additionally, Catalog Item access can be set on the Tenant Role to restrict certain items from all users in the Tenant. By default, User Roles have no access to any catalog items (and no access to the Service Catalog Persona). When enabling Service Catalog Persona access for User Roles, you will also need to give access to some or all Catalog Items.
+
+Configuring Global Access:
+
+- **Full:** Gives access to all Catalog Items
+- **Custom:** Gives access to individually-selected items from the list below
+- **None:** No access is given to any Catalog Items
+
+TIP
+
+When giving Custom access, be sure to set access on some of the individual catalog items to Full in order to reveal those items to the Role group.
+
+## Dashboard
+
+The default page for the Service Catalog Persona is the Dashboard. The Dashboard shows a selection of featured catalog items, a listing of the last few items the user has ordered, and a selection from the user’s inventory.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-98CB46CB-C852-48BE-8F39-09E5E676BCCE-high.png)
+
+## Catalog
+
+The catalog shows the complete list of pre-defined catalog items available to the user for provisioning. Catalog items are not created in the Service Catalog Persona. For more on creating catalog items, see the [Self Service section](https://docs.morpheusdata.com/en/latest/tools/self-service.html) (Tools > SelfService) of HPE Morpheus Enterprise docs.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-782B5419-8EEF-4E93-A621-974E15760B4A-high.png)
+
+## Inventory
+
+The Inventory Page reveals the complete list of items which have been ordered by the user and provisioned. Users will only see their own items in this section.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-BA083368-6AF1-4E7D-A035-B175C86AED03-high.png)
+
+## Inventory Detail
+
+Access the detail page for an item in your inventory by clicking the View Details link. The page displayed will look very similar to an Instance or App detail page in the Standard Persona. Highly detailed information on the health of the Instance or App are shown here. We can also take actions against Instances such as running Tasks or Workflows, reconfiguring the Instance, controlling the power state, and more.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-193E867C-87CF-49A6-B994-AC2CEE9B6D08-high.png)
+
+## Placing Orders
+
+From the Catalog page, select the tile for your chosen item to see any custom options that may need to be set prior to provisioning.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-B4E37C64-41C3-4CF9-8D36-47260212AEC6-high.png)
+
+Once the item is in the cart, make any additional selections to complete the order. Once finished, proceed to the cart by clicking on the cart icon at the top of the application window. Click “Review Order”. When reviewing your order, each selected item is listed along with its estimated cost. The total estimated cost for the entire order is also computed.
+
+![](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-6A53CB8B-6B6D-40A5-AEB3-AF96A7D8917B-high.png)
+
+Once PLACE ORDER is clicked, the provisioning process will begin and the user is redirected back to the catalog page. Any new orders can be viewed in Inventory and additional details can be accessed through the Inventory item detail page.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json b/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
new file mode 100644
index 0000000..61b58cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+  "title": "Overview",
+  "ordinal": 288,
+  "parent_title": "Plans",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.html",
+  "topic_cluster": {
+    "clustering_title": "Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49",
+        "clustering_title": "Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md b/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
new file mode 100644
index 0000000..47efcc6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F27780CE-E5E8-4E4E-B25A-328CB036BB49.md
@@ -0,0 +1,9 @@
+# Overview
+
+Service Plans determine the amount of compute resources available to each Instance. When provisioning new Instances from HPE Morpheus Enterprise, a plan is selected which determines the number of CPU cores, amount of memory and the amount of storage available to the associated machines. Additionally, when converting discovered instances in integrated clouds to HPE Morpheus Enterprise-managed Instances, the user selects a plan which best fits the instance as it is currently configured. When Instances are reconfigured, a new plan may be selected which redefines the compute resources which should be available to the Instance.
+
+Plans can be as specific or open-ended as the user would like, restricting the user to the resources defined in the plan or allowing the user to increase those amounts at provision time. Price sets are associated with plans, which is how HPE Morpheus Enterprise can compute cost values even for Instances running in private, on-prem Clouds.
+
+The Plans & Pricing section is where Plans, Prices Sets and Prices are managed. These concepts are associated with each other in the following way: Prices are added to Prices Sets, and Price Sets are added to Plans. Plans include Service Plans, Load Balancer Price Plans, Virtual Image Prices Plans and Snapshot Price Plans. Price sets can be agnostic and available for any Plan, or specific to a Region Code, Cloud or even a specific Resource Pool. Prices are configured per Price Type and can be added to Price Set configurations that support the Price Type. Master Tenant Prices can apply to all Tenants or be assigned to a single Tenant.
+
+A set of Service Plans are seeded by HPE Morpheus Enterprise for private cloud provision types as well as some public clouds. Additional Plans and Prices are synced in for other public clouds when the corresponding cloud types are added to an appliance. Users can create new Service Plans or edit the system-seeded Service Plans for Private Cloud types. Service Plans configurations cannot be created or edited for Public Cloud provision types.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json b/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
new file mode 100644
index 0000000..b4513dc
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+  "title": "Microsoft DNS",
+  "ordinal": 485,
+  "parent_title": "DNS",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.html",
+  "topic_cluster": {
+    "clustering_title": "Microsoft DNS",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71",
+        "clustering_title": "Microsoft DNS"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md b/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
new file mode 100644
index 0000000..9c25dee
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F3EE0A66-353F-4987-AE3D-C3F29AFCBE71.md
@@ -0,0 +1,328 @@
+# Microsoft DNS
+
+The HPE Morpheus Enterprise Microsoft DNS integration is developed as an official plugin separate from the core product. It is easily added and uploaded to any HPE Morpheus Enterprise appliance. Download the plugin from the official plugin repository <share.morpheusdata.com > \_ and add it to the appliance from the plugin management UI section (Administration > Integrations > Plugins).
+
+The MSDSN integration automates DNS record creation and DNS record cleanup both manually or automatically during workload provisioning to a configured Cloud or Group. It should be noted that this integration is typically not needed when joining a Windows VM to an Active Directory Domain as typically this automatically creates a DNS record.
+
+## Prepare DNS Server(s)
+
+NOTE
+
+This section will assume a the DNS server is in an Active Directory environment and joined to the domain. The process may be different for other configurations.
+
+The easiest method to prepare DNS server(s) is to use a service account that is added to the `DnsAdmins` and `Remote Management Users` groups, either in Active Directory (if DNS is on domain controllers) or the local groups of a member server. The `DnsAdmins` group will provide permissions for the service account to make DNS changes, such as creating/deleting A and PTR records. The `Remote Management Users` group will allow HPE Morpheus Enterprise to connect to the server(s) via WinRM.
+
+Additionally, ensure firewall rules have been updated if needed to allow WinRM through. In some cases, the default WinRM rules allow `Private` and `Domain` networks but not `Public`. Enable `Public` if the network HPE Morpheus Enterprise is connected is considered `Public`, or disable the firewall if permitted. If a jump box is required (discussed below), then ensure the firewall is configured to allow the jump box to connect to the DNS server instead.
+
+Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+### Minimum Permissions
+
+Some organizations may require that users cannot be added to the `DNSAdmin` group, mentioned previously. If this is a requirement, the following process/permissions would be required to ensure HPE Morpheus Enterprise can connect successfully. This process may be required on each DNS server, depending on the environment. Note that if HPE Morpheus Enterprise adds additional functionality at a later time, these permissions may need to be updated to support those features.
+
+- Run `dnsmgmt.msc`
+- Right-click the DNS server object and choose `Properties`
+- Add the service account to the user list and ensure the following permissions are applied:
+
+  - Read
+  - Create all child objects
+  - Delete all child objects
+- Run `wmimgmt.msc`
+- Right-click `WMI Control (Local)` and choose `Properties`
+- Click the `Security` tab
+- Set the following permissions for each of the below nodes:
+
+  - `CIMV2`
+  - `MicrosoftDNS`
+  - `Microsoft => Windows => DNS` (only the DNS node)
+- Hightlight the node and click the `Security` button
+- Click the `Advanced` button
+- Click the `Add` button to add the service account to the list
+- Ensure the `Applies to` field is set to `This namespace and subnamespaces`
+- Set the following permissions:
+
+  - Enable Account
+  - Remote Enable
+  - Execute Methods
+- Finally, restart Windows Management Instrumentation Service or the server. This is required for the change in permissions to take place.
+
+Additional support reference: <https://support.morpheusdata.com/s/article/How-to-give-C?language=en_US>
+
+## (Optional) Prepare Jump Box
+
+In some environments, HPE Morpheus Enterprise may not be allowed to access the DNS servers directly, as they may be on segregated networks. In this case, HPE Morpheus Enterprise can utilize a member server as a “jump box” that can access the DNS servers directly, the jump box will be used to interact with the DNS server instead. If this is a requirement, follow the below process to prepare the jump box.
+
+- Add the service account to the `Remote Management Users` group of the jump box, which will allow WinRM to access
+- Verify the firewall allows WinRM from HPE Morpheus Enterprise
+- Create or edit the following registry key by running `regedit`:
+
+  - Navigate to: `HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb`
+  - Create or edit `ProtectionPolicy` DWORD (32-bit) Value
+  - Set `ProtectionPolicy` value to `1`
+- Finally, `winrm quickconfig` may need to be run to enable WinRM, if the server is an older operating system.
+
+## Adding a Microsoft DNS integration
+
+For appliances with the MSDNS plugin installed, the option to create an integration is available. Navigate to Administration > Integrations and click + NEW INTEGRATION to create a new one.
+
+- **NAME:** A friendly name for the integration in HPE Morpheus Enterprise
+- **RPC SERVER** Enter the name of the server brokering access to the Microsoft DNS Services. This is the Windows server HPE Morpheus Enterprise will connect to directly. In most cases, the RPC SERVER will be a Windows domain-joined server with the DNS Server tools installed. HPE Morpheus Enterprise will use this server to connect and manage DNS
+- **RPC PORT:** This configuration is visible if “USE AGENT FOR RPC” is unmarked. The WinRM port number 5985/5986, default is 5985
+- **USE AGENT FOR RPC:** Select this option to have the plugin use a configured agent to handle the HPE Morpheus Enterprise to Windows RPC connection. The RPC SERVER should be an Instance (in other words, a managed VM) which is part of the same HPE Morpheus Enterprise environment where the integration is added. The HPE Morpheus Enterprise Agent must also be configured to logon as the DNS Service user account. In most cases, customers would only use this option when using an intermediate server to access DNS services
+- **CREDENTIALS:** Provide account credentials for a service account. You may use credentials already stored in HPE Morpheus Enterprise or create new Username/Password credentials
+- **DNS SERVER:** If the RPC SERVER is not the server hosting DNS Services, then add the FQDN name of the DNS server here. Leave blank if the RPC SERVER is also the DNS Server
+- **ZONE FILTER:** The ZONE FILTER is a comma separated list of glob-style filters which can be used to specify the zones that HPE Morpheus Enterprise will import and sync. Glob style filters apply to the zone name only and at a domain level. The `\*` character matches any legal DNS character [-] 0 or more times. Wildcarding stops at the . (period), leave blank to import all forward and reverse zones
+- **SERVICE TYPE:** This configuration is visible if the DNS SERVER is not blank. This option informs the plugin how the RPC SERVER should contact the DNS SERVER. There are 3 supported options: **local** when the RPC SERVER is the DNS Server (ie when DNS SERVER is blank in which case local is the default and only option), **wmi** which is used when the RPC SERVER contacts the DNS Server over WMI (Windows RPC, this is the recommended and default option when using an intermediate RPC SERVER), and **winrm** which is used when the RPC SERVER connects to DNS SERVER over a WinRM session (this is not often used due to WinRM restrictions on domain controllers)
+- **INVENTORY EXISTING:** Have the integration import and sync all DNS records for the matching Zones. Using this option is not recommended for installations with large namespaces
+- **CREATE POINTERS:** Have DNS create a PTR record when the forward record is created
+
+NOTE
+
+If you’re not using an intermediate server, the RPC SERVER will also be the DNS Server. The HPE Morpheus Enterprise Windows Agent should be set to log in using these credentials.
+
+## Domains
+
+Once the integration is added, Microsoft DNS Domains will sync and listed under Infrastructure > Network > Domains.
+
+NOTE
+
+Default Domains can be set on Networks and Clouds, and can be selected when provisioning. Additional configuration options are available by editing a domain in Infrastructure > Network > Domains
+
+## Configuring Microsoft DNS with Clouds and Groups
+
+DNS Integrations are available in the `DNS Integration` dropdown in Cloud and Group settings. HPE Morpheus Enterprise will register Instances with the DNS provider when provisioned into a Cloud or Group with a DNS Integration added.
+
+### Add DNS Integration to a Cloud
+
+#### Procedure
+
+1. In Infrastructure  >  Clouds edit the target Cloud.
+2. Expand the `Advanced Options` section.
+3. In the `DNS Integration` dropdown, select an available DNS Integration.
+4. Save Changes
+
+### Add DNS Integration to a Group
+
+#### Procedure
+
+1. In Infrastructure  >  Groups select the target Group.
+2. Select the `Edit` button for the Group
+3. Expand the `Advanced Options` section.
+4. In the `DNS Integration` dropdown, select an available DNS Integration.
+5. Save Changes
+
+#### Results
+
+NOTE
+
+Instances provisioned into a Cloud or Group with a DNS Integration added will be registered as instancename.domain with the DNS Provider during provisioning, and de-registered at teardown.
+
+## Using Zone Filters
+
+In this example a ZONE FILTER string of
+
+`*.morpheus.com, *.10.in-addr.arpa, d*.us.morpheus.com`
+
+would
+
+**IMPORT**`test.morpheus.com, prod.morpheus.com` but **NOT** `mydomain.test.morpheus.com` which has a 4th level
+
+**IMPORT**`32.10.in-addr.arpa, 33.10.in-addr.arpa` but **NOT** `12.11.in-addr.arpa` or `10.in-addr.arpa` (which has 3 levels)
+
+**IMPORT**`denver.us.morpheus.com` and `delaware.us.morpheus.com` but **NOT** `ohio.us.morpheus.com` (wildcard at 4th level)
+
+## Improved Integration Validation
+
+Recent versions of this integration have improved the error handling and validation. RPC connectivity and access to DNS Services is tested at the time the integration dialog is saved. The dialog will not save unless validation is passed successfully. The integration dialog will hint where problems occur but you should check the HPE Morpheus Enterprise Health logs (Administration > Health > Morpheus Logs) to see detailed messages.
+
+TIP
+
+To force the integration to save you can uncheck the ENABLED checkbox. Doing this disables the validation testing allowing you to save the integration dialog contents and perform troubleshooting without having to reenter configurations. When the issue is resolved, edit the integration and set the integration to ENABLED. Validation will then be performed on the save.
+
+## Custom Powershell Module Script
+
+Recent versions of this integration include a custom Powershell Module script (.ps1 file) which is maintained by the plugin and transferred to the RPC SERVER when the integration is added. The Powershell script file contains functions designed to handle the interface between Morpheus and DNS. The script uses the standard Windows DNS-Server module (Windows feature RSAT-DNS-Server). The script file is MD5 checked each time the integration syncs and the module is refreshed from the plugin if the checksum fails. The custom script is stored in the **%LOCALAPPDATA%** folder for the integration service account user.
+
+The module contains custom functions designed to interface with the MSDNS plugin via JSON.
+
+- Having the Powershell module installed on the RPC SERVER offers some performance benefits as HPE Morpheus Enterprise now can call on the modules functions to perform tasks
+- The Powershell functions test RPC connectivity and DNS service connectivity on each sync refresh ensuring the integration is healthy
+- The module uses a standard JSON interface between Windows RPC SERVER and HPE Morpheus Enterprise
+- The module overcomes restrictions imposed on HPE Morpheus Enterprise WinRM connections authenticating with NTLM
+
+IMPORTANT
+
+For version 2.1.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v32.ps1` and for version 2.3.3, the script file is named `%LOCALAPPDATA%\morpheusDnsPluginHelper_v34.ps1`. The HPE Morpheus Enterprise health logs will log the status of the HPE Morpheus Enterprise Powershell file on each refresh. For example: `INFO c.m.m.MicrosoftDnsPluginHelper - testHelperFileScript - Checking for valid Helper script fileName: morpheusDnsPluginHelper_v32.ps1 - MD5: 698d8e6ad0bf7f64d9e9ccac962e4ab1`
+
+## Secure credential cache file
+
+The HPE Morpheus Enterprise Powershell functions use a technique where script blocks are executed with Invoke-Command passing a credential object. This effectively creates a new session from RPC SERVER using kerberos overcoming the restrictions imposed by Windows on the original Morpheus NTLM connection. Credentials are cached using the Windows Data Protection API meaning only the user account who created the credential can decrypt it and only on the original Windows server. The credential cache is stored in `%LOCALAPPDATA%\S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` where `S-1-5-21-nnnnnnnnnn-nnnnnnnnnn-nnnnnnnnnn-nnnn-dnsPlugin.ss` is the Service Account SID.
+
+NOTE
+
+If “USE AGENT FOR RPC” is checked, there is no need to create a new session since the original session is already Kerberos, however the credentials are still cached.
+
+## Troubleshooting Connections
+
+### Service Account Requirements
+
+The service account used to access DNS via the plugin must meet the following requirements:
+
+- If using an intermediate server as the RPC SERVER, the service account should be a member of local `administrators` group on the RPC SERVER
+- If “USE AGENT FOR RPC” is checked, the HPE Morpheus Enterprise Windows Agent service must be configured to login as the service account. The service account will require `Log on as a Service` rights in the RPC SERVER local policy
+- If not using an intermediate server, the service account must be a member of `Remote Management Users` on the RPC SERVER as a minimum in order to access the RPC SERVER from HPE Morpheus Enterprise via WinRM. Membership of `administrators` however, is recommended
+- The service account must be a member of the domain global group `DNS Admins`
+- To Access Microsoft DNS WMI namespaces, the service account must be granted access to the DNS WMI classes
+
+### RPC SERVER requirements
+
+When using an intermediate server as the RPC SERVER, the following requirements must be met:
+
+- The RPC SERVER must be a Windows Server which is a member of a domain or forest which is trusted to access the DNS namespace
+- The RPC SERVER must have the Microsoft Windows feature RSAT-DNS-Server installed
+- If planning to “USE AGENT FOR RPC” then the Windows server must have a HPE Morpheus Enterprise Windows Agent installed and this agent must report into the HPE Morpheus Enterprise environment where the DNS Integration is being added or configured. Ideally, HPE Morpheus Enterprise will have deployed the RPC SERVER as an Instance
+- If not planning to “USE AGENT FOR RPC” then the RPC server must have WinRM configured and must be reachable over WinRM from the HPE Morpheus Enterprise appliance
+- When using an intermediate server to access DNS Services, the computer account of the RPC SERVER must be configured for delegation `Trusted for Delegation to any service (Kerberos only)`. Use Active Directory Users and Computers, locate the computer account for RPC SERVER. Click properties and select the Delegation tab and choose the option `Trust this computer for delegation to any service (Kerberos only)`
+
+## Using the plugin test Service page
+
+Recent versions of this integration have the ability to run a connection test via the HPE Morpheus Enterprise appliance. Users must have full access to the Integrations permission to test a Microsoft DNS plugin connection. For example, to test connectivity to an integration with id value of 5, browse to the following URL in HPE Morpheus Enterprise: `https://my.morpheus.appliance/plugin/msdns/service?integrationId=5`
+
+The plugin will run a series of tests using details from the integration dialog.
+
+NOTE
+
+Tests can be run even if the integration ENABLED checkbox is unmarked allowing troubleshooting with the integration offline.
+
+The results are output in the browser in JSON.
+
+In the example below, inspect the `serviceProfile`. Here, the `rpcType` is “agent” so “USE AGENT FOR RPC” is checked and the `serviceType` is “wmi”. The `rpcSession` and `serviceSession` show the connection details, logon types and group membership for the RPC and service sessions. The `dnsServer` section shows the FQDN and version of the DNS server and if populated indicates a successful test (status = 0).
+
+If the test is unsuccessful, a status code other than 0 is returned and any error will be listed in the “Errors” section
+
+```
+```
+Morpheus Microsoft DNS Integration Service Profile  
+Discovered service profile for Microsoft DNS integration : 5  
+Rpc Connection Status true  
+Successful rpc response from spie-mo-w-3011 via agent: Command completed successfully  
+Errors  
+{  
+}  
+Rpc Output  
+{  
+    "status": 0,  
+    "cmdOut": {  
+        "serviceProfile": {  
+            "rpcHost": "SPIE-MO-W-3011",  
+            "rpcType": "agent",  
+            "serviceHost": "ip-c61302.myad.net",  
+            "serviceType": "wmi",  
+            "useCachedCredential": false  
+        },  
+        "dnsServer": {  
+            "computerName": "IP-C61302.myad.net",  
+            "version": "10.0.17763"  
+        },  
+        "rpcSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "serviceSession": {  
+            "userId": "myad\\spsvcdns",  
+            "computerName": "SPIE-MO-W-3011",  
+            "authenticationType": "Kerberos",  
+            "impersonation": "None",  
+            "isAdmin": true,  
+            "localProfile": "C:\\Users\\spsvcdns\\AppData\\Local",  
+            "tokenGroups": [  
+                "myad\\Domain Users",  
+                "Everyone",  
+                "BUILTIN\\Users",  
+                "BUILTIN\\Administrators",  
+                "NT AUTHORITY\\SERVICE",  
+                "CONSOLE LOGON",  
+                "NT AUTHORITY\\Authenticated Users",  
+                "NT AUTHORITY\\This Organization",  
+                "LOCAL",  
+                "Authentication authority asserted identity",  
+                "myad\\AWS Delegated Domain Name System Administrators",  
+                "myad\\AWS Delegated Server Administrators",  
+                "myad\\AWS Delegated Add Workstations To Domain Users",  
+                "myad\\DnsAdmins",  
+                "myad\\AWS Delegated Kerberos Delegation Administrators"  
+            ],  
+            "isSystem": false,  
+            "isService": true,  
+            "isNetwork": false,  
+            "isBatch": false,  
+            "isInteractive": false,  
+            "isNtlmToken": false  
+        },  
+        "domainSOAServers": {  
+            "nameToQuery": "ip-c61302.myad.net",  
+            "fqdn": "ip-c61302.myad.net",  
+            "dcList": [  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61301.myad.net"  
+                },  
+                {  
+                    "zone": "myad.net",  
+                    "dnsServer": "ip-c61302.myad.net"  
+                }  
+            ]  
+        }  
+    },  
+    "errOut": null  
+}
+```
+```
+
+## DNS Record validation and Error Handling
+
+- DNS records are now fully validated before they are created. Only record types A, AAAA, CNAME and PTR are currently supported
+- Adding a DNS Record which already exists (ie FQDN and IP address match an existing record in DNS) would normally return an error (code 9711), this is masked to a success to prevent HPE Morpheus Enterprise aborting the provision
+- Removing a HPE Morpheus Enterprise DNS Record that does not exist in DNS (error 9714) is also masked to success to have HPE Morpheus Enterprise delete its copy
+- If a fwd record is created but the PTR record fails (due to missing PTR zone error 9715), this is also masked to success to prevent HPE Morpheus Enterprise aborting the Provision
+- All errors are logged to the HPE Morpheus Enterprise health logs (Administration > Health > Morpheus Logs).
+
+## AWS Directory Services Support
+
+Support is included for AWS Active Directory service.
+
+- Access is only possible via a correctly configured intermediate server (RPC SERVER) hosted in AWS and having the DNS Management Tools installed
+- The DNS SERVER must be the fully qualified name of one of the AWS Domain controllers
+- The Service Account should be a member of AWS Delegated Domain Name System Administrators, AWS Delegated Kerberos Delegation Administrators and AWS Delegated Server Administrators (for access to RPC SERVER)
+- The RPC SERVER computer object should be trusted for delegation for all Kerberos Services on the AWS Directory Service domain controllers. This can be performed using AD Users and Computers to modify the properties of the RPC SERVER Computer object. Right click the computer object, select properties and open the Delegation tab. Select the Radio button `Trust this computer for delegation to any service (Kerberos Only)`. Click OK to Save
+
+NOTE
+
+It is possible to finely tune the delegation so that the RPC SERVER computer object can only delegate to specific services if this is required.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json b/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
new file mode 100644
index 0000000..3a058c7
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+  "title": "Reconfiguring Volume",
+  "ordinal": 446,
+  "parent_title": "Volume Management",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.html",
+  "topic_cluster": {
+    "clustering_title": "Reconfiguring Volume",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088",
+        "clustering_title": "Reconfiguring Volume"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md b/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
new file mode 100644
index 0000000..95301ea
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6459690-0DE9-48CE-95B2-C7BE033E8088.md
@@ -0,0 +1,19 @@
+# Reconfiguring Volume
+
+## About this task
+
+Reconfiguration allows the user to make changes to volumes consumed by a compute instance post-provisioning. This is achieved through the Reconfigure action on the instance.
+
+New volumes can be created and attached to the compute instance. These can be shared or unshared volumes. Any volume attached to the compute instance can be resized to increase the size of the volume. Any attached volume can be detached. However, volumes cannot be deleted from the Reconfigure action. Volumes can be deleted only from the infrastructure management section.
+
+All these operations work in the context of a compute instance and are not specific to a compute server within the instance.
+
+## Procedure
+
+1. Navigate to Provision > Instance.
+2. Click on the compute instance you want to reconfigure and access the details of the instance.
+3. Click on Actions and select Reconfigure.   
+   ![Action Reconfigure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-DE3C1BD1-CF86-4745-BF9D-F88C65D2E407-high.png)
+4. In the Reconfigure wizard, make the changes desired to add a new volume, resize an existing volume or click the trash icon to detach a volume from the instance.   
+   ![Reconfigure Instance](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-12FE7650-4E11-449B-907A-4AB15A132992-high.png)
+5. Click on Reconfigure.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json b/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
new file mode 100644
index 0000000..fa29c4f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+  "title": "Morpheus API & CLI",
+  "ordinal": 527,
+  "parent_title": null,
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.html",
+  "topic_cluster": {
+    "clustering_title": "Morpheus API & CLI",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4",
+        "clustering_title": "Morpheus API & CLI"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md b/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
new file mode 100644
index 0000000..6de0d35
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F695DE83-0DF8-4C5E-A932-79B60E12C7B4.md
@@ -0,0 +1,4 @@
+# Morpheus API & CLI
+
+- [API Documentation](https://apidocs.morpheusdata.com)
+- [CLI Documentation](https://clidocs.morpheusdata.com)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json b/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
new file mode 100644
index 0000000..356e521
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+  "title": "VMware Support Statement",
+  "ordinal": 52,
+  "parent_title": "Core Functionality",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.html",
+  "topic_cluster": {
+    "clustering_title": "VMware Support Statement",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29",
+        "clustering_title": "VMware Support Statement"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md b/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
new file mode 100644
index 0000000..95b085a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6AA539D-0F1B-416D-B507-ECC21F8A7A29.md
@@ -0,0 +1,18 @@
+# VMware Support Statement
+
+## About this task
+
+Morpheus Data will support customers who run HPE Morpheus Enterprise products on supported operating systems, irrespective of whether they are running in VMware environments or not. Morpheus Data supports operating systems, not specific hardware configurations. Accordingly, VMware operates as a hardware abstraction layer.
+
+VMware supports a set of certified operating systems and hardware. The customer and VMware will be responsible for any interactions or issues that arise at the hardware or operating system layer as a result of their use of VMware.
+
+Morpheus Data will not require clients to recreate and troubleshoot every issue in a non-VMware environment; however, Morpheus Data does reserve the right to request our customers to diagnose certain issues in a native certified operating system environment, operating without the virtual environment. Morpheus Data will only make this request when there is reason to believe that the virtual environment is a contributing factor to the issue.
+
+Any time spent on investigation of problems that may, in the sole opinion of Morpheus Data be related to VMware, will be handled in the following fashion:
+
+## Procedure
+
+1. Morpheus Data will provide standard support to all HPE Morpheus Enterprise products.
+2. If a problem is encountered while HPE Morpheus Enterprise is/are running in a VMware environment, the client may be required to recreate the problem on a non-VMware server unit, at which time Morpheus Data will provide regular support.
+3. The client can authorize Morpheus Data to investigate the VMware-related items at normal time and materials rates. If such investigation shows that the problem is VMware related, the client may contract Morpheus Data to provide a software change to resolve the issue if such a resolution is possible.
+4. Regardless of the problem type or source, if the problem is determined to be a non VMware-related issue, time spent on investigation and resolution will be covered as part of regular maintenance and support will be provided as usual.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json b/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
new file mode 100644
index 0000000..8acda92
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+  "title": "Provisioning an Instance",
+  "ordinal": 417,
+  "parent_title": "Provisioning a New Server",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning an Instance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7",
+        "clustering_title": "Provisioning an Instance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md b/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
new file mode 100644
index 0000000..4e151e3
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F6FA00DA-FD93-4AF1-BA10-BB876D19C6A7.md
@@ -0,0 +1,37 @@
+# Provisioning an Instance
+
+## About this task
+
+Perform the following steps to provision an instance:
+
+## Procedure
+
+1. Navigate to Provisioning > Instances.   
+   ![Provisioning](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-C7BB967B-5DC0-4932-8F24-0AD471BB5430-high.png)
+2. Click the + ADD.
+3. In the TYPE tab, select the Instance Type as HPE Bare Metal (ILO) SERVER.  
+   ![Type](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D8ED39AD-773F-408D-9AC6-075C86E99337-high.png)
+4. In the GROUP tab, complete the Instance Summary fields.  
+   ![Group](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-7F89FF6E-7D74-47A0-8C79-7564B839ED39-high.png)
+5. In the CONFIGURE tab, complete the Configuration Options:
+
+   1. Layout: Select the appropriate layout from the drop-down list (for example, Single iLO Server).
+   2. Plan: Choose one of the following:
+
+      - Generic Plan: Any iLO
+      - Specific Plan: For example, DL360.Gen10Plus.1-32C.129-256GiB
+   3. Resource Pool: Select the required resource pool from the drop-down list.
+   4. Volumes: Configure storage volumes as required. Refer to the Storage section for details.
+      - Enter the name of the volume in the first field.
+      - Select the volume type from the drop down list.
+
+        NOTE
+
+        When you select any other option apart from RAID, the system shows additional field to specify storage capacity. Enter the required storage. Ensure that you configure more than 16 GB storage. You cannot specify more than one volume for Windows environment.
+   5. Networks: Configure network settings as required. Refer to the Networking section for details.
+   6. Image: Select the Bare Metal OS image from the drop-down list.
+   7. Baremetal Host(s): Select the target Bare Metal host(s) from the drop-down list if specific server(s) are desired.  
+   ![Configure](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-CD1137C9-31F0-4058-91C5-B2329DBF2836-high.png)
+6. In the AUTOMATION tab, select the appropriate options, then click Next.
+7. In the REVIEW tab, verify the configuration summary and click Complete.   
+   ![Review](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-86C9130B-3808-4D68-AD5F-75D408B4B4C8-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json b/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
new file mode 100644
index 0000000..8d4259a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+  "title": "Requirements",
+  "ordinal": 80,
+  "parent_title": "Provisioning",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.html",
+  "topic_cluster": {
+    "clustering_title": "Requirements",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9",
+        "clustering_title": "Requirements"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md b/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
new file mode 100644
index 0000000..6ead524
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F721C7A6-2022-4F4F-9FDC-36C70A2ABEC9.md
@@ -0,0 +1,231 @@
+# Requirements
+
+Provisioning Instances and Apps typically involves many steps beyond starting a workload. HPE Morpheus Enterprise is centered around automating everything desired for your application to be fully operational, including networking, storage, hostnames, domains, dns, licenses, scripts/automation, scaling, load balancers, security, accessibility, governance, auditing, monitoring, backups, costs, sizing and on and on. Point being there is a lot that goes on when spinning up an instance or app, and to make the magic happen a few requirements need to be met.
+
+IMPORTANT
+
+By default, Agent Installation is enabled when provisioning unless deselected on the Virtual Images or SKIP AGENT INSTALL is selected when provisioning.
+
+## VM Provision Steps
+
+While an infinite number of steps can happen when provisioning an Instance or App using VM(s) in HPE Morpheus Enterprise, the basic order is:
+
+- Look for Virtual Image
+
+  HPE Morpheus Enterprise will check if the Virtual Image set on the Node Type or selected during provisioning is already available in the source Cloud. If not and it is an Uploaded/Local Image, HPE Morpheus Enterprise will attempt to upload the Image to the target Cloud.
+
+  **Upload Image**
+
+  For Uploaded/Local Images that do not exist in the target cloud, HPE Morpheus Enterprise will need to upload the Image. Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+  NOTE
+
+  When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+  **Clone Image**
+
+  Once the Image is confirmed available in the target cloud, HPE Morpheus Enterprise will clone the Image to the target Datastore.
+
+  NOTE
+
+  The target host must have access to the target Datastore of the Image
+- Reconfigure Image
+
+  Once cloned, HPE Morpheus Enterprise will resize the Image based off provisioning parameters
+- Cloud-init (if enabled)
+  :   Attached cloud-init iso
+      :   When using cloud-init, HPE Morpheus Enterprise will attach a tiny metadata iso to the new VM. Network, Machine, User and any other cloud-init metadata will be sourced from this iso.
+
+      VM Tools
+      :   HPE Morpheus Enterprise will run Guest Customizations via VMware VM Tools, including network config when assigning static IP’s.
+- Wait for Power On status and Network info
+
+  HPE Morpheus Enterprise will wait to hear back from the target cloud/hypervisor that the VM has successfully started and has an IP address.
+
+  NOTE
+
+  If `VM TOOLS INSTALLED?` is NOT checked on the source Virtual Image configuration, HPE Morpheus Enterprise will skip waiting for network.
+- Finalize
+
+  By default this will include Agent Installation and any post-provision scripts or workflows or integration automation steps.
+
+  IMPORTANT
+
+  If the VM is stuck in finalize for longs periods of time, this typically means the Agent cannot be installed or has not been heard back from. This will result in a ! warning Instance status upon provisioning completion.
+
+  If agent installation is not possible or desired, uncheck “Install Agent” on the source Virtual Image configuration or select “Skip Agent Install” during provisioning to speed up provisioning completion.
+
+## Virtual Images
+
+While containers are the future, the most common provisioning method involves Virtual Machines, and the most important part of Provisioning a VM is the Virtual Image. When provisioning a VM, HPE Morpheus Enterprise will need to do a few things depending on the location of the Virtual Image and if agent install, console access, and script execution is desired.
+
+Synced Images need to be properly configured
+:   HPE Morpheus Enterprise gathers as much metadata for synced images as possible, but depending on the cloud, os, image configuration, agent install settings, by default the synced Virtual Images may not be ready to provision until configured. The Virtual Image is already at the target Cloud, but datastore selection, credentials, cloud-init settings, and networks and security settings on the Virtual Image can cause provisioning issues.
+
+Local/Uploaded Virtual Images
+:   Images uploaded to HPE Morpheus Enterprise are configured during the Add Virtual Image process, however HPE Morpheus Enterprise in most scenarios will still need to copy the Virtual Image to the target Hypervisor/Cloud upon the first provision to the target Cloud. In addition to the requirements for provisioning a synced Virtual Image, copying an uploaded Virtual Image to the target Cloud is required and network and image configurations can cause upload failures, resulting in provisioning issues.
+
+Marketplace Images
+:   AWS and Azure marketplace Images can be provisioned using the generic Amazon or Azure Instance Types, or added as Virtual Images as scoped to Node Types for custom Instance Types. Marketplace items provisioned/added to HPE Morpheus Enterprise still fall upon the requirements of the target Cloud, such as matching the region with the Image and licensing.
+
+### Synced Images
+
+When a Cloud is added to HPE Morpheus Enterprise, all available Images/Templates records from that Cloud will be synced in regardless of Inventory settings on the Cloud. These Image records will be available in the Virtual Images section and can be provisioned by using the target clouds generic Instance Type, ie VMware, Amazon, Azure, Openstack etc Instance Types, or by creating custom Instance Types and selecting the Image on a Node Type.
+
+NOTE
+
+Synced Virtual Images are just meta-data records in HPE Morpheus Enterprise pointing to the Image in the target Cloud. The actual Image files are not copied/imported to HPE Morpheus Enterprise.
+
+Before provisioning a synced Virtual Images, ensure the image is configured properly:
+
+Name
+:   Name of the Virtual Image in HPE Morpheus Enterprise. This can be changed from the name of the Image, but editing will not change the name of the actual Image.
+
+Operating System
+:   Specifies the Platform and OS of the image. All Windows images will need to have Operating System specified on the Virtual Image, as HPE Morpheus Enterprise will assign Linux as the Platform for all Images without Operating System specified.
+
+Minimum Memory
+:   The Minimum Memory setting will filter available Service Plans options during provisioning. Service Plans that do not meet the Minimum Memory value set on the Virtual Image will not be provided as Service Plan choices.
+
+Cloud Init Enabled?
+:   On by default, uncheck for any Image that does not have Cloud-Init or Cloudbase-Init installed.
+
+    IMPORTANT
+
+    Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+Install Agent
+:   On by default, uncheck to skip Agent install. Note this will result in the loss of utilization statistics, logs, script execution, and monitoring. (Some utilization stats are collected for agent-less hosts and vm’s from VMware and AWS clouds).
+
+Username
+:   Existing Username on the Image. This is required for authentication, unless HPE Morpheus Enterprise is able to add user data, Cloud-Init, Cloudbase-Init or Guest Customizations. If Cloud-Init, Cloudbase-Init Guest Customizations or Nutanix Sysprep are used, credentials are defined in Administration > Settings > Provisioning and User Settings. If credentials are defined on the Image and Cloud-Init is enabled, HPE Morpheus Enterprise will add that user during provisioning, so ensure that user does not already exist in the image (aka `root`). For Windows Guest Customizations, HPE Morpheus Enterprise will set the Administrator password to what is defined on the image if Administrator user is defined. Do not define any other user than Administrator for Windows Images unless using Cloudbase-init. HPE Morpheus Enterprise recommends running Guest Customizations for all Windows Images, which is required when joining Domains as the SID will change.
+
+Password
+:   Password for the Existing User on the image if Username is populated.
+
+Storage Provider
+:   Location where the Virtual Image will be stored. Default Virtual Image Storage location is /var/opt/morpheus/morpheus-ui/VMs. Additional Storage Providers can be configured in Infrastructure > Storage.
+
+Cloud-Init User Data
+:   Accepts what would go in runcmd and can assume bash syntax. Example use: Script to configure satellite registration at provision time.
+
+Permissions
+:   Set Tenant permissions in a multi-tenant HPE Morpheus Enterprise environment. No impact on single-tenant environments.
+    :   Visibility
+        :   Private
+            :   Image is only available in the specified Tenants below.
+
+            Public
+            :   Image is available to all Tenants.
+
+        Tenant
+        :   If Visibility is set to Private, specify Tenants the Image will be available for.
+
+Auto Join Domain?
+:   Enable to have Instances provisioned with this image auto-join configured domains (Windows only, domain controller must be configured in Infrastructure > Network and the configured domain set on the provisioned to Cloud or Network).
+
+VirtIO Drivers Loaded?
+:   Enable if VirtIO Drivers are installed on the image for provisioning to KVM based Hypervisors.
+
+VM Tools Installed?
+:   On by default, uncheck if VMware Tools (including OpenVMTools) are not installed on the Virtual Image. HPE Morpheus Enterprise will skip network wait during provisioning when deselected.
+
+Force Guest Customization?
+:   VMware only, forces guest customizations to run during provisioning, typically when provisioning to a DHCP network where guest customizations would not run by default. This is required for host/computer name definitions. domain joining, licenses and user definitions when using DHCP.
+
+Trial Version
+:   Enable to automatically re-arm the expiration on Windows Trial Images during provisioning.
+
+Enabled Sysprep?
+:   Applicable to Nutanix Only. Enable if the Windows Image has been sysprepped. If enabled, HPE Morpheus Enterprise will inject Unattend.xml through the Nutanix API (v3+ only)
+
+IMPORTANT
+
+Provisioning a Virtual Image that has Cloud Init Enabled? checked on the Virtual Record in HPE Morpheus Enterprise but does not have cloud-init installed will result in immediate provisioning failure.
+
+IMPORTANT
+
+For Linux images without cloud-Init, an existing username and password must be defined on the Virtual Image record for Agent Install, Domain joining, licensing, script execution and other automation, and SSH or RDP Console access.
+
+### Local Virtual Images
+
+A Local Virtual Image means it has been uploaded to HPE Morpheus Enterprise. To provision, HPE Morpheus Enterprise will need to upload the Image to the target Cloud upon first provision.
+
+- Ensure the Virtual Image is valid for the target Cloud, the Image meets the target cloud upload requirements, and HPE Morpheus Enterprise has network access and permissions to upload the image.
+
+NOTE
+
+When uploading an image to a VMware Cloud, the Virtual Image is copied directly to the target ESXi host, NOT through the vCenter server. Ensure the HPE Morpheus Enterprise Appliance(s) can resolve target ESXi hostnames and connect on port 443 for successful vmdk/ova uploads.
+
+Once a Local Virtual Image has been uploaded to a Cloud, subsequent provisions will use the Image local to the cloud instead of uploading again as long as the copied image is still available in the source Cloud.
+
+## Agent Install
+
+When provisioning an instance, there are some network and configuration requirements to successfully install the morpheus agent. Typically when a vm instance is still in the provisioning phase long after the vm is up, the instance is unable to reach HPE Morpheus Enterprise, or depending on agent install mode, HPE Morpheus Enterprise is unable to reach the instance.
+
+The most common reason an agent install fails is the provisioned instance cannot reach the HPE Morpheus Enterprise Appliance via the appliance\_url set in Administration > Settings over both 443 and 80. When an instance is provisioned from HPE Morpheus Enterprise, it must be able to reach the HPE Morpheus Enterprise appliance via the appliance\_url or the Agent will not be installed.
+
+![../_images/agent-7c9a2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2D5FF1AC-0C5C-4977-BFC3-19FBA953BC8F-high.png)
+
+In addition to the main appliance\_url in Administration > Settings, additional appliance\_urls can be set per cloud in the Advanced options of the cloud configuration pane when creating or editing a cloud. When this field is populated, it will override the main appliance url for anything provisioned into that cloud.
+
+TIP
+
+The HPE Morpheus Enterprise UI current log, located at /var/log/morpheus/morpheus-ui/current, is very helpful when troubleshooting agent installations.
+
+### Agent Install Modes
+
+There are 3 Agent install modes:
+
+- ssh/winrm
+- VMware Tools
+- cloud-init
+
+#### For All Agent Install modes
+
+When an instance is provisioned and the agent does not install, verify the following for any agent install mode:
+
+- The HPE Morpheus Enterprise appliance\_url (Administration > Settings) is both reachable and resolvable from the provisioned node.
+- The appliance\_url begins with to `https://`, not `http://`.
+
+NOTE
+
+Be sure to use `https://` even when using an IP address for the appliance.
+
+- Inbound connectivity access to the HPE Morpheus Enterprise Appliance from provisioned VM’s and container hosts on port 443 (needed for agent communication)
+- Private (non-morpheus provided) vm images/templates must have their credentials entered. These can be entered/edited in the Library > Virtual Images section but clicking the Actions dropdown of an image and selecting Edit.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+- The instance does not have an IP address assigned. For scenarios without a DHCP server, static IP information must be entered by selecting the Network Type: Static in the Advanced section during provisioning. IP Pools can also be created in the Infrastructure > Networks > IPPools section and added to clouds network sections for IPAM.
+- DNS is not configured and the node cannot resolve the appliance. If DNS cannot be configured, the IP address of the HPE Morpheus Enterprise appliance can be used as the main or cloud appliance.
+
+### SSH/Winrm
+
+#### Linux Agent
+
+- Port 22 is open for Linux images, and SSH is enabled
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+![../_images/agent_ssh.gif](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D2F4F5EE-5377-4E4A-A6E8-DAD6ED4FBD80-high.gif)
+
+#### Windows Agent
+
+- Port 5985 must be open and WinRM enabled for Windows images.
+- Credentials have been entered on the image if using custom or synced image. Credentials can be entered on images in the Library > Virtual Images section.
+
+NOTE
+
+Administrator user is required for Windows agent install.
+
+### VMware tools (vmtools) rpc mode
+
+- VMware tools is installed on the template(s)
+- Credentials have been entered on the Image if using uploaded or synced image when Cloud-init or Guest Customizations or Sysprep for Windows are not used. Credentials can be entered on Images in the Library > Virtual Images section.
+
+### Cloud-Init agent install mode
+
+- Cloud-Init is configured in Administration > Settings > Provisioning section
+- Provisioned image/blueprint has Cloud-Init (linux) or Cloudbase-Init (windows) installed
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json b/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
new file mode 100644
index 0000000..3ed2cdb
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+  "title": "Integrations",
+  "ordinal": 311,
+  "parent_title": "Integrations",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.html",
+  "topic_cluster": {
+    "clustering_title": "Integrations",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF",
+        "clustering_title": "Integrations"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md b/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
new file mode 100644
index 0000000..426743a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F7C9EB98-701B-4C51-966C-3448AF3575AF.md
@@ -0,0 +1,26 @@
+# Integrations
+
+NOTE
+
+To add and edit certain integrations such as Ansible Tower, vRO, Chef and Puppet, the user must have FULL permission for “Library: Integrations” in addition to “Admin: Integrations”.
+
+To add an integration select + ADD and choose your integration. Many HPE Morpheus Enterprise-supported integrations can be configured in this section, though not all. Some integrations, such as networking integrations, must be configured within their own areas of the application. The following integrations can be configured in this section:
+
+- Chef
+- Puppet
+- Ansible
+- Ansible Tower
+- vRealize Orchestrator
+- Microsoft DNS
+- PowerDNS
+- Route 53
+- Bind DNS
+- Git
+- Github
+- Docker Repositories
+- Jenkins
+- ServiceNow
+- Cherwell
+- Remedy
+
+Refer the [Guides](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-334FA46B-AE38-41A7-BACC-8F8384C5D010.html) for each specific integration type for more detailed information on setup steps and features supported by the integration.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json b/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
new file mode 100644
index 0000000..2f0dad9
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+  "title": "Initial Appliance Setup",
+  "ordinal": 39,
+  "parent_title": "Getting Started",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.html",
+  "topic_cluster": {
+    "clustering_title": "Initial Appliance Setup",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990",
+        "clustering_title": "Initial Appliance Setup"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md b/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
new file mode 100644
index 0000000..d2144be
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-F8ACBA94-AE68-44F7-A393-3EBA8C513990.md
@@ -0,0 +1,80 @@
+# Initial Appliance Setup
+
+## Appliance Setup
+
+### About this task
+
+After installation, log into the appliance at the URL presented upon completion. An initial setup wizard walks through the first account and user creations.
+
+### Procedure
+
+1. Enter Master Account name 
+
+   - Typically, the Master Account name is your Company name.
+2. Create Master User 
+
+   - First Name
+   - Last Name
+   - Username
+   - Email Address
+   - Password \* Must be at least 8 characters long and contain one each of the following: Uppercase letter, lowercase letter, Number, Special Character
+3. Enter Appliance Name & Appliance URL 
+
+   - The Appliance Name is used for white labeling and as a reference for multi-appliance installations.
+   - The Appliance URL is the URL all provisioned instances will report back to. Example: <https://example.morpheusdata.com>. The Appliance URL can be changed later, and also set to a different URL per cloud integration.
+4. Optionally Enable or Disable Backups, Monitoring, or Logs from this screen. 
+
+   NOTE
+
+   You may adjust these settings from the Administration section.
+
+   NOTE
+
+   The Master Account name is the top-level admin account.
+
+   NOTE
+
+   The Master User is the system super user and will have full access privileges.
+
+### Results
+
+Upon completing of the initial appliance setup, you will be taken to the Administration > Settings page, where you will add your License Key.
+
+## Login Methods
+
+Master Tenant
+
+- Enter username (or email address) and password
+
+Subtenant
+
+To login, subtenants can either use the master tenant URL with `subtenant\username` formatting:
+
+Example:
+:   I have a username `subuser` that belongs to a tenant with the subdomain `subaccount`. When logging in from the main login url, I would now need to enter in: `subaccount\subuser`
+
+Or use the tenant specific URL which can be found and configured under Administration > Tenants > Select Tenant > IdentitySources.
+
+![../../_images/tenant_url.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-24D6CCD6-E864-4CA6-8D91-5EFDFB50CB33-high.png)
+
+IMPORTANT
+
+In 3.4.0+ Subtenant users will no longer be able to login from the main login url without specifying their subdomain.
+
+## Configure Cloud-init Global Settings
+
+When using cloud-init, cloudbase-init, VMware Tools customizations, or Nutanix Sysprep, Global Linux User and Windows Administrator credentials can be set using the settings in Administration > Settings > Provisioning. It is recommended to define these settings after installation unless credentials are defined per Virtual Image for Provisioning.
+
+## Add a License Key
+
+In order to provision anything in HPE Morpheus Enterprise, a HPE Morpheus Enterprise License Key must be applied.
+
+If you do not already have a license key, one may be requested from <https://app.morpheushub.com> or from your HPE Morpheus Enterprise representative.
+
+In the Administration > Settings section, select the LICENSE tab, paste your License Key and click UPDATE
+
+![../../_images/license_key.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-1DE90FFC-D78A-4AEC-B168-D1AF1DF3E611-high.png)
+
+When the license is accepted, your license details will populate in the Current License section.
+
+If you receive an error message and your license is not accepted, please check it was copied in full and then contact your HPE Morpheus Enterprise representative. You can also verify the License Key and expiration at <https://app.morpheushub.com>.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json b/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
new file mode 100644
index 0000000..91c52a5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+  "title": "Power Scheduling",
+  "ordinal": 123,
+  "parent_title": "Automation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.html",
+  "topic_cluster": {
+    "clustering_title": "Power Scheduling",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E",
+        "clustering_title": "Power Scheduling"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md b/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
new file mode 100644
index 0000000..fe2efd6
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FAF9ECBA-F679-4F1B-A010-5B4AFAD65C4E.md
@@ -0,0 +1,114 @@
+# Power Scheduling
+
+Set weekly schedules for shutdown and startup times for Instances and VM’s, apply Power Schedules to Instances pre or post-provisioning, apply Power Schedule policies on Group or Clouds, or use Guidance to automatically recommend and apply optimized Power Schedules.
+
+## Create Power schedules
+
+### Procedure
+
+1. Navigate to Library > Automation > Power Scheduling
+2. Select + ADD
+3. Configure the following options: 
+
+   NAME
+   :   Name of the Power Schedule
+
+   DESCRIPTION
+   :   Description for the Power Schedule
+
+   TIME ZONE
+   :   Time Zone the Power Schedule times correlate to.
+
+   TYPE
+   :   Power On
+       :   Power Up and then Down at scheduled times
+
+       Power off
+       :   Power Down then Up at scheduled times
+
+       Enabled
+       :   Check for Power Schedule to be Active. Uncheck to disable Power Schedule.
+
+       DAYS
+       :   Slide the start and end time controls for each day to configure each days Schedule. Green sections indicate Power on, red sections indicate Power Off. Time indicated applies to selected Time Zone. The sliders can be used to set time in 15-minute steps, for single-minute granularity click the pencil icon and enter a specific time down to the minute.
+
+   ![../../_images/powerSchedule.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3FAFD413-3475-44A9-811A-575B689D836D-high.png)
+4. Select SAVE CHANGES
+
+### Results
+
+TIP
+
+To view the Instances a power schedule is currently set on, select the name of a Power Schedule to go to the Power Schedule Detail Page.
+
+## Add Power Schedule to Instance
+
+### Procedure
+
+1. Navigate to Provisioning > Instances
+2. Select an Instance
+3. Select EDIT
+4. In the POWER SCHEDULE dropdown, select a Power Schedule.
+5. Select SAVE CHANGES
+
+## Add Power Schedule to Virtual Machine
+
+### Procedure
+
+1. Navigate to Infrastructure  >  Compute  >  Virtual Machines
+2. Select a Virtual Machine
+3. Select EDIT
+4. Expand the Advanced Options section
+5. In the POWER SCHEDULE dropdown, select a Power Schedule.
+6. Select SAVE CHANGES
+
+## Add Power Schedule Policy
+
+### About this task
+
+NOTE
+
+Power Schedule Policies apply to Instances created after the Policy is enabled.
+
+### Procedure
+
+1. Navigate to Administration > Policies
+2. Select + ADD
+3. Select TYPE Power Schedule
+4. Configure the Power Schedule Policy: 
+
+   NAME
+   :   Name of the Policy
+
+   DESCRIPTION
+   :   Add details about your Policy for reference in the Policies tab.
+
+   Enabled
+   :   Policies can be edited and disabled or enabled at any time. Disabling a Power Schedule Policy will prevent the Power Schedule from running on the Clouds Instances until re-enabled.
+
+   ENFORCEMENT TYPE
+   :   - User Configurable: Power Schedule choice is editable by User during provisioning.
+       - Fixed Schedule: User cannot change Power Schedule setting during provisioning.
+
+   POWER SCHEDULE
+   :   Select Power Schedule to use in the Policy. Power schedule can be added in Library > Automation > Power Scheduling
+
+   SCOPE
+   :   Global
+       :   Applies to all Instances created while the Policy is enabled
+
+       Group
+       :   Applies to all Instances created in or moved into specified Group while the Policy is enabled
+
+       Cloud
+       :   Applies to all Instances created in specified Cloud while the Policy is enabled
+
+       User
+       :   Applies to all Instances created by specified User while the Policy is enabled
+
+       Role
+       :   Applies to all Instances created by Users with specified Role while the Policy is enabled
+
+   Permissions- TENANTS
+   :   Leave blank to apply to all Tenants, or search for and select Tenants to enforce the Policy on specific Tenants.
+5. Select SAVE CHANGES
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json b/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
new file mode 100644
index 0000000..240b8ba
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+  "title": "Appliance",
+  "ordinal": 322,
+  "parent_title": "Settings",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.html",
+  "topic_cluster": {
+    "clustering_title": "Appliance",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7",
+        "clustering_title": "Appliance"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md b/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
new file mode 100644
index 0000000..54e61d5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FB4FF7B6-7561-456F-8AC9-8415BE11B9E7.md
@@ -0,0 +1,189 @@
+# Appliance
+
+## Appliance Settings
+
+Appliance URL
+:   The default URL used for Agent install and Agent functionality. All Instances and Hosts must be able to resolve and reach this URL over 443 for successful agent install and communication.
+
+NOTE
+
+Alternate Appliance URLs can be configured per Cloud in the Edit Cloud  >  Advanced Options section.
+
+Internal Appliance URL (PXE)
+:   For PXE-Boot your appliance needs to be routable directly with minimal NAT masquerading. This allows one to override the default appliance url endpoint for use by the PXE Server. If this is unset, the default appliance url will be used instead.
+
+API Allowed Origins
+:   A CORS-related field which specifies the origins that are allowed to access the HPE Morpheus Enterprise API. For example, if you were designing a web application which needed to make AJAX calls to HPE Morpheus Enterprise API. The origins should be specified here. By default, all origins are allowed. When this field is filled, an exclusive whitelist of allowed origins is established.
+
+Cloud Sync Interval
+:   Data is refreshed through cloud integrations at the interval specified here in seconds, the default value is 300 seconds (five minutes). Appliances managing a very large number of clouds may be adversely affected by setting this value too low.
+
+Usage Retainment
+:   Determines how many days to keep account usage (metered costing data) records. Retainment period is not set by default. Usage records will remain indefinitely if Usage Retainment is not set. Note this does not affect generated Invoice records.
+
+Incident Retainment
+:   Enter the number of days HPE Morpheus Enterprise should keep incident records in the database. In general, this setting can be left alone but in certain cases may need to be adjusted as very large incident database tables can affect the stability of the application.
+
+Stats Retainment
+:   Select 30, 60 or 90 days period for stats retainment. Selecting a larger period gives the ability to analyze stats, such as Instance metrics, over a longer period of time. For example, in the Monitoring tab of an Instance detail page, users can select a 60 or 90-day analysis period if the stats have been retained that long
+
+Denied Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which should not be allowed sources for HTTP Tasks or REST-populated Option Lists.
+
+Approved Hosts
+:   A comma-delimited list of IP addresses and/or hostnames which are the only approved sources for HTTP Tasks or REST-populated Option Lists. By entering any values here, all others are automatically denied.
+
+Enable SSL Verification of Agent (Communications)
+:   Enabling SSL Verification of Agent Communications requires a valid Certificate be installed on the Appliance.
+
+Disable SSH Password Authentication
+:   Only allow ssh login using SSH keys. When true, SSH Password Authentication will not be enabled for VM’s and Hosts provisioned after the setting is enabled.
+
+Default Appliance Locale
+:   Sets the default language and region for all users on the HPE Morpheus Enterprise appliance. Users with individual language preferences may also override this selection on their User Settings page
+
+Default Console Gateway
+:   Select a configured HPE Morpheus Enterprise Worker as a console gateway or VDI gateway. For more on installation and configuration of a gateway, see the [VDI Gateways section](https://docs.morpheusdata.com/en/latest/tools/vdi_pools.html#vdi-gateways) of HPE Morpheus Enterprise documentation.
+
+Max Option List Size
+:   Sets a maximum size for Option Lists (such as those sourced from REST calls to a remote server) to preserve appliance performance in the event that a very large payload is inadvertently accessed. The entered number is multiplied by 1000 (for example, entering “1” results in a maximum list size of 1000).
+
+Dashboards to Display
+:   A typeahead field which will show all Dashboards available to the appliance from Dashboard-type plugins. Select all desired Dashboards and they will be displayed in the order set. Dashboards can be dragged up and down the list to set the order correctly.
+
+## Tenant Management Settings
+
+Registration Enabled
+:   If enabled, the appliance login screen will have a “NEED AN ACCOUNT? SIGN UP HERE” link added, enabling new Tenant registration.
+
+Default Tenant Role
+:   Sets the default Tenant Role applied to Tenants created from Tenant Registration.
+
+Default User Role
+:   Sets the default User Role applied to the User created from a Tenant Registration.
+
+## User Management Settings
+
+Min Password Length
+:   User passwords must at least be as many characters in length as the entered value
+
+Min Password Uppercase
+:   User passwords must include at least as many uppercase characters as the entered value
+
+Min Password Numbers
+:   User passwords must include at least as many numerals as the entered value
+
+Min Password Symbols
+:   User passwords must include at least as many special characters as the entered value
+
+Session Expires (Minutes)
+:   A user session is forcibly logged out after the entered number of minutes of inactivity
+
+Session Warning (Minutes)
+:   A pop-up warning is shown to the user when they have been inactive for the number of minutes entered. Example: If sessions are set to expire after 90 minutes, warn the user after 60 minutes if you intend to provide 30 minutes advance warning
+
+Expire Password After (Days)
+:   User account passwords will expire after the entered number of days. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User After Attempts (Number of Attempts)
+:   Disable a User account after a specified number of failed login attempts. Enter 0 or leave the field empty to opt out of this feature.
+
+Disable User If Inactive For (Days)
+:   Disable a User account if inactive for the entered number of days. The User will not be able to log into the appliance again until another User with sufficient rights enables the account. Enter 0 or leave the field empty to opt out of this feature.
+
+Send warning email before deactivating (Days)
+:   Enter the number of days prior to account deactivation that a warning email should be sent. For example, enter “5” to warn the User when they are five days short of the deactivation time entered in the prior field. Enter 0 or leave the field empty to opt out of this feature.
+
+## Email Settings
+
+In this section, you can configure an SMTP server for email notification delivery. You will need to provide HPE Morpheus Enterprise the following information, your mail server systems administrator can assist you in filling these fields and with the preferred encryption method.
+
+- From Address
+- SMTP Server
+- SMTP Port
+- SSL Enabled
+- TLS Encryption
+- SMTP User
+- SMTP Password
+
+We recommend that you add the HPE Morpheus Enterprise server to your SMTP whitelist as well as using user authentication as an additional security measure.
+
+Once you have added your SMTP server information into HPE Morpheus Enterprise, scroll down to the bottom of the page and press the blue SAVE button which can be found under the Enabled Clouds section.
+
+When you have saved your SMTP server settings in the HPE Morpheus Enterprise appliance you will then need to restart the UI. To restart the morpheus-ui, connect to your HPE Morpheus Enterprise server via SSH and run the below command:
+
+`sudo morpheus-ctl restart morpheus-ui`
+
+IMPORTANT
+
+If you do not restart morpheus-ui, the notifications will not be sent. Please note it can take up to three minutes for the UI to become reachable again.
+
+## Twilio SMS Settings
+
+Configure SMS text message delivery for HPE Morpheus Enterprise alerts. Previously, customers could use HPE Morpheus Enterprise’ own account for delivery, but for security reasons clients must now supply their own. Complete the fields indicated below and then restart all HPE Morpheus Enterprise nodes to apply the changes.
+
+- **Account SID:** Twilio Account SID
+- **SMS From #:** The “From” number to receive the text message from
+- **Auth Token:** The Twilio API authentication token for your account
+
+## Proxy Settings
+
+The HPE Morpheus Enterprise Appliance can be configured to communicate through a Proxy server for Cloud API’s and Agent communication back to the Appliance.
+
+NOTE
+
+Additional Proxy configuration is available in the Infrastructure  >  Network  >  Proxies section. Added Proxies can be scoped to Clouds in the Edit Cloud  >  Advanced Options section of the Cloud.
+
+Add a Global Proxy server by entering the following:
+
+- Proxy Host
+
+  : Specifies the hostname or IP address of the proxy server.
+- Proxy Port
+
+  : Specifies the port number used by the proxy server to communicate.
+- Proxy User
+
+  : Specifies the username used to authenticate with the proxy server.
+- Proxy Password
+
+  : Specifies the password associated with the proxy user account.
+- Proxy Domain
+
+  : Specifies the authentication domain for the proxy user.
+- Proxy Workstation
+
+  : Specifies the workstation name used for proxy authentication.
+- No Proxy
+
+  : Specifies a list of hosts that should bypass the proxy.
+
+## Currency Settings
+
+In HPE Morpheus Enterprise, Tenants are separate environments which can be defined as using currencies that are unique from one Tenant to the next. In addition, these currencies may be different from the currency in which Price Sets have been defined. In order to present pricing to Subtenant users in their designated currency, HPE Morpheus Enterprise allows for integration with currency conversion services “open exchange rates” and “fixer.io”. This article goes through the process of setting up the integration and how it works to determine pricing conversions.
+
+## Integrating With a Currency Exchange Provider
+
+### Procedure
+
+1. Navigate to Administration > Settings > Appliance
+2. Under the Currency Settings heading, make a “Currency Provider” selection
+3. Enter your “Provider API Key”
+
+### Results
+
+The service is now integrated and can be used as described in the next section.
+
+## Consuming Currency Exchange in HPE Morpheus Enterprise
+
+Currency exchange data is synced from the integrated provider once every 12 hours. When needed, Morpheus will use this cached data to present currency conversions rather than hitting the API directly each time. This limits the total number of API hits and reduces costs.
+
+Exchanged currency values will be shown under conditions similar to the following scenario:
+
+A user is working in a Subtenant configured for Currency B. The user is attempting to provision an instance with pricing sets that have only been defined in Currency A. Morpheus will convert the pricing data from currency A to Currency B for this user (and all users in this Subtenant) since price conversion has been enabled.
+
+## Enabled Clouds (Types)
+
+Controls which types of Cloud can be created.
+
+- When a Cloud type is disabled, it will be removed from the available options when adding new Clouds in Infrastructure  >  Clouds. Existing Clouds are not affected by changes to this setting.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json b/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
new file mode 100644
index 0000000..8fc91aa
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+  "title": "Adding the OpenShift Plugin",
+  "ordinal": 206,
+  "parent_title": "OpenShift Clusters",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.html",
+  "topic_cluster": {
+    "clustering_title": "Adding the OpenShift Plugin",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FBA4AD60-9130-49BD-B10F-074439138A4B",
+        "clustering_title": "Adding the OpenShift Plugin"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md b/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
new file mode 100644
index 0000000..f782676
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FBA4AD60-9130-49BD-B10F-074439138A4B.md
@@ -0,0 +1,13 @@
+# Adding the OpenShift Plugin
+
+The OpenShift integration is developed as a standalone plugin for HPE Morpheus Enterprise, which is not included in the product by default.
+
+1. To download the plugin, navigate to the plugin share site (share.morpheusdata.com) and browse or search for the OpenShift plugin
+2. With the plugin downloaded to your workstation, navigate to the plugins list page (Administration > Integrations > Plugins) in HPE Morpheus Enterprise UI
+3. Click Add
+4. Browse for the plugin JAR or drag and drop it onto the target
+5. Click Upload
+
+After a few brief moments, the new plugin will be added. This plugin adds a new Cluster type, which can be added from the Clusters list page (Infrastructure > Clusters) and also adds a new Instance Type which can be provisioned from the Instance provisioning wizard once a compatible cluster is integrated.
+
+Further configuration and usage details are covered in later sections of this guide.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json b/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
new file mode 100644
index 0000000..e3d70cf
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+  "title": "See Also",
+  "ordinal": 529,
+  "parent_title": null,
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.html",
+  "topic_cluster": {
+    "clustering_title": "See Also",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8",
+        "clustering_title": "See Also"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md b/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
new file mode 100644
index 0000000..bab8c84
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FCB5E6FB-1C68-4B5B-8C8C-0B9803DB90F8.md
@@ -0,0 +1,14 @@
+# See Also
+
+**Subtopics**  
+
+- **[Navigation Updates](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C1F33430-1CA3-47FB-9BEA-767738C1DA94.html)**
+- **[Integrations](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-768B1CD6-73F8-4CBC-9675-E03000B36147.html)**
+- **[Creating a HPE Morpheus Enterprise VMware Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-AB13B0F1-6759-49B6-9EFB-7D7B75D95798_2.html)**
+- **[Creating a Windows Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-C45628C9-77B0-48E5-84A0-55B1EF41F0CA_2.html)**
+- **[Creating a CentOS/RHEL 7 Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-FB1EB109-EDF5-4B45-9ACF-60EA214E50D2_2.html)**
+- **[Creating a CentOS/RHEL 8 Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-B88D86E8-E689-4AF7-ABB7-44760FE9EC42_2.html)**
+- **[Creating an Ubuntu 20.04 Image](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-5E1D1576-AB5F-4842-842F-A314D73E97AD_2.html)**
+- **[Gotchas](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-266213A6-ED4A-4F33-BE4D-12D1E399C66F_2.html)**
+- **[A Note on Proxies](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-62D603EE-56F3-478D-9625-2FC3B6F189E8_2.html)**
+- **[Task Results](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/render?page=GUID-84B6C16D-5601-4CFB-9C53-47AE75271884_2.html)**
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json b/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
new file mode 100644
index 0000000..c8aa326
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+  "title": "Failover",
+  "ordinal": 190,
+  "parent_title": "Monitoring the Cluster",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.html",
+  "topic_cluster": {
+    "clustering_title": "Failover",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E",
+        "clustering_title": "Failover"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md b/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
new file mode 100644
index 0000000..bcac42d
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FE2F3DC5-2758-41C2-906B-F3DAFDBB538E.md
@@ -0,0 +1,17 @@
+# Failover
+
+HVM supports automatic failover of running workloads in the event of the loss of a host. Administrators can control the failover behavior through the “Manage Placement” action on any running VM. From the VM detail page, click ACTIONS and select “Manage Placement”. Any VM with a placement strategy of “Auto” or “Failover” will be eligible for an automatic move in the event its host is lost. When the loss of a host does occur, the workload will be up and running from a different cluster host within just a short time if it’s configured to be moved during an automatic failover event. Any VMs pinned to a lost host will not be moved and will not be accessible if the host is lost. When the host is restored, those VMs will be in a stopped state and may be restarted if needed.
+
+This three-node cluster has three VMs running on the first host:
+
+![../../_images/threeRunningWorkloads.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D85300D8-59A9-406D-99F4-2A83E4812C52-high.png)
+
+Each of these VMs is configured for a different failover strategy. When the host is lost, we should expect to see the first two VMs moved to an available host (since they have the “Auto” and “Failover” placement strategies, respectively). We should not see the third VM moved.
+
+![../../_images/auto.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-4AF17304-D863-46CD-B761-F76CA83B5DA1-high.png) ![../../_images/failover.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-450A2043-9995-4352-B52F-0D85D7A9500E-high.png) ![../../_images/pinned.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-3C5798EF-8010-4C2C-A9C1-B1A07D5BBCE3-high.png)
+
+After loss of the host these three VMs were running on, we can see the lost host still has one associated VM in a stopped state. The other two VMs are running on a second host which is still available.
+
+![../../_images/lostNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-69BB84AC-5461-4818-A90F-10BB7308E937-high.png) ![../../_images/liveNode.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-688399E1-CBDA-4B89-AC61-80CF6FCBEBCD-high.png)
+
+When the lost host returns, the moved VMs will come back to their original host. The third VM is associated with this host as well and is in a stopped state until it is manually restarted.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json b/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
new file mode 100644
index 0000000..9990c7a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+  "title": "Provisioning Images",
+  "ordinal": 150,
+  "parent_title": "Virtual Images",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.html",
+  "topic_cluster": {
+    "clustering_title": "Provisioning Images",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FE7CCD11-6021-491F-BC50-596DA68F9206",
+        "clustering_title": "Provisioning Images"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md b/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
new file mode 100644
index 0000000..f77c843
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FE7CCD11-6021-491F-BC50-596DA68F9206.md
@@ -0,0 +1,13 @@
+# Provisioning Images
+
+When provisioning a system image, HPE Morpheus Enterprise will stream the image from Amazon S3 to the target Cloud if the image is not local to the Cloud.
+
+When using images that already exist in the destination Cloud, such as synced, marketplace, or previously copied images, no image stream from S3 through the HPE Morpheus Enterprise Appliance to the destination cloud will take place.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able to download from Amazon S3 when provisioning system images.
+
+NOTE
+
+The HPE Morpheus Enterprise Appliance must be able reach and resolve the destination Host when provisioning System Images or uploaded Images for the first time. This included being able to resolve ESXi host names in VMware vCenter clouds, and reach the destination ESXi host over port 443.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json b/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
new file mode 100644
index 0000000..41a21b5
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+  "title": "Creating Apps",
+  "ordinal": 88,
+  "parent_title": "Apps",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.html",
+  "topic_cluster": {
+    "clustering_title": "Creating Apps",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B",
+        "clustering_title": "Creating Apps"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md b/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
new file mode 100644
index 0000000..8db584a
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FEDEE0B4-AD5A-493D-A873-4E352B45D69B.md
@@ -0,0 +1,56 @@
+# Creating Apps
+
+New Apps can be created from Blueprints or using existing Instances.
+
+## Creating Apps from Blueprints
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select an existing App Blueprint and click NEXT. 
+
+   NOTE
+
+   App Blueprints must be created in Library > Blueprints > App Blueprints to appear as options when provisioning an App.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected.
+4. Click NEXT. Blueprint configurations matching the Group, Cloud and Environment selections will auto-populate the configurations of the Instances in the App. If no Blueprint Configuration matched the Group, Cloud or Env selections, the Instances will have default configurations.
+5. Configure your Instances. Depending on the Blueprint Configurations settings, instances may already be fully configured. Fields that are locked in a Blueprint cannot be edited when creating an App. 
+
+   NOTE
+
+   Once an Instance is fully configured, a green checkmark will appear next to the Instance. Instances that have required fields that need populated will have a red X and must be completed. If your Blueprint is already fully configured, you can simply select COMPLETE!
+6. Select COMPLETE and the App will be created, and the Instances will begin provisioning.
+
+### Results
+
+![../../_images/apps_301_1.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-F0EDC63A-480C-4013-AC6D-A1C51BA13CC7-high.png)
+
+## Creating Apps from Existing Instances
+
+### Procedure
+
+1. Click +ADD on the right side of the main Apps section in Provisioning.
+2. Select `APP FROM EXISTING INSTANCES` from the Blueprints list and click NEXT.
+3. Enter a Name for the App and select a Group. Default Cloud and Env can also be selected. 
+
+   NOTE
+
+   Only instances within the selected Group and Cloud will be available to be added to the App.
+4. In the STRUCTURE section, select + to add a Tier
+5. Select or enter a Tier Name.
+6. Select the Tier to set Boot Order, rename, or once multiple Tiers are added, connect the Tier to other Tiers.
+7. In the STRUCTURE section, select + in a Tier to add an Instance
+8. Select the Instance Type of the Existing Instance to be added to the App.
+9. In the STRUCTURE section, select the Instance.
+10. In the CONFIGURATION section, select the Cloud the Existing Instance is in. Existing INSTANCES that match the Group, Cloud and Instance Types set will populate.
+11. Select the desired Instance from the INSTANCES list. Selected instance will show in the SELECTED INSTANCE section. 
+
+    NOTE
+
+    Only one existing Instance can be added per Instance. To add multiple Existing Instances, repeat the step above including adding an Instance for each Existing Instance to be added to the App.
+12. Once all Existing Instances have been selected, click COMPLETE.
+13. A new App will be created out of the Existing Instances.
+
+### Results
+
+![../../_images/apps_301_2.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-2EECD2F1-36D5-4E56-B12D-99872F54B075-high.png)
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json b/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
new file mode 100644
index 0000000..759e178
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+  "title": "Boot Prompt Configuration",
+  "ordinal": 413,
+  "parent_title": "Windows OS Imaging",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.html",
+  "topic_cluster": {
+    "clustering_title": "Boot Prompt Configuration",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9",
+        "clustering_title": "Boot Prompt Configuration"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md b/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
new file mode 100644
index 0000000..8675424
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FEF7530C-DBA2-4B59-A328-96ADBBCC27B9.md
@@ -0,0 +1,30 @@
+# Boot Prompt Configuration
+
+Unmodified Microsoft Windows Server ISOs display a Press any key to boot CD/DVD… prompt, which will interrupt unattended bare metal deployments.
+
+Two approaches are supported:
+
+- Option 1: Use a Modified ISO (Recommended)
+- Option 2: Manual Console Interaction
+
+## Option 1: Use a Modified ISO (Recommended)
+
+Use a Windows ISO with the boot prompt removed. A script to generate such an ISO is available at `https://github.com/HewlettPackard/hpegl-metal-os-windows-iso`
+
+Only the resulting ISO is required. A prebuilt Windows Server 2022 Evaluation ISO with this modification is also available and suitable for testing environments.
+
+## Option 2: Manual Console Interaction
+
+If using an unmodified ISO:
+
+1. Create the instance as usual.
+2. When the instance enters provisioning, open the Remote Console.
+3. Press Enter when prompted to boot from the installation media.
+
+## Windows Licensing Considerations
+
+At present, Windows licensing is not supported during bare metal provisioning.
+
+Only Evaluation editions or versions that do not require a Product Key in AutoUnattend.xml can be deployed.
+
+The modified Windows Server 2022 ISO referenced above is an Evaluation edition and is suitable for testing.
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json b/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
new file mode 100644
index 0000000..8d0668f
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+  "title": "Installation Overview",
+  "ordinal": 15,
+  "parent_title": "Installation",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.html",
+  "topic_cluster": {
+    "clustering_title": "Installation Overview",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832",
+        "clustering_title": "Installation Overview"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md b/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
new file mode 100644
index 0000000..d86e675
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FF4390B9-DCC2-4CE1-A9CC-C883A735E832.md
@@ -0,0 +1,111 @@
+# Installation Overview
+
+IMPORTANT
+
+HPE Morpheus Enterprise v4.2.0 enhanced security configuration restricts incoming appliance connections to TLS v1.2, potentially impacting front-end load balancer monitoring/health checks that support only TLS v1.1 or lower, as well as HPE Morpheus Enterprise Agent installations for Windows nodes using .net versions that do not support TLS v1.2. Refer to TLS
+
+HPE Morpheus Enterprise comes packaged as a `debian` or `yum` based package. The default configuration installs all required services on a single vm or bare metal Host. Morpheus can be configured in a distributed architecture to use one or multiple external services, and multiple application Hosts can be configured for High Availability configurations.
+
+All components required for Morpheus are installed and configured by default during the Morpheus `reconfigure` command. The Morpheus config file, `morpheus.rb`, can optionally be configured to point the Morpheus App to external services (distributed configuration).
+
+Morpheus can optionally be configured to use external Database, Messaging, and/or Search Tiers. This means instead of installing, for example, MySQL on the same host as the Morpheus App, the Morpheus configuration file (morpheus.rb) is setup to point to an external MySQL host, cluster or service, and MySQL will not be installed or configured on the Appliance Host.
+
+## Install Packages
+
+HPE Morpheus Enterprise Release Package URLs can be obtained from My HPE Software Center.
+
+## Configuration Options
+
+- Single Host (All-In-One/default)
+  :   All tiers running on a single host. The reconfigure process installs all required services. This is the default configuration.
+- Single Hosts with Distributed Service(s)
+  :   Transactional Database, Non-Transactional Database, and/or Message tiers are externalized, with the remaining services on a single host. The reconfigure process installs all services not set to false in `/etc/morpheus/morpheus.rb`
+- Clustered Hosts with Distributed Transactional Database (3-Node HA)
+  :   Application, Message and Non-Transactional tiers are installed and clustered on three or more hosts, with all three hosts pointing to externalized database tier. The reconfigure process installs all services except mySQL.
+- App Host(s) with Distributed Services (Full HA)
+  :   Application tier is installed on one or more hosts. All UI hosts point to externalized Transactional Database, Non-Transactional Database, and Message Tiers. The reconfigure process installs only Application services.
+
+## Distributed Configurations
+
+Morpheus provides a wide array of options when it comes to deployment architectures. It can start as a simple one machine instance where all services run on the same machine, or it can be split off into individual services per machine and configured in a high availability configuration, either in the same region or cross-region. Naturally, high availability can grow more complicated, depending on the configuration you want to do and this article will cover the basic concepts of the Morpheus HA architecture that can be used in a wide array of configurations.
+
+There are four primary tiers of services represented within the Morpheus appliance. They are the Application Tier, Transactional Database Tier, Non-Transactional Database Tier, and Message Tier. Each of these tiers have their own recommendations for High availability deployments that we need to cover.
+
+### Application Tier
+
+The application tier is easily installed with the same Debian or yum repository package that Morpheus is normally distributed with. Advanced configuration allows for the additional tiers to be skipped and leave only the “stateless” services that need run. These stateless services include Nginx and Tomcat. These machines should also have at least 8gb of Memory. They can be configured across all regions and placed behind a central load-balancer or Geo based load-balancer. They typically connect to all other tiers as none of the other tiers talk to each other besides through the central application tier. One final piece when it comes to setting up the Application tier is a shared storage means is necessary when it comes to maintaining things like deployment archives, virtual image catalogs, backups, etc. These can be externalized to an object storage service such as Amazon S3 or Openstack Swiftstack as well. If not using those options a simple NFS cluster can also be used to handle the shared storage structure.
+
+### Transactional Database Tier
+
+The Transactional database tier usually consists of a MySQL-compatible database. It is recommended that a lockable clustered configuration be used. There are several documents online related to configuring and setting up such a cluster but it most simply can be laid out in a many-master configuration. There can be some nodes setup with replication delay as well as some with no replication delay. It is common practice to have no replication delay within the same region and allow some replication delay cross region. This does increase the risk of job run overlap between the 2 regions however, the concurrent operations typically self-correct and this is a non-issue.
+
+### Non-Transactional Database Tier
+
+The Non-Transactional tier consists of an OpenSearch (version 7.6.0) cluster. OpenSearch is used for log aggregation data and temporal aggregation data (essentially stats, metrics, and logs). This enables for a high write throughput at scale. OpenSearch is a Clustered database meaning all nodes no matter the region need to be connected to each other over what they call a “Transport” protocol. It is fairly simple to get setup as all nodes are identical. It is also a Java-based system and does require a sizable chunk of memory for larger data sets. 8 GB is recommended and more nodes can be added to scale either horizontally or vertically.
+
+### Messaging Tier
+
+The Messaging tier is an AMQP based tier along with STOMP Protocol (used for agent communication). The primary model recommended is to use RabbitMQ for queue services. RabbitMQ is also a cluster-based queuing system and needs at least 3 instances for HA configurations. This is due to elections in the failover scenarios RabbitMQ can manage. If doing a cross-region HA RabbitMQ cluster, it is recommended to have at least 3 Rabbit queue clusters per region. Typically to handle HA a RabbitMQ cluster should be placed between a load balancer and the front-end application server to handle cross host connections. The ports necessary to forward in a Rabbit MQ cluster are (5672, and 61613). A RabbitMQ cluster can run on smaller memory machines depending on how frequent large requests bursts occur. 4 - 8 GB of Memory is recommended to start.
+
+## Pros/Cons
+
+### Single Host
+
+Advantages
+:   - Simple Installation - Morpheus Installs all required services
+    - Simple Configuration - Morpheus configures all required services
+    - Simple Maintenance - All service connections and credentials are local - All logs are local - All Data is local (by default)
+    - Not dependent on network connections for vital services - Facilitates speed and reliability
+
+Disadvantages
+:   - Single point of failure
+    - Individual services cannot be scaled
+    - Upgrades require (minimal) downtime
+    - Single region
+
+### Single Hosts with Distributed Service(s)
+
+Advantages
+:   - Individual services can be scaled
+    - Managed Services such as RDS can be utilized
+
+Disadvantages
+:   - Single region
+    - External services require additional configuration and maintenance
+    - Morpheus is subject to network performance, configuration and availability
+    - Increased Installation time possible
+
+### Clustered Hosts with Distributed Transactional Database
+
+Advantages
+:   - Database can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - RabbitMQ and Opensearch Clusters
+
+Disadvantages
+:   - External Database services requires additional configuration and maintenance
+    - App Host Clustering requires additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+
+### App Host(s) with Distributed Services
+
+Advantages
+:   - Individual services can be scaled vertically and/or horizontally
+    - Managed Services such as RDS can be utilized
+    - Zero down time upgrades
+    - No single point of failure
+    - Multi region support
+
+Disadvantages
+:   - External services require additional configuration and maintenance
+    - Extended Installation time
+    - Increased Infrastructure Requirements
+    - Increased Networking requirements
+    - Load Balancer required to front App Hosts
+    - Shared Storage configuration required
+    - Rabbit Load balancer required
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json b/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
new file mode 100644
index 0000000..72c0295
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.json
@@ -0,0 +1,26 @@
+{
+  "bundle_id": "morpheus_user_manual_8_1_2",
+  "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+  "title": "Costing: Budget Analysis",
+  "ordinal": 63,
+  "parent_title": "Analytics",
+  "doc_id": "sd00007732en_us",
+  "version": "8.1.2",
+  "product": "User Manual",
+  "source_url": "https://support.hpe.com/hpesc/public/docDisplay?docId=sd00007732en_us&page=GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.html",
+  "topic_cluster": {
+    "clustering_title": "Costing: Budget Analysis",
+    "clustered_topics": [
+      {
+        "bundle_id": "morpheus_user_manual_8_1_0",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      },
+      {
+        "bundle_id": "morpheus_user_manual_8_1_1",
+        "page_id": "GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA",
+        "clustering_title": "Costing: Budget Analysis"
+      }
+    ]
+  }
+}
diff --git a/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md b/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
new file mode 100644
index 0000000..0eb6f93
--- /dev/null
+++ b/corpus/morpheus_user_manual_8_1_2/GUID-FFA7E948-6DC0-49D2-A47F-9FC1690A0ACA.md
@@ -0,0 +1,25 @@
+# Costing: Budget Analysis
+
+![../_images/6budgetanalysis.png](https://support.hpe.com/hpesc/public/api/document/sd00007732en_us/GUID-D7C44885-681F-4B92-8D83-E5EB52F25660-high.png)
+
+The Budget Analysis dashboard allows administrators to filter and view budgets in one place in order to keep track of progress against budget over time. Budgets in HPE Morpheus Enterprise (Operations > Budgets) are tied to a specific scope (Account, Tenant, Cloud, Group, or User) and budgets of the same scope are viewed together in this dashboard. A scope filter must be set in order for data to be populated into the dashboard. Once a scope is selected, the search bar can be utilized to return only budgets within the selected scope whose “Name” meets the search terms.
+
+## Filters
+
+Filter the budgets pulled into the dashboard by one or more of the following fields:
+
+- Budget name (all matched by search)
+- Scope (This is a required field, data is not populated into the dashboard until a scope is specified)
+
+## Data Displayed
+
+The following aggregate totals are compiled for all budgets that meet set filters:
+
+- **BUDGETS:** The total number of budgets that meet set filters
+- **MONTH TO DATE:** The total spend in the current month against the selected budgets
+- **BUDGETS TO DATE:** The total amount budgeted to date among budgets selected by the dashboard filters (from the start of the year to the end of the current interval)
+- **TO BUDGET:** The difference between the COST TO DATE and BUDGETS TO DATE value, should be close to $0 if the costs are appropriately tracking against the budgeted amounts
+
+## Budget List
+
+Each budget with its own graph and breakdown is displayed going down the page. The format of the information presented depends on the interval that the specific budget is configured for.